From: Kevin Greene <kgreenek@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] The Bitcoin Node Market
Date: Mon, 15 Jun 2015 20:49:43 -0700 [thread overview]
Message-ID: <CAEY8wq4SOddGUJNqkrdhhfQEn4tXehCWiifk-P=PYUdfFcXFTQ@mail.gmail.com> (raw)
In-Reply-To: <201506160341.10994.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On Mon, Jun 15, 2015 at 8:41 PM, Luke Dashjr <luke@dashjr•org> wrote:
> On Tuesday, June 16, 2015 3:30:44 AM Kevin Greene wrote:
> > Would SPV wallets have to pay to connect to the network too? From the
> > user's perspective, it would be somewhat upsetting (and confusing) to see
> > your balance slowly draining every time you open your wallet app. It
> would
> > also tie up outputs every time you open up your wallet. You may go to pay
> > for something in a coffee shop, only to find that you can't spend your
> > bitcoin because the wallet had to create a transaction to pay to sync
> with
> > the network.
> >
> > Also, users of centralized wallet services like Coinbase would not have
> to
> > pay that fee; but users of native wallets like breadwallet would have no
> > such option. This incentivizes users to use centralized wallets.
> >
> > So this is kind of imposing a worse user experience on users who want to
> > use bitcoin the "right" way. That doesn't seem like a good thing to me :/
>
> SPV isn't the "right" way either ;)
>
Hah, fair enough, there is no such thing as the "right" way to do
anything. But I still think punishing users who use SPV wallets is a
less-than-ideal way to incentive people to run full nodes. Right now SPV is
the best way that exists for mobile phones to participate in the network in
a decentralized way. This proposal makes the user experience for mobile
wallets a little more confusing and annoying.
>
> If you're running a full node (the real "right way"), you should be able to
> earn more bitcoins than you pay out.
>
> Luke
>
[-- Attachment #2: Type: text/html, Size: 2394 bytes --]
next prev parent reply other threads:[~2015-06-16 3:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 21:23 [Bitcoin-development] comments on BIP 100 Adam Back
2015-06-14 22:23 ` Mike Hearn
2015-06-14 23:58 ` Adam Back
2015-06-15 0:53 ` Eric Lombrozo
2015-06-15 0:55 ` Eric Lombrozo
2015-06-15 4:11 ` Peter Todd
2015-06-15 4:43 ` Eric Lombrozo
2015-06-15 9:27 ` Mike Hearn
2015-06-15 9:39 ` Eric Lombrozo
2015-06-15 10:24 ` Pieter Wuille
2015-06-15 10:36 ` Mike Hearn
2015-06-15 10:40 ` Pieter Wuille
2015-06-15 10:50 ` Mike Hearn
2015-06-15 11:16 ` Rebroad (sourceforge)
2015-06-15 17:53 ` Raystonn .
2015-06-15 18:14 ` Adam Back
2015-06-15 18:57 ` [Bitcoin-development] The Bitcoin Node Market Raystonn .
2015-06-15 19:18 ` sickpig
2015-06-15 19:36 ` Raystonn .
2015-06-15 20:12 ` sickpig
2015-06-16 3:30 ` Kevin Greene
2015-06-16 3:41 ` Luke Dashjr
2015-06-16 3:49 ` Kevin Greene [this message]
2015-06-16 4:05 ` Kevin Greene
2015-06-16 4:12 ` Aaron Voisine
2015-06-16 5:28 ` justusranvier
2015-06-16 5:30 ` Potter QQ
2015-06-16 7:55 ` Aaron Voisine
2015-06-16 13:32 ` justusranvier
2015-06-16 17:04 ` Aaron Voisine
2015-06-16 17:22 ` Aaron Voisine
2015-06-16 15:52 ` devrandom
2015-06-15 4:43 ` [Bitcoin-development] comments on BIP 100 Peter Todd
2015-06-15 9:06 ` Mike Hearn
2015-06-15 2:28 ` Jeff Garzik
2015-06-15 2:44 ` Jeff Garzik
2015-06-16 4:38 [Bitcoin-development] The Bitcoin Node Market Raystonn
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='CAEY8wq4SOddGUJNqkrdhhfQEn4tXehCWiifk-P=PYUdfFcXFTQ@mail.gmail.com' \
--to=kgreenek@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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