Conversation
Sneh1999
commented
Nov 24, 2024
| [ | ||
| ./smoke-test.bash, | ||
| ./smoke-test-l3.bash, | ||
| ./smoke-test-nitro-simple.bash, |
Author
There was a problem hiding this comment.
we dont need all these tests for celestia integration
Member
|
Thanks! @Sneh1999 |
Author
Sorry @ImJeremyHe, we had to get a working demo ready for caldera and I had to test our existing code. There are still a lot of improvements we can do to this lol |
2 tasks
In this commit, a dummy TEE Verifier address is being used, we will use a correct one later
Fix the batch poster
* Update migration test for TEE integration This commit updates the migration-test.bash script to reflect the new migration flow for the TEE integration. It also adds some utility scripts and updates some exsisting example files to assist in the migration test. * Remove changes to docker-compose.yml * Respond to review feedback
* Update espresso image to point to integration (#83) * Update espresso image to point to integration * update espresso dev node * Update light client address --------- Co-authored-by: Jeremy <297323986@qq.com> * add blobSchedule for new genesis creator requirement (#84) * add blobSchedule for new genesis creator requirement * Rename (cherry picked from commit 01b9f3a) * Fix caff node test (#85) * WIP * WIP * small fixes * rename to caff * fix * use bc for big numbers * Send transaction through caff node --------- Co-authored-by: Sneh Koul <snehkoul1999@gmail.com> (cherry picked from commit bfaaf1d) * Add EspressoTEEVerifier address (#86) * Add EspressoTEEVerifier address * Fix the TEE address --------- Co-authored-by: Jeremy <297323986@qq.com> (cherry picked from commit b1ce7e1) * Fix caff node test (cherry picked from commit 589b44b) * Remove simple test --------- Co-authored-by: Sneh Koul <35871990+Sneh1999@users.noreply.github.com>
* create celestia-migration-test script * work on migration test for celestia-2.1.3 * Update to celestia-migration-test to start on espresso contracts * update orbit-actions submodule * add celestia-migration-test.bash and associated .env file * fix orbit-actions subodule commit * Rename celestia-2.1.3-migration-test.bash script
* Fix caff node test (#100) * Fix caff node test * comment out l3 * fix launch bash * fix caff node test * cleanup * fix smoke test * fix migration test * fix l3 test * comment out l3 test * Restart sequencer when it hangs --------- Co-authored-by: Jeremy <yiliang.he@qq.com> * update celestia contracts version * add migration ci check * fix docker file * Fix l3 test * Fix caff node * Correct the configuration --------- Co-authored-by: Sneh Koul <35871990+Sneh1999@users.noreply.github.com> Co-authored-by: Jeremy <yiliang.he@qq.com>
* Update config.ts * Change defaults and add Celestia DA Server * Do not transfer all supply to L2, leave some for L1-L3 bridging test * 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 * Update ci.yml * Simple local script on Arabica testnet Simple local script on Arabica testnet. Run `./celestia-start.sh`, can pass `--validate` for WASM validation and `--anytrust` to spin up a local anytrust setup in order to test fallbacks and other things * Update .gitignore * fix cancun and light up * containerize and simplify * Update docker-compose.yaml * Update docker-compose.yaml * Update docker-compose.yaml * Fix caff node test (#100) * Fix caff node test * comment out l3 * fix launch bash * fix caff node test * cleanup * fix smoke test * fix migration test * fix l3 test * comment out l3 test * Restart sequencer when it hangs --------- Co-authored-by: Jeremy <yiliang.he@qq.com> * update celestia contracts version * add migration ci check * fix docker file * Fix l3 test * Fix caff node * Correct the configuration * add flooding script * Update Dockerfile * update docker image * fix image * Remove redundancy * update docker compose indenting * Remove unused fallback urls * update latest devnode image * remove platform specification --------- Co-authored-by: Diego <diego@celestia.org> Co-authored-by: Goran Vladika <goran.vladika@gmail.com> Co-authored-by: Tsahi Zidenberg <65945052+tsahee@users.noreply.github.com> Co-authored-by: Tristan Wilson <twilson@offchainlabs.com> Co-authored-by: Pepper Lebeck-Jobe <pepper@offchainlabs.com> Co-authored-by: Pepper Lebeck-Jobe <eljobe@gmail.com> Co-authored-by: gzeon <hng@offchainlabs.com> Co-authored-by: gzeon <im@gzeon.dev> Co-authored-by: Chris Buckland <cpbuckland88@gmail.com> Co-authored-by: Tristan-Wilson <87238672+Tristan-Wilson@users.noreply.github.com> Co-authored-by: Lee Bousfield <ljbousfield@gmail.com> Co-authored-by: Tsahi Zidenberg <tsahi@offchainlabs.com> Co-authored-by: Harry Kalodner <harry@offchainlabs.com> Co-authored-by: Joshua Colvin <jcolvin@offchainlabs.com> Co-authored-by: Diego <31937514+Ferret-san@users.noreply.github.com> Co-authored-by: Sneh Koul <35871990+Sneh1999@users.noreply.github.com> Co-authored-by: Jeremy <yiliang.he@qq.com>
ImJeremyHe
pushed a commit
that referenced
this pull request
Aug 11, 2025
Bump nitro-contracts and token-bridge
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR outlines the difference in our celestia-integration vs the integration branch.