Working iPhone and Mac wallet

Fund six months of Opal Wallet production readiness.

58 Opals has already built a working iPhone and Mac Bitcoin Cash wallet. This 350 BCH campaign funds six months of production-readiness work: core wallet reliability, App Intents-ready wallet actions, public demos, validation reports, GitHub milestones, and monthly Blog updates.

Target
350 BCH
Planning value
About $68,250
Baseline
$195/BCH
Fund on FundMe.cash

Why this matters

Bitcoin Cash needs wallet actions that can live beyond one app screen.

Bitcoin Cash already has practical payment strengths: low fees, fast settlement, and a culture focused on peer-to-peer electronic cash. Apple is moving toward a system where app capabilities can be understood by Shortcuts, Siri, Spotlight, and Apple Intelligence through App Intents.

Most wallets are still designed as isolated app screens. Opal Wallet is being built differently: current BCH wallet actions are being prepared as structured Apple-platform capabilities, backed by an open Swift stack that future builders can inspect and reuse.

This campaign is about making Bitcoin Cash easier to request, prepare, find, automate, and confirm through native Apple workflows while payment movement stays inside Opal Wallet's review path.

Apple system layer

What App Intents means.

App Intents is Apple’s framework for turning app features into structured actions the system can understand. Those actions can appear in places like Shortcuts, Siri, Spotlight, widgets, controls, and Apple Intelligence.

For Opal Wallet, this means wallet capabilities should not exist only as buttons inside one app. Receiving BCH, preparing a payment, finding activity, opening a wallet view, or starting a user-confirmed action can be designed as clear wallet actions that Apple’s system can route into everyday workflows.

Why it matters for BCH

System action A wallet task becomes understandable outside the app screen.
User workflow Shortcuts and Siri can help users start or combine supported actions.
Wallet consent Payment actions still return to Opal Wallet for review and confirmation.

Learn more from Apple: App Intents documentation, Design App Intents for system experiences, and Bring your app to Siri.

Wallet actions

What App Intents makes possible for Opal Wallet.

Funders are not just helping another wallet screen get polished. They are funding the work to make safe BCH wallet actions available as structured Apple-platform capabilities that can be started, combined, found, and reviewed through native workflows.

Shortcuts examples

Wallet actions users can combine.

Open Receive Open the receive flow for a selected wallet.
Create BCH request Prepare a request amount and show it in Opal Wallet.
Find recent activity Open filtered wallet activity for review.
Show latest incoming BCH Open the newest incoming payment details.
Prepare payment for review Stage payment details without sending BCH.
Open payment review in Opal Wallet Return to Opal Wallet for user confirmation.

Siri examples

Natural language can start a safe review path.

“Show my latest incoming BCH in Opal Wallet.” Opal Wallet opens recent incoming activity.
“Start a BCH request for 0.02 BCH.” Opal Wallet prepares a receive request for review.
“Prepare this BCH payment for review.” Opal Wallet stages payment details without broadcasting.
“Find the payment I received this morning.” Opal Wallet opens matching wallet activity.

Safety matrix

Receive and request System actions can open receive flows or prepare BCH requests; sharing or sending request details still stays user-controlled.
Activity lookup System actions can open recent, incoming, or filtered activity so users can inspect wallet history inside Opal Wallet.
Payment preparation System actions can stage payment details for review, but they do not send BCH.
Signing and broadcast Direct automation cannot sign or broadcast transactions; Opal Wallet review and local device authentication are required before money moves.

Readiness bar

A working app is the starting point, not the finish line.

Production readiness means the core wallet paths behave predictably under real use, failures are handled clearly, wallet actions are prepared for safe App Intents surfaces, and you can follow the validation work through public reports and open source activity.

Six-month deliverables

