nopara73

Author: Kukks

New protocol design: Discrete Payments through Wabisabi coinjoins and Nostr ecnrypted communication

1. Merchant creates invoice of 0.1BTC
2. Merchant generates a unique key for invoice
3. Merchant shows the pubkey of (2), a recommended nostr relay uri
4. Customer generates a unique key for this invoice payment
5. 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

nopara73

Infographics: https://i.imgur.com/zGygu4U.jpg

Luke Dashjr, a prolific Bitcoin Core developer, has been sent to Twitter jail: he received a permanent suspension for proclaiming he'll respond with appropriate force if anyone tries to force vaccination on him or his family. To avoid confusion it's important to clarify he does not have an anti-vaccine stance, rather he took a wait for more data approach instead.

Bitcoin is the future of money, a technology that is as fundamental to humanity as speech itself. It is paramount for mankind to thrive. Luke spent over a decade working on this technology, therefore taking away his access to public communication channels is great disservice to society itself.

Flexes:

- Core dev
- BIP maintainer

nopara73

What do the users want?

• faster mixes
• cheaper mixes
• no changes
• more money a user have, the more output it tolerates
• avoid coin bloat
• low minimum denomination

Output Creation

nopara73

This happens when an unconfirmed transaction spent a coin of yours, but your Wasabi somehow lost knowledge about it. Note that you are going to doxx your IP address to the block explorers mentioned below, unless you do this over Tor browser.

1. Expand the coin details and check the TransactionId and the Index
2. Search for the TransactionId in http://blockstream.info and search for the Index in the outputs.
3. Click on the address and you'll see all the transactions concerning that address.
4. One of those transactions spend your coin. If the address transactions are too large and you cannot find the spender, then check https://www.smartbit.com.au/
5. The advantage of SmartBit is that you can click on the spender transaction unlike Blockstream.info, however the disadvantage of SmartBit is that it doesn't provide indexes to the inputs and outputs.
6. Finally acquire the unconfirmed spending tarnsaction hex that your wallet is not aware of with the following call: `https://blockchain.info/tx/6f31577df3

nopara73

UPDATE: FIXED! https://github.com/zkSNACKs/WalletWasabi/pull/1341/commits/2e732b1f54b9107649c09a509c3088b90c2b2494#diff-bc431b4bc31acb6d49cd62c6288310e7R280

1. PSBT passed to Coldcard (Hex + Decoded)

cHNidP8BAFIBAAAAAc7zcL29QILOKmfw2HxoIPW+ptT73rk9dlDTKAKnDZTvAQAAAAD/////AXjzAgAAAAAAFgAUyI/BVg66hOg6mhA75T7jNY4Q9LcAAAAAAAEBH0ANAwAAAAAAFgAUqzA+o/d8FXwN9KUcOx8sOnTCrlEiBgIn178QYmbFrS8Bge/N+qOdlTmwHmXldAfk1XwRUxUutBh6iOeiVAAAgAAAAIAAAACAAAAAAAEAAAAAIgICCkeqqmQACENtyZREwn1I4O7gA6eAVfNwPgEeYM/EaisYeojnolQAAIAAAACAAAAAgAAAAAADAAAAAA==

nopara73

Adversary	Core	Core + Tor	Wasabi 1.1.3	Wasabi 1.1.4	Wasabi 1.1.4 + Full Node
One Peer Is Malicious Spy	private	private	private	private	private
All Peers Are Malicious Spies	vulnerable[1]	private	vulnerable[2]	private	private
Tor Breaker	private	private	private	private	private
All Peers Are Malicious Spies && Tor Breaker	vulnerable[1]	vulnerable[1]	vulnerable[2]	vulnerable[1,2]	vulnerable[1]
Malicious Wasabi Backend	private	private	private	private	private
Malicious Wasabi Backend && Tor Breaker	private	private	vulnerable[1]	private	private
Supernode	vulnerable[1]	private	private	private	private
Spying ISP	vulnerable[1]	private	vulnerable[2]	private	private

nopara73

  BIP: ?
  Layer: Applications
  Title: Address Paste Improvement
  Author&#58; nopara73 <[email protected]>
          David Molnar <[email protected]>
  Comments&#45;Summary&#58; No comments yet.
  Comments&#45;URI&#58; 
  Status&#58; Draft
  Type&#58; Standard Track

nopara73

Most active GitHub users (git.io/top)

The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Mon, 01 May 2017 19:27:03 GMT till Tue, 01 May 2018 19:27:03 GMT.

Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:

githubUsers
 .filter(user => user.followers > 1000)

nopara73

ExtKey _fundingExtKey = _seed.ExtKey.Derive(0, hardened: false);
BitcoinAddress fundingAddress = _fundingExtKey.ScriptPubKey.GetDestinationAddress(_network); // mkvRuHAv3qek4mP3ipjqFnaFXj4d2kKit3
WriteLine($"{nameof(fundingAddress)}: {fundingAddress}");
uint256 txIdToSpend = (await _qBitClient.GetBalance(fundingAddress, unspentOnly: false).ConfigureAwait(false)).Operations.First().TransactionId;
ctsToken.ThrowIfCancellationRequested();
Transaction txToSpend = (await _qBitClient.GetTransaction(txIdToSpend).ConfigureAwait(false)).Transaction;
ctsToken.ThrowIfCancellationRequested();

// BUILD OFFER TRANSACTION

nopara73

using NBitcoin;
using NBitcoin.Policy;
using QBitNinja.Client;
using System;
using System.Linq;
using System.Threading;
using System.Threading.Tasks;
using static System.Console;

namespace HTumbleBitProofOfConcept