Delegation is key to participating in consensus in Cardano right now. A lot of people do not have millions of ADA to open a block producing private stake pool. Adding 'optional' permissioned delegation would allow entities to enforce requirements at the base layer. If you value censorship resistance and neutrality, contingent staking is a step in the wrong direction. An example of giving options like this: Ethereum had optional privacy through Tornado Cash, now their blocks are OFAC compliant.

Question

Answer

Con: Optional permissioned delegation for specific pools does not allow entities to enforce requirements because the base layer is still permissionless.

Answer

Con: People don't need to have millions of ADA to start a block producing pool. They can simply delegate to someone else who runs a pool that aligns with their values.

Answer

Con: CS does not block participation in consensus.

Answer

Con: CS does not introduce censorship. SPOs can already censor transactions if they wanted to, exactly the same way that Ethereum validators censor Tornado Cash. CS has no bearing on this.

Cardano Contingent Staking

Pros

Cons

CS does not block participation in consensus.

People don't need to have millions of ADA to start a block producing pool. They can simply delegate to someone else who runs a pool that aligns with their values.

Optional permissioned delegation for specific pools does not allow entities to enforce requirements because the base layer is still permissionless.

CS does not introduce censorship. SPOs can already censor transactions if they wanted to, exactly the same way that Ethereum validators censor Tornado Cash. CS has no bearing on this.

Selected claim, opposing its parent

Con claim 1

CS does not block participation in consensus.

Con claim 2, children below

People don't need to have millions of ADA to start a block producing pool. They can simply delegate to someone else who runs a pool that aligns with their values.

Con claim 3

Optional permissioned delegation for specific pools does not allow entities to enforce requirements because the base layer is still permissionless.

Con claim 4, children below

CS does not introduce censorship. SPOs can already censor transactions if they wanted to, exactly the same way that Ethereum validators censor Tornado Cash. CS has no bearing on this.