pezkuwichain 718fea7cad fix: noter bot flip-flop bug — combine direct+pool before cache comparison ...

processAccount() was comparing direct staking against cache BEFORE
checking pool data. This caused a flip-flop: when cache=121K and
direct=100K, the bot submitted 100K (missing pool). Next scan it
detected the difference and submitted 121K. Every 5 minutes, forever.

Worse, when direct staking went to 0, the bot submitted 0 which
caused the pallet to delete StakingStartBlock — permanently removing
the user from tracking and zeroing their trust score.

Fix: collect ALL staking data (direct + pool) first, combine into
a single total, then compare against cache. Also adds queryFailed
flag to prevent downgrading stake when pool RPC query fails.

2026-02-28 01:32:55 +03:00

..

bot.js

fix: noter bot flip-flop bug — combine direct+pool before cache comparison

2026-02-28 01:32:55 +03:00

Dockerfile

feat: add noter bot service for staking score data submission

2026-02-17 01:32:51 +03:00

package-lock.json

feat: add noter bot service for staking score data submission

2026-02-17 01:32:51 +03:00

package.json

feat: add noter bot service for staking score data submission

2026-02-17 01:32:51 +03:00

setup-secret.js

feat: add noter secret setup script

2026-02-17 01:35:02 +03:00