From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 43782C016F for ; Wed, 27 May 2020 04:12:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 2C88387E93 for ; Wed, 27 May 2020 04:12:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JEq6+v02v-zg for ; Wed, 27 May 2020 04:11:59 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch [185.70.40.135]) by hemlock.osuosl.org (Postfix) with ESMTPS id 439DE87D8E for ; Wed, 27 May 2020 04:11:59 +0000 (UTC) Date: Wed, 27 May 2020 04:11:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1590552717; bh=VqqgVxSh008aBdmHAX12AM5lwhAaN8xkIJBCQi4gaJc=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=kvmUGiKk9EoAkLlSg+q+Kg1Yno+jA6J6HJpKW+D5kKfSjYorVaGDs5IYz3hxyzLrt 9EM0rc8/NjvX7+B5mZiQos23EV7MOc5a/LP/mqTveNMaPdug4ho0WgH/LvUbPM+R3b k3JbnXDFTNWOo0XpBjJwdjR7FkyraLq2QJUsmAEM= To: Prayank From: ZmnSCPxj Reply-To: ZmnSCPxj Message-ID: <5cRx3Q_UFKDJkF0Jc8XcZEHHwbPxc85YbGPcITRMweC9qdfhmZLT3AVdnqpej5poLdl8t2JiHyRofBD22yv_lxFlxz2J6N8eiBHsMRM_cBQ=@protonmail.com> In-Reply-To: References: <3K6kmk75oNFwNf_E4xqPgf5URJOf4c64Iyxi1HOgEpvvZrdn_wBWxbx3hRBEDfu2MjC5kF6N0ejpjqeG_5FTGIFD_45sFyhLCtMvhJNdq3E=@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Post-mix(coinjoin) usage with multisig and cpfp in bitcoin core wallet 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: Wed, 27 May 2020 04:12:01 -0000 Good morning Prayank, > 1. The spending tx of multisig can be decided earlier and all three can = review the outputs involved in it. All 3 txs involved in the system if we c= onsider only one mixer and not a chain will get confirmed in the same block= as we are using CPFP so child pays for 2 parent txs. However, disputes are= possible and to manage it we will have to make the system complex with thi= ngs like Peer 1 locking some amount in a 2 of 2 multisig with Peer 2 or som= e other incentives structure. Initially we can try to keep it simple and a = way to spend coins after coinjoin with the help of another person you trust= . The payee is not necessary here and you can remove the intermediate transac= tions that pay to 2-of-3s. > 2. Yes, you described coinjoin in joinmarket but the problem I am trying= to solve is: spend coins after coinjoin because post-mix usage is as impor= tant as coinjoin. Some users dont follow the best practices after coinjoin = and it makes coinjoin useless or less effective in that case and sometimes = for others involved in the process as well. ... I already mentioned this, but what I am describing is *how JoinMarket spend= s coins from its wallet*. That means that what I am describing is *how JoinMarket performs spends aft= er mixing, i.e. post-mix*. I was not describing how JoinMarket performs mixing. Is that clearer now? Regards, ZmnSCPxj