Change Details

Cashtab's "token" page used to be only for sending tokens. Gradually we expanded token actions. Now there is a good deal of complicated logic to handle the different actions that are available for different tokens. Not to worry, we have much more complicated action to add. Ultimately, it makes since to support a single screen that loads based on a tokenId. The tokenId is the "contract address" of eCash, and we want users to be able to share tokenIds with each other to see specific info (and orderbook) for a given tokenId. The feature will need to be slightly different for different token types. Because this diff is already large, add support for SLP1 only. - User can visit a token/<tokenId> page and load info about the token if they have no token balance and token is not in cache - User can see active offers - User can see a notice that it is blacklisted (and no active offers) if this is the case

Cashtab's "token" page used to be only for sending tokens. Gradually we expanded token actions. Now there is a good deal of complicated logic to handle the different actions that are available for different tokens. Not to worry, we have much more complicated actions to add. It makes sense to support a single screen that loads based on a tokenId. The tokenId is the "contract address" of eCash, and we want users to be able to share tokenIds with each other to see specific info (and orderbook) for a given tokenId. The feature will need to be slightly different for different token types. Because this diff is already large, add support for SLP1 only. - User can visit a token/<tokenId> page and load info about the token if they have no token balance and token is not in cache (works for any token) - User can see active offers for SLP1 tokens - User can see a notice that it is blacklisted (and no active offers) if this is the case

Cashtab's "token" page used to be only for sending tokens. Gradually we expanded token actions. Now there is a good deal of complicated logic to handle the different actions that are available for different tokens. Not to worry, we have much more complicated actions to add. Ultimately, i It makes sinceense to support a single screen that loads based on a tokenId. The tokenId is the "contract address" of eCash, and we want users to be able to share tokenIds with each other to see specific info (and orderbook) for a given tokenId. The feature will need to be slightly different for different token types. Because this diff is already large, add support for SLP1 only. - User can visit a token/<tokenId> page and load info about the token if they have no token balance and token is not in cache (works for any token) - User can see active offers for SLP1 tokens - User can see a notice that it is blacklisted (and no active offers) if this is the case