Original contents of the issue follows. It was submitted as https://github.com/bitcoin-sv/bitcoin-sv/issues/210 but later deleted by the repository owners.
| #!/bin/sh | |
| cd ~/src/bitcoin/src | |
| ./bitcoind -regtest -daemon=1 | |
| printf "Waiting for regtest bitcoind to start" | |
| while ! ./bitcoin-cli -regtest getconnectioncount 2>/dev/null 1>&2 | |
| do printf .; sleep 1 | |
| done; echo |
My previous issue #220 was deleted as it was not fully code-related. But there is one part of it, which is.
Please have a look at this code-related part of it:
London Bitcoin Devs links for Socratic on “Taproot is locked in. What now?”
July 20th 2021
YouTube Live link: https://www.youtube.com/watch?v=GAkLuZNsZzw
Zoom link (passcode if needed 957503): https://us02web.zoom.us/j/82418128719?pwd=SVRvZ0Rvd094UHROazM5VTBKcHVTQT09
Meetup link: https://www.meetup.com/BitDevsLDN/events/279041693/
A description of known problems in Satoshi Nakamoto's paper, "Bitcoin: A Peer-to-Peer Electronic Cash System", as well as notes on terminology changes and how Bitcoin's implementation differs from that described in the paper.
The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power.