Eyal Chojnowski

I realized there was already an issue for this bug (#2941) so I'm going to close this one.

This sounds like it's very close to the second solution I described here: https://github.com/warp-contracts/warp/issues/178#issuecomment-1260753678 so I think it should be good! I have a few questions regarding your description of...

Looks like it should be ok then, thank you for taking the time to answer my points! > My main question to you is will you need the information about...

I've switched to Postman in the meantime. I'll try again if ever this issue gets some attention from the developers.

Hello @sash9696, I'm afraid I don't have the permission to do that. Also, at the time of creation of this issue (~3 years ago) I was only trying out Brave,...

Hey @Blagoja95, sorry but as I said in my previous comment I don't use Brave anymore.

> https://medium.com/@wl1508/avoiding-using-serde-and-deserde-in-rust-webassembly-c1e4640970ca - but that's unusable in our case. Yes unfortunately it's not going to be a feasible option as the contract's state type are going to be too complex...

> One thing to reconsider is the evolve [...] Ah yes that's a good point... It's a bummer to have a special case like this but I guess there's no...

I have good news regarding your idea of using msgpack as the serialization format for the state & WASMJS communication. I've implemented it based on Warp v1.2.32, using only msgpack...

Wow. We were just talking with @lowczarc (Pianity's CTO) these very last few days about this crazy idea of exposing an SQL database per contract instead of relying on a...