canto-network/docs

Open source docs for Canto Public

docs's Issues

🤔 CSR Backwards Compatibility

Many existing protocols utilize create2 to claim vanity or other recognizable addresses across chains. This makes it easier for users and developers to identify secure instances.

The current CSR implementation suggests that dev/deployers will need to include the CSR interface for eligible contracts.

While convenient to handle CSR at contract level and install trustless fee mechanisms to reward popular contracts, existing, already popular protocols, such as UniV3 and Seaport would need to change their bytecode by implementing the CSR interface, breaking backwards compatibility and identification with their sister deployments.

It seems preferable to design a method to mint CSR NFTs, claimable by deployers, but without changing protocol code (unless I am missing something, ofc!).