In the last #bitcoin-core-dev IRC meeting, the mailing list moderation
was slightly discussed. It was decided to do this discussion mainly on
this mailing list (which makes sense).
The current situation is that the moderation is slow and takes around
>24h for a E-Mail to be on the mailing list.
I spoke to some people OOB and they said that they didn't really like
the idea of having a prefix string (partially because they've already
implemented some proprietary types by simply squatting on unused types).
Matching the prefix string adds additional complexity to the parser
code. The main
It seems like the consensus is that we should use Compact Size Unsigned
Integers for the field types, so we will do that. The types will be
minimally encoded CSUints.
For the proprietary types, I will use Dimitry's and Andrew Poelstra's
> why not use Bitcoin compact uint, which most PSBT consumers already
implement?
I totally agree with that, compact int parsing is already implemented in
all bitcoin applications, wallets and libraries. Also, for certain (mb
proprietary) applications I will be willing to use multi-byte keys where
mm you are right, then the "moving checkpoint" rule needs to have some limits
to allow the network self-heal instead of requiring humans detecting the splits
or stopping nodes.
Let's suppose than a 51% attack can be detected and the developers can release
a new version of the software with a
