axelarnetwork / support

Your source for support with the Axelar Network
3 stars 1 forks source link

I can't deploy an ITS Token #77

Closed iBercryptoLabs closed 7 months ago

iBercryptoLabs commented 7 months ago

I have a question, because I have tried everything and I can not deploy an ITS Token, I think the problem is my region because I live in Spain, can this be the problem? I can not go to step 3 but friends outside Spain if they can move forward, I do not know if it's my computer or what the problem is, can you help me, please? This is the error that comes out when I try, same error in different browsers and different wallets, I have created a new wallet and again the same error occurs, I do not know what to do anymore, I need help and many users have this same error, can you tell me what is happening? Please consider extending the ITS competition, it's not fair that most users can't deploy a token to participate.

This is the error when I go from step 2 to step 3, following the same steps like other users who can complete the deployment:

SyntaxError: Cannot convert 0,00000000000000000000 to a BigInt at BigInt () at a (https://interchain.axelar.dev/_next/static/chunks/354-a8661048522703ca.js:1:83053) at https://interchain.axelar.dev/_next/static/chunks/563.287d068aee0916bd.js:1:7036 at Object.lQ [as useMemo] (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:65276) at t.useMemo (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:41:5984) at F (https://interchain.axelar.dev/_next/static/chunks/563.287d068aee0916bd.js:1:6990) at lk (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:60903) at op (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:72785) at i (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:120317) at uD (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:99073) at https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:98940 at uI (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:98947) at uE (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:95699) at uT (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:96088) at r6 (https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:44813) at https://interchain.axelar.dev/_next/static/chunks/framework-63c261f7457c35c5.js:25:93599

canhtrinh commented 7 months ago

@JLiBercry can you file a ticket here (https://axelar.zendesk.com/hc/en-us/requests/new) and tell me here what the ticket # is, once it's generated?

i want to set up a troubleshoot with you tomorrow to discuss

iBercryptoLabs commented 7 months ago

This is the answer from 5 days ago, no more answers, I have already try and informed them that this does not work and I have not received any other answer yet:

  | AntonMashnin (Axelar Network)Feb 9, 2024, 18:58 GMT+1Hello Team, Yes, you've understood it correctly. For blockchain and cryptocurrency operations, especially when dealing with tokens and their supply, it's common to work with very large numbers to accommodate the decimal precision required by the token. If your token has a supply of 100,000,000 and you want to include 18 decimal places for precision, you indeed need to represent the supply as 100,000,000 followed by 18 additional zeros. This means your total supply value would be represented as 100000000000000000000000000 for the system to correctly interpret it as an integer, compatible with BigInt, and not lose the precision for fractional values. This approach ensures that all calculations within the blockchain maintain the necessary precision and are accurately processed.Best regards,Anton Mashnin

I have tried putting much more than 18 decimal zeros. But this is not the solution, since I see some users deploy the token by typing the desired supply without typing as many 000 as this answer indicates.

I think is an error for the region location, I don't know, I live in Spain.

benjamin852 commented 7 months ago

Hey the team is looking into this we'll provide an update once bugfix is released. Thanks for flagging

iBercryptoLabs commented 7 months ago

What about old wallets? this is my address I use, but I also try on a new address too:

0x0A5960eE3D261A89F563B2FC105487bA30cAE475

El vie, 16 feb 2024 a las 18:59, ben-weinberg @.***>) escribió:

Hey the team is looking into this we'll provide an update once bugfix is released. Thanks for flagging

— Reply to this email directly, view it on GitHub https://github.com/axelarnetwork/support/issues/77#issuecomment-1948993645, or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6DPEIYGUHAGG3KT7J7VTDYT6NBVAVCNFSM6AAAAABDHRLZWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYHE4TGNRUGU . You are receiving this because you were mentioned.Message ID: @.***>

benjamin852 commented 7 months ago

Hey, I am sorry can you clarify what you mean by your old address? You're having the BigInt bug with a different address you mean? Thanks

iBercryptoLabs commented 7 months ago

The address I use has more than 6 years. I don't know if is a problem

El lun, 19 feb 2024, 16:38, ben-weinberg @.***> escribió:

Hey, I am sorry can you clarify what you mean by your old address? You're having the BigInt bug with a different address you mean? Thanks

— Reply to this email directly, view it on GitHub https://github.com/axelarnetwork/support/issues/77#issuecomment-1952716643, or unsubscribe https://github.com/notifications/unsubscribe-auth/BE6DPEKQ4E5XH3AJKR4J2A3YUNWVVAVCNFSM6AAAAABDHRLZWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSG4YTMNRUGM . You are receiving this because you were mentioned.Message ID: @.***>

benjamin852 commented 7 months ago

Hi, @JLiBercry can you please try again see if this is working now? Thanks

benjamin852 commented 7 months ago

bug has been fixed should be working now please confirm if issue needs to be re-examined closing this issue unless i hear otherwise, thanks!