Branch: refs/heads/master
  Home:   https://github.com/btcsuite/btcd
  Commit: 0280fa0264f907cc9a8113f40cec0327206e0196
      
https://github.com/btcsuite/btcd/commit/0280fa0264f907cc9a8113f40cec0327206e0196
  Author: Dave Collins <[email protected]>
  Date:   2015-08-11 (Tue, 11 Aug 2015)

  Changed paths:
    M blockchain/accept.go
    M blockchain/blocklocator.go
    M blockchain/chain.go
    M blockchain/checkpoints.go
    M blockchain/common_test.go
    M blockchain/difficulty.go
    M blockchain/internal_test.go
    M blockchain/txlookup.go
    M blockchain/validate.go
    M blockchain/validate_test.go
    M blockmanager.go
    M chaincfg/params.go
    M chainindexer.go
    M cmd/dropafter/dropafter.go
    M cmd/findcheckpoint/findcheckpoint.go
    M cpuminer.go
    M database/db.go
    M database/interface_test.go
    M database/ldb/block.go
    M database/ldb/dup_test.go
    M database/ldb/insertremove_test.go
    M database/ldb/leveldb.go
    M database/ldb/operational_test.go
    M database/ldb/tx.go
    M database/memdb/memdb.go
    M database/reorg_test.go
    M mempool.go
    M mining.go
    M peer.go
    M rpcserver.go
    M rpcwebsocket.go

  Log Message:
  -----------
  Convert block heights to int32.

This commit converts all block height references to int32 instead of
int64.  The current target block production rate is 10 mins per block
which means it will take roughly 40,800 years to reach the maximum
height an int32 affords.  Even if the target rate were lowered to one
block per minute, it would still take roughly another 4,080 years to
reach the maximum.

In the mean time, there is no reason to use a larger type which results
in higher memory and disk space usage.  However, for now, in order to
avoid having to reserialize a bunch of database information, the heights
are still serialized to the database as 8-byte uint64s.

This is being mainly being done in preparation for further upcoming
infrastructure changes which will use the smaller and more efficient
4-byte serialization in the database as well.


Reply via email to