How do I deploy my smart contract on a test net? on mainnet?

[dckc]

I was recently asked about this...

[dckc]

notes in progress

A typical progression is:

1. Write a contract and test it outside any blockchain
2. Test it on a JavaScript-only simulated chain ("sim chain")
3. Test it on a local chain (including golang tendermint consensus, cosmos-sdk)
4. Test it on devnet - a multi-validator development network where nearly anything goes
5. Test it on emerynet - a multi-validator test network intended to be as similar to mainnet as possible
6. Deploy to mainnet

Write and test a contract

Use agoric init to scaffold the project, as discussed in Starting a Project.

Not discussed there:
cd contract; yarn test to run some agoric-sdk style ava tests that use E(zoe).install() and E(zoe).startInstance().

Permissioned, Permissionless Deployment

Keep in mind the phased roll-out of the Agoric chain:

0. cosmos-sdk only with BLD staking and governance token
1. JavaScript smart contracts written by Agoric and the addition of the Inter Stable Token, IST.
2. Permissioned smart contracts
3. Permissionless smart contracts

The beta release of the Agoric SDK was a preview of permissionless smart contracts that extended the distributed computing framework all the way out to client machines in a peer-to-peer fashion. Much of the SDK documentation is written for this architecture, but aspects of it are not complete for production use.

The architecture that was deployed in phase 1 is a smart wallet architecture where clients can make RPC queries and send signed offer transactions. Until phase 3, smart contract deployment is permissioned by BLD staker governance.

Environment	tendermint consensus	Permissionless	Permissioned
ava / yarn test	no	YES	yes*
sim chain	no	YES	no
local chain	YES	YES	YES
devnet	YES	YES	YES
emerynet	YES	no	YES
mainnet	YES	no	YES

Test it on a sim chain

Use agoric start to start a simulated chain and ag-solo client, as discussed in Starting a Project.

Use the REPL to interact with the contract.

sequenceDiagram
  participant wallet-ui
   note right of wallet-ui: on desktop
  participant ag-solo
   note right of ag-solo: wallet-vat

  participant zoe

    wallet-ui->>ag-solo: makeInvitation()
    ag-solo-->>cardStore: makeMintInvitation()
    cardStore-->>ag-solo: inv1
    ag-solo->>zoe: offer(inv1, { want: { name: 'Fred' } })
    zoe-->>cardStore: handle(seat1, { want: { name: 'Fred' } })
    cardStore-->>zoe: zcfMint(character)
    zoe-->>ag-solo: { payouts: character }

Loading

Test it on a local chain - permissionless preview style

As discussed in Starting Multiuser Dapps:

Use agoric start local-chain to start a single-node blockchain, including cosmos-sdk tendermint consensus.
Use agoric start local-solo.

Test it on a local chain - permissioned contract deployment

See Permissioned Contract Deployment.

Missing

• the proposal is atypical; should use E(zoe).installBundleID() and E(zoe).startInstance().
• voting for the proposal
• interacting with the contract

See also: Smart Wallet Dapp Architecture.

devnet

See https://devnet.agoric.net/ for chain-id, RPC, explorer, faucet, etc.

devnet validators include a few nodes run by Agoric plus several by community members.

devnet gets reset occasionally with little notice.

Devnet supports both permissionless and permissioned deployment.

To set up an ag-solo client for permissionless deployment, see:

• Setting up an Agoric Dapp Client with docker compose

emerynet

Emerynet, like mainnet, supports only permissioned deployment.

See https://emerynet.agoric.net/ for chain-id, RPC, explorer, faucet, etc.

mainnet

See Integrating with Agoric Network