deuszx
deuszx
Since `contract_ref!` macro produces the "access trait" with the exact same method signatures as the ones on the original contract, sometimes it puts too strong of requirements on `self` on...
Hey team 👋 I'm not 100% sure this is an issue for `dylint`, or even a bug, but have to start somewhere: I'm trying to build as small as possible...
**Is your feature request related to a problem? Please describe.** Currently, when calling contract's endpoint that is `payable`, the **Value** field unit is fixed to the main unit of the...
`Header` definition from [`header.rs`](https://github.com/informalsystems/tendermint-rs/blob/master/tendermint/src/block/header.rs#L19-L61) has inconsistent types around representation of various hashes. It uses both `Option` and `Hash` but `Hash` itself can have `None` variant. In that case, what's the...
I propose renaming `init` command to `new`. There are two reasons for this that come to my mind: 1. Similarity with `cargo contract` -- it uses `new` for generating starting...
https://docs.soliditylang.org/en/develop/security-considerations.html#use-the-checks-effects-interactions-pattern I think it should be possible to write a detector for it? Since it maps nicely: 1. Checks == `if` , `assert` , etc 2. Effects == mutating state...
I've been wondering why there is no mention/support for partial fills. Is there anything in particular in UniswapX's design choice for `Order`(`Info`)~ structs that makes it impossible?
Clients should need to only synchronize the block headers of admin chain (or any other chain for that matter) and be able to identify whether they need its body based...
This could become an umbrella issue for sub-issues that are required to be able to verify. We need to be able to take a (serialized) `Block` value and upload it...