From: Peter Todd <pete@petertodd.org>
To: Pindar Wong <pindar.wong@gmail.com>
Cc: Constance Choi <constance.choi@gmail.com>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Primavera De Filippi <pdefilippi@gmail.com>,
bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork
Date: Fri, 26 Jun 2015 15:30:31 -0400 [thread overview]
Message-ID: <20150626193031.GA17829@muck> (raw)
In-Reply-To: <CAM7BtUqCZSGfgF7Xq4g7ZCrB-nrsur8B78myDd+NBsqZ0S_rZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On Thu, Jun 25, 2015 at 02:43:19PM +0800, Pindar Wong wrote:
> > Yup, though keep in mind the regulatory question is more than just how
> > your local jurisdiction views Bitcoin, but rather how your customers'
> > jurisdictions view Bitcoin.
> >
> > Of course, when I say "customers" above, I mean the entire Bitcoin
> > community that is ultimately buying the new coins produced by miners and
> > paying fees to them!
> >
>
> I'm sorry for the distraction with the mailing list problems.
>
> Taking an ecosystem view, the miners are important, so are all the other
> participants who rely on it and invest time, effort and energy to make
> Bitcoin work and work well.
Agreed.
IMO any change to the blocksize needs explicit mechanisms to let all
Bitcoin holders have a say in it.
> I am in contact with Primavera and it would appear that the Cyberport is
> available for use on October 14 and 15 (Wed/Thursday).
Great! Glad to hear.
> Last November, this was where the Global Bitcoin Summit (Hong Kong)
> <http://www.cyberport.hk/en/about_cyberport/our_5_centres/collaboration_centre/collaboration_news/2146>
> was hosted with the participation of many of China's leading
> Bitcoin-related companies. There is a meeting now in Shanghai.
>
> It would be an honour to host a more technical meeting to discuss BIP100,
> 101 et al. should be interest to do so.
Are you thinking this more technical meeting should be before or after
the October event? Perhaps a better question, is what exactly do you see
being discussed at a technical meeting?
--
'peter'[:-1]@petertodd.org
0000000000000000007fc13ce02072d9cb2a6d51fae41fefcde7b3b283803d24
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-26 19:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 0:04 [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Adam Back
2015-06-15 9:56 ` Mike Hearn
2015-06-15 18:03 ` Adam Back
2015-06-15 20:55 ` Mike Hearn
2015-06-15 21:56 ` Bryan Bishop
2015-06-15 22:17 ` Faiz Khan
2015-06-15 22:56 ` Brian Hoffman
2015-06-15 23:05 ` [Bitcoin-development] questions about bitcoin-XT code fork &non-consensus hard-fork Raystonn .
2015-06-16 0:08 ` [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Aaron Voisine
2015-06-16 0:41 ` Mark Friedenbach
2015-06-16 1:17 ` Alex Morcos
2015-06-16 4:00 ` Aaron Voisine
2015-06-17 3:54 ` Peter Todd
2015-06-18 15:23 ` Jorge Timón
2015-06-16 11:29 ` Mike Hearn
2015-06-16 11:20 ` Mike Hearn
2015-06-16 12:33 ` Pindar Wong
2015-06-16 13:33 ` Peter Todd
2015-06-16 13:55 ` Pindar Wong
2015-06-17 3:59 ` Peter Todd
2015-06-25 6:43 ` [bitcoin-dev] " Pindar Wong
2015-06-26 19:30 ` Peter Todd [this message]
2015-06-15 22:54 ` odinn
2015-06-16 1:20 ` Eric Lombrozo
2015-06-16 5:18 ` Venzen
2015-06-16 6:09 ` Marcel Jamin
2015-06-16 9:21 ` Benjamin
2015-06-16 11:01 ` Tier Nolan
2015-06-17 3:52 ` Troy Benjegerdes
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=20150626193031.GA17829@muck \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=constance.choi@gmail.com \
--cc=pdefilippi@gmail.com \
--cc=pindar.wong@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