Waiting on node
Build on Robinhood Chain
Secure the
autonomous future.
Secuty is a protection protocol for wallets. Owners write the rules, credentials stay sealed, risk gets screened, and every approved move is signed to outlast tomorrow's computers. People and AI agents share one guarded path.
Tokens in motionDEXSCREENER / BY LIQUIDITY
OWNER OR AGENTstates what it wants
ROBINHOOD CHAINonly what was cleared
QUANTUM-RESISTANT SIGNATURE FOR BIG-TICKET MOVES
└─ Target design · parts arrive in stagesPick a node to open it
Chain pulse
The network, right now.
Read straight from public sources while you scroll: the chain's own node, a TVL tracker and a DEX index. Nothing here is a Secuty product metric.
Block height
Gas price
gwei
Waiting on node
Chain TVL
Waiting on DefiLlama
Chain ID
Fixed by the network
Top pairs by liquidityCHAIN-WIDE
Showing the whole chain. Once a contract address is announced, this list narrows to that token.
Dry run
SCRIPTED EXAMPLE / NOTHING MOVES
Walk a request through.
One wallet, three requests. Switch the request and watch the owner's rules change the ending.
The request
250USDC
A routine payment to an address the owner saved before.
- Destination
- Saved contact
- Rule hit
- Under daily ceiling
- Proof needed
- Owner signature
CHECKS IN ORDERIDLE
- —
Intent
Work out what is being asked.
- —
Screen
Replay it and read the risk.
- —
Authorize
Compare against the owner's rules.
- —
Outcome
Decide whether it may go out.
Nothing run yet
Pick a request, then start the dry run.
Models flag. Rules decide.
Request path
Four stops.
Four stops.
No shortcuts.
Machines act faster than people can watch. So nothing reaches the chain on a hunch: a request is declared, screened, authorized by fixed rules and only then signed.
Declare
A person, or an AI agent holding a narrow key, says what it wants to do.
Screen
The request is replayed in private to learn which assets move and which permissions change.
Authorize
Fixed limits and lists answer yes, no, or "show me stronger proof".
Sign
Cleared requests are signed and sent. Big-ticket ones demand a quantum-resistant signature.
Models flag ───── Rules decide ───── Owners hold the keys
Building blocks
One wallet.
One wallet.
Six moving parts.
Each part solves a separate problem and can ship alone. Together they turn a raw request into controlled, approved execution.
Build order
Foundations first.
Foundations first.
Extras after.
Stage 01 is being designed now. The rest show the intended order of work, with no promised dates.
STAGE 01Guarded walletACTIVE DESIGN
- Owner-set ceilings
- Saved destinations
- Rescue and recovery
- Expiring keys
- Emergency pause
STAGE 02ScreeningQUEUED
- Private request replays
- Allowance inspection
- Lookalike contract spotting
- Risk notes in plain words
- Score history per wallet
STAGE 03Agent railsQUEUED
- Per-agent limits
- Daily spend caps
- App and asset lists
- Keys that retire themselves
STAGE 04Quantum-resistant signingQUEUED
- Registered backup keys
- Extra proof above a threshold
- Swappable signature schemes
- Rescue with the stronger key
STAGE 05Credentials and sealed proofsQUEUED
- Owner-held credentials
- Reputation that travels
- Proofs of fit
- One-fact disclosure
- ZK verification
STAGE 06Builder kitQUEUED
- Libraries for wallets
- Toolkit for AI agents
- Credential toolkit
- Owner console
STAGE 07Shared watchlistQUEUED
- Community-fed bad-contract list
- Automated sweeps for known flaws
- Live alerts to wallets
Order reflects intent only. No ship dates are set.
First cut
Start small, prove it.
The first build pairs the guarded wallet with rough versions of the checks. These are goals, not features you can use today.
WALLET CORE
Guarded wallet
Expiring keys
Send ceilings
Saved destinations
EARLY CHECKS
Request replay
Allowance reader
Emergency pause
Rescue key trial
Link wallet→Open vault→Set rules→Fund it→Use the chain
Stay close
Back to top ↑
News will land here first.
Official channels get linked in the top bar the moment they exist. Until then, treat anything claiming to speak for Secuty as unverified.