Transaction queue

[ablax]

• [x] Create transaction pool
• [x] Create transaction queue
• [x] Prepare for transaction validation

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

[ablax]

Currently blocked, as it depends on Trie

[Zurcusa]

This PR can be merged with its current state. The logic for sending a validation request to the runtime and decoding the response is there. However, it seems we have some kind of an issue that causes the runtime to respond with an invalid transaction validation error for every transaction.

We have:

• Logic for validating incoming transaction from the transactions protocol.
• Logic for appropriately putting transactions in queue or pool.

What is still needed:

• Fix the issue that causes validation error. (could be related to the fact that we don't execute blocks after full sync, or as Kamil from Kagome mentioned it could be because the validation runtime request is trying to alter the state)
• Send known non repetitive transactions to peers in a transaction message.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud