jferrant

There is inconsistency throughout the logs when printing hashes. It makes it impossible to know sometimes what hash is being printed and it is difficult to compare across logs for...

Neon integrations have a series of tests that utilize test_competing_miners_build_on_same_chain for testing multiple miners building blocks. We should have something similar for Nakamoto.

[Nakamoto] add a flow chart for the nakamoto miner

1

Not sure exactly where this should be stored, but it would be good to have a flow chart of the nakamoto miner. See https://github.com/stacks-network/stacks-core/pull/4827#pullrequestreview-2131106879 for additional context

There are some tests (e.g. block_proposal, sign_after_signer_reboot, mine_2_nakamoto_reward_cycles, etc.) that are not v1 specific tests and should be ported to v0 as well. Depends on a working path between miner...

Context https://github.com/stacks-network/stacks-core/pull/4788#discussion_r1607006217

Added two commands: generate-vote: prints a vote signature across a SIP and vote value using the provided key verify-vote: prints whether the message signature verifies against the provided info and...

Was irritated trolling the logs so figured I would open this quickly so I feel like I did SOMETHING

I really have no idea if these changes are correct...some insight would be nice. For some reason, sometimes this test has the first sortition has no tenure and as a...

Add an integration test for duplicate signers on the same network

1

We should have a test that spins up multiple signers with the same private key and ensure the system can handle signatures from duplicate signers. The first submitted valid signature...

Add a means to easily check if an external signer is signing blocks as expected

1

There are plans to add metrics to the dashboard concerning how many blocks were signed in a given reward cycle by a signer. Create an RPC endpoint that reports the...