API: Data Syncing Improvements

[ifaouibadi]

Core Features

• create sync logic that starts from the block BCL was deployd
• create a table to keep track of synced blocks and how many transactions synced on each
• auto resume sync on restart from latest synced block

Better Debugging

• track which transactions has failed to sync
• create cron job to retry resolving the failed transaction
• if the failed tx, is create_community it should re-sync all transaction for that token

Faster Syncing

• on server restart & each hour, a cron job that should check and make sure all tokens are synced

[ifaouibadi]

#75
this issue happens when the API syncs a token that are not fully on the node.
or it has failed to pull the meta data due to API rate limiting

Solution:

• create a cron job that will run periodically to search for tokens without address and re-sync it
• create a cron job that will check for duplicate tokens and illuminate it
• on tx fail, it should retry after few secs (handled by block syncer & checker already)

[ifaouibadi]

#67

[ifaouibadi]

• API Error (OIN DEV)

[Nest] 18  - 06/10/2025, 8:10:24 AM   ERROR [ExceptionsHandler] Cannot read properties of null (reading 'id')
TypeError: Cannot read properties of null (reading 'id')
    at TokenPerformanceController.getTokenPriceMovement (/src/dist/transactions/controllers/token-performance.controller.js:53:28)
    at TokenPerformanceController.performance (/src/dist/transactions/controllers/token-performance.controller.js:37:37)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

[ifaouibadi]

•  API ERROR (on DEV)

[Nest] 18  - 06/10/2025, 8:16:28 AM   ERROR [TokensService] saleAddress is not a valid token address
null