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

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

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