Chance
Chance
The coordinator does not wait for mass deposit blocks to be confirmed before including it in an L2 block. This can lead to an invalid block being proposed if the...
Right now a coordinator specifies the price per byte they are willing to accept. This means a wallet must ask the coordinator for this value. Instead the wallet should calculate...
The @zkopru/core package is the best way for most node applications to interact with the Zkopru contracts. The package breaks any web app build system because it relies on packages...
Currently the wallet will attempt to spend as many notes as necessary to send funds. The wallet tries to retrieve a file like `zk_transaction_6_2.vk.json` where 6 is the number of...
When a coordinator accepts a transaction via http it should validate the SNARK and the grove patch (to detect a double spend). The coordinator should perform a dry run of...
Right now the wallet naively chooses the largest (or smallest) notes to spend when creating a transaction. Instead the wallet should use the smallest notes possible while still being able...
I'm looking at the slash logic and it seems the challenger receives [2/3 of the stake](https://github.com/zkopru-network/zkopru/blob/develop/packages/contracts/contracts/zkopru/controllers/Challengeable.sol#L92). What happens to the remainder of the stake and the reward?
There is a discussion about implementing a minimum deposit fee chosen by the current active coordinator. Such a mechanism could be built into the `_deposit` function by asking the burn...
When synchronizing the blockchain we should attempt decryption of memo fields in a background thread to avoid slowing down the user interface (especially in the web wallet). UTXOs should be...
A user should be able to rebroadcast a transaction with a higher fee. Such a transaction should replace a previous underpriced transaction similarly to how Ethereum transactions work.