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

Make Solana ready faster by improving chain registration submissions #1826

Closed
evan-gray opened this issue Oct 29, 2022 · 1 comment · Fixed by #1828
Closed

Make Solana ready faster by improving chain registration submissions #1826

evan-gray opened this issue Oct 29, 2022 · 1 comment · Fixed by #1828
Assignees
Labels

Comments

@evan-gray
Copy link
Contributor

Expected Behavior

The containers in tilt should become usable as fast as reasonably possible. If there are obvious optimizations to be made with minimal complexity, they should be made.

Current Behavior

Every chain registration is performed in series by running worm submit $VAA --chain solana --network devnet

worm submit $VAA --chain solana --network devnet

Possible Solution

worm submit performs multiple transactions per VAA and uses a confirmed connection to submit them. Perhaps there are easy devnet-specific improvements to make there. Alternatively, could the registration accounts be generated / dumped and restored? The only downside to that approach would be that the registration flow of the contracts and worm submit wouldn't be tested in this way anymore.

Context (Environment)

Tilt

@kcsongor
Copy link
Contributor

🤔

@kcsongor kcsongor self-assigned this Oct 29, 2022
kcsongor pushed a commit that referenced this issue Oct 29, 2022
Doing so reduces the time it takes to do the registrations from ~90s to
~9s, a 10x improvement.
evan-gray pushed a commit that referenced this issue Oct 29, 2022
Doing so reduces the time it takes to do the registrations from ~90s to
~9s, a 10x improvement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants