Test the deployment of besu network with ethereum account generated using the geth binary

[suvajit-sarkar]

Description

As a developer I want to generate ethereum account so that i can use them for smartcontract deployment

Use geth binary to generate the ethereum accounts and then use the accounts to deploy the Besu network

Acceptance Criteria

1. Creating further stories if deployment is successful

[lakshyakumar]

Tested baf Besu code by adding the eth_accounts generated by the geth binary. The geth binary successfully created the ethereum accounts but the smartcontract deployment got failed with message "method is not enabled"

.

[lakshyakumar]

Tested the creation of accounts using the web3.eth.accounts.privateKeyToAccount("privatekey") function, the function has created the ethereum accounts but the supplychain deployment is again failed with the message "method is not enabled".

[lakshyakumar]

Tested the javascript code to create ethereum accounts, the supply chain deployment failed with the same message.

[lakshyakumar]

The next steps should be

• create stories to generate and add the ethereum accounts in the ibftConfigFile.json in the baf code using ansible.
• The error "method not enabled" is due to the bug in existing code, the besu and orion charts. The spike story should be created to check the missing options in the charts.

use web3.eth.accounts.privateKeyToAccount() to create account in supplychain playbook.

[suvajit-sarkar]

903 bug is create for the investigation of this issue