On-Chain
Proof
A score means nothing if it can be edited later. Accepted blueprints are attested with EIP-712 signatures and anchored by a quorum of authorised validators, so provenance survives the protocol that produced it.
Chain Robinhood / 4663
Standard EIP-712
Phase Testnet
Relay Runtime
Attestation Payload
| Field | Type | Purpose |
|---|---|---|
| motionHash | bytes32 | Identifies the exact trajectory |
| contributor | address | Who submitted the blueprint |
| roboScore | uint8 | Composite validation score |
| viability | uint16 | Operational viability, fixed point |
| tier | uint8 | Validation tier at acceptance |
| nonce | uint256 | Blocks attestation replay |
Contract Surface
| Function | Access | Effect |
|---|---|---|
| anchorProof(hash, score, sigs) | Quorum | Records a proof once enough authorised signatures verify |
| getProof(motionHash) | Public view | Returns the stored proof record |
| isAnchored(motionHash) | Public view | Cheap existence check for indexers |
| hashAttestation(...) | Public view | Recomputes the EIP-712 digest clients must sign |
| setValidator(addr, bool) | Owner | Adds or removes an authorised signer |
| setQuorum(n) | Owner | Changes how many signatures an anchor requires |
Deployment status
The KineticProof contract is written and unit tested, and proofs settle on testnet during the current phase. Mainnet attestation and veRONET-secured signer locking are planned, not live. Do not treat testnet records as final settlement.