Add STNT to superbridge

[supermigrate-bot]

Adding STNT to superbridge token list repo. Tagging @sjalq for verification

[sjalq]

Approved
https://x.com/Stiintit/status/1819703342437667024

[sjalq]

Gracias!!

[sjalq]

Hi there,
Apparently I made a mistake in the token naming, it should be
"STiiNT-iT" not "STiiNT-It"

Is it possible to alter that?

[njokuScript]

Hi there, Apparently I made a mistake in the token naming, it should be "STiiNT-iT" not "STiiNT-It"

Is it possible to alter that?

Yes it's possible, but that has to be done manually. You'll have to fork this repo, make the changes, push up and raise another pull request. Happy to get on a call to walk you through this.

[sjalq]

Thank you!
I see I made the same mistake on the mainnet contract, I assume the bridge would have bridged it with the same mistake.

[sjalq]

Hi there, Apparently I made a mistake in the token naming, it should be "STiiNT-iT" not "STiiNT-It"
Is it possible to alter that?

Yes it's possible, but that has to be done manually. You'll have to fork this repo, make the changes, push up and raise another pull request. Happy to get on a call to walk you through this.

Hey there,
Sorry to bug you again, I just need some clarity on if the Name in the bridged contract is indeed immutable and if I need to redeploy if I want to bridge it with the correct stuff?

[njokuScript]

Hi there, Apparently I made a mistake in the token naming, it should be "STiiNT-iT" not "STiiNT-It"
Is it possible to alter that?

Yes it's possible, but that has to be done manually. You'll have to fork this repo, make the changes, push up and raise another pull request. Happy to get on a call to walk you through this.

Hey there, Sorry to bug you again, I just need some clarity on if the Name in the bridged contract is indeed immutable and if I need to redeploy if I want to bridge it with the correct stuff?

The only issue is that the name will be different on the L2, but it doesn't affect bridging - downside is that it might confuse your users. So you can redeploy the contracts and go through the process to update this one.

[sjalq]

OK, I can burn all the tokens that exist on the current contract. So there will be nothing in circulation at least.

I assume that if I redeploy the contract I can fork this repo with the chances (address, etc) and then that PR becomes the canonical info you will share on your bridge?

[njokuScript]

OK, I can burn all the tokens that exist on the current contract. So there will be nothing in circulation at least.

I assume that if I redeploy the contract I can fork this repo with the chances (address, etc) and then that PR becomes the canonical info you will share on your bridge?

You can go through the migration process again after bridging the current tokens back to Ethereum. You don't need to do it manually.

[sjalq]

Hey njoku,

Just to clarify, I can redeploy the contract and start this whole process afresh using the new contract address?

Will there be any conflicts because the social media is the same and the websites / details are the same?

Also can we remove from the repo the token I've submitted?

[njokuScript]

Hey njoku,

Just to clarify, I can redeploy the contract and start this whole process afresh using the new contract address?

Will there be any conflicts because the social media is the same and the websites / details are the same?

Also can we remove from the repo the token I've submitted?

Yes you can restart the process

No, there won't be any conflict.

The new token details will override the current one.