@Henry_Suso what kind of hiding do you mean? I don’t see any special restrictions applied to this thread
Thanks @ZackDS, I read it as ‘forum users’ and did not think of unauthenticated users. It’s now visible
@Gabriel Don’t forget to add this review to the grant spreadsheet.
Buenos días.
Por favor podrían indicar porque app swap.tendy.zone no permite cambiar old tendy en la app, swap.tendy.zone por sns tendy.
Buenos días. Usted ofreció un swap 1:1 old tendy por tendy sns, pero ni funciona swap.tendy.zone ni el equipo responde a porque no indexa los id y devuelve siempre 0 tendy!! Podría contestar cuando será posible hacer swap tendy??? Gracias
Hi there. Now that we are comming out of the holidays the team can srsly look into your issue. but it seems to be related to the two indexers running the swap. Your issue appears to be isolated to the single tx of the 3 tendys (which you said was a 5 token tx). We can pick up in the tg and get it going over the comming days. So far no other users have reported issues and many have successfully swapped so we are confident that it will work for you.
Thanks for the clarification.
To confirm: the test transaction was a small transfer from an NFID wallet, not from ICS, used only to check swap functionality.
The transaction is visible on-chain but not being processed by the swap, which indicates an indexer/backend issue rather than a user error.
I’ll wait for confirmation that the OLD → SNS TENDY swap and required identifiers are fully operational before doing any further tests.
Please update the group once this is resolved.
Hi Hugo / Bitcorn Labs team,
Additional issue detected: ICS is also blocked.
Current state:
- Balance reading issue: fixed.
- OLD (non-SNS) TENDY → SNS TENDY conversion: works.
- Post-swap cleanup: NOT working.
- ICS interactions: BLOCKED after swap attempts.
Observed behavior:
- OLD TENDY already converted still appears as available.
- Re-attempting swap triggers:
“The transaction indexer is not up to date.”
- ICS (wallet / swap interaction) becomes blocked or unusable after these failed states.
Impact:
- Inconsistent balances between ledger / indexer / UI.
- Users cannot determine real remaining OLD TENDY.
- Swap app allows repeated processing of already-converted amounts.
- ICS blockage prevents further actions.
Principal (II):
gtzsc-3opm7-gr6yr-7t6es-4tawm-3trm4-2vy3z-da5qy-2uidl-khvut-hae
Request:
- Clean or mark OLD TENDY balances as consumed after successful swap.
- Prevent re-processing of converted balances.
- Re-sync indexer with completed transactions.
- Unblock ICS once state is consistent.
This appears to be an indexer / state-cleanup issue, not a user error.
Thanks.
He cambiado old tendy perfecto, app tendy.zone funciona perfecto!!!
Gracias core team y a Hugo!!!
@aterga, I assume the ability for SNS’s to be able to decide what they want to be called without NNS oversight is actually a pretty big issue. Are DFINITY planning to do anything about this misrepresentation?
LOL cardano.org
He was selling metadata changes left and right, I didn’t think he would go thru with it, just shows how Dfinity not voting can only make things worst.
Just wait when they run out of tokens and start minting more.
Run out of tokens for what?
It’s a funny satire on the state of the network. I wouldn’t expect non English speakers to understand the humor involved with replacing “writing” with “writhing” like a snake.
it’s also obvious that some of your nerds are (un)initiated into the esoteric.
A writhing snake, a demiurge if you will, separating our worldly knowns from the magnificent with a mighty firmament.
feel free to push a proposal to change the meta data. The dao can vote.
Lorimer I’m really concerned that you didn’t take a voting position in tendys to protect the network.
@aterga can you please give lorimer some guidance on how if she doesn’t have a voting neuron her opinion is irrelevant.
Dexter come back sir