I logged into ICPSwap using Oisy and this is what I see. A stroke of luck!
I can’t spend it or transfer it however, I guess it’s DIP 20? It won’t let me trade it either because it’s giving me icrc_method not exported. @ICPSwap
It won’t let me top-up a canister either. Please I got my hopes up here, don’t let them be dashed against the rocks of poverty.
EDIT : I also have a tonne of Arbitrum USDC in there. I need to be better at crypto.
No it will stay there forever and you will look at it everyday!!!
Dear @borovan,
XTC is a DIP20 token.
Could you please DM me your Principal ID so I can check if your wallet holds these balances, or if there’s an issue with our display?
Thank you so much!
Dear @borovan,
Indeed, you do have these balances. Both the dev and I have confirmed it.
At the same time, we’ve identified the issue you mentioned.
The Oisy wallet requires the targeted canister (in this case, the XTC canister: aanaa-xaaaa-aaaah-aaeiq-cai) to support ICRC21 for proper interaction. Without this, actions like swapping, transferring, or importing tokens to the Oisy wallet page (https://oisy.com/) won’t function correctly.
Dear team, @memecake, would it be possible to add ICRC21 support for the XTC token canister? Thank you!
Hi @borovan, OISY here
About your cycles, we do only support icrc-1 and -2 tokens from the IC network, that’s why you can’t add the token through the manual add process. And as ICPSwap stated, we require the token ledger to implement the icrc-21 protocol when being accessed from dapps, so users can confirm the transaction from within their wallet.
I will check if there is an easy way to add XTC to the default token list, but since the specification differs from the supported ones, it might not really be easily possible.
We actually implemented a default consent message in OISY, in case the ledger does not implement icrc-21, so users can also trade non-supportive tokens from dapps. I will check if the condition to use that fallback is based on the token standard, and if it would work to include DIP 20. The lengths we go to save some poor lost cycles… 
About the USDCs, we plan to support some EVM based networks soon, ARB being one of them.
And out of curiosity: Do you know how you got these cycles? (asking bc I want to rule out that somehow we also sprinkle users with cycles…)
Stay tuned and eligible…
Stefan
I bought them to provide liquidity to a XTC-ICP pair back in the day, I guess when I was moving to Oisy I moved them and forgot… I had loads of tokens.
Ahhh yes very easy to forget moving 35k worth 
Please find a way to help him
Adam promised me pokemon cards to add to my collection if so 
Dear Stefan, @StefanBerger-DFINIT1
Thank you so much for your prompt and detailed response!
From my understanding, many ICRC tokens in the ecosystem might not yet support ICRC-21. If I may ask, would excluding these tokens from Oisy Wallet be necessary? Please correct me if I’m mistaken, as these tokens have also contributed to the IC ecosystem’s growth.
in case the ledger does not implement icrc-21, and users can also trade non-supportive tokens from dapps. (in cases where their ledgers don’t support the standard) sounds like an ideal solution! I’m genuinely excited to see how this could be implemented!
Thank you again for your hard work and transparency. looking forward to Oisy Wallet’s continued innovation!
Warm regards,
Well DIP-20’s a bit of a dumpster fire that we need to replace.
Can the foundation come up with a standard for tokenised cycles? Do we even need one? May be nice just to put them on an equal playing field with other exchange tokens.
Hi
We did extend our support for the signer standard, esp. regarding the icrc-21 standard, to also support all token ledgers that don’t implement this standard.
in this case, we do parse the sent transaction and display the contained data in a constructed confirm modal.
(see PRs feat: build custom consent message for icrc1_transfer by peterpeterparker · Pull Request #371 · dfinity/oisy-wallet-signer · GitHub, feat: use icrc2 approve consent message builder as fallback by peterpeterparker · Pull Request #388 · dfinity/oisy-wallet-signer · GitHub, feat: builder for ICRC2 transfer from by peterpeterparker · Pull Request #398 · dfinity/oisy-wallet-signer · GitHub).
This allows all icrc tokens to be used with OISY in all dapps via the signer standard. The consent form is then generated by OISY directly.
Isn’t that the cycles ledger? Cycles ledger | Internet Computer
yes, and transactions for this specific token standard (DIP 20) is not supported by this default handling that works for all icrc 1 and 2 tokens. so for icrc1_transfer and icrc2_approve rsp. icrc2_transfer_from.
i mean id rather burn the cycles than have developers at the foundation work on some band-aid just so I can sell my XTC
Sooooo can it be fixed or?
