-
Make sure Borsh either does not work with trait objects entirely (because we don't know the type that we need to deserialize into) or if it works it works correctly.
-
As I've come to learn with Borsh serialization, the processing order of the fields is of utmost importance for proper serialization/deserialization. Unfortunately Java doesn't enforce any sort of inte…
-
Currently, if we gotta do any filtering by field, we gotta manually crunch the offset of each field and then slot in the right bytes in order.
My suggestion is to improve the filtering to a simple …
-
`Upgradable::up_stage_code` uses borsh parameter serialization:
https://github.com/aurora-is-near/near-plugins/blob/c043add4c2a0810872c4326a55c5162bccd3f4ee/near-plugins-derive/src/upgradable.rs#L3…
-
I got an error : InvalidParamsMessage { message: "invalid transaction: Transaction failed to sanitize accounts offsets correctly" } when simulate and send transaction to mainnet and local net.
I have…
-
Currently in the code we have a lot of hand rolled serialization code using this idea of the `Encode` and the `Decode` trait. While there are a couple of well-defined sterilization formats (such as `H…
-
$ anchor build
Error: Invalid Base58 string
-
I've been trying for the last while to get the fail result from the contract from `ExecutionFailure`. For `ExecutionSuccess` this is fine because I can return the `json`, `borsh` or `raw_bytes` quite …
-
### Current State
The WIP Registry module currently stores all persisted data as JSON.
### Proposition
I recently discovered NBT as a viable format for compressing large amounts of data, There also e…
-
Might want to create an issue here to see if we can avoid the extra allocation.
There's a borsh function that gives you the max-size of the serialized form of T. We could create a ve…