Implement Transactions

Problem/Motivation

The Drupal Ethereum relies on Transactions (aka TX). TX are the blood of the Ethereum state machine, constantly submitted, verified, dropped, replaced, committed... ultimately building the chain of blocks. So it will be our starting point for the new module version 3.0.x

As explained in this documentation by Infura, There are currently 3 types of transaction on the Ethereum networks:

1. Legacy transactions
2. Access list transactions
3. EIP-1559 transactions

Proposed resolution

Implement Transactions using a custom storage bundle (e.g. Drupal Storage entities → ), custom fields for Address, Value, Nonce, Data...etc

Remaining tasks

• Implement Networks as taxonomy
• Implement Transaction type as taxonomy
• Implement Address element (e.g. form element + field widget + field formatter + wallet in context + convert ENS)
• Implement Value element (e.g. converting value from/to WEI/GWEI/ETH + check amount from wallet in context)
• Implement Nonce element (e.g. retrieving last nonce from the default network)
• Implement address validator (e.g. accept ENS, restrict by contact list)
• ...