How to deploy the unified program
This guide is for the holder of the Slip program upgrade authority. It does not grant or infer that authority.Required inputs
- upgrade-authority keypair for program
8VNZ5VseAcFaYhAZxetgE5N8eiD17ZZNchGhoatYUUXw; - funded devnet fee payer;
- RPC that permits program deployment;
- activated TxLINE API token;
- funded six-decimal devnet USDT accounts for lifecycle verification;
- the exact reviewed commit and its generated IDL.
Build and verify the artifact
anchor --version reports 0.32.1. Record the commit SHA and hash of
target/deploy/slip.so. Confirm the IDL contains two accounts and five instructions before
deployment.
Perform the authorized upgrade
Use the organization’s approved Solana deployment procedure and explicit upgrade-authority key. The repository does not embed or recover that key. Confirm the resulting transaction and executable program account on devnet. Do not enable the web write flag immediately after the deployment transaction.Verify the deployed binary
Execute a real devnet lifecycle against the upgraded program:- create a market from a live TxLINE fixture and visible expression;
- stake different USDT amounts from at least two wallets on different outcomes;
- confirm pool counters equal the market vault;
- wait for or select a terminal fixture with an available proof;
- run the keeper or submit
resolve_marketpermissionlessly; - claim a winning ticket and verify proportional payout, fee, and resolver tip;
- create and void a one-sided market, then verify its refund;
- store transaction signatures and the deployed binary hash in the handoff.
Enable the hosted product
Point both RPC variables at the verified deployment, setNEXT_PUBLIC_SLIP_MARKET_ENABLED=true, and
run:
/api/healthz, create, stake,
resolve, claim, and /me from the public URL.