average_bitcoiner on Nostr: I wanted to give an overview of the recent Chaincode Dialogues. It was a Chatham ...

I wanted to give an overview of the recent Chaincode Dialogues. It was a Chatham house style event with open-source projects maintainers and bitcoin industry professionals.

All comments and notes are mine own. Other attendees perspectives likely vary.

The event started with 15min “lightning talks”. Participants rotated between four topics total with SMEs at each. We broke for topical 1:1 before lunch and finished with 45min discussions at the end.

Lightning talk topics:
Bitcoin payments regulatory landscape - I attended this one and it seemed like a shill for meta protocols being developed for payments that fit nicely into existing structures. The premise was two parties want to conduct payments between them, so let’s have a common protocol for how to handle this. This would create an opt-in network of participating institutions. Think ACH/FedWire/etc. but for bitcoin. My takeaway was lawyers and regulators are trying to fit bitcoin into existing paradigms but fundamentally miss the point of p2p monies. IMHO, meta-protocols are best enforced by code but the discussion seemed geared toward existing governance models that fall short since we’re all fallible humans.

Covenants - General discussion around what a covenant is. The main added functionality of a covenant op_code(s) would be transaction additional introspection and programmability. op_codes are expressions within the smart contracting language of Bitcoin script. The most basic form being a digital signature for a pubkey that signs some aspect of the spending UTXO. Covenant proposals ranges from opinionated (OP_VAULT which defines a very specific construct and use case) to less opinionated “state-machine-like” op_codes (OP_CheckTemplateVerify (CTV) or OP_CheckContractVerify (CCV) or OP_TxHash) to fully generic scripting upgrades (Simplicity which enables a small number of primitives that can be used to recreate almost any spending condition. There’s a lot more to Simplicity outside the scope of this discussion but happy to elaborate more). One of the benefits of covenants is reducing interactivity. A lot of protocols or spending conditions make use of pre-signed bitcoin transactions and covenant op_codes remove the need for pre-signed transactions by moving the evaluation logic to bitcoin script. One of my personal interests is with OP_CTV which has documented use case examples at https://utxos.org.

OP_RETURN debate - I did not attend this as I am well versed on the subject already. Please let me know if you have any questions.

Core Devs - I attended this one. It was a discussion about goals of Core Developers and Q&A about repository and project maintenance/management. Nothing of note from this talk but I am happy to field additional questions.

Great Consensus Cleanup soft-fork - Arguably the least-contentious soft fork being proposed as it addresses some vulnerabilities within bitcoin consensus. There are four issues it aims to address:
    1 - Timewarp attack (manipulating the difficulty to accelerate blocks) - This has to do with the buffer and timing between difficulty adjustments.
    2 - SlowBlock validation (transactions that create super slow block validation, possibly slowing block validation to minutes, demo’d at OpNext this year by PortlandHodl) - this is easily detectable for bare script version, but Pay2ScriptHash can conceal a setup for this attack. This invalidation would be confiscatory for attacker’s transactions since it could render them invalid, a desired outcome.
    3 - 64 byte transactions invalidation (since we use Merkel trees with nodes that are 64 bytes, a 64byte transaction can be problematic and malicious for users) - This is defensible by application developers but the goal would be removing the need for application developers to address this by enforcing it within consensus rules.
    4 - Unique transaction id (ensuring unique ids (hash) for transactions to include coin bases (BIP34/BIP66/BIP65 related)

Quantum - I did not attend this but some present were skeptical of the immediate need for such changes but still interested in the proposals/discussion. "Fear of Quantum is worse than Quantum itself." Anecdotally, I’ve heard from others that one of the proposals would be generally desirable even if the Quantum threat remains just a threat.

45min topics:
LN + Payments tech - I did not attend

Blockchain Regulatory Certainty Act (BRCA) + Political landscape - https://saveourwallets.org - I did not attend but am familiar with the BRCA and implications it has for protecting developers of free and open source projects that enable the bitcoin industry

Softforks history - I attended this one to understand previous soft fork history and the activations methods used. Was an excellent discussion with someone who was present for the history itself.

5 Things Scarier than Quantum - I did not attend this talk

Mining Centralization - I did not attend but was happy to see this discussion well attended. Hashrate marketplaces, pool payout schemas and more were discussed and well received from my discussions with the moderator.

The event wrapped with a round table discussion about Bitcoin’s success/failure and what it looks like to those in attendance. We discussed difficulties in communication of technical changes and risks of regulatory landscapes as it applies to developers. A fun anecdote was a mention of mining on Mars.

Please reach out if you would like deeper discussion about any of the topics presented. If I do not have the answers, I know who to reach out to for the answers and would be happy to facilitate.

This was an excellent event, and I hope more Dialogue events will be considered for in-person discussions that cannot be replicated online.