Damus
BlessedBovine profile picture
BlessedBovine
@BlessedBovine

Husband of npub12wk0tlwr5wa39l6slw8rskwsvkatcll6zjrx8d909ltkvu7lsalsveyvqf
Father
Catholic
Bitcoiner (Class of 2023)
American Dreamer
Bitcoin Full Node Runner on Tor
On Nostr Since 850200; Verified 852712

Relays (8)
  • ws://100.112.123.51:8080/ – read & write
  • wss://nos.lol/ – read & write
  • wss://relay.nostrplebs.com/ – read
  • wss://relay.primal.net/ – read
  • wss://relay.primal.net/v1 – read
  • wss://192.168.0.231:8080/ – read & write
  • wss://nostr.land/ – write
  • wss://nostr.mom/ – write

Recent Notes

Johnny · 2d
nostr:nprofile1qqsv2e42qa64uxvz727walka85d3gux8kz2xqzsz5d3x044snjd6fgszmqwsx that is fair, i read channel as an in protocol one. the social side is real, it just runs operator to operator rather than at miners, and none of it binds until it ships as code someone chooses to run.
BlessedBovine profile picture
#BIP110 didn't fail because of "corrupt" miners, nor did it fail due to miners "colluding" with one another. Although I do agree that miner centralization could pose a risk, I don't think that the bippers are correct in calling the miners corrupt over the failure of BIP110 to activate. The failure to activate was a due to a lack consesus among the broader node community.

I'm a pleb. I'm not a cryptographer, nor am I a software developer in any way. This post is mostly just testing and articulating my understanding of the Bitcoin network. If I'm correct in my understanding of the #WhitePaper and how the #Bitcoin network operates, then the following is true:

1. Nodes provide the rules for the Bitcoin network through reaching an independent agreement (consensus) of what is and isn't allowed. They communicate these rules to the miners.

2. Miners try to brute force guess the magic number to mine the next block for the timechain. They also create templates for what information they want to put into the block. Generally being monetary transactions based on fees, but also "spam" or other inscriptions (“The Times 03/Jan/2009 Chancellor on brink of second bailout for banks” inscribed by Satoshi). Miners can also choose not to include transactions, spam, or inscriptions based on their own criteria. Which is why controlling enough hash to assure your transactions get through is important.

3. If 51% or more of the nodes are in agreement of what the rules of the network are, they have consensus.

4. A miner who tries to submit a block that violates the consensus will have that block rejected by the nodes with consensus, and therefore rejected by the Bitcoin network. If there are nodes that would otherwise accept that block, the minority nodes fork off. Or vice versa, the majority network with consensus accepts a block, while the minority nodes may reject a block, causing the minority to fork off.

BIP110 forked off because they didn't have majority node consensus. They composed a minority consensus with one another rejected a block that was considered acceptable to the majority of nodes, and forked off.

I don't think changing the #PoW (proof of work) of #BTC is the correct solution. For BIP110 (or any other BIP) to succeed, I think they need to:

1. Acquire majority consensus with the nodes all signaling for an upcoming rule change.

2. After acquiring consensus through signaling for the change, they need to put out a specific block height for the change to go effective, and broadcast it to as many node runners signaling for the BIP as possible.

3. After step two they should notify the miners of an upcoming consensus rule change, and warn them (miners) that blocks submissions that are not compliant with the new consensus will be rejected by the network after the specified block height.

Is that all correct? #AskNostr #AskBTC
2❤️1
oadissin · 3d
Greetings, It is a community of node who will decide the adoption or rejection of the upgrade. Perhaps you are free to explore this opportunity. Satsman pays you in Bitcoin for learning about Bitcoin. If you've been Bitcoin-curious but didn't know where to start — this might be it. https://tinyurl...
BlessedBovine · 3d
Audio is missing for some reason. Playing fine on the device I uploaded it from, but not in the nostr client. Luke (forward) makes a face when the other guy mentions changing the proof of work for the Bitcoin network. https://youtu.be/rHKXKR-jXPg?t=5061
Johnny · 3d
nostr:nprofile1qqsv2e42qa64uxvz727walka85d3gux8kz2xqzsz5d3x044snjd6fgszmqwsx six confirmations is a cost estimate. it says reversing that far back gets expensive enough that nobody bothers, and it holds as long as every node is applying the same validity rules. when nodes disagree about what counts ...
Johnny · 4d
nostr:nprofile1qqsv2e42qa64uxvz727walka85d3gux8kz2xqzsz5d3x044snjd6fgszmqwsx start with the recovery instead of the device. make a seed, wipe it, restore it on a different wallet, and fund it only aft...
BlessedBovine profile picture
The paralysis is in finding the "right" hardware solution. I'm very comfortable and confident in restoring a seedphrase. My discomfort comes from ever being able to trust a wallet has been generated with proper entropy. Even with the dice roll, or coin flips, how do I know that the hardware is taking that into account or properly hashing a key from the input?

Best I can figure is separate devices all tested 2-3 times with the same inputs against each other, until using them to finally generate a key. Since they should all generate the same mnemonic seed given the same dice roll input.

Or hashing it out myself, but that introduces its own potential risk of human error on the mathematical end.
1❤️1🤙1
Johnny · 4d
nostr:nprofile1qqsv2e42qa64uxvz727walka85d3gux8kz2xqzsz5d3x044snjd6fgszmqwsx the check that settles both worries is deriving the first address yourself, offline, from the seed the device gave you. if your derivation and the device agree, the entropy question is closed and so is the human error one, ...
The Bullish ₿itcoiner · 4d
Yes! nostr:npub1zzmxvr9sw49lhzfx236aweurt8h5tmzjw7x3gfsazlgd8j64ql0sexw5wy has attended at least a couple markets. 💪