You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
In the latest edition of Buildnet, large event messages are no longer supported. This was a key feature in the previous version and is crucial for many use cases.
Details:
Issue: Large events are now restricted, causing disruptions in applications that rely on extensive data exchanges within a single event.
Impact:
Hinders projects requiring detailed logging or complex event data.
Reduces the flexibility of the network for developers.
Forces developers to split data into smaller events, increasing complexity and transaction costs.
Expected Behavior:
Large event messages should be supported as in the previous Buildnet edition, ensuring backward compatibility and a seamless developer experience.
Priority: High
This feature is vital for many developers and impacts the overall usability of the Buildnet ecosystem.
The text was updated successfully, but these errors were encountered:
Hello,
We had to cap event size following a security audit that detected a security issue related to event flooding. For now the limit was set to 512 bytes.
How big of a payload does your application need ? Would 1 kilobyte be ok ?
Summary:
In the latest edition of Buildnet, large event messages are no longer supported. This was a key feature in the previous version and is crucial for many use cases.
Details:
Expected Behavior:
Large event messages should be supported as in the previous Buildnet edition, ensuring backward compatibility and a seamless developer experience.
Priority: High
This feature is vital for many developers and impacts the overall usability of the Buildnet ecosystem.
The text was updated successfully, but these errors were encountered: