xermicus
xermicus
Removing from the OZ milestone for Polkadot; OppenZeppelin contracts check the `address.code.length` to distinguish contract addresses, however on Polkadot we have the `is_contract` builtin to do the same.
Fixed a while ago
Hi @ychen-1202 For the most recent version ink! v4.0, storage key calculation for mappings [is explained in our docs](https://use.ink/datastructures/storage-in-metadata#storage-key-calculation-for-ink-mapping-values). In a nutshell, `SCALE` encode the mapping key to the base...
We do not link to it on crates.io, but that doesn't mean it is not on [`docs.rs`](https://docs.rs/solang/latest/solang/). However, please keep in mind, providing a stable and well-documented API for 3rd-party...
Closed by #990 Thanks @extraymond!
`ink!` release didn't happen this week. Pinned the dependencies so we can merge as soon as @LucasSte approves
Solved by: #1084
As we found out, there also needs to be configuration for `Hash` length, similar to `--address-length`, which defaults to 32.
@extraymond it makes me sad that we didn't go forward sooner with this PR, sorry! I really like what you implemented here. In the long run, it would make sense...
> Sure! I'll be on it sometime this week. Awesome, thanks! While you're on it, can you directly aim for compatibility with pallets contract v0.22.1 (it uses WeightV2)? Not all...