Migrate transaction-building to evm-actions-api (v0.1.0) - #1
Merged
Conversation
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
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.
Summary
Makes
nestthe canonical Plume CLI for both human (private-key broadcast) and agentic (--dry-run -o json+--address) use by moving transaction-building onto theevm-actions-apiHTTP service.deposit/withdrawthroughmint/build-txandredeem/build-tx; keep cross-chain boring deposit-and-bridge built locally behind--bridge.EvmActionsClient(retry-once on 5xx, clean 4xx{error}surfacing) alongside the untouchedNestApiClient.bridge(local LayerZero OFT send),claim {pending,submit},instant-redeem {quote,liquidity,submit},update-redeem {pending,submit},auto-claim {status,enable,disable}.TxBundlestable JSON contract (decimalvalue, per-routelabelset,extrapassthrough) for agentic signing; drop the private-key requirement for dry-runs (use--address).cargo clippy --all-targets -- -D warningsclean.boringNestvault type the API returns fornest-treasury-vault.New env var:
EVM_ACTIONS_API_BASE(defaulthttps://api-dev-test.nest.credit/v1/actions). Chains served by the API are pinned inACTIONS_API_CHAINS(1, 56, 9745, 42161, 98866; no Worldchain).Test Plan
cargo test(19 unit/wiremock tests),cargo clippy --all-targets -- -D warnings,cargo build --release— all greennest-treasury-vault(boringNest) parses, decimals resolve, requests reach the API, 4xx errors surface cleanlyETHEREUM_RPC_URLto confirm happy-path output:deposit --vault nest-treasury-vault --asset 0x55d3…(USDT) --amount 1 --chain bsc --address <you> --dry-run -o json→ 2-tx bundle,shareDecimals: 18deposit --vault nest-elixir-vault --asset 0xa0b8…(USDC) --amount 1 --chain ethereum --address <you> --dry-run -o json→ 2-tx boring bundle,shareDecimals: 6bridge --vault nest-treasury-vault --shares 0.1 --from-chain ethereum --to-chain plume --address <you> --dry-run -o json→ 1-tx send bundle, non-zerovalueclaim pending --vault nest-treasury-vault --redemption-asset <valid plume asset> --user <you> --chain plume -o json→ claimable-shares structureRelease: tag
v0.1.0after merge to build the three platform tarballs (aarch64-darwin, x86_64-darwin, x86_64-linux-gnu).