Accounts that failed to be inserted into the bags-list due to locking.
These accounts will be processed with priority in on_idle or via rebag extrinsic.
Note: This storage is intentionally unbounded. The following factors make bounding
unnecessary:
The storage usage is temporary - accounts are processed and removed in on_idle
The pallet is only locked during snapshot generation, which is weight-limited
Processing happens at multiple accounts per block, clearing even large backlogs quickly
An artificial limit could be exhausted by an attacker, preventing legitimate
auto-rebagging from putting accounts in the correct position
We don't store the score here - it's always fetched from ScoreProvider when processing,
ensuring we use the most up-to-date score (accounts may have been slashed, rewarded, etc.
while waiting in the queue).
Accounts that failed to be inserted into the bags-list due to locking. These accounts will be processed with priority in
on_idleor viarebagextrinsic.Note: This storage is intentionally unbounded. The following factors make bounding unnecessary:
on_idleWe don't store the score here - it's always fetched from
ScoreProviderwhen processing, ensuring we use the most up-to-date score (accounts may have been slashed, rewarded, etc. while waiting in the queue).