👨🏻‍💻 Reorg extrinsics

[JuaniRios]

What?

Change the order, naming, and indexing of some extrinsics

Why?

Easier readability, and less guessing what the next index will be for new extrinsics

[JuaniRios]

• 💻 Run new benchmarks #352
• 🧪 Experiment hrmp weighing #351
• ✨ New CT Migration benchmarks #346
• 👨🏻‍💻 Reorg extrinsics #345 👈
• ✨ Multiple migration paths #341
• 💀 Add real weights to extrinsics #344
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Auto-assign PRs to author" took an action on this PR • (07/02/24)

1 assignee was added to this PR based on Juan Ignacio Rios's automation.

[vstam1]

I think it would be good to keep all the project transition (root) functions together for now. With the project simplifications we will probably move from automatic to semi automatic transitions, so the root function won't be necessary anymore. We will probably rename them and make them available for anyone to be called. However, we might change some protocol flow as well (merge auction rounds, merge community + remainder round and maybe remove decision logic) so we might have to do the reindexing all over again.

[lrazovic]

However, we might change some protocol flow as well (merge auction rounds, merge community + remainder round and maybe remove decision logic) so we might have to do the reindexing all over again.

In order to minimize the number of times we do a re-index, isn't it better to do it once the protocol simplification has been done?

[vstam1]

Yeah think so as well!

[JuaniRios]

However, we might change some protocol flow as well (merge auction rounds, merge community + remainder round and maybe remove decision logic) so we might have to do the reindexing all over again.

In order to minimize the number of times we do a re-index, isn't it better to do it once the protocol simplification has been done?

Right now there is no reason not to reindex. But that might change in the future. So I would rather reindex now since we know there are no side effects.

We already have the indexes all over the place

[vstam1]

I don't like that we probably have to reindex twice, but I won't block the pr if you are convinced

[JuaniRios]

Merge activity

• Jul 8, 8:35 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• Jul 8, 8:36 AM EDT: Graphite rebased this pull request as part of a merge.
• Jul 8, 8:37 AM EDT: @JuaniRios merged this pull request with Graphite.