is to give
network the bytes type, but defining a UUID message type is also
possible. In either case bitcoin mainnet would be the default, so the
extra 12 bytes (vs: main or test) would only be an issue for
alt-chains or colored coins.
Kind regards,
Mark Friedenbach
If you're considering a datagram protocol, you might be interested in some
more modern alternatives to UDP:
UDT: Breaking the Data Transfer Bottleneck
http://udt.sourceforge.net/
Stream Control Transmission Protocol
http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol
On Sat, Mar
. Multiple UDT flows can share a single UDP
port, thus a firewall can open only one UDP port for all UDT connections.
The latter appears not so friendly to NAT.
On 3/23/2013 3:30 PM, Mark Friedenbach wrote:
If you're considering a datagram protocol, you might be interested in
some more
I'm not sure I understand the need for hard forks. We can get through this
crisis by mining pool collusion to prevent forking blocks until there is
widespread adoption of patched clients.
Proposal:
1) Patch the pre-0.8 branches to support an increased lock count, whatever
number is required to
and give them time to react, then move on. Let's
not codify the bug in the protocol.
Mark
On Wed, Mar 13, 2013 at 10:58 AM, Pieter Wuille pieter.wui...@gmail.comwrote:
On Wed, Mar 13, 2013 at 10:41:29AM -0700, Mark Friedenbach wrote:
4) At some point in the future once we've crossed an acceptable
or nRefHeight is what we call this
value internally, but blocktime or blockheight would work as well.
Github is currently down, so I apologize if a suitable field has already
been added.
Cheers,
Mark Friedenbach
[1] http://freico.in/ Freicoin: a P2P digital currency delivering freedom
from usury
Alan's UTxO meta-chain proposal becomes vastly easier to do now that
ultraprune is merged. That would allow the Satoshi client to know it's
wallet balance and operate with a =SPV level of security during the
initial block download, and keep them on the path of becoming a full node.
If users can
My only comment is that it should be called escheatment, not demurrage ;)
It's relation to demurrage is only that it might be desirable to garbage
collect decayed bit-dust. We looked at it early-on in the Freicoin
development, but rejected it as a possibility due to reasons others have
mentioned,
Running a concurrent Mantis tracker would be confusing and fragment the
development pathway. We have an issue tracker; it's on github.
What's being talked about here are two separate things. Jenkins is a
continuous integration system. It can be configured to run the suite of
unit tests,
the necessary dependencies installed.
I hope that others find this useful. I have submitted these scripts as
pull-request #1597 on github.
Cheers,
Mark Friedenbach
--
Live Security Virtual Conference
Exclusive live event
On Tue, Jun 19, 2012 at 10:33 AM, Alan Reiner etothe...@gmail.com wrote:
I hope that someone else here would chime in on the issue raised in the
thread, about using a tree-structure that has multiple valid
configurations for the same set of unspent-TxOuts. If you use any
binary tree, you
Sorry for the duplication Amir, I meant to send this to everyone:
BitTorrent might be an example to look to here. It's a peer-to-peer network
that has undergone many significant protocol upgrades over the years while
maintaining compatibility. More recent clients have had the ability to
expose
101 - 112 of 112 matches
Mail list logo
