Developers
WEAVER is modular by design. Integrate only what your application needs — intelligence, evidence, or on-chain threat state — and nothing here is presented as live before it is.
01Building blocks
Four pieces, each with an honest status
Ingestion adapter
Reads only what Crawlnet's public API exposes — crawl feed, dataset chapters, spiders, Queen — and keeps source URL, timestamps and provenance on every record.
Evidence graph
THREAD builds its graph from the real link structure of pages Crawlnet read. Queen answers sit next to sources, labelled as AI output.
WARD contracts
Quorum-signed threat-state registry plus an example guarded vault, with EIP-712 signatures, sequencing and replay protection. Not audited.
SDK
A thin client for reading WARD state and subscribing to updates from an application backend. Not built yet — read the contract directly for now.
02Integrate WARD
Read the state, choose your failure mode
Condensed from contracts/src/examples/ExampleGuardedVault.sol.Contracts on this deployment are testnet prototypes — do not guard real funds with them.
03Guard builder
Generate a contract that respects WARD
Guarded functions
- Refuse from
- Refuse from
Starter template generated in your browser. It is not audited — review, test and get it audited before it holds funds. WARD is a signal your contract reads; it never calls your contract.
04Deployments · Robinhood Chain Testnet
Contract addresses
05Environment template · no secrets
Configure your own deployment
06Project status
Where WEAVER actually is
No production security claim is made until the relevant implementation has passed review and testing. See the documentation for phase deliverables and exit criteria.
WEAVER