Core iPhone and Mac wallet reliability Send, receive, sync, transaction history, wallet management, and confirmation-state handling move through deeper validation.
App Intents-ready wallet actions Receive, request, activity lookup, and payment-review flows are prepared as structured Apple-platform actions.
Recovery and safety validation BIP-39 restore checks, manual backup guidance, transaction testing, and wallet-consent boundaries are documented.
Public Swift stack work Opal Base, SwiftFulcrum, Opal Crypto, Opal Fusion, and Opal Hedge receive visible documentation, milestones, or implementation links tied to wallet behavior.
Monthly Blog reports Each month reports completed work, validation notes, GitHub milestones or public-stack links, screenshots or demos, open items, next focus, and material budget impact.
Secondary BCH workstreams macOS CashFusion stays visible as secondary production-readiness context, and AnyHedge stays visible as Opal Hedge roadmap context behind the core wallet ask.

What this phase strengthens

Core payments Send and receive BCH remain stable while transaction construction, signing, broadcast, balance sync, and confirmation-state handling get deeper validation.
Intent-ready actions Current wallet actions are mapped toward App Intents surfaces for requesting BCH, opening receive flows, finding wallet activity, preparing payments for review, and confirming user-controlled actions inside Opal Wallet.
Live detection Address monitoring, incoming transaction detection, pending/confirmed transitions, and Fulcrum-backed network behavior are tested and reported.
History and addresses Cleaner transaction history, transaction detail states, address handling, and QR code scanning become part of the production-readiness checklist.
Recovery and safety Wallet creation, BIP-39 restore, manual backup guidance, recovery checks, failure cases, and known limitations are documented alongside validation status.
Readiness decisions Monthly reports make open items, demos, validation notes, budget-impact notes, and production-readiness decisions visible before any broader distribution claim.

Current app

The current app and open stack are inspectable before the budget.

The capability map summarizes the wallet surfaces already in the iPhone and Mac app. The walkthrough then shows those surfaces before the funding plan explains what has to become more reliable, verifiable, and ready for production-readiness decisions.

Current capability map

Core wallet works today

  • Wallet creation Working
    In the current app.
  • Restore Working
    In the current app.
  • Receive address generation Working
    In the current app.
  • Balance sync Working
    Fulcrum-backed app state.
  • Send, sign, and broadcast Working
    Mainnet transaction path.
  • Transaction history and detail states Working
    Pending and confirmed transaction states.
  • Wallet management Working
    Visible iPhone and Mac app surfaces.

Advanced BCH scope

  • macOS CashFusion Secondary
    Secondary macOS context behind core wallet readiness.
  • AnyHedge Roadmap scope
    Opal Hedge public-stack work.

App walkthrough

iPhone and Mac app flows

The sections below show the product surfaces you can inspect now: wallets, send, receive, activity, management, and advanced BCH scope.

01

Wallets and accounts

Opal Wallet starts with the basic surface every wallet has to get right: accounts, balances, and visible wallet structure.

Opal Wallet wallet list on iPhone Opal Wallet account swipe send action on iPhone Opal Wallet account swipe receive action on iPhone

WalletA clear account list gives the wallet a familiar starting point.

SendThe same account surface keeps sending close to the wallet.

ReceiveAccount actions expose receiving without leaving the wallet context.

Opal Wallet add wallet screen on Mac
Opal Wallet wallet view on Mac

AddThe Mac app includes a wallet setup surface.

WalletThe desktop wallet view mirrors the same account-first model.

02

Send

The send flow shows review, preparation, progress, and confirmation surfaces as current app work, not planned mockups.

Opal Wallet send screen on iPhone Opal Wallet send review with Face ID symbol on iPhone Opal Wallet send progress screen on iPhone Opal Wallet send confirmation on iPhone

SendThe send flow starts with a focused payment entry screen.

ReviewThe review step gives the user one more clear confirmation point.

ProgressThe app shows movement through the send process.

DoneThe confirmation screen closes the loop after sending.

Opal Wallet send review on Mac
Opal Wallet send preparing state on Mac
Opal Wallet send confirmation step on Mac

ReviewThe Mac send flow starts with a full review surface.

PrepareThe preparing state shows the transaction moving forward.

