Usage of existing account addresses and keys and how to mark them in individuals

[lisv]

At the moment, accounts are created upon starting the server and one account is then used to replace the ACCOUNT tag (which is a placeholder) inside requests.

• We should make use of more accounts (randomly selecting one of them) and of the secret keys that are also created (which are necessary to transfer cryptocurrency).

• Accounts and corresponding secret keys should be matched among one individual so that multiple requests within one individual make sense and have some cohesion.

• Furthermore, these placeholder tags are not great as they require the altering of the OpenRPC specification, which can be confusing. I should find a different way to mark the keys of which the values should be replaced with existing values.

One other issue is that by using these tags, the functionality of leaving out response values in the feature vector that were specific to the request values does not work anymore (so a solution must be found for this).

[lisv]

For XRP accounts, the wallet_propose function is used to generate key and address values. Next, the submit method is used to transfer funds from the genesis account to the generated accounts.

For Ganache, accounts and private keys are generated upon starting the server.

A constantString gene is created to differentiate between variables that should or should not be (fully) mutated.