Go to file
Patrick Lodder bde7442526
mempool: tune incremental fee to make more sense for Dogecoin
The value of DEFAULT_INCREMENTAL_RELAY_FEE has never been tuned for
Dogecoin since porting from Bitcoin Core 0.14. Even though the dual
meaning of this parameter is suboptimal, it can still be tuned.

This commit sets the value to 1/10th of DEFAULT_MIN_RELAY_TX_FEE
from validation.h, which causes:

1. Mempool limiting to be performed in steps of 0.0001 DOGE/kb
   instead of 0.00001 DOGE/kb
2. RBF to be accepted by the mempool if the new fee is at least
   0.0001 DOGE/kb higher than the previous fee known to the
   mempool
3. RBF to be cheaper than CPFP by a factor 10 (as the latter would
   require a fee of more than 0.001 DOGE/kb on a subsequent bumping
   transaction), to encourage mempool replacement over prioritizing
   through additional transactions that need to be mined.
4. Mempool limiting to be 10x faster to reset to zero than before,
   because for bitcoin, fee increments equaled their minimum fee,
   but for us this was 1/100th.

mempool_tests.cpp has been reworked a bit to reflect the reality
of having a lower increment than the minimum fee, as even though
this already was the case, this was not tested correctly due to the
static values in the unit test.
2021-09-25 21:51:36 +02:00
.github issue template updated to prevent spam in repository 2021-08-19 00:11:57 +02:00
.tx qt: Set transifex slug to 0.14 2017-01-02 09:36:03 +01:00
build-aux/m4 Update to Berkeley DB 5.3 2021-08-21 23:55:05 +01:00
contrib snap packaging for 1.14.5 2021-08-20 23:09:51 -04:00
depends depends: Fully determine path for darwin_{CC,CXX} 2021-09-23 20:14:03 +02:00
doc rename other icons 2021-09-14 21:18:15 -04:00
qa Reduce recommended fees 2021-09-03 10:52:24 +01:00
share rename other icons 2021-09-14 21:18:15 -04:00
src mempool: tune incremental fee to make more sense for Dogecoin 2021-09-25 21:51:36 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Added IntelliJ IDEA in .gitignore and removed dot from dogecoin.com link 2021-08-15 16:09:14 +01:00
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh 2016-09-21 23:01:36 +00:00
configure.ac Merge pull request #2483 from bjacquin/dev/beber/db53 2021-08-24 22:26:03 +02:00
CONTRIBUTING.md Grammatical: Added "," in #156 2021-08-23 23:29:35 +05:30
COPYING fix COPYING 2021-08-20 03:51:39 +02:00
INSTALL.md fixup installation guide 2021-08-20 03:07:32 +02:00
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 2015-12-14 02:11:10 +00:00
Makefile.am rename other icons 2021-09-14 21:18:15 -04:00
README.md Docs4Doge: refresh README introduction sentence 2021-09-14 18:24:28 +02:00
README_zh_CN.md Changes made to the readme translation file 2021-05-30 07:02:58 -07:00

Dogecoin Core [DOGE, Ð]

Dogecoin

DogecoinBadge MuchWow

Select language: EN | CN

Dogecoin is a community-driven cryptocurrency that was inspired by a Shiba Inu meme. The Dogecoin Core software allows anyone to operate a node in the Dogecoin blockchain networks and uses the Scrypt hashing method for Proof of Work. It is adapted from Bitcoin Core and other cryptocurrencies.

Website: dogecoin.com

Installation 💻

Please see the installation guide for information about installing Dogecoin Core.

Such ports

Dogecoin Core by default uses port 22556 for peer-to-peer communication that is needed to synchronize the "mainnet" blockchain and stay informed of new transactions and blocks. Additionally, a JSONRPC port can be opened, which defaults to port 22555 for mainnet nodes. It is strongly recommended to not expose RPC ports to the public internet.

Function mainnet testnet regtest
P2P 22556 44556 18444
RPC 22555 44555 18332

Ongoing development - Moon plan 🌒

Dogecoin Core is an open source and community driven software. The development process is open and publicly visible; anyone can see, discuss and work on the software.

Main development resources:

  • Github Projects is used to follow planned and in-progress work for upcoming releases.
  • Github Discussion is used to discuss features, planned and unplanned, related to both the development of the Dogecoin Core software, the underlying protocols and the DOGE asset.
  • Dogecoindev subreddit

Version strategy

Version numbers are following major.minor.patch semantics.

Branches

There are 3 types of branches in this repository:

  • master: Stable, contains the latest version of the latest major.minor release.
  • maintenance: Stable, contains the latest version of previous releases, which are still under active maintenance. Format: <version>-maint
  • development: Unstable, contains new code for planned releases. Format: <version>-dev

Master and maintenance branches are exclusively mutable by release. Planned releases will always have a development branch and pull requests should be submitted against those. Maintenance branches are there for bug fixes only, please submit new features against the development branch with the highest version.

Contributing 🤝

If you find a bug or experience issues with this software, please report it using the issue system.

Please see the contribution guide to see how you can participate in the development of Dogecoin Core. There are often topics seeking help where your contributions will have high impact and get very appreciation. wow.

Communities 🚀🍾

You can join the communities on different social media. To see what's going on, meet people & discuss, find the lastest meme, learn about Dogecoin, give or ask for help, to share your project.

Here are some places to visit:

Very Much Frequently Asked Questions

Do you have a question regarding Dogecoin? An answer is perhaps already in the FAQ or the Q&A section of the discussion board!

License - Much license ⚖️

Dogecoin Core is released under the terms of the MIT license. See COPYING for more information or see opensource.org