You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case in steps:
1 - I used 'EC SLP v 3.6.6 to create a mine-able token (exact condition: with some pre-minted tokens).
Result: Created token appears in the < Tokens Tab > with the (unexpected) 'Token Name' instead of the 'Token Symbol'.
Expected : The 'Token Symbol' is expected but the 'Token Name' is displayed instead.
2 - When I send/blockchain transfer the same token to another EC SLP wallet v3.6.6:
Result: The token is listed in the with the (expected) 'Token Symbol'
Expected: The expected 'Token Symbol' is displayed for the token.
Conclusion:
The wallet that was used to create the SLP token displays the token as 'Token Name' while the 'Token Symbol" is expected in the < Tokens Tab >.
This indicates that the "token creating wallet' is in error and reads the content for the 'Token Symbol' from an incorrect source.
The text was updated successfully, but these errors were encountered:
Hi James,
I would like to report the following issue:
Use case in steps:
1 - I used 'EC SLP v 3.6.6 to create a mine-able token (exact condition: with some pre-minted tokens).
Result: Created token appears in the < Tokens Tab > with the (unexpected) 'Token Name' instead of the 'Token Symbol'.
Expected : The 'Token Symbol' is expected but the 'Token Name' is displayed instead.
2 - When I send/blockchain transfer the same token to another EC SLP wallet v3.6.6:
Result: The token is listed in the with the (expected) 'Token Symbol'
Expected: The expected 'Token Symbol' is displayed for the token.
Conclusion:
The wallet that was used to create the SLP token displays the token as 'Token Name' while the 'Token Symbol" is expected in the < Tokens Tab >.
This indicates that the "token creating wallet' is in error and reads the content for the 'Token Symbol' from an incorrect source.
The text was updated successfully, but these errors were encountered: