https://twitter.com/chrisblec/status/1632851504175501312

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

as we shared in our blog, our intention is for base to remain open, decentralized, and permissionless.

https://base.mirror.xyz/H_KPwV31M7OJT-THUnU7wYjOF16Sy7aWvaEr5cgHi8I

@base builder #001; onchain cities w/ OAK & city3

I understand intentions, but for now, it’s not decentralized, which lead to the questions in the interview. What happens when tornado cash gets deployed to Base?

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

I don't disagree but again, this is strictly on the conditions of Base at launch time. While you could have the scenario of an OFAC address depositing on L1 to Base and this is uncensorable, the question of what happens on Base at the sequencer level, or at the Withdrawal level, has repeatedly gone unanswered.

They just need to implement 'forced txn inclusion' at L1, which would solve the problem by taking it out of their hands. This eventually has to happen anyway, just needs to be prioritized...

lol @cassie asking the important questions 3 months before I even think about them 😩

Please answer @jessepollak, would love to hear the counter here. Feels like a good litmus test

A boring OFAC tells CB to not bridge out any token that touched the contract.  

A creative OFAC will tell CB to block the sequencer from allowing any transaction involving the contract.

will they acknowledge that the successor to TC can arbitrarily exclude wallets? might be the case that Privacy Pools on Base would need to be more strenuous/sybil resistant