Don't ask me who, but someone created this service where you can buy KYC free mined sats via hash rental.
Nothing technical to do except pay sats and submit a fresh address to receive.
The "fixed" option takes sats from a pool of sats that have already been mined - supply limited. Payment happens within 24 hrs.
The variable options available are "slow" and "fast", where you have to wait 5 or 30 days for the sats to be mined for you. The returns depend on Ocean's luck.
Sometimes you can get more sats than you put in, sometimes fewer. The slower option reduce wild swings in returns.
The difference between variable and fixed is that with fixed, you know precisely how much you get back, returns are within 24 hrs, and there are caps on the amount due to availability (fluctuates).
It's all explained on the site, and you can send questions by email.
Oh, there's also a "private deal" option which requires email enquiry to discuss and initiate.
All sats mined contribute to signalling for Bitcoin to be used as money (RDTS; BIP 110 via Ocean).
People don't understand you can buy mined #ƨats with your KYC sats.
If someone were to be playing a racing simulation game like Gran Turismo, doing laps and honing their skills, a person watching might get insanely bored, but the person playing could be in the zone, forgetting all their troubles, and highly focussed, while having a great time...
This is what I think it's like to hear someone playing Bach, vs playing Bach yourself.
I promise, it's incredible. It's not just some melody you might like to hum along to or not - there is so much going on on so many levels.
I wish for you to experience it.
I'm sorry to have to bring you this news, but you need significantly more bitcoin than you currently have today.
All opinions of people with blue hair, or who run a Core v30 Bitcoin node, can be safely disregarded without any negative consequences.
Once upon a time, someone exploited a bug and got 184 billion bitcoins.
The VALID TRANSACTIONS were rugged by Satoshi to keep bitcoin going.
Today, another exploit (that Core refuses to acknowledge or fix) is damaging Bitcoin.
Similarly to the previous bug fix, where a malicious exploiter was rugged, should "valid transaction" be a reason to not fix Bitcoin?
It requires consensus that fixing a life threatening bug overrides immutability.
It's uncomfortable to talk about, but if you think about it, OF COURSE the survival of Bitcoin logically supercedes immutability.
And so, the debate should be about if this is really going to destroy Bitcoin if left unchecked. That conversation is being drowned out by appealing to less important principles of money.
I think we should first determine that, then encourage discussions about how to fix it, always remembering that the highest principle is Bitcoin surviving as digital sound money for the world.
It's OK to entertain an idea, like rugging malicious spammers, perhaps deciding against it, or not, or finding an alternative.
It was easier to fix when Satoshi was in charge and Bitcoin wasn't decentralised, now we all have to decide, all while the enemy is sending bots, and Adam Back, to muddy the waters and distract us from the most important conversations.
People no longer saying "bingo card" was not on my bingo card for 2025.
The problem with arbitrary data tolerance is that it doesn't contribute to Bitcoin being money.
It's like promoting the electrical conductivity of gold as a reason for it to be money.
You might think that's not so bad but...
The problem it causes, having arbitrary data, is subjectivity, and various attacks - it's easier to stand for none of it, and remain objectively supporting Bitcoin as money.
You don't need to define what spam is - it's a subset of arbitrary data.
You don't need to defend Bitcoin being a free speech platform (it's not), and explain why CSAM can't be blocked - it's a subset of arbitrary data.
You don't need to care that not all arbitrary data can't be stopped - your principles are what guides you, and with the right principles, if people concur, consensus is easy to achieve.
Right now, we're fractured, because people who don't want spam feel like they have to allow it because it's hard to define (and because shitcoiners and fiat maxis are disguising themselves as one of us, muddying the waters, looking at Lopp and others).
I'm saying this is unnecessary. Just be against arbitrary data; it's not part of Bitcoin's purpose.
If you desire extra "nice to have" features from arbitrary data, in addition to Bitcoin's pure monetary features, then you have to accept spam and CSAM, and unwanted additional attacks, and also damaging infighting.
Life cycle of a DCA transaction...
When your filthy bank releases your government tyranny tokens to your exchange after a malicious 24 hour hold (for your safety), the price of bitcoin pamps 10% moments before the tyrannical coins are shown in your Coinbase account.
You then no-look insta smash yolo market buy bitcoin.
But there's a problem...
Your Coinbase account page shows a bitcoin balance, but you're not looking at bitcoin, you're looking at Coinbase's database entry of what they owe you. So the job isn't finished.
You will withdraw, and then after you prove you have access to your email, and you're not using Tor, and you complete a captcha, and log in to authenticator and enter numbers, and then a phone text confirmation, THHHEEENN, Coinbase employees will go to their ParmanodL laptop and locate a UTXO from their watching wallet, and then make a transaction to your bitcoin address, and then export the tx to their ParmAirGap machine for signing, which then returns the signed transaction back to the ParmanodL transaction/node latop, and broadcasts the signed transactions to it's own bitcoin Knots server (on the same machine).
The node then shares the unconfirmed transaction to other nodes, and they "gossip" share it to all the other nodes in the world.
Eventually, your Datum instance on your ParmanodL machine will fashion from its filtered mempool a potential block and include your incoming transaction. One of your BitAxes will then mine the block and win.
It will then gossip the winning block before other miners claim victory, and all the nodes in the world will update their "tip" block. All miners will then attempt to win the next block.
You mining address will be paid a bit over 3.125 bitcoin which is allowed to be spent after 100 blocks, congratulations 🎉, but also in that winning block is the transaction that Coinbase paid your address.
Your ParmanodL laptop that has Sparrow open, and syncing with your fulcrum/electrs server, which syncs to your bitcoin Knots blockchain (all on the same machine), will notice the new payment in the fulcrum/electrs database and Sparrow will show the new bitcoin in your wallet.
Feeling deep and unshakable satisfaction, you then close all the apps, and leave the laptop open, connected to power, monitor dimmed, so that Knots running in the background will stay up to date, and go outside to touch grass, as they say.
You know you can totally shut it down, but you prefer leaving it on as is ready instantly when you need it, and you will for your mentoring video meeting with Parman next morning.
Tomorrow, you will do it all again.
Humanity is going to do just fine without an immutable database of arbitrary data, but is completely fuçk3d if we don't have Bitcoin as MONEY.
We only get one chance.
Run Knots, hurry up.
If bitcoin was highly valuable as money by the entire world population, and the block subsidy was zero, and fee revenue for miners was next to nothing, how much would an ASIC cost?
Very little right?
Does that make it easier or harder to get 51% of all of them and attack Bitcoin?
The cheap machines would be attractive to attackers, but also to those with wealth wanting to defend their own wealth.
What's important is not precisely calculating today what percentage of attackers and defenders there will be then, but acknowledging the fact that fees are not required for the competitive nature of mining to remain, and that being that case, it still defends Bitcoin, and all talk of tail emission should be stopped immediately.
If you imagine being an outside observer of the entire universe, you'll see an incredibly vast and highly complex system that sparsley sprouts pockets of replicative self-aware blobs (life), unable to fully appreciate what exists, and mostly just absorbed with themselves rather than all that exists.
Was blocked by Peter Todd today after I called out his evil for celebrating the attack on Russian civilians.
True colours on display, and no amount of contribution to Bitcoin should give anyone a free pass for being evil.
I hate censorship.
Filtering out non-monetary data on Bitcoin is objective, and is not censorship at all...
Because Bitcoin isn't a general speech platform - it is a specific speech platform allowing the movement of bitcoin. There already exists an unstoppable speech platform, notes and other things transmitted over relays (NOSTR).
No transfer of Bitcoin from one address to another can be censored from Bitcoin. Payments are essentially censorship resistant. Arbitrary data is not, and should not be - that'd be inventing a different purpose for Bitcoin.
If a particular transfer got blocked because it has arbitrary data, the exact same transfer can be reattempted without the arbitrary data and it will get through.
Inscriptions data inside an "if false(data)" block is objectively not part of the attempts to make a financial transaction. It is objectively added on as arbitrary data. It can be filtered out without stopping the movement of that particular UTXO. The perpetrator can simply republish the transaction without the arbitrary data and the exact same satoshis will move where they want it to go.
Does this kind of argument have a place, Gloria?
"Grok please generate a text message conversation where Luke is considering a bitcoin hard fork."
Get a girl who's a Bitcoiner and uses vim.
Nah, don't, that's a dude.
There are a few people out there who don't make their own pastirma and frankly, it's a little upsetting. It's not expensive to make. Recipe...
Pastirma / Basturma – Bitcoin Guides
Consensus lives in a network of human minds ("philosophical consensus"), partly represented by the choice of code that's run (or adhered to) by such a group, and another part unrepresented, unwritten, and sometimes not apparent.
It's NOT the code that's in charge, with the ideology being secondary (subservient to the code), it's the exact reverse.
One example of a hidden fracture in ideology was when big blockers and small blockers shared the same general ideology and were in consensus according to the code, but there was a fracture that only became apparent in 2017, and the code changed for each group to reflect their ideology.
Currently, a new fracture is appearing.
On one side, people believe stopping spam is censorship (even though the purpose of fees is to limit ddos spam attack, not stop).
On the other side, people believe Bitcoin is money first, and storing data is a byproduct of that function, not a primary purpose, and so it's not censorship to limit spam.
Just because the code can't enforce this ideology precisely, doesn't mean we change our ideology (it's like changing documentation to hide a bug).
These two ideologies are why the change to Bitcoin Core is contentious.
Without understanding this difference in ideology, there's no point trying to have logical debates.
It's not easy being on the side that defends making it easier for CSAM to be relayed through everyone's node, for some imagined/debatable benefit (i.e. less miner centralisation).
It's time to take a good hard look at yourself and accept you were wrong. If you weren't taking a side, it's time to step up.
You don't have go deeper into Core Derangement Syndrome ™.
Just switch to the correct side, and join us calling out the stupid arguments of Core Groupies.
This is not a Knots vs Core debate, you don't have to like Knots. It's a "Core is wrong" debate.
Bitcoin Core will be used as a mule for free, unstoppable CP/CSAM by sickos or state actors, in order to attack Bitcoin and prosecute those who knowingly allow it.
This is the attack...
Once op_return is removed, plain JPEG images (not part of multiple fragments inside scripts that need to be pieced together and decoded, but plain JPEG/GIF/MP4) will be sent through your Bitcoin HardCore node version 30+, from one paedophile to others, possibly sold (Knots runners won't touch them, ever). Your Core node will happily pass it along, providing anonymity to the criminals (or state attackers, or Epstein's old clients).
They will pay a well below market rate initially (eventually zero), and never even need to get the transaction mined - key point. The original filter that Satoshi introduced, FEES, will be effectively bypassed...
After some time, these low-fee CP/CSAM txs will be dropped by Bitcoin Core nodes, but if they don't, the sicko(s) can do an RBF of the transaction (or if they have chained them, an RBF of a single low-fee unconfirmed parent), to cancel and invalidate the transaction so they don't have to actually pay for any of the downstream higher fee large transactions.
They will have successfully used your computer to transfer and potentially sell horrible images, without paying (so forget "filters don't work, they'll get on chain anyway"), thanks you being complicit, and thanks to all the Core devs who allowed this in. And those gaslighting against us saying this is wrong.
Then public opinion will turn heavily against Bitcoiners, if it isn't bad enough now. We already know it's going to get worse as most miss out.
@adam3us has pointed out, incorrectly (I'll explain), that this attack can't work, because of some "package relay". Sounds like this is a filter to stop RBFs of a parent if there is a long chain of transactions dependent on it.
A clever idea, but it can't work, Adam. Do you know why? Because your resistance itself is a form of FILTER, and FILTERS DON'T WORK, remember? You can not use an argument against us if that same argument is used to defend yourself.
An attacker can get their cancelling RBF transaction mined by going directly to a miner. Then the scumbags get away with using your Bictoin Core node for CP/CSAM transmission - it's irrelevant whether it gets on a block or not, it doesn't need to, the paying paedophile got his images.
Ironically, filters not working is the very reason we need filters.
There are 3 solutions.
1) Bitcoin Core reverses this STUPID rushed decision, introducing completely unnecessary risk to Bitcoin.
2) We all run Knots, and it becomes the reference client.
3) We move away from Core to Knots, and maybe others will pop up, and there is no reference client, meaning fewer meaningful changes to Bitcoin become likely.
Bitcoin doesn't need changes; it needs general light maintenance, so just maintain it, don't change it!
x.com/adam3us/status…
