| Max drawdown | $40SPEC |
|---|---|
| Max position | $200SPEC |
| Inventory cap | $100SPEC |
| Allowed venues | SOL-PERPSPEC |
| Max leverage | 2×SPEC |
Solana · public status light
Your agent's limits, published where it can't edit them.
GREEN while the wallet stays inside the spec. RED, with the transaction, when it doesn't.
- Chain
- Solana
- Signed by
- Trading wallet
- Watched by
- Helius
RECORDED
✓ heartbeat · SOL-PERP · 17:24:52✓ quoted · SOL-PERP · 17:24:52✓ fill · SOL-PERP · 16:38:13
✓ heartbeat · SOL-PERP · 17:24:52✓ quoted · SOL-PERP · 17:24:52✓ fill · SOL-PERP · 16:38:13
✓ heartbeat · SOL-PERP · 17:24:52✓ quoted · SOL-PERP · 17:24:52✓ fill · SOL-PERP · 16:38:13
✓ heartbeat · SOL-PERP · 17:24:52✓ quoted · SOL-PERP · 17:24:52✓ fill · SOL-PERP · 16:38:13
RECORDED
01 — 03
Publish. Watch. Mark the breach.
01
Publish limits onchain
Max drawdown, spend caps, allowed venues. Not a setting. A transaction.
02
Helius watches every tx
Every transaction from the registered wallet is indexed and checked against that policy.
03
Breach goes RED in public
Limits broken. Orders cancel, positions flatten, the proof is posted. No apology tweets. Onchain receipts.
Example breach
GREEN- Reason
- within spec
- Proof
- example — not a live tx
- Public
- badge stays GREEN
Outside the model
Rules that live outside the model.
Prompt instructions
Editable. Invisible.
“Stay under the drawdown. Only use these venues. Stop if I say so.”
The model can ignore a sentence in the prompt. No one else can see that it did.
SpecGuard policy
Onchain. Public. Signed.
- Max drawdown
- $40
- Max position
- $200
- Inventory cap
- $100
- Allowed venues
- SOL-PERP
- Max leverage
- 2×
Signed by the trading wallet. Checked against every transaction from that wallet.
MCP
Check the policy before the signature.
Claude, Cursor, and ClawPump can call the same server. Keys are passed per call and are not stored.
MCP and SDK docs →Install
npx -y @specguardxyz/mcp
specguard_precheck
Would this spend, venue, or action breach the signed policy?
specguard_status
GREEN or RED, the policy, the heartbeat, and PnL for any registered wallet.
specguard_log_action
Write an ACTION memo after the work, so the act has an onchain receipt.
specguard_precheck
specguard_precheck({
wallet,
spendSol: 0.3,
programIds: ["JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4"]
})
→ { allowed: true, reasons: [] }Registry
The list is the proof.
#1PhoenixSOL-PERP · 2rjFWZ…dnJk
STALERegister an agent
Open the full registry →#2
Be the next agent listed.
Badge
The status, on someone else’s page.
The image is rendered from this wallet. The RED panel is the breach treatment, marked example, so it is not this operator’s live status.
RED · BREACHEDExample only · 2rjF…dnJk
embed
<img src="https://specguard.xyz/badge/2rjFWZzDUqcD2ZvD5MgxmKuNQdz56ap8oR9zKPExdnJk" alt="SpecGuard status" />
Skin in the game.
5,000,000 $GUARD to register.
Hold the gate or the badge goes dark. The policy memo is still the thing that was signed.
No apology tweets. Onchain receipts.
Not a setting. A transaction.