Exchange balance for Ethereum

When all merkle branches for a pool match another pool (colored cells), it means that they are using the same block template.

You can also see custom transaction prioritization, like a tx accelerator, when there’s a lower than normal fee rate for the “first transaction”.

As with any ai, it's not going to be 100% correct 100% of the time.

Still pretty good for a brand new one imo...

I have one specific journo who always asks me for quotes on “crypto” regulation and policy — but he always brings it around to XRP, the Ripple foundation, and the “bold moves” of Gerlinghouse.

At this point, I’m certain he needs to write these articles to pump his own bags…or he’s gotta fulfill that XRP grant…

The only people I’ve met who’ve talked to me about XRP are people paid to do so

Overton window shattered.

I asked my Rabbit r1 who created nostr;

Our old house garden is going nuts ... pears, figs, blueberries ... Leaving these as a gift for my parents to tend 😁

#permies

Supra I believe

Hash rate jumps up and down all the time

Testing out a new Lightning wallet, first 3 people who respond to this note get zapped.

anyone use a blockstream Jade and how did you like it

#asknostr #plebchain #hardwarewallet

Day 49 of buying $1 worth of BTC everyday as part of a long term social experiment to see how BTC performs against the USD as well as a historical record. I want to find out if “stacking sats” really was beneficial.

Silent Payments are clever: you create a shared secret (ecdh) from a utxo and a public silent payment address. Then you simply add (tweak) this shared secret into this silent address.

The receiver then scans the entire utxo set, looking for any payments to this silent payment address tweaked with the shared secret from all taproot/pubkey inputs.

For onchain zaps, you can skip the scanning process and just send a giftwrap with the txid and the receiver can verify that you sent it and control the utxo just by knowledge of this shared secret.

To generate the shared secret from the sender side, you need the inputs private key multiplied by the silent address pubkey.

On the receiver side, you multiply the silent address secret key by the input’s pubkey.

This gives you the same shared secret which you can use on both sender and receiver side to validate the onchain zap.

The nice thing about leveraging silent payments is that the receiver doesn’t have to use nostr, they could just be using a silent payments wallet to receive the zap.

On the nostr side, all you would need is a silent payment address in your profile. Heck you could even use the users pubkey itself as a key as a less secure silent address fallback if they don’t have one in their profile.