Hein Dauven

Results 44 issues of Hein Dauven

#### Summary Consensus should emit events so clients can listen to them and act accordingly. #### Possible solution design or implementation Blocks should emit events on: - Block accepted -...

type:feature
module:consensus
module:node

#### Summary To get insight into how code changes impact the network, it would be beneficial to include benchmarks as part of our CI. This gives us a baseline to...

type:feature
module:rusk

#### Summary Provisioners should turn off all client APIs and prune transaction history. #### Possible solution design or implementation This should be a configurable setting, where the user can choose...

fix:vulnerability
type:enhancement
module:node

**Describe what you want implemented** Update the script to retrieve the Rusk-wallet from our [Rusk](https://github.com/dusk-network/rusk/) repository instead of retrieving it from the [Wallet-cli](https://github.com/dusk-network/wallet-cli) repository. **Describe "Why" this is needed** This...

**Describe the bug** When creating a memo transaction, the user is not asked for a receiving address. Nor is the user asked to send funds along. **To Reproduce** Simply execute...

fix:bug
module:rusk-wallet

#### Summary Memos are currently displayed as HEX, unintelligible for the average user. It would be cool if users could check the meaning of memos. #### Possible solution design or...

type:feature
module:explorer

**Describe the bug** The behavior between Moonlight and Phoenix reward withdrawal is different. When doing a Phoenix withdrawal of staking rewards, a user only has to fill in the gas...

fix:bug
module:rusk-wallet

**Describe the bug** When doing a transfer/stake with a zero balance, the user should get a "balance too low" warning by default. Instead, now the user can use the default...

fix:bug
module:rusk-wallet

#### Summary Update the CI action update-artifact to the latest verions, with a newer node runtime.

type:enhancement
module:rusk-wallet

#### Summary Currently archival events are in binary. For our most common use cases, like Moonlight transactions, the full history would require a traversal through many events. #### Possible solution...

type:enhancement
module:rusk