$STACKThe next rip.

Buy $STACK shares in Rip mode on RIPSTACK, BNB Chain (chain ID 56). Use only this selected route. Do not switch modes, enter Genesis rounds or trade on PancakeSwap without a separate instruction from me. Read https://ripstack.fun/docs/stack-token and https://ripstack.fun/docs/participation-and-refunds.

MY SELECTION
Buy exactly 1 paid share in Rip mode. Use shares=1 in the quote request. Do not ask me to enter the quantity again. Recheck my registered Agent ID, purchasedShares, remaining shared Rip/Stack allowance, available shares and the pool-opening boundary. If this quantity no longer fits, stop and explain the current limit; do not silently resize or split the purchase. Show the current USDT quote and obtain my payment approval before execution. This copied selection is not transaction approval.

EXISTING WALLET SESSION
Use my Binance Agentic Wallet session already connected to this agent. Run baw wallet status --json once under the official skill preflight; reuse its result if already checked in this workflow. If CONNECTED, continue with that wallet: do not run auth signin, sign out, request another QR/pairing code, or ask me to connect on the RIPSTACK website. Only follow the official Binance sign-in flow when status explicitly reports no active session. A network error or unavailable status is not evidence of disconnection: stop and report it instead of starting another login. Confirm the BSC address and registered Agent ID without changing accounts. Keep Binance credentials on my device. Website connection is not required for this agent workflow. This session does not replace transaction previews or required Binance confirmations.

REUSE RIPSTACK AUTHENTICATION
After checking the public campaign identity, reuse an existing RIPSTACK bearer token scoped to this same BSC wallet, campaign and https://ripstack.fun. Test it once with GET https://ripstack.fun/api/protocol/stack/access and Authorization: Bearer <token>. A successful response confirms the session: skip https://ripstack.fun/api/protocol/auth/challenge, https://ripstack.fun/api/protocol/auth/verify and the login signature, then continue using that response. This read also satisfies the route's initial wallet/access check. If no matching token exists, it is expired, or the API returns 401, follow the authentication step below once. All challenge creation, typed-data signing and verification instructions apply only inside this missing/expired-token branch. This is a RIPSTACK ownership signature using the already connected wallet, not a second Binance login. A 403, 429, 5xx or network failure must not start Binance pairing or repeated signing. Never reuse a token across wallet or campaign changes, expose it in chat, extract website cookies, or send Binance credentials to the API.

IDENTITY AND CONFIGURATION
Use the official binance-agentic-wallet skill and its current preflight and external-sign references. Confirm my registered .ai Agent ID and BSC wallet. Keep my Binance credentials on my device. Check baw wallet settings --json for active Developer Mode before signing, requesting quotes or preparing calls. If disabled, ask me to enable it in the Binance App and stop until I confirm. Verify the published contract addresses, chain, bytecode and official ABI. If deployment or an authenticated quote is unavailable, stop and state the missing requirement. Do not invent signatures, addresses, API authentication or receipts. Website login is not required; never extract its cookies or upload local Binance credentials.

DEPLOYMENT CHECK
Read https://ripstack.fun/api/stack/status once. Require state=ready and a matching BNB Chain deployment. Use snapshot.sale and snapshot.token as published references, then verify the relevant live contract before a transaction. A missing deployment is a stop condition; do not poll for launch or probe other hosts. Before API sign-in, read https://ripstack.fun/api/protocol/status once to verify the campaign identity used by the authentication domain. These reads do not authorize a transaction.

AUTHENTICATE
Use API base https://ripstack.fun/api/protocol. Only if RIPSTACK authentication is missing or expired, POST https://ripstack.fun/api/protocol/auth/challenge with {address: my BSC Agentic address, mode: "eip712"}. Review the returned typed data, including origin, chain, campaign contract and expiry. Sign it through the official baw sign-message preview and execute flow with my explicit confirmation. POST https://ripstack.fun/api/protocol/auth/verify using challenge.verification.body plus the completed signature and signatureRecovery fields, following SIGNATURE RESULT below. Keep its short-lived bearer token private and send it only in the Authorization header to this API. GET https://ripstack.fun/api/protocol/stack/access confirms the registered identity and purchase limit. This sign-in does not activate Origin round entries or approve token spending.

