Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

bos blacklist #6947

Closed
wants to merge 11 commits into from
Closed

Conversation

vlbos
Copy link

@vlbos vlbos commented Mar 15, 2019

Change Description

Fix #192 Add blacklist in the system contract.
System contract added 'insert and remove blacklist' feature;
through setblacklist action insert or remove 'actor, contract, resource' three types list
eosio.contracts part: EOSIO/eosio.contracts#205
eosio.cdt part: EOSIO/eosio.cdt#448

Consensus Changes

  • Consensus Changes

API Changes

  • API Changes

In producer API,
set_whitelist_blacklist interface method sets blacklist does not override 'actor_blacklist,contract_blacklist' set by the system.contract.
remove_greylist_accounts interface method cannot remove 'resource graylist' set by the system.contract

Documentation Additions

  • Documentation Additions

@vlbos vlbos marked this pull request as ready for review March 29, 2019 06:23
@vlbos vlbos changed the title Feature/blacklistonchainforeosio bos blacklist Apr 1, 2019
@wanderingbort wanderingbort added the CONSENSUS Introduces a change that may modify consensus protocol rules on an existing blockchain. label Apr 1, 2019
@wanderingbort
Copy link
Contributor

I've flagged this as a consensus breaking change as it adds an intrinsic to the web-assembly interface. Even though this is intended to be a privileged intrinsic we cannot guarantee backwards compatibility to any EOSIO-based blockchain with this PR as spec'd.

We do have features, on schedule for the next release, which address this in a way that affords EOSIO-based chains a definable path for maintaining original functions and adding/modifying consensus rules in the same code base.

You can read more here #6429

A compliant version of this change will also depend on #6437

@vlbos
Copy link
Author

vlbos commented Apr 2, 2019 via email

@b1bart
Copy link
Contributor

b1bart commented Jul 30, 2019

This PR is being closed due to inactivity or incompatibility. If you feel this has been done in error please feel free to open a related issue for discussion.

For PRs that are labeled as CONSENSUS that are not implemented according to the system introduced in v1.8.x future submissions and issues will need to be compatible with this system in order to be accepted in the future. This system allows existing deployments of EOSIO-based blockchains to maintain backwards compatibility and forwards upgradability in a consistent manner.

@b1bart b1bart closed this Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CONSENSUS Introduces a change that may modify consensus protocol rules on an existing blockchain.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants