From: Tony Churyumoff <tony991@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Fwd: Hiding entire content of on-chain transactions
Date: Wed, 10 Aug 2016 10:50:25 +0300 [thread overview]
Message-ID: <CAL3p6zoMK=3Rv5VmR5auOt3CpnLaFQ-N2Gz4NBCBLqgmQr+mOA@mail.gmail.com> (raw)
In-Reply-To: <CAL3p6zpvv7ph9CJQF6E1VVdwCKKFLNe2EVh=JE=R0Gpt4y=1Tw@mail.gmail.com>
> The OP's proposal sounds quite similar to my earlier one along similar lines:
>
> https://petertodd.org/2016/closed-seal-sets-and-truth-lists-for-privacy
Similar indeed, thank you for the link.
2016-08-09 0:53 GMT+03:00 Peter Todd <pete@petertodd•org>:
>
> On Mon, Aug 08, 2016 at 09:41:27PM +0000, James MacWhyte via bitcoin-dev wrote:
> > Wouldn't you lose the ability to assume transactions in the blockchain are
> > verified as valid, since miners can't see the details of what is being
> > spent and how? I feel like this ability is bitcoin's greatest asset, and by
> > removing it you're creating an altcoin different enough to not be connected
> > to/supported by the main bitcoin project.
>
> The fact that miners verify transactions is just an optimisation:
>
> https://petertodd.org/2013/disentangling-crypto-coin-mining
>
> Preventing double-spending however is a fundemental requirement of Bitcoin, and
> this proposal does prevent double-spending perfectly well (although there may
> be better ways to do it).
>
> The OP's proposal sounds quite similar to my earlier one along similar lines:
>
> https://petertodd.org/2016/closed-seal-sets-and-truth-lists-for-privacy
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
next prev parent reply other threads:[~2016-08-10 7:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 15:30 [bitcoin-dev] " Tony Churyumoff
2016-08-08 15:47 ` Henning Kopp
2016-08-08 16:03 ` Tony Churyumoff
2016-08-08 21:41 ` James MacWhyte
2016-08-08 21:53 ` Peter Todd
[not found] ` <CAL3p6zpvv7ph9CJQF6E1VVdwCKKFLNe2EVh=JE=R0Gpt4y=1Tw@mail.gmail.com>
2016-08-10 7:50 ` Tony Churyumoff [this message]
2016-08-08 23:42 ` Tony Churyumoff
2016-08-09 0:03 ` James MacWhyte
[not found] ` <CAL3p6zr76k1F07dtvxQ8hiOiK_ZvVFBmW=ESYem60udUQmM+Cw@mail.gmail.com>
2016-08-10 7:51 ` [bitcoin-dev] Fwd: " Tony Churyumoff
2016-08-09 0:18 ` [bitcoin-dev] " James MacWhyte
[not found] ` <CAL3p6zqdKgkFWSDZYqVERvX2iGyS3qaLZae-kDp3Y-s1rmB2Zg@mail.gmail.com>
2016-08-10 4:31 ` James MacWhyte
2016-08-10 8:37 ` Tony Churyumoff
2016-08-10 7:53 ` [bitcoin-dev] Fwd: " Tony Churyumoff
2016-08-09 7:26 ` [bitcoin-dev] " Henning Kopp
[not found] ` <CAL3p6zqj7bc=qrayBBK=O6p2b2PBNO3n5EMFf_1dR1oMq581hg@mail.gmail.com>
2016-08-10 7:52 ` [bitcoin-dev] Fwd: " Tony Churyumoff
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='CAL3p6zoMK=3Rv5VmR5auOt3CpnLaFQ-N2Gz4NBCBLqgmQr+mOA@mail.gmail.com' \
--to=tony991@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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