8 Things You Didn't Know About Ethereum 2.0
1. It needs 2 million deposited Ether to start
The deposit ceremony is held at Devcon 5 in Osaka, but this will not be a mobile event of 2 million ethers. It will start at that time and we will have 3-4 months until we have collected enough deposits.
Since non-developers and casual users are not recommended to join the bet system, because their Ethernet will eventually be locked into a risk-free system (no trading at the moment!), it may take some time for all Ethernet to come in.
The contract collected 2 million ethers of ether to start the origin of Ethereum 2.0, which only happens at midnight the next day, not the last deposit! This is because we want to wait for many confirmations and gain incredible high security in our commitment to guarantee the hash power of the final deposit block.
Some other interesting numbers:
The goal is that each committee has 128 validators (groups that are validated on a given shard), 1024 shards, which is a 131k validator for minimal network security. There are at least 111 verifiers per committee, but 128 is a more rounded number, slightly above the minimum, so this is the goal.
At less than the number of validators (such as 65k at Genesis), the network gradually skips some shards and gradually slows down and slows down slightly to ensure that the 128/committeator number remains the same.
This won't be a problem in Genesis, because the fragments don'2t/ exist yet. When we have fragments, we assume there are more validators than 131k.
The network can only use 64 validators technically, but it will be very insecure and slow, and the fragments will not work as expected.
Blockchain Generations Explained in 2019 | Blockchain History
2. Your private key is online, but you can't get hacked
In order to sign the certificate and generate a block, you must connect the validator to the Internet and must load the account's private key. There is widespread concern that hackers will allow hackers to steal all 32 people. It's not like this!
When you deposit 32 Ethernet as a validator, you will also send information about logging out of the account and exiting the shard. This means that no matter what happens - whether you voluntarily quit the system or be logged out of the system - your funds will be sent to a specific account designated as the withdrawal address.
For example, this allows you to install a Ledger device in a safe, or prepare multiple sig accounts, and accept Ethernet when they are sent to them, and the original private key used by the authenticator can be safely discarded!
Ethereum 2 slots are 6 seconds in length, except when they aren't
Because the general generation time and time in Ethereum 2.0 are represented by unix timestamps, and those are susceptible to leap seconds, some papers may be 5 seconds long, and some may be 7 seconds, although hard coded to 6 seconds. Ah, modern computing!
Ethereum dapps List to Consider in 2019
4. There are two types of penalties for validators!
If your validator node is offline for 18 days and the beacon chain is not completed, your balance will be reduced by up to 60.8% slash within 18 days, resulting in an inactive leak.
Cuts: If the verifiers show malicious behavior, their balance will decrease. The minimum penalty is 1 ETH, but the number of people who cut at the same time increases linearly.
It is important to note that this acts as a mechanism for distributed beacon nodes (although there is no incentive) because if many validators rely on the same beacon node and the beacon node fails with the validator due to the verifier, then those Verifiers suffer greater penalties than their independent beacon nodes.
In other words, offline is not as severe as you might think. As Vitalik himself said:
If you are offline when more than 1/3 of other validators are offline, you will only suffer a huge penalty. Otherwise, the penalty for offline will be small, as long as you are online for more than about 50-67% of the time, you will get a net profit (excluding computer costs, etc.). These incentives are deliberately designed to avoid dissuading amateur institutions from promoting decentralization.
What is a Decentralized Application (dApp)? dApp Examples in 2019
5. You don't need a supercomputer to run a validator
It is possible to run one or two validators on weak devices such as NanoPC, but you may not be able to run beacon nodes on them. See this interpreter for the differences between beacon nodes and validators.
You'll be able to monetize your mobile device, but because mobile devices turn off long-running connections while you sleep, this can disrupt your connection to Ethereum and can impact your bet profit. Mobile devices are not recommended unless you can insert them and always turn them on.
In either case, you will need an external beacon node to connect. Almost all entities like Infura provide a Beacon node for the certifier to connect to, but if you have a stable connection at home, it is recommended that you run it yourself, or connect to a place to host it but it is not so popular.
In other words, a standard laptop should hold up to 10 validators, so don't expect to get the necessary hardware for amateur settings and destroy the bank.
6. I heard there would be ASICs for Eth2. How, if there's no mining?
What you're hearing may be the VDF ASIC, a device that is currently being researched, as an enhancement to the randomness that already exists in Ethernet 2.0. For more information on randomness in Eth2, see this article. For additional information on VDF, see VDFResearch.
7. Not every slot has a block
Since slots are a cautious time unit (about 6 seconds each), some slots may not have blocks. This happens when there is a disagreement between the validators, the delay in the committee responsible for creating and proving the new block, the validator does not appear at work, and they should raise a block or any other number.
Unpredictable anomalies, Therefore, although you may be accustomed to blocking time of 15 seconds from Ethereum 1, the blocking time in Ethereum 2 may vary between 6 and 18 seconds (more than two should not be skipped) Time slot).
8. There is a queueing mechanism keeping the set of validators roughly the same
The queuing mechanism will ensure that the large-scale exit of the verifier is slow.
This means that many verifiers cannot leave at once - kick or legally quit. The number of validators in this system is as stable as possible. If a lot of pending exits (extracts) are detected, there is time to make the stakeout more attractive by automatically increasing the stakeout return rate and bringing more validators into the system, just like the mining difficulty adjustments under proof of work. .
This can also be used as an incentive for centralized infrastructure - if many verifiers leave immediately (for example, they all connect to AWS via a beacon node hosted on Infres and one is turned off) - they are all punished for inactivity They waited a long time to quit.
For more, visit meetnoor.com