Please use ASCII quotes in the Title. It is also too long (max size 44
characters).
Add missing headers:
Layer: Consensus (hard fork)
Comments-Summary: No comments yet.
Comments-URI: TBD
Status: Draft
Type: Standards Track
License: PD
It must be made at least technically sound. The B
On Wed, Dec 14, 2016 at 3:45 PM, Johnson Lau wrote:
> I think that’s too much tech debt just for softforkability.
>
> The better way would be making the sum tree as an independent tree with a
> separate commitment, and define a special type of softfork (e.g. a special
> BIP9 bit).
>
One of the p
I think that’s too much tech debt just for softforkability.
The better way would be making the sum tree as an independent tree with a
separate commitment, and define a special type of softfork (e.g. a special BIP9
bit). When the softfork is activated, the legacy full node will stop validating
t
On Wed, Dec 14, 2016 at 10:55 AM, Johnson Lau wrote:
> In a sum tree, however, since the nSigOp is implied, any redefinition
> requires either a hardfork or a new sum tree (and the original sum tree
> becomes a placebo for old nodes. So every softfork of this type creates a
> new tree)
>
That's
> On 14 Dec 2016, at 19:07, Luke Dashjr wrote:
>
> On Wednesday, December 14, 2016 11:01:58 AM Johnson Lau via bitcoin-dev wrote:
>> There is no reason to use a timestamp beyond 4 bytes.
>
> Actually, there is: lock times... my overflow solution doesn't have a
> solution
> to that. :x
You c
> On 5 Dec 2016, at 04:00, adiabat wrote:
>
> Interesting stuff! I have some comments, mostly about the header.
>
> The header of forcenet is mostly described in Luke’s BIP, but I have made
> some amendments as I implemented it. The format is (size in parentheses;
> little endian):
>
> Heigh
On Wednesday, December 14, 2016 11:01:58 AM Johnson Lau via bitcoin-dev wrote:
> There is no reason to use a timestamp beyond 4 bytes.
Actually, there is: lock times... my overflow solution doesn't have a solution
to that. :x
___
bitcoin-dev mailing lis
There is no reason to use a timestamp beyond 4 bytes. Just let it overflow. If
a blockchain is stopped for more than 2^31 seconds, it’s just dead.
> On 5 Dec 2016, at 19:58, Tom Zander via bitcoin-dev
> wrote:
>
> On Sunday, 4 December 2016 21:37:39 CET Hampus Sjöberg via bitcoin-dev
> wrote:
I think the biggest problem of sum tree is the lack of flexibility to redefine
the values with softforks. For example, in the future we may want to define a
new CHECKSIG with witness script version 1. That would be counted as a SigOp.
Without a sum tree design, that’d be easy as we could just de
Hi Ben,
not sure if this is the right mailing list for that. I think it rather
belongs to bitcoin-discuss.
And I am also not sure if I understand your question. What you may
mean is the private key of a user. If you find this, you can spend his
funds and also prove that you own the funds.
Depend
10 matches
Mail list logo
