LDOGE

Litedoge: So Lite, So Fast! Much Fun!

CORE Wallet Version 3.6.0.1

https://s2.coinmarketcap.com/static/img/coins/64x64/853.png https://github.com/ldoge/LDOGE/blob/update-copyright-and-bug-fixes/src/qt/res/icons/litedogecoin-128.png

LDOGE Information

Ticker: LDOGE | PoW/PoS | Algorithm:SCRYPT | Nodes | Ports :———————-:|:—————:|:—————-:|:—————–:|:————-: Genesis Block: | 3/15/2015 | 08:15:00 PM UTC | 108.95.86.140 | MAINNET Max POS REWARDS: | 500.1 COINS | | 122.173.26.30 | PORT 17014 Last PoW Block:8000 | 3/19/2015 | 9:08:33 PM UTC | 46.223.163.18 | RCP 17015 First PoS Block:8001 | 3/19/2015 | 9:10:56 PM UTC | 174.84.66.125 |
PoS Annual Interest: | 1% | | 189.161.146.213 | TESTNET PoS type: | 2.0 | | 88.78.111.11 | PORT PoS Minimum Stake Age: | 8 Hours | | 176.137.227.2 | RCP TOTAL SUPPLY | NO CAP | | 24.18.45.238 | Maturity: |501 blocks | | 89.41.26.58 |

Punch list of development in the works

Enable Proof of work again, Make rewards up to 18 coins per P.O.W. Block, Electrum Wallet, make buildable on all systems

LITEDOGE Development Repository

Official Website: https://ldoge.github.io/LDOGE

====================

Latest Wallets: https://github.com/ldoge/LDOGE/releases

====================

Wiki Build/Install guides: https://github.com/ldoge/LDOGE/wiki

====================

Development Channel: https://discord.gg/88sqh9jYt3

====================

Forums

Visit our BitCoinTalk Forum https://bitcointalk.org/index.php?topic=1308769.0

Block Explorers

NEW BLOCK EXPLORER COMING SOON!

Node Peer list to manually add nodes: 66.129.156.184:17014 46.105.78.216:17014 137.184.45.155:17014 95.217.77.209:17014 5.180.25.86:17014

Exchanges

https://www.nofinex.com/market/pair/LDOGE-USDT.html

HTTPS://btcpop.co

Faucets

https://btcpop.co/faucet/LDOGE

https://bill48105.github.io/wallet/ -wallet/tip bot/faucet/2fa

Social Media

Visit our Twitter/X page https://x.com/LiteDogeLDOGEUS

License

Litedoge (LDOGE) Core is released under the terms of the MIT license. See COPYING for more

information or see http://opensource.org/licenses/MIT.

Development Process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don’t match the project’s coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of LiteDoge.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled ‘stale’.

When Building Litedoge use qmake for QT GUI and use make for building Non GUI deamon.