The organization that built R-Series is its own first deployment. Each lane has an independent ed25519 key, registered under the fleet root. Every lane action is signed by that lane and countersigned by the manager (R+5 federation). Each day's activity is aggregated into one Merkle root anchored on Base. Everything below is re-verified in your browser — no trust in our servers required.
Each lane's identity is attested by a fleet-root-signed registration. Status and receipt counts below are computed from the signed roster + the day's receipts.
| Lane | Role | Status | Fingerprint | Receipts | Activity | In root |
|---|---|---|---|---|---|---|
| Loading roster… | ||||||
Each UTC day's lane receipts fold into one R+3 Merkle root (SHA-256, domain-separated, promote-not-duplicate) and are anchored on Base mainnet. Days chain to each other via prev_bundle_hash.
Anti-gaming score computed live from the fleet's signed receipts: manager-countersigned work counts ×2, disputes −4, unwitnessed self-issued work capped at 0.25. Higher = more independently-verified contribution.
The complete R-Series check, run entirely in your browser against the live fleet data already loaded above — registrations, lane signatures, post-quantum co-signatures (ML-DSA-65), manager countersignatures, transparency-log inclusion, and the anchored Base root. Every result is explicit: verified, failed, or unavailable — never a simulated pass.