public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Justus Ranvier <justusranvier@gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>,
	 Justus Ranvier <justusranvier@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Incentivizing the running of full nodes
Date: Mon, 16 Jun 2014 14:00:17 -0500 (CDT)	[thread overview]
Message-ID: <422d16e8.kqhkiG.146a60d2382@gmail.com> (raw)
In-Reply-To: <1866054.ECx185lXld@crushinator>

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

There can be multiple independent transport networks for Bitcoin.

There already is: ipv4, ipv6, Tor, and native_i2p (out of tree patch).

As long as multihomed hosts that act as bridges then information will propagate across all of them.
--
Justus Ranvier
-----------------
sent with R2Mail2

----- Original Message -----
From: Matt Whitlock <bip@mattwhitlock.name>
Sent: 2014/06/16 - 13:10
To: Mike Hearn <mike@plan99.net>, Justus Ranvier <justusranvier@gmail.com>
Subject: Re: [Bitcoin-development] Incentivizing the running of full nodes

> On Monday, 16 June 2014, at 7:59 pm, Mike Hearn wrote:
>> >
>> > This is a cool idea, but doesn't it generate some perverse incentives? If
>> > I'm running a full node and I want to pay CheapAir for some plane tickets,
>> > I'll want to pay in the greatest number of individual transactions possible
>>
>> Peers can calculate rewards based on number of inputs or total kb used:
>> you're paying for kilobytes with either coin age or fees no matter what. So
>> I think in practice it's not a big deal.
>
> So effectively, if you pay for your bandwidth/storage usage via fees, then the reward system is constrained by proof of burn, and if you pay for your usage via coin age, then the reward system is constrained by proof of stake.
>
> Now another concern: won't this proposal increase the likelihood of a network split? The free-market capitalist nodes will want to charge their peers and will kick and ban peers that don't pay up (and will pay their peers to avoid being kicked and banned themselves), whereas the socialist nodes will want all of their peers to feed them transactions out of the goodness of their hearts and will thus necessarily be relegated to connecting only to other altrustic peers. Thus, the network will comprise two incompatible ideological camps, whose nodes won't interconnect.



[-- Attachment #2: PGP/MIME digital signature --]
[-- Type: application/pgp-signature, Size: 532 bytes --]

  reply	other threads:[~2014-06-16 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16  8:12 [Bitcoin-development] Incentivizing the running of full nodes Odinn Cyberguerrilla
2014-06-16 11:35 ` Mike Hearn
2014-06-16 16:25 ` Matt Whitlock
2014-06-16 17:07   ` Justus Ranvier
2014-06-16 17:26     ` Matt Whitlock
2014-06-16 17:59       ` Mike Hearn
2014-06-16 18:10         ` Matt Whitlock
2014-06-16 19:00           ` Justus Ranvier [this message]
2014-06-16 20:55             ` Justus Ranvier
2014-06-17 17:47               ` Odinn Cyberguerrilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422d16e8.kqhkiG.146a60d2382@gmail.com \
    --to=justusranvier@gmail.com \
    --cc=bip@mattwhitlock.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox