Substrate Multisig

A simple workable Demo that shows how to implement a multi signature smart contract in Pallet(Runtime) module.

Recommend that DO NOT use it in production.

Description

It is an example to show that how to completely implement a multi signature wallet using pallet. It includes:

How to generate a random AccountId that is impossible to control with a known secret key, like a smart contract address
How to make Calls on-behalf-of this randomly generated account

Dapp-developer-friendly, as it acts in the same way as the multisig wallet smart contract while implemented in Pallet(Substrate Runtime).

What you can do with it

Use multi-sig wallets as the stash-controller pair, it allows multi users to collaborate while it requires no trust
Make decisions within a DAO

Ready for Hacking

Introduce score to better measure each member's power
...

Build

Install Rust:

curl https://sh.rustup.rs -sSf | sh

Build Wasm and native code:

cargo build --release

Run

Single node development chain

Purge any existing developer chain state:

./target/release/node-template purge-chain --dev

Start a development chain with:

./target/release/node-template --dev

Detailed logs may be shown by running the node with the following environment variables set: RUST_LOG=debug RUST_BACKTRACE=1 cargo run -- --dev.

Multi-node local testnet

If you want to see the multi-node consensus algorithm in action locally, then you can create a local testnet with two validator nodes for Alice and Bob, who are the initial authorities of the genesis chain that have been endowed with testnet units.

Optionally, give each node a name and expose them so they are listed on the Polkadot telemetry site.

You'll need two terminal windows open.

We'll start Alice's substrate node first on default TCP port 30333 with her chain database stored locally at /tmp/alice. The bootnode ID of her node is QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR, which is generated from the --node-key value that we specify below:

cargo run -- \
  --base-path /tmp/alice \
  --chain=local \
  --alice \
  --node-key 0000000000000000000000000000000000000000000000000000000000000001 \
  --telemetry-url ws://telemetry.polkadot.io:1024 \
  --validator

In the second terminal, we'll start Bob's substrate node on a different TCP port of 30334, and with his chain database stored locally at /tmp/bob. We'll specify a value for the --bootnodes option that will connect his node to Alice's bootnode ID on TCP port 30333:

cargo run -- \
  --base-path /tmp/bob \
  --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR \
  --chain=local \
  --bob \
  --port 30334 \
  --telemetry-url ws://telemetry.polkadot.io:1024 \
  --validator

Additional CLI usage options are available and may be shown by running cargo run -- --help.

sekisamu / substrate-multisig