-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/2014 10:31 PM, Thomas Voegtlin wrote:
You are right. The 256-way branching follows from the fact that the
tree was implemented using a key-value database operating with byte
strings (leveldb). With this implementation constraint, a
On Sun, Jan 05, 2014 at 07:43:58PM +0100, Thomas Voegtlin wrote:
Hello and happy new year to this mailing list!
Thank you Mark for the incredible work you've been doing on this.
I am following this very closely, because it is of primary importance
for Electrum.
I have written a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/2014 10:13 AM, Peter Todd wrote:
On Sun, Jan 05, 2014 at 07:43:58PM +0100, Thomas Voegtlin wrote:
I have written a Python-levelDB implementation of this UTXO
hashtree, which is currently being tested, and will be added to
Electrum
Le 07/01/2014 01:21, Mark Friedenbach a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/2014 10:13 AM, Peter Todd wrote:
On Sun, Jan 05, 2014 at 07:43:58PM +0100, Thomas Voegtlin wrote:
I have written a Python-levelDB implementation of this UTXO
hashtree, which is currently
Hello and happy new year to this mailing list!
Thank you Mark for the incredible work you've been doing on this.
I am following this very closely, because it is of primary importance
for Electrum.
I have written a Python-levelDB implementation of this UTXO hashtree,
which is currently being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jeremy, Let's give a preview of the application-oriented BIPs I
mentioned:
Stateless validation and mining involves prefixing transaction and
block messages with proofs of their UTxO state changes. These are the
operational proofs I describe in
On Fri, Dec 20, 2013 at 03:10:50AM -0800, Mark Friedenbach wrote:
On 12/20/2013 02:48 AM, Peter Todd wrote:
On Thu, Dec 19, 2013 at 05:47:52PM -0800, Mark Friedenbach wrote:
This BIP describes the authenticated prefix tree and its many
variations in terms of its serialized representation.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sorry Peter, this was meant for the whole list:)
On 12/20/2013 05:17 AM, Peter Todd wrote:
I've thought about this for awhile and come to the conclusion that
UTXO commitments are a really bad idea. I myself wanted to see them
implemented about a
On Thu, Dec 19, 2013 at 5:47 PM, Mark Friedenbach m...@monetize.io wrote:
Hello fellow bitcoin developers. Included below is the first draft of
a BIP for a new Merkle-compressed data structure. The need for this
data structure arose out of the misnamed Ultimate blockchain
compression project,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2013 11:48 AM, Gregory Maxwell wrote:
A couple very early comments— I shared some of these with you on
IRC but I thought I'd post them to make them more likely to not get
lost.
I got the inputs from IRC, but thank you for posting to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello fellow bitcoin developers. Included below is the first draft of
a BIP for a new Merkle-compressed data structure. The need for this
data structure arose out of the misnamed Ultimate blockchain
compression project, but it has since been
11 matches
Mail list logo
