Skip to content

Conversation

@rebroad
Copy link
Contributor

@rebroad rebroad commented May 17, 2012

Also, reduces confusion when combined with future pull requests.

This is a small change, and possibly seems petty, but it's useful for two reasons:

  1. Principle of least surprise. Waiting can end (and does in the code), but Already Asked for requires a past event that's happened to unhappen. This is confusing.

  2. Later code (which I am hoping gets pulled when finished, such as Parallel block download #1326) uses variables that make sense, and makes the code simpler to understand when used with this renamed mapping.

  3. probably other reasons....

Also, reduces confusion when combined with future pull requests.
@Diapolo
Copy link

Diapolo commented May 17, 2012

I know from own observations, that core devs dislike variable or function renaming without a very good reason ;), only wanted to say...

@rebroad
Copy link
Contributor Author

rebroad commented May 17, 2012

Principle of least astonishment is usually the best reason for such a change, along with naming conventions probably coming a close second (or joint first).

@jgarzik
Copy link
Contributor

jgarzik commented May 17, 2012

NAK, breaks other more important changes for little gain

@jgarzik jgarzik closed this May 17, 2012
suprnurd pushed a commit to chaincoin-legacy/chaincoin that referenced this pull request Dec 5, 2017
* Few networking fixes:
- skip "masternode"/inbound connections for sync related processes
- do not sync gov data to other nodes until fully synced ourselves
- do not accept incoming connections until fully synced

* inbound connections could be harmful only if our node is a masternode

* same for CGovernanceManager::Sync
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request Jan 22, 2019
Add missing debug categories debug helper message
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
64465b7 [Refactor] Consensus: Stake Modifier V2 (random-zebra)
8083725 [Refactor] Consensus: TimeProtocolV2 parameters (random-zebra)
4d1c696 [Refactor] Consensus: nStakeMinAge, nStakeMinDepth, nFutureTimeDrift (random-zebra)
e69cee2 [Refactor] Consensus: restore nMaxMoneyOut as consensus param (random-zebra)
08a581d [Refactor] Consensus: fAllowMinDifficultyBlocks, fPowNoRetargeting (random-zebra)
ca6ea3c [Refactor] Consensus: nTargetTimespan, nTargetSpacing, nTimeSlotLength (random-zebra)
a281dee [Refactor] Consensus: remove unneeded getters. Rename BIP65Height (random-zebra)
284271c [Refactor] Consensus: bnProofOfWorkLimit / bnProofOfStakeLimit (v1-v2) (random-zebra)

Pull request description:

  This PR builds on
  - [x] bitcoin#1328

  Populates the `consensus` struct with all relevant consensus parameters.
  Resets `nMaxMoneyOut` as chain param (with different value for TestNet).
  Cleans up several unneeded fields in ChainParams.

  EDIT: Current PR has been split in two. Second part is bitcoin#1344

ACKs for top commit:
  furszy:
    good, utACK 64465b7.
  Fuzzbawls:
    utACK 64465b7

Tree-SHA512: d3e46bc8bb2ad9ee48abcbc4d4b1df2f59914360aaca72e93e19a5578248ecb95fd6a422477238e4736bc767d4e226f5b7f867174d96dcace73621946bf84df8
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
92221b1 [Cleanup] Remove ChainParams::DefaultMinerThreads (random-zebra)
98494ab [Refactor] Consensus: move other consensus params to the struct (random-zebra)
7c673bf [Refactor] Consensus: masternode/budget-related fields (random-zebra)
7736d6c [Refactor] Consensus: zerocoin-related fields (random-zebra)
0b63af4 [Refactor] ChainParams: move genesis creation at the beginning (random-zebra)
1e5a33d [Refactor] Consensus: wrapped serials params (nSupplyBeforeFakeSerial) (random-zebra)
70c4ae5 [Refactor] Consensus: height-based activations (random-zebra)

Pull request description:

  Second part of
  - [x] bitcoin#1341

  Split as individual PR for ease of review.

ACKs for top commit:
  Fuzzbawls:
    ACK 92221b1
  furszy:
    utACK 92221b1.

Tree-SHA512: a3f1c10fc568e264039d2fc5a4dedc01d947b380e55c5170679598cb6859274c73157fb9ade6f5345a9781b9028943629b304aac8c3b0d7849946bdaed85fb52
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants