From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B009AC52 for ; Thu, 14 Mar 2019 01:17:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 308DEFD for ; Thu, 14 Mar 2019 01:17:44 +0000 (UTC) Received: from ip-10-217-1-36.ap-northeast-1.compute.internal (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id C6CE614C0C5 for ; Thu, 14 Mar 2019 10:17:43 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1) by 0 with SMTP; 14 Mar 2019 10:17:43 +0900 X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id B3EF24C06D for ; Thu, 14 Mar 2019 10:17:43 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw22.oz.hdemail.jp (ip-10-127-175-123.ap-northeast-1.compute.internal [10.127.175.123]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id A70BF14C0C5 for ; Thu, 14 Mar 2019 10:17:43 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qt1-f199.google.com (lb06.oz.hdemail.jp [54.238.50.28]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw22.oz.hdemail.jp (Postfix) with ESMTP id 4487B148C10B for ; Thu, 14 Mar 2019 10:17:43 +0900 (JST) X-Received: by mail-qt1-f199.google.com with SMTP id o56so3857074qto.9 for ; Wed, 13 Mar 2019 18:17:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=wjfgEydcjvciD3X/P/LvWLss1dTJcjAuvadHh8mP5IM=; b=q1JOBl/t8QTIYjV3Nqf36pgGsfjHXFwsbJ8OH9jbFgR+aL00r6ackTQKwLpjHCqogn zNnnTlcSQxnOoNd/SSR03PUP/q0L1zd6O3TNnwGHY7k/+lvm+zINx43c/WYwShd1TWiR RNsG3btO0CPVZrLj7SCTu4FGenyD0NIZ3LwEQj4FqndDk8wK3KLu2VwAeDPf69kzNLwp QJY4cc90SEdoGv+smcdOPs33336DFARi2B6o+orp5gvZJXpaDYmz5l0ItzbZDQppbsV1 /N5kt6mtBT/70WtPi6+Bjvyy9PQD9QQGoIpQfkt6n3u6re3QtCTIYNew/DciCCEIDk11 8sPg== X-Gm-Message-State: APjAAAUgHibJn3P1QBswGYInxxPukDS7jODvJn6J5t2KfEnEnbPEaiWT 9Vb7u65xZOwZkfLgOXBXmm8gsLVr6/jW5W1obvFuPuJvGrnrN0NUxJmw+Eu+V1w0QNSXwIhQoSR ZoUOt1GrAfsgl7H951jhYy8uS14/+eemFG4KNIFz9l7n2zHNM5WoiMe6Pfpox+gJUmVyMX1Muwy zN3ZR3qHxWGxanUjSf+XLoDDqziUIq4BGh431/yIa8XvLx+CEE/V0oKtnzT1qlcNW9AT1UM3muT 7rll3HVV/Hd13SqjqupwTzxlFgE7svv8Ld6OcCNFqot1bxSgcwz3sj53ZoTVDZq6btB1UTFkQ/B gSgWs8xQUhIEgMH0QWHCBlvFFUs= X-Received: by 2002:ae9:ec13:: with SMTP id h19mr24698667qkg.345.1552526261984; Wed, 13 Mar 2019 18:17:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqwXsynd2j+2KV43CpREbmtREcwD/LKCOdEWOjI+oMYV/xb2jNC8X6LTWyAz4MDCjoiVaR2313HaTpHhPND/140= X-Received: by 2002:ae9:ec13:: with SMTP id h19mr24698655qkg.345.1552526261810; Wed, 13 Mar 2019 18:17:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Karl-Johan Alm Date: Thu, 14 Mar 2019 10:17:31 +0900 Message-ID: To: Varunram Ganesh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 14 Mar 2019 02:53:19 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Signet X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2019 01:17:45 -0000 Hi Varunram, On Wed, Mar 13, 2019 at 3:41 PM Varunram Ganesh wrote: > > I like your idea of a signet as it would greatly help test reorgs and stu= ff without having to experiment with regtest. But I'm a bit concerned about= running a common signet (Signet1) controlled by a trusted entity. I guess = if someone wants to test signet on a global scale, they could spin up a cou= ple nodes in a couple places (and since it is anyway trusted, they can choo= se to run it on centralised services like AWS). Another concern is that the= maintainer might have unscheduled work, emergencies, etc and that could af= fect how people test stuff on. This would also mean that we need people to = run signet1 nodes in parallel with current testnet nodes (one could argue t= hat Signet is trusted anyway and this doesn't matter, still) > > I'm sure you would have considered these while designing, so would be gre= at to hear your thoughts. For starters, I assume that the signer would run an automated script that generated blocks on regular intervals without requiring manual interaction. So even if the signer went on a vacation, the network would keep on ticking. I also assume the signer would be running a faucet service so users could get coins as needed. Ultimately though, if a signer ended up vanishing or being unreliable, people would just set up a new signet with a different signer and use that instead, so ultimately it's not a big deal.