Using Remittances to Bootstrap Adoption

TLDR

A P2P remittance system where merchants cash out recipients in exchange for BCH—effectively buying BCH with built-in customer acquisition. Payment-first covenants protect recipients from volatility. Passive sellers automate liquidity via phone notification parsing. Merchants mint stability tokens to hold value without risk.


The Mechanism (How It Actually Works)

Here’s a concrete example: María in Madrid wants to send €100 to Elena in Venezuela.

María opens the app, selects “Send money,” enters €100. The app queries the bulletin board—an on-chain list of BCH sellers who can automatically fund covenants using payment notifications from their banking apps.

María sees Isabel listed: “Accepts Bizum (Spanish mobile payment), 0.5% fee, active now.” María selects Isabel and creates a covenant with a 7% volatility buffer and 8-hour claim window. She gets payment instructions via Nostr: “Send €100.50 via Bizum to Isabel, reference: ELENA#142.”

María sends the Bizum payment. Isabel’s phone is monitoring bank notifications 24/7. The notification arrives: “Received €100.50 from María.” Isabel’s bot parses the notification, extracts the amount, sender, and reference, then auto-funds the covenant with €107 worth of BCH to cover the buffer.

Elena gets a Nostr notification: “You have €100 worth of BCH from María. Claim within 8 hours.”

Elena opens the app, sees two options: claim BCH directly to her wallet (free), or cash out at a local merchant (0.5% fee). She taps “Find merchant.” The app shows Carlos’s grocery store nearby. Elena walks to the store, tells Carlos: “I want to cash out a remittance.” Carlos opens his app, types “Elena#142” (her Cash Account), sees the pending covenant, hands Elena cash. Both tap “Confirm” to co-sign the covenant. BCH moves directly from the covenant to Carlos.

Carlos now holds €100 worth of BCH. He doesn’t want volatility risk, so he mints H€ tokens (Euro-pegged) using an AnyHedge-inspired contract. A bull pool provides the long position, Carlos takes the short side, locking in stable value. He holds the H€ tokens, cashes out when he needs VES for restocking.

The key insight: Carlos isn’t just accepting BCH—he’s buying it from remittance recipients with built-in customer acquisition. Elena came to cash out and stayed to buy groceries.


Why This Works for Merchant Adoption

The merchant capable of cashing out a remittance is a business anyone can pay with BCH. Why would they do it? Three reasons.

Reason one: Fee revenue. They earn 0.5% on every cash-out. €100 remittance = €0.50 fee. If they cash out ten remittances per week, that’s €5 in extra revenue. Small amount, but it compounds.

Reason two: Customer acquisition. Elena came to cash out and bought groceries. That’s the key—recipients don’t just cash out, they become customers. The right business sells products and services alongside the cash-out service.

Reason three: Stable holding. Merchants don’t want volatile BCH, they want stable value. H€ and HAu tokens solve this—Euro-pegged or gold-pegged value using AnyHedge-inspired contracts. In hyperinflation markets, every remittance they cash out is an opportunity to dump rapidly depreciating fiat for stable crypto.

Compare this to Western Union: 5-10% fees, no merchant involvement, bank-dependent, recipient waits days for pickup. Asgaya: 1% total fees (0.5% seller + 0.5% merchant), P2P, no KYC, settlement in 30 minutes, (and most of that time is Elena walking to Calos’s) merchant keeps value stable.

The adoption flywheel: Remittances create merchant demand. Recipients become customers. Merchants accumulate stable value. Sellers automate passive income via notification bots. Everyone saves 90% on fees. Self-funding, no intermediaries.


What We’ve Built So Far

Five months ago I posted about how close we were to having a remittance app. The feedback made me realize we weren’t that close—I’ve been building since then.

Completed:

  • Full conceptual framework at docs.asgaya.org
  • The Mechanism — covenant architecture, payment-first model, stability layer
  • Notification bot research (RS072) — 48-hour validation test complete
  • Production-ready: boot receiver, battery exemption, foreground service
  • My phone monitors Bizum notifications 24/7 from five Spanish banks, parsing amount/sender/reference automatically

Current status: Phase -1 (documentation complete, notification bot validated, almost ready for Phase 0 trials with real money)


I haven’t shared this project publicly until now because the idea was immature. It’s mostly still research, but I’m getting close to testing with real money and potential users.

I’m especially interested in feedback on:

  • The Mechanism
  • Unknowns — 14 investigation briefs with hypotheses that need real-world testing
  • Edge cases I haven’t considered
  • Phase 0 trial candidates

The examples use EUR and Venezuelan bolívares (VES), but there’s no reason this shouldn’t work in any high-remittance, high-inflation corridor.

Any insight is welcome.

2 Likes

Why not using stable coins for simplicity?

2 Likes

