Branch: refs/heads/master
  Home:   https://github.com/btcsuite/btcd
  Commit: 191420008079ba0b405f987c9e70e843715f59b6
      
https://github.com/btcsuite/btcd/commit/191420008079ba0b405f987c9e70e843715f59b6
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M blockchain/accept.go
    M blockchain/chain.go
    M blockchain/validate.go
    M wire/msgtx.go

  Log Message:
  -----------
  blockchain: introduce SequenceLocks for relative lock-time calcs

This commit introduces the concept of “sequence locks” borrowed from
Bitcoin Core for converting an input’s relative time-locks to an
absolute value based on a particular block for input maturity
evaluation.

A sequence lock is computed as the most distant maturity height/time
amongst all the referenced outputs within a particular transaction.

A transaction with sequence locks activated within any of its inputs
can *only* be included within a block if from the point-of-view of that
block either the time-based or height-based maturity for all referenced
inputs has been met.

A transaction with sequence locks can only be accepted to the mempool
iff from the point-of-view of the *next* (yet to be found block) all
referenced inputs within the transaction are mature.


  Commit: de709f28f6132e7df5514de5981f8c0a976d113f
      
https://github.com/btcsuite/btcd/commit/de709f28f6132e7df5514de5981f8c0a976d113f
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M blockchain/chain.go

  Log Message:
  -----------
  blockchain: add new LockTimeToSequence function

This commit adds a new function to the package: `LockTimeToSequence`.
The function is a simple utility function which aides the caller to
mapping a targeted time or block based relative lock-time to the
appropriate sequence number.


  Commit: e855c0dd82dc5e036393fa81e43227f3fef1bed2
      
https://github.com/btcsuite/btcd/commit/e855c0dd82dc5e036393fa81e43227f3fef1bed2
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M blockchain/chain_test.go

  Log Message:
  -----------
  blockchain: add table driven unit tests for CalcSequenceLock


  Commit: ecdaf9726ca2fa7d4c387e001292d04023897078
      
https://github.com/btcsuite/btcd/commit/ecdaf9726ca2fa7d4c387e001292d04023897078
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M blockchain/validate_test.go

  Log Message:
  -----------
  blockchain: add basic tests for SequenceLockActive


  Commit: 7eb0ab5f8d2b097a75f4de60e016ab4504f1749c
      
https://github.com/btcsuite/btcd/commit/7eb0ab5f8d2b097a75f4de60e016ab4504f1749c
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M mempool/mempool.go
    M mempool/mempool_test.go
    M server.go

  Log Message:
  -----------
  mempool: add function to config for computing sequence locks


  Commit: 6cd895549889c2de7fba7e88e05cd180024228a0
      
https://github.com/btcsuite/btcd/commit/6cd895549889c2de7fba7e88e05cd180024228a0
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M mempool/mempool.go
    M mining.go

  Log Message:
  -----------
  mempool: enforce relative lock-time semantics

This commit introduces behavior which enforces sequence num based
relative lock-time semantics when accepting transaction to the mempool.


  Commit: e3eeb4a34a04c8ec40298fee9f9d8fe2ce0c13ca
      
https://github.com/btcsuite/btcd/commit/e3eeb4a34a04c8ec40298fee9f9d8fe2ce0c13ca
  Author: Olaoluwa Osuntokun <[email protected]>
  Date:   2016-10-26 (Wed, 26 Oct 2016)

  Changed paths:
    M mempool/mempool.go
    M mempool/mempool_test.go
    M mempool/policy.go
    M mempool/policy_test.go
    M server.go

  Log Message:
  -----------
  mempool: add policy config option for transaction version

This commit adds a new option to the mempool’s policy configuration
which determines which transaction versions should be accepted as
standard.

The default version set by the policy within the server is 2; this
allows accepting transactions which have version 2 enabled in order to
utilize the new sequence locks feature.


Compare: https://github.com/btcsuite/btcd/compare/74fe2a4dfde5...e3eeb4a34a04

Reply via email to