summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Dashjr <luke@dashjr.org>2017-05-03 23:21:13 +0000
committerbitcoindev <bitcoindev@gnusha.org>2017-05-03 23:21:31 +0000
commit44fae840f437e5c76e6215e094a2ddf464a0a953 (patch)
tree2a3d793c8217675d6bfec15d0651c880eb8e2a9a
parent9a6dbcefab9ca4cc2ef2c77809692288dcbde610 (diff)
downloadpi-bitcoindev-44fae840f437e5c76e6215e094a2ddf464a0a953.tar.gz
pi-bitcoindev-44fae840f437e5c76e6215e094a2ddf464a0a953.zip
Re: [bitcoin-dev] Full node "tip" function
-rw-r--r--ea/b2b7cb9251f1e1b8a4f6502013d73945a623ca84
1 files changed, 84 insertions, 0 deletions
diff --git a/ea/b2b7cb9251f1e1b8a4f6502013d73945a623ca b/ea/b2b7cb9251f1e1b8a4f6502013d73945a623ca
new file mode 100644
index 000000000..0f4e13a78
--- /dev/null
+++ b/ea/b2b7cb9251f1e1b8a4f6502013d73945a623ca
@@ -0,0 +1,84 @@
+Return-Path: <luke@dashjr.org>
+Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
+ [172.17.192.35])
+ by mail.linuxfoundation.org (Postfix) with ESMTPS id 2BF78B73
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Wed, 3 May 2017 23:21:31 +0000 (UTC)
+X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
+Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21])
+ by smtp1.linuxfoundation.org (Postfix) with ESMTP id 0D1C2170
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Wed, 3 May 2017 23:21:29 +0000 (UTC)
+Received: from ishibashi.localnet (unknown
+ [IPv6:2001:470:5:265:a45d:823b:2d27:961c])
+ (Authenticated sender: luke-jr)
+ by zinan.dashjr.org (Postfix) with ESMTPSA id 5B5EF38A2263;
+ Wed, 3 May 2017 23:21:15 +0000 (UTC)
+X-Hashcash: 1:25:170503:bitcoin-dev@lists.linuxfoundation.org::NWceCsxZLYSl5je+:xnxH
+X-Hashcash: 1:25:170503:erik@q32.com::K+vmQacdblpBb8K4:a31um
+From: Luke Dashjr <luke@dashjr.org>
+To: bitcoin-dev@lists.linuxfoundation.org,
+ Erik Aronesty <erik@q32.com>
+Date: Wed, 3 May 2017 23:21:13 +0000
+User-Agent: KMail/1.13.7 (Linux/4.9.16-gentoo; KDE/4.14.29; x86_64; ; )
+References: <CAJowKg+snAUjbCFkTybNqiJCy=d_M3s5k376y1B=rVqD8WCOXA@mail.gmail.com>
+In-Reply-To: <CAJowKg+snAUjbCFkTybNqiJCy=d_M3s5k376y1B=rVqD8WCOXA@mail.gmail.com>
+X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
+X-PGP-Key-ID: BD02942421F4889F
+X-PGP-Keyserver: hkp://pgp.mit.edu
+MIME-Version: 1.0
+Content-Type: Text/Plain;
+ charset="iso-8859-15"
+Content-Transfer-Encoding: 7bit
+Message-Id: <201705032321.14356.luke@dashjr.org>
+X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
+ RP_MATCHES_RCVD autolearn=ham version=3.3.1
+X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
+ smtp1.linux-foundation.org
+Subject: Re: [bitcoin-dev] Full node "tip" function
+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
+X-Mailman-Version: 2.1.12
+Precedence: list
+List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
+List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
+List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
+List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
+List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
+List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
+X-List-Received-Date: Wed, 03 May 2017 23:21:31 -0000
+
+I think paying for services is in general a great idea, but one that Bitcoin
+can much better serve once Lightning is in production. Not only does it enable
+cost-effective micro-transactions, it also should allow nodes to initiate
+payments before they have a synced node (which is something impractical at
+present).
+
+On Wednesday 03 May 2017 9:08:35 PM Erik Aronesty via bitcoin-dev wrote:
+> IDEA:
+>
+> - Full nodes advertise a bitcoin address. Users that need to download the
+> block chain from that node can be encouraged to send a tip to the peers
+> that served them (by % served). Recommended tip of 10mbit should be fine.
+>
+> - A full nodes can *require* a tip to download the blockchain. If they do,
+> users that don't specify a tip cannot use them.
+>
+> CONS:
+>
+> For some people, this may represent a barrier to hosting their own full
+> node. After all, if you have to pay $15 just to get a copy of the
+> blockchain, that just adds to the already expensive prospect of hosting a
+> full node.
+>
+> PROS:
+>
+> As long as you manage to stay online, you should get your money back and
+> more. This is the an incentive for quality, long term hosting.
+>
+> In the long term, this should cause stable nodes to stick around longer.
+> It also discourages "installation spam" attacks on the network.
+>
+> Fees for other node operations can be considered if this is successful.
+