Transaction confirmation/Token name issue

[kjchiang3]

Issue with updated token names for tokens launched on Stackswap's Token Launchpad.
Issue is occurring on v3.7.1

Tokens launched from the Launchpad before the last update are showing correctly, but tokens launched since then are showing as "TOK" ticker instead of the updated ticker.

e.g. SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.tokensoft-token-v4ktqebauw9
This token should be displaying a ZERO ticker.

[andresgalante]

Thanks for the report. We have a release ready for tomorrow that solves it.

[janniks]

This might be related to an issue in stacks.js (stx-labs/stacks.js#1230) username validation, which fails to fully authenticate users. The latest fixes are released in @stacks/...@4.0.0, @stacks/connect@6.5.0, @stacks/connect-react@14.0.0

[timstackblock]

@andresgalante @janniks this issue you are mentioning above was something I noticed during testing but is not related to the issue with the token name.

I was able to reproduce this and I do not see the token name listed in the wallet or in explorer.

I created a token called Tim Test Token the ticker it TTT, it looks good on stackswap but is very hard to follow in the wallet.
Here are screenshots of the token

It shows the TTT ticker but when I look in the wallet I do not see anything that related to TTT. I have Stackables and LTO liquidity tokens. I am guessing these represent TTT but do not show the TTT ticker

[Eshwari007]

The latest fix @stacks/...@4.0.0 fixes the issue of an account with bns name to sign in successfully to https://app.stackswap.org/swap, this however failed in v 3.7.1 testing.
cc @andresgalante @janniks

[kjchiang3]

Would it just be an issue of updating the token metadata on the DB about once a day?

[kjchiang3]

zero : SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.tokensoft-token-v4ktqebauw9
wagmi : SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.tokensoft-token-v4ka1lgcc8y

In the above examples, Zero token is not updating to new values, but WAGMI token shows up as expected.

[markmhendrickson]

@andresgalante Let's assign to a dev?

[diwakergupta]

zero : SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.tokensoft-token-v4ktqebauw9 wagmi : SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.tokensoft-token-v4ka1lgcc8y

In the above examples, Zero token is not updating to new values, but WAGMI token shows up as expected.

So neither the zero token nor the wagmi token actually define the relevant SIP-010 properties:

(define-data-var token-name (string-ascii 32) "")
(define-data-var token-symbol (string-ascii 32) "")
(define-data-var token-decimals uint u0)

But the API returns this for the wagmi metadata

{
  "token_uri": "https://jsonkeeper.com/b/EO9R",
  "name": "WAGMI",
  "description": "WE'RE ALL GONNA MAKE IT",
  "image_uri": "https://stacks-api.imgix.net/https%3A%2F%2Fi.postimg.cc%2FWzh48MdD%2FWagmi.png?s=29d469371f8d450895534f1b4b70256b",
  "image_canonical_uri": "https://i.postimg.cc/Wzh48MdD/Wagmi.png",
  "symbol": "WAGMI",
  "decimals": 4,
  "tx_id": "0x1aad6a5d2559642fa9af74844b4478d9695ba884a404ba6f60102b70019aa413",
  "sender_address": "SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275"
}

And this for the zero token:

{
  "token_uri": "https://stackswap-launchpad.s3.amazonaws.com/14c2a187-9e69-4682-bd93-1e59155978e0.json",
  "name": "Zero Authority DAO",
  "description": "",
  "image_uri": "",
  "image_canonical_uri": "",
  "symbol": "ZERO",
  "decimals": 6,
  "tx_id": "0x735598041387d188d0c5238132ef070a4e05fe9a9394282e706c95b020f68613",
  "sender_address": "SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275"
}

So API is returning the correct metadata for both tokens -- @kjchiang3 can you confirm?

Separately, given the contracts don't define these properties, I don't quite understand where the API is picking up the FT metadata. @zone117x @rafaelcr could you chime in?

[kjchiang3]

yes @diwakergupta, the metadata is correct.