Thanks for the clarification. Yes, I referred to CompactSize using the lingo of https://en.bitcoin.it/wiki/Protocol_documentation
I am not sure if it is current concern. Apparently an exception is thrown if non-canonical CompactSize in a transaction s parsed. Is it ensured that transactions are always parsed before computing their hash? Tamas Blummer On Feb 1, 2015, at 11:44 AM, Wladimir <laa...@gmail.com> wrote: > > On Sun, 1 Feb 2015, Tamas Blummer wrote: > >> I wonder of consequences if var_int is used in its longer than necessary >> forms (e.g encoding 1 as 0xfd0100 instead of 0x01) > > In serialize.h lingo you are talking about CompactSize, not VarInt. > > CompactSizes indeed have redundancy in their representation, i.e. the same > number can be represented as up to four different byte sequences. > > VARINTs have a different format that (AFAIK) isn't used anywhere in the block > chain. See WriteVarInt / ReadVarInt. These were designed to not have any > redundancy in their representation. > >> This is already of interest if applying size limit to a block, since >> transaction count is var_int but is not part of the hashed header or the >> merkle tree. > > Are you sure that this is a current concern? Non-canonical CompactSizes are > forbidden - in serialize.h this is flagged in ReadCompactSize. > > Wladimir > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
