Hitch — txbt4 channels · a node in this tabtestnet4 · test coins
Balances
In channels (spendable):… In channels (theirs):… In flight (HTLCs out):… Settling on chain:… Opening (unconfirmed):… On chain (available):… On chain (immature):… Channels:…
A channel is a 2-of-2 output on txbt4 that this tab funded, watches and can settle itself; the balances inside it move between tabs over the relays without touching the chain. On-chain coins are the wallet key's, read from the tab's own validated UTXO set.
This node
Node id:…Chain address:…Node:…Relays:…
Give your node id to the other side; a channel is opened to a node id. Reef's key in this browser is used when there is one, so Reef's coins fund channels and Reef sees what comes back.
Recent activity
nothing yet
Open a channel
sat, from this tab's on-chain coins
sat of it credited to the other side at once, so a hub can pay you back through this channel
Pay an invoice
Or push to a channel
sat
Make an invoice
sat
An invoice names this node, an amount, a payment hash and the hubs this node has channels with; it expires after an hour. The payment is an HTLC on a channel to this node or through one of the hubs; this tab settles it with the preimage. Channel messages are signed, not encrypted: memos and amounts are readable on the relays.
Activity
Starting the node…TESTNET4 · BLAKE2b
Question
About Hitch

Hitch 0.1 · payment channels in a browser tab, for txbt4, the BLAKE2b testnet4.

The Lightning shape without the network: a 2-of-2 funding output, asymmetric commitments with a revocable to_local, penalties for old states, cooperative and forced closes. Funded, watched and settled by the tab's own node; messages between tabs over the relays. Not compatible with Lightning peers, and not private: channel messages are signed, not encrypted.

Source · AGPL-3.0-or-later.
Options
channel messages and transactions are published to each; the same relays are followed for messages to this node
blocks (…) before a forced close pays its owner; the other side may punish a revoked close within it. Channels opened to you are refused below 6.
sat per channel transaction, paid by the funder
The channel documents hold the signed commitments and the revocation secrets, not the key. Losing them means the other side can close at any signed state and cannot be punished for an old one; export after every session that changed something, and keep the file where only you can read it. Never restore an old copy over a newer one: a channel restored at an old state and force-closed is a cheat, and is punished.