gentx Meeting
===

Agenda:

1. Questions by Validators
2. gentx process
3. Turing Testnet

Questions by Validators
---

1. What are network Token Economics? Do they have a role to play in testnets?

- Turing-1 will have 2B
- Will have swapnet in between
- Swapnet tokens need to execute 1:1 with the mainnet

1.1) What are token economics of the first testnet and last testnet? If there is a change, why do we need that?
1.2) Are testnet tokens valid or exchangable in any way?

- Run incentivization till the end of testnets
@takFujiwara We'll have difficulty in how we will take address of mainnet to send tokens(cosmos used mails and kyc wheresas iris used keybase accounts).I think keybase will be better and we need to ask all validators to have keybase accounts for identification

1.3) Does the dVPN run with the testnet?

1.4) Can I connect my app with the testnet? If so, are there any custom transactions that I will have to write? Can this be done via governance?

- Turing-1 will have cli enabled client
- Turing-2 will have the client with front-end electron app
-

2. What is the min. stake required?

- To be decided (should be in-line with what we will have when the network is at 5B)
@takFujiwara The minimum stake will be decided based on network and it will sound too restricted to have a condition on this.
I propose giving around 5k tokens on validator faucet so the users can test other transactions as required
- Activity to run the Validator to be decided. Mostly a delegate transaction to Validator X and then receive stake tokens through the faucet

3. Are tokens transferable?

- Yes

4. Are governance proposals enabled? If so, how many characters fit into the message?

- Yes. 5000 chars for description and 140 chars for Title.

5. What is the update/upgrade process?

- Turing-1 will have chain update as a patch, continuing the old chain
- Turing-2 will have the chain upgrade process or a fork where the old chain
- Chain will be archived by specific Nodes that will be incentivized on the mainnet

6. Is my server secure if I just run the Validator code or do we have any other security measures recommended?

- Protection from DDOS,preventing open access to nodes(rpc),perfect firewall restrictions

7. How can I be part of the network right from the start? i.e. gentx process

- gentx process
- with a transaction with min. delegation
- Validator cap to start off at 50(@takFujiwara will this limit be on genesis file.?) @eon_1 : No. It will not be mentioned. We left it as 100

8. Do I need a HSM to run a Validator?

- No
- Have a secure software wallet for testing

9. What is the recommended architecture? How many nodes does it involve?

- To be discussed with Sahith
@takFujiwara as we discussed let's leave this to validators.We can have few tests since start making our own validators do some spam attacks to test other validators.Making all testnets adversial without announcing may even make other validators intrested

10. Can the entire setup run on a new computer that runs at our office?

- Yes
@takFujiwara Better not encourage this as more will be just rogue nodes without servers or proper infra (@eon_1 : Will not mention this, but tell people that they can run it in the cloud as well)

11. Are there any rules for bonding? How long is the unbonding period?

- Will start with 6 hour on Turing Testnets and will be decided while going to mainnet

12. Is there instant stake redelegation to a different Validator in case the first one goes down? (we discussed a priority list of Validators sometime back with respect to this query)

@takFujiwara Cosmos supports instant redelegation once but second redelegationwe have to wait for 21 days.For now we can leave it same as cosmos

(@eon_1 - Sure)

- Will be worked on by Turing-2

13. What are network tools offered for the Validators? Will we need to develop any custom interfaces to monitor and maintain the Validator?

- No. Turing-1 will not have.
- Turing (mainnet-1) will have

14. What is the eligibility criteria to participate in the mainnet?

- Have to decide before Turing-(mainnet-1)

15. Are there any tasks or objectives for participants of testnets? (IRIS has tasks, Cosmos ended with GOS)

16. How many Validators can participate in each testnet?
@takFujiwara I think we don't need to change defaults(100) here,or we can start at a lesser number(20-30) and make a proposal to make it 100

(@eon_1 : Sure. Proposal to make it from 20 to 100 will work great)

gentx Process
---

Sentinel-Turing-1
---

Sentinel-Turing-1 should test/execute the following in it's lifespan:

1. Validator Staking
2. Validator Sync for an update
3. Validator Update - manually async/not coordinated
4. Community defined update - coordinated through Governance
5. Bandwidth Exchange
6. dVPN Node Hosting - Protocols to be finalized
7. Total Token Transfer (Payments) Transactions within a fixed time duration (to determine transactions per second)
8. Delegation by Users

@takFujiwara Adding a new list here as discussed

1. Will differ for genesis and later validators(genesis vals will have submitting gentx as task while new ones will have delegation tasks)
2. We can test withdraw rewards and redelegate
3. Governance proposal to increase Validators from 20 to 100
4. Update chain to a latest version
5. We can ask them to set min-gas-prices (and all transactions happeing on client v2 will have variable fees) [@eon_1 : Any specific reason for this task?]
6. Send to a particular address can also be added as a task but will be too simple [@eon_1 : True, something like this is not needed]

Sentinel-Turing-2
---

1. Delegation through the client v2 based on your preference