Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset-Hub Migration: Investigate throughput #6273

Open
2 tasks
ggwpez opened this issue Oct 29, 2024 · 1 comment
Open
2 tasks

Asset-Hub Migration: Investigate throughput #6273

ggwpez opened this issue Oct 29, 2024 · 1 comment
Assignees

Comments

@ggwpez
Copy link
Member

ggwpez commented Oct 29, 2024

Estimate how many messages and how much time we will need to migrate all pallets to the AH.

First investigations were promising with the indices pallet. Now going to test with real state on AH to measure the PoV sizes in the collator logs. My approach currently is to migrate pallets and then see how fast it is. Pallet-indices was very fast, next going to try pallet-balances.

Issues identified so far:

  •  DMP delivery fee increases once the relay starts spamming
  • AH can silently drop messages if they are too big. Need to safeguard against this on the relay side already.
@ggwpez ggwpez self-assigned this Oct 29, 2024
@burdges
Copy link

burdges commented Oct 30, 2024

You could go the other way: Fork the relay chain into a parachain, upgrade that fork into AssetHub v2, with a migration, and the message over all the AssetHub v1 accounts.

I'd honestly just not think of this as messaging though: Freeze realy chain accounts, copy that state root to AssetHub as a subtree, do a state migration in AssetHub from that subtree into AssetHub accounts, and O(1) drop that state tree when done. All told only one "message": the state root hash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants