Error Creating the stablecoin - For no KYC selected
Describe the bug When creating a stablecoin through the Web UI, and specifically selecting not to have KYC enabled, the interface throws an error
To Reproduce Steps to reproduce the behavior:
- Clone the repo
- Run npm install
- Configure env files as required
- Run npm run start in "web" subdirectory
- Select HashPack wallet
- Select Testnet and click Accept
- Create a new stablecoin - specifically select not to have KYC enabled during the process, otherwise use the default control options.
- Submit the transaction to create the coin, and sign off the transactions in the connected wallet.
- Observe the error in the Web UI / console (the wallet report successful transactions).
- The stablecoin is still created (successfully?).
Expected behavior No error is shown upon creating the stablecoin
Screenshots
Desktop (please complete the following information):
- OS: WSL2 (Ubuntu 22.04.3 LTS) under Windows 11 (22631.3155)
- Browser: Brave
- Version: v1.63.165 (Chromium 122.0.6261.94)
Additional context
- Error text shown in the console:
2024-03-15T01:46:14.183Z - [ERROR] 20006 - The coin 0.0.3711618 does not have KYC active
StableCoinCreation.tsx:390 Error: The coin 0.0.3711618 does not have KYC active
at GrantKycCommandHandler.execute (GrantKycCommandHandler.js:66:1)
at async StableCoinInPort.grantKyc (StableCoin.js:299:1)
at async LogError.descriptor.value (LogErrorDecorator.js:25:1)
at async SDKService.grantKyc (SDKService.ts:492:1)
at async handleFinish (StableCoinCreation.tsx:360:1)
- Create Token Transaction List: https://hashscan.io/testnet/transactionsById/[email protected]
- Associate Token Transaction: https://hashscan.io/testnet/transactionsById/[email protected]
Strangely when repeating this, the error didn't re-occur 🤔
- Create Token Transaction List: https://hashscan.io/testnet/transactionsById/[email protected]
- Associate Token Transaction: https://hashscan.io/testnet/transactionsById/[email protected]
@app-matt there is something I do not understand, you said that you used the default options when deploying the new stablecoin except for the "enable KYC account flags", you said that you disabled it, but the thing is that by default it is already disabled....
Did you maybe, enable KYC then disable it before moving to the next step?
Thinking about it, when I ran through the creation of the first coin I did turn kyc on, then back off - but I didn't do this on the second coin. So that could be where the bug lies.
I hadn't correlated that, good catch! 🙌
indeed there is an issue with that, we will fix it and let you know when done.