dogecoin / ltc-scrypt

Python3 wrapper for Litecoin-Scrypt

Dogecoin Core [DOGE, Ð]

IMPORTANT: Starting August 2024, the master branch has become the primary integration branch and has become unstable. Please check out a tagged version before compiling production binaries.

For internationalized documentation, see the index at doc/intl.

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.

For information about the default fees used on the Dogecoin network, please refer to the fee recommendation.

Website: dogecoin.com

Usage 💻

To start your journey with Dogecoin Core, see the installation guide and the getting started tutorial.

The JSON-RPC API provided by Dogecoin Core is self-documenting and can be browsed with dogecoin-cli help, while detailed information for each command can be viewed with dogecoin-cli help <command>. Alternatively, see the Bitcoin Core documentation - which implement a similar protocol - to get a browsable version.

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 4 types of branches in this repository:

• master: Unstable, contains the latest code under development.
• maintenance: Stable, contains the latest version of previous releases, which are still under active maintenance. Format: <version>-maint
• development: Unstable, contains new code for upcoming releases. Format: <version>-dev
• archive: Stable, immutable branches for old versions that no longer change because they are no longer maintained.

Submit your pull requests against master

Maintenance branches are exclusively mutable by release. When a release is planned, a development branch will be created and commits from master will be cherry-picked into these by maintainers.

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 latest meme, learn about Dogecoin, give or ask for help, to share your project.

Here are some places to visit:

• Dogecoin subreddit
• Dogeducation subreddit
• Discord
• Dogecoin Twitter

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

ltc-scrypt's Issues

Build the module differently

Originally posted by @xanimo in #9 (review)

Also a small nit that can be addressed in the future is to address the deprecation warnings regarding setup.py install as shown here:

$ CC=clang python setup.py install --user
running install
/home/bluezr/.local/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/bluezr/.local/lib/python3.10/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/bluezr/.local/lib/python3.10/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 0.1.43ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/bluezr/.local/lib/python3.10/site-packages/pkg_resources/__init__.py:123: PkgResourcesDeprecationWarning: 1.1build1 is an invalid version and will not be supported in a future release
...

This can be resolved by running python -m pip install .:

bluezr@x:/source/repos/ltc-scrypt$ CC=clang python -m pip install .
Defaulting to user installation because normal site-packages is not writeable
Processing /source/repos/ltc-scrypt
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: ltc-scrypt
  Building wheel for ltc-scrypt (setup.py) ... done
  Created wheel for ltc-scrypt: filename=ltc_scrypt-1.0-cp310-cp310-linux_x86_64.whl size=36781 sha256=0bceca8e9adbf6d2df42c6d9ac0e48a14036b00f1c5d6a61a9df77345dae241d
  Stored in directory: /home/bluezr/.cache/pip/wheels/ef/29/20/2b1706323ba8e21079924937b665d6b9c847ee8e478587a526
Successfully built ltc-scrypt
Installing collected packages: ltc-scrypt
  Attempting uninstall: ltc-scrypt
    Found existing installation: ltc-scrypt 1.0
    Uninstalling ltc-scrypt-1.0:
      Successfully uninstalled ltc-scrypt-1.0
Successfully installed ltc-scrypt-1.0
bluezr@x:/source/repos/ltc-scrypt$ CC=clang python test.py
test successful.

Tracker: module intake into Dogecoin "org"

Minimum needed for this to be a workable repo:

• Needs a license: #2
• Needs contribution guidelines: #3
• Needs a README with install documentation #6