[Advanced test scenarios]

[sergey-melnychuk]

Beerus must be able to support the same functionality as a full node. The advanced test scenarios should include user-like interactions with the network, such as:

• creating and deploying new account
• declaring and deploying new classes
• calling existing contracts
• submitting transactions (INVOKE)
• providing useful abstractions
  • user-friendly API (ERC20-like etc)
  • (investigate for more use cases)

Such interaction need to be as smooth via Beerus as they would be via the full node directly, so it makes sense to try A/B tests (e.g. run the same scenario against Beerus and then against RPC directly and compare the results).

Scope

• feat: block hash to number in proof validation #675
• test: create and deploy new account #694
• test: declaring and deploying new classes #695
• test: calling existing contracts #696
• test: submitting transactions (INVOKE) #697
• test: providing useful abstractions - user-friendly API (ERC20-like etc) #698