Closed kalepail closed 8 months ago
Looking at https://stellar.expert/explorer/public/protocol-history for Soroban runtime configs we need to “unlimitize” all these values at the very least.
{
"contractDataEntrySizeBytes": 65536,
"contractCompute": {
"txMaxInstructions": "100000000",
"txMemoryLimit": 41943040
},
"contractMaxSizeBytes": 65536,
"contractLedgerCost": {
"txMaxReadLedgerEntries": 40,
"txMaxReadBytes": 133120,
"txMaxWriteLedgerEntries": 25,
"txMaxWriteBytes": 66560
},
"contractEvents": {
"txMaxContractEventsSizeBytes": 8198
},
"contractDataKeySizeBytes": 200,
"contractBandwidth": {
"txMaxSizeBytes": 71680
}
}
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed.
What version are you using?
As of the time of this ticket open.
What did you do?
What did you expect to see?
When invoking the function which calls the above on the unlimited local network I would expect the function to pass.
What did you see instead?
I get an error during submission
Other tx limits besides CPU and memory can be exceeded, such as the number of reads and writes as well as the number of bytes which can be read or written. At least this
contractDataKeySizeBytes
however seems to not be able to be exceeded.This is important to resolve in order to allow folks to test extreme cases past live network phased limits in order for devs to get a full picture of all their contract invocation costs. Especially given the
AAAAAP/////////vAAAAAA==
gives zero clues as to the nature of the exceeded limit.