Eduardo Leegwater Simões
Eduardo Leegwater Simões
#### Summary It might be viable to (re)introduce a fixed fee for simple transfers, for both better user experience and client-side note proliferation mitigation. #### Possible solution design or implementation...
**Describe the bug** Currently 8 circuits can be compiled to produce their prover and verifier keys. For this process, a single CRS is lazily generated and cached for subsequent use....
#### Summary The functions exposed by the transfer contract shouldn't return `bool` since they are either pass or fail, and use a panic to signal a failure. #### Possible solution...
#### Problem Currently, `wallet-core` depends or `rusk-abi` - which is in this repository. However, `rusk` - which is also in this repository - depends on `wallet-core`. This generates a really...
#### Summary In the context of the [fee market](https://github.com/dusk-network/rusk/issues/880) we should allow the contract to comp the gas cost of running one of its functions. Since someone should still pay...
#### Summary We should try and avoid redefining types defined in other crates, or using "untyped" fields. Currently the `Transaction::proof` field is a `Vec`, when it really should be a...
#### Summary Contracts writers should be able to instantiate contracts that have already been deployed as template contracts. This will ensure that bytecode is reused for instantiating multiple versions of...
**Describe the bug** Currently, when a contract is called multiple times during a `call` cycle, its instance is reused by all those calls. Even though this is deterministic, it leads...
#### Summary Currently, in an effort to make commits independent from others, we hard link each page that doesn't change from the previous(base) commit from every contract. This means that...
#### Summary It should be possible for host functions to call contracts during execution of a program. This will allow for downstream to move all the logic of the transfer...