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

Update 04.md

Browse Source
This commit is contained in:
brqgoo
2023-01-16 16:53:16 +03:00
committed by GitHub
parent 4279e1a2d5
commit 923658675d
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
04.md
View File

@@ -18,13 +18,13 @@ Cannot allow batch openings, consuming more on-chain footprint. A third party (i
### Receiver privacy
Offline receiving is not possible without compromising privacy.
### Scalibility
### On-chain footprint
Submarine swaps don't scale. From sweeping funds to opening a channel, overall process consumes >182 vBytes in a HTLC-based approach and 142 vBytes in a PTLC-based approach:
| Type | HTLC output | HTLC outpoint | HTLC redeem | Channel output | Total |
|------------------------------|----------------|----------------|--------------|----------------|----------- |
| HTLC-based Submarine Swaps | 43 vBytes | 40 vBytes | 56 vBytes | 43 vBytes | 182 vBytes |
| PTLC-based Submarine Swaps | 43 vBytes | 40 vBytes | 16 vBytes | 43 vBytes | 142 vBytes |
| HTLC-based submarine Swaps | 43 vBytes | 40 vBytes | 56 vBytes | 43 vBytes | 182 vBytes |
| PTLC-based submarine Swaps | 43 vBytes | 40 vBytes | 16 vBytes | 43 vBytes | 142 vBytes |
## Specification
`Channel addresses`, as seen [here](https://burakkeceli.medium.com/channel-addresses-bd85e9ab8fe1) and [here](https://rubin.io/bitcoin/2021/12/11/advent-14/), make it possible to craft on-chain bitcoin addresses such that whenever funded by someone, becomes a payment channel between the user and the channel partner (LSP), where the channel funds are initially kept on the user's side. Channel address require new additions to the bitcoin scripting system, and planned as a future extension under [BDS-19](https://github.com/bits-wallet/specs/blob/main/19.md).