From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6CFFEC0051 for ; Sat, 3 Oct 2020 05:21:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 4F7DD86887 for ; Sat, 3 Oct 2020 05:21:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pMMmuDYeCb1L for ; Sat, 3 Oct 2020 05:21:21 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from secmail.pro (secmail.pro [46.226.111.104]) by whitealder.osuosl.org (Postfix) with ESMTP id 3434A868AF for ; Sat, 3 Oct 2020 05:21:20 +0000 (UTC) Received: by secmail.pro (Postfix, from userid 33) id 17D3D40A6D; Sat, 3 Oct 2020 07:21:19 +0200 (CEST) Received: from secmail63sex4dfw6h2nsrbmfz2z6alwxe4e3adtkpd4pcvkhht4jdad.onion (localhost [IPv6:::1]) by secmail.pro (Postfix) with ESMTP id 05C042B39B2 for ; Fri, 2 Oct 2020 22:21:17 -0700 (PDT) Received: from 127.0.0.1 (SquirrelMail authenticated user lee.chiffre@secmail.pro) by giyzk7o6dcunb2ry.onion with HTTP; Fri, 2 Oct 2020 22:21:17 -0700 Message-ID: <976903d1529adef2aff8839290a91f2c.squirrel@giyzk7o6dcunb2ry.onion> Date: Fri, 2 Oct 2020 22:21:17 -0700 From: "Mr. Lee Chiffre" To: bitcoin-dev@lists.linuxfoundation.org User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Mailman-Approved-At: Sat, 03 Oct 2020 20:22:27 +0000 Subject: [bitcoin-dev] A thought experiment on bitcoin for payroll privacy X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Oct 2020 05:21:24 -0000 Lets pretend that I have a company. I'll call it cut throat industries. We are a box cutter testing firm. HR pays the employees biweekly Fridays. In the current way. Cut throat industries pays a single transaction with the company's treasury as the input and each employee payroll as an output. There is no address reuse because HR has a xpub provided by each employee for their payroll wallet. I have 120 employees. The problem The concern is the competition of my precious company and employees seeing our worth and amount in our treasury account. This also exposes how many employees we have and an idea of what the average payroll is. One of my employees is Frank. Frank gets paid then a couple days later he buys some random thing that should not be talked about from a coworker. The coworker can observe Franks input and know what Frank makes. There is another time where cut throat industries is in a temporary financial clamp down. To save money my company is not giving bonuses for the rest of the fiscal year. But one employee of mine has done a very good job at cutting and I was afraid he was going to leave my agency if I did not make an exception for him. So I gave him a raise but not others. Employees notice that one of the 120 biweekly outputs is higher than usual. So they know someone got a raise. Problem summary I am paranoid because I run a company with my finances transparent to my competition and my employees. And my employees are starting to get concerned because their income is transparent to everyone also. These employees are dangerous and professional cutters. I don't want to upset them. What can I do to use bitcoin with privacy to eliminate these concerns? Lightning network is not much an option because they do not have inbound balance to get paid. I cannot front up funds of my own to give them inbound balance because it would consume all of my treasury to lock up funds. So it seems that I have to do payroll on chain. What do I do? -- lee.chiffre@secmail.pro PGP 97F0C3AE985A191DA0556BCAA82529E2025BDE35