You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is meant to be a todo of all the issues related to core functionality that needs to be implemented for the core algorithm to match the description in the whitepaper and also tasks that to not add any features and are sometimes pushed back but that increase the robustness and are required for a quality production ready product.
The wire protocol firewall (#594) will prevent deletes & updates on the bigchain & votes tables. If a node deletes a transaction from the backlog table, then the client can just resend it, so such deletions don't have to be reverted. As for updates to the backlog table, those must be allowed, for example, to reassign stale transactions (PR #359).
I'm going to close this "meta-issue" because there's only one remaining open issue within it ( #444 ); I will just move that issue into meta-issue #284
Abstract
Implement core functionality from whitepaper.
Goals
This issue is meant to be a todo of all the issues related to core functionality that needs to be implemented for the core algorithm to match the description in the whitepaper and also tasks that to not add any features and are sometimes pushed back but that increase the robustness and are required for a quality production ready product.
Steps
General
hard
for all writes Ensure durability == 'hard' everywhere #504Voting
Skip/abort voting on a block if/when it is already decided: Skip/abort voting on a block if/when it is already decided #190Algorithmic/WP
Querying
get_transactions_by_asset_id()
should ignore invalid blocks: All backend implementations of get_transactions_by_asset_id() should ignore invalid blocks #332get_transactions_by_metadata_id()
should ignore invalid blocks: All backend implementations of get_transactions_by_metadata_id() should ignore invalid blocks #792bigchain
table should ignore invalid blocks - issue Queries to the bigchain table should ignore invalid blocks #192 (ryan), PR Ignore invalid blocks #324Mutability
The wire protocol firewall (#594) will prevent deletes & updates on the
bigchain
&votes
tables. If a node deletes a transaction from thebacklog
table, then the client can just resend it, so such deletions don't have to be reverted. As for updates to thebacklog
table, those must be allowed, for example, to reassign stale transactions (PR #359).Prevent deletes on thebigchain
table - Prevent deletes on the bigchain table #197 (ryan), PR Core/197/revert bigchain deletes #330Handle deletes on thebacklog
table - Handle deletes on the backlog table #196 (ryan), PR Core/196/handle backlog deletes #337Handle updates on thebigchain
table - Handle updates on the bigchain table #195 (unassigned)Prevent updates on thebacklog
table - Prevent updates on the backlog table #194 (unassigned)What to do when a node creates another Genesis block? What to do when a node creates another Genesis block? #444 (unassigned)(Moved to meta-issue All known fault vectors accounted for, w/ system test per fault #284)Multiprocessing
There were other issues listed here before but then we realized this isn't core consensus stuff.
backlog
table - Handle stale transactions on thebacklog
table #198 (ryan), PR Core/198/handle stale transactions #359The text was updated successfully, but these errors were encountered: