Emanuele Francioni

This issue depends on phoenix integration to be done first

The strategy should also keep into consideration eventual flooding attacks based on burst of invalid transactions. In this case, we should make sure that valid transactions in the Mempool are...

Another potential solution would be to sanity check the `AggrAgreement` in the `AggrAgreementChan` in the same fashion of [how we sanity check Candidate blocks from the wire](https://github.com/dusk-network/dusk-blockchain/blob/65aa1e5bf1691ce0a404b6041964c80b30acd493/pkg/core/candidate/requestor.go#L45) before processing them.

@zer0 is this for the wallet feature or we need it more generally in the core board?

+1

This should solve the persistence error popping up when improperly shutting down the node: `Error: PersistenceError(Custom { kind: InvalidData, error: "Invalid index file ""/opt/dusk/rusk/state/246607761c6c6a5b9791c08cbb38e1692eacee015b074864358e5c230f66d480/index"": context error: pointer out of bounds:...

Depends on #1516

Blocked by #1657

The issue of checking the uniqueness of transaction when added in the mempool is part of this task. A more in-depth discussion about it needs to take place and be...

The flooding with random walk over Kadcast has been deemed the best approach