INVISIBLE[01]
No shared view of performance.
Delivery speed varies by provider and corridor. Today, it’s hard to compare like for like.
FIG. 01 — A PAYMENT, WITH AN ACCOUNTABLE PATH
PAYMENT
PROMISES,
MADE
ENFORCEABLE.
Reliable payments should be more than a promise. Vaeltrix makes delivery commitments public, measurable, and backed by a provider’s own stake.
FOLLOW THE PAYMENTPUBLIC PROMISES / SIGNED EVIDENCE / LOCKED COLLATERAL / CLEAR OUTCOMES / PUBLIC PROMISES / SIGNED EVIDENCE / LOCKED COLLATERAL / CLEAR OUTCOMES / PUBLIC PROMISES / SIGNED EVIDENCE / LOCKED COLLATERAL / CLEAR OUTCOMES /
VAELTRIX / PAYMENT RELIABILITY
FROM A PROMISE TO A PUBLIC RECORD.
FROM A PROMISE TO A PUBLIC RECORD.
EVERY PAYMENT.
A TRACEABLE
PROMISE.
A TRACEABLE
PROMISE.
01 / DEFINE THE COMMITMENT
02 / LOCK THE PERFORMANCE BOND
03 / OBSERVE THE PAYMENT
04 / VERIFY THE EVIDENCE
05 / RECORD THE OUTCOME
02 / LOCK THE PERFORMANCE BOND
03 / OBSERVE THE PAYMENT
04 / VERIFY THE EVIDENCE
05 / RECORD THE OUTCOME
THE PERFORMANCE BONDCollateral that
RESERVED FOR VERIFIED CLAIMS.
Collateral that
stays committed.
STAKE ASSETTestnet USDC
COVERAGEOne commitment
CAPITAL POLICYNever lent or invested
FAST RAILS.
SLOW PAYOUTS.
LET’S CLOSE
THE GAP.
Stellar can settle in seconds. The bank or mobile-money payout can still take hours. Vaeltrix holds that last mile to a promise everyone can see.
EXPLORE THE PROTOCOLBUILT AROUND EXISTING STELLAR FLOWS
STELLARSOROBANSEP-31USDC
OPEN PROTOCOL DESIGN · NO NEW PAYMENT RAIL REQUIRED
THE RELIABILITY GAPTHE MONEY MOVES.
THE MONEY MOVES.
THE CERTAINTY
DOESN’T.
Between settlement and delivery, accountability gets lost. Private agreements and support tickets can’t give a wallet a clear picture of its next payment.
UNBACKED[02]
Promises without a deposit.
Service terms often live in private agreements, without funds already set aside for a breach.
MANUAL[03]
A delay becomes a support ticket.
Chasing a partner is slow. Enforcing a small payment claim can cost more than the claim itself.
ANECDOTAL[04]
Reputation isn’t a routing signal.
Wallets need an observable delivery record, not a recommendation buried in a chat thread.
ONE PAYMENT. A COMPLETE ACCOUNT.60 MIN TARGET
[ 01 / 03 ]
A promise with something behind it.
PROVIDER → COMMITMENT
A payment provider chooses a standard delivery promise and locks USDC as a performance bond. The rules are public. The deposit stays put.
SCROLL TO FOLLOW THE PAYMENT ↓
SMALL ON-CHAIN FOOTPRINTTHREE CONTRACTS.
THREE CONTRACTS.
ONE CLEAR
ACCOUNTABILITY LOOP.
Keep the funds, the rules, and the record in separate places. Each layer does one job. The evidence connects them.
The identity & the promise.
Providers, signing keys, and standard SLA templates.
The stake & the settlement.
Locked collateral, claims, challenges, and penalty payouts.
The public track record.
Payment statistics and claim outcomes, ready to query.
SENDERRECEIVER
1,000USDC
DELIVERY TARGET60 min + 2 min graceCOMPLETION75 minutes
SLA BREACH5 USDC proposed penaltySUBJECT TO CLAIM RESOLUTION
[01] / PAYMENT COVERAGETHE PROMISE
THE PROMISE
TRAVELS WITH
THE PAYMENT.
A tagged payment points to a specific commitment. That means a known deadline, a known penalty, and a known source of funds.
Example uses the proposed fast bank payout template. A penalty goes to the sending client by default.
INSPECT THE TERMSEvery outcome
leaves a record.
leaves a record.
01 / DELIVERYOn-time rate & payout latency
02 / EXCEPTIONSDeclared holds, by reason
03 / COVERAGEStake backing the commitment
04 / CLAIMSUpheld, rejected, paid, expired
METRIC STRUCTURE — LIVE PROVIDER DATA COMES WITH THE PILOT
[02] / PUBLIC SCOREBOARDRELIABILITY
RELIABILITY
YOU CAN
ACTUALLY READ.
Compare providers by corridor and asset. See delivery speed, exceptions, stake, and claim history in one public record.
A track record that wallets can use to make better routing decisions.
READ ABOUT THE SCOREBOARDSTANDARD TERMS. COMPARABLE PROVIDERS.A PROMISE
A PROMISE
WITH THE DETAILS
FILLED IN.
Same rules, same measurements. Three proposed launch templates turn service quality into something providers and clients can agree on.
PROPOSED TESTNET TEMPLATESEP-31 / USDC
60MINUTES
TO COMPLETE
TO COMPLETE
PENALTY0.5%
PENALTY CAP50 USDC
GRACE2 minutes
CLAIM WINDOW7 days
PAYMENT SIZE10–10,000 USDC
PAYOUT RAILBANK
DRAFT PARAMETERS. TO BE TUNED WITH PILOT PROVIDERS.
DESIGNED TO BE FAIRACCOUNTABILITY
ACCOUNTABILITY
GOES BOTH WAYS.
01 / OBSERVE
Measure what can be proven.
Ledger timestamps and signed events make the payment’s timeline attributable.
02 / PROTECT
Keep the collateral in place.
A performance bond is locked against its commitment. It is never lent or invested.
03 / CHALLENGE
Give evidence room to answer.
Providers can contest a claim. Declared, auditable exceptions protect legitimate delays.
04 / PUBLISH
Make every outcome visible.
Breach counts, carve-outs, and resolved claims all contribute to the public record.
FOR THE PEOPLE MOVING MONEYA SHARED STANDARD.
A SHARED STANDARD.
A BETTER PAYMENT
FOR EVERY SIDE.
Compare delivery performance before choosing a provider. Route using verifiable reliability, with clear coverage for each tagged payment.
Know what your receiving partner has promised. Signed evidence and a defined claim process replace a chain of support tickets.
Build on open templates, published evidence, contract events, and a planned TypeScript SDK. Help make payment reliability observable.
Evaluate counterparties using delivery records, locked stake, and claim history rather than a promise in a sales deck.
MAKE THE NEXT
PAYMENT A PROMISE
YOU CAN VERIFY.
The first milestone: commit stake, track a payment,
prove a breach, resolve a claim. All on testnet.