Thanks for reporting this issue. I've made an issue on GitHub to report this UX bug
Thanks for reporting this issue. I've made an issue on GitHub to report this UX bug
nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 how about a functionality to pin unconfirmed transactions in my personal node so they don’t get purged?
Made a feature request as an issue on GitHub.
Please add any information if you have additional ideas.
Justin Murray posted these photos of bitcoin miners on sale at an electronics market in Shenzhen.
https://twitter.com/jjustinmurrayy/status/1735877635824386265
5 pools provide block templates for 85% of the hashrate.
Self sovereign zaps to my tor LN node are now finally enabled
I tried to set up zaps without success 8 months ago. My LN Address worked but nostr clients didn't recognise that the payment had been made. Thanks to @npub1y24gz5gwucl79vtv4ctwpysl0r5m4xyzu2rgulnr44ks3t5mt92q4nz2ad this is now easy for btcpayserver users
1. Exposed your BTCPayServer publicly (guide here https://orange.surf/public-btcpay-umbrel-tailscale/)
2. Create a lightning address in BTCPayServer
3. Install the nostr BTCPayServer extension, enter the same name and your Nostr PubKey and PrivKey
Zaps will now work.
Remember to set relays for the zap response post
For example
wss://relay.primal.net
wss://relay.damus.io
wss://relay.snort.social
If you previously used an old version of the plugin uninstall and reinstall the latest (1.1.2)
If a small amount of gold is real it can be used.
If a utxo is expected to remain unspendable it can't be used
Self sovereign zaps to my tor LN node are now finally enabled
I tried to set up zaps without success 8 months ago. My LN Address worked but nostr clients didn't recognise that the payment had been made. Thanks to @npub1y24gz5gwucl79vtv4ctwpysl0r5m4xyzu2rgulnr44ks3t5mt92q4nz2ad this is now easy for btcpayserver users
1. Exposed your BTCPayServer publicly (guide here https://orange.surf/public-btcpay-umbrel-tailscale/)
2. Create a lightning address in BTCPayServer
3. Install the nostr BTCPayServer extension, enter the same name and your Nostr PubKey and PrivKey
Zaps will now work.
Thank you for verifying, you are correct, I made a typo in the post. The chart and delta are correct, but the max value is 7.30606132 BTC (-0.43183364)
jpeg transaction creators would just submit the transactions directly to the mining pools, bypassing the mempools of the nodes which reject.
Miners determine which of the valid transactions in their mempool are selected for inclusion in a block.
Aside from the need for transactions to be valid, there are no consensus rules around transaction selection, miners are able to use whatever selection method they wish.
So how do block templates compare? Let's examine what happened prior to block 821498 (mined within the last hour).
The block mined by Antpool had a max total bid of 7.73789496 BTC. You can find this using bitcoin-cli getblockstats
My local instance of bitcoin core running the default policy rules + FullRBF had a max total bid of 7.71806816 BTC, lower than the mined block by 0.01982680 BTC.
The block templates provided by nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3
had a max total bid of 7.7334687 BTC, lower than the mined block by 0.00442626 BTC.
The block template provided by ocean npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze
had a max total bid of 6.6127135 BTC, lower than the mined block by 0.43183364 BTC
Filtering policy and sorting method vary by pool, but mining is highly competitive. For how long can mining pools who do not maximise fee revenue survive?
The rate of my data logging (every few seconds) means it's inevitable that I don't capture the latest templates, so that accounts for a small part of the delta. You can see on the mempool block audit page that the expected mempool space template for the mempool block is 7.737 BTC , slightly higher than the 7.7335 BTC template I captured.
An additional source of the delta is that there were some transactions (in blue) which AntPool included which were not in
@mempool
's mempool and likely not in mine or oceans (I didn't save the block template so can't check).
These 6 transactions pay a total of 4,072,619 sats in fees. Plus there is a transaction that was included which had a marginal fee rate, paying a 73,828 sats.
A total of 4,146,447 sats
To create space to include these transactions 45 transactions were dropped, each paying 89,833 sats.
A total of 4,042,485 sats
Including these transactions resulted in a net increase for the in band fees of 103,962 sats (0.00103962 BTC)
Check the block audit at https://mempool.space/block/000000000000000000028bdf4456e7e2519b0ba4b6d52cea0cc18c726f60a578
A small sample of 20 recent blocks
In blue - The predicted proportion of transactions that conform with BIP69 (based on transaction input and output counts in blocks)
In green - The extra proportion required to match what is measured. Average 11.6% (min 7.2 exc 0, max 14.8)
https://pbs.twimg.com/media/F9o-unXXEAAe5Cu?format=jpg&name=large
?w=900the nostr, what are you grooving to?
nostr dm's are a mistake should be hidden until a method of hiding the metadata is deployed
nostr:note1mjnzf542v8rxsxmkjmzqz0m739jp6xk7tq9l0efkfs7pszdj9jsse4km82
nostr:npub1chxa2um7gl65ymyaagjrqys39mtzlwnm2drcs6qkqmme7k4edq4qghrjdd is testnet mode within SBW on the roadmap? It would be very useful when teaching new bitcoiners.
In Riga - Hit me up
Anyone else struggle to find interesting content on nostr?
Which nostr clients have filters that prioritise showing content of quality?