Skip to main content
When an agent attempts an operation that exceeds its policy limits or requires explicit human approval, the x0-guard program generates a Blink — a Solana Action that the owner can approve from any Blink-compatible wallet or application.
Generated when an agent transfer exceeds policy limits.
Fields:

Rate Limiting

Blinks are rate-limited to prevent spam and denial-of-service: If the agent exceeds the Blink rate limit, the transfer is rejected with BlinkRateLimitExceeded (0x1130).
1

Generation

The agent SDK creates a Blink object containing action details, encodes it as a Solana Actions URL, and optionally generates a QR code.
2

Delivery

The Blink URL is surfaced to the owner via the agent’s interface — push notification, chat message, email, or QR display.
3

Review

The owner opens the Blink in any Solana Actions-compatible wallet (Phantom, Solflare, Dialect, etc.) and reviews the requested action.
4

Approval

The owner signs the transaction in-wallet. The signed transaction is submitted directly to Solana — no intermediary.
5

Expiration

If the owner does not act within 15 minutes, the Blink expires. The agent may generate a new one (subject to rate limits).

Solana Actions Metadata

The SDK produces an Actions-compliant JSON metadata response for rendering in Blink clients:

QR Code Generation

For mobile-first approval flows:

Validation

Events

Last modified on February 8, 2026