From: Levin Keller <post@levinkeller.de>
To: Upal Chakraborty <bitcoin@upalc.com>,
bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap
Date: Mon, 17 Aug 2015 09:54:00 +0000 [thread overview]
Message-ID: <CAG86ZOxeBMAHPJYD0aN05WaJZwc8+2HhnpS0UnZUxnD9PNzOKA@mail.gmail.com> (raw)
In-Reply-To: <CAED3CWjfWAC-6=5P8OWx-1eP6Dq52K=c1L5B7h6fjGb71e-STw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Interesting. I am writing down something similar. Will share soon.
Upal Chakraborty via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
schrieb am Mo., 17. Aug. 2015 um 11:45 Uhr:
> I have tried to solve the maximum block size debate, depending on the
> previous block size calculation.
>
> Requesting for comment - http://upalc.com/maxblocksize.php
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1296 bytes --]
next prev parent reply other threads:[~2015-08-17 9:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 9:44 [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap Upal Chakraborty
2015-08-17 9:54 ` Levin Keller [this message]
2015-08-17 9:59 ` Patrick Strateman
2015-08-17 10:51 ` Btc Drak
2015-08-17 11:57 Rodney Morris
2015-08-17 12:38 ` Angel Leon
2015-08-17 12:43 ` Tier Nolan
2015-08-18 12:13 Upal Chakraborty
2015-08-18 17:26 ` Chris Wardell
2015-08-20 7:31 ` Jorge Timón
2015-08-20 10:23 ` Milly Bitcoin
2015-08-21 0:25 ` Tom Harding
2015-08-21 0:37 ` Peter Todd
2015-08-21 16:52 ` Tom Harding
2015-08-21 22:21 ` Peter Todd
2015-08-21 23:16 ` Tom Harding
2015-08-22 0:01 ` Peter Todd
2015-08-22 3:21 ` Jorge Timón
2015-08-22 6:26 ` Peter Todd
2015-08-23 23:41 ` Tom Harding
2015-08-24 2:27 ` Jorge Timón
2015-08-21 0:45 ` Milly Bitcoin
2015-08-21 0:58 ` Peter Todd
2015-08-21 1:30 ` Milly Bitcoin
2015-08-21 20:28 ` Jorge Timón
2015-08-21 12:13 ` Sriram Karra
2015-08-21 20:09 ` Jorge Timón
2015-08-18 19:44 ` cedric perronnet
2015-08-18 20:58 ` Danny Thorpe
2015-08-18 21:17 ` Chris Wardell
2015-08-19 17:21 ` Upal Chakraborty
2015-08-20 15:02 Upal Chakraborty
2015-08-21 21:45 Upal Chakraborty
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=CAG86ZOxeBMAHPJYD0aN05WaJZwc8+2HhnpS0UnZUxnD9PNzOKA@mail.gmail.com \
--to=post@levinkeller.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin@upalc.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