TelRPC Brings Phone-Call Transactions to Cardano

TelRPC lists Cardano among the networks supported by its Android beta wallet, allowing users to send ADA through a telephone call without internet access from the wallet application. During the World Mobile Alliance Space, Rob, Cal, and Val examined the service through practical questions about custody, connectivity, fees, and adoption.

How Phone Calls Carry Cardano Transactions

TelRPC uses telephone keypad signaling tones to carry signed transaction information to its infrastructure. The receiving system, TELRPC Grid, decodes the message, reconstructs the transaction, and submits it to the appropriate blockchain. Cardano then validates a payment under its existing network rules.

The user checks the recipient and amount before approving the signature on a phone or supported hardware wallet. The private key remains on the signing device. The telephone connection carries the signed information needed for submission.

Preparing a payment still requires current public blockchain information. Depending on the network, this includes unspent transaction outputs or other data needed to construct the transaction and calculate its fee. TelRPC describes importing that information through QR codes, voice calls, manual entry, or callback signaling.

After submission, a brief callback carries a transaction reference through its caller ID. The wallet compares that reference with the transaction identifier it calculated locally. TelRPC calls this return channel an “echo” and also uses it for certain requests about blockchain state.

Offline signing is already established in Cardano. Its developer documentation describes preparing transactions, signing them on an air-gapped machine, and submitting the signed result. TelRPC adds telephone delivery to that separation between authorization and submission.

The project's published demonstration shows a USDC transfer on Base, taking approximately 95 seconds of telephone tones. That timing belongs to the demonstrated Base transaction; Cardano sending support is listed in the product documentation.

Rob, Cal, and Val Explore Practical Uses

Rob approached the product through a distinction familiar to wallet users: would it primarily serve cold storage and occasional transfers, or regular trading and swaps?

Cal described his own preference for keeping a smaller balance in a hot wallet for everyday DeFi activity. He saw TelRPC as an option for larger transfers, including making a substantial purchase. He also discussed potential applications in emerging markets where voice service is available but internet access is limited.

His account remained exploratory. Cal explained that he had downloaded and tried the wallet interface but had not yet completed a transaction. He wanted to provide feedback to the team and expressed interest in established wallets integrating the service.

Val brought the discussion closer to the World Mobile community. He highlighted wallets associated with SwitchNodes, ValidationNodes, and EarthNodes as examples of accounts whose owners have a reason to protect their signing arrangements. He also stressed the human factor in wallet security and the need for adoption beyond the initial release.

Those examples connect with the project's telecommunications structure. World Mobile develops community-supported network infrastructure, including AirNodes, while Minutes Network operates voice infrastructure connecting calls between networks.

TelRPC's architecture description assigns call handling to Minutes Network, blockchain data access and transaction submission support to World Mobile's EarthNode network, and local access-number support to UNetwork.

The Android wallet is available as a beta APK, with an iOS version planned. Its documentation lists Cardano support with selected Ledger and Trezor devices over USB-C and with the Keystone 3 Pro through QR codes. Compatibility depends on the model and software, including a firmware qualification for Keystone.

In these configurations, the hardware wallet approves and signs the payment on its own screen while the phone handles delivery. TelRPC states that compatibility does not constitute endorsement by the device manufacturers.

For institutional users, TelRPC describes keeping existing signing controls, including hardware security modules and arrangements requiring multiple approvals. A handset or dedicated module carries the signed transaction. Its institutional offering includes approved addresses, user roles, and exportable records for reconciliation.

A separate self-assembly Wallet Kit combines a Raspberry Pi computer, display, camera, and voice modem. Its product page still lists TELRPC Kit OS as awaiting publication, distinguishing that hardware offering from the available Android beta.

Fees, Availability, and Privacy Limits

Rob also raised a practical pricing question: did the quoted charge include blockchain network fees?

TelRPC's published pricing separates the costs. A broadcast uses $0.10 of prepaid credit, with additional charges for the blockchain transaction and the telephone call at the user's carrier rate. Certain other requests, including balance checks by call, also consume credit. The service charges per request rather than as a percentage of the transferred amount.

The project lists live local numbers in 15 countries, additional countries available on request, and a U.S. access line for users without a local number. Calling an overseas number can affect the total cost.

A working voice connection and functioning TelRPC infrastructure are required. The model can serve users without mobile data where telephone service remains available, while the receiving infrastructure must still reach the blockchain.

The security model centers on an Android application that does not request internet permission and on keeping signing keys under the user's control. The project's security description also identifies local interfaces, including the phone's operating system, QR input, and callbacks. It describes a dedicated phone or separate hardware wallet as options for additional isolation.

Privacy has a separate boundary. TelRPC states that its system and the telecommunications carrier can associate a telephone number with a blockchain address. Transactions remain public on their destination networks.

Detailed protocol specifications, the scientific whitepaper, and parts of the developer documentation are provided to partners under licensing and nondisclosure agreements. Public materials contain architecture descriptions and demonstrations.

Cal's interest in integration with established wallets and Val's emphasis on adoption have a specific development route in the product offering. Wallet developers can license TelRPC's protocol and reference implementation, while embedded hardware and SIM-based configurations are offered as implementations built with its team.

For users sending ADA, the Android beta is the currently available wallet route described by the project. Bringing telephone delivery into other wallets requires a separate integration of the signing handoff, call transport, and confirmation process.