New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestCoin 0.0.1 #10643
Closed
Closed
TestCoin 0.0.1 #10643
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ss of state (#1094) * Allow MN broadcasts to update MN information regardless of state * Add masternode public keys to log output for debugging * Moved log message from start-alias to CMasternodeBroadcast::Create * Fixed log message
* add GetStateString and static CMasternode::StateToString helpers * Fix CActiveMasternode: - should run `ManageStateLocal` only when `eType == MASTERNODE_LOCAL` - should set `nState = ACTIVE_MASTERNODE_NOT_CAPABLE` in `ManageStateInitial` to let `GetStatus` return proper message - more/better log output
Set last watchdog time to mnb.sigTime when masternodes are first added or updated from a broadcast
Use nSuperblockCycle instead of "blocks monthly" approximation
* [UI] Fix for empty Masternode list when mncache.dat exists [review changes] * [UI] Fix for empty Masternode list when mncache.dat exists [review changes]
- more dash -> dashcore - dashpay.io -> dash.org
* PoSe changes: - use helpers to alter nPoSeBanScore within predefined range only - use nPoSeBanHeight instead of timeout of inactivity to ban masternodes till some block in the future (currently should block for the whole payment cycle) - add log output on pose score increase in CheckSameAddr
Fix Linux packaging
Fix Gitian Packaging
calculate hash once before entering loop, should make it around an order of magnitude faster
* refactoring PS, cleanup, more log output in debug mode (part of #1120) * fix dsq rate limit calculations on new dsq
…instead of wallet (#1122)
Fixes dash-qt --version (--help etc) crash (Segmentation fault: 11)
* Added net logging messages in main.cpp * Added logging for trigger removal * Improved log message for CGovernanceManager::UpdatedBlockTip * Improved log messages in CGovernanceManager::UpdateCachesAndClean * Added more logging to CGovernanceTriggerManager * Check vote validity before pushing inventory during sync * Add triggers to map after loading governance.dat file
…ting from queue, should check nLastDsq only (#1123)
- fail to process dsa when session is already ready - fail to process dsvin if session is not ready yet - fail to process any message on the wrong side (mn/client) - fail in PrepareDenominate if pool already has entries - fail if can't sign anything in final tx, also reset local pool in such case - fix "number of entries" pushed on DSSTATUSUPDATE
- make sure dsq is not too much in the future - do not process seen dsq - do not alter nTime for dsq localy, use memory only fTried instead
* Implement RequestOrphanObjects * Ensure governance objects are only requested from peers once per call * Add gobject log messages * Implemented CleanOrphanObjects * Move governance maintenance functions from NewBlock to a time-based function * Remove unused delcaration for mapAskedForGovernanceObject
Imports keys from an Electrum wallet export file (.csv or .json)
#1393) If daemon crashes, it can't save latest block sometimes, so querying daemon for presumably best/last hash would result in a list of all txes recognized by this wallet as its own since genesis block which could be confusing, to say at least. Same applies for typos etc. This should fix it. Not sure why but such weird behaviour was the case since listsinceblock rpc was initially introduced in Bitcoin 0.5 (Oct 5, 2011) bitcoin@3a6e468
* Add keyed netgroup field to CNode * Improved node eviction implementation * Remove need for CNodeRef
* Overhaul of coin selection for mixing DoAutomaticDenominating logic should be: - check pre-conditions, - check denominations and collaterals, - try using existing queue, - try creating new queue. Currently coins are selected too early and conditions are not quite right. This is partially due to the fact that we no longer merge old inputs and thus we are no longer able to calculate thresholds correctly using SelectCoinsDark. To do this in a proper way we should use balances i.e. GetAnonymizableBalance etc. Another issue is that we should take fee into account when we calculate such balancies and when we select coins we should ask for a correct denom, not just the smallest one as a minimum value. And finally there are two bugs. SelectCoinsGrouppedByAddresses: shouldn't push items smaller than the smallest denom into resulting vector. SelectCoinsDark: should allow small inputs in where "small" is defined by nValueMin, not by some arbitrary amount. * apply fee assumption for non-denoms only * fix * remove const
* Disable salvagewallet in GUI salvagewallet is known to cause problems and it's way to powerful to let it be accessible in GUI bitcoin#7463 I have few reports from different users as well, would be a disaster for them, glad we have autobackup... * typo
* Add missing alert functionality * add alert test generation * re-enable alerts by default
* Fixing download path and sha256 hash * typo * package version variable
* translations201703 - en part * 80%+ translations * ru to 100%
* Fix mn list sync Bump sync timeout if masternode is "initially valid" and last ping was quite a long time ago * compare to current time
- fix info about files - add info about InstantSend
- check if mn rank can be calculated - fix "is in top" condition
* Avoid adding the same vote multiple times to the vote file * Cleanup multiple votes in vote file
* Modify MasternodeRateCheck to support updating buffers only on failure * Update rate check buffer only when fAddToSeen is true
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.