By Providencia Onchain (VIIO x Climate Future)

Providencia Onchain

SCF #42

$37.5K

Build

Awarded

Products & Services

VIIO’s mission is to bring Providencia on-chain by making track investments transparent, sustainable, and auditable on Stellar through our existing infrastructure. This Integration Track submission funds the public transparency dashboard, attribution registry, and reconciliation layer needed to show where sponsor-funded track money is being invested. The scope is intentionally narrow: dashboard, proof, and reconciliation only. The payments app, merchant onboarding, wallet connectivity, and point-of-sale rollout are out of scope.

The dashboard is the first visible layer of that mission because it lets sponsors, operators, and local partners see where track funds are going before any broader system expansion.

Public Transparency Dashboard

A public reporting layer showing batch totals, line-item statuses, category allocations, CSV exports, and transaction-hash-linked proof for the first track.

Stellar integration: Every disbursement executed via the Stellar Disbursement Platform surfaces its mainnet transaction hash directly in the dashboard, so any viewer can click through to Stellar Expert and verify the on-chain payment.
Project impact: Replaces PDF reporting with a live, verifiable source of truth — funders, community members, and auditors can independently confirm where each peso went without waiting on Climate Future to compile reports.

Track Attribution Layer

A metadata and reconciliation layer linking each line item to a node, track, milestone, and recipient category so the first Providencia track can be traced end to end.

Stellar integration: SDP payment records (tx hash, amount, asset, timestamp, recipient) are the anchoring key — every attributed line item carries its Stellar hash as the immutable reference.
Project impact: Turns scattered field spend into a structured, queryable ledger where "who received what, for which milestone" is answerable in seconds instead of days — the missing backbone for the dashboard and all downstream reporting.

Reconciliation and Proof Pack

A traceability layer joining attribution data with source records, surfacing matched and unmatched items, and publishing the proof pack for the first track.

Stellar integration: Stellar transaction hashes serve as the cryptographic join key between off-chain source records (invoices, receipts, field logs) and on-chain disbursements; the published proof pack includes the full hash list for third-party verification.
Project impact: Closes the audit loop — gives Climate Future, SCF, and external reviewers a single artifact proving the track was funded, executed, and reconciled, setting the reusable template for every subsequent Providencia track.

Risk Controls and Scoping Guardrails

Scope lock: only the dashboard, attribution layer, and proof layer are claimed in this submission.
No fake full launch: the first live proof is a scoped track batch, not a totalized consumer product rollout.
Existing VIIO treasury rails remain supporting infrastructure rather than becoming new grant scope.
The public dashboard is evidence-oriented: it publishes what is verified, not inflated roadmap fiction.
Anti-grant-dependency: funded output is a reusable operating layer, not a one-off narrative deck. VIIO self-funds ongoing operational costs beyond the pilot period.

Explicit Sequencing After This Grant

Install the rail under the Integration Track.
Use that rail to run and prove the first Providencia-aligned track.
Apply later under Open Track for the broader first-node deployment rather than forcing everything into this submission.

Repository and Maintenance

The GitHub URL will be finalized before portal submission so the implementation can be reviewed from a single repository link.
The repository should contain the dashboard implementation, architecture diagrams, and deployment notes tied to the Stellar integration scope.
VIIO will own maintenance during the build period and after launch, using the same engineering team that is already listed in the submission.

Requested Budget

$37.5K

Traction Evidence

Current Traction

VIIO (Payment Infrastructure)

$326M total payment volume (last twelve months)
650 active SME accounts
11,900 operations processed
~$27K average transaction size
Infrastructure partners: FV Bank, BVNK, BBVA, Visa, Fireblocks, Chainalysis

Climate Future (Field Operations in Providencia)

Multi-year field operations on the island
~1,500 trees/shrubs planted
420+ children engaged in educational programs
Ongoing local execution, merchant relationships, and impact reporting
~30 dogs + 50 cats adopted and ~95% of known street dogs regularly supported/adopted.
Docs: https://drive.google.com/drive/folders/1x6vjbikVLsfO8Z7aBV4FeCM0Nu-6XTXe?usp=sharing

