Go to file
shreerang a3738cb036 Update prerequisites to include published files (#17)
Part of https://www.notion.so/Create-stacks-for-mainnet-1f2a6b22d4728034be4be2c51decf94e

Co-authored-by: Shreerang Kale <shreerangkale@gmail.com>
Reviewed-on: #17
Co-authored-by: shreerang <shreerang@noreply.git.vdb.to>
Co-committed-by: shreerang <shreerang@noreply.git.vdb.to>
2025-06-13 09:29:03 +00:00
config Update multisig playbook to setup deployment on remote machine (#15) 2025-06-11 15:05:04 +00:00
docs Update prerequisites to include published files (#17) 2025-06-13 09:29:03 +00:00
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 Divide generate genesis and create validator playbooks into build and start playbooks (#13) 2025-06-10 10:07:15 +00:00

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

  • 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

    • Run Subsequent Validator Nodes: Run subsequent validator nodes by following the instructions in run-validator.md