Home

Degens mining - TM sBTC workflow wiki
Main flows, common grounds and differences between those

table of content

dkg
coordinator
signer
relay server
miners flow

dkg

They sign all network messages, so the recipients will know they are unaltered and came from the correct signers
The coordinator also signs its messages for the same reasons
This prevents spoofing and DOS attacks over the p2p network
The end goal is to sign the eventual BTC tx using an aggregate schnorr signature

• current config

  • "network_private_key" is the ECDSA signing key used to sign all outgoing messages
  • each signer has a public_key
  • coordinator has "coordinator_public_key", used to verify the signatures on the p2p messages

• where most messages are verified

• where the signers sign outgoing messages

• coordinator signs messages in several places e.g.

coordinator

• communicate to others to sign txs

• interact with stacks chain

  • read read-only
  • call sc
  • do DGK
    • where coordinator runs dkg round
    • where coordinator signs everything
    • the line calling the frost signing functionality
    • how to share key shards, create it etc.
    • dkg round isn't running where it should be. it should be run once every stacking cycle for TM and every time threshold changes on the sc for Degens
    • TODO: more questions

• btc tx

  • create btc transaction
  • send btc through transactions to given addresses
    • for "5" and "10" to send to pox address
    • for "1" to send to personal script

• TODO: complete with more points

signer

• btc tx tasks
  • for "4" and "9"
    • verify tx
    • sign tx
  • notify coordinator to combine all signs/key shards and broadcast tx
• sign messages
  • how do they sign?
  • do we need them to?
  • can they sign txs or is the message signing with nonce combined necessary for each to confirm its shard part of the key?
  • TODO: update with responses from github etc.

relay server

• take step by step

• how to run 3 signers via cli:

  1. run a relay: cargo run --bin relay-server
  2. in sep terminals run some stacks-signers.
     • stacks-signer run --id 1 --config ~/git/core-eng/stacks-signer/conf/signer.toml
     • stacks-signer run --id 2 --config ~/git/core-eng/stacks-signer/conf/signer.toml
     • stacks-signer run --id 3 --config ~/git/core-eng/stacks-signer/conf/signer.toml

• readme to test frost signing functionality alone

• readme to test stacking signing functionality

• can we simulate a DKG with it?

• TODO: update with responses and the commands/flow etc.

miners flow