EOSIO Dawn 4.1

EOSIO Dawn 4.1 Release

As we continue the march towards our 1.0 release, today we have tagged a 4.1 release of the EOSIO software.

Notable Updates

We continue to squash bugs and improve stability. We’ve fixed issues relating to general network stability, duplicate transactions spamming the network, nodes failing to propagate transactions in some instances, and others.

Bringing a Failed Node Back Online

We have enhanced nodeos to persist accepted but reversible blocks (#3140). This greatly improves the startup time for nodes to come back online and resync.

Command Line Tool Improvements

The command line tool cleos is now able to output the full list of producers (#2933). Note that you can paginate results and that they’re sorted by vote.

Quality Name Distribution & Namespaces

Of particular note in this release is the restriction of account names to exactly 12 characters with no periods/dots (“.”). This is change is in an attempt to discourage name squatting. Dan is requesting community feedback for his proposal regarding name distribution via GitHub (#3189).

Renaming of the Core Token

Please be aware that we have changed the name of the token symbol from “EOS” to “SYS”. If you would like to change the name to something different, check CORE_SYMBOL_NAME in the “CMakeLists.txt” file.

BIOS Boot Process Tutorial

There is now a script that demonstrates the steps necessary to boot an EOSIO network along with a detailed tutorial (https://github.com/EOSIO/eos/tree/master/programs/bios-boot-tutorial). We will be adding additional steps to this script and tutorial in the coming week related to upgrading the eosio.system and eosio.token contracts via the producers using multi-sig.

Testnets

Our internal testnets are running strong. We’ve been happily watching multiple community testnets and we are proud of the work that we see there. Of particular note is the EOS Jungle Testnet (http://dev.cryptolions.io) which has been running an earlier build (DAWN-2018-05-16) for the last few days and has participation from over 70 nodes. Watch for more updates on the EOSIO Community Testnet (https://t.me/CommunityTestnet) Telegram group.

Patroneos

We are preparing a new tool for protecting RPC-API endpoints from abuse. We are calling it Patroneos because it keeps the Dementors soul sucking spammers at bay. Behaviors that we’re currently watching out for are things such as repeated, invalid JSON payloads, signature spam, blacklisted contracts, and oversized transaction payloads.

We’ve been developing this tool in-house and will be releasing more information to the community in the near future. Keep an eye out for this one.

Dawn 4.1 on GitHub

EOSIO Dawn 4.1 is available on GitHub here (https://github.com/EOSIO/eos/releases/tag/dawn-v4.1.0) so that developers and block producer candidates can continue testing their applications and networks.

Community Support

We love hearing from our community and are dedicated to helping them run EOSIO successfully. Our EOSIO Stack Exchange (https://eosio.stackexchange.com/) beta is going well and we encourage questions about how to use the software on Stack Exchange.

Please continue to report any potential bugs you may see in GitHub and include the following information:

Testnet: what testnet you are reporting the issue on
EOSIO git version: nodeos -v output
config.ini: attach your config.ini file
genesis.json: attach your genesis.json file
Command line: your full nodeos command line
Console output: attach console debug output around the error that you are seeing (ok to paste into the description if it is small)

Future Releases

We plan one more pre-release (Dawn 4.2) next Friday May 25th and we’re on target for the EOSIO Version 1.0 release on June 1st. You can follow the issues that we are committed to working on over the next few weeks by observing the Version 1.0 milestone (https://github.com/EOSIO/eos/milestone/10) in GitHub.