deploy-stellar-mainnet
Walk through the devnet → mainnet deployment checklist for a Soroban contract or Stellar dApp. Use when a user says "deploy to Stellar mainnet", "going live on Stellar", "deploy my Soroban contract", "Stellar production deployment", "mainnet checklist", or "ship it on Stellar". Covers pre-deployment verification, deployment mechanics with stellar CLI, and post-deployment monitoring with Soroban-specific gates.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- deploy-stellar-mainnet
- description
- Walk through the devnet → mainnet deployment checklist for a Soroban contract or Stellar dApp. Use when a user says "deploy to Stellar mainnet", "going live on Stellar", "deploy my Soroban contract", "Stellar production deployment", "mainnet checklist", or "ship it on Stellar". Covers pre-deployment verification, deployment mechanics with stellar CLI, and post-deployment monitoring with Soroban-specific gates.
03 SKILL.md 正文
What this skill does
Walk through three gates. Do not let the user skip a gate.
Gate 1: Pre-deployment verification
Check each item. If any fails, stop and fix before moving on.
Contract correctness:
- [ ] All contract tests pass on testnet (
stellar contract invoke ...against a deployed testnet copy) - [ ] At least one end-to-end integration test exists (deploy → invoke → assert state)
- [ ] Storage usage profiled — no unbounded growth, TTL extension wired up for long-lived data
- [ ] Authorization paths reviewed — every
require_authis justified, no missing auth on sensitive operations - [ ] CPI (cross-contract call) safety considered if calling other contracts (reentrancy patterns)
Security:
- [ ] No
unwrap()on user-controlled paths — use?with proper error types - [ ] No panics on malformed input
- [ ] Integer overflow handled —
checked_*arithmetic ori128where appropriate - [ ] Admin operations gated by explicit role checks
- [ ] If accepting assets, contract uses the Stellar Asset Contract (SAC) correctly
Audit / formal verification (for high-value contracts):
- [ ] At least informal peer review by someone outside the team
- [ ] For contracts holding >$100K TVL or critical infra: third-party audit (Certora, OtterSec, Code4rena are active on Stellar — see
data/lumenloop/audits/registry.json) - [ ] If skipping audit, document explicit risk acceptance with reasoning
Operational:
- [ ] Admin keys: who holds them, where stored (hardware wallet preferred, NOT in CI secrets)
- [ ] Upgrade path: contract is upgradeable via WASM hot-swap, OR explicitly immutable and documented as such
- [ ] Emergency pause exists and is admin-only if user-facing funds are involved
- [ ] Deploy SOPs documented (1-pager — at minimum: who can deploy, network config, contract ID location)
Gate 2: Deployment mechanics
Check stellar CLI is installed: stellar --version (install: cargo install stellar-cli or brew install stellar-cli).
# 1. Ensure mainnet network is configured
stellar network add mainnet \
--rpc-url https://mainnet.sorobanrpc.com \
--network-passphrase "Public Global Stellar Network ; September 2015"
# 2. Build optimized WASM
stellar contract build
# Artifact lands at target/wasm32-unknown-unknown/release/<contract>.wasm
# 3. Upload to mainnet
stellar contract upload \
--network mainnet \
--source <DEPLOYER_KEY> \
--wasm target/wasm32-unknown-unknown/release/<contract>.wasm
# Save the returned WASM hash
# 4. Deploy (instantiate) from the uploaded hash
stellar contract deploy \
--network mainnet \
--source <DEPLOYER_KEY> \
--wasm-hash <HASH>
# Save the returned contract ID
# 5. Initialize if your contract has a constructor
stellar contract invoke \
--network mainnet \
--id <CONTRACT_ID> \
--source <DEPLOYER_KEY> \
-- initialize <ARGS>
# 6. Verify by reading state
stellar contract invoke \
--network mainnet \
--id <CONTRACT_ID> \
-- <read_method>
After successful deploy:
- [ ] Verify contract responds to expected read methods on mainnet RPC
- [ ] Run the smoke test from Gate 1 against the mainnet contract ID
- [ ] Save contract ID to repo README +
deployment-log.md(date, ID, WASM hash, deployer key fingerprint, commit SHA) - [ ] View on
stellar.expert/explorer/public/contract/<CONTRACT_ID>and confirm it matches expectations
Gate 3: Post-deployment
Monitoring:
- [ ] Indexer or event stream set up (Mercury, Subquery, or custom) to capture contract events
- [ ] Alerting on: unexpected admin operations, large value transfers, paused state changes, error rate spikes
- [ ] Dashboard for key metrics (TVL, user count, transaction volume) — even a simple Streamlit or Notion page works
Ecosystem distribution:
- [ ] Announce on X / Discord with contract ID and a
stellar.expertlink to verify - [ ] Submit project to lumenloop.com if not already listed
- [ ] Open PR to
github.com/lumenloop/stellar-ecosystem-dbadding a YAML entry — free distribution to the Stellar ecosystem
Funding / grants:
- [ ] If pre-launch SCF Build Award already received: prepare tranche reports — route to
scf-tranche-reporter - [ ] If not yet funded and round is open: route to
scf-round-watcherfor active round status, thenscf-submission-drafter
Constraints
- Do not let the user skip any Gate 1 checkbox. A broken mainnet contract is dramatically harder to fix than a delayed deploy
- For first-time deployers, walk them through
stellarCLI installation ifwhich stellarreturns nothing - For high-value contracts (anything holding user funds or being core infrastructure), refuse to proceed without at least informal peer-review evidence
- Mainnet network passphrase is critical — never copy from testnet config. The mainnet passphrase contains "September 2015"; testnet contains "September 2015" too but with "Test" prefix — always verify
04 同仓库更多 Skills
zk-proofs
Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.
tyler-architect
System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.
stellar-help
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
stellar-competitive-landscape
Map the competitive landscape for a Stellar project idea. Use when a user says "who are my competitors on Stellar", "competitive analysis Stellar", "what already exists in this space on Stellar", "show me similar Stellar projects", "is anyone else building this on Stellar", "map the Stellar landscape for X" — or the Spanish/mixed-language equivalents, e.g. "cual es la competencia de X", "que tan saturado está este espacio", "que aspectos están menos explorados y la SDF/SCF están dispuestos a fondear", or "analiza la competencia de estos bounties". Also fires when a user (directly, or via a BMAD persona like justin-analyst) names a specific protocol/idea inline and asks about its competition, viability, or market whitespace — including "should we integrate [external protocol]" or "does anything like this already exist on Stellar" research, where the deliverable is the same landscape map applied to a build-vs-integrate decision. Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.
standards
Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.
smart-contracts
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.