Noesea

Protocol Console

Use the protocol, end to end.

Every claim ID, evidence hash, commitment, and piece of calldata below is computed by the Noesea SDK — the same code the contracts and CLI use. Connect a wallet to broadcast; without one you still get real, verifiable artifacts and the exact calldata.

Network

Local Anvil · chain 31337

RPC http://127.0.0.1:8545

No injected wallet — read-only mode.
Artifacts & calldata are still real.

Pointed at the local dev deploy (chainId 31337). Run make dev and point a wallet at http://127.0.0.1:8545 to broadcast. Configure a testnet via the NEXT_PUBLIC_* env vars.

Already have a claim?

Skip step 1 to anchor evidence, dispute, vote, or read a verdict for an existing claim.

1

Register a claim

Canonicalize a statement into a deterministic claim ID and anchor it on ClaimsRegistry.

2

Anchor evidence

Hash a file or snippet and bind it to the claim on EvidenceRegistry. Content stays off-chain; only the hash is anchored.

Register or paste a claim in step 1 first — evidence anchors against a claim ID.

3

Stake & take a dispute position

Deposit NOESEA into StakingEscrow, then open a dispute or join its bounded pre-jury market on either side with accountable stake.

Register or paste a claim in step 1 first.

4

Juror vote — commit & reveal

Selected jurors commit a hidden vote, then reveal it with the same salt. The commitment binds the vote to this dispute and juror.

Register or paste a claim in step 1 first. Only jurors selected by the protocol randomness process can commit or reveal on-chain; the artifacts compute regardless.

5

Appeal a finalized verdict

Read the exact account-specific appeal terms, fund the escrow, and declare the side the next jury should hear.

Register or paste a claim in step 1 first.

6

Verdict

Read the finalized on-chain verdict, confidence, and settlement direction straight from DisputeEngine.

Register or paste a claim in step 1 first.