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
Similar to what we do as a "catch all" to limit transaction size (done outside of env - stellar/stellar-core#3672 ): we need a limit (network setting) on how big any Soroban ledger entry can get:
while limits on SCVals , keys (#629) , etc should be enough, there is a possibility that we miss something (or a combination of things) and that can become a problem for the network over time.
It seems we should be able to enforce this within env, but if not, we should enforce this in the core bridge (when we convert entries into binary blobs when crossing back to C++).
The text was updated successfully, but these errors were encountered:
Similar to what we do as a "catch all" to limit transaction size (done outside of env - stellar/stellar-core#3672 ): we need a limit (network setting) on how big any Soroban ledger entry can get:
while limits on SCVals , keys (#629) , etc should be enough, there is a possibility that we miss something (or a combination of things) and that can become a problem for the network over time.
It seems we should be able to enforce this within env, but if not, we should enforce this in the core bridge (when we convert entries into binary blobs when crossing back to C++).
The text was updated successfully, but these errors were encountered: