The peer book's size could only fit in 1 byte, so the JSON payload could only be 255 bytes in length. I've updated this to use a uint32, which should fit most use cases.
Coverage decreased (-0.9%) to 97.333% when pulling 66b1dfaa214836f9979d5015d4c09f79b45b391c on mslipper:larger-byte-size into bae95eb1558afc1f1b7d18a1c01a3533511758cf on dfinity:master.
Coverage remained the same at 98.206% when pulling 19efe6662ca3253358d229b0e65f139da9dae7b2 on mslipper:larger-byte-size into bae95eb1558afc1f1b7d18a1c01a3533511758cf on dfinity:master.
Coverage increased (+0.02%) to 98.222% when pulling 0e46925893ec7ab7535ebe2efb9701508f26cd56 on mslipper:larger-byte-size into bae95eb1558afc1f1b7d18a1c01a3533511758cf on dfinity:master.
Coverage increased (+0.02%) to 98.222% when pulling 0e46925893ec7ab7535ebe2efb9701508f26cd56 on mslipper:larger-byte-size into bae95eb1558afc1f1b7d18a1c01a3533511758cf on dfinity:master.
Coverage remained the same at 98.206% when pulling 3f2fb660391e0d8ca164d41b50bec639b5deb4e8 on mslipper:larger-byte-size into bae95eb1558afc1f1b7d18a1c01a3533511758cf on dfinity:master.
The peer book's size could only fit in 1 byte, so the JSON payload could only be 255 bytes in length. I've updated this to use a
uint32,
which should fit most use cases.