Milosz Muszynski
Milosz Muszynski
**Describe what you want implemented** Persistence mechanism should support contracts with bytecode larger than 64k. **Describe "Why" this is needed** We need to be able to persist and restore contracts'...
**Describe what you want implemented** In VM2 contract size grew in comparison with VM1. Gather more data for proper comparison and try to explain what is causing the growth. **Describe...
**Describe what you want implemented** Implement as-is state persistence for VM2, as opposed to incremental state persistence. **Describe "Why" this is needed** Incremental state persistence consumes much more memory, for...
#### Summary Implement contract which will allow users to keep unobfuscated balance accounts and allow for seamless exchanges of balances between users. This functionality complements the existing Phoenix transaction model...
#### Summary Currently, only `owner` and `self_owner` ABIs are available, providing deserialised owner. It is beneficial to also have "raw" methods, which do not perform deserialisation. #### Possible solution design...
#### Summary Users submitting paid-by-the-contract contract calling transaction must provide a PoW which will prevent a possibility of DOS attack. Only then the contract call should be performed, after additional...
#### Summary In addition to issue #1603 implementing contract-pays scenario, but still requiring user's deposit, we also need an implementation which does not require a deposit. #### Possible solution design...
#### Summary Currently, it is not possible to execute smart contract method call via transaction without having a valid Dusk note that could cover the gas cost, which implies that...
#### Summary Currently, in order for a contract to pay for gas to execute a given transaction, we need to ask contract for a funding note, and this solution has...