Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.182 as permitted sender)
	client-ip=209.85.216.182; envelope-from=gmaxwell@gmail.com;
	helo=mail-qy0-f182.google.com; 
MIME-Version: 1.0
In-Reply-To: <201108241215.36847.luke@dashjr.org>
References: <CABsx9T1uw43JuvhEmJP0KCyojsDi1r7v6BaLBHz7wWazduE5iw@mail.gmail.com>
	<201108241215.36847.luke@dashjr.org>
Date: Wed, 24 Aug 2011 12:46:42 -0400
Message-ID: <CAAS2fgQspsXy1Vw=fNr1FvsDRkEbP6dEcFLgUpK9DrBKXyiWNg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] New standard transaction types: time to
 schedule a blockchain split?
Precedence: list

On Wed, Aug 24, 2011 at 12:15 PM, Luke-Jr <luke@dashjr.org> wrote:

> - Replace hard limits (like 1 MB maximum block size) with something that =
can
> dynamically adapt with the times. Maybe based on difficulty so it can't b=
e
> gamed?

Too early for that.

> - Adjust difficulty every block, without limits, based on a N-block slidi=
ng
> =C2=A0window. I think this would solve the issue when the hashrate drops
> =C2=A0overnight, but maybe also add a block time limit, or perhaps includ=
e the
> =C2=A0"current block" in the difficulty calculation?

The quantized scheme limits the amount of difficulty skew miners can
create by lying about timestamps to about a half a percent. A rolling
window with the same time constant would allow much more skew.

> Replacing the "Satoshi" 64-bit integers with
> "Satoshi" variable-size fractions (ie, infinite numerator + denominator)

Increasing precision I would agree with but, sadly, causing people to
need more than 64 bit would create a lot of bugs.

infinite numerator + denominator is absolutely completely and totally
batshit insane. For one, it has weird consequences that the same value
can have redundant encodings.

Most importantly, it suffers factor inflation: If you spend inputs
1/977 1/983 1/991 1/997 the smallest denominator you can use for the
output 948892238557.

Not to mention that the idiots writing financial software can only
barely manage to not use radix-2 floating point on everything. Asking
them to use arbitrary rational numbers with mixed radix will never
fly.

> - Remove the 100 confirmation requirement for spending generated coins. I=
f
>  they are respent before 100 confirmations, clients can/should flag the n=
ew
>  outputs as also "generated" or "recently generated" so recipients are aw=
are
> of the risk.

Please lets not make bitcoin _less_ trustworthy.

The 100 block maturity on generated coins is good. The generation from
an orphaning is lost forever like the losing side of a double spend,
but far far worse... because orphaning happens all the time on its own
without any malice.

I agree it's obnoxious that you can't pad your generation payouts
without creating more transactions, but I don't see a solution for
that. Repeat the addresses... make up for it by increasing your payout
threshold.