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.

Sign up for GitHub

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

Jump to bottom

start additional services before full mev components are launched #168

Closed
h4ck3rk3y opened this issue Aug 30, 2023 · 4 comments
Closed

start additional services before full mev components are launched #168

h4ck3rk3y opened this issue Aug 30, 2023 · 4 comments
Assignees
@kamilchodola

Comments

@h4ck3rk3y
Copy link
Collaborator

MEV requires epoch 1 and @barnabasbusa suggested we can launch additional services before waiting for this to happen. This makes sense to me.
@h4ck3rk3y
Copy link
Collaborator Author

@kamilchodola is on this!

@kamilchodola
Copy link
Contributor

Just tested it once and seems to be working fine but need more tests

@kamilchodola kamilchodola mentioned this issue Sep 20, 2023
Merged
h4ck3rk3y pushed a commit that referenced this issue Sep 20, 2023
@kamilchodola
feat: Add Tx_spamer_params and move MEV to the bottom of main.star (#208
23628b2 
)

PR adds a possibility to push custom params to Tx_Spammer.

tested with flag --txcount=100 - Looking at Tx_Spammer logs change is
applied.
Also addressing #168

---------

Co-authored-by: Kamil Chodoła <[email protected]>
@h4ck3rk3y
Copy link
Collaborator Author

@kamilchodola i had to revert the previous change as it was causing issues with the mev-flood contracts being deployed.

@h4ck3rk3y
Copy link
Collaborator Author

MEV doesn't require epoch 1 so this isn't painful anymore, MEV starts at epoch 0. There were some problems with mev-flood init if we changed the ordering; closing this. Will open if people want the ordering to change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kamilchodola kamilchodola

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@h4ck3rk3y @kamilchodola