Steem 0.14.3 - #527
Closed
mvandeberg wants to merge 59 commits into
Closed
Conversation
Custom ops can fail fast on producing nodes. Updated the follow plugin to throw exceptions on bad ops (handled by custom op code).
20160913 follow
#426 CI testing automation is slow
Fix deleting blog_object when comment is deleted #440
Fix and document get_replies_by_last_update #445
381 vop fixes
Posts in "@user/posts" are now stored as author/permlink.
Backported to develop as part of #476
Validate posting auth and check for account auth existence as a soft …
Update fc on develop to match shared-db branch
refactored documentation
does not run tests as part of main docker build
Update mining stats display #282
Removed addresses that were not responding ( multiple probes done over a week ), replaced with current when possible, added nodes provided by community ( thanks to @wackou for maintaining list ) IPs replaced with hostnames where applicable. Sorted by current approval rate for their providers ( where possible )
…s-list Improved and updated Steem seed nodes list
- Follow new plugin constructor API - Create impl class for plugin as well as API - Attach to on_applied_block() by default as this is so common
newplugin.py: Updates to new plugin template
Update compile-time constants
Remove deterministic_openssl_rand
Convert last_hardfork variable to uint32_t
Allow debug node to generate blocks without editing database
Contributor
Author
|
Do not merge yet. The mining fix did not make it in yet. |
added 2 commits
October 21, 2016 13:13
Fix mining threads #525
theoreticalbts
approved these changes
Oct 21, 2016
Contributor
|
During my review I summarized the changes. Let's use this as a starting point for patch notes. Documentation changes
Functionality changes
Bugfixes
Architecture changes
|
Contributor
Author
|
Due to problems with github merging, closing this PR and creating a new one. |
On1x
pushed a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this pull request
May 28, 2018
…r-17 Less account history master 17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a cumulative update of improvements and bug fixes over the last month. Most of them are plugin/API related that are already being used by Steemit.com and are not related to consensus at all.
Most important are the two following changes that will effect users of steemd.
Mining is fixed again. When we updated the proof of work algorithm, the code in the witness plugin was not ported properly which resulted in multiple threads mining the same hashes. The problem has been fixed and threads once again mine unique hashes.
Soft Fork on authority names. Account names in authorities were not properly sanitized. This allowed accounts to have public keys as account authorities which both, do not work, and are invalid account names. Those names are now checked both for validity and existence. This is implemented as a soft fork and will be enforced through a hard fork at a later date.