ConfirmThe confirmation step gives the final send checkpoint.

03

Receive

Receiving stays close to the wallet, with the QR code and address presented as a focused payment surface.

Opal Wallet receive screen on iPhone Opal Wallet copied receive address feedback on iPhone

ReceiveA focused QR and address screen makes receiving BCH direct.

CopiedCopy feedback confirms the address action immediately.

Opal Wallet receive screen on Mac

ReceiveThe Mac receive screen keeps the same payment information visible.

04

Activity and transactions

Activity views keep payment context visible after a send, from pending state to transaction history.

Opal Wallet pending transaction detail from send confirmation on iPhone Opal Wallet confirmed transaction detail with 1281 confirmations on iPhone Opal Wallet newly confirmed transaction detail on iPhone Opal Wallet transaction list on iPhone

PendingA new transaction can be inspected while it is still pending.

1,281Confirmed transaction detail remains readable after deeper confirmation.

1 confA newly confirmed transaction has its own detail state.

ListThe account history brings transaction context back into one list.

Opal Wallet transaction view on Mac

TransactionThe Mac transaction view keeps the same payment detail readable.

05

Filtering and management

Wallet management and filtering show the product standard beyond the first send or receive action.

Opal Wallet transaction filter on iPhone

FilterFiltering helps narrow activity without leaving the account view.

Opal Wallet manage wallet view on Mac

ManageWallet management gives the desktop app a practical control surface.

06

Advanced wallet capabilities

CashFusion is already visible on Mac, while broader advanced wallet work stays carefully scoped.

Mac
Opal Wallet CashFusion screen on Mac

CashFusionCashFusion is visible on Mac without implying platform parity or delivery in this phase.

How the wallet work can be checked

Screenshots show the app surface. The underlying Bitcoin Cash work is also visible through the public Swift stack, and monthly updates can link back to the repositories behind validation, demos, and production-readiness decisions.

Opal Base Wallet and Bitcoin Cash foundations used to connect app behavior with public implementation work.
SwiftFulcrum Fulcrum client work behind balance sync, address monitoring, transaction detection, and network behavior checks.
Opal Crypto Cryptographic building blocks for transaction, key, and validation work that should not be hidden behind screenshots.
Opal Fusion and Opal Hedge BCH-community workstreams that stay visible while the main campaign remains centered on core wallet reliability and production readiness.

Funding plan

What the $68,250 planning value funds.

The visible target remains 350 BCH. The operating plan is easier to judge in USD: about $68,250 at the $195/BCH planning baseline, covering six months of focused Swift wallet engineering and production-readiness work.

Target
350 BCH
BCH/USD
1 BCH = $195.00
Estimated value
About $68,250

Operating budget

The allocation stays fixed to the $195/BCH planning baseline so you can read the work clearly. Monthly reports will note material BCH/USD impact on scope or priorities if the realized value moves away from the planning value.

Each row below names the output you should be able to inspect, not just the activity being funded.

Use Planning value
Core wallet reliability Send, receive, sync, wallet management, transaction history, live address monitoring, incoming transaction detection, and confirmation-state handling. $19,500
Recovery and safety BIP-39 restore checks, manual backup guidance, wallet-consent boundaries, key-protection documentation, transaction safety checks, and known-limitation reporting. $12,675
Apple-system wallet actions App Intents mapping for receive, request, activity lookup, payment preparation, Opal Wallet review paths, Shortcuts action surfaces, and Siri prompt surfaces where supported. $10,725
Production-readiness validation and demos Validation reports, public demo material, screenshots, issue triage, readiness notes, and visible production-readiness decisions. $8,775
Public Swift stack, docs, and monthly reports Public Swift stack milestones, public repository links, README/API cleanup, monthly Blog reports, documentation, and explanations connecting stack work to wallet behavior. $5,850
BCH advanced workstreams macOS CashFusion production-readiness context, Opal Fusion notes, AnyHedge roadmap context through Opal Hedge, and BCH-community workstream reporting. $3,900
Volatility, fees, admin, and contingency Budget-impact notes when BCH/USD assumptions change, FundMe/payment fees, basic administration, small operating needs, and priority adjustments. $6,825
Total $68,250

