From: "Jorge Timón" <jtimon@jtimon.cc>
To: Natanael <natanael.l@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For Comments
Date: Sun, 2 Apr 2017 13:43:54 +0200 [thread overview]
Message-ID: <CABm2gDpHKpU_nF_-7V59YhwqGnUc=2pXQNU9dDUq7wOvd7Uyyw@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M1_Ac4or_awrGTuYGEwLsJLP+_LBCsu2SubaJGr-f0BkoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
Just saying that we can talk in terms of weight alone after segwit. 8 mb
weight is much more clear than 2 mb size to me. 2 mb size seems to
obfuscate the actual new limit with the proposed hf, which simply 8 mb
weight.
On 2 Apr 2017 12:03 pm, "Natanael" <natanael.l@gmail.com> wrote:
> My point, if you missed it, is that there's a mathematical equivalence
> between using two limits (and calculating the ratio) vs using one limit and
> a ratio. The output is fully identical. The only difference is the order of
> operations. Saying there's no blocksize limit with this is pretty
> meaningless, because you're just saying you're using an abstraction that
> doesn't make the limit visible.
>
[-- Attachment #2: Type: text/html, Size: 1007 bytes --]
next prev parent reply other threads:[~2017-04-02 11:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 21:09 [bitcoin-dev] Segwit2Mb - combined soft/hard fork - Request For Comments Sergio Demian Lerner
2017-03-31 21:18 ` Matt Corallo
2017-03-31 21:22 ` praxeology_guy
2017-03-31 21:50 ` Sergio Demian Lerner
2017-03-31 21:22 ` Matt Corallo
2017-03-31 22:13 ` Sergio Demian Lerner
2017-04-01 3:03 ` Samson Mow
2017-04-01 3:35 ` Sergio Demian Lerner
2017-06-02 20:04 ` Erik Aronesty
2017-04-01 6:55 ` Jared Lee Richardson
2017-04-01 11:44 ` Sergio Demian Lerner
2017-04-01 12:33 ` Jorge Timón
2017-04-01 13:15 ` Natanael
2017-04-01 14:07 ` Jorge Timón
[not found] ` <CAAt2M1_gDzEuDLSvVsJARvdCAtUyM3Yuu7TT25sbm3L-Zi6+0Q@mail.gmail.com>
[not found] ` <CAAt2M18=Tjw+05QCv6G7Abv=idB6ONgU9xvtrR=fn731452_mg@mail.gmail.com>
2017-04-01 15:34 ` Natanael
2017-04-02 4:57 ` Jorge Timón
2017-04-02 10:03 ` Natanael
2017-04-02 11:43 ` Jorge Timón [this message]
2017-06-02 20:04 ` Erik Aronesty
2017-06-02 21:51 ` Sergio Demian Lerner
2017-06-03 0:53 ` Erik Aronesty
2017-06-03 2:03 ` Oliver Petruzel
2017-06-03 21:05 ` Oliver Petruzel
2017-04-03 14:40 ` Btc Drak
2017-04-06 2:27 ` Erik Aronesty
2017-04-06 20:58 ` Sergio Demian Lerner
2017-04-06 20:42 ` Sergio Demian Lerner
2017-04-06 21:03 ` Sergio Demian Lerner
2017-04-06 22:29 ` Aymeric Vitte
2017-06-02 12:29 ` R E Broadley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABm2gDpHKpU_nF_-7V59YhwqGnUc=2pXQNU9dDUq7wOvd7Uyyw@mail.gmail.com' \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=natanael.l@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox