When the service starts the btc subscriber poller loops through all the unbonded and unbonding_requested delegations.
In testnet this is around 50K, so basically we spin up 50K go routines to register&monitor the spend (1 routine for each staking tx)
From the logs I can see we only received ~2k notifications logs link (search string "spent")
This doesn't seem normal. For example we should have received notification for this tx.
My hunch is b/c we are registering so many notifications there might be some connection limit on btc node but even in that case our service should show some err which didn't happen so idk 🤷