a-scalability-roadmap question #5062

issue philsong opened this issue on October 8, 2014
  1. philsong commented at 3:45 AM on October 8, 2014: contributor

    (the practical limit before the change was 32 megabytes– the maximum size of a message in the p2p protocol). in https://bitcoinfoundation.org/2014/10/a-scalability-roadmap/

    can someone know how does 32M come from?

  2. sipa commented at 3:47 AM on October 8, 2014: member

    which 15M?

  3. philsong commented at 3:57 AM on October 8, 2014: contributor

    sorry 32M

  4. TheBlueMatt commented at 3:59 AM on October 8, 2014: member

    Its the maximum size a network message can be. Larger messages are considered invalid whether they are of type block, inv, or anything.

  5. philsong commented at 5:01 AM on October 8, 2014: contributor

    i check, it should be static const unsigned int MAX_SIZE = 0x02000000; // Message size if (nMessageSize > MAX_SIZE) { LogPrintf("CMessageHeader::IsValid() : (%s, %u bytes) nMessageSize > MAX_SIZE\n", GetCommand(), nMessageSize); return false; }

  6. TheBlueMatt commented at 5:04 AM on October 8, 2014: member

    Yes, 0x02000000 == 32M

  7. philsong commented at 5:10 AM on October 8, 2014: contributor

    thx

  8. philsong closed this on Oct 8, 2014

  9. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-21 21:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me