News
Entertainment
Science & Technology
Life
Culture & Art
Hobbies
News
Entertainment
Science & Technology
Culture & Art
Hobbies
A concern brought up in the context of block content diverging from the default mempool policy is the reduced compact block reconstruction rates. In this context, I have seen the extra pool brought...
As far as I know Bitcoin Core obfuscates both block/undo data and level DB indexes with XOR. Where are those randomly generated keys actually stored? Is it self contained within the DB directories?
I'm trying to understand Bitcoin's consensus rules regarding empty scriptPubKey fields in transaction outputs. I've found conflicting information: Some AI sources claim that empty scriptPubKey fie...
How can I always have a second copy of my Bitcoin Core data (blocks, indexes, chain state) on an external drive? The drive will only be connected to the node at times when it's not connected to sep...
One justification for removing the OP_RETURN policy limit is that arbitrary data is “unstoppable” and will always find its way onto the blockchain. At the same time, not all data vectors have the s...
Bitcoin originally limited OP_RETURN outputs to 80 bytes to discourage arbitrary data storage and keep the chain focused on monetary use. Recently this cap was removed, with the argument that some
OP_RETURN outputs are provably unspendable, so they don’t add to the UTXO set. This is sometimes used to argue that uncapping OP_RETURN is “safe.” But the raw payloads are still committed to the
Bitcoin Core v30 will for the first time allow transactions into the default mempool with more than one OP_RETURN output. The datacarriersize= setting is being repurposed so that numeric limits now...
With Bitcoin Core v30 removing the 80-byte OP_RETURN relay cap, transactions with very large OP_RETURN payloads can now propagate by default, up to block weight limits. In a stress-test context, I’...
In v30, default relay policy allows OP_RETURN outputs up to consensus limits. OP_RETURN outputs are provably unspendable (so they don’t grow the UTXO set), but they still consume block weight/size ...
Bitcoin Core v30 removes the long-standing 80-byte OP_RETURN cap, raising the default to the full consensus limit (~4 MB) while deprecating -datacarriersize. Proponents argue that OP_RETURN restric...
As you may know, there has been a debate around the upcoming release of Bitcoin Core. I hear the arguments against it and I agree that Bitcoin is money, not a storing database, and strictly only mo...
Why are OP_RETURN transactions discouraged? Are they paying less fees compared to other transactions? Will it make any difference if same thing is done using version or locktime when data is either...
One of the reasons given for raising the OP_RETURN default in v30 is that restrictions are ineffective: miners and users can bypass relay policy anyway. But allowing megabytes of arbitrary OP_RETUR...
I want to include some random (for me it is not really random 🙂) data when unlocking an UTXO. I would like to keep the spending secured by a classic signature. At first, I thought about using P2WP...
Main question (focus on this incase you are looking to close it as "needs focus"): Why can't we change default minimum fee rate to something below 1 sat/vByte? It was done in past: https://
So I initiated a withdrawal from BetOnline (casino/poker platform) and withdrew it to my cash app wallet. I have done this hundreds of times between the two and have never had an issue before. I se...