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 98F029F0 for ; Sat, 8 Jun 2019 15:01:53 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0EE736D6 for ; Sat, 8 Jun 2019 15:01:52 +0000 (UTC) Received: by mail-wm1-f53.google.com with SMTP id u8so4455847wmm.1 for ; Sat, 08 Jun 2019 08:01:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XMU0azuiVHij9TV6T8BVqJP26xXawmGGncLmf7N1/AU=; b=IYBgyTHkiU7VBHSMp0/hrEpDKiDV3o6Nc8SNXCX4M11aHWbk437t7Y0xV0chUn78MA q1YTBaQqA5I12teCDs/Vc6ayZWFe3a57tIhQJBFY6ywl6KnDlrab5YS/qOKLtvN7JHi9 kJ4dqvNIyEGpGqKlWn92BsWEJyNVveVuNpsEhQMMwaJWzYVjGXE0mKv5QVLcOswReV0v oKUrQeVRRbic0SobGes87u4Io7jgvIaBi757nIB8tO0WhiYDt+fpqa2jx1VeYNCOoiR2 soXwHFJBRySJJQJmemMiqn4xV609ZiWbVZc9KY6omQM28urAQTYNBP13lL/Jt1r9hWuA X4ng== X-Gm-Message-State: APjAAAV6viCKFuyXtYtPzGFEG28uL5ijSMjAT/osinBZ1AvS6o+tZ4tq VzW7RBo+yHDVkGYXhkvEDy8niH+u X-Google-Smtp-Source: APXvYqzXZJUkwuKWSsuVZR4OwHQ+wA9+PYDVXmLA/LUsW6zEp0NVKmcyoU6urQPsOsjLPyWUj4y7lg== X-Received: by 2002:a1c:9cd1:: with SMTP id f200mr5599212wme.157.1560006111396; Sat, 08 Jun 2019 08:01:51 -0700 (PDT) Received: from ?IPv6:2a02:8108:8240:4e4c:527d:c7f:2174:340b? ([2a02:8108:8240:4e4c:527d:c7f:2174:340b]) by smtp.gmail.com with ESMTPSA id b5sm5242214wru.69.2019.06.08.08.01.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Jun 2019 08:01:50 -0700 (PDT) To: Bryan Bishop , Bitcoin Protocol Discussion References: <205859a9-635a-e958-a03f-8d9a35e0da1a@emilengler.com> From: Emil Engler Message-ID: Date: Sat, 8 Jun 2019 17:01:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, 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: Sun, 09 Jun 2019 08:19:23 +0000 Subject: Re: [bitcoin-dev] testnet4 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: Sat, 08 Jun 2019 15:01:53 -0000 I don't get why the testnet shouldn't be resetted just because there is a (probably better) alternative for it. The testnet is still a thing and is also used. Am 08.06.19 um 16:21 schrieb Bryan Bishop: > Be greeted Emil, > > On Sat, Jun 8, 2019 at 9:21 AM Emil Engler via bitcoin-dev > > wrote: > > Hello, I tried myself with some Bitcoin development. For this I used of > course the Bitcoin testnet. However it took me one hour to sync the > blockchain with around 1538358 blocks. In my opinion that is too much > for a testnet. Especially the blockchain size with around 26GB is so > much. Would it be possible to reset the testnet with a new genesis > block > ? And if so, can we setup a fixed cycle for resetting the testnet (For > example every second 1st of January) ? > > > At the moment, I somewhat doubt this is likely to happen. Signet > provides an alternative for configuring multiple separate private and > public testing networks. If you would like to get involved, check out > the recent discussion on the topic recorded here: > http://diyhpl.us/wiki/transcripts/bitcoin-core-dev-tech/2019-06-07-signet/ > > - Bryan > http://heybryan.org/