# Configure the mainnet platform

Use the owner account and a Ledger signature to create Scrip’s platform, fee destinations and enforced quote-only migration rules.

State: Mainnet setup · Updated September 21, 2026

## Keep the admin key on your hardware wallet

The setup is pinned to the founder-approved Ledger public address. The private key and recovery phrase never belong in Scrip, chat, Vercel, a server environment variable, or a screenshot. Connect the hardware wallet through its supported wallet interface; do not import its recovery phrase into a software wallet.

The authorized owner account controls access to the setup page. Connecting an ordinary wallet does not give it Scrip platform authority. The Ledger must separately sign the exact reviewed mainnet transaction. A normal Scrip login uses a message signature and does not perform this setup.

[Open network control](/operations/onchain)

[Phantom hardware-wallet instructions](https://help.phantom.com/hc/en-us/articles/4406388670483-Connect-a-Ledger-hardware-wallet-to-the-Phantom-browser-extension)

## What the setup creates

LP fee rights do not authorize withdrawal of the locked liquidity. The pool fee has a protocol/LP split; a 0.25% pool fee is not a claim that Scrip receives the entire 0.25%. Stock-linked pairing remains part of the product, but this SOL setup does not activate additional quotes or override issuer restrictions.

| Setting | Initial policy |
| --- | --- |
| Bonding curve | 1.00% platform + 0.25% protocol; no extra creator fee |
| Migration | Raydium CPMM index 9: 0.75% creator + 0.25% pool |
| Creator fee asset | Quote only; no project-token transfer tax |
| Initial quote | SOL; additional quotes require separate configuration and eligibility review |
| Liquidity | 100% permanently locked; platform treasury receives eligible LP fee rights |
| Supply allocation | No platform vesting allocation |
| Treasury | The approved Ledger receives curve fees, migrated creator fees, and the locked-liquidity Fee Key |

## Simulate, review, sign

1. **Connect the approved admin wallet.** Use the owner sign-in, then connect the Ledger-backed Solana mainnet account. Check the address on the hardware device.

2. **Simulate setup.** The server checks mainnet identity, fee configurations, existing accounts, account rent, and the exact post-transaction rules. The browser independently compares the transaction with the pinned policy.

3. **Review the complete summary.** Check admin, treasury, platform address, fee rates, LP fee rights, SOL cost, and the 0.02 SOL hard cap. Estimates are refreshed for each preparation.

4. **Approve on your Ledger.** Sign only the expected setup transaction. Nothing is signed or sent automatically when you visit the page.

5. **Refresh for finality.** The submitted signature is saved before broadcast. Completion requires a successful finalized transaction and matching onchain account state.

## Recover without double submission

If the browser or RPC times out after submission, refresh status. The saved signature remains attached to the attempt. Duplicate submission requests do not send another transaction. A replacement is allowed only after finalized blockhash expiry and a check that no platform accounts were created.

If the transaction has changed, the rates drift, the rules are missing, the wallet differs, or the cost exceeds the cap, setup stops for review. Never retry with a different wallet simply to bypass a failure.

## Platform setup is one milestone

A configured platform is not a launched token, active market, collected fee, provider credit, or buyback. A first market still needs its own launch transaction and verification. Fee collection needs an authorized claim, finalized receipt, durable asset accounting, and settlement before it can fund paid content.

Stock-linked assets require asset-specific technical and eligibility checks. A public buyback or revenue-share program needs its actual policy, funding, implementation, and applicable legal review. Terms cannot create permissions that a protocol, issuer, or applicable law does not allow.

[Fee schedule and scenarios](/revenue)

[Terms of use](/terms)

[Disclaimer & risk notice](/disclaimer)