Handle case where wallet has not enough SPORE #10

Open
opened 2026-03-16 21:28:48 +00:00 by scott · 2 comments
Member

If there wasn't enough SPORE in the wallet to be sent out to a user, they see an error but also a "finalized" status:

image

I think it would be better to refund the TFT to the user in this case and advise them to contact support.

We need to also understand in this case if the user will be paid when the wallet is topped up with SPORE, or if we need to pay out manually.

If there wasn't enough SPORE in the wallet to be sent out to a user, they see an error but also a "finalized" status: ![image](/attachments/618d6603-cf9e-4b14-9c8d-da5c9cf6e615) I think it would be better to refund the TFT to the user in this case and advise them to contact support. We need to also understand in this case if the user will be paid when the wallet is topped up with SPORE, or if we need to pay out manually.
mahmoud added this to the ACTIVE project 2026-03-17 09:22:15 +00:00
Member
  • The "finalized" status the user sees is from TFChain (the Substrate block is finalized), not from the daemon
  • For old transactions, the user is NOT paid automatically. The tx is stuck at FAILED with retries >= 5. The only way to pay them is manual

To be added:

  • mark insufficient balance failure as refundable
  • check balance before

For manual retrying failures:

  • The retry CLI resets retries=0 in the DB, but the daemon's cursor has already moved past the original block. The event is never re-polled, so nothing happens.
- The "finalized" status the user sees is from TFChain (the Substrate block is finalized), not from the daemon - For old transactions, the user is NOT paid automatically. The tx is stuck at FAILED with retries >= 5. The only way to pay them is manual To be added: - mark insufficient balance failure as refundable - check balance before For manual retrying failures: - The retry CLI resets retries=0 in the DB, but the daemon's cursor has already moved past the original block. The event is never re-polled, so nothing happens.
Author
Member

Tracking the manual payouts here: mycelium/circle_ops#706

Tracking the manual payouts here: https://forge.ourworld.tf/mycelium/circle_ops/issues/706
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_tfspores#10
No description provided.