[Testing]: Testing Round Epic

[guibvieira]

We are going to simulate the protocol on a PR net in an attempt to find bugs and to collect data to help define the ranking system calculated by the indexer.

Steps for data analysis:

• Set of utilities/script to scrape the data from subgraph

• Collect and Organize the subgraph data to analyse

  • APY, stake_room, continuity, commission changes over time.

• Analyse the data to find the following:

  • How APY evolves over time for each validator
  • How the distribution of delegated TARA behaves over time (epoch based)
  • Figure 2/3 alternative methods to calculate ranking in order to see behaviour changes between approaches.

Main objective:

• Find a ranking mechanism that guarantees maximum welfare:
  • Good decentralization -> e.g. not only 2 validators get everything for example.
  • Good APY for user

#####################################################################

Genesis of Testing Scenario: Launch PR net, mint Tara to 10 wallets, from 10 wallets fund validators

• Max amount of tara to "user" wallet => 800m - 40m - 80m = 680m
• Let's do 200 wallets with random allocation of Tara maxing out at 800m Tara (random(0, 680m) to 200 wallets)
• Validator1 -> 40m self-delegation
• Validator2 (full-node) -> 40m Lara delegation
• Allocate 60% of "user" wallet funds to Lara
• Remaining randomly allocate between (start_block, end_block)
• Randomly unDelegate from Lara from "users" wallets.

Process to update ranking method mid-test scenario:

• If new ranking method is implemented, update indexer and let it run

Finalize Testing Scenario:

• Undelegate slowly at random - see behaviour
• Undelegate all at once - see behaviour

Smart Contract stuff:

• Quantify the leak over time.
• Staking 200m manually vs 200m in the protocol over X timeperiod, e.g. a few days to a week.
• Compare the difference the APY between running a node and staking in Lara.

Security:

• Think Einsten, Think.
• Indexer security -> private key management, machine security, etc.

[VargaElod23]

How to get the yields for intervals:

1. Port-forward any of the rpc nodes:

   kubectl -n platform-qa port-forward po/pr-2609-taraxa-node-0  8080:8080

2. Specify the from & to blocks in the query + substitute the address to the validator you want to get the yield for

   curl -X GET http://localhost:8080/address/0xfe3d5e3b9c2080bf338638fd831a35a4b4344a2c/yieldForInterval?fromBlock=1&toBlock=5000