On Wed, 2011-11-23 at 15:39 +, Andy Parkins wrote:
> On 2011 November 23 Wednesday, Gavin Andresen wrote:
>
> > Bitcoin as-is doesn't have the "I got lucky and found an extremely
> > hard block" problem because the difficulty TARGET is used to compute
> > chain difficulty, not the actual hashe
On 2011 November 23 Wednesday, Gavin Andresen wrote:
> Bitcoin as-is doesn't have the "I got lucky and found an extremely
> hard block" problem because the difficulty TARGET is used to compute
> chain difficulty, not the actual hashes found.
Good points. I don't think I have a response to that o
But the protocol must have a deterministic way to determine if a block
must be accepted or rejected.
I don't know what NTP is, but if you can have a perfect distributed
clock your proposal may work.
2011/11/23, Andy Parkins :
> On 2011 November 23 Wednesday, Jorge Timón wrote:
>
>> Well, I meant "
I can substantiate Gavin's point quite powerfully: a couple months ago I
did a search for the "hardest" block in the network and found a *very
**impressive* one:
https://bitcointalk.org/index.php?topic=29675.0
That block has a difficulty of **36 billion** when the network had a
difficulty of
On 2011 November 23 Wednesday, Jorge Timón wrote:
> Well, I meant "the probability of your block being the hardest".
> What a miner can do is hash the block (cheating the timestamp) for 2
> more minutes than the rest of the people and then send it to the other
> nodes. Nodes cannot possibly know
On 2011 November 23 Wednesday, Christian Decker wrote:
> Just brainstorming here, no idea if this would work:
>
>- Pick any old block
>- Create a chain fork by creating simpler blocks on top of your chosen
>one
>- The chain will not be accepted by others
>- At some point you mi
2011/11/23, Andy Parkins :
> On 2011 November 23 Wednesday, Jorge Timón wrote:
>> With the current system, the timestamp can also be cheated, but miners
>> have no direct incentive to do it. With your system, they increase
>> their probability of mining a block by putting a false timestamp.
>> Also
On Wed, Nov 23, 2011 at 9:38 AM, Christian Decker
wrote:
> At some point you might find an incredibly hard block that makes your forked
> chain the hardest one in the network
Seems to me that's the real problem with any "hardest block found in X
minutes" scheme.
If I get lucky and find a really
Just brainstorming here, no idea if this would work:
- Pick any old block
- Create a chain fork by creating simpler blocks on top of your chosen
one
- The chain will not be accepted by others
- At some point you might find an incredibly hard block that makes your
forked chain the
On 2011 November 23 Wednesday, Christian Decker wrote:
> The current block generation with a fixed difficulty was chosen because it
> it clear when to adjust and to what target difficulty it has to be
> adjusted. If we were to use synchronized time windows and select the
> hardest block it gets in
On 2011 November 23 Wednesday, Jorge Timón wrote:
> With the current system, the timestamp can also be cheated, but miners
> have no direct incentive to do it. With your system, they increase
> their probability of mining a block by putting a false timestamp.
> Also, where's the network clock you'r
First of all I do agree that a method for adjusting the difficulty in a
huge power drop is needed (I don't see it so much in power rises).
The current block generation with a fixed difficulty was chosen because it
it clear when to adjust and to what target difficulty it has to be
adjusted. If we w
With the current system, the timestamp can also be cheated, but miners
have no direct incentive to do it. With your system, they increase
their probability of mining a block by putting a false timestamp.
Also, where's the network clock you're talking about? Isn't it the
timestamps in the blockchain
On 2011 November 23 Wednesday, Jorge Timón wrote:
> 2011/11/23, Andy Parkins :
> > Let's abandon the idea of a target difficulty. Instead, every node just
> >
> > generates the most difficulty block it can. Simultaneously, every node
> > is listening for "the most difficult block generated bef
2011/11/23, Andy Parkins :
> Let's abandon the idea of a target difficulty. Instead, every node just
> generates the most difficulty block it can. Simultaneously, every node is
> listening for "the most difficult block generated before time T"; with T
> being
> picked to be the block generati
Hello,
One problem with Bitcoin is that if large numbers of miners suddenly switch
off, the network takes a long time to adapt (since the adaption time is a
function of blocks generated, and the block generation rate has changed). The
same problem exists in the other direction, but an increase
16 matches
Mail list logo
