Add CHI token

[dusan-mrsic]

Token name and symbol is CHI. It is added in CHI-PROTOCOL folder because there is already CHI folder in project.

[wbnns]

@dusan-mrsic

Hi there! CI is failing with the following issue:

error: CHI-PROTOCOL on chain base token 0x3b21418081528845a6DF4e970bD2185545b712ba could not fetch l2Bridge or l1Token.

This token most likely needs nobridge or a bridge override set.

Could you please fix and update the PR?

[dusan-mrsic]

Hi @wbnns , can the problem be with the name? Because symbol is CHI, but folder name is CHI-PROTOCOL, but I didn't know what to put because there is already CHI folder?

[wbnns]

@dusan-mrsic

Heya, hm, yeah -- let's loop in @annieke or @hamdiallam here. 🤔

[hamdiallam]

Hey @dusan-mrsic, this error isn't due to the name but due to the contract itself.

How is this token bridged from L1, through the standard bridge contracts? If so it's not a proper OptimismMintableERC20. I would recommend not extending the interface but the concrete contract. Then supply the appropriate constructor arguments

[wbnns]

@dusan-mrsic

Will close this PR for now. Please let us know if you'd like to pursue this change and we can reopen. 👍

[dusan-mrsic]

@wbnns @hamdiallam But why this is the problem? It is extending IOptimismMintableERC20. Our token USC is the same as this one and it is merged without problems.