# UniPCH Proposes a Two-Layer Framework for Cross-Chain Payments

Published 2026-10-28 · Crypto.world Team · Crypto.world

> A paper submitted to arXiv on October 27 proposes UniPCH, a payment-channel-hub framework for private cross-chain transfers across UTXO and smart-contract account ledgers. Its Go prototype reports lower latency than XPCH in some test configurations, while the authors identify growing hub-channel and liquidity demands as a scaling cost.

> “We present UniPCH, a framework with two layers that separates native channel execution from private cross-chain payment logic.”
>
> [Yuanming Shao et al., UniPCH](https://arxiv.org/abs/2610.36866)

Six researchers submitted UniPCH to arXiv on October 27, proposing a common architecture for payment-channel hubs that move payments across blockchains with different ledger designs. The paper targets a practical integration problem: existing hub protocols may depend on a particular transaction format or execution model, forcing teams to adapt payment logic and repeat security analysis when adding a different kind of chain.

UniPCH separates that chain-specific work from the cross-chain payment protocol. Its lower layer, called UniPC, defines shared channel operations and security requirements; an upper layer coordinates transfers among hubs using those common interfaces. The authors provide channel realizations for UTXO ledgers and account ledgers with smart contracts, using Bitcoin and Ethereum as examples of the two models.

## UniPC separates channel rules from payment coordination

In the proposed architecture, users keep off-chain payment channels with a hub tied to their blockchain. Hubs also maintain channels with one another on a shared blockchain. For a transfer between users on different chains, the path can involve the sender’s hub, a coordinating hub and the receiver’s hub. The payment uses as many as four channels, according to the paper.

UniPC standardizes how a channel update is authorized and confirmed without requiring the upper-level protocol to interpret each chain’s native transactions. The authors’ selective re-signing blind conditional signatures, or S-RBCS, coordinate conditional authorization across the hubs. Their four-phase payment flow—Reserve, Promise, Convert and Solve—first establishes linked conditions and then settles the transfers, with refunds available if a payment does not complete.

The paper’s security analysis claims local channel security, resistance to griefing, economic atomicity and session unlinkability within an epoch, subject to its stated assumptions. Those include valid ledger execution within assumed delay bounds, fixed exchange rates during a payment and specific confidential or anonymous communication channels. The unlinkability claim also concerns a defined setting: colluding honest-but-curious hubs and payments sharing a coordinating hub and agreed amount.

## Prototype results favor the account-ledger path

The researchers implemented UniPCH in Go and compared it with A²L+, P2C2T and XPCH. Their default test workload used six blockchains, 50 users on each chain and five payments per user. UniPCH ran against three Bitcoin instances in regtest mode and three Ethereum instances supplied by Ganache; the experiments were conducted on a Windows 11 machine with an Intel Core i7-12700H processor and 24 GB of memory.

In the far-path account-ledger configuration, UniPCH recorded an average of 762.8 milliseconds and 44.42 KB per payment. The paper reports 1,026.2 milliseconds and 93.59 KB for XPCH’s far path in the comparison. The authors attribute much of the account configuration’s advantage to retaining valid authorization evidence instead of regenerating it after every update. Under an emulated 200-millisecond network delay, the far account configuration completed in 14.936 seconds, compared with 17.899 seconds for XPCH’s far path.

Results differed by ledger realization. In the far UTXO configuration, UniPCH took 1,048.4 milliseconds—slightly above XPCH’s 1,026.2 milliseconds—and used more bandwidth. UTXO updates require fresh evidence for active transfer tasks, while the account realization can retain evidence that remains valid. The reported gains therefore depend on the implementation and payment path, rather than establishing a universal speed advantage.

## Adding hubs brings a channel and liquidity cost

UniPCH’s framework does not remove the cost of connecting hubs. Its design assumes a fully connected overlay, requiring n(n−1)/2 channels among n hubs on the shared blockchain; each payment uses at most four channels. The authors caution that a larger hub set increases channel maintenance and funding requirements, while shared channels process updates sequentially and reserve liquidity for pending payments.

The results come from a prototype tested with local Bitcoin regtest and Ganache instances, not deployments on live public networks. UniPCH offers a defined way to adapt channel implementations while reusing the payment protocol, but a new chain still needs a conforming UniPC realization that satisfies the framework’s security requirements.

## Sources

1. Original source · Preprint [UniPCH: A Unified Framework for Cross-Chain Payments via Payment Channel Hubs](https://arxiv.org/abs/2610.36866) arXiv:2610.36866

## Related stories

- [Lightning force-closes cost 2–6 times more in fees, preprint finds](https://crypto.world/news/study-lightning-force-close-fee-cost)
- [BNB Chain Schedules Jenner Testnet Fork for Oct. 28](https://crypto.world/news/bnb-chain-jenner-testnet-hard-fork-october-28)
- [Stellar’s Project Thruput Hits 7.02M Payments Per Second in Test](https://crypto.world/news/stellar-project-thruput-7-million-payments-per-second)
- [Robinhood Chain Reports $26M in First Mainnet Quarter](https://crypto.world/news/robinhood-chain-26-million-first-mainnet-quarter)
- [Bitcoin Core Releases 31.2 With a 10,000-Entry Queue Limit](https://crypto.world/news/bitcoin-core-31-2-release-private-broadcast-queue-limit)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/unipch-two-layer-cross-chain-payment-framework
