[TRACKING] Polkadot contributions

[al3mart]

This is a tracking issue used to maintain a list of issues or other items that the Paseo initiative has helped identifying / resolving within the Polkadot community

🔗 zboto Link

[al3mart]

paritytech/polkadot-sdk#10324

[al3mart]

paritytech/polkadot-sdk#11034

[tsenovilla]

Given there's not up to date info on how to get auto renewals, we created this guide: https://paseo.site/coretime and assisted the following teams understanding the process and enabling their autorenewals on Paseo:

• Shibuya (Astar).
• Aventus.
• Pendulum.
• EnergyWeb.
• Hyperbridge.

[tsenovilla]

We identified an issue on the onDemand pallet, that led to a huge growth ratio on the Paseo DDBB (~35 GB daily). The root cause was related to this storage item, which wasn't getting cleaned properly under certain constraints and ended up taking up to 6MB per block. This is specially harmful for archive nodes.

The bug

consume_index can only drain freed_indices when smallest_index is consumed first. If we got an index stuck in a FreeEntries or AffinityEntries queue and never gets popped, smallest_index can never advance, and every consumed order piles into freed_indices instead of being drained. Conclusion: One stuck entry blocks everything.

That's exactly what happened on Paseo, an index got stuck on AffinityEntries -> smallest_index was set to 2347695 while the first freed entry was set to 2347696 -> The BinaryHeap accumulated information for > 712K blocks (~49 days).

The solution

paritytech/polkadot-sdk#10184 <- Removes the affinity system as it is, so this shouldn't happen again.