SIGNATURE RESULT
Use --json with documented Binance commands. If sign-message execute returns PENDING_CONFIRMATION, keep its orderId and use sign-message result --order-id under the official skill flow. Check after 6, 12, 24, then 30 seconds, stopping when the signature arrives, the request expires or five minutes pass. Never create parallel challenges or repeat sign-message execute while confirmation is pending. For POST https://ripstack.fun/api/protocol/auth/verify use Content-Type: application/json and exactly {address:challenge.verification.body.address,nonce:challenge.nonce,signature:result.data.signature,signatureRecovery:result.data.signatureRecovery}. Omit signatureRecovery only when absent and the signature already has 65 bytes. Use the original top-level challenge.nonce (48 lowercase hex characters without 0x), never typedData.message.nonce (a bytes32 hash). The API accepts the completed Binance 64-byte signature with its separate recovery field, or a complete 65-byte signature. Do not guess a recovery byte, append it twice, send an order ID, or wrap the body in data. Keep typedData unchanged when signing. A 400 response identifies the invalid field; stop and report that field rather than trying different signature formats. Reuse a valid bearer token for this wallet and campaign instead of signing in again for each action.

ENDPOINT MAP
Use these complete URLs exactly. Status only: GET https://ripstack.fun/api/stack/status. Wallet access: GET https://ripstack.fun/api/protocol/stack/access. Purchase quote: POST https://ripstack.fun/api/protocol/stack/quote. Origin redemption quote: POST https://ripstack.fun/api/protocol/stack/origin/quote. The status endpoint is separate from the authenticated protocol API. Do not derive other URLs from the status URL, remove /protocol, or use browser Task endpoints. Send the bearer token in Authorization: Bearer <token> only to the protocol API. Reuse a valid token for the same wallet, campaign and origin; do not sign in again unnecessarily.

ACCESS CHECK
Check that https://ripstack.fun/api/protocol/stack/access.address matches my wallet. Its allowance is the total purchase limit, not the remaining amount: subtract purchasedShares(myAddress) read from the verified sale. Both Rip and Stack consume that same counter. Refunds do not restore it.

QUOTE LIFECYCLE
Select the requested quantity and confirm that I am ready to review before requesting a quote. Load the official ABI and finish static checks before requesting the time-limited quote. Request one quote, review it, perform any required approval, wait for its receipt, then recheck allowance, deadline and on-chain phase before buy preview. Skip approval when the existing allowance already covers maxPayment. Never ask for another approval just because a quote expired. If the approval or my review outlasted the quote, request one replacement and repeat the preview and my confirmation. Do not refresh a quote continuously or reroll a discount. If the replacement expires, stop until I ask to resume. A rejected quantity, unavailable inventory or closed phase is a stop condition, not a retry loop. No background vesting or claim polling is authorized.

PURCHASE QUOTE ENDPOINT
POST https://ripstack.fun/api/protocol/stack/quote with {shares: the requested integer, mode: 0} and the bearer header. The response contains quote, signature, maxPayment, chainId, sale, expiresAt, transaction and abiUrl. Fetch the official sale ABI from https://ripstack.fun/contracts/StackPublicSale.abi.json; no explorer API key is required. Never infer a selector or tuple layout from bytecode. Decode transaction.data with this ABI and require buy(quote,signature,maxPayment) with every field matching the response. Require transaction.from=my wallet, transaction.to=sale, transaction.chainId=56 and transaction.value="0". Integer quote fields are raw decimal strings: use BigInt, never floating-point conversion. Verify quote.buyer, nonce, shares, principal, allowance, sold, discountBps, deadline, poolOpen and mode. Decode amounts with the actual token decimals. Before approval, compare the current sale nonce and phase. Use the returned transaction.data unchanged in baw contract-call preview --binanceChainId 56 --from <myAddress> --to <transaction.to> --value 0 --inputData <transaction.data> --json. Do not rebuild calldata or pass the JSON quote as calldata. The buyer must match my authenticated BSC address. Never use a quote for another mode, wallet or contract.

PURCHASE REQUEST
Use the exact share count in MY SELECTION and confirm my maximum USDT payment against the fresh quote. Use Rip mode (mode = 0) in the authentic purchase quote. Read my allowance and consumed shares: ten paid shares initially, plus one right for each distinct STACK referral completing social tasks and one more for that referral's first confirmed purchase. Referral count is unlimited; remaining shares and token inventory still limit purchases. Never fabricate social completions or referral credits.

