Skip to main content
This page enumerates all wallet interactions. Microset is Solana-only, so the relevant concepts are message signing, transaction signing, and SOL movement — not EVM token approvals.

​
Permissions requested

​
Signature types

Used once per connected wallet for authentication. The signed payload begins with Microsets:wallet-auth: and is verified server-side to issue a JWT. It grants no on-chain authority and moves no funds.
Used for place_bet, claim, and quick-prediction session management. Each is a standard Solana transaction the user reviews in their wallet.
Optional. The user signs once to create an on-chain delegate session (create_delegate_session), funding an escrow with a spend cap (max_lamports) and an expiry (expires_at). A local delegate key then signs quick bets (place_bet_with_delegate) drawn only from that capped escrow. The user can add funds (fund_delegate_session), withdraw unused funds (withdraw_delegate_funds), or revoke the session at any time (revoke_delegate_session). The delegate cannot spend beyond the cap and cannot touch the user’s main wallet balance.

​
Token authorization behavior

Solana does not use ERC20 approve / setApprovalForAll / Permit2. Stakes are native SOL, moved by the program’s instructions only when the user signs the corresponding transaction. No broad token-delegate authority is granted.

​
Program mechanics (Solana equivalents)

​
Summary

Microset requests a wallet connection, one human-readable sign-in message, and explicit transaction signatures for each prediction or claim. Stakes are native SOL that move only through documented instructions, the optional quick-prediction delegate is bounded by a user-set cap and is revocable, and no SPL token delegate is granted.