You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These notes refer to the setup described in table and diagram form here.
Why tweak the original Coinswap design.
The original design is explained in the original CoinSwap post.
The reason for attempting to come up with a modification is seen in the diagram line E:
WabiSabi is a protocol (work in progress)
for constructing CoinJoin
transactions with the aid of a centralized coordinator. It utilizes keyed-verification
anonymous credentials, homomorphic value commitments, and zero knowledge proofs to
achieve privacy and flexibility.
Wasabi Wallet v1.1.12 deterministic build for bitcoinbinary.org
This video and guide should give everyone a fairly easy to follow and repeat the reproducible build for the Windows MSI package of Wasabi Wallet.
Since there is currently (2021-09-12) a problem with the automated deterministic build and I was unable to build the last three releases (v1.1.12.7 - v.1.1.12-9) this can act as a baseline to start and bisect the build issues and figure out where it stopped working.
New protocol design: Discrete Payments through Wabisabi coinjoins and Nostr ecnrypted communication
Merchant creates invoice of 0.1BTC
Merchant generates a unique key for invoice
Merchant shows the pubkey of (2), a recommended nostr relay uri
Customer generates a unique key for this invoice payment
Customer posts an encrypted event addressed to pubkey of (3) with a message stating intent to pay invoice of 0.1BTC using a specific wabisabi coordinator
Ecash mints funded with Spillman channels: The ultimate nodeless Lightning wallet
Overview
This proposal introduces a self-custodial credit system that sits in front of an existing ecash mint. The users balance is held in a trustless credit contract that can be instantly swapped for ecash tokens offchain at the time of payment. Custodial risk only exists while payments are in flight, which is usually seconds, and only for the amount currently being transacted. The balance is always self-custodial and if the mint disappears or is uncooperative the user can unilaterally exit and reclaim their credits onchain.
The protocol works on Bitcoin today and does not require a soft fork or any new opcodes. Infact it doesn't require any opcodes at all. The protocol is almost entirely off chain, every possible way to execute the trustless credit contract results in a MuSig2 taproot key path spend onchain, no Bitcoin Script required.