From c8b644908c1b6c2126756433cef7006a281bfac7 Mon Sep 17 00:00:00 2001
From: brqgoo <100725376+brqgoo@users.noreply.github.com>
Date: Mon, 16 Jan 2023 16:55:44 +0300
Subject: [PATCH] Update 04.md

---
 04.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/04.md b/04.md
index c99cf9f..03b2f43 100644
--- a/04.md
+++ b/04.md
@@ -11,8 +11,6 @@ This BDS defines a privacy-preserving, footprint-minimal, offline swap-in mechan
 ## 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:
-### 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
 Offline receiving is not possible without compromising privacy.