I now understand why AI will eat the software industry.
I used to have a web agency.
With Claude over the last 3 days I have built and deployed a system that would have:
- Taken 6 months
- Cost £150-200k
- Required 8 different skill sets
I can't design. I can't code. I don't understand SQL, APIs, Cloud Storage - yet Claude has walked me through Github, Supabase, Vercel and it is deployed and working.
A 100% custom software system - 3 days, 1 idiot.
BLOWN AWAY!
@_PyBlock_@ckpooldev I’m in the process of moving home, new place is being renovated, should hopefully be finished this month and then I can move in set up my stuff again.
If everything is fine, then don’t change anything at all.
But when the financial system isn’t working for so many people in the UK, it needs to be updated.
Adding a nerdQaxe++ to the fleet, I want to say that’s it now but we all know it’d be BS.
Chip wise I’m happy, mining with ultras, supras and Gammas. Get yours here:
https://t.co/E7Z4DnLi3O
@BitronicsStore My smart fridge locked me out, toaster demanded sats, and even the Roomba started mining Doge. I snapped. Slapped a NeedqAxe++ miner on the shelf. Now I mine BTC, the appliances fear me, and the dog pays me in sats. Dominance restored.
🎉 GIVEAWAY TIME! 🎉
To celebrate the launch of the Nerdqaxe++ 4.8TH on May 26th, we’re giving one away — absolutely FREE!
🚀 One lucky winner will receive:
🟠 1 Nerdqaxe++ 4.8TH/s
🟠 Custom stand color of your choice
🟠 Power supply included — plug and mine!
🟠 5 reflective #Bitaxe stickers to flex your setup
✅ How to enter:
Follow @BitronicsStore on X
Like this post
Repost it
Comment why you need a home miner in your life
🎯 Winner will be announced next week! Don’t miss your shot — good luck! 🍀
At @River we will continue to run Bitcoin Core because it is the only properly maintained Bitcoin node software. The Bitcoin Core dev team is highly competent and dedicated to the long-term success of the network. The current state of the debate around OP_RETURN relay rules is the result of overdramatizing a nuanced technical decision regarding tx standardness rules. Running poorly maintained forks of Bitcoin (with their own large flaws) because of this minor technical debate is an overreaction IMO.
No Bitcoin Core dev wants the blockchain spammed with data because they are the ones forced to deal with the scaling issues and edge cases that follow. However, the reality today is that consensus rules allow transactions with large amounts of data in OP_RETURN, regardless of mempool policy! So, the broader debate here is twofold:
1. People want to put data onchain and they will do so with or without OP_RETURN limits. There is nothing stopping these people from skipping the mempool and submitting nonstandard txs directly to a mining pool today, or using even uglier approaches that bloat the UTXO set (even worse for the network). If we want to actually “fix” this, we would need a consensus fork, not a mempool rule change. The decision to change the standardness rules to allow these txs to be relayed seems reasonable and not a big deal.
2. The divergence between standardness rules and consensus rules: There are many transactions one could make that are valid by consensus rules that cannot be broadcast to the network today because they are “nonstandard”. This does not stop a miner from including the transactions in a block. High divergence between standardness rules and consensus rules leads to complexity in the Bitcoin Core software and causes problems for block relay efficiency when people start sending non-standard transactions direct to miners. Starting to move away from this divergence seems reasonable, but needs to be done carefully. We can likely never fully delete standardness rules but I understand the goal to reduce complexity here.
This debate should remain objective and technical. It’s being blown way out of proportion. Remember, the vast majority of Bitcoin Core devs deeply care about the long-term health of Bitcoin and have dedicated their careers to getting Bitcoin where it is today.