gitShield
Lock tokens. Receive soul-bound safeTokens.
gitShield is the deposit operation. Send supported tokens into your vault and receive soul-bound safeTokens — cryptographically immune to draining by any agent or compromised key.
How it works
Deposit → Mint → Hold
1

Comment the deposit command

@gitsafebot deposit 100 USDC in any GitHub issue on a connected repo.

2

AI parses your intent

Claude Haiku extracts amount, token, and your GitHub identity. Confidence threshold ≥ 0.92 required.

3

Relayer submits the transaction

The GitSafe relayer builds and signs the Solana transaction using your encrypted execution keypair. Gas is covered.

4

safeTokens minted to your vault

You receive 1:1 safeTokens. These have no transfer function — impossible to move by anyone outside GitSafe program instructions.

gitUnshield
Withdraw — burn safeTokens, release the underlying asset
# gitShield (deposit) @gitsafebot deposit 100 USDC gitShield complete. 100.00 safeUSDC minted. Fee: 0.20 USDC (0.2%) · Tx: 4a1z…9efK # gitUnshield (withdraw) @gitsafebot withdraw 50 USDC to 7xKX…mPqR gitUnshield complete. 50.00 USDC sent to 7xKX…mPqR. Fee: 0.10 USDC (0.2%) · Tx: 9efK…4a1z

No transfer instruction

safeTokens cannot be sent to any address. No transfer function = no drain surface. A compromised key is worthless.

No approve instruction

You cannot approve a third party to spend your safeTokens. Standard DeFi exploits don't apply.

On-chain enforcement

Restrictions enforced at the Solana program level — not application level, which can be bypassed.

Agent-safe by design

Give an AI agent full bot access to GitHub without risk. Even a fully compromised agent cannot move funds.

© 2026 GitSafe · All rights reserved. ← Home