ClawRTC — Mine RTC Tokens With Your AI Agent
Your Claw agent can earn RTC (RustChain Tokens) by proving it runs on real hardware. One command to install, automatic attestation, built-in wallet.
Quick Start
pip install clawrtc
clawrtc install --wallet my-agent-miner
clawrtc start
That's it. Your agent is now mining RTC.
How It Works
- Hardware Fingerprinting — 6 cryptographic checks prove your machine is real hardware (clock drift, cache timing, SIMD identity, thermal drift, instruction jitter, anti-emulation)
- Attestation — Your agent automatically attests to the RustChain network every few minutes
- Rewards — RTC tokens accumulate in your wallet each epoch (~10 minutes)
- VM Detection — Virtual machines are detected and receive effectively zero rewards. Real iron only.
Multipliers
| Hardware | Multiplier | Notes |
|---|---|---|
| Modern x86/ARM | 1.0x | Standard reward rate |
| Apple Silicon (M1/M2/M3) | 1.2x | Slight bonus |
| PowerPC G5 | 2.0x | Vintage bonus |
| PowerPC G4 | 2.5x | Maximum vintage bonus |
| VM/Emulator | ~0x | Detected and penalized |
Commands
| Command | Description |
|---|---|
clawrtc install |
Download miner, create wallet, set up service |
clawrtc start |
Start mining in background |
clawrtc stop |
Stop mining |
clawrtc status |
Check miner + network status |
clawrtc logs |
View miner output |
clawrtc uninstall |
Remove everything |
What Gets Installed
- Miner scripts from RustChain repo
- Python virtual environment with
requestsdependency - Systemd user service (Linux) or LaunchAgent (macOS)
- All files in
~/.clawrtc/
VM Warning
RustChain uses Proof-of-Antiquity (PoA) consensus. The hardware fingerprint system detects:
- QEMU / KVM / VMware / VirtualBox / Xen / Hyper-V
- Hypervisor CPU flags
- DMI vendor strings
- Flattened timing distributions
If you're running in a VM, the miner will install and attest, but your rewards will be effectively zero. This is by design — RTC rewards machines that bring real compute to the network.
Requirements
- Python 3.8+
- Linux or macOS (Windows installer coming soon)
- Real hardware (not a VM)
Links
License
MIT — Elyan Labs
Metadata
Release files for clawrtc 1.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| clawrtc-1.9.0.tar.gz | 51.9 kB | Without provenance | Details for clawrtc-1.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| clawrtc-1.9.0-py3-none-any.whl | Python 3 | none | any | Details for clawrtc-1.9.0-py3-none-any.whl |
Total release size: 106.2 kB
Release files / clawrtc-1.9.0.tar.gz
| Download URL | clawrtc-1.9.0.tar.gz |
|---|---|
| Size | 51.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7a2351a3d5b3869187588b12f37f5008216892cc0be8b4cd0ce09e711be51a1
|
|
BLAKE2b-256 checksum How to use checksums |
d62f06ae57402f77c04c13c1b221b31960fa479b3a276fc3ef36dbcb1612052f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / clawrtc-1.9.0-py3-none-any.whl
| Download URL | clawrtc-1.9.0-py3-none-any.whl |
|---|---|
| Size | 54.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14618065ba2d3c8f25de1550068a58290057df7d95c39e3345a973c0700207c6
|
|
BLAKE2b-256 checksum How to use checksums |
771cd84916ce3e6660a00614fe7252b2427a58a619def9e9994c3f62e29b4102
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for clawrtc 1.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.