Doge Chain WP
Doge Chain WP
Doge Chain WP
Whitepaper
V1.1
June 2022
Table of Contents
Abstract 3
Introduction 3
1.1 Dogecoin - The Original Meme Coin 3
1.2 The Unfortunate Shortcomings of Dogecoin 4
Introducing Dogechain 4
2.1 Solutions brought by Dogechain 5
2.2 Characteristics of Dogechain 5
2.3 Main Features of Dogechain 6
Background 7
3.1 Cryptographic Hash Functions 7
3.2 Digital Signatures 8
3.3.1 Secp256k1 Curve 8
3.3.2 ECDSA Signature Algorithm 8
3.3 Ethereum Virtual Machine (EVM) 9
3.4 Consensus Protocols 9
3.4.1 Proof-of-Work (PoW) - Nakamoto Consensus 9
3.4.2 Istanbul Byzantine Fault Tolerant (IBFT) 9
3.4.3 IBFT Proof of Authority (PoA) 10
3.4.4 IBFT Proof-of-Stake (PoS) 10
3.4.5 RAFT 11
3.5. Comparison and Selection 11
Dogechain (DC) Architecture 11
4.1 Dogechain Layering Architecture 13
4.2 Dogechain Cross-Chain Protocol 14
4.3 Dogechain Design 15
4.4 Native Currency of Dogechain: the $DC token 15
4.5 Dogechain Configurations 16
VE Model for DogeChain 16
5.1 Voting Power 16
5.2 How to Use $veDC 17
Smart Contracts of Dogechain 17
6.1 Governance Contract 17
6.2 Validator Set Contract 18
6.3 Vault Contract 18
6.4 Staking Contract 18
6.5 Slashing Contract 18
6.6 Bridge Contract 19
Dogechain Staking 19
Potential Applications on top of Dogechain 19
8.1 NFTs 22
8.2 DeFi 22
8.3 GameFi 22
Implementation details 22
References 22
22
Abstract
This whitepaper proposes a full overview of the standalone Dogechain blockchain, its key
concepts, and its core principles. The following text outlines several major pain points common
to the original Dogecoin cryptocurrency and how Dogechain can solve these lingering issues.
The text also details how Dogechain complements the existing Dogecoin ecosystem via its
incorporation of smart contracts. In addition, this whitepaper examines the technicalities of
bridging the Dogecoin blockchain with Dogechain and its capacity for interoperability. It also
introduces the $wDOGE and $DC cryptocurrencies and thoroughly reviews their use cases
within the Dogechain ecosystem. Finally, this whitepaper delves into the project’s tokenomics
and surveys the token’s distribution, vesting periods, and release schedule.
1. Introduction
From a technical standpoint, Dogecoin is a fork of Litecoin, the “silver to Bitcoin’s gold”.
Consequently, Dogecoin is mineable, enabling more than 10,000 new coins to be released into
the market every minute. Moreover, the token supply is not capped as it is with Bitcoin.
The $DOGE cryptocurrency has a single use case - to be accepted as a means of payment for
exchanging goods and services online. Given its growing popularity, it seems to have achieved
this goal quite admirably. People simply love using Dogecoin and participating in the meme
culture that is associated with it. Conclusively, $DOGE has gained mainstream recognition and
adoption.
Having said that, Dogecoin’s age is starting to catch up with it. Its fundamentals have remained
stagnant relative to the multitude of tokens that have evolved with the medium.
Moreover, as a fork of Litecoin, Dogecoin uses the proof-of-work (PoW) Scrypt mining algorithm
for validating transactions and creating new coins. While Scrypt is easier to mine than Bitcoin’s
SHA-256, the PoW architecture remains difficult to scale for mass usage. In its current form,
micro-transactions could easily create the kind of network congestion that would slow it down to
a crawl.
Additionally, crypto mining is considered a notoriously wasteful process for validating blockchain
transactions. A study by Digiconomist revealed that Dogecoin consumes as much as 6.54 TWh,
roughly the energy needs of a small country. Unfortunately, $DOGE’s increasing popularity
promises to increase its carbon footprint even further.
Finally, it’s worth noting that Dogecoin’s PoW protocol presents insurmountable challenges to
implementing smart contracts. A PoW consensus mechanism simply can’t scale to meet mass
demand for millions of simultaneous transactions, even if they merely fuel dApps. Even
Ethereum is migrating to a more scalable PoS mechanism to alleviate this issue. Consequently,
the most viable solution is to implement a complementary blockchain with a PoS token that
prioritizes fast transactions and enables smart contract functionality.
2. Introducing Dogechain
Dogechain is an EVM-compatible blockchain that aims to complement the original Dogecoin
cryptocurrency. As a proof-of-stake blockchain, Dogechain seeks to bring scalability, security,
robustness, and utility to Dogecoin. In short, Dogechain doesn’t compete with Dogecoin.
Instead, it aims to harmonize with the original meme crypto and enhance it with smart contract
capability.
It's important to note that the Dogechain project is a community-first blockchain that aims to
empower Dogecoin holders and enthusiasts. Dogechain will ultimately provide Dogecoin users
with access to blockchain games, NFTs, and the ever-growing DeFi ecosystem, one in which
they can showcase their favorite meme coin for a wide range of applications.
In sum, Dogechain promises to transform the single-usage Dogecoin crypto into a DeFi
powerhouse. With any luck, Dogecoin will be able to readily compete with many of the top smart
contract platforms in the current blockchain environment.
EVM is at the core of the Ethereum blockchain and plays an instrumental role in creating
decentralized applications. In particular, it allows developers to build and deploy solutions and
protocols much more quickly (as opposed to building them from scratch). Indeed,
EVM-compatible protocols incorporate a robust and proven architecture and are thus a
game-changer for DeFi product developers. And in addition to existing protocols, Dogechain will
propose its own smart contracts, thus building upon the extensive DeFi ecosystem.
Bitcoin and other payment-focused / store-of-value blockchains haven’t been able to invoke the
same demand as smart contract-capable platforms. In contrast, Dogechain’s ability to improve
Web3 ecosystem productivity promises to increase blockspace demand. This event will equally
play a part in increasing demand for the native cryptocurrency of Dogechain, the $DC token.
Given Dogechain’s capacity for high throughput and decentralization, token users will not need
to suffer the same user concerns associated with many PoW tokens (including low transactions
per second, public chain congestion, centralized mining, and high transaction fees). Moreover,
Dogechain will conserve a high degree of decentralization due to its PoS architecture.
3. Background
H:{0,1}*→ {0,1}ᵏ
A hash function takes on the input of any size and produces a fixed k length output. In addition,
it must satisfy the following properties:
● It is easy to compute H regardless of input data size.
● Given any h, it is computationally infeasible to find an input x such that H(x) = h.
● Given any x, it is also computationally infeasible to find y such that H(y) = H(x) and x≠ y.
● It is computationally infeasible to find any (x, y) such that H(x) = H(y) and x≠ y.
SHA-256 and Keccak-256 are widely used in several blockchains, and they produce a hash
(output) of 256 bits in size.
3.2 Digital Signatures
Before a user generates a public and private key pair (pk, sk), he/she must first generate a
sufficiently large random number (which is going to be sk) and use it to multiply with the private
key by the generator point G as sk.G (which is going to be the pk).
We use this number to define a point on the secp256k1 curve. Due to the underlying discrete
log problem (DLP), no one can derive the private key from the given public key and the
generator point (as long as the key size is sufficiently large).
Note that for each value of x, the y component is squared in this equation leading to having two
symmetric points across the x-axis. Hence, there are two values of y called odd and even
numbers. Therefore, public keys can be identified by the x-coordinate and the parity of the
y-coordinate. In the blockchain space, this feature is crucial, as it saves significant data storage.
Elliptic Curve Digital Signature Algorithm (ECDSA) is a cryptographic algorithm for creating
digital signatures. More concretely,
Setup
● Public Parameters: Let 𝐹𝑞 be a finite field, two parameters 𝑎 and 𝑏 define an elliptic
255
curve 𝐶 over 𝐹𝑞, a seed which validates 𝐶, a prime integer 𝑛 > 2 , and a point
𝐺∈ 𝐶 of order 𝑛 where 𝑞 is either prime or a power of 2.
● Private Key: An integer 𝑑 in [1, 𝑛 − 1].
● Public Key: 𝑄 = 𝑑𝐺.
The Ethereum Virtual Machine (EVM) is a software platform that developers can use to build
decentralized applications (dApps) on Ethereum. All Ethereum accounts and smart contracts
live in this virtual machine.
The Ethereum virtual machine and EVM codes are designed using memory, bytes, along with
blockchain concepts such as Proof-of-Work (PoW) or Proof-of-Stake (PoS), Merkle tree, and
hash functions. The purpose of the EVM is to determine what the total Ethereum state will be for
each block in the blockchain.
In order to avoid a Sybil attack, PoW is used to force the miners to have and run predefined
computational resources. Additionally, PoW protects the security of the blockchain from the
longest chain attacks. Unfortunately, PoW requires a large amount of energy which keeps
increasing as more miners join the network.
There are four types of messages which are exchanged between the nodes:
● Pre-Prepare, Ready, Commit: Used through ordinary consensus algorithms operations.
● Round robin: Used to select a new block producer when the current producer is
suspected of failing or when the block has not been created within a specific time frame.
Additionally, there are two approaches in the Polygon Edge framework for choosing block
producers:
In these two approaches, every validator knows in advance which one of them is going to be the
next block producer. This is because the decision is made through deterministic calculations
based on node IDs. Similar to PBFT, IBFT also guarantees that there will be only one single
bidder in each round.
Moreover, the bidder is required to get responses from the other nodes in order to continue
executing its further tasks. This means that in the case of a network partition with more than n
nodes (at least more than 3n+1 nodes), the protocol does not make any decisions not to break
the consensus until the partition is fixed and their communication is timely synced. This also
allows immediate finality where no forks are ever allowed to occur.
This means that validators can be included or excluded from a validator group if the majority
(51%) of validator nodes voted to add/remove a particular validator from the set. Thus,
malicious validators can be detected and removed from the network at any point in time, and
new trusted validators can be added to the network.
All validators propose the next block in turn (by means of the round-robin leader selection). For
a block to be validated/added to the blockchain, the overwhelming majority of the validators (i.e.,
more than 2/3) must approve that block. In addition to the validators, there are also
non-validators who do not participate in block generation directly but take part in the block
validation process. IBFT PoA is the default consensus mechanism of the Polygon Edge
framework
This query and saving the cycle are recurring at the end of every epoch period. Fundamentally,
this allows the staking smart contract to have full control over the addresses in the validator
group, leaving only one task to the nodes. Each contract query is executed only once per period
to obtain the latest information about the validator set. This removes the responsibility of dealing
with validator sets from individual nodes.
3.4.5 RAFT
Raft is a distributed consensus mechanism that relies on Paxos. The Raft protocol works with a
node failure model where each error (e.g., missing messages, network partitions, or
hardware-only failure) is considered a node failure.
Hence, it should run n ≥ 2f+1 where f is the maximum number of nodes that can fail and n is the
total number of nodes. The Raft protocol first selects a leader among a set of nodes and then
makes the leader fully responsible for receiving transaction requests and handling the copying
of logs (i.e., blocks) on other nodes.
Each node can be either a candidate, a follower, or a leader. The leader selection procedure is
deterministic, so the protocol cannot run until the leader is selected by more than half of the
nodes.
However, if there is an assumption of only having partial trust in the validators, then it would be
better to utilize IBFT. Since Dogechain is decentralized and permissionless, it is going to
run IBFT as its underlying consensus protocol.
Finally, Polygon Edge uses the IBFT consensus mechanism since it provides for PoA and PoS.
Likewise, the Dogechain EVM blockchain invokes IBFT PoS with built-in system contracts. With
the help of Polygon Edge, Dogechain can employ the following features:
Thanks to the underlying Polygon Edge architecture, Dogechain can achieve full compatibility
with Ethereum smart contract technology. It can also use IBFT PoS to ensure high network
decentralization, security, and scalability.
4.1 Dogechain Layering Architecture
Conversely, when a user destroys a $wDOGE token, he can withdraw a Dogecoin from the
Dogechain chain using a ratio of 1:1. In this context, a cross-chain bridge protocol module will
be utilized to achieve cross-chain transactions.
As shown above, the Dogechain Chain and the Dogecoin chain have a symbiotic relationship. In
particular,
● Users can lock their Dogecoin on the cross-chain protocol to receive $wDOGE on the
Dogechain blockchain.
● Users can use $wDOGE to deploy and interact with smart contracts, pay transaction
fees, and participate in the governance of Dogechain.
● Users can destroy $wDOGE and reclaim their native Dogecoin.
Worth noting is that $veDC is non-transferable and each account can only have a single lock
duration. This means that a single address cannot lock $DC tokens for different time lengths.
For example, a user will be unable to lock one set of $DC for 2 years and then another set of
$DC tokens for 3 years. All $DC per account must have a uniform lock time.
5.2 How to Use $veDC
$veDC tokens cannot be sold or transferred. Instead, they have other use cases, including:
Community-selected validators suggest possible ideas through code updates and written
suggestions. All chosen validators and regular users vote to accept/reject the proposed change.
Under the governance contract, community members democratically vote on proposals that will
advance the development of the blockchain network. To be able to recommend a proposal, the
user must have a sufficient number of $DC token shares.
On the other hand, people with a certain amount of $DC tokens can vote on proposals. There
will also be an option to report management commitments to report misuse of contracts.
The following sample options are subject to change following community feedback:
The IBFT PoS consensus mechanism ensures decentralization and community participation.
$DOGE holders, including validators, can stake their tokens “pegged” to a $wDOGE share.
Dogechain chain slash evidence can be submitted by anyone. It’s worth noting that each
transaction submission demands a slashing proof and is subject to fees. That said, it also
produces a higher reward if it is successful.
● Double-Signing: Let us assume that two different block headers have the same height
and the same parent block hash. If these two block headers are sealed by the same
validator and different signatures are created, then this validator will be punished and
jailed permanently.
● Unavailable: If a validator misses 48 blocks per 24 hours, it will be unable to receive
rewards from the block fees. If a validator misses more than 96 blocks for 24 hours, the
validator will be punished for 10,000 $DC tokens and will be jailed for 3 days. During jail
time, it will still be able to produce or validate blocks.
6.6 Bridge Contract
Stakeholders can call upon the Bridge contract to withdraw their native $DOGE and destroy the
native token of the EVM chain. The protocol will then transfer the redeemed token to the
designated address of the original Dogecoin chain. The minimum reclaim value of the native
token is 100 $DOGE.
When the transaction is synchronized, multiple operators (of the bridging signers) will sign and
confirm the transaction and call upon the bridge contract to write data. After more than half of
the operators confirm (by means of a digitally signing procedure), the native token will be added
to the reclaim address which is specified by the user.
7. Dogechain Staking
The Dogechain project will enable users to access three different token staking models in order
to earn yields:
● Staking $wDOGE tokens on the Dogechain blockchain will allow stakeholders to secure
the native blockchain and receive $DC rewards.
● Staking $DC tokens on the chain will provide additional $DC rewards.
● Staking $DC tokens into the Dogechain Ve model will allow users to receive $veDC
tokens. They can select a vesting time between half a year and 4 years, with longer
vesting periods granting higher $DC rewards and more $veDC in return.
8.1 NFTs
Dogechain will provide its users with the capability to publish their own NFTs following the
ERC721 protocol. Since this proven NFT standard is widely accepted by marketplaces and
metaverses, Dogechain NFT owners will be able to integrate their NFTs into the existing NFT
landscape.
8.2 DeFi
As an EVM-compatible blockchain, DeFi protocols such as Uniswap and SushiSwap can be
seamlessly integrated with Dogechain. $wDOGE and $DC are DeFi-capable cryptocurrencies
that can be locked in various liquidity pools and provide rewards to their holders. Moreover, they
will be able to use them as collateral on decentralized lending platforms, exponentially
increasing the utility of their original Dogecoin.
In addition, several Layer 2 solutions found within the Polygon Edge architecture (including both
ZK Rollups and Optimistic Rollups) will enable Dogechain to make improvements on their
existing transaction speeds in DeFi and address some privacy concerns.
8.3 GameFi
Dogechain will provide developers with the ability to build entire virtual worlds and blockchain
games on the Dogechain smart contract framework. As a result, the $wDOGE and $DC
cryptocurrencies will enable users to participate in virtual gaming economies and share digital
resources in their favorite metaverses.
9. Implementation details
The source codes and further information are available on https://github.com/Dogechain-lab.
10. References
● Marco Mazzoni, Antonio Corradi, Vincenzo Di Nicola. Performance evaluation of
permissioned blockchains for financial applications: The ConsenSys Quorum case study,
Blockchain: Research and Applications, Volume 3, Issue 1, 2022, 100026, ISSN
2096-7209, https://doi.org/10.1016/j.bcra.2021.100026.
● Crypto Energy Consumption.
https://www.moneysupermarket.com/gas-and-electricity/features/crypto-energy-consump
tion/, 2021.
● Bitcoin vs. Ethereum vs. Dogecoin: Top cryptocurrencies compared.
https://www.bankrate.com/investing/bitcoin-vs-dogecoin-vs-ethereum-crypto-comparison/
, Dec 2021.
● First NFT ever minted on Dogecoin Blockchain.
https://twitter.com/inevitable360/status/1470414541490110472/, Dec 2021.
https://blockchair.com/dogecoin/transaction/19aeaa88859c04a333257f1119a77438ac08f
eec424c6ad3645a0679c8be9882, Dec 2021.
● Optimistic Rollups vs ZK Rollups: Examining Six of the Most Exciting Layer 2 Scaling
Projects for Ethereum, https://limechain.tech/blog/optimistic-rollups-vs-zk-rollups/, Aug
2021.
● Dogecoin. https://Dogecoin.com/.
● Ethereum Virtual Machine. https://ethereum.org/en/developers/docs/evm/.
● Jury. https://docs.Dogechain.community/docs/overview
● Polygon Edge. https://github.com/0xPolygon/polygon-edge
https://polygon.technology/solutions/polygon-edge/
● Paxos, Raft, EPaxos: How Has Distributed Consensus Technology Evolved?
https://www.alibabacloud.com/blog/paxos-raft-epaxos-how-has-distributed-consensus-te
chnology-evolved_597127, Jan 2021.
● An Introduction to Binance Smart Chain (BSC),
https://academy.binance.com/en/articles/an-introduction-to-binance-smart-chain-bsc,
Sep 2021.
● Shiba Token, https://shibatoken.com/, 2021.
● The Raft Consensus Algorithm, https://raft.github.io/, 2021.
● Paxos consensus for beginners,
https://medium.com/distributed-knowledge/paxos-consensus-for-beginners-1b8519d336
0f, May 2020.
● Ongaro, J. Ousterhout, In search of an understandable consensus algorithm
Proceedings of the 2014 USENIX Conference; 19–20; Philadelphia, PA, USA, USENIX
Association, pp. 305-320, June 2014.
● Optimistic vs. ZK Rollup: Deep Dive,
https://blog.matter-labs.io/optimistic-vs-zk-rollup-deep-dive-ea141e71e075, Nov 2019.
● Bitcoin Whitepaper.
https://www.ussc.gov/sites/default/files/pdf/training/annual-national-training-seminar/201
8/Emerging_Tech_Bitcoin_Crypto.pdf, Oct 2008.
● M. Castro and B. Liskov, “Practical byzantine fault tolerance,” in Proceedings of the 13th
Symposium on Operating Systems Design and Implementation, vol. 99, 1999, pp.
173–186.
● Polygon Edge. D. Ongaro, J. Ousterhout, In search of an understandable consensus
algorithm, in: Proceedings of the 2014 USENIX Conference; 19–20 Jun 2014;
Philadelphia, PA, USA, USENIX Association, 2014, pp. 305–320. L. Lamport, The
part-time parliament, ACM Trans. Comput. Syst. 16 (2) 133–169, 1998.
● Leslie Lamport. 1998. The part-time parliament. ACM Trans. Comput. Syst. 16, 2,
133–169. DOI: https://doi.org/10.1145/279227.279229, May 1998.