Docs/Build guides/Mainnet launch guide
Mainnet launch guide
A practical launch path for brands tokenizing selected loyalty value from sandbox testing to public Base use.
Loyfin launches should start with one clear onramp and one clear offramp. Keep the brand's CRM, points database, customer auth, fraud checks, and support in place; use Loyfin for the selected loyalty value that should move between the brand ledger and customer wallets.
Launch path#
Scope
Choose one existing loyalty balance, campaign, expiry rescue, credit, perk, or reward bucket to tokenize.
Dry run
Run controlled Base Sepolia Add to wallet and Add from wallet flows using disposable issuer, relayer, and customer wallets.
Integrate
Connect your backend to signed issuance and redemption actions, then poll receipts before changing final brand-side state.
Launch
Move to Base with clear customer copy, a support/reconciliation runbook, and public docs for customers and partners.
Decisions#
- Choose the issuer wallet or multisig. The issuer is the permanent brand identity and signs issue/redeem actions.
- Choose the admin owner. The owner controls metadata, royalties, and capability flags until ownership is renounced.
- Decide whether tokenized points can transfer, whether Add from wallet is open, and whether any expiry bucket is part of the launch scope.
- Choose your operation ID strategy before launch. See Operation hash.
- Create a Loyfin account, rotate an API key, and configure account-level webhook endpoints before wiring production traffic.
- Decide whether your app will use the session API plus Loyfin relayer, submit contract transactions directly, or run its own relayer.
Dry run#
Production uses Base mainnet and sandbox testing uses Base Sepolia. A brand engineer should complete one Add to wallet, one Add from wallet, one failed duplicate nonce, one expired deadline, and one polling-based confirmation before broad rollout.
Production checklist#
- Confirm the production factory and event emitter addresses in Contract addresses.
- Move admin owner to the intended multisig before opening broad access.
- Store signed operations internally with operation hash, customer ID, loyalty ID, amount, expiry bucket, status, and support reference.
- Use webhooks as the default completion signal, and keep receipt polling as a reconciliation fallback. See Receipts and webhooks.
- Prepare customer-facing copy for fees, expiry, transferability, Add to wallet, and Add from wallet. See Customer communication.
Public launch#
Mainnet Beta will launch on Base. Brands and integration partners should confirm the new production addresses, choose issuer/admin custody, and launch with the smallest loyalty value that can be supported clearly.