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 17:35:31 +03:00
committed by GitHub
parent 2d723edb39
commit 9b6caa576b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
04.md
View File

@@ -26,8 +26,8 @@ Submarine swaps don't scale. From sweeping funds to opening a channel, overall p
## Specification
This BDS proposes a replacement for submarine swaps; silent swaps. Silent swaps are effectively a specialized form of submarine swaps, however, built in mind with scaling and privacy. Silent swaps utilize a channel factory approach to save massively on fees and space and use ECDH to enable offline receiving while preserving recipient privacy.
The sender non-interactively pays the recipient based on their dedicated Nostr pubkey npub without revealing the npub itself, similar to silent payments. The recipient can get paid without inbound liquidity issues, doesn't need to remain online to receive, and their npub is not doxxed to the rest of the network.
When a sender wants to pay the recipient, the sender initiates a swap-in payment through a specialized submarine service provided by TBD wallet SSP. Here's how it's done step-by-step:
The sender non-interactively pays the recipient based on their dedicated Nostr pubkey [npub](https://github.com/nostr-protocol/nips/blob/329cd8d8a19fd1dcb12df7eb7a5d640b2a5b6bf8/19.md?plain=1#L19) without revealing the npub itself, similar to [silent payments](https://gist.github.com/RubenSomsen/c43b79517e7cb701ebf77eec6dbb46b8). The recipient can get paid without inbound liquidity issues, doesn't need to remain online to receive, and their npub is not doxxed to the rest of the network.
When a sender wants to pay the recipient, the sender initiates a swap-in payment through a specialized submarine service provided by BitsApp SSP. Here's how it's done step-by-step:
### 1. The sender first generates a preimage and a tweaked destination:
* Where the recipient npub is `R = r*G` , and the sender npub is `S = s*G`.