just_ppe
just_ppe
optimize the interactions cache loader so that it would not try to load the interactions during foreign contracts read/writes - for contracts that have zero interactions. Example contract - `f86Qw3vp6TlgxI3mABFnWDQNqR8mPVkVTBN04hwywqc`...
..as currently it may lead to some unexpected results - i.e. the the write result will be visible only during the view state function call - as the viewState does...
The contract interactions processed via bundled transactions MUST NOT access any data releated to transactions reward and transactions transfers (as in this case this data is irrelevant). To secure against...
especially reading/writing state from/to WASM module. 1. Fix double state initialization - https://github.com/warp-contracts/warp/blob/main/src/core/modules/impl/DefaultStateEvaluator.ts#L65-L79 2. Implement fix from https://github.com/warp-contracts/warp/blob/main/src/core/modules/impl/handler/WasmHandlerApi.ts#L41 3. Try to optimize executionContext creation - i.e. recreating the execution context...
https://jsonpatch.com/ https://www.rfc-editor.org/rfc/rfc7386 Potential libraries: https://github.com/Starcounter-Jack/JSON-Patch (watch for issues!) https://github.com/streamich/json-joy/blob/master/src/json-patch/README.md BUT - watch out when pruning states ;-)
Is there an option to set the jobs auto-removal feature into "eager" mode? The documentation says that they're removed in the "lazy" mode, but I believe it does not suit...
Hey, is there a way to somehow name and identify sandboxed workers (from within their code) - assuming that I'm creating them with concurrency set to > 1. e.g. sth...