aljaz/specs
1
1
Fork 0
mirror of https://github.com/bits-wallet/specs.git synced 2025-12-17 05:34:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update 04.md

Browse Source
This commit is contained in:
brqgoo
2023-01-16 16:55:44 +03:00
committed by GitHub
parent 44265816cf
commit c8b644908c
1 changed files with 0 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
04.md
View File

@@ -11,8 +11,6 @@ This BDS defines a privacy-preserving, footprint-minimal, offline swap-in mechan
## Rationale ## Rationale
[BDS-01](https://github.com/bits-wallet/specs/blob/main/01.md) mandates BitsApp channels to operate one-way-only for the interactivity benefits. This means inbound payments are not allowed for BitsApp channels. Sending on BitsApp is off-chain only, and receiving is on-chain-only. The only way to receive on-chain liquidity through lightning is submarine swaps. However, submarine swaps have many drawbacks: [BDS-01](https://github.com/bits-wallet/specs/blob/main/01.md) mandates BitsApp channels to operate one-way-only for the interactivity benefits. This means inbound payments are not allowed for BitsApp channels. Sending on BitsApp is off-chain only, and receiving is on-chain-only. The only way to receive on-chain liquidity through lightning is submarine swaps. However, submarine swaps have many drawbacks:
### On-chain footprint
Cannot allow batch openings, consuming more on-chain footprint. A third party (i.e. on-ramp exchange) cannot open a channel for two other parties (between the user and LSP), among other outputs. Note that Vortex enables batch openings as a side result but requires interactivity pre-channel formation.
### Receiver privacy ### Receiver privacy
Offline receiving is not possible without compromising privacy. Offline receiving is not possible without compromising privacy.