PRICE AND OUTPUT
Before pool opening, each paid share has 55,000 base $STACK. Rip delivers 55,000 STACK for each share bought before opening in the USDT payment transaction, with no bonus or later base claim. The USDT ladder is 1 USDT for gross paid positions 1–10,000, increasing by 0.16 USDT for each subsequent 10,000-position band. Charge each band correctly when a purchase crosses bands.

AFTER POOL OPENING
Do not reuse the fixed pre-opening token amount. The full ladder determines the USDT bill; the current checked pool price with the assigned 0.5%, 1.5% or 2.5% token-price discount determines base output. The discount increases tokens rather than reducing the bill. quote.principal is the signed minimum base output; actual execution can deliver more. Review maxPayment, base, bonus, total, minimum output and quote.deadline before approval. A quote cannot straddle the 10,000-active-paid-share opening boundary. Do not count Origin shares, bonus tokens or cancelled purchases toward that trigger.

RIP DELIVERY
The successful buy transaction must deliver the quoted base STACK directly to my wallet, before or after pool opening. Do not accept a deferred allocation or a claim-after-opening flow for this mode. Check the receipt's STACK transfer and my balance change. The shared inventory must cover this output and matching liquidity before payment.

PAYMENT
Verify the actual USDT contract and decimals. Approve only the reviewed payment allowance to the sale contract if needed, then call buy with the authentic signed quote and my maximum payment. Never send USDT directly to a treasury or pool address. Pool opening and later liquidity settlement are part of the purchase transaction; the contract allocates 80% to LP and 20% to treasury and mints protocol LP to the dead address.

TRANSFER LOCK AND REFUND
Received STACK cannot be transferred or sold before pool opening. Each paid purchase is 100% refundable strictly before its own purchase timestamp + 30 days, only while the pool is unopened. Refund cancels the entire position and burns all of its base and bonus, including already claimed wallet tokens, in the same transaction as the full USDT return. Gas is not refunded. If it expires before opening, token and refund rights expire and its settled payment becomes owner-withdrawable to treasury. Read the position's actual UTC deadline and pool state. A refund requires my separate explicit request and transaction confirmation.

TRANSACTION REVIEW
Before building an external call, check baw wallet settings --json for active Developer Mode. Use the official contract-call preview command with chain 56 and value 0. Show the full contract addresses, exact assets, gas, decoded operation, simulation and authority changes. Obtain my explicit confirmation before each approval and execution. Execute only the requestId from a successful preview. Never execute a failed or expired preview.

CONFIRMATION
Track the original transaction hash until confirmed or definitively failed. A timeout is not a failed payment: reconcile it before retrying. Record the Purchased event and position ID for a paid purchase, or the redemption event and edition ID for an Origin. Confirm actual token delivery and allocations from the canonical receipt, not the quoted estimate alone. Report transaction hashes and release timestamps in UTC. Never promise a market value or return.

REQUEST DISCIPLINE
Run one workflow for this wallet, with at most one non-stream request in flight. Use a 15-second timeout for ordinary API reads; a live event stream and the official blocking Binance pairing flow are separate. Reuse valid authentication and configuration. Do not refresh quotes, balances, registry data or approvals in a loop. Respect Retry-After; on 429 without that header, wait at least 60 seconds. The specific round and receipt retry schedules override this general read schedule. For other transient read failures, wait 2, 4 and 8 seconds with small random jitter, then pause and report the problem after three retries. Never fan requests out across providers. On 400, 403, 404 or 410, stop and explain the response. On 409, reconcile state once and follow the specific state instead of repeating the rejected action. On 401, allow one reauthentication within an explicitly authorized session scope; otherwise get my confirmation first. If it fails again, stop. Never automatically repeat a signature or blockchain submission. An unexpected HTML response or missing deployment means unavailable, not permission to try alternative endpoints.

TRANSACTION TRACKING
Keep a private local record of the wallet, chain, contract, action, selected quantity or edition, and the original transaction hash or wallet order ID. Resume that record after interruption. Execute each approved preview only once. If execution returns an order ID or pending confirmation, use the official skill's documented status flow; do not execute again to obtain a hash. Check a pending transaction after 6, 12, 24, then 30 seconds, with only one check in flight. After five minutes without a final result, pause and report it as pending with its identifier. A timeout or missing receipt is not a failed transaction. Never replace or resubmit it without reconciling the original request and obtaining my confirmation. Verify the canonical receipt and contract events before reporting success. Stop after the requested operation is complete; do not start purchases, refunds, renewals or vested claims that I did not request.