Dogecoin is a cryptocurrency like Bitcoin

Dogecoin Core [DOGE, Ð]

Dogecoin

Build Status

Dogecoin is a cryptocurrency like Bitcoin, although it does not use SHA256 as its proof of work (POW). Taking development cues from Tenebrix and Litecoin, Dogecoin currently employs a simplified variant of scrypt.

License – Much license ⚖️

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

Development and contributions – omg developers

Development is ongoing, and the development team, as well as other volunteers, can freely work in their own trees and submit pull requests when features or bug fixes are ready.

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: -maint
  • development: Unstable, contains new code for planned releases. Format: -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.

Contributions ✍️

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Very Much Frequently Asked Questions

How much doge can exist? – So many puppies! 🐕

Early 2015 (approximately a year and a half after release) there will be approximately 100,000,000,000 coins. Each subsequent block will grant 10,000 coins to encourage miners to continue to secure the network and make up for lost wallets on hard drives/phones/lost encryption passwords/etc.

Such mining information

Dogecoin uses a simplified variant of the scrypt key derivation function as its proof of work with a target time of one minute per block and difficulty readjustment after every block. The block rewards are fixed and halve every 100,000 blocks. Starting with the 600,000th block, a permanent reward of 10,000 Dogecoin per block will be issued.

Originally, a different payout scheme was envisioned with block rewards being determined by taking the maximum reward as per the block schedule and applying the result of a Mersenne Twister pseudo-random number generator to arrive at a number between 0 and the maximum reward.

This was changed starting with block 145,000, to prevent large pools from gaming the system and mining only high reward blocks. At the same time, the difficulty retargeting was also changed from four hours to once per block (every minute), implementing an algorithm courtesy of the DigiByte Coin development team, to lessen the impact of sudden increases and decreases of network hashing rate.

The current block reward schedule:

1–99,999: 0–1,000,000 Dogecoin

100,000–144,999: 0–500,000 Dogecoin

145,000–199,999: 250,000 Dogecoin

200,000–299,999: 125,000 Dogecoin

300,000–399,999: 62,500 Dogecoin

400,000–499,999: 31,250 Dogecoin

500,000–599,999: 15,625 Dogecoin

600,000+: 10,000 Dogecoin

The original block reward schedule, with one-minute block targets and four-hour difficulty readjustment:

1–99,999: 0–1,000,000 Dogecoin

100,000–199,999: 0–500,000 Dogecoin

200,000–299,999: 0–250,000 Dogecoin

300,000–399,999: 0–125,000 Dogecoin

400,000–499,999: 0–62,500 Dogecoin

500,000–599,999: 0–31,250 Dogecoin

600,000+: 10,000 Dogecoin

Wow plz make dogecoind/dogecoin-cli/dogecoin-qt

The following are developer notes on how to build Dogecoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

Such ports

  • RPC 22555
  • P2P 22556

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.

debug.log

If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging messages are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play dogecoins" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode, blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regtest mode.

DEBUG_LOCKORDER

Dogecoin Core is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of which locks are held, and adds warnings to the debug.log file if inconsistencies are detected.

