警告:您可能成为了企图假冒本网站内容的目标。 我们检测到该网站被IFRAME包裹,这意味着与EOS Canada无关的人试图向您展示他们的内容与我们的内容相关,可能为了让您相信他们与EOS Canada有关。 我们与任何试图这样做的组织都没有联系,它也没有受到我们的认可



WARNING: you may have been the target of an attempt to misrepresent the content of this site. We detected that the site was wrapped in an IFRAME, which means that someone else, not associated with EOS Canada, attempted to show you their content combined in some way with ours, possibly to make you believe they are associated with EOS Canada. We are not associated with, and do not endorse, any organization attempting to do this.
background-flotant-top-right-01

Blog: EOS Block Producer Tips & News

background-flotant-top-left-01

EOS-BIOS Boot Stage 16

May 29, 2018 / by Alexandre Bourget

Stage Reports 16

As the launch of the EOS blockchain approaches, a group of Block Producers are testing the EOS BIOS sequence to work through the software to help ensure a successful and secure launch. The `eos-bios` tool allows for multiple stages to take place. Here is the report with the highlights and improvement of the Stage 16.

Block Producers that participated in Stage 16 (in alphabetical order): Aloha EOS, Bitspace, BlockEOS, Cybex, Easypayx, EOSIO.SG, EOS 42, EOS Amsterdam, EOS Argentina, EOS Asia, EOS Authority, EOS Bixin, EOS BlockSmith, EOS Cafe, EOS Canada, EOS Cannon, EOS Ecosystem, EOS Germany, EOS LaoMao, EOS Nairobi, EOS Nation, EOS NodeOne,  EOS Pacific, EOS Romania, EOSpace, EOS Store, EOSys, EOS TaxRelief, EOS Thu, EOS Worbli, EOS Vibes, GenerEOS,  JEDA, MeetOne, Oracle Chain, HelloEOS, TokenPocket.

Stage 16 Bubbles

Visualisation of the 34 peers connected to Stage 16

Highlights

  • Over 60 participants present on the call
  • 34 participating infrastructures to the actual launch
  • Tyee from EOSpace, Joshua from EOSeco, and Zhaoyu from EOS LaoMao did a great job helping with translations.
  • EOS LaoMao successfully booted up this Stage of the launch! Well done!
  • We fixed a bug and shipped a release during the call. Between bug identification and everyone having the release, 15 minutes passed.

Next Steps:

  • JJ from EOS Germany will lead an effort to try and attack the network launch two days from now to test the security of the network. EOS Amsterdam immediately offered help.
  • Fix a sorting bug that was discovered in the sorting algorithm written last night

 

THINGS TO NOTE FROM THE LATEST RELEASE:

The latest release includes many improvements, most of which come from community suggestions:

  • Boot node hooks updated: introduces the `hook_boot_mesh.sh` script, which can be left to be done manually.
  • Sample `base_config.ini` updated as we’re nearing mainnet. Make sure you master your configuration before going to prod.
  • Load contents from IPFS only from the top 8 by weight, avoids locking a launch because someone published stale content.
  • Implemented @daniellarimer’s suggestion to stake .25 EOS, keep 10 floating, and half/half the rest.
  • Support `target_p2p_address` value `none`, if you want to be excluded from the automatic mesh.
  • Boot node should now NOT connect to any swarm.  Sample hooks were updated to do that, by changing the listening address (make sure it fits your infra), and by commenting the `p2p-peer-address` (they are left for when you’re ready to connect, and randomized so we don’t know to which swarm node you’re going to connect)
  • Removed boot node handoff of the eosio private key. eosio is on schedule until the 15% cliff.. publishing the private key would allow rogue parties to produce blocks on its behalf. SO, Boot node: don’t share the private key until 15% cliff.
  • Lowered producer enrichment (in testnet), to avoid people directly altering the ABP schedule, while not available to produce.  We tested it, it works well.. but we don’t want to screw up the next staged launches. We need a stable seednet this week to launch mainnet from.
  • Publishing a `seed_network_launch_block` with value 0 allows you to be an ABP, and use the `eosio.disco` consensus mechanism, vote on content, etc.. but prevents you from being selected the BIOS Boot node. This allows someone to not use `eos-bios` and participate in the launch.  The bios boot node in an orchestrated `eos-bios` launch still needs to run `eos-bios`.
  • Added `--write-actions` to write all actions to `actions.jsonl` for tools to do cross-checking. With the last snapshot we used, actions.jsonl weighs 178MB (full snapshot), and 22MB (truncated snapshot to 1000). It can be used with orchestrate, join and boot.


We will be running the next Stage at 1300 UTC of May 30. Please follow along with the EOS BIOS Telegram channel for updates. We encourage those who want to practice amongst themselves to continue to do so and provide further feedback to the community!

All BPs are invited to participate in the next launches.

For anyone who will be joining for the first time, we invite you to first go through the eos-bios YouTube playlist.

Topics: EOS Canada, BIOS Boot, EOS Blockchain, EOS BIOS, EOS Launch, Bios process, Boot sequence, Stage Reports

Alexandre Bourget

Written by Alexandre Bourget

Alexandre lives through technology. He wrote his first botnet at 12, later graduated in classical piano and went on to a prolific career in software engineering, with notable open source contributions. Alexandre co-founded two startups, including Bitcredits (a bitcoin payments processor, FounderFuel 2014 Spring Cohort). He then helped PasswordBox (acquired by Intel) craft their data stack and ended up as a lead Data Scientist in the Intel Security Consumer division. Today, Alexandre is very active in the blockchain space, advising several early stage companies. Alexandre taught programming for many years. He does live-coding presentations like no one else (Confoo, PyCon conferences) and is the lead organizer of Golang Montréal. You’ll often find him on Telegram, working through lines of code and bugs with others, doing what he can to help build the EOS community.

cubes-solid

ABCs of EOS

A glossary of terms that every EOS user should know.

MORE

Apply to Access Our Newsletter

Get exclusive insights into EOS blockchain technology