On Sun, Dec 21, 2014 at 02:18:18PM +0800, Mark Friedenbach wrote:
> Care to expand?
>
> Freimarkets does not require proof of publication of bids or asks, which
> are distributed out of band from the block chain until a match is made. It
> does not guarantee ordering of market transactions. Indeed
On Wed, Dec 17, 2014 at 10:55:28PM +1100, Gareth Williams wrote:
> > I covered this in my original post: 1-way-pegs allow the creation of new
> > valuable tokens without those tokens being useful for speculation.
>
> I stand corrected. A permanent 1-way-peg is sufficient to preserve
> scarcity; "n
On Sun, Dec 21, 2014 at 11:57:51AM +0800, Mark Friedenbach wrote:
> On Sat, Dec 20, 2014 at 10:48 PM, Peter Todd wrote:
>
> > However the converse is not possible: anti-replay cannot be used to
> > implement proof-of-publication. Knowing that no conflicting message
> > exists says nothing about w
Thanks Jeff. I'll start looking there.
Will Bickford
"In Google We Trust"
On Sat, Dec 20, 2014 at 3:26 PM, Jeff Garzik wrote:
> Getting back to the original topic...
>
> I would recommend first taking a look at how the current tests are built
> (via autoconf/automake) in src/test. There are se
Getting back to the original topic...
I would recommend first taking a look at how the current tests are built
(via autoconf/automake) in src/test. There are several surfaces to test,
RPC, REST, P2P, internal unit tests, and more. Then, Travis applies a
second level of testing via the bitcoinj-b
On Sat, Dec 20, 2014 at 11:14 AM, Jeremy Spilman wrote:
>> are dnsseeds being blocked
> ostensibly because they are acting as dyanamic DNS infrastructure for
> malware sites?
Pretty much appears to be the case. In every instance it appears to be
automated. This predates the msft no-ip.com stuff.
Well, some ISPs, when they see an IP address serving malware, will
(apparently) simply replace DNS results for anything returning that IP
with a warning page.
One solutions is to just blindly block everything with HTTP(S), as
Christian has done, but this is a rather ugly solution, since many
perfe
Thanks for bringing this to my attention.
I added a safety check to my crawler and seed.bitcoinstats.com should
not return IPs that also run HTTP or HTTPS, hopefully this'll keep it
off blacklists :-)
--
Christian Decker
On Sat, Dec 20, 2014 at 9:57 AM, Matt Corallo wrote:
> There was recently
Gregory Maxwell recently pointed out to me in private conservation that
there potentially existed a fundemental disagreement between him and I
on our philosophical approaches to blockchains, in that he prioritised
the notion of the blockchain as an anti-replay oracle, and I prioritised
it as a publ
On Sat, Dec 20, 2014 at 08:57:53AM +, Matt Corallo wrote:
>> There was recently some discussion around dnsseeds. Currently some
>> dnsseeds are getting blocked by ISPs because the hosts they pick up
>> (which run bitcoin core nodes) often run rather web servers alongside
>> which serve malware
Why would we want to have anything to do with people who are hosting
malware? Or do I misunderstand?
On Sat, Dec 20, 2014 at 08:57:53AM +, Matt Corallo wrote:
> There was recently some discussion around dnsseeds. Currently some
> dnsseeds are getting blocked by ISPs because the hosts they pic
There was recently some discussion around dnsseeds. Currently some
dnsseeds are getting blocked by ISPs because the hosts they pick up
(which run bitcoin core nodes) often run rather web servers alongside
which serve malware or whatever else and thus end up on IP-based malware
blacklists.
Of cours
12 matches
Mail list logo