perun-primary-sources-2026-05-14

Perun primary sources

Reviewed: 2026-05-14 UTC

Official homepage

• https://perun.network/
  • Best concise summary of Perun’s current positioning.
  • Used to confirm that Perun presents itself as an off-chain framework for real-time payments, complex business logic, interoperability between blockchains, offline payments, and AI/IoT-style micropayment use cases.
  • Also useful because it frames Perun as more than a paper: there is an SDK surface, a node surface, and a productized Perun-X swap surface.

Technology / research page

• https://perun.network/technology/
  • Best source for Perun’s own decomposition of the research stack.
  • Used to confirm that Perun grounds itself in state channels, claims blockchain-agnostic offchain execution with blockchain-as-judge dispute handling, and explicitly points to four research tracks: General State Channel Networks, Virtual Payment Channel Hubs, FairSwap, and Multi-Party Virtual State Channels.
  • Important because it makes clear that Perun should be cataloged as a protocol-and-research family, not just a product page.

Introductory whitepaper note

• https://www.perun.network/wp-content/uploads/Perun2.0.pdf
  • Saved locally as perun2.0-whitepaper.pdf.
  • Best single introductory document surfaced in this pass for the virtual-channel construction and Perun-over-Ethereum framing.
  • Used mainly as the canonical introductory paper reference because Perun’s repos and docs repeatedly point to it as the intro paper.

Framework documentation

• https://perun-network.github.io/perun-doc/
  • Best high-level documentation hub for the software framework.
  • Used to confirm that Perun is framed as a modular framework for blockchain-agnostic payment and state-channel applications, including both blockchain and classical transaction backends.
  • Also useful because it documents the split between protocol, concepts, SDK, and node components.

Framework introduction

• https://perun-network.github.io/perun-doc/introduction.html
  • Best source for Perun’s own explanation of why it is different from ordinary bilateral channel systems.
  • Used to confirm the core claim that a handful of main-chain transactions can support a wider offchain peer-to-peer network and that users can transact via virtual channels without extra onchain setup.
  • Also used to confirm the explicit comparison against Lightning-style channel technology, the blockchain-agnostic framing, and the current roadmap gap where virtual channels and wider cross-chain features remain roadmap items in the implementation stack.

go-perun SDK repository

• https://github.com/hyperledger-labs/go-perun
  • Best source for the concrete implementation surface.
  • Used to confirm that go-perun is a blockchain-agnostic Go implementation of the Perun protocols with injected backends, messaging, logging, persistence, watcher logic, and current support or partial support for multiple chains.
  • Especially important for implementation-status nuance: the repo lists generalized state channels, dispute watchtowers, data persistence, virtual payment channels (direct dispute), and multi-ledger channels as current features, while indirect-dispute virtual payment channels, virtual state channels, and multi-party channels remain planned.

perun-node repository

• https://github.com/hyperledger-labs/perun-node
  • Best source for the operator-facing node layer.
  • Used to confirm that Perun is not only an SDK but also a multi-user node with key management, identity management, session handling, persistence, and user APIs on top of the core protocol.
  • Important because it shows where practical control can accumulate: node operators, API surfaces, key custody, and user-session management.

Perun-X product page

• https://perun.network/perun-x/
  • Best source for the current application-facing productization of the Perun stack.
  • Used to confirm that Perun-X markets cross-chain atomic swaps, decentralized multi-hubs, and channel-level security plus TEE, with live or adapter-ready integrations across Ethereum, Bellecour, Stellar, Polkadot, Cosmos, Cardano, Internet Computer, Fabric, Nervos, Solana, and Lightning-research paths.
  • Useful because it exposes the hub/liquidity/operator layer that can otherwise get hidden when Perun is described only as state channels.

Main takeaways from this pass

• Perun is worth cataloging separately because it provides a clean state-channel and virtual-channel comparison point beneath later cross-chain swaps, interop, and payments products.
• The most reusable analytical split is between base ledger channels, virtual-channel composition, backend-specific funding/adjudication adapters, and operator-facing node or hub layers.
• The source set makes implementation drift legible in a useful way: Perun’s research and docs strongly emphasize generalized and virtualized state-channel networks, but the public software stack still presents parts of the virtual and multi-party surface as partial or roadmap items.
• Perun-X is useful evidence that state-channel research can evolve into cross-chain-swap and hub-style operating surfaces, which means future comparisons should not stop at cryptographic channel design alone; they should also track who runs liquidity hubs, nodes, watchtowers, and APIs.