From: Brooks Boyd <boydb@midnightdesign•ws>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments
Date: Thu, 6 Mar 2014 12:20:24 -0600 [thread overview]
Message-ID: <CANg-TZCAriYNbcA90YxKy6fRaioJ=0E18EcxAm0A6DssWkRrnw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3pD2c-UFUZZAJAXBFTynx5Vusdw7As6O3RYuix3mMXDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Thu, Mar 6, 2014 at 12:12 PM, Mike Hearn <mike@plan99•net> wrote:
> If there was a way for a Bitcoin user to provide feedback on a payment
>> (ECDSA signature from one of the addresses involved in the payment, signing
>> an identifier of the payment and a feedback score)
>>
>
> Well now you're getting into the area that I said "rapidly got very
> complicated".
>
> Define bitcoin user? What stops me paying myself to accrue positive
> reputation? Etc.
>
Yes, I could see how that could get hairy; it would also need some ability
to rate those giving the feedback, such that if you generate a whole bunch
of payments to yourself, those payees don't have reputation on their own,
so their review of you as a payer isn't weighted that highly. Then you have
that ring-of-trust possibility where Alice thinks Eve is bad, so the fact
that Eve thinks Bob is good doesn't impact Alice. But if Carol thinks Eve
is good, Carol thinks Bob is good too, so Bob's reputation is different
based on who's asking, and it's the responsibility of the individual
members to maintain their own good/bad user lists. Would you think that's a
good thing or a bad thing to give the individual players that level of
control/responsibility?
[-- Attachment #2: Type: text/html, Size: 1934 bytes --]
next prev parent reply other threads:[~2014-03-06 18:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:45 Mike Hearn
2014-03-06 11:26 ` Andreas Schildbach
2014-03-06 13:44 ` Mike Hearn
2014-03-06 14:51 ` Andreas Schildbach
2014-03-06 16:55 ` [Bitcoin-development] Instant / contactless payments, IsoDep Andreas Schildbach
2014-03-06 17:00 ` Mike Hearn
2014-03-07 8:45 ` Andreas Schildbach
2014-03-07 9:26 ` [Bitcoin-development] Instant / contactless payments Johannes Zweng
2014-03-07 10:00 ` Mike Hearn
2014-03-07 10:23 ` Andreas Schildbach
2014-03-07 11:01 ` Mike Hearn
2014-03-07 12:00 ` Johannes Zweng
2014-03-06 14:20 ` Brooks Boyd
2014-03-06 17:07 ` Mike Hearn
2014-03-06 18:08 ` Brooks Boyd
2014-03-06 18:12 ` Mike Hearn
2014-03-06 18:20 ` Brooks Boyd [this message]
2014-03-06 18:24 ` Mike Hearn
2014-03-07 18:07 ` Joel Kaartinen
2014-03-06 14:39 ` Alex Kotenko
2014-03-06 16:46 ` Andreas Schildbach
2014-03-06 16:52 ` Mike Hearn
2014-03-06 18:03 ` Alex Kotenko
2014-03-07 8:59 ` Andreas Schildbach
2014-03-06 17:03 ` Mike Hearn
2014-03-06 18:49 ` Alex Kotenko
2014-03-08 8:52 ` Jan Vornberger
2014-03-10 15:09 ` Alex Kotenko
2014-03-10 19:28 ` Andreas Schildbach
2014-03-10 19:47 ` Alex Kotenko
2014-03-07 19:08 ` Troy Benjegerdes
2014-03-10 16:04 ` Mike Hearn
2014-03-10 16:14 ` Jean-Paul Kogelman
2014-03-10 16:27 ` Alex Kotenko
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='CANg-TZCAriYNbcA90YxKy6fRaioJ=0E18EcxAm0A6DssWkRrnw@mail.gmail.com' \
--to=boydb@midnightdesign$(echo .)ws \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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