CA Not announced yet
SECUTY
Guardrails for onchain wallets

Check every move
before the chain does.

Secuty is a concept for screening transfers, allowances and bot actions on Robinhood Chain. Rules make the call. Models only advise.

CONNECTING TO CHAIN
Tokens in motionDEXSCREENER / BY LIQUIDITY
THE GUARD LANESECUTY / CONCEPT
SENDERa person or a bot
ROBINHOOD CHAINonly what passed
EXTRA PROOF REQUIRED FOR LARGE 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
—
Waiting on node
Gas price
—gwei
Waiting on node
Chain TVL
—
Waiting on DefiLlama
Chain ID
4663
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

Send it through the lane.

SCRIPTED EXAMPLE / NOTHING MOVES

Same wallet, three requests. Switch the request and watch the 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
Invented rules and amounts.
CHECKS IN ORDERIDLE

  1. Parse

    Work out what is being asked.

    —

  2. Rehearse

    Replay it and read the effects.

    —

  3. Judge

    Compare against the owner's rules.

    —

  4. Verdict

    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.
No shortcuts.

Nothing reaches the chain on a hunch. A request is declared, rehearsed, judged by fixed rules and only then released.

Declare

A person, or a bot holding a limited key, states what it wants to do.

Rehearse

The request is replayed in private to learn which assets move and which permissions change.

Judge

Fixed limits and lists answer yes, no, or "show me more proof".

Release

Only an approved request is sent. Larger moves can ask for a stronger signature.

Models flag ───── Rules decide ───── Owners hold the keys
Building blocks

One wallet.
Six moving parts.

Each part solves a separate problem and can ship alone. Together they form a single guarded path.

Build order

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 02Rehearsal and ScoutQUEUED
  • Private request replays
  • Allowance inspection
  • Lookalike contract spotting
  • Risk notes in plain words
  • Score history per wallet
STAGE 03Bot walletsQUEUED
  • Per-bot permissions
  • Daily spend caps
  • App and asset lists
  • Keys that retire themselves
STAGE 04Stronger signaturesQUEUED
  • Registered backup keys
  • Extra proof above a threshold
  • Swappable signature schemes
  • Rescue with the stronger key
STAGE 05PassportQUEUED
  • Owner-held credentials
  • Over-age proofs
  • Region proofs
  • Proofs of fit
  • One-fact disclosure
STAGE 06Builder kitQUEUED
  • Libraries for wallets
  • Bot toolkit
  • 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 rehearsal
Allowance reader
Emergency pause
Rescue key trial

Link wallet→Open vault→Set rules→Fund it→Use the chain
Stay close

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.

Back to top ↑
SECUTY / INSPECTOR