Lineage
Sigvara did not start on Arc. The same protocol, identity, reputation, staking, epoch fees, oracle and SDK, ran as a public testnet on Robinhood Chain for a month under its earlier name, Countersig Network. This page records that run so anyone can check it. Every value below was read from the chain and its explorer on 17 September 2026. Every address and transaction below is on a public explorer, so none of it rests on this site being truthful.
Deployment
| Item | Value |
|---|---|
| Network | Robinhood Chain testnet, chain ID 46630 |
| Deployed | 15 July 2026, 02:40 UTC, block 90338571 |
| Deployer | 0xfB38fA3C085FD9D06564524855d00E098ae0c450 |
| Identity proxy | 0xCCF2Fd69c07EDFbc3C215cfD31e2F20FC208A16C |
| Reputation proxy | 0xbB0c9C2DF28af31905dEfEa04c80372C0909f1bF |
| Staking proxy | 0x7281cf35ae9Bf56EAF5B1d0C2C8e167e50BCEC75 |
| Epoch-fee registry proxy | 0x9a9b6A49f3FE1C02Fb1b5cB7f2911Add0ce2e2bb, deployed 16 July 2026 |
| Testnet bond token | CSIG faucet token, 0x7E44aF56d14EBfd16D5D7Ba4F011b5206d487D55, 1,000 minted, no value |
| Creation transactions | identity 0x36fd2ea5…8430 · reputation 0x0aeadd94…7405 · staking 0x1923d98a…e88d · fee registry 0x9130edb6…c18c |
Live parameters as read on 17 September 2026: minimum stake 1,000 CSIG, slash challenge period 7 days, unbonding period 21 days, score challenge window 30 minutes (a testnet setting; Arc uses 6 hours), epoch fee 0. A legacy Sepolia deployment from 30 June 2026 preceded it.
What ran
- Reputation oracle, hourly epochs. The oracle wallet called
proposeReputationandfinalizeReputationevery hour. The reputation contract shows 2,470 transactions between deployment and the last epoch on 14 August 2026, 18:19 UTC: roughly 1,200 scoring epochs over 30 days. - Registered agents. Three agents registered through the identity registry, at blocks
90339181,90758493and90820089. Their scores were rewritten every epoch; the last finalized values on chain are 24 and 63 out of 100, consistent with the six-factor model's ramp-up curve for agents a few weeks old with mixed activity. - Attestation and flag feeds. CounterAudit consumed scores and fed work-outcome attestations back; a rug-risk scanner reported red-verdict deployers as community flags. These were the live inputs behind the success and community factors.
- SDK. The protocol SDK was published to npm and used for the live integration tests against this deployment.
- Not exercised. No bonds were deposited on testnet (the staking proxy has only its deployment transaction) and no slash was filed. The slashing path is covered by the contract test suite and by the interactive demo, not by this run.
Why the name changed
In late June 2026, while the protocol was still on Sepolia, an unrelated party copied the Countersig profile and brand images, scraped from the public repository, and launched a token under the Countersig name on a memecoin launchpad. Nothing trading under that name came from this team. The project had no token and had said so. An anti-impersonation notice went up on 1 July 2026, and on 15 July the direction was fixed as oracle-first with any token deferred. The Robinhood Chain testnet run continued under the Countersig name through August.
On 17 September 2026 the protocol was renamed Sigvara, with a new domain and new brand assets, so that the name people verify against is one that has never been attached to a token. The code, deployments and history on this page are the continuity.
What changed on the way to Arc
- Contracts renamed from Countersig to Sigvara; storage layouts unchanged.
- Score challenge window set to 6 hours for Arc (30 minutes on the testnet).
- Slash exit-dodge closed via the unbonding queue (22 July 2026), which is why
executeSlashsweeps queued withdrawals. - ERC-8004 adopted as the canonical identity registry; the on-chain Ed25519 key and slash status remain Sigvara's extension.
- Bond token moved from the faucet
CSIGto a deploy-time address, so the same scripts serve testnet and mainnet.
Caveats
- The Robinhood testnet contracts are not source-verified on the explorer. Bytecode and the broadcast records in the earlier repository are the evidence.
- The agent scores quoted above are point-in-time reads. The deployment has been dormant since 14 August 2026 and the network may reset it at any time.