Avatar
Dan
40bdcc08888d98d49d03fb93bffd1cc46d9b8f187d08c9fc81b4adf0ad00fd2c
Est. 769,296

Having a relaxing morning routine is sooo key to me not losing my mind at work. I throw on a record, make some espresso, water our plants, and read something uplifting. Sets the whole day's trajectory!

Every drivechain supporter should be required to, with a whiteboard, explain how they work. Not saying a ton of you couldn't. But there are some of you that definitely couldn't.

If you suddenly doubled/tripled/whatever the number of Bitcoin nodes could you hypothetically DDoS the existing nodes by doing too many IBDs at once?

If 2x is good, 10x must be gooder

PWAs distributed via nostr relays would be very cool

Running Lume, join with me #nostr #lume : https://lume.nu

Replying to Avatar PABLOF7z

nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x extension: 0.2.1 released

Codename: Thanks, Comrade Google!

👉Now available on the Chrome Store!

Create nostr highlights from ANYWHERE on the web, (including paywalls)

Add comments to any website

Add nostr encrypted bookmarks

All WITHOUT granting ANY access to the extension, the way it should be.

https://chrome.google.com/webstore/detail/higlighter-extension/hkicahoeiljchfoopjibfdnibceelecp

https://cdn.satellite.earth/c2dbf656d5989389c6b89a6249f2491a5efa173df39e76eccaca2e058fe4c060.mov

I know it is not designed for Arc browser, so totally not a complaint, but interestingly clicking the extension or context menu does nothing. no errors, no popups, just sits there. Interesting. Installs without issue though

Sent my brother a snort link once and he immediately said "what is this? Social media for drugs?" 😂

I stopped sharing snort links after that...

Watching Brian Deese this early in the morning was a terrible idea... 🤢

Each node maintains its own mempool. The mempool is a collection of unconfirmed transactions stored in a Bitcoin node's memory, waiting to be included in a block. However, the mempool is not uniform across all nodes due to the following reasons:

1. **Transaction Propagation Time**: It takes time for a new transaction to propagate across the network. Different nodes may hear about transactions at slightly different times.

2. **Node Policies**: Not all nodes have the same transaction acceptance policies. Some nodes might refuse to accept a transaction if its fee is too low, or for other policy reasons.

3. **Mempool Size and Limits**: Nodes might have different hardware capacities. Some nodes set limits on the maximum size or number of transactions in their mempool to prevent running out of memory. If the mempool reaches its limit, the node might start dropping low-fee transactions.

4. **Node Restart and Uptime**: If a node goes offline or is restarted, its mempool might be cleared, and it would then start building it up again based on new transactions and what it hears from peers.

5. **Mempool Eviction**: If a transaction remains unconfirmed for a long time (perhaps due to a low fee), some nodes might eventually drop it from their mempool.

Due to these factors, while there's a significant overlap, the exact contents of the mempool can vary from one node to another.

RBF or wait it out 🤷‍♂️