cerc-io/laconicd-stack
14
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
21 Commits 5 Branches 0 Tags 7.5 MiB
Shell 57.1%
Python 41.1%
Jinja 1.8%
7b24731d70
Go to file
Prathamesh Musale 7b24731d70 Avoid removing existing console deployment
2025-06-13 19:01:04 +05:30
config Update multisig playbook to setup deployment on remote machine (#15) 2025-06-11 15:05:04 +00:00
docs Avoid removing existing console deployment 2025-06-13 19:01:04 +05:30
playbooks Update prerequisites to include published files (#17) 2025-06-13 09:29:03 +00:00
scripts Update playbooks to sign txs on a separate machine from the one running laconicd node (#5) 2025-06-09 12:37:50 +00:00
stack-orchestrator Divide generate genesis and create validator playbooks into build and start playbooks (#13) 2025-06-10 10:07:15 +00:00
.gitignore Add playbook to send create-validator tx for subsequent nodes (#3) 2025-05-16 09:54:09 +00:00
node-addresses.yml Add stack to run mainnet validator node (#1) 2025-05-15 06:38:42 +00:00
README.md Add steps to migrate service provider deployment 2025-06-13 18:30:36 +05:30

README.md

laconicd-stack

  • This stack is used for running nodes to launch Laconic mainnet chain

  • It allows you to export SAPO testnet state and start mainnet nodes

Mainnet OPS

  • To launch Laconic mainnet, follow these steps:

    • Run the First Validator Node: Begin by setting up and running the initial validator node as detailed in run-first-validator.md

    • Deploy Cosmos Multisig App: Integrate and run the Cosmos Multisig app using the playbook available at cosmos-multisig-app playbook

  • To migrate existing deployments from SAPO testnet to mainnet, refer to update-deployments.md

Join Mainnet

  • Run A Validator Node: Follow steps in run-validator.md to run a mainnet validator node

  • Update Service Provider: Follow steps in update-service-provider.md to migrate your service provider from SAPO testnet to mainnet