Skip to content

docs: comprehensive Stellar deployment guide#186

Open
sungdark wants to merge 1 commit intoANAVHEOBA:mainfrom
sungdark:docs/deployment-guide
Open

docs: comprehensive Stellar deployment guide#186
sungdark wants to merge 1 commit intoANAVHEOBA:mainfrom
sungdark:docs/deployment-guide

Conversation

@sungdark
Copy link
Copy Markdown

Summary

Added docs/DEPLOYMENT.md — a comprehensive step-by-step guide for deploying the PrivacyLayer ZK-proof shielded pool to Stellar testnet and mainnet.

What Was Added

  • Prerequisites: Rust 1.75+, Stellar CLI 20.0+, Noir toolchain installation and verification
  • Circuit Compilation: Commitment and withdraw Noir circuits with verification key generation
  • Contract Compilation: WASM build, optimization with wasm-opt, hash verification
  • Testnet Deployment: Full walkthrough with 10 steps (network config → initialize → verify)
  • Configuration: Admin, fee, deposit enable/disable controls
  • Testing: Deposit and withdrawal test procedures
  • Mainnet Deployment: Security checklist with 8 pre-deployment requirements
  • Troubleshooting: Common errors and debug commands
  • Production: Monitoring, backup, and upgrade path guidance

Why This Matters

The PrivacyLayer project is the first ZK-proof shielded pool on Stellar Soroban. This guide enables developers and auditors to independently deploy and verify the contract, which is essential for trust and adoption.

Payment address: eB51DWp1uECrLZRLsE2cnyZUzfRWvzUzaJzkatTpQV9

Bounty: USDC via Drips Wave - Create Comprehensive Deployment Guide (issue ANAVHEOBA#18)

Added docs/DEPLOYMENT.md with:
- Prerequisites (Rust, Stellar CLI, Noir toolchain)
- Testnet account setup and funding
- Circuit compilation (commitment and withdraw circuits)
- Contract compilation and WASM optimization
- Testnet deployment step-by-step
- Contract initialization and verification
- Configuration (admin, fees, deposits)
- Test deposit and withdrawal procedures
- Mainnet deployment with security checklist
- Troubleshooting section with common errors
- Production monitoring and backup considerations

Payment address: eB51DWp1uECrLZRLsE2cnyZUzfRWvzUzaJzkatTpQV9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants