public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: Chaofan Li <li3939108@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Blockchain Voluntary Fork (Split) Proposal (Chaofan Li)
Date: Tue, 30 Jan 2018 00:32:58 -0500	[thread overview]
Message-ID: <TPisDO8RJhPB6N8hdXNKMdJvWTw3nLycrGPRXPN32Fj9FqqMJ9mEgtiHmqYX5vK9kvCYFtwNkrMGqB2QcuK16CL6Tz8Xb1DcyaNmsJIOSF0=@protonmail.com> (raw)
In-Reply-To: <CANZDnNo29+9jezspt8sRaq8WpUjLghkQ0Ubvxb6=_2nuOs-frw@mail.gmail.com>

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

Good Morning Chaofan Li,

> The human perception of difference will be eliminated.
> Will your bank tell you whether your balance means coins or paper money?
> If wallets and exchanges only show the total amount of btc rather than btc.0 and btc.1, there is no human perception difference.

This returns my initial question.

What ensures that a paper money with "10 Dollar" on it, is same as 10 coins each with "1 Dollar" on it?

This is the principle of fungibility, and means I can exchange a paper with "10 Dollar" on it for 10 coins with "1 Dollar" on it, because by government fiat, such an exchange is valid for all cases.

What ensures that btc.0 and btc.1 are indistinguishable from a human perception?

> Also note that one valid address is automatically valid on the other chain, which means you can send money through any one chain. As long as one has the private key, he/she can get the money anyway. So there is no difference between number of merchants. The merchant ‘s address is valid on both chains.
>
> The exchange cost would be trivial. People don’t need to exchange two same thing.

You are talking about sidechains.  In every sidechain proposal, there is always some mechanism (SPV proof-of-work, drivechain proof-of-voting, proof-of-mainstake...) that ensures that a sidechain coin is exchangeable for a mainchain coin, and from there, that every sidechain coin is exchangeable for every other sidechain coin.  I.e. that a smart contract with "1 BTC" on it is exchangeable for a mainchain UTXO of value "1 BTC".

A mere split is not enough.  As I brought up, what makes your proposal different from 2X, BCash, etc.?

Regards,
ZmnSCPxj

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]

  reply	other threads:[~2018-01-30  5:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  0:38 [bitcoin-dev] Blockchain Voluntary Fork (Split) Proposal (Chaofan Li) Chaofan Li
2018-01-23  4:57 ` Eric Voskuil
2018-01-23  5:47   ` Chaofan Li
2018-01-30  5:32     ` ZmnSCPxj [this message]
2018-01-30  6:20       ` Chaofan Li
     [not found] <CALTsm7iyJjQa5rkddZj2jL_BTdGxH+6Xz78Rt0wOqW1OveecHw@mail.gmail.com>
     [not found] ` <CALTsm7gQC8RejAhmobzejEoU4T7xLf77Ykk2m0p=Z2=oM2p0Uw@mail.gmail.com>
2018-01-22 19:01   ` Ilan Oh
2018-01-22 19:59     ` Mark Friedenbach
2018-01-22 22:52       ` Eric Voskuil

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='TPisDO8RJhPB6N8hdXNKMdJvWTw3nLycrGPRXPN32Fj9FqqMJ9mEgtiHmqYX5vK9kvCYFtwNkrMGqB2QcuK16CL6Tz8Xb1DcyaNmsJIOSF0=@protonmail.com' \
    --to=zmnscpxj@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=li3939108@gmail.com \
    /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