Repository navigation
Vault history, internal diagnostics console, and verified contract registry - #356
Merged
Merged
Conversation
…ction Detail Hist Closes Zenith-options#261
…nly Diagnostics Closes Zenith-options#262
…n-Chain Address R Closes Zenith-options#264
|
@sundayjob996 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! 🚀 |
- .github/workflows/ci.yml: merged [markers] — model resolved the conflict markers - src/env.ts: merged [markers] — model resolved the conflict markers - src/lib/api/vaults.ts: merged [markers] — model resolved the conflict markers Co-authored-by: Simple Agent <agent@simple.dev>
- .github/workflows/ci.yml: merged [markers] — model resolved the conflict markers - src/env.ts: merged [markers] — model resolved the conflict markers - src/lib/api/vaults.ts: merged [markers] — model resolved the conflict markers Co-authored-by: Simple Agent <agent@simple.dev>
- src/lib/api/vaults.ts: merged [markers] — model resolved the conflict markers Co-authored-by: Simple Agent <agent@simple.dev>
- src/lib/api/vaults.ts: merged [markers] — model resolved the conflict markers Co-authored-by: Simple Agent <agent@simple.dev>
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
Vault history, internal diagnostics console, and verified contract registry
What was solved
#261 — Build Vault Transaction Receipts and a Transaction Detail History Surface
Add a vault-aware transaction history surface with durable per-vault/per-account receipts for vault actions (deposits, redemption requests, redemptions, epoch payouts, fee charges), showing type, amount, share delta, NAV at execution, fee, status, and a linkable Stellar tx hash, with designed empty/loading/degraded states and clear next steps for failed/stuck actions.
Addressed:
#262 — Build a Depositor Support Console With Read-Only Diagnostics
Add an internal, strictly read-only depositor support console (App Router route under src/app/) that looks up vaults by vault ID, Stellar account, tx hash, or receipt/idempotency key and returns one consolidated diagnostic view showing reconciled on-chain vs backend state with explicit drift. Access is gated to internal deployment, authenticated via existing admin auth, uses a read-scoped diagnostics client (read-only enforced at API surface, not UI), and every lookup is written to the immutable audit log. Out of scope: operator console changes and depositor session impersonation.
Addressed:
#264 — Implement Verified-Build Attestation and an On-Chain Address Registry for Vault Contracts
Add reproducible verified-build attestation and a canonical on-chain address registry for vault contracts: pin the toolchain and build scripts so a tagged revision yields a byte-identical WASM hash, have the release pipeline emit a signed attestation (hash, revision, git ref, toolchain, builder identity) published with the artifact, maintain a versioned machine-readable registry mapping network → contract ID → verified WASM hash → audit revision as the single source consumed by src/env.ts, the SDK, and docs, and add a CI drift check that fails when a configured contract ID's on-chain code hash diverges from the registry (with unverified/pending-audit revisions visibly marked).
Addressed:
Changes
src/lib/api/vaults.ts(modify).github/workflows/ci.yml(modify)src/lib/store/wallet.ts(modify)src/env.ts(modify)Approach
Issues
Closes #261
Closes #262
Closes #264