Comments
  • Not actually capped at 100 billion?

    Not actually capped at 100 billion?

    Looking at getBlockValue (and nSubsidy), after the 600 000th block, it will forever be 10k a block. Once it hits 100 billion, it should be set to 0. However, this seems a bit difficult due to the randomness being brought in.

    Or rather, that this is intentional? But then the dogecoin thread should mention there is no theoretical cap, but will basically level out at 10 billion (for all intents and purposes)?

    Such confuse?

  • URGENT : Dogecoin fork #2

    URGENT : Dogecoin fork #2

    Hello everyone :) Reddit is constantly going down so lets start a discussion here about what were going to do ? So far what we know is :

    1. Most of the pools are forked.
    2. 1.5 is having issues on RPC and thats why pools are using the 1.4x wallet for payouts
    3. Dogechain is running 1.4 for the exact same reason as 2. So far what we dont know is :
    4. Which fork is the correct fork ?
  • Consensus plan for next major release (1.21)

    Consensus plan for next major release (1.21)

    This issue describes the planned protocol features that need to be activated by consensus for the next major release (planned to be 1.21)

    Summary

    With the next major release, we plan to propose 2 protocol changes for activation at once: segwit and csv. Both have been deployed on Bitcoin's mainnet for a longer time and are considered non-contentious. As such it will save us all time when we do them at once instead of sequential. VersionBits / BIP9 will not be proposed at this time because of the conflict in the version with AuxPow, and this would be a much more dangerous, and possibly contentious change.

    A block versions 5 and protocol version 70016 will be proposed for this implementation.

    Details

    In scope

    • Segregated witness a.k.a. segwit
      • Functionality: Separates spending proofs (i.e. signatures) from transactions when embedded in blocks
      • Rationale: Further reduces transaction malleability.
      • Scope: BIP141, BIP143 and BIP147
      • Note: we will carefully consider P2W* addressing.
    • CheckSequenceVerify a.k.a. CSV
      • Functionality: Allows consensus-enforced locking of an output until a relative time and exposes the field to redeem scripts
      • Rationale: Allows for much more sophisticated redeem scripts, must-have feature for Lightning-like L2 networks.
      • Scope: BIP68, BIP112 and BIP113

    Not in scope

    • VersionBits - Needs another, more dangerous soft-fork, see #1340 and #1344. We deem this too risky to do at once with the features described above, especially for a meta-feature.
    • TapRoot - Not yet deployed on Bitcoin
    • Extension Blocks - Not yet deployed on Litecoin

    Deployment

    Deployment is planned to be proposed through a single soft fork, identified by block version 5 (full version: 0x00620104) and a protocol update to version 70016 (0x011180) through the usual 95% SuperMajority consensus rule (full activation with 1900 blocks having v5 in a 2000 block window) similar to the BIP65 soft fork that was proposed with Dogecoin Core 1.14.

    Comments / questions? Let us know here.

  • [feat] Radically improve Dogecoin by forking Nano: Zero fees, fastest cryptocurrency, no inflation, no mining

    [feat] Radically improve Dogecoin by forking Nano: Zero fees, fastest cryptocurrency, no inflation, no mining

    One idea to radically improve Dogecoin would be to fork Nano and implement its featureset in Doge:

    How is this accomplished?

    • A block-lattice ledger data structure (every account has its own blockchain that only the owner can modify)
    • Open Representative Voting for consensus instead of Proof of Work
    • https://docs.nano.org

    Describe Alternatives Banano is another meme coin that peeled (forked) Nano. It even has its own yellowpaper :)

    Related Code https://github.com/nanocurrency/nano-node

    Lowest latency + least error == Win

  • Peer-to-Peer Dogecoin Relay Network (based on Starlink)

    Peer-to-Peer Dogecoin Relay Network (based on Starlink)

    There exist several technical bottlenecks to scale Proof-of-Work (PoW) blockchains. Some of them are the CPU time for transaction validation, the hard disk space to store the chain, and many others.

    One of the most often overlooked bottlenecks is the communication latency and Internet speed between miners. The slower the Internet between the miners is, the less synchronized they become, and the more the blockchain security degrades. That is one of the fundamental reasons why it’s not trivial to scale Doge- or Bitcoin by simply increasing the block-time frequency and the block size. You can find empirical results for blockchain network simulations here.

    Dogecoin on Starlink?

    Now, one way to speed up a blockchain without any protocol change is to simply improve the network connectivity between the miners! This is where Starlink, the satellite-based Internet from SpaceX could help Dogecoin to be closer to the moon.

    Starlink latency between London and Singapore is expected to be much lower than current Internet round trip times (RTT). Starlink could hence speed up Dogecoin’s block and transaction propagation, effectively scaling its blockchain substantially.

    1_xjFd6c4GylHPlSh9s9VO2Q

    Mark Handley beautifully simulated how much lower the latency of Starlink would be, when compared to the current terrestrial Internet. For example, he estimates that the round trip time (RTT) between London and Singapore would be about 108ms on Starlink, while Fiber optic Internet currently yields 159ms.

    Starlink is certainly already highly anticipated by traditional financial institutions to perform lower latency arbitrage across the major financial exchanges. Using Starlink as a network to propagate blockchain peer-to-peer data among miners would equally help speed up substantially the current blockchain throughput, without deteriorating its security. Naturally, a possible risk here would be for a single for-profit company to effectively own the entire blockchain relay network, a risk that may be mitigated with future orthogonal satellite Internet services.

    Blockchain Relay Network

    Analogous to the FIBRE network, Erlay, and other prior relay networks, Dogecoin could very well scale its transaction throughput by orders of magnitude, if its miners were to engage in a dedicated Starlink relay network. Naturally, this relay network propagation protocol should be optimized for the Starlink characteristics to fully take advantage of its topology.

    Quantifying the optimal protocol, and parameters is certainly a very exciting avenue towards scaling Dogecoin! What do you think?

  • much crash to encrypt moneybag

    much crash to encrypt moneybag

    crash on win7 64bit when trying to encrypt wallet. someone on forum also reported this. other wallets do not crash.

    NOTE: Only on certain windows platforms and not on others

    Other Manifestations: Cannot import private key Cannot run console commands

  • Proposed Dogecoin Scaling Roadmap

    Proposed Dogecoin Scaling Roadmap

    So seeing as how rnicoll said they would like a Dogecoin CTO, (EDIT: I am not proposing roles and do NOT want to be the "Dogecoin CTO"! I am merely saying I can help with those sorts of functions, as can many others here) I can help out with some tech planning as someone who has thought deeply about blockchain and other forms of crypto since Feathercoin came out and has dozens of inventions in the crypto space, and am the CTO of my own crypto (non-blockchain) project. I also have been around the Dogecoin community since 2017 and have always been a huge supporter of tail emission, of which Dogecoin is the most prominent example.

    Based on this post to reddit with tons of community support: https://www.reddit.com/r/dogecoindev/comments/nfabqm/im_not_elon_but_i_do_understand_him_a_deep_dive/

    And also this github issue for segwit2x: https://github.com/dogecoin/dogecoin/issues/1849

    Galaxy Digital Analysis: https://docsend.com/view/vutymtgqjf99yrpu

    Ross on "Working with Elon": https://decrypt.co/71264/dogecoin-dev-what-its-like-working-with-elon-musk

    Satoshi Nakamoto on Scaling: https://www.reddit.com/r/btc/comments/6cb4ey/bitcoin_can_already_scale_much_larger_than_that/

    2021 -Scale 2x current-

    1. Reduce min tx fees to below 1 cent in 1.14.4 update. Elon suggests 100x reduction, I suggest 200x (which would put us at half a cent when we hit $1)

    2. Once fee is reduced, monitor blocksize for 3 months. See if the blocksize increases significantly and we have any spam issues. I anticipate blocksize will not change significantly and there will be no spam issues.

    3. If blocksize is stable, implement segwit and double max blocksize to 2mb at the same time in 1.21 update.

    2022 -Scale 8x current-

    1. Address any issues with segwit and monitor that blocksize is stable.

    2. Once everything is stable, reduce blocktime by one-half to 30 seconds. Monitor syncing and orphan rate. Orphan rate should always stay below 10%.

    3. Once everything is stable double blocksize again (to 4mb). Monitor for spam and adjust min tx fee accordingly. Implement lightning code as needed.

    2023 -Scale 16x current-

    1. Once everything is stable reduce blocktime by one-half to 15 seconds. Monitor syncing and orphan rate.

    2024 -Scale 40x current-

    1. Once everything is stable Increase max blocksize to 10mb (10x bitcoin and our current blocksize). Adjust min tx fee as needed to keep blockchain growth under control and in-line with our recommended full node specifications *.

    Beyond -Scale potentially 100x + current-

    1. As orphan rate approaches 5% consider future incremental blocktime decreases to eventually 6-7 seconds or faster depending on how we can stay synced and maintain orphan rate below 10%.

    2. If we get to the point that block space is limited and fees are increasing, consider increasing max blocksize while keeping to parameters of node syncing and orphan rate.

    *Notes:

    • Of course we will need to change block reward every time blocktime is updated to maintain a constant emission of 10,000 coins per minute.

    • We need to develop metrics and measures for orphan rate and syncing rate.

    • We need to develop suggested specifications for full nodes and required specifications for full nodes. RAM, processor speed/cores, and storage space should be specified. We need to consider that each full node does the job of the entire paypal server farm and therefore a rudimentary server will be required if we progress beyond a hobby project. In light of this we need to make running a "pruning node" easily selected from the core wallet.

    • If energy usage / asic unavailability due to chip shortage becomes a serious issue and is causing potential centralization, consider change of PoW algorithm to ProgPoW which is a well developed ASIC resistant GPU friendly hashing algorithm. If energy use or GPU availability becomes a major concern, there is always the CPU algo Yespower.

    • If Proof of Work proves way too slow or other serious problems with PoW arise (in other words; "if all else fails"), we can consider a change to PoS or Proof of Rest https://github.com/dogecoin/dogecoin/issues/1942 or some other solution. Or PoS as a layer 2 https://github.com/dogecoin/dogecoin/issues/1924.

    • We should also do research into how our nodes sync with having our nonce in other chains' (we are merge mined with all scrypt coins, not just Litecoin) blockchain and how that effects our syncing, if at all.

    • Consider improving/tweaking payout protocols for development contributions with the goal that someone can quit their job and work full time on dogecoin development with minimal risk.

  • Fixed Block Sizes & Block re-targetting

    Fixed Block Sizes & Block re-targetting

    Implemented Digishield on 1min retarget, and Fixed Block Sizes after the 150k block mark, in order to prevent multipool's gaming the random block algorithm, and distorting the hash rates.

    NB: UNTESTED ON TESTNET. Do not deploy.

    11/03/14 : Release Candidate

    • /u/lleti
  • Doge Chain Balance amout not showing up in Doge Core Wallet

    Doge Chain Balance amout not showing up in Doge Core Wallet

    Describe the issue

    Transfer of my first mining payout shows in dogechain but hasn't went to dogecore wallet

    Expected behaviour

    Balance from dogechain should show in dogecore wallet

    Actual behaviour

    Correct amount shows in dogechain

    Screenshots.

    Lost

    What version of Dogecoin Core are you using?

    Dogecoin Core version v1.14.3 (64-bit)

    Machine specs:

    • OS: Windows 8.1 Pro
    • CPU: i7 4980HQ
    • RAM: 32 G
    • Disk size: 500 G
    • Disk Type (HD/SDD): SSD
  • Derivation path changes in 1.21-dev

    Derivation path changes in 1.21-dev

    This PR generates derivation path m/0'/3'/ for newly-created wallets in dogecoin-1.21 to be consistent with derivation path used in version 1.14.5.

    Note: As I understand it, version 1.21 already seems to support "out-of-the-box" older derivation path m/0'/0' used in 1.14.0-1.14.4 because the condition that checks path vector elements in walletdb.cpp expects 0' value at path[1]:

    if (path[1] != 0x80000000 && path[1] != (1 | 0x80000000)) 
    {
        strErr = strprintf("Unexpected path index of 0x%08x (expected 0x80000000 or 0x80000001) for the element at index 1", path[1]);
        return false;
    }
    

    (it's just a matter of making sure that wallets with path m/0'/3' from 1.14.5 and newly-created wallets will have no issues moving forward, so, naturally, more testing will be required).

    P.S. augmenting what was done by rnicoll in https://github.com/dogecoin/dogecoin/pull/2355

  • Can we double blocksize at the same time as we introduce Segwit?

    Can we double blocksize at the same time as we introduce Segwit?

    Example code pull https://github.com/bitcoin/bitcoin/pull/6451

    This topic has received massive upvotes with 97% up for doubling blocksize when introducing segwit: https://www.reddit.com/r/dogecoindev/comments/mvdzls/transaction_speed_and_fees_hyper_doge/

    And this topic describes it also: https://www.reddit.com/r/dogecoindev/comments/muvl1t/scaling_bitcoin_was_supposed_to_implement_segwit/

    Sporkin posts that relate to this: (Thanks u/jamiereeno) https://www.reddit.com/r/dogecoin/comments/be8pe8/fully_exited_all_positions_in_doge/el4v0bj/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

    Sporklin post with an acknowledgment from langer_hans: (Thanks u/jamiereeno) https://www.reddit.com/r/dogecoin/comments/2hdjuj/dogecoin_is_an_independent_codebase/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

    See comments for a proposal by @rnicoll to reduce blocktime to achieve the same goal

    Even supposing Segwit leads to a fully functional lightning network, still a transaction pair needs to be completed before a lightning channel can be opened. So it makes sense to scale blocksize to accommodate for mass adoption so that fees and congestion stay low - and high value transactions can be settled on-chain. Also I strongly suggest that segwit addresses always remain optional, like in Bitcoin. My suggestion is to double blocksize whenever needed, perhaps every 7 years. I think doing this at the same time as the addition of segwit can help set a culture that we will increase blocksize as needed to scale to be money for the world. Currently we never fill up blocks which also shows that increasing the blocksize isn't going to magically make the blocks bigger in the near term and there would be no difference to running a node. As a global payments network, we will eventually need to settle (on-chain) hundreds or more transactions per second (even if there are thousands of lightning per second) and we can only accommodate 33 with a 1mb block size. If we doubled blocksize every 7 years on average, this stays well below moore's law and running a node will never become burdensome to someone willing to invest in a reasonable server. Again each server is hosting a global payments network so we shouldn't assume a full node will always be able to be run from a smartphone, so I think slowly increasing blocksize would be the way to go to make sure we are able to scale properly.

    I understand this will take a hard fork, but it keeps with the core of Dogecoin so it will get full adoption and will not lead to a chain split. I think the biggest risk to a chain split is refusing to increase blocksize, and that is what led to the creation of Bitcoin Cash. So a hard fork to double blocksize will not lead to a chain split and can help unify the community and show the world that we indeed will scale to be money for the world and can increase mainstream adoption even more. ETH hardforks regularly and this does not lead to chain splits, so it is a very viable strategy especially if planned long in advance.

  • [bug]

    [bug]

    Bug Report

    Current behavior:

    Expected behavior

    Steps to reproduce:

    Screenshots

    Dogecoin Core version

    Machine specs

    • OS:
    • CPU:
    • RAM:
    • Disk size:
    • Disk Type (HD/SDD):

    Extra information

  • [bug]

    [bug]

    Bug Report

    Current behavior:

    Expected behavior

    Steps to reproduce:

    Screenshots

    Dogecoin Core version

    Machine specs

    • OS:
    • CPU:
    • RAM:
    • Disk size:
    • Disk Type (HD/SDD):

    Extra information

  • question about lost dogecoin REVISITED

    question about lost dogecoin REVISITED

    Discussed in https://github.com/dogecoin/dogecoin/discussions/3061

    Originally posted by ckoretsky July 21, 2022 hi, im sorry to bother anyone, i dont know where else to ask help finding my dogecoin. I have this from coinbase. and I was running dogecoin core on both my computers at the time, silly since i know nothing about how it all works. thanks if anyone can help

    email: [email protected] image

    Screenshot 2022-07-214111806

  • [bug] 	 How to change ONLY wallet location?

    [bug] How to change ONLY wallet location?

    Error: Wallet /root/.dogecoin/wallet resides outside data directory /root/.dogecoin

    image

    .CONF FILE : dnsseed=1
    upnp=0
    printtoconsole=1

    server=1

    rpcuser=XXXXXXXXXXXXXXXXXXXXXXXXXXXX addresstype=XXXXXXX rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX rpcport=2002
    rpcbind=0.0.0.0
    rpcallowip=0.0.0.0/0
    prunr=2500

    #->>>>>>
    wallet=/root/.dogecoin/wallet

    Bug Report

    Current behavior:

    Expected behavior

    Steps to reproduce:

    Screenshots

    Dogecoin Core version

    Machine specs

    • OS:
    • CPU:
    • RAM:
    • Disk size:
    • Disk Type (HD/SDD):

    Extra information

  • depends: Suppress array-bounds errors in libxkbcommon

    depends: Suppress array-bounds errors in libxkbcommon

    When building depends on GCC 12.1+ (GCC 12.2 in my case) it will fail when building libxkbcommon. This PR introduces a workaround around that error to fix compilation.

    src/xkbcomp/ast-build.c:82:27: error: array subscript 'ExprDef[0]' is partly outside array bounds of 'unsigned char[32]' [-Werror=array-bounds]
       82 |     expr->expr.value_type = type;
          |     ~~~~~~~~~~~~~~~~~~~~~~^~~~~~
    src/xkbcomp/ast-build.c:75:21: note: object of size 32 allocated by 'malloc'
       75 |     ExprDef *expr = malloc(size);
          |                     ^~~~~~~~~~~~
    
  • Correct DEFAULT_BLOCK_MAX_SIZE to increase network Capacity

    Correct DEFAULT_BLOCK_MAX_SIZE to increase network Capacity

    The maximum allowed size for a block in /src/consensus.h (protocol rule), excluding witness data, is 1 MB. The default setting for DEFAULT_BLOCK_MAX_SIZE should be 1 MB if we are trying to fully maximize the network.

    Some pools probably patch this on their own anyway. But setting this at 750K might lead to reduced network throughput.

Upbit(업비트) Cryptocurrency Exchange Open API Client of Multi-Programming Language Support
Upbit(업비트) Cryptocurrency Exchange Open API Client of Multi-Programming Language Support

Upbit Client Documents Support Upbit Client Upbit(업비트) Cryptocurrency Exchange API Client Description Upbit(업비트) Cryptocurrency Exchange Open API Clie

Nov 6, 2022
Monero: the secure, private, untraceable cryptocurrency
Monero: the secure, private, untraceable cryptocurrency

Monero: the secure, private, untraceable cryptocurrency

Nov 26, 2022
NanoSwift: A Swift Library for the Nano cryptocurrency

Nano is an instant, feeless and eco-friendly cryptocurrency that is also super easy to use. This library lets you create wallets, accounts and blocks as well as manage Nano amounts, interact with a node and more.

Mar 1, 2022
Simple C++ implementation of a blockchain based cryptocurrency
Simple C++ implementation of a blockchain based cryptocurrency

Welcome to PandaCoin! PandaCoin is a minimalist implementation of a layer 1 cryptocurrency similar to Bitcoin. It is designed with utmost simplicity a

Nov 26, 2022
A basic C++ cryptocurrency/block-chain. Includes a basic wallet system. See README.md for all the inclusions and future additions.

Cryptocurrency Project C++ cryptocurrency/block-chain. Mostly basic blockchain for now. New Additions are in the works(see below). This file details w

Dec 23, 2021
BTCU Wallet is the original Bitcoin Ultimatum client and it builds the backbone of the network.

The concept of BTCU is similar to the concept of the second cryptocurrency by capitalization - Ethereum.

Jul 1, 2022
Bitcoin Core integration/staging tree

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

Dec 1, 2022
A high-performance distributed Bitcoin mining pool server.
A high-performance distributed Bitcoin mining pool server.

Viabtc Mining Server ViaBTC Mining Server is a high-performance distributed Bitcoin mining pool server. We have made a lot of optimizations for Bitcoi

Nov 22, 2022
Bitcoin Point of Sale
Bitcoin Point of Sale

LNPoS Hardware https://shop.pimoroni.com/products/m5stack-faces-kit-pocket-computer-with-keyboard-game-calculator Installation Install Arduino IDE: ht

Nov 20, 2022
Bitcoin and Altcoins Publickey subtracter

keysubtracter Bitcoin and Altcoins Publickey subtracter Generate multiple but different "copies" of a publickey, Actually Added and substracted public

Nov 7, 2022
Bitcoin Core integration/staging tree

Bitcoin Core integration/staging tree https://bitcoincore.org For an immediately usable, binary version of the Bitcoin Core software, see https://bitc

Nov 19, 2022
Brute Force Bitcoin Private keys, Public keys

Rotor-Cuda This is a modified version of KeyHunt v1.7 by kanhavishva. A lot of gratitude to all the developers whose codes has been used here. Feature

Sep 24, 2022
Onix is a decentralized blockchain project built on Bitcoin's UTXO model

What is Onix? Onix is a decentralized blockchain project built on Bitcoin's UTXO model, with support for Ethereum Virtual Machine based smart contract

Dec 16, 2021
mako - full bitcoin implementation in C

mako - full bitcoin implementation in C

Nov 24, 2022
Small collection of tools written in C for ECC and bitcoin

ecctools Small collection of tools written in C for ECC and bitcoin Why this programs are written in C language? Well i like C language because compil

Nov 8, 2022
Open-source, airgapped bitcoin hardware signer for the M5StickV.
Open-source, airgapped bitcoin hardware signer for the M5StickV.

Krux ✝ Krux is an open-source DIY hardware signer for Bitcoin that can sign for multisignature and single-key wallets. It is a low-cost airgapped devi

Nov 19, 2022
FCracker is a command line tool designed to brute force encrypted files like zip, 7z, rar, pdf etc.

FCrack is a command-line tool designed to brute force encrypted files like zip, 7z, rar, pdf, gpg etc.

Oct 3, 2022
A Key Calculation Based Program For Data Confidentiality Over A Steganography-Like Technique
A Key Calculation Based Program For Data Confidentiality Over A Steganography-Like Technique

The Key Calculation Process : The Program Work By Calculating a Decryption Key For The Target File Based On Another File To Reproduce Again The Target

Oct 22, 2022
Dogecoin is a cryptocurrency like Bitcoin
Dogecoin is a cryptocurrency like Bitcoin

Dogecoin is a cryptocurrency like Bitcoin, although it does not use SHA256 as its proof of work (POW). Taking development cues from Tenebrix and Litecoin, Dogecoin currently employs a simplified variant of scrypt.

Nov 29, 2022
This project shows how to interface Nokia 5110 LCD with Esp32 module to show current prices of any cryptocurrency like Bitcoin, Dogecoin, etc
This project shows how to interface Nokia 5110 LCD with Esp32 module to show current prices of any cryptocurrency like Bitcoin, Dogecoin, etc

ESP32 Cryptocurreny Ticker Introduction This project shows how to interface Nokia 5110 LCD with Esp32 module to show current prices of any cryptocurre

Jun 16, 2022