-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NOMERGE: [0.17] Signet implementation #433
Conversation
7e93457
to
2b3b8c8
Compare
cc0f135
to
93d75f3
Compare
e55e65e
to
5e9632a
Compare
log "hit ^C to stop" | ||
|
||
while true; do | ||
let rv=$RANDOM%$randinterval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this needs +$min_time
We're going to work directly on a branch, rather than a PR on top of elements-0.17. |
You're going to need at least part of it here too, assuming #414 is merged and forward ported. putting it all facilitates testing since you wouldn't need a separated binary to test the fedpeg to a parent signet anymore. |
Not going to delete the branch to be clear. I made a copy to the repo: https://github.com/ElementsProject/elements/tree/e17-signet IIRC I was getting conflicts as the base branch was moving along with features, and for now we just wanted a 0.17 Core branch to work on. |
A rebase of kallewoof/bitcoin#5 on top of #432 taking the opportunity to simplify its changes around chainparams code and adding a test that also acts as a script to generate a private key in wallet importable format and its corresponding p2pk blockscript, which should be useful for people wanting to generate their own signets.
This represent a hardfork from that implementation because the genesis block now includes the name of the chain too, like all other custom chains, and the bits have to be low enough so that tests keep working with regtest-like pow.
Example to generate chain arguments:
That will generate:
Dependencies: