Skip to content

[codex] Add multi-network TVL and contract ops#232

Draft
prissca wants to merge 2 commits into
vestflow-labs:mainfrom
prissca:codex/network-tvl-contract-ops
Draft

[codex] Add multi-network TVL and contract ops#232
prissca wants to merge 2 commits into
vestflow-labs:mainfrom
prissca:codex/network-tvl-contract-ops

Conversation

@prissca

@prissca prissca commented Jun 24, 2026

Copy link
Copy Markdown

What changed

  • Adds config-driven Testnet/Mainnet selection for the indexer and API via ?network=mainnet|testnet.
  • Adds parsed asset and created amount fields to indexed events, a scheduled TVL aggregation cache, and GET /stats/tvl plus the Next.js /api/stats/tvl proxy.
  • Removes the contract's storage-backed re-entrancy lock from claim and revoke, avoiding unnecessary instance storage writes in Soroban's single-invocation execution model.
  • Extends contract operations scripts with build/optimize/deploy/cost/upload/upgrade flows and documents the 48-hour WASM hash upgrade procedure.
  • Repairs a few small existing TypeScript issues surfaced by the build: missing imports and the duplicated createSchedule argument path.

Closes #229
Closes #213
Closes #209
Closes #230

Validation

  • npm --prefix indexer run build passes.
  • git diff --check passes.
  • npm run build gets through app compilation, then fails because the root app does not install better-sqlite3 for notification API routes and root TypeScript includes sdk/tsup.config.ts without the SDK package's tsup dependency installed at the root.
  • cargo test --manifest-path contracts/Cargo.toml and lefthook cargo_* checks could not run because cargo is not installed in this container.

Notes

  • The root package-lock.json had pre-existing local churn and is intentionally not included in this PR.
  • Mainnet indexing requires CONTRACT_ID_MAINNET to be configured before running a mainnet poller.

@drips-wave

drips-wave Bot commented Jun 24, 2026

Copy link
Copy Markdown

@prissca Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@libby-coder

Copy link
Copy Markdown
Contributor

resolve please

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

Labels

None yet

Projects

None yet

2 participants