Avatar
Big Barry Bitcoin
0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14
Big Barry Bitcoin - Bitcoiner, pleb, developer, enthusiast, 👎💩coins Check out my nostr blog! https://big-barry-bitcoin.npub.pro/

They decide how to resolve a potential double spend. But a double spend is really when conflicting txs append to the blockchain. So validating blocks is the preventative measure.

During the validation process.

The successful miner will have validated transactions and in the case of a double spend where all conflicting transactions are still unconfirmed, the miner will have chosen one of them based on their own criteria such as fees, other associated unconfirmed transactions, and their fees. That is how a double spend is RESOLVED.

A double spend is PREVENTED when nodes validate blocks and ensure that there are no double spends present within the blockchain. If a double spend is detected, then the block is not appended to the user's blockchain and the double spend is prevented. This happens the same on all nodes across the network.

Can't wait to come tonight. Just know that the universe has been putting obstacles in my way, but I WILL make it.

That's Bob. Bob had a sex change and now likes to be called Barbara.

Looks like it is warning you that it hasn't got the latest info yet and you're asking it to add a contact on top of an empty list... It is assuming that this is wrong (which it is) and avoiding the worse outcome where people start asking "I used to follow 100 people, now I follow no one?"

Replying to Avatar Sjors Provoost

nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 for a non-travel coldcard it could be handy to have one pin for duress (when you need to type the number) and one to trigger an explosion (when the bad the bad guy is typing).

But I suppose customs wouldn't like that. And ordering that component separately might also invite the wrong kind of attention.

Been watching spy movies recently?

The timestamps on the blocks are written by the miner that built the block.

Computers suck at time, so the time of one machine may be minutes off another, also miners could be intentionally lying in the hopes of breaking or swaying something in the Bitcoin protocol.

Fortunately, this is all accounted for in the code. Timestamps are allowed a threshold of error when an active node sees it, so that reduces massive lies, and there is also a threshold, although more forgiving, applied when nodes are validating historical blocks during bootstrapping.

Also the difficulty adjustment algo in Bitcoin relies on the timestamps, but it relies on median averages instead of mean averages because that is less susceptible to biases.

Bitcoin has us covered.

My nostr experience is pretty fine, for social media, for zaps, for keeping a private spreadsheet via sheetstr, and for blogging.

I also don't see a wave of nostr devs getting frustrated with technical debt or bad design and quitting, heck I see interest growing.

Look out the other window friend.