DEMO MODE — placeholders are permitted · switch to SUBMISSION MODE to enforce real evidence requirements
01 — PACKAGE OVERVIEW
Ranger Basis Guard Vault · V4

Verification
Proof Package

Gov-grade deterministic verification system. Every material claim maps to evidence. Every output is traceable to input. No fabrication.

◈ NO-FABRICATION POLICY
This tool is designed to help you build a verifiable proof package. In Submission Mode, every field marked REQUIRED must contain real, onchain-checkable data. Placeholder values will block export. Any real submission should replace all example placeholders with actual addresses, transactions, and screenshots generated during the hackathon window.
--
Package Confidence Score
Completeness0%
Not yet validated

Quick Status

No fabrication · Real evidence only in submission mode

02 — EVIDENCE INGESTION
Capture + Normalize Evidence

Submit Vault Evidence

All fields are hashed on input and stored locally. Nothing is transmitted externally.

Vault Identity

Start and end timestamps of the hackathon window (ISO 8601)

PnL Formula Declaration

Net PnL = funding income + basis capture + reserve yield
        - trading fees - borrow costs - slippage - unwind costs
= Realized Net PnL
Actual realized during submission window only. No projections.
Declare the nature of ALL evidence in this package. Submission mode blocks PLACEHOLDER.

Sleeve Allocation Declaration

100%

03 — POSITION LIFECYCLE
Trade Evidence

Position History

Each position requires entry transaction, reason, and exit transaction. Reductions are optional but recommended for full traceability.


04 — EVIDENCE UNITS
Normalized Evidence Chain

Structured Evidence

Each evidence unit has a content hash, data type declaration, and validation status. Click any unit to expand details.

Run validation to generate structured evidence units

05 — VALIDATION ENGINE
Deterministic Pipeline

Validation Results

Identical inputs produce identical results. Each rule is checked independently and contributes to the confidence score.

Validation Checks

Click "Run Validation" to execute the validation pipeline

Integrity Chain

Integrity chain will be generated after validation

Risk Policy Compliance

Awaiting validation

06 — AUDIT LOG
Execution Trace

Audit Trail

Full trace of all validation runs, field changes, mode switches, and export attempts. Tamper-evident sequence.


07 — EXPORT + PRINT PACKAGING
Submission Artifact

Export Proof Package

Single-file self-contained artifact. Includes all evidence, hashes, validation results, and audit trace. Print-safe layout.

Pre-Export Checklist

⛔ EXPORT BLOCKED: One or more required fields contain placeholder data. Switch to Demo Mode to export an example package, or replace all placeholders with real evidence before submission export.
✓ Package ready for submission. All required fields contain real data. Validation passed.

Package Integrity Hash

Generated on each export. Use to verify the package has not been modified post-export.
Hash will be computed on export

Documentation

Vault Address — Solana public key of the deployed vault contract
Manager Wallet — EOA controlling vault operations during the submission window
Trade ID — Unique identifier per position (slug format recommended)
Entry TX Hash — Solana transaction signature for position entry
Entry Reason — Human-readable statement why the trade met admission gates
Realized Net PnL — Actual PnL computed via formula. No projections.