LibraryScaling2017Design paperCorpus record
Perun: Virtual Payment Hubs over Cryptocurrencies
Perun. Stefan Dziembowski, Lisa Eckey, Sebastian Faust and Daniel Malinowski.
Lightning routes each payment through the intermediaries. Perun asks those intermediaries to set up a virtual channel and then step out of the individual payments. The paper gives the construction for one hub, on a chain that can run the contracts.
Perun builds a virtual payment channel through one hub. The hub helps open it, then individual payments do not touch the hub or the chain. Disputes return to contracts on a chain that can express them. The formal result is one intermediary, not a global routing network.
The five-minute read
Virtual, not routed
A Lightning-style hop updates every channel on the path for every payment. A Perun virtual channel lets the two ends exchange payments on their own after setup.
The hub is real at the edges
The hub has ledger channels with each user. The virtual channel's funds are carved out of those. The hub is not gone. It is absent from the hot path.
Disputes need a rich chain
The security proof assumes smart contracts that can referee the channel. The paper is not a Bitcoin-script construction.
One hub is the theorem
Composing many hubs into a network is described as the direction, not as a proof in this version.
One action, walked through
- Each user opens a ledger channel with the hub on the underlying chain.
- The three parties agree to a virtual channel with a capacity and a timeout.
- The two users update that virtual channel off-chain for each payment.
- They close cooperatively, and the hub's ledger channels absorb the net.
- If someone cheats or disappears, the contracts on the ledger are the enforcement path, inside the timeout.
The argument, unpacked
Idle hubs are the point
The efficiency claim is that the intermediary does not wake up for every micropayment. A design that still pings the hub per payment has not used the virtual channel. It has used a route.
One honest period at dispute time
Off-chain systems are only as good as the dispute. A user who cannot post the dispute transaction in time loses the theorem's protection. The paper does not remove the need to watch.
What has to be true
- The underlying chain executes the contracts the construction uses.
- The hub and the users can be forced to settle before timeouts.
- Virtual-channel capacity was actually locked. An unfunded virtual channel is an IOU outside the paper.
- The adversary model is the one in the proofs, which includes a malicious hub. Read which theorem covers which party.
What happened after the paper
Perun is the citation for virtual channels through a hub, next to Lightning and Sprites. A payment system that says 'we are like Lightning but the hub is offline' is pointing at this idea, and still owes the dispute contract.
What to check before you use the idea
- Does a normal payment require the hub to be online?
- Which chain holds the dispute contract?
- What is the timeout?
- Is the result proved for one hub or for a network?
Terms
- Virtual channel
- An off-chain channel between two users, funded through a hub, that the hub does not update on every payment.
- Ledger channel
- The on-chain channel between a user and the hub, from which the virtual channel's funds are drawn.
The problem the paper names
A routed payment makes every intermediate node update its channels for every transfer. That costs liveness and attention from the hub. A virtual channel should let the two ends pay each other until they disagree or they close.
What the design proposes
- Two users each have a ledger channel with a hub.
- They and the hub open a virtual channel whose funding sits in those ledger channels.
- Payments inside the virtual channel are off-chain between the two users. The hub is not in the loop for each one.
How the mechanism is specified
- If everyone is honest, the hub learns that the virtual channel exists and then does not touch each payment.
- If someone misbehaves, the contracts on the underlying chain are the dispute path. The paper needs a chain that can express those contracts.
- The formal result is for one intermediary. A network of hubs is left as the obvious next composition, not as a theorem in this version.
What this page does not treat as proven
- This is not the Lightning paper and it does not run on Bitcoin's script as written. The model assumes richer contracts.
- A hub that disappears still forces a dispute. Virtual does not mean unsupervised.
- The paper does not establish the security of any later commercial hub.
Why a venture studio still reads it
Ask who must be online for a single payment. In Lightning, the route. In this paper, the two ends, until something goes wrong. Then ask which chain the dispute contract actually lives on.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.
