Merge espresso code with celestia-integration #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: nomaxg <[email protected]>
Test node config fix
Local dev env with Espresso Sequencer
Use the broadcaster to deliver msgs if espresso mode is on
WIP: Run validator test node in espresso mode
Misc. espresso configuration options
Remove extra quotes around hotshot address
Set FS storage tag
more traffic
Add eth RPC to validation node
Sync upstream 2023-12-21
Update sequencer command line arguments
…-testnode into espresso-migration
Add full node example and test
* Remove enable espresso * Set the transaction streamer * fix build * Revert unnecessary changes --------- Co-authored-by: ImJeremyHe <[email protected]>
Espresso migration
* CI: print docker logs on failure * Pin version before LC ABI changes In EspressoSystems/espresso-sequencer#1939 the light client ABI changed and as a result we need to make changes in multiple places. The tracking issue for the changes in our nitro integration is https://github.com/EspressoSystems/nitro-contracts/issues/20 * Pin the espresso-dev-node image
update `orbit-actions` submodule
* merge * use latest instead of integration
* Add smoke test for finality node * add smoke test to ci * use wscat * use wscat * update bash * fix yaml * cleanup * cleanup * fix smoke test * fix smoke test
* Add smoke test for altlayer config * add docker compose down * update docker compose * cleanup * address comments * use full node as l2 url * re-run ci
* Do not transfer all supply to L2, leave some for L1-L3 bridging test * Bump blockscout pin to include ABI change * Bump nitro contracts * Disable rebuild of dev docker imgs w --build false * Make UpgradeExecutor L3 arbowner * Clarify logic around dev builds and rebuilding The concepts of using the dev builds for nitro and blockscout and rebuilding are now split into different variables internally to the test-node.bash script and can be controlled independently. The --dev flag by itself means to use the dev builds and to rebuild them. --no-build-dev-nitro and -no-build-dev-blockscout disable rebuilding the respective dev images. --no-build disables rebuilding the dev images and also rebuilding contracts related images, and the node images. This finer grained control saves time in the development cycle by allowing the user to rebuild only what is needed. An example command line to reinitialize the blockchain, use the dev images, but not rebuild anything except blockscout would be: ./test-node.bash --init --dev --no-build --build-dev-blockscout --blockscout Flags are read from left to right; flags to the right cancel the effects of flags to the left. * No skip_build * Add comment * Contracts and node images should rebuild on --init * Declare variable before use for -u flag * Change contracts to utils, add --force-build-utils * Upgrade to the consensus-v31 release * Update versions of contracts token-bridge and node These updated versions are needed to work with the consensus-v31 release. * fix: prysm config * fix: remove irrelevant changes * fix: pos * fix: working config * chore: reduce slot time to speed up deployment * fix: enable electra since genesis * fix: use newer geth * fix: remove --config-name=interop * fix: disable electra * fix: use latest geth * fix: add fee recipient * fix: enable deneb * fix: wait for tx sync * fix: format * feat: shorter slot for faster testing * fix: readd dev flags * fix: readd condition * fix: reduce diff * fix: docker compose * ci: test pos * ci: fix * ci: debug log * fix: also use 1337 for pos setup * Test commit * Test passing all the args through * Test tokenbridge and l3node startups * Changed the runner names * Cleanup in ci bash * Dont test for l3 tx if no l3node * Added l3 node comment * Add --l2-anytrust option to run in AnyTrust mode test-node.bash can now be run with --l2-anytrust which runs the l2 nodes in AnyTrust mode. It creates a committee of 2 daserver with assumed-honest set to 1, requiring successful stores of the batch data to both of them. Nitro nodes sync from a mirror daserver. All dasevers use local file storage for the batch data on their own volumes. BLS keys for the committee are automatically generated and the keyset is activated automatically on the SequencerInbox contract. * Use latest Nitro release v3.1.2 * Added some testing for l3node with custom fee token * Rename token6 * Set lower transfer amounts * Update to nitro v3.2.1 * Update blockscout pin to arbitrum branch * Add clabot config * Fix PR comments * merge upstream master * fix test-node.bash * add caldera smoke test * add smoke test to ci * fix smoke tests * delete clabot * remove unused vars --------- Co-authored-by: Goran Vladika <[email protected]> Co-authored-by: Lee Bousfield <[email protected]> Co-authored-by: Tsahi Zidenberg <[email protected]> Co-authored-by: Tristan Wilson <[email protected]> Co-authored-by: Pepper Lebeck-Jobe <[email protected]> Co-authored-by: Pepper Lebeck-Jobe <[email protected]> Co-authored-by: gzeon <[email protected]> Co-authored-by: gzeon <[email protected]> Co-authored-by: Chris Buckland <[email protected]> Co-authored-by: Tristan-Wilson <[email protected]> Co-authored-by: Tsahi Zidenberg <[email protected]> Co-authored-by: Harry Kalodner <[email protected]>
Sync nitro v3.2.1
Causes our nitro docker build to fail https://github.com/EspressoSystems/nitro-espresso-integration/actions/runs/11727749989/job/32669575639 Switch to https URL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #<ISSUE_NUMBER>
This PR:
This PR does not:
Key places to review: