forked from collinsadi/opauque-stellar
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
27 lines (23 loc) · 1.28 KB
/
Copy path.env.example
File metadata and controls
27 lines (23 loc) · 1.28 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
# =============================================================================
# Opaque Stellar — root .env (contract deployment / tooling)
# =============================================================================
# Copy to `.env` (`cp .env.example .env`) and fill in before running:
# npm run deploy:testnet # build + deploy all contracts to testnet
# npm run deploy:mainnet # mainnet (requires audit signoff)
#
# The FRONTEND has its own env file — see frontend/.env.example. You only need
# this root .env when deploying contracts.
# -----------------------------------------------------------------------------
# Target network for deploys: testnet | mainnet
STELLAR_NETWORK=testnet
# Deployer identity (PREFERRED). Create once with the Stellar CLI:
# stellar keys generate opaque-deployer --network testnet --fund
# stellar keys address opaque-deployer
# Then set the identity NAME here:
STELLAR_DEPLOYER=opaque-deployer
# Alternative to STELLAR_DEPLOYER: a raw secret seed (S...). Use ONLY for
# automation/CI; never commit a real secret. If both are set, STELLAR_DEPLOYER wins.
# STELLAR_DEPLOYER_SECRET=S...
# Optional: the funded G... address to record as deployer/admin in the manifest.
# Auto-derived from STELLAR_DEPLOYER when omitted.
# STELLAR_DEPLOYER_ADDRESS=G...