Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2026 Stellar Development Foundation
Subscribe to the Newsletter
By PigFi
1. DeFindex Multi-Vault Integration
PigFi will expand its existing DeFindex integration into a configuration-driven, multi-vault savings experience supporting its current vault and at least two additional DeFindex vaults. The funded work is limited to PigFi’s application-level integration: a reusable backend vault registry and adapter, normalized transaction-state handling, mobile vault discovery and detail screens, embedded-wallet transaction preparation and authorization, portfolio synchronization, risk and liquidity disclosures, runtime configuration controls, automated tests, and integration documentation.
PigFi will not create, modify, audit, or maintain Soroban smart-contract code under this award. DeFindex supplies and maintains the vault contracts, strategies, contract interfaces, and related tooling. Any vault deployment or configuration will use DeFindex-provided contracts and tooling. PigFi’s work will consist of selecting compatible deployed or configurable vaults, mapping their contract IDs, assets, strategies, and parameters into PigFi’s integration layer, and enabling users to interact with them through the PigFi applications.
PigFi’s existing educational experience may continue as an independently funded product feature, but creating or expanding educational content is outside the scope and budget of this SCF Build submission.
2. Multi-Country & Multi-Provider LATAM Ramps
PigFi will expand beyond its current BRL/Pix experience into Brazil, Argentina, Colombia and Mexico through a provider-neutral ramp architecture using BlindPay and Etherfuse. The funded work will normalize KYC, quotes, fees, payment rails, orders, webhooks and reconciliation across providers and markets. Stellar serves as the settlement layer connecting local currency to on-chain assets and back. Spanish localization will be implemented across onboarding, ramps, vaults and portfolio flows, enabling PigFi to serve Spanish-speaking users through one consistent product architecture.
3. Production Mainnet, Observability & On-Chain Adoption
The funded integrations will be released in PigFi’s production Android and iOS applications on Stellar mainnet. PigFi will strengthen monitoring and reconciliation across ramp providers, Stellar transactions and DeFindex contracts, while adding attributable on-chain measurement for real user activity. This creates a measurable end-to-end journey from local currency → Stellar asset → DeFindex savings → local currency and gives PigFi the infrastructure required to scale consumer adoption across Latin America.
$96.1K
PigFi is live on Stellar mainnet with real users, measurable on-chain activity, and active mobile distribution.
Our public Dune dashboard and proprietary dashboard show US$ 12,791.34 in TVL, 51 deposit transactions, 28 withdrawal transactions, US$ 13,707.69 deposited all-time, and US$ 922.54 withdrawn. PigFi has recorded activity from 57 individual Stellar wallets.
https://dune.com/mayconweb37901/cofrinho-pigfy-vault-dashboard
https://pigfi-analytics-production.up.railway.app/
PigFi has 59 registered users (Privy), is available through Google Play Open Testing, is in iOS Closed Testing, and has 107 people on the iOS waitlist.
Google Play:
https://play.google.com/store/apps/details?id=com.pigfi.app
Our core team has been building together for more than one year, with a consistent commitment to the Stellar ecosystem. Our journey progressed from participating together in Meridian, to Stellar 37 Graus, where we actively developed PigFi, followed by an InstaAward, where we successfully completed the agreed deliverables, and then the Stellar Summit, where we continued refining and improving the product.
We also have signed commercial agreements with BlindPay and Etherfuse, strengthening our ability to expand local-currency access across Latin America.
Supporting evidence including waitlist and commercial agreements:
https://drive.google.com/drive/folders/1q1OAqtYCsIGuTJSMARUkKomStoMsEweM?usp=sharing
Brief description
Expand PigFi’s existing DeFindex integration into a configuration-driven multi-vault savings experience supporting its current vault and at least two additional DeFindex vaults.
PigFi will build the custom application-level components required to support multiple DeFindex vaults through one reusable integration. This work includes a backend vault registry and DeFindex adapter, normalized vault metadata and transaction states, mobile vault discovery and detail views, embedded-wallet transaction preparation and authorization, portfolio synchronization, versioned risk disclosures and acknowledgments, runtime activation controls, automated tests, and technical documentation.
PigFi will not author, modify, audit, own, or maintain Soroban smart-contract code under this award. DeFindex supplies and maintains the standard vault contracts, strategy contracts, interfaces, factory contracts, and deployment and configuration tooling.
If an additional vault instance must be created, it will be instantiated and configured using DeFindex-provided factory contracts, standard vault contracts, interfaces, and tooling. This work is classified as DeFindex configuration, not PigFi-authored smart-contract engineering. It may include selecting the supported asset and strategy, assigning required vault roles, setting supported parameters, recording the resulting contract IDs, performing the initial configuration and rebalance, and validating the configured vault.
For each additional vault, PigFi will select a compatible primary or fallback candidate documented in the technical architecture, confirm its availability with DeFindex, map its vault and strategy contract IDs, asset, parameters, and operational metadata into PigFi’s integration layer, and validate end-to-end deposits and withdrawals through the user’s embedded Stellar wallet.
Before a user’s first deposit into each newly integrated vault, PigFi will display a vault-specific risk disclosure and require explicit acknowledgment. The disclosure will describe the applicable asset, liquidity, withdrawal, variable-yield, smart-contract, oracle or pricing, issuer, underlying-pool, backstop, and protocol-dependency risks in plain language. The acknowledgment is a product risk-control mechanism.
Vault selection will remain entirely user-directed. PigFi will not automatically select or recommend a vault and will not store, access, or control users’ private keys.
Creating or expanding educational materials, lessons, knowledge checks, learning progression, or education-based access requirements is outside the funded scope of this deliverable.
Scope boundaries
PigFi custom engineering includes:
- reusable backend vault registry and DeFindex adapter;
- normalization of vault metadata and transaction states;
- mobile vault discovery and detail interfaces;
- deposit and withdrawal transaction preparation;
- explicit authorization through the user’s embedded Stellar wallet;
- transaction-status and portfolio synchronization;
- vault-specific, versioned risk disclosures and acknowledgment records;
- enforcement of acknowledgment before a user’s first deposit into each new vault;
- runtime vault activation, deactivation, and metadata controls;
- error handling, automated integration tests, monitoring, documentation, and completion evidence; and
- production deployment of the application-level integration.
DeFindex configuration includes:
- selection of at least two compatible DeFindex-supported vault candidates;
- use of DeFindex-provided factory contracts, standard vault contracts, interfaces, and tooling;
- vault instantiation where a new instance is required;
- configuration of supported assets, strategies, roles, fees, and other applicable parameters;
- initial strategy allocation or rebalance where required;
- recording and mapping the resulting vault, strategy, and asset identifiers; and
- technical validation of the configured DeFindex vaults.
Out of scope includes:
- authoring or modifying Soroban smart-contract code;
- deploying PigFi-authored smart contracts;
- creating or modifying DeFindex strategy logic;
- auditing DeFindex or other third-party contracts;
- owning or maintaining DeFindex protocol contracts or strategies;
- remediating vulnerabilities in third-party protocols, pools, assets, or oracle services; and
- creating or expanding educational materials, modules, lessons, knowledge checks, or education-based access requirements.
How completion will be measured
PigFi’s existing DeFindex vault and at least two additional DeFindex vaults operate through the common PigFi vault registry and adapter.
Primary and fallback candidates for the additional vaults are documented in the technical architecture submitted with this application.
The two additional vaults are instantiated or configured using DeFindex-provided factory contracts, standard vault contracts, strategies, interfaces, and tooling. No PigFi-authored Soroban contract is included in the funded work.
For each additional vault, the final configuration records:
- DeFindex vault contract ID;
- strategy contract ID;
- supported Stellar asset and asset identifier;
- strategy and source of yield;
- roles, fees, and applicable configuration parameters;
- liquidity and withdrawal conditions;
- oracle or pricing dependencies where applicable;
- issuer, underlying-pool, backstop, and protocol dependencies; and
- principal risks in plain language.
Users can discover and open a detail view for every supported vault.
Users can complete an end-to-end deposit into each additional vault.
Users can complete an end-to-end withdrawal from each additional vault.
Deposits and withdrawals require explicit authorization through the user’s embedded Stellar wallet.
PigFi does not store, access, or control users’ private keys.
The transaction interface displays the selected vault, asset, amount, and relevant transaction context before authorization and displays pending, successful, rejected, and failed states.
Before a user’s first deposit into each additional vault, the application displays the applicable vault-specific risk disclosure and requires explicit acknowledgment.
The acknowledgment record is persisted per user and vault and includes the disclosure version and timestamp.
A first-deposit request for a newly integrated vault is not prepared or submitted through PigFi until the current disclosure version has been acknowledged.
Acknowledging one vault’s disclosure does not satisfy the acknowledgment requirement for another vault.
The acknowledgment does not automatically select or recommend a vault.
Vaults can be activated or deactivated and their application metadata and disclosure versions can be updated through backend configuration without requiring a new mobile release. These controls do not alter DeFindex contract code or strategy logic.
Automated tests cover:
- the common vault registry and DeFindex adapter;
- configuration mapping for both additional vaults;
- vault discovery, metadata, and dependency disclosures;
- transaction preparation and embedded-wallet authorization;
- deposits and withdrawals;
- transaction-state normalization and error handling;
- portfolio synchronization;
- persistence and versioning of risk acknowledgments;
- rejection of a first-deposit request when the applicable disclosure has not been acknowledged;
- successful continuation after the applicable disclosure is acknowledged;
- separation of acknowledgment records by user and vault; and
- runtime activation and deactivation controls.
Completion evidence includes:
- the corresponding PigFi source-code release or tagged commit;
- access to the review build;
- the two additional DeFindex vault contract IDs, strategy IDs, asset identifiers, and configuration records;
- identification of which activities were PigFi custom engineering and which were DeFindex configuration;
- successful deposit and withdrawal transaction hashes for each additional vault;
- automated test results;
- screenshots or records demonstrating the versioned risk-disclosure acknowledgment; and
- a recorded end-to-end demonstration showing vault discovery, risk disclosure, enforcement before acknowledgment, acknowledgment, user-directed vault selection, embedded-wallet authorization, deposit, portfolio display, and withdrawal.
Estimated completion
Approximately four to five weeks after project start.
Budget breakdown
[PigFi custom engineering] Backend vault registry, DeFindex adapter, and normalized metadata and transaction-state handling: US$ 4,500
[PigFi custom engineering] Mobile vault discovery, detail, deposit, withdrawal, and embedded-wallet authorization flows: US$ 4,000
[DeFindex configuration] Candidate validation; vault instantiation and parameter and role configuration using DeFindex-provided factory contracts, standard vault contracts, interfaces, and tooling; configuration and technical validation of strategy-allocation and rebalance instructions and workflows; and mapping of vault, strategy, and asset identifiers for at least two additional vaults: US$ 3,000
[PigFi custom engineering] Vault-specific risk and dependency disclosures, versioned acknowledgment persistence and enforcement, and runtime activation and deactivation controls: US$ 2,000
[PigFi custom engineering] Automated integration testing, technical documentation, review build, recorded demonstration, and completion evidence: US$ 2,212
The DeFindex configuration allocation covers configuration and integration labor only. It does not fund deposited principal, vault liquidity, minimum locked amounts, incentives, rewards, transaction value, or the creation or modification of DeFindex or other Soroban smart-contract code.
Total PigFi custom engineering: US$ 12,712
Total DeFindex configuration: US$ 3,000
Total Deliverable 1 scoped cost estimate: US$ 15,712
Brief description
Expand PigFi’s existing production BRL/Pix integration into a resilient, provider-neutral ramp orchestration layer supporting local fiat access to and from Stellar across Brazil, Argentina, Colombia, and Mexico.
PigFi currently operates its Brazilian BRL/Pix flows through BlindPay. ChatPay Go Labs has commercial coverage with BlindPay for all four countries. The funded work will enable the contracted local payment rails:
Brazil: Pix
Argentina: Transfers 3.0
Colombia: PSE and COP ACH
Mexico: SPEI
PigFi has also started an initial Etherfuse implementation in a separate development branch. This proof of concept is disclosed as pre-existing work and is not presented as grant-funded development.
SCF funding will cover the remaining:
production integration;
backend orchestration;
mobile experience;
testing;
reconciliation;
monitoring; and
deployment
required to make Etherfuse an additional provider for Mexico.
The backend will introduce a canonical ramp model and provider-adapter architecture covering:
provider capabilities;
countries;
currencies;
Stellar assets;
local payment rails;
KYC requirements;
quotes;
fees;
limits;
payment instructions;
transaction states;
webhooks;
settlement; and
reconciliation.
Provider and country capabilities will be controlled through backend configuration, without requiring a new mobile release.
The mobile applications will dynamically present the providers, rails, KYC journeys, quotes, instructions, and transaction states available for each country.
The deliverable also includes internationalization infrastructure and Spanish localization across the PigFi experience.
PigFi will produce a threat model and corresponding on-chain monitoring plan covering:
system assets;
data flows;
trust boundaries;
external dependencies;
principal threats;
mitigating controls;
monitored signals;
alert conditions;
operational responsibilities; and
recovery procedures.
Android and iOS release candidates, store-submission materials, and production configurations will be prepared early enough to support the production launch and final measurement window described in Deliverable 3.
PigFi’s existing BlindPay BRL/Pix production pay-in and pay-out flows remain operational in Brazil.
The following contracted BlindPay flows are implemented:
Argentina: pay-in and pay-out through Transfers 3.0;
Colombia: pay-in through PSE and pay-out through COP ACH; and
Mexico: pay-in and pay-out through SPEI.
The remaining Etherfuse integration for Mexico is completed as an adapter within the common orchestration architecture.
Mexico supports BlindPay and Etherfuse through the same provider-neutral architecture.
Grant-funded Etherfuse development is distinguishable from the pre-existing proof-of-concept branch through documented:
commits;
pull requests; or
releases.
A support matrix identifies, for every supported combination:
provider;
country;
currency;
payment rail;
transaction direction;
Stellar asset; and
validation environment.
The canonical backend interface normalizes:
provider and market capabilities;
customer and KYC states;
quotes, exchange rates, fees, and limits;
payment instructions;
order and settlement states;
provider webhooks; and
reconciliation outcomes.
Country, provider, rail, and transaction-direction combinations can be enabled, disabled, or restricted through backend configuration.
Provider-specific failures are translated into:
consistent internal states; and
user-readable recovery instructions.
Provider webhooks include:
authenticity verification where supported;
idempotent processing;
duplicate-event protection; and
replay protection where the provider protocol supplies the required information.
Duplicated, delayed, missing, or out-of-order events do not create duplicate:
credits;
debits;
orders; or
settlement records.
Incomplete or inconsistent transactions can be identified and reconciled:
automatically; or
through documented operational procedures.
The backend maintains an audit trail for:
provider state transitions;
webhook processing;
manual interventions; and
reconciliation actions.
Provider-neutral mobile interfaces cover:
country, currency, provider, and rail availability;
KYC initiation and status;
quotes, exchange rates, fees, and limits;
payment instructions;
transaction tracking; and
completion, failure, and recovery.
Where more than one provider is available, users can see the applicable:
provider;
rate;
fees;
limits;
KYC requirements; and
expected settlement conditions
before confirmation.
The application supports Portuguese and Spanish.
Spanish localization covers:
onboarding;
vault information;
risk disclosures;
KYC;
ramp instructions;
transaction states;
errors;
deposits;
withdrawals; and
portfolio screens.
Financial amounts, currencies, dates, and decimal separators are formatted according to the applicable locale.
Missing translations fall back safely without:
displaying internal keys; or
blocking transactions.
A documented threat model identifies:
protected assets and sensitive information;
data flows, trust boundaries, privileged components, and external dependencies;
principal threats involving wallet authorization, provider APIs and webhooks, Stellar transactions, configuration, reconciliation, and operational access; and
the mitigating controls for each principal threat.
A corresponding on-chain monitoring plan identifies:
the Stellar accounts, sponsored accounts, assets, transaction sources, and DeFindex contracts to be monitored;
relevant on-chain and off-chain signals;
failed, delayed, duplicated, inconsistent, or anomalous transaction conditions;
alert and escalation conditions;
operational ownership; and
investigation and recovery procedures.
Automated tests cover:
provider adapters;
market routing;
quote normalization;
state transitions;
webhook security and idempotency;
duplicate and out-of-order events;
reconciliation;
provider failures;
feature flags; and
localization.
Technical and operational documentation covers:
provider configuration;
supported markets;
webhooks;
reconciliation;
outages;
monitoring;
feature disablement; and
recovery procedures.
Android and iOS release candidates, store-submission materials, and production configurations are prepared before the final production stage.
Completion evidence includes:
the corresponding source-code release or tagged commit;
access to the review build;
the provider and market support matrix;
the threat model and corresponding on-chain monitoring plan;
automated test results;
recorded demonstrations of each country and provider flow;
redacted provider logs, certification, or equivalent validation evidence;
applicable Stellar transaction hashes;
reconciliation and monitoring evidence; and
evidence of Android and iOS production-release preparation.
Production activation in each country depends on the applicable provider’s final operational, compliance, and regulatory approval.
If a provider has not authorized production transactions in a country by the tranche review date, that flow may be considered complete only if:
PigFi’s implementation is production-ready and deployed behind a disabled feature flag;
the flow is validated end to end in the highest environment authorized by the provider;
provider certification, written confirmation, or equivalent technical-acceptance evidence is supplied;
transaction states, webhook handling, failure recovery, and reconciliation are demonstrated; and
the unsupported flow is not exposed to production users.
A mock-only demonstration will not be sufficient.
Approximately two months following Deliverable 1.
Canonical ramp model, orchestration layer, and provider-adapter architecture: US$ 6,500
BlindPay expansion for Argentina, Colombia, and Mexico: US$ 7,500
Completion and integration of the Etherfuse Mexico adapter: US$ 4,500
Provider-neutral mobile experience, internationalization infrastructure, Spanish localization, and production-release preparation: US$ 5,000
Webhook reliability, audit trail, reconciliation, operational monitoring, threat model, and on-chain monitoring plan: US$ 4,000
Automated tests, technical and operational documentation, and completion evidence: US$ 2,818
Brief description
Launch the complete SCF-funded scope as a production PigFi release for Android and iOS, connected to Stellar mainnet.
PigFi is already live on Stellar mainnet and currently has approximately US$ 13,000 deposited in its existing DeFindex vault. This milestone will release the newly funded capabilities: at least two additional DeFindex vaults, provider-neutral ramp orchestration across Brazil, Argentina, Colombia, and Mexico, and a complete Spanish-language experience.
1. Production Release
The funded backend and mobile capabilities will be hardened, deployed, and released through PigFi’s production Android and iOS applications. Both applications will connect to PigFi’s production backend and Stellar mainnet.
Production-release preparation will begin during Deliverable 2. Android and iOS release candidates, store-submission materials, and production configurations will be prepared early enough for the funded applications to become publicly available at the beginning of the final project stage and provide a continuous 30-day production measurement window before final review.
2. End-to-End Savings Lifecycle
The production release will connect the complete user journey:
Local currency → KYC and ramp eligibility → quote and local payment → Stellar asset settlement → user-directed DeFindex vault selection → portfolio reconciliation → vault withdrawal → local-currency off-ramp
The provider-neutral ramp layer will support PigFi’s existing BlindPay BRL/Pix production flow in Brazil and the funded integrations for Argentina, Colombia, and Mexico. Mexico will support both BlindPay and Etherfuse through the common provider architecture.
3. User-Directed Vault Access
Users will independently select the vault into which they want to deposit. PigFi will not automatically select a vault, allocate a user’s funds, provide a personalized recommendation, or make a suitability determination.
Before a user’s first deposit into each additional vault, PigFi will display the current version of that vault’s risk disclosure and require explicit acknowledgment. The disclosure will describe the applicable asset, liquidity, withdrawal, variable-yield, smart-contract, oracle or pricing, issuer, underlying-pool, backstop, and protocol-dependency risks in plain language.
The acknowledgment is a product risk control. It does not recommend a vault, determine suitability, or waive user rights. The acknowledgment record will be persisted per user and vault with the disclosure version and timestamp. A first-deposit request will not be prepared or submitted through PigFi until the applicable disclosure has been acknowledged.
Deposits and withdrawals will require explicit authorization through the user’s embedded Stellar wallet. PigFi will not store, access, or control users’ private keys or seed phrases.
4. Production Reliability and Measurement
The production system will include monitoring, reconciliation, and recovery across ramp providers, Stellar transactions, and DeFindex vault interactions. PigFi will implement an attributable on-chain measurement layer for the Integration Track’s final-tranche metric.
How completion will be measured
The complete funded scope is publicly released in PigFi’s production Android application.
The complete funded scope is publicly released in PigFi’s production iOS application.
Both applications connect to PigFi’s production backend and Stellar mainnet.
At least two additional DeFindex vaults are available beyond PigFi’s pre-award vault.
Each additional vault displays its underlying asset, strategy, source of yield, liquidity and withdrawal conditions, fees where applicable, oracle or pricing dependencies, issuer and protocol dependencies, and principal risks in plain language.
Users independently select the vault into which they want to deposit.
Before a user’s first deposit into each additional vault, the application displays the current vault-specific risk disclosure and requires explicit acknowledgment.
The acknowledgment is persisted per user and vault with its disclosure version and timestamp.
A first-deposit request is not prepared or submitted through PigFi until the current disclosure version for that vault has been acknowledged.
Acknowledging one vault’s disclosure does not satisfy the acknowledgment requirement for another vault and does not automatically select or recommend a vault.
Users explicitly authorize deposits and withdrawals through their embedded Stellar wallet.
PigFi does not store, access, or control users’ private keys or seed phrases.
The provider-neutral ramp orchestration layer is deployed in production.
PigFi’s existing BlindPay BRL/Pix pay-in and pay-out flows remain operational in Brazil.
The funded BlindPay flows for Argentina, Colombia, and Mexico are integrated through the common orchestration architecture.
The funded Etherfuse integration for Mexico is available through the same common provider architecture.
Mexico supports the funded BlindPay and Etherfuse integrations without separate hard-coded mobile journeys.
Country, provider, rail, and transaction-direction combinations that have received production approval can be enabled or disabled through backend configuration without requiring a new mobile release.
Portuguese and Spanish production experiences are available on Android and iOS, including vault discovery and information, risk disclosures, KYC, ramp instructions, transaction states, deposits, withdrawals, and portfolio screens.
Users receive the appropriate country, currency, provider, payment rail, and language configuration.
Transactions interrupted by provider delays, application closure, or temporary network failures can be resumed, safely retried, or reconciled without creating duplicate orders, credits, debits, or on-chain transactions.
Production monitoring covers:
- ramp orders and provider availability;
- provider webhooks and webhook-processing failures;
- Stellar transaction submission and confirmation;
- DeFindex deposits and withdrawals;
- incomplete, delayed, duplicated, inconsistent, or anomalous transaction states;
- underlying vault, pool, oracle, asset-issuer, or protocol incidents;
- runtime vault or provider deactivation; and
- reconciliation failures and backlogs.
Automated unit, integration, regression, and end-to-end tests cover the critical funded flows.
Automated tests verify risk-disclosure display, acknowledgment persistence and versioning, rejection of a first-deposit request before acknowledgment, successful continuation after acknowledgment, and separation of acknowledgment records by user and vault.
Structured user testing is completed on representative Android and iOS devices.
Critical usability findings that block or materially impair a funded flow are resolved before final review.
Completion evidence includes:
- Android and iOS production release links;
- application and backend release identifiers;
- the two additional DeFindex vault contract IDs, strategy IDs, and asset identifiers;
- applicable Stellar mainnet transaction hashes;
- automated test results;
- user-testing results;
- versioned risk-disclosure and acknowledgment evidence;
- production monitoring and reconciliation evidence;
- a recorded end-to-end demonstration for each funded vault and market flow; and
- public technical and operational documentation.
The recorded vault demonstration will show vault discovery, the applicable risk disclosure, enforcement before acknowledgment, acknowledgment, user-directed vault selection, embedded-wallet authorization, deposit confirmation, portfolio display, and withdrawal.
Provider-dependency condition
Production activation in each country depends on the applicable provider’s final operational, compliance, and regulatory approval.
If a funded provider or country combination has not received production approval by final review, that combination will be considered complete only if:
- PigFi’s implementation is production-ready and deployed behind a disabled feature flag;
- the flow has passed end-to-end validation in the highest environment authorized by the provider;
- provider certification, written confirmation, or equivalent technical-acceptance evidence is supplied;
- webhook handling, transaction states, failure recovery, and reconciliation are demonstrated; and
- the unavailable flow is not exposed to production users.
A mock-only demonstration will not be sufficient.
This dependency condition does not modify the final on-chain metric, which must be achieved through eligible production activity on Stellar mainnet.
Final outcome
At completion, PigFi will operate as a bilingual, multi-country Stellar savings application for Android and iOS, combining embedded non-custodial wallets, local payment rails, USDC, and multiple DeFindex vaults.
Users will be able to move from familiar local currency into user-selected on-chain savings and back without needing to understand wallets, trustlines, XDRs, or smart-contract infrastructure.
Estimated completion
Production-release preparation will begin during Deliverable 2. The funded Android and iOS releases will be made publicly available at the beginning of the final project stage, followed by a continuous 30-day production measurement window and preparation of the final completion evidence.
Budget breakdown
Production hardening and Stellar mainnet activation: US$ 9,000
Android and iOS release engineering and rollout controls: US$ 5,500
Production monitoring, reconciliation, alerting, and recovery: US$ 7,000
Automated unit, integration, regression, and end-to-end testing: US$ 4,500
Structured Android and iOS user testing and usability remediation: US$ 3,500
On-chain attribution, measurement, and final reporting: US$ 5,000
Documentation, operational runbooks, and completion evidence: US$ 5,924
Total Deliverable 2 scoped cost estimate: US$ 40,424
PigFi’s sole binding final-tranche on-chain metric is at least US$ 5,000 in cumulative user-originated deposits into the additional DeFindex vaults delivered through this SCF award during a continuous 30-day production measurement window.
Metric type and threshold
The metric is the cumulative USD value of successfully confirmed Stellar mainnet deposits into the registered contract IDs of the funded vaults. Withdrawals will not reduce cumulative eligible deposit volume.
Baseline
PigFi’s pre-award DeFindex vault currently holds approximately US$ 13,000. Before the measurement window begins, PigFi will record its contract ID, snapshot date, on-chain value, and valuation methodology. The existing balance and all deposits into that pre-award vault are excluded from the metric.
Measurement window
The continuous 30-day window will begin after:
- the funded Android and iOS releases are publicly available;
- both additional DeFindex vaults are available to eligible production users; and
- the funded vault contract IDs and PigFi-attributable on-chain footprint have been registered with the SCF panel.
The window will end before final-tranche review.
Attribution and valuation
Eligible activity must originate through an attributable PigFi user journey. The registered footprint may include the funded vault contract IDs, PigFi-linked embedded Stellar wallets, attributable transaction-source or fee-sponsorship accounts, sponsored accounts, relevant asset identifiers, and transaction-operation patterns agreed with the SCF panel.
Each confirmed deposit will be valued in USD at the time of confirmation using the valuation methodology agreed with the panel.
Exclusions
The following will not count:
- the existing balance or any new deposits in the pre-award vault;
- transactions outside the measurement window;
- failed or unconfirmed transactions;
- internal testing activity;
- transactions funded by PigFi, ChatPay Go Labs, team members, or contractors;
- duplicated, circular, wash, sybil, artificially generated, or self-canceling activity; and
- transactions that cannot be attributed to an eligible PigFi user journey.
Binding and non-binding measures
The US$ 5,000 cumulative deposit threshold is the sole binding adoption metric. PigFi will also report the number of unique eligible PigFi-linked Stellar wallets as a non-binding adoption indicator; no minimum wallet count is required for tranche completion.
Reporting
The final report will provide the eligible cumulative deposit volume, transaction hashes, funded vault contract IDs, measurement timestamps, valuation methodology, registered-footprint description, non-binding unique-wallet count, and excluded-activity summary.
ChatPay Go Labs is a long-standing team united by a clear purpose: bringing the power of blockchain to everyday people. We have worked together for more than a year and are deeply committed to building on Stellar. Vanessa Barros, our CEO, is a biologist and a specialist in human behavior and relationships; she and Maycon have been Stellar Ambassadors for over two years. Ana Carolina Tavares, our CPO, brings 20+ years in the oil industry leading innovation and portfolio initiatives, plus experience as a serial entrepreneur. Maycon Rodrigues, our CTO, has 18+ years as a full-stack developer with experience in payments and blockchain. Matheus Aguiar, our software engineer, specializes in UX and AI. Carol and Matheus are currently enrolled in the Stellar/NearX postgraduate program, while Vanessa has already graduated. We attended the latest Meridian as a team and now operate as ChatPay Go Labs, with PigFi and other Stellar-based products in our pipeline. We are not building on Stellar opportunistically: it is the ecosystem we have chosen for our long-term mission. https://www.linkedin.com/in/caroltavaresblockchainproductmanager/ https://www.linkedin.com/in/maycon-rodrigues/ https://www.linkedin.com/in/matheusbrasilaguiar/ https://www.linkedin.com/in/vanessabarros-tech/ https://github.com/orgs/ChatPay-Go-Labs-Oficial/repositories https://github.com/Maycon-Rodrigues https://github.com/matheusbrasilaguiar https://github.com/CarolTea https://chatpaygolabs.com
Matheus Brasil
Ana Carolina Gonçalves Tavares
Vanessa Barros
Maycon
No other submissions.