4. Appendix

4.1. Appendix I: Related information about Loom validator. Extracted from the Internet: http://www.tucaod.com/3497.html

4.1.1 Validator Responsibilities

It’s not possible to overstate the critical function that validators play in keeping the network honest. To ensure this, the responsibilities as a validator node will include:

Continuously running the latest and greatest version of the Loom SDK

Staking LOOM tokens for a period of time

Complying with Loom validation requirements and specs

Maintaining properly functioning hardware

Actively participating in network governance (voting on software upgrades, changes to the fee structure, etc.)

4.1.2 Requirements for Validators

As validation activity during an initial testnet phase typically requires minimal resources, we expect an accelerated bootstrapping of the network given recent milestones and momentum.

As such, we’ll be continuously iterating on precise specs and requirements to find the optimal setup for mainnet and anticipated growth in transaction volumes. At this point, approximate guidelines for testnet validators are outlined below:

Hardware

Server and backup server running Loom software (both with firewall)

Memory: 16GB of RAM, preferably 32GB

Disk space: 2TB of SSD storage

CPU: 64-bit

Processor: 2 cores, 3GHz each

Network: 1GB fiber

Hardware security module (HSM) and backup

Operation

Co-location at a top-tier data center; security and 100% uptime are paramount, so redundancy is a must

An additional backup location operation

Loom will provide examples and documentation on monitoring and alerting tools, but each validator is responsible for their own instance

Initially, more frequent upgrades during the testnet phase as the wrinkles are ironed out

LOOM Tokens

Must stake 1,250,000 LOOM tokens

Requires a 6-month lock-up period on the staked tokens

The larger the stake, the larger the validator will be rewarded

4.2. Appendix II: Guideline to TRON Super Representative Elections (SuperNode. Abbr: SR) Extracted from the official developer documentation: https://github.com/tronprotocol/Documentation/blob/master/TRX_CN/Tron-doc.md

4.2.1 Guideline for Applying to be a Super Representative Candidate

Any account in the TRON network can apply to be a super representative candidate and have the opportunity to become a super representative. Every account in the TRON network has the right to vote for his super representative candidate, and top 27 individuals among the candidates will be the Super Representatives that has the right for block generation. The votes are updated once every 6 hours.

To prevent malicious attacks, a threshold for admittance is set up — to run for Super Representative, 9999 TRX in the applicants’ account will be burnt. After successful application, users can run for Super Representatives.

4.2.2 Super Representatives Election

Voting requires TRON Power (TP), which is determined by the users’ frozen balance.

TP Calculation: 1 TP for 1 frozen TRX

Every account in TRON’s network can vote for the Super Representatives they support. Once you unfreeze your balance, an equivalent amount of TP is also lost, meaning previous vote cast may no longer be valid.

You can refreeze your balance to revalidate the votes.

Note: TRON network only records the latest votes, so every new allocation of votes you make replaces all previous records.

An Example:

freezebalance password 10_000_000 3 // 10 TP for 10 frozen TRX

votewitness password witness1 4 witness2 6 //4 votes for witness1 and 6 votes for witness2

votewitness password witness1 3 witness2 7 // 3 votes for witness1 and 7 votes

4.2.3 Super Representative Rewards

Vote Reward: 127 candidates updated once every 6 hours will share 115,200 TRX. The reward will be split in accordance to the votes each candidate receives. Total reward for candidates will be 168,192,000 TRX each year.

Block Reward: The TRON Protocol network will generate one block every 3 seconds, with each block awarding 32 TRX to Super Representatives. A total of 336,384,000 TRX will be awarded annually to 27 Super Representatives.

Each time a Super Representative finishes block production, rewards are sent to the sub-account in the superledger. Super Representatives can check, but not directly make use of this asset. A withdrawal can be made once every 24 hours, transferring the reward from the sub-account to the Super Representative’s account.

4.2.4 Committee

What is the committee?

