This has been discussed before. I believe most people don't expect Bitcoin
to replace all of the various methods of payment. Scalability is always a
concern, just not to the level of Alipay this year (or the next or the
next for that matter.)
Nick
On Jan 30, 2015 7:08 PM, "Angel Leon" wrote:
>
Referring to the subsidy for miners as "wasting it on miners" isn't going to
garner you much favor.
On May 20, 2014 11:12:53 AM CDT, Stephen Reed wrote:
>I completed a whitepaper for Bitcoin a proof-of-stake version which
>uses a single nomadic verifiable mint agent and distributed replication
Luke's server has been having issues with ipv4 routing lately anyway, even
ignoring any DNS issues.
Nick
On May 16, 2014 12:17:17 PM CDT, Rob Golding wrote:
>> > dnsseed.bitcoin.dashjr.org SERVFAIL, tried multiple ISPs
>
>dnsseed.bitcoin.dashjr.org. 60 IN NS jun.dashjr.org.
>
You must be new here. MtGox very rarely comments on things like this publicly,
outside of irc or their website.
Second, MtGox problem is a MtGox problem. You have no right to demand access to
their private code. If you feel wronged as a customer, sue them. Otherwise,
they have no obligation to
Not any more than sourceforge or github.. None of these solutions are
replacements, but rather only supplements to self hosted files.
Jeff Garzik wrote:
>On Tue, Jul 9, 2013 at 11:32 AM, Nick Simpson
>wrote:
>> What about something like Cloudflare? Transparent to most and it&
What about something like Cloudflare? Transparent to most and it'd help with
your bandwidth issues.
Mike Hearn wrote:
>That's true - we could serve new users off our own servers and auto
>updates
>off SF.net mirrors, potentially.
>
>
>On Tue, Jul 9, 2013 at 4:57 PM, Daniel F wrote:
>
>> on 07/
6 matches
Mail list logo
