Merged
Conversation
…o be holesky :'((( many debugging later. This did work in the past though
reecepbcups
changed the title
Member
Author
|
NOTE: testnet/README.md is far out of date, latest README.md in the main of the repo is the current WIP. Goal is to transition the main README.md closer to the testnet/README.md without the headache of LOCAL & TESTNET incompatibility |
reecepbcups
changed the title
* create deployer & minimize start all * create operator script * generate and fund local aggregator * create agg + operator cleanup & start all * launch IPFS in start_all & rename to start-all-local * start aggregator * LOCAL WORKING YES * misc * refactor(testnet): set service uri standalone (allows for wavs to remain pre start phase) (#160) * feat: break apart setting the service URI and deploying service -> WAVS instance * latest wavs & wavs-wasi 0.4 for all components * merge of #162 into this * only use the uploaded wasi component for both local & testnet * fix: golang versions * fix: use wa.dev domain * feat: local warg server for `LOCAL` deployments (#163) * local oci * oras push package * move to local image * rm tmp * AHHH IT WORKED * tweaks * old * nit: http * finishing touches * 1 last * use upstream wavs image * fix: space * refactor: telemetry for testnet (#165) * Add support for tracing and metrics in default docker compose (#156) * Add jaeger and prometheus services to docker-compose * Add wasm-tools install to the readme * Add empty prometheus.yml file for metrics * Enable jaeger and prometheus in default wavs config * Add network mode host and sigkill to the jaeger and prometheus docker compose configuration * Update readme with instruction how to enable telemetry export * Add a note about accessing both jaeger and prometheus * Bring back default debug level in wavs.toml * Move jaeger and prometheus images to a separate docker compose configuration file * Add note in readme about the new telemetry docker compose file * Comment out by default the jaeger and prometheus usage in wavs config * Enable telemetry export by default; modify readme to simplify the instructions * latest * move telemetry to its own dir --------- Co-authored-by: Jakub Bogucki <jakub@moonbite.space> * minor * feat: latest middleware (wip for beta.3+) (#166) * working local deploy, better checks to avoid pain * private_key, better upload to ipfs for Testnet * remove legacy testnet/ dir * woo! working on testnet (all in this repo) * optionally include .env * show logs if failure to start * wip: holesky having issues, this should work * note * feat: add update threshold * use pinned wavs version * Add info that the values are to be configured in wavs.toml file * rm old script * run `operator-register` in verbose mode --------- Co-authored-by: Jakub Bogucki <jakub@moonbite.space>
* jq should use '' for zsh compat * upload-to-wasi-registry script * move sleep before WAVS_ENDPOINT check * move `PKG_NAMESPACE` out of the wasi registry script, move IPFS section * rm duplicate .env checks * fix: sleep time
Member
Author
|
Successful runs with:
Jakub and jake hit the same issues, got those resolved but still pending 2 upstream WAVS changes to get this finalized. Once merged docs can be focused on to match + update the GO / TS examples |
reecepbcups
commented
May 26, 2025
Member
Author
|
Getting this in as the new focus is docs & 3 of us have run through successfully. |
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
2 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.
ref #153 | Older version of this is found at https://github.com/lay3rlabs/testnet
Summary
Adds proper testnet support for holesky with the same setup flows for local. Testnet requires some external actions (funding the aggregator, operator, and deployer for example) so it properly polls for balance changes on testnet. However on the local version this is not required, and we magically (good devEx) set the account balance without interaction.
This means within 1 foundry flow we support 2 different deployment flows, both with very similar setups.
TODO
Stats