bounded-onchain
Add onchain to a Bounded app: Solana collections, embedded non-custodial wallets for email/social users (@user.address, Turnkey by default), client- and server-signed transactions, DEX/perps trading patterns, and crypto payments (accept USDC/crypto non-custodially). Use for wallet, token, on-chain transaction, or crypto payment work. Part of the Bounded skill family; policy and the actor model live in bounded-backend.
How do I install this agent skill?
npx skills add https://github.com/bounded-sh/skill --skill bounded-onchainIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a comprehensive suite of instructions, technical documentation, and code examples for building on-chain applications on the Solana blockchain using the Bounded platform. It covers embedded wallet management, transaction signing, and integrations with major DeFi and NFT protocols. No malicious patterns, such as data exfiltration, obfuscation, or unauthorized code execution, were detected during the analysis.
- Socketwarn
2 alerts: gptSecurity, gptAnomaly
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Bounded onchain
Wallets, tokens, on-chain transactions, and payments. The canonical Bounded
email/social login includes a wallet by default: keep the default Turnkey auth
and supported email/social logins carry a real @user.address - see
docs/embedded-wallets.md. @user.id (the account id)
stays the identity/ownership key; @user.address is the wallet. On-chain writes
still pass their policy rules and invariants first, so pair this with the
bounded-backend skill for the governing rules. To route across the family, see
the root bounded skill.
Reference Router
Read only the row matching the current task or term.
| Task or term | Read |
|---|---|
| Find a plugin namespace or function quickly | plugin catalog - compact namespace/function router |
| Scan every bare signature and callable context | complete signatures index |
| One plugin function's exact signature, manifest argument descriptions and signer markers, return type, and callable context | plugin catalog, then its per-namespace page under docs/plugins/ |
| Token-2022 transfer tax, withheld wallet/vault fees, mint harvesting, dedicated withdrawal authority, treasury as fee recipient, pending claims | transfer-fee collection |
Who holds funds, who signs, escrow vs named PDA vs user wallet, @AccountPlugin.createAccount, account-id hygiene, create-fund-use idiom | custody and PDAs |
| A complete policy for an escrow, vault, treasury, staking, market, launch, NFT, Token-2022, randomness, or liquidity app | examples index |
| A failing onchain write: error lookup, rent, ATA payer, transaction limits, confirmation, environment differences | onchain troubleshooting |
Fund any wallet with simulated SOL, USDC, or another token on Poofnet, bounded wallet fund, realtime_offchain | Poofnet onchain simulation |
SOLANA_DEVNET_RPC_URL is required, SOLANA_MAINNET_RPC_URL, validate pre-built transaction, submission fails before signing, no --rpc-url flag, public-RPC fallback | CLI submission needs an explicit RPC endpoint |
Browser onchain set() cannot submit, chain in init(), default Helius RPC, optional top-level rpcUrl override | Browser/SDK RPC defaults and overrides |
onchain account resolution failed (422), onchain account not found: <pubkey>, a write naming an account that does not exist on chain, wrong mint/pool derivation, 1-arg vs 3-arg getTokenMintAddress mismatch | Missing onchain accounts vs platform 502s |
onchain account resolution failed (502), onchain query failed (502), Transaction building failed without a 403 and without a 422, named queries and plain getBalance failing together, platform resolver outage | Platform resolver and onchain-query 502s |
Pump.fun launch fails after signing with insufficient lamports (need 1461600, Create Metadata Accounts v3), app-custody creator funding | error table and the token-launch example |
Onchain collections, onchain:true, --protocol, Solana, mainnet permit, patches, readonly !, FieldReadOnly | onchain |
| Compiler vs deployed support, devnet status, blocked or unverified integrations (Jupiter, Phoenix, DFlow, Kamino, Pump.fun, PumpSwap, Tensor, SPL stake pool, liquid staking, Raydium CPMM, Meteora DLMM), runtime-v4 gating | capability status |
| Helius, mirror/indexer, missed transactions, eventual consistency, unmirrored writes; who owns webhooks, ingest queue/DLQ, recovery and reconciliation | mirror completeness |
| Bonding curve, AMM, shared price or counter, writes fail under load, race, slippage, max paid / min received | shared prices and counters |
| Transaction too large, 413, 1182/1232-byte packet limit, oversized hook, lookup tables | transaction-size limit |
governance.upgrade, immutable/controller policy, manifest root, governed session, recovery, extend, cancel | runtime-v3 governance |
@CPI, @Solana, @Bytes, @App, @DocumentPlugin.updateField, @PredictionMarketPlugin, PDAs, get/getAfter, ProgramData, shouldSubmitTx, skipPreflight, @contract.address, @AccountPlugin.getAccountAddress, generic CPI, cross-app, prediction-market arithmetic, runtime parity, @Solana.verifyEd25519, @Solana.secp256k1Recover, @Bytes.sha256, @Bytes.keccak256, signature verification, EVM signer recovery | policy primitives |
Auction, order book, multi-transaction financial state machine, aggregate buckets, permissionless crank, lazy claim/settlement, fixed-point units, independent arithmetic oracle, operation receipt retry, _hook_completed, _error_message | policy-native financial state machines |
| Anchor/custom errors or stale numeric decoding | custom-error diagnosis |
| Trading, Phoenix perps, DEX swaps, server-signed execution | onchain trading |
Escrow custody, source argument, per-entity funds, named PDA accounts, @AccountPlugin.createAccount | named escrow accounts |
| Rule arithmetic overflow, int64, division-first pins, large-magnitude comparisons | rule arithmetic |
Pyth USD prices, decimal price strings, getPriceFeedScaled, micro-USD, integer price arithmetic | price-feed units and runtime availability |
Randomness, VRF, raffle/gacha/shuffle, @OraclePlugin, requestRandomness, getRandomNumber, isRevealPath | randomness |
Meteora token launch, DBC, anti-snipe fee decay, DAMM v2, createMeteoraConfig, createMeteoraVirtualPool, claimDammV2PoolFees, withdrawLeftover | Meteora launch |
Pump.fun, PumpSwap, @PumpFunPlugin, createToken/createTokenV2, buyExactSolIn, creator fees, fee sharing, updateShareholders, distributeCreatorFees, pumpswapDeposit/pumpswapWithdraw, argument names/units | Pump.fun reference |
Multi-party fee split, feepool, mulDivFloor, keeper/scheduled onchain writes, actAs, rollingSum fee-funded build allowance | oApps tokenomics |
Embedded wallet for email/social users, @user.address, Turnkey, auth.wallets | embedded wallets |
403 anonymous_onchain_blocked, guest/signInAnonymously session writing an onchain collection, works on poofnet but not mainnet | guests cannot write to an onchain collection |
Bring-your-own Solana wallet login, walletLogin, Phantom / Wallet-Standard, SIWS | wallet login |
onramp(), buy SOL/USDC by card, Coinbase Onramp, wallet top-up | onramp |
Accept crypto/USDC, payments.acceptCrypto, seller settlement, direct-transfer rail | accept crypto |
Rules Of Thumb
- Default onchain login = default Turnkey email/social auth, plus optional wallet login. Do not add
authModeorauth.walletsfor the normal path; supported email/social users already have@user.address. Deploy"auth": { "wallets": true }only for an EXTERNAL-keypair session (wallet login, a server-SDK keypair client, the CLI keypair data lane). Full rule and the opt-outs: docs/embedded-wallets.md -> recommended login. - Use
@user.addressonly for wallet/onchain semantics; use@user.idfor normal ownership. See the bounded-backend skill. - A guest (
signInAnonymously) session can never write anonchain: truecollection, on ANY network. Poofnet, devnet, and mainnet all return403 anonymous_onchain_blockedbefore a transaction is built, so a guest flow that works against a test network cannot break on promotion. Keep the guest-reachable surface offchain and prompt the upgrade before the first onchain write. See guests cannot write to an onchain collection. - When a function's existing manifest description accepts account IDs, a non-pubkey string resolves to its own program-signed PDA.
@contract.addressis ONE shared fund for the whole app; a named id is a separate fund per name. Do not assume every source, owner, creator, or destination accepts all three custody forms - check that argument's manifest description on the function page. When separate pots of user money coexist (escrows, auctions, prize pools, per-tenant balances), use named accounts where accepted. Decide before the first deposit; retrofitting means migrating live balances. - For onchain writes, use explicit network/RPC configuration and devnet by default; do not treat immediate read-after-write as confirmation.
The CLI submits the transaction itself, and it reads its endpoint ONLY from
SOLANA_DEVNET_RPC_URL/SOLANA_MAINNET_RPC_URL: no flag, no config-file setting, and no public-RPC fallback. An unset variable fails the write before signing withvalidate pre-built transaction: SOLANA_DEVNET_RPC_URL is required ..., so set it in the shell runningboundedwhenever an app isrealtime_devnetorrealtime_mainnet. See CLI submission needs an explicit RPC endpoint. - Mainnet is a real target, not a placeholder: the program is live on mainnet-beta. Creating a mainnet app requires a paid account plan (no API key or shared secret), and an app you create is owned on-chain by the creator's wallet - a wallet your signed-in identity can prove it controls: the local CLI keypair, or on a web login your Bounded account's own wallet, whose permit signatures happen through a per-deploy browser approval. That owner can never move to another person's wallet. The one hand-over is to an OpenApps agent: an OpenApps app runs on mainnet owned on-chain by an OpenApps custody key, so the platform can publish its policy updates with no person holding that key, and a mainnet app you give to an agent moves to that key once, in a transaction your own wallet signs (see the openapps skill). See docs/onchain.md.
@contract.addressis the Solana program-ID sentinel, not the app escrow address returned by a direct query. Supported built-in plugins resolve the sentinel to the app escrow PDA. On the current deployed Devnet runtime, do not compose the sentinel as@AccountPlugin.getAccountAddress(@contract.address): that call fails because the sentinel is address-typed while this function currently accepts a string account id. For a Devnet policy query that needs the concrete escrow address, bind the current Devnet program ID as a string literal:@AccountPlugin.getAccountAddress("openTv7fbpYSseNHYmCZFZ1CZgj4r8D9fKNgEz1qo6F"). This literal is Devnet-specific and must be updated if the deployed program changes. See policy-primitives.md.- Treat discovery, deployed-runtime support, and live-network verification as three independent states.
- Use
bounded plugins list --jsonandbounded plugins describe <plugin.function> --jsonas the offline callable signature source before authoring a hook. - Check the Solana devnet capability catalog before proposing any plugin or primitive.
- Never infer devnet support from a compiler tag, manifest, proof contract, Poofnet model, lookup-table entry, or local validator test.
- When live evidence uses a hosted release marker, resolve its environment-qualified site URL from
bounded domains list --app-id <id> --env <environment> --jsonslugUrlor the exact successful site-deploy receipturl. Require the JSON field itself for staging evidence instead of copying a human-rendered hostname.bounded apps inspectproves the active policy/runtime publication and carries no hosted URL. - Never emit runtime-v2 primitives for a runtime-v1 deployment; follow docs/policy-primitives.md.
- Put a named query on the collection its plugins allow:
onchain: truefor chain reads over onchain data,onchain: falsefor anything calling an offchain-only plugin (such as@DeFiPlugin.getSwapQuote) or reading offchain documents. Both run on Solana apps. Anonymous execution is admitted for identity-independent queries whose path read rule authorizes the caller; a query reading@user.address/@user.evmAddressrequires that identity. The anonymous surface is the browser SDK, not the CLI. On Solana mainnet a signed-out chain query currently fails, so require a signed-in wallet there until the platform's query payer fix ships. - Treat runtime-v3 governance the same way: enroll only after the deployed capability registry reports v3, and publish governance from observed chain state rather than policy intent.
- Keep Poofnet and Solana behavior paired.
- Use
bounded wallet fundonly for explicit development funding onrealtime_offchain. The caller must be the app owner, an admin, or a developer, and the balance exists only inside the selected app's simulated ledger. - Pure/read primitives must return the same shape in runtimes where they are actually executable, and mutating primitives must apply a modeled effect or fail closed.
- Validation-only success is a parity bug.
- For a Poofnet onchain hook, application-side success means
_hook_completed == _transaction_hash. Row existence and_error_message == nullare only pending state. But those stamps are SIMULATOR-only: a policy RULE that requires them is permanently unsatisfiable on a real-chain protocol - a payout gated that way becomes a one-way valve that locks user funds, and every sim-side proof and test stays green. Rules gate on a declared field the hook itself writes (paidAt-style) or on the hook-derived head state; reserved_stamps are for Poofnet clients only. Give every semantic operation id a policy-legal failed-attempt retry path. See reserved receipt stamps are Poofnet-only. - Helius mirroring is environment-level Bounded infrastructure: one raw program webhook per environment/network, never one per app. App builders never create webhook URLs or supply provider secrets, and the operator runbook (webhook, secrets, queue/DLQ, recovery) lives in the monorepo, not this skill. See mirror completeness for the app-facing caveats.
- Crypto is accepted non-custodially; sellers settle to their own wallet.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/bounded-sh/skill/bounded-onchain">View bounded-onchain on skillZs</a>