Help review mainnet migrations

I would like to see if the community wants to help speedup a filtering process. Idea is to avoid issues such as: VECHAIN VET but written VEN on the nash wallet

Would be nice to have a list with tokens like those to remove on the following format:

symbol, contract_hash, still_valid

For tokens that still have a valid ERC20/NEP5, that allow conversion for example, please use still_valid = True , and we will keep the token but add a ERC20 or NEP5 note in the name.

Our community is always so up to date, let’s see this :smiley: , our team will do it either way but researching more than a thousand tokens may take some time.

4 Likes

ICX, 0xb5a5f22694352c15b00323844ad545abb2b11028, False

2 Likes

BNB, 0xB8c77482e45F1F44dE1745F52C74426C631bDD52, False

2 Likes

DAI, 0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359, False

2 Likes

NEP5

ONT, 442e7964f6486005235e87e082f56cd52aa663b8, false

2 Likes

NEP5

SOUL, ed07cffad18f1308db51920d99a2af60ac66a7b3, True

2 Likes

ERC20

DREP, 0x3aca71c508e06dc6b2758dab6eb20f7654572fb7, false

2 Likes

ERC20

FSN, 0xD0352a019e9AB9d757776F532377aAEbd36Fd541, TRUE

1 Like

NEP5

NEX,3a4acd3647086e7c44398aac0349802e6a171129, TRUE

:stuck_out_tongue_winking_eye:

3 Likes