Having an option to have a blacklist member check during the runtime config for any permission'd network is a better than 'allowing' membership.
In a permission'd network, it is good to approve the node-authorization based on account and nodeKey, but any account with a balance should be able to transact on the network, which makes the job of governance more simpler. With ability to approve the revoking of membership, governance council can still take control of any account which got balance by mistake.
Similar to membership (isMember()) pallet, implement a blacklist pallet.
Having an option to have a blacklist member check during the runtime config for any permission'd network is a better than 'allowing' membership.
In a permission'd network, it is good to approve the
node-authorizationbased on account and nodeKey, but any account with a balance should be able to transact on the network, which makes the job of governance more simpler. With ability to approve the revoking of membership, governance council can still take control of any account which got balance by mistake.Similar to membership (isMember()) pallet, implement a blacklist pallet.