The committee is used to modify TRON dynamic network parameters, such as block generation rewards, transaction fees, etc. The committee consists of the 27 SRs in the current round. Each SR has the right to propose and vote on proposals. When a proposal receives 19 votes or more, it is approved and the new network parameters will be applied in the next maintenance period (3 days).

Create Proposal

Only the Super Representative’s corresponding account has the rights to propose, while other accounts are forbidden. Following is the network dynamic parameters and the No. ( [min,max] ):

0: MAINTENANCE_TIME_INTERVAL, [3 * 27* 1000 , 24 * 3600 * 1000] //Change SR adjusts time interval. Currently 6 * 3600 * 1000ms

1: ACCOUNT_UPGRADE_COST, [0,100 000 000 000 000 000] //Change the cost of becoming a Tron Representative. Currently 9999_000_000 Sun

2: CREATE_ACCOUNT_FEE, [0,100 000 000 000 000 000] // Change the account creation fee. Currently 100_000Sun

3: TRANSACTION_FEE, [0,100 000 000 000 000 000] // Change the cost of the TRX deductible bandwidth. Currently 10 Sun/byte

4: ASSET_ISSUE_FEE, [0,100 000 000 000 000 000] // Change the for assets issuance. Currently 1024_000_000 Sun

5: WITNESS_PAY_PER_BLOCK, [0,100 000 000 000 000 000] // Change SR blockchain generation rewards. Currently 32_000_000 Sun

6: WITNESS_STANDBY_ALLOWANCE, [0,100 000 000 000 000 000] // Change the rewards given to the top 127 SR candidates, 115_200_000_000 Sun

7: CREATE_NEW_ACCOUNT_FEE_IN_SYSTEM_CONTRACT, []// Change the cost that the system creates an account. Currently 0 Sun

8: CREATE_NEW_ACCOUNT_BANDWIDTH_RATE, // Use proposals 7 and 8 together to modify the resources or TRX consumption of account creation.

9: ALLOW_CREATION_OF_CONTRACTS, //Activate Tron Virtual Machine

10: REMOVE_THE_POWER_OF_THE_GR // Remove the votes initially given to Genesis Representatives

12: EXCHANGE_CREATE_FEE, [0,100 000 000 000 000 000] //sun

13: MAX_CPU_TIME_OF_ONE_TX, [0, 1000] //ms

14: ALLOW_UPDATE_ACCOUNT_NAME, // Use to allow change of nicknames and repeated nicknames. Currently 0, indicating not allowed

15: ALLOW_SAME_TOKEN_NAME, // Use to allow creation of tokens with the same name. Currently 0, indicating not allowed

16: ALLOW_DELEGATE_RESOURCE, // Use to control unlocking of the resource proxy function

17: TOTAL_ENERGY_LIMIT, // Use to adjust Energy limit

18: ALLOW_TVM_TRANSFER_TRC10, // Allows the smart contract to call the interfaces of

TRC10 token. Currently 0, indicating not allowed. Set to 1 to allow

API: createproposal id0 value0 … idN valueN id0_N: parameter number value0_N: new parameter value

Note: In a Tron network, 1 TRX = 1000_000 Sun. Vote on the proposals

Voting on the Proposal

The proposal only supports affirmative vote, and the member who does not vote in time will be considered as a disagree. The proposal is active for 3 days after it is created. The vote will be expired if the proposal doesn’t gain enough affirmative vote during the 3-days voting window. Cancellation of previous affirmative votes is allowed.

API: approveProposal id is_or_not_add_approval id: Proposal Id. Accumulated over time of proposal creation.

is_or_not_add_approval: Approve or cancel approval

Cancel Proposal

The proposer can cancel the proposal before it becomes effective.

API: deleteProposal proposalId id: Proposal Id, Accumulated over time of proposal creation.

Query Proposal

You can enter the following interfaces to query the proposals, including: querying all proposal information, query proposal information (GetPaginatedProposalList) by paging, query specified information(GetProposalById).

For more information on api, please check out Tron-http