Transactions got resetted for some reason #21

New issue

Open

opened 2026-04-06 09:28:52 +00:00 by mahmoud · 2 comments

mahmoud commented

2026-04-06 09:28:52 +00:00

Owner

Description

On the deployed devnet instance, the transactions.confirmed was +100 2 weeks ago, and now they are 15 transactions only. We need to debug to understand why we have such behavior

### Description On the [deployed devnet instance](https://br.dev.projectmycelium.com/status), the `transactions.confirmed` was +100 2 weeks ago, and now they are 15 transactions only. We need to debug to understand why we have such behavior

salmaelsoly self-assigned this

2026-04-06 10:27:01 +00:00

salmaelsoly commented

2026-04-06 14:24:58 +00:00

Member

wip:

reviewed the codebase only parts of db migration which may have lead to this behaviour since there is no any delete or processing happens on the db except read ops and adding records
the db only contain the 22 confirmed transactions, the bin was modified on 17-3 and restart happen may be this restart wiped the db not sure yet

### wip: - reviewed the codebase only parts of db migration which may have lead to this behaviour since there is no any delete or processing happens on the db except read ops and adding records - the db only contain the 22 confirmed transactions, the bin was modified on 17-3 and restart happen may be this restart wiped the db not sure yet

salmaelsoly commented

2026-04-08 08:28:09 +00:00

Member

after investigation:

The bridge was deployed on March 5. From that day until March 6, only 7 confirmed transactions were saved in the DB. From March 18 onward, 15 more confirmed transactions were saved — also matching the bin logs. There are zero records from March 6 to March 18 in the DB.
Attempted to verify outgoing SPORE transfers from the bridge account. However, the hero ledger have no indexer or explorer. The SPORE contract (spore.dev.hero) is a standard NEP-141 token that only exposes ft_balance_of, ft_metadata, and ft_total_supply — no transaction history.

### after investigation: - The bridge was deployed on March 5. From that day until March 6, only 7 confirmed transactions were saved in the DB. From March 18 onward, 15 more confirmed transactions were saved — also matching the bin logs. There are zero records from March 6 to March 18 in the DB. - Attempted to verify outgoing SPORE transfers from the bridge account. However, the hero ledger have no indexer or explorer. The SPORE contract (spore.dev.hero) is a standard NEP-141 token that only exposes ft_balance_of, ft_metadata, and ft_total_supply — no transaction history.

salmaelsoly added this to the ACTIVE project

2026-04-08 08:45:13 +00:00

salmaelsoly added this to the later milestone

2026-04-08 08:45:55 +00:00

salmaelsoly removed this from the ACTIVE project

2026-04-08 08:46:00 +00:00