We thought a lot about it and took a serious look at BCH-native options (MUSD not available until they sort the vulnerability, ParyonUSD is too young) and non-BCH stablecoins (permissioned - non-starter).

But even decentralized USD-pegged tokens are “the same dog with a different collar” - still fiat-based. We can’t legally create our own stablecoin, so we’re using AnyHedge-inspired utility tokens as a volatility hedge instead. That said, the bulletin board is permissionless—if users want to trade USDT instead, I can’t stop them. I can only offer a better alternative.

Why the harder path? If we stabilize BCH by growing real economy usage (vs speculation), we don’t need stablecoins at all. BCH becomes a genuine fiat alternative - which is my real goal. A stable BCH can be a global reserve currency.

2 Likes

Interesting,hope to see it.

1 Like

flow_fps10_480

Loads of progress since July. The gif is a proof of concept for cash in person as a payment method (this is the TXID if anyone is curious)

This is still research code and the UI design is all over the place, but it does what it says in the tin. Multiple devices can coordinate to send guarantied value money transfers in a reasonable window of time. This is the main goal so we can leverage the remittances to incentive merchants to accept BCH.

In the gif there is a side by side of two devices. One acting as the sender and the other as the merchant funding the covenant. The sender selects the recipient and the amount, looks up a list of BCH sellers with cash in person as payment method, sends a DM to request payment instructions, and when it’s ready to pay, creates the covenant. Meanwhile on the other device nothing happens until the sender is at the counter. The merchant goes to the trade tab, finds the covenant funding request, the cash changes hands, funds the covenant, and now the recipient has an 8 hour window to claim the value in fiat that the sender selected. The “owner” of the covenant is the sender and that’s why it’s able to refund the transaction anytime; when that happens, the BCH lands in his wallet (the amount depends on the fiat value selected initially)

So the backbone of the app is ready. Now I’ll keep working on the UI and hardening the cash in person flow (it’s the universal default payment method after all) and the custom oracle before I start testing with real money again parsing the bank app notifications to automate the covenant funding process.

1 Like

Hmmm.
ParyonUSD is too young (much older now in Oct than back in July), but your new option wouldn’t be?
Legally, Paryon is NOT a Stablecoin. In the US “Stablecoins” must be backed by US treasuries. But, it does a great job of approximating USD value, and it’s TVL has doubled quickly.
In my opinion, you efforts would benefit the community far better by helping to ensure Paryon has no exploits. It is a successful project, and by introducing unneeded competition, BCH joins the convoluted stablecoin world of Ethereum.
Your imagination is great, but I would need to study your project quite a bit before I could explain it to someone else. Reading it reminded me of some of the BTC projects (Lightning, Cashu, Liquid, etc) that present many hoops to jump through when more efficient options already exist.
Think about the processes needed to educate users, vendors. Cryptocurrency in general still struggles with this after 17 years. Sadly, it’s greatest success is BTC Lightning via centralized Square, and the adoption is still very, very, very low. So, if the world’s most well known cryptocurrency, sponsored by an extremely popular payments service still struggles with adoption, what reception will your hard work attract?

2 Likes

:joy: This is funny because when I started to put everything together I said something similar, “we’re making a new Lightning network”. The thing is the more efficient option, I’d argue, is Bitcoin Cash. The hoops aren’t inefficiency. They’re the price of having no custodian and no intermediary. Remove them and you need to be an expert to tell it apart from the system I’m trying to replace.

If this ever reaches a beta I don’t see why the users wouldn’t list PUSD for sale in the bulletin board. We don’t pick assets, it’s neutral and permissionless by design, so it’s up to users what they list. That neutrality is the point (and the legal posture): no intermediary, nothing for us to control.

One clarification: the hedge-tokens are nothing more than a simplified version of AnyHedge, the same tech behind BCH Bull, consolidated and proven for years. Nothing unproven is being introduced. But we agree on this. It’s not realistic to explain to all merchants that they can go to bchbull.com and stabilize their BCH there. That complexity needs to be in the background and make it just a tap or something preselected so they don’t even have to think about it. The UI needs to solve that issue so the UX is better than TradFi.

Totally agree. 17 years in, street adoption is still a rounding error not because crypto doesn’t work, but because nobody ever gave the merchant a reason. The first sticker wave was pure FOMO, and it died the day fees ate the margin. That’s the gap we’re trying to fill. The question I want to answer is: what does it take for merchants to accept BCH?

My hypothesis: they need, at minimum, customers who already hold bitcoin. Where does that come from? Remittances, a niche that’s expensive and underserved, especially in countries with weak currencies and unstable economies.

To get there peer to peer, permissionless, and legal in most jurisdictions, the protocol has to solve a lot of problems. Each hurdle is trivial on its own; together, the result is very counterintuitive. I guess it’s the price we have to pay for missing the opportunity of putting bitcoin in the pockets of customers.

1 Like