Skip to content
Argus

Argus

web3 open security intelligence protocol

Created on 10th May 2026

•

Argus

Argus

web3 open security intelligence protocol

The problem Argus solves

Wallet users grant token approvals that later become dangerous when a contract is flagged. They need independent, verifiable risk signals—not a single vendor opinion—and automatic protection when consensus crosses a threshold.

Argus ingests signals from Sourcify-oriented watchers, social/Apify scouts, and on-chain monitors into a consensus engine with TEE-attested outputs. A role-aware dashboard shows live scores, agent registry on Sepolia, and ENS CCIP-Read resolution of risk text records. A Guardian service revokes approvals to a monitored spender using Space Orbitport KMS digest signing where configured.

Challenges we ran into

We unified standalone and TEE-bridge deployments behind one signal-api surface, shipped a wildcard ENS resolver plus HTTP gateway with /preview/:addr, and kept Sepolia demos reversible (MockUSDC + FakeSwapNet + guardian loop). Wiring contributor enrollment, social polling agents, and telemetry for KMS-signed revokes made the judge story visible without sacrificing a clear separation between consensus, custody, and UX.

Tracks Applied (3)

SpaceComputer Bounty

Orbitport KMS: Guardian revocation txs are signed via sdk.kms.sign (DIGEST / ETHEREUM_SECP256K1) with telemetry lines in...Read More

SpaceComputer

Sourcify Bounty

Dedicated watcher-sourcify agent; SWAT detector runs on verified sources. SWAT-004 path simulates txs against Sourcify v...Read More

Sourcify

Most Creative Use of ENS

Wildcard ArgusRiskResolver + ENS text records for per-address risk. HTTP gateway with /preview/:addr; dashboard ENS risk...Read More

ENS

Discussion

Builders also viewed

See more projects on Devfolio