"What do prostitutes, blackmailers, slumlords, and Bitcoin miners who censor transactions all have in common? ...They are heroes of the free market."
https://bitcoinmagazine.com/markets/defending-the-undefendable-the-censoring-miner
Ledger Live Tracks and Sends ALL User Information to Outsourced Data Harvesting Service
"The tracking code is too structural to be just counting users and downloads, like regular apps do. Ledger Live is doing analytics on everything from screen views, to button clicks, error events, installs, uninstalls, etc. It's basically tracking everything. Anything you do on that app gets tracked."
https://www.nobsbitcoin.com/ledger-live-tracks-and-sends-out-all-user-information-by-default/
Don't use Ledger if you can avoid it. Every bit of news about these guys is worst than the last.
If you do own a Ledger or know someone who does, and aren't in a position to get a better device, at least set it up in the best way possible, avoiding Ledger live.
There is a great article by arman the parman that walks you through this process. You only use Ledger live initially to download the Bitcoin app, then you never touch it again. Then you set up a fresh Bitcoin wallet offline and connect to sparrow wallet.
Yes. More pools! We need more options that offer privacy, decentralization-forcing incentives/protocols like SV2, fair/transparent payouts. I'd love to see this built in a way that also works for pleb miners heating at home where miners aren't on all the time. This has potential to be a huge market in the future and could represent a large portion of hashrate. Glad to see this conversation gaining traction.
The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam. At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier). Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive. There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it.
It is not my intention, nor that of my team at
nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze, to filter coinjoins. These present an innovative tool for increasing Bitcoin’s privacy and, when constructed properly, coinjoins can easily stay within the OP_RETURN limit (indeed, there is no reason for them to have *any* OP_RETURN data at all). I have some ideas on how to alleviate the recent issue where some coinjoin transactions were flagged as spam from Knots v25, and I am willing, with the full resources of my team, to work collaboratively on a solution in good faith.
Bitcoin does and always has allowed nodes to set filters based on multiple sets of criteria and Knots v25’s defaults are IMO what is best for Bitcoin at this time. Others may disagree and that is ok. They are free to (and should) run their own nodes - it is good for Bitcoin to have more people running nodes, including miners, and there should be a natural diversity in node policies. As was stated before, OCEAN is on a path to decentralization and very soon we are going to be in a position where hashers will be able to fully participate as miners and perform the intelligent parts of mining such as deciding which version of node software to run and what filters or other policies to apply to block template construction.
Discussion is good. Glad to see it.
True use case for it is criminals, drug traffickers, anti-money laundering and tax avoidance. Break it down.
https://video.nostr.build/fab89f588fc617fbb7e0ee36901491edc9c281530602e85f6fcbb905b275bda6.mp4
Turn it up!
😂
Literally everything these people say is a projection of their own criminality.
As seen in nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze's second block found, the coinbase generated subsidy and fees were awarded directly to miners who met the threshhold for immediate payment. My understanding is that these coins still have to wait 100 confirmations before they can be spent.
This is different from how Braiins would distribute their coins, as all coinbase rewards would go to one address, and then payments would be made based on payout settings configured by individual miners.
Once lightning payments are enabled, this will further reduce nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze's custody of coins to almost zero. With stratum v2 implementation, block templates will be created by individual miners, who can decide for themselves which transactions will be included in a block. Stratum v2 also improves the network in many other ways, including encrypted communications by default. This all adds up to positive steps forward for #Bitcoin mining.
Shout-out to Braiins for all the work they've done in the space since the early days, including creating stratum v2.
Malaysian flight MH-370 solved? You decide. Fascinating times we live in.
cc nostr:npub1a3hrd4wfawr578d5y5l0qgmh7lx8q6tumfq0h7eymmttt52veexqkcfg37 based on your conversation with Matt Pines, you may find this interesting.
It's still very lucky. We should only be finding one block every 10 days, so getting two this quick is very lucky. But that's randomness!
Current hashrate on mempool.space is 455,300 PH/s (455.3 EH/s). Compare that to current hashrate on Ocean (314.3 PH/s). That represents about 0.069% of total hashrate which translates into the pool finding a block on average every 10 days. You are correct, this is very lucky, but not out of the realm of possibility.
It's 1000 PH/s = 1EH/s, not 10,000.
Sounds like the perfect Christmas gift!
The mining situation is discouraging right now. Braiins moving to FPPS, and Ocean falling well short of expectations. Seems like there's no place to go for plebs who actually care about Bitcoin.