stacks-network
Mainnet Mock Signing confirmation and feedback
We'll use this to track successful mock signing on Mainnet from Signers and also help troubleshoot any issues. Goal:
- Atleast 100% of Public Signers to confirm that mock signing works on Mainnet
- Atleast 95% of Private Signers to confirm that mock signing works on Mainnet
- 15 of 40 Signers are successfully mock Signing as of Aug-30-24
- Most likely that Signers haven't upgraded yet
Signer key: 0239c18936f09a6194a7f6ba8f5f25556520325141fe8f4b3d8bca6d8da2d45fb8
Testnet logs
Signer Key: 02778d476704afa540ac01438f62c371dc38741b00f35fb895e5cd48d070ebab41 Mainnet Logs.txt Testnet logs.txt
Signer Key: 0x03fc7cb917698b6137060f434988f7688520972dfb944f9b03c0fbf1c75303e79a
signer testnet logs.txt signer mainnet logs.txt
Signer key:
025b55f3c4ce97bf39f7c7ae45f71a12a5dadaf4f4fd6964e52c914128d021433b
Mainnet signer logs.txt testnet signer logs.txt
Signer STX address: SP2VK5S20KQ1QHFBDRKRJD5EW12TYHAZJMPAFFQEK
Signer Key:
020100729b92cbb163dae01a92c8191f531afb663c0dcf8cad59b2888b879fee63
Signer key: 02448796d32eb4ea7766d8be9ce71430a488698fd9433fa5f4842a5e99e3f7ff2d
signer pubkey: 03f8fb910ad71bd774ca53f06d99988295dcc1802498c64a24fbddffa035e96315
Signer Logs SN.txt signer logs 2 SN.txt node logs SN.txt
Signer key: 02c1037d06165188745709ba57d38adce71a036f403dd02dfda78add9adecdec05
Signer pubkey 0253c42dfe58b48e57a621415557878ac7438cae5ac419c8d6bf08316c0349cef0
Signer Pubkey 02e32e665bb3420e64847ff28361a4fd95ff574d422d283b5c895b60802ee7250e node.logs.gz signer.logs.gz
@saralab @hstove could you pls take a look at the logs and let us know if there are any issues, couldn't find Jacinta on GH so pls feel free to add her as well!
We've received 12 signer logs so far and working on getting a couple more asap.
Thank you!
Signer pubkey : 03ed732eab6b99b90315f9b58ce9c3e2d1991bc4e9cfa59841535c0ef7dbba38e0
Signer key:
025b55f3c4ce97bf39f7c7ae45f71a12a5dadaf4f4fd6964e52c914128d021433b
These mainnet logs look good. The testnet logs appear to be stacks-node logs, not signer logs, and it's possible there is something wrong with the config of that node.
Signer STX address: SP2VK5S20KQ1QHFBDRKRJD5EW12TYHAZJMPAFFQEK
This seems to be known based on the filename, but this signer is not registered for the cycle that these logs are from. Otherwise, the logs are as expected.
Signer key: 025b55f3c4ce97bf39f7c7ae45f71a12a5dadaf4f4fd6964e52c914128d021433b Mainnet signer logs.txt testnet signer logs.txt
These mainnet logs look good. The testnet logs appear to be stacks-node logs, not signer logs, and it's possible there is something wrong with the config of that node.
@obycode could you please specify what is wrong with the node config? is it the stacker=true issue ?
Signer Key: 039ce67c2c914802fc405c860d76851ee243a7aadefa0ea7cb26d23f4ee6046a1b
@saralab @obycode last remaining public signer logs
Signer key: 02c1037d06165188745709ba57d38adce71a036f403dd02dfda78add9adecdec05
Signer Key: 03e0df37e83e43847625a0320456cb9758050a61ce76c2c130bf50242f27ba6d54 20240918-signer-logs.txt
Signer Key: 03ed732eab6b99b90315f9b58ce9c3e2d1991bc4e9cfa59841535c0ef7dbba38e0
Signer KEY: 0x024f164c6e73df283d34d7d9cc86553a82dce76045ba7dfbf4de0004f89eabb8e0 Signer logs SN2.txt