- Revert moving of ports and branching strategy because those are
actively preventing questions and PR difficulty
- Remove travis badge because we no longer use travis
- Fix formulation throughout the document
- Rewrite the contribution section
- Switch from Dogecoin devs twitter to Dogecoin twitter under
communities
- Add Q&A board to FAQ section
- Fix document language selector
- Bring tables back to "mining information"
Author: AbcSxyZ <rossi.sim@outlook.com>
Cherry-picked and squashed from:
20480d33b README: change social media position
39a209b98 README: Change section order
bdb727981 README: reorganize social medias, split dev specific
& and more community related in 2 sections
bbc6c921c Add emote to titles
e39256825 Install.md : Improve first title
ebef882c5 Fix typo
1cec6b16b Extract FAQ and INSTALL into respective files
314b6f8e2 Add developement & contribution information directly
on readme
a7e556924 Remove original block reward schedule
8cb73041a Move licence section at README bottom
without partially backporting a new testframework.
- Adds a condition to NodeConn that when asyncore calls handle_read
without any data, this must be a disconnect and closes the socket
- Adds a little loop in the p2p-acceptblock client that waits for
the socket to be in a closed state
- Makes expected disconnects non-optional in p2p-acceptblock
- Syncs the test descriptions and outputs with reality
Implements, tests and assures wallet operator ease-of-sovereignty and making
sure that user-defined fee logic persists through versions in the future by
fixing and testing -paytxfee
1. There was an override of ANY user-defined value to CWallet::GetMinimumFee
- Former logic: always override any value with either -mintxfee or
-mintxrelayfee, whichever is highest
- Proposed logic in this pull request:
- if the user specifies a value, only override when it is lower than
-mintxfee or -mintxrelayfee - this works because we set any default
-mintxfee to be the same as -paytxfee, unless the user explicitly
sets a -mintxfee.
- if no value has been specified, use the rate from -mintxfee or
-mintxrelayfee, whichever is highest
2. Test that the interaction between the wallet parameters -paytxfee and
-mintxfee function as intended. This has to be done using rpc tests rather
than unit tests because it tests the actual parameters passed to the
executables.
3. Undoing the override exposed a misconfiguration in the bumpfee.py test,
where fees were explicitly set higher, yet ignored in subsequent bumps.
Test that the interaction between the wallet parameters
-paytxfee and -mintxfee function as intended. This has to
be done using rpc tests rather than unit tests because it
tests the actual parameters passed to the executables.
recreated seeds by selecting peers across 20+ nodes that:
1. Keep up with updates, in this case run 1.14.3 or higher
2. Have NODE_NETWORK set
3. Are not known scanning clients
4. Are connectable
5. Are stable - I ordered nodes by time they have been connected to
one of my nodes
resulting set is 120 good nodes for mainnet and 20 good nodes for
testnet, serialized into chainparamsseeds.h using the contrib/
scripts.
