prevent duplicate tokens being added in adminJS

[divine-comedian]

On a few different occasions now we have had instances of donations going missing because of duplicate tokens being added to the adminJS. We should create some checks and error conditions to prevent this from recurring.

We should check two conditions when a user is adding a new token for a given network and throw an error if true

• the token SYMBOL already exists in the DB on the given network
• the token address already exists in the DB for the given network

the error thrown should be descriptive depending on the condition that triggers it

i.e "This token symbol already exists for {network}", "This token address already exists for this network"

[divine-comedian]

@RamRamez have you had a chance to investigate this issue?

[RamRamez]

@maryjaf please test and verify.

Users shouldn't be able to add a token when:

• the token SYMBOL already exists in the DB on the given network
• the token address already exists in the DB for the given network

(FYI We have a full page error for these scenarios and I couldn't customize the error page in adminjs)

[maryjaf]

• I can create new token with a symbol that is already exist @RamRamez

but when I try to add token with address that is already exist on our db I got below error

[RamRamez]

@maryjaf those tokens you added are on different chains. This was scenario:
"the token SYMBOL already exists in the DB on the given network"

The error you showed is ok.
"(FYI We have a full page error for these scenarios and I couldn't customize the error page in adminjs)"

[maryjaf]

@maryjaf those tokens you added are on different chains. This was scenario:

[RamRamez]

@maryjaf those tokens you added are on different chains. This was scenario:

@maryjaf This is the token I added myself for testing.

[maryjaf]

now the Acs have bben passed .
Thanks @RamRamez