Nikita Zhavoronkov
Nikita Zhavoronkov
While 32 MB may look valid today, it may be become too low in a few years, but there will be a hard limit in place which would require a...
> In this case, we are talking about a limit that literally prevents the network from breaking down. The solution to this issue should be fixing the 100 MB packet...
> Yes, everyone agrees with this. Do you volunteer? I think an acceptable compromise would be to publish a bounty funded from the Monero general fund to fix the bug....
> This already is a limit in the code Yet you won't find any mention of this limit anywhere. All the existing articles and materials on dynamic blocks don't mention...
> There is, and has been since 2014: > https://github.com/monero-project/monero/blob/296ae46ed8f8f6e5f986f978febad302e3df231a/contrib/epee/include/net/levin_base.h#L71 I've specifically asked that many times on Twitter if someone is able to present at least one (one!) article (not...
> It was probably unintentionally introduced by the original Bytecoin developers, which explains why it's not documented anywhere. I'm glad that we agree that it's an undocumented leftover rather than...
> That'd presumably allow OOM killing every node on the network No, it won't, and you well know it, because miners will not be constructing blocks over some soft limit...