Planning note: The allocation uses a fixed $195/BCH baseline, so 350 BCH is shown as about $68,250. Fee handling stays inside the contingency row; monthly reports will explain any material BCH/USD budget impact.

How you judge progress

Each monthly update should answer the same practical questions: what changed, what was validated, what you can inspect, what remains open, what comes next, and whether BCH/USD movement changed priorities.

Completed work Wallet flows, interface work, production-readiness decisions, and public Swift Bitcoin Cash stack updates completed during the month.
Validation notes Recovery checks, transaction testing, address monitoring, failure handling, known limitations, and links to relevant public Swift stack work.
GitHub and demo material GitHub milestones or public-stack links, screenshots, demo videos, public transaction references, or test transaction references when they help verify a specific behavior.
Budget impact Budget notes when BCH/USD movement materially changes scope, priority, or the use of the contingency line.
Next focus Open items, next-month priorities, and any phase-one assumptions that changed.
Month-6 retrospective A final phase-one report with completed flows, validation links, open release issues, budget-impact notes when material, and phase-two priorities.

Accountability and scope

Accountability for this pass stays simple: public reporting, open repository activity, a community letter for context, and a dedicated fundraising email for campaign questions.

Funding path

The funding action runs through FundMe.cash. You pledge with a WalletConnect-compatible Bitcoin Cash wallet, and FundMe.cash handles the target and refund path through its campaign flow.

Monthly reporting

Monthly updates will be published on the Blog with a consistent rhythm: completed work, validation notes, GitHub milestones or public-stack links, screenshots or demo videos, budget-impact notes, open items, and next focus.

Open verification

The Opal Wallet consumer app and frontend remain closed-source. Opal Base, SwiftFulcrum, Opal Crypto, Opal Fusion, and Opal Hedge are the open-source public Swift stack tied to the funded work.

Security posture

Wallet secrets are protected using Secure Enclave-backed device security and Face ID. The seed is never transmitted, and sensitive wallet operations require local device authentication.

Core scope first

The main ask is a reliable, recoverable iPhone and Mac wallet. visionOS/watchOS companion support and advanced BCH features stay visible, but they do not replace core wallet reliability.

Roadmap hierarchy

The campaign keeps a broad Apple-platform ambition, but the order matters. Core wallet reliability and safe wallet actions come first.

Core wallet first iPhone and Mac wallet reliability, live transaction detection, recovery checks, cleaner history management, QR scanning, a personalized balance activity chart, reporting, and production-readiness decisions are the center of the 6-month phase.
visionOS and watchOS support visionOS and watchOS support stay on the roadmap as companion Apple-platform surfaces around the core wallet: glanceable activity, receive/request context, and careful review handoff rather than autonomous payment movement.
BCH-community workstreams CashFusion and AnyHedge stay visible because they matter to the BCH community, while core wallet reliability remains the main production-readiness ask.
Fund on FundMe.cash

This 350 BCH campaign uses FundMe.cash. Pledgers need a WalletConnect-compatible Bitcoin Cash wallet, and the PledgeNFT preserves refund access through the FundMe.cash campaign flow.

Public stack

The public Swift Bitcoin Cash foundation is visible.

Opal Wallet is built by 58 Opals. The Opal Wallet consumer app and frontend remain closed-source, while the public Swift Bitcoin Cash infrastructure behind it is open source.

Opal BaseShared Swift wallet and Bitcoin Cash foundations. SwiftFulcrumFulcrum client work for Bitcoin Cash infrastructure. Opal CryptoCryptographic building blocks used by the Swift stack. Opal FusionCashFusion-oriented Swift work for privacy-focused wallet capabilities. Opal HedgeAnyHedge roadmap work in the public Bitcoin Cash stack.