Sjors Provoost's avatar
Sjors Provoost sjors@sprovoost.nl 8 months ago
Maintaining such a patch is probably a couple of days work per year, assuming a worst case scenario of the patch being hard to maintain. Maybe half a day if you can cherry-pick it out of Knots. This is a much lower bar than having to maintain a custom Bitcoin Core fork for consensus changes. Don't be shy.
↑ Parent

Replies (3)

Default avatar
npub18w5m...8w27 8 months ago
Citrea publishes some whitepaper(!), for a bridge that would benefit from relaxed OP_RETURN limits. Immediately everybody at Core: "yeah let's DROP the limits - they're useless anyway. LFG 🚀" All the while other major changes (e.g. CTV) there's years of filibuster: Where is your signet implementation? Where is your documented user demand? Where is the documented consensus? etc etc etc [Ironically, something like CTV would have done away with the interactive presigning ceremonies that particularly hinder 2way pegs such as said Citrea's bridge] You see the point why people are confused by how Core is handling that, don't you??? Besides, blocking dissenting voices from GH for the slightest of disagreements is absolutely disgusting 👎 This may break the straw for many ppl
1 replies ↓
vnprc's avatar
vnprc vnprc@trianglebitdevs.org 8 months ago
Sjors, who knows better than me, doesn't seem to think it's that difficult.
Sjors Provoost's avatar Sjors Provoost
Maintaining such a patch is probably a couple of days work per year, assuming a worst case scenario of the patch being hard to maintain. Maybe half a day if you can cherry-pick it out of Knots. This is a much lower bar than having to maintain a custom Bitcoin Core fork for consensus changes. Don't be shy.
View quoted note →
↑