User:
qbtc-coreAdditional information (optional):
* I suspect this user spam with AI/chatbot.
List of post:
The table is outdated and missing some alternatives... but it's enough to show there's no single "best" choice.
Pick a scheme even if it is inefficient, and do a large block size increase. This will lead to a severe and negative impact on decentralization.
You guys are touching on the real elephant in the room, but most of the community is still completely missing the actual bottleneck: TCP transport buffers and mempool serialization.
Everyone stares at the 3.3 KB size of ML-DSA-65 (Dilithium) and argues about on-chain storage or block limits. But if you try to forcefully soft-fork a 3KB+ signature into the legacy Bitcoin Core architecture, the nodes will literally choke during transaction relay before a block is even mined.
BIP-360 (P2MR) is just a band-aid. Sure, it hides the pubkey, but the moment you actually spend that UTXO, you are still slamming the mempool with a massive PQ signature.
Satofan44 is absolutely right: blindly increasing the block size to accommodate PQC will completely wreck node decentralization. On the flip side, waiting around for some "magical, tiny PQC math" is just gambling against quantum hardware advancements.
The only mathematically sound way out is a ground-up architectural rewrite. I'm talking about a native base-layer Commit-Reveal mempool isolation. A true PQ-SegWit architecture that entirely decouples raw cryptographic proofs from state storage. And you have to rip out and expand the default P2P Yamux/TCP buffers right at the consensus layer.
I've been testing this exact architecture natively on a Layer-1 PoW network (enforcing ML-DSA-65 at consensus). The sheer verification overhead of lattice-based cryptography actually solves another problem by accident: it naturally bricks legacy ASICs and forces a return to bare-metal CPU mining.
Soft-forking PQC into legacy Bitcoin is an engineering nightmare. The true quantum transition will inevitably require a parallel genesis.
1. There's no explanation why TX that use 3KB signature would "choke" TX relay. After all, node have no real problem/issue when relaying TX with few KB size (such as ordinal TX with arbitrary data).
2. Changing signature cryptography (from ECDSA to QC resistant else) alone wouldn't break today's Bitcoin mining.
3. I downloaded Bitcoin Core source by git clone
https://github.com/bitcoin/bitcoin. But there's mention of text "yamux" at all on the Bitcoin Core source code. So claim Bitcoin or Bitcoin Core P2P Yamix is wrong.
User:
Mario0Additional information (optional):
* Additional information 1
List of post:
Claude can only be useful to check the code and find some hidden bugs and flaws in the code.
Someone already used this tool to exploit some shitcoins, and I am sure hackers are using it steal coins from exchanges.
But totally replacing any human bitcoin developer with Claude or any other AI would be stupid and dangerous.
I don't think Claude can be utilized for the things you are saying since, as soon as they are added, you will receive a response from Claude because it might negatively impact the AI's reputation, and I'm confident that Claude won't be involved in anything that would lead to criminal activity. And from what I understand, developers can benefit from it, but not in the way you truly believe.
False claim. Claude actually used to find security vulnerabilities on altcoin when used by actual security expert. See
https://www.schneier.com/blog/archives/2026/06/critical-zcash-vulnerability-found-and-fixed.htmlCertain Crypto Currencies are claiming to have them already. When Bitcoin?
Since Bitcoin does not yet have a quantum-secure address, it is clear that it does not require it at this time, and the quantum's that are available now are not yet powerful enough to break Bitcoin's encryption, and if it becomes so, I am confident that the developers will make an upgrade, because, and since awareness is everywhere, I do not believe things like this will be ignored. And other new cryptocurrencies are built with different cryptography when it becomes a concern, then it will not be ignored, that I know for sure.
1. While Bitcoin currently have no QC-resistant address, BIP 360 already created as foundation for such address.
2. Bitcoin does not use encryption cryptography.
User:
ROCtermAdditional information (optional): -
List of post:
It's crazy how self hosted nodes are hitting more blocks than those of the public.
Is there something that we all need to learn from this?
Smart miners in the house, what is should we take from this?
https://bitcointalk.org/index.php?topic=5583890.msg66758428#msg66758428 explain problem with this thread.
You can't get that type of lottery from asic miners, if your asic says 3500watts, its definitely going to take 3500watts, unless the miner have a way that you can down clock its hashrate that will reduce the power consumption.
If you are looking for a way to get away with Bitcoin mining because of power consumption you can start with small home miners, I know one that takes 1500watts I forget the name, there are few others too with lower power consumption, you just need to find them.
https://bitcointalk.org/index.php?topic=5581449.msg66668902#msg66668902 explain problem with this reply.
User:
KhaleedmaineAdditional information (optional):
* This account suspected to spam with AI/chatbot,
https://bitcointalk.org/index.php?topic=5456516.msg66922858#msg66922858.
List of post:
Another generic reply. Company (such as exchange) and people already use Bitcoin today to send or settle big amount of Bitcoin, some of them even do that during past congestion.
User:
WakeUpToCryptoAdditional information (optional):
*
https://bpip.org/Profile?p=MrEazyLife shows 65/335 (19.4% post) deleted by moderator.
List of post:
Generic or unhelpful reply.
User:
iooijingAdditional information (optional): -
List of post:
The full thread have about 43822 characters and probably generated with AI/chatbot. I only skimmed it, but there are misleading statement.
1. "Mining revenue per kilowatt-hour, by contrast, moves directly with Bitcoin's price and network difficulty". This is misleading, because ASIC efficiency and other operational cost are also other factor of mining revenue.
Therefore, expanding the block is like increasing the Bitcoin limit of 21 million, and segwit removing the signature data is like buying half of the goods.
For full context, visit his thread.
1. Increasing block size isn't equal or similar with increasing Bitcoin total supply.
2. SegWit doesn't remove signature data. SegWit actually change TX structure.
User:
CryptoTroubleshooterAdditional information (optional):
* This user claim they bring high quality technical content,
https://bitcointalk.org/index.php?topic=5355092.msg66425563#msg66425563. But most of his posts appear to be only generic or acceptable quality.
List of post:
Simply unhelpful/spam reply.