Fixed tabIndex and width in debugwindow.ui
Added Qt UI files for each dialog
Added Qt UI files
Added separate thread for peer dialogs to run RPC commands
Fixed tabIndex
Remove unneeded includes
Fixed error
Replaced RPCExecutor with g_connman
Replaced RPCExecutor with g_connman
Added two input fields for peer address and port
Remove peerThread
Validate IP addresses
Remove Peer now uses selected IP address in peerWidget
Interpret RPC response
Remove redundant include
Use a regular expression to validate IPs
Disconnect node if it has been discovered
Use port based on current chain
Change peerAddress -> peerPort
Allowed DNS names to be entered
Update src/qt/peerdialog.cpp
Co-authored-by: Ross Nicoll <rnicoll@rnicoll.name>
Fix typo
Co-authored-by: Ross Nicoll <rnicoll@rnicoll.name>
Use LookupHost to check address
Co-authored-by: Ross Nicoll <rnicoll@rnicoll.name>
Fix syntax typo
- Removed dead image links.
- Updated Travis ci badge link to direct to the master branch and the new Travis website url.
- Added Emojis to headers for clarity and to get the feel of dogecoin for newcomers.
- Bolded some sub headers for clarity. e.g. block reward sections.
- Code formatting.
plodder: cherry pick notes:
- Cherry-picked and sanitized to resolve conflicts
- fixed some very long lines
- removed tip4commit
- changed header for mining/subsidy info
Some locales sort differently, which causes a different order
of files, which leads to an unreproducible build.
Sort the files always with the C locale.
Checking scrypt PoW is expensive and needless in this case. All block
headers are already checked when they are accepted, and they will be
checked again on the receiving end.
Block download timeouts are expressed as a fraction of block interval time, so Dogecoin values have been too aggressive.
Matching Bitcoin values as a starting point.
Reduces DEFAULT_MEMPOOL_EXPIRY from 336 hours to 24 hours.
Motivation is that while blocks are empty, un-relayable tx are
stuck in mempools for a long time and effectively locking utxo
for 2 weeks until they can be respent, if no RBF opt-in was
performed (most wallet implementations do not do RBF opt-in.)
As the expectation is that block space will not be fully utilized
for the foreseeable future, and therefore, as long as this is the
case, no valid transaction should ever live in the mempool for
more than a couple of minutes.
This default setting can be overridden with the -mempoolexpiry
parameter by individual node operators to a value (expressed
in hours) that makes the most sense for the use cases the node
serves.