Websites: https://viio.me | https://www.climatefuture.de

Tranche 1 (Deliverable Roadmap) - MVP

Tranche 1: Foundation and Testnet Install

$7,500 / 20%

Due May 20, 2026 (+6 weeks)

D1.1 — Dashboard environment setup + source data environment (22h / $2,750): single-tenant testnet environment, organization setup, role model, attribution database, CI/CD baseline.
D1.2 — VIIO batch adapter + source mapping (20h / $2,500): adapter that turns approved track batches into dashboard-ready records and produces stable external IDs.
D1.3 — Project coordination (10h / $1,250): release management, cross-team syncs, delivery tracking.
D1.4 — DevOps / CI/CD baseline (8h / $1,000): deployment pipelines, environment config, release references.

Acceptance evidence:

Deployed testnet environment with immutable build/release references.
One successful named batch created through the VIIO adapter and reflected in the dashboard.
Test evidence showing created batch, uploaded source records, resulting statuses, and linked Stellar transaction references.

Tranche 2 (Deliverable Roadmap) - Testnet

Tranche 2: Attribution and Public Transparency

$11,250 / 30%

Due July 1, 2026 (+12 weeks)

D2.1 — Track attribution schema + registry (28h / $3,500): registry for node_code, track_code, milestone_code, recipient category, and line-item external IDs keyed to source records.
D2.2 — Public transparency dashboard + exports (28h / $3,500): public view showing batch totals, statuses, category breakdowns, and transaction-linked exports for the first Providencia track.
D2.3 — Reconciliation + alert baseline (12h / $1,500): join logic between local attribution and source data, plus error and mismatch reporting.
D2.4 — Project coordination (12h / $1,500): cross-team delivery management, stakeholder reporting.
D2.5 — Local field preparation (10h / $1,250): Providencia recipient verification, local partner onboarding prep.

Acceptance evidence:

Public dashboard URL (or staging URL) with an exportable batch view.
At least one fully traced batch where local attribution fields resolve cleanly against source records.
Reconciliation output showing matched/unmatched items and operator action path for exceptions.

Tranche 3 (Deliverable Roadmap) - Mainnet

Tranche 3: Mainnet Proof and Providencia Track Readiness

$15,000 / 40%

Due August 12, 2026 (+18 weeks)

D3.1 — Mainnet deployment + hardening (32h / $4,000): production environment hardening, funded distribution account workflow, release controls, runbook for mainnet batches.
D3.2 — First live Providencia track batch (24h / $3,000): execution of first scoped sponsor-funded batch for approved Providencia recipients, with proof artifacts and operator review.
D3.3 — QA + proof operations (20h / $2,500): end-to-end testing, failure injection, proof verification, operational acceptance.
D3.4 — Project coordination + handoff (20h / $2,500): final delivery management, proof pack, operating notes for next track.
D3.5 — Local field execution (24h / $3,000): Providencia on-ground activation, partner coordination, local verification, impact reporting.

Acceptance evidence:

Mainnet environment and release bundle for the live integration.
One live batch with line-item statuses and transaction-linked proof published to the transparency layer.
Versioned proof pack and operating notes showing the rail is reusable for the next track.

Team

The implementation is a joint team combining VIIO’s product and delivery organization with Climate Future’s on-the-ground execution in Providencia. VIIO contributes treasury operations, backend integration, release engineering, compliance-minded reporting, and dashboard delivery. Climate Future contributes node design, beneficiary mapping, local operator coordination, reporting, and stewardship of the first Providencia track.

VIIO:

Technical Build and Operations
Product and release management
Backend / integration engineering: source-data ingestion and proof-layer support
Data / dashboard engineering: attribution registry, transparency layer
DevOps / SRE: CI/CD, monitoring, environment management
Compliance and operational controls