deploy-stellar-mainnet
/deploy-stellar-mainnet
Prowadzi listę kontrolną wdrożenia kontraktu Soroban lub dApp Stellar z devnet na mainnet, od weryfikacji przez monitoring po starcie.
- Autor
- danielchukuma-dev ↗
- Repozytorium
- cougr ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 21.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi listę kontrolną wdrożenia kontraktu Soroban lub dApp Stellar z devnet na mainnet, od weryfikacji przez monitoring po starcie.
Wyzwalacze z opisu
Oryginalny opis (EN)
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.
Jak działa
- What this skill does
- Constraints
Podgląd SKILL.md
--- 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. --- ## 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_auth` is 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 or `i128` where 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`). ```bash # 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.expert` link to verify - [ ] Submit project to lumenloop.com if not already listed - [ ] Open PR to `github.com/lumenloop/stellar-ecosystem-db` adding 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-watcher` for active round status, then `scf-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 `stellar` CLI installation if `which stellar` returns 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
Wersje
W bazie nie ma innych skilli o nazwie deploy-stellar-mainnet.
Migawka bazy z 13.11.2026 · wersja paczki 4dab8981288d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95dapp
Pomaga budować aplikacje dApp na Stellar i Soroban w JavaScripcie: portfele, transakcje, podpisy i wywoływanie kontraktów. - 100smart-contracts
Pomaga pisać kontrakty Stellar w Rust z soroban-sdk, od struktury, przez build i testy, po bezpieczeństwo. - 91soroban
Pomaga pisać, testować i zabezpieczać kontrakty Soroban na Stellar w Rust, łącznie z wzorcami i pułapkami. - 100py-stellar-base
Buduje aplikacje na blockchainie Stellar w Pythonie przez stellar-sdk: transakcje, podpisywanie, zapytania Horizon, Soroban RPC, kontrakty, konwersja XDR i SCVal, async oraz integracje SEP. - 100upgrade-stellar-contracts
Przygotowuje kontrakty Stellar i Soroban do aktualizacji przez podmianę WASM, z migracją, zgodnością kluczy pamięci i testami. - 100java-stellar-sdk
Buduje aplikacje na blockchainie Stellar w Javie z stellar-sdk: budowanie i podpisywanie transakcji, zapytania Horizon, Soroban RPC, wdrażanie i wywoływanie kontraktów, konwersja XDR i SCVal oraz integracje SEP.