EOS Block Producers has been organized into 3 random groups and they are working with other BPs to prepare for the launch. Here is an update:
Group 1
CIGEOS
EOSDR.io
EOS WTZ
91EOS
BlockPro.One
JEDA
EOSGeek
EOS.CYBEX
EOS Detroit
EOSeoul
MeetOne
eosONO
EOS UK (formerly EOS Nottingham)
EOS42.io
EOSBIXIN
EOSNz
HelloEOS
EOSYS
ChainPool
EOSVibes
Worbli
EOS Authority
Eosio.SG
Bitfinex
UnlimitedEOS
EOShuobipool
EOS College
5/4/2018 - BP Random pool update:
Snapshot Generation
This week the focus has been continuing on generating the Ethereum snapshot synchronising the Ethereum Blockchain using Parity
Once completed generating the snapshot will be generated and EOSVibes is doing this part already having completed Parity synchronisation.
Once EOS UK, EOS Authority and Worbli have also synched Parity then each other can validate the others snapshot against an agreed Ethereum block number.
Bios Boot Rehearsal Preparations
Using EOS Canada research we’ve testing launching a single node using their script and pre-generated snapshot, so this can be repeated with up to date snapshots.
The next stage before group testing is for each participant to confirm they are able to launch a boot node and then at least 1 other instance of a joining node.
EOS UK are designing this solution at the moment and will contribute it back to the EOS Canada GitHub repository once we’ve cleaned it up and solicited any other BPs research.
DDoS
EOS 42 having held their latest London meetup this week which many BPs attended, are publishing the results of their research on DDoS protection, which looks to have resolved the vulnerability of DDoS attacks and the rest of the group are eagerly awaiting Charles report so they can attempt to reproduce his solution.
VPNs
Next week the group looks to implement the suggested meshing methodology from BP Infrastructure group using Wireguard to create a mesh VPN network of block producer nodes, so each BP only runs 6-10 VPNs to reduce the overhead of having to maintain VPN tunnels to all 21 BPs.
Voting
EOS Singapore have successfully simulated the voting process and are developing a web UI for voting. They have also published interesting findings with regards BP rewards and revealed they may only be claimed once every 24 hours.
Next week
In addition to continuing on with the above, focus still needs to be applied to the following areas
RC2
Key exchange and verification for bootup
Security and backup
Failover solutions
Monitoring & log analysis
Go EOSVIBES
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit