Active Discussions

Bitcoin Core's standardness rules aim to mitigate DoS attacks, enable upgrades, and discourage data storage.

The Citrea bridge utilizes Taproot outputs to embed data, circumventing OP_RETURN output limits.

Proposals exist to remove OP_RETURN restrictions to prevent endorsing less desirable data storage practices.

Testnet4's difficulty reset rule, intended to ease development, has perpetuated significant issues.

A proposed flag day hard fork on January 1, 2026, aims to remove this rule for improvement.

The change seeks a balance between simulating Bitcoin's mainnet and facilitating developer testing.

SwiftSync facilitates near-stateless, parallel Bitcoin blockchain validation using hints for unspent outputs.

It improves validation efficiency by eschewing a constant UTXO set, aiming for a zero total hash aggregate.

The protocol speeds up processing, especially on limited RAM devices, and seeks feedback on its comprehensive analysis.

Covenants in Bitcoin protocol enhance transaction control and security through spend conditionality.

They enable innovative financial instruments and complex smart contracts within the ecosystem.

A dedicated wiki page provides comprehensive details on covenants' technical and application aspects.

The `OP_INOUT_AMOUNT` proposal aims to enhance Bitcoin Script with input and output stack functionality.

It explores integrating with a 64bit op code and seeks community feedback on its design considerations.

Modifications include new methods in `BaseTransactionSignatureChecker` to support these functionalities.

The write-up analyzes `assumevalid` in SwiftSync, enhancing system efficiency by skipping some block verifications.

It discusses safeguarding against inflation despite omitting certain validations, ensuring monetary policy integrity.

SwiftSync's methods for parallel transaction order validation and innovative BIP30 check are explored for better scalability.