Ward · 05 · Protect>Live

On-Chain Threat State & Protection

WARD publishes authenticated threat state so explicitly integrated contracts can apply predefined policies. Critical state changes require a quorum of independent reviewer signatures — never an unverified AI response alone.

01Threat state · read on-chain

What integrators see right now

Read directly from the WeaverWard contract on every request. If the read fails, no state is shown in its place.

Current threat state

Baseline

Sequence #2 · updated 2026-10-12 11:38:57 UTC

Network: Robinhood Chain Testnet (46630)
Contract: 0x594b56…54D4
Evidence hash: 0xa35734d375…efdd1927
Policy version: 0xabc5e63ea0…86ee89ed

02Registered reviewer signers

2 of 3 reviewers must sign

Independent keys registered in the contract. Each links to the explorer; none of them can act alone.

#010x251E4a86…9AD9f5 #020x885aA735…C83349 #030x8CD090Ab…99C50b

04Event history

Every accepted update, with its transaction

Live

#2 → Baseline

block 1336033630x3e527c…f778

#1 → Elevated

block 1336032960x1f99a0…ba76

05Developer integration

Opt in by reading, not by being called

A compatible contract reads the published threat state and applies its own policy. See Developers for the interface and an example guarded vault.

Interface

IWeaverWard

Read

getThreatState()

Fail-closed read

currentLevelOrRevert()

Event

ThreatStateUpdated

Status

Deployed · Robinhood Chain Testnet

Previous · TestPROBEVerifiable cryptographic challenges, read by their parameters.Next in the flow · RecoverMENDRecovery plans and rehearsals, proven before an emergency.

Reading WARD state from Robinhood Chain…

Ward · 05 · Protect>Live

On-Chain Threat State & Protection

01Threat state · read on-chain

What integrators see right now

Read directly from the WeaverWard contract on every request. If the read fails, no state is shown in its place.

Current threat state

Baseline

Sequence #2 · updated 2026-10-12 11:38:57 UTC

Network: Robinhood Chain Testnet (46630)
Contract: 0x594b56…54D4
Evidence hash: 0xa35734d375…efdd1927
Policy version: 0xabc5e63ea0…86ee89ed

02Registered reviewer signers

2 of 3 reviewers must sign

Independent keys registered in the contract. Each links to the explorer; none of them can act alone.

#010x251E4a86…9AD9f5 #020x885aA735…C83349 #030x8CD090Ab…99C50b

03Example integrator · ExampleGuardedVault

One contract applying its own policy

Live

Contract

0x9D2cb0…Eb62

Blocks all withdrawals at

Verified+

Large withdrawal (> 1 ETH)

Requires Baseline

If WARD is stale / paused

Fail-closed (block)

Evaluated on-chain right now via canWithdraw()

small withdrawal · allowedlarge withdrawal · allowedvault balance · 0 ETH

04Event history

Every accepted update, with its transaction

Live

#2 → Baseline

block 1336033630x3e527c…f778

#1 → Elevated

block 1336032960x1f99a0…ba76

05Developer integration

Opt in by reading, not by being called

A compatible contract reads the published threat state and applies its own policy. See Developers for the interface and an example guarded vault.

Interface

IWeaverWard

Read

getThreatState()

Fail-closed read

currentLevelOrRevert()

Event

ThreatStateUpdated

Status

Deployed · Robinhood Chain Testnet

Previous · TestPROBEVerifiable cryptographic challenges, read by their parameters.Next in the flow · RecoverMENDRecovery plans and rehearsals, proven before an emergency.