Repository navigation
Caatinga v3.10.3
Caatinga v3.10.3
Status
Stable patch release on top of 3.10.2. Recommended for anyone targeting mainnet: with the default mainnet config, 3.10.2 and earlier could not reach mainnet at all.
Packages
@caatinga/cli@3.10.3@caatinga/core@3.10.3@caatinga/client@3.10.3@caatinga/zk@3.10.3
npm install -g @caatinga/cli@latestCompatibility
- Node.js 22+
- Stellar CLI minimum
23.0.0, last tested28.0.0 - Rust 1.91.1+ with the
wasm32v1-nonetarget (not 1.91.0)
Fixes
- Mainnet commands use the configured RPC. A config matching the well-known mainnet network (
https://mainnet.sorobanrpc.com+ the public passphrase, the scaffold default) was passed to the Stellar CLI as--network mainnet. The CLI's built-inmainnetentry has no RPC URL ("Bring Your Own"), soread,invoke,deploy,upgradeand related commands failed withInvalid URL Bring Your Own: …, or silently used a locally addedmainnetnetwork. Mainnet now always gets explicit--rpc-url/--network-passphrasefromcaatinga.config.ts; testnet keeps the--network testnetshorthand. (#224) - No implicit
aliceon mainnet.ctg readandctg smokeno longer fall back to the built-inaliceidentity on mainnet (detected by name or passphrase). Pass--source <alias>or setCAATINGA_SOURCE; otherwiseCAATINGA_SOURCE_ACCOUNT_REQUIREDis raised. Testnet keeps thealicefallback. (#226) - ZK dev-ceremony block detects mainnet by passphrase.
ctg zk build,ctg zk invokeand verifierctg deploynow block single-party dev-ceremony artifacts on mainnet networks with a custom name (e.g.pubnet), not only on a network literally namedmainnet. (#228)
Behavior change
ctg read/ctg smokeagainst mainnet now require an explicit source identity.
API additions (backward-compatible)
describeCliSource(explicit, { network })/resolveCliSource(explicit, { network })accept an optional target network.isProductionNetwork(name, config?)andassertDevCeremonyAllowed({ networkConfig })in@caatinga/zkaccept an optional network config.
Full changelog: v3.10.2...v3.10.3