Steem 0.16.1 Bug Fix Release

in steem •  10 months ago

We are happy to announce the release of Steem 0.16.1. This is a bug fix release that all witnesses and seed nodes are encouraged to upgrade to. Those who do not upgrade should remain compatible; however, the various stability enhancements are a benefit to all.

There are two changes in particular that witnesses should upgrade for. These are both related to security of the blockchain and/or security of individual nodes.

  • A new bandwidth algorithm has been implemented that more accurately saves bandwidth used over time and prevents abuse by sending two transactions in the same block. Along with this change, the soft fork that was preventing two transactions from the same account from being present in a block has been lifted.

  • Fixed asset deserialization error that could result in a div0 DoS.

The rest are optimizations or non-forking bug fixes.

  • Blocks are no longer saved in the memory mapped file once written to the block log.

  • Various stability improvements in the block log and fork database.

  • Nodes now require their peers to report a Chain ID and will actively reject connections that don't. All nodes running 0.16.0 report their Chain ID.

  • steemd now periodically reports how much free memory in the memory mapped file remains.

  • The Database API now has a method, get_ops_in_block which returns all operations contained in a block. Full account history must be enabled for all operations to be returned.

  • Custom operations that have only a required posting authority show up in account history.

  • The Equihash PoW will no longer display egregious error messages in the account_by_key plugin and accounts created through Equihash mining will be able to be looked up by key in the CLI Wallet.

  • The author reward virtual op will display the entirety of the comment's permlink.

  • Properties contained in the witness schedule object are properly mirrored when contained in other objects.

  • Tag filtering has been improved and much of the display logic has been moved to Steemit.com

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  trending
·

Cheetah, you should white list this account. Thanks for your effort.

·
·

It worked Dan!!! Comments below.

·
·
·

Bahaha! Awesome, this made me laugh.

·

but you are more good than silly! That's why we love you.

Thanks for the update - regarding tags for posts - are we able to tag 5 topics again, or should we stick to 4? (Following up on an issue noted on @timcliff 's page, here)

·

The update on tags filtering is about moving the backend (Steem) tag filtering to frontend (Steemit). The next step is blocking the submission of 5 tags, and forcing only 4. It is already in the Develop branch.

After the tags plugin will be updated in the backend to make available using 5 tags, the mentioned frontend tags reduction will be reverted.

(Disclaimer: I'm not a dev so I may be wrong.)

·
·

So it's taking the back-end and moving to the front-end and at the end you will be turned around? Was that also 4 tags in the back-end then 5 tags in the front-end and then 5 tags in the back-in only after the plug-in? Just make sure the plug-in doesn't go in the back-end. It is only to be used in the front-end. :D

!cheetah whitelist

·

Okay, I have whitelisted @steemitblog. I won't bug them.

Thanks a lot!

Fixed asset deserialization error that could result in a div0 DoS

I wish I knew what this meant.

·

The Fixed Asset is converted to another format (serialization), then sent, then converted back (deserialization). The problem is that a divide by zero (div0) throws an error in the program. Its then probably caught and the retried (rerun again) then you will get the div0 again, then caught, then retry, forever. Transactions can't be processed (Dos) because its still running the div0 error.

·
·

It means the program crashes forcing a reindex.

any idea how much RAM is required for this release? 0.16 need at least 8GB RAM