# Welcome to the DigitalNote Wiki DigitalNote is a time tested and battle hardened open source blockchain that offers a fast, secure, and low-fee cryptocurrency, an interoperable DeFi platform, and Peer-to-Peer secure messaging. The XDN Wiki is intended to be your one-stop source for all things DigitalNote. Here you can learn more about the DigitalNote Ecosystem--including the following aspects, and much more: * The core components of DigitalNote Ecosystem * Technologies that power DigitalNote Ecosystem * Staking & Mining * Cryptocurrency: XDN * Chain Tokens: WXDN * Other Chain integration * Wallets Desktop users can navigate the site by using the menu on the left side of your screen while mobile users can tap on the 3 horizontal bars found in the upper-left corner of your screen. # A Brief History A journey that started with CryptoNote based block chain, continues with bitcoin based PoW/PoS hybrid chain, integrating with Binance and Ethereum ecosystems to expand its DeFi offerings. ## **The Past** On May 30, 2014, the very first version of the current DigitalNote was launched and it was called **duckNote (**the term “duck” was chosen because duck is a symbol of freedom and privacy protection). It appeared on the crypto circle with a bang. It was termed as the most “mysterious cryptocurrency” of that time — because it was based on [CryptoNote](https://en.wikipedia.org/wiki/CryptoNote) anonymous technology, like Monero, and was a fork of ByteCoin. It was run by a very strong technology community. ![The specifications of the first version of DigitalNote that was launched on May 30, 2014](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MV2AbiZ7f6Ua6MLmpnT%2F-MV2BMxEV3hbFmtDrCY9%2Fimage.png?alt=media\&token=75aa702d-be25-4e2f-9950-aecc471f7939) DuckNote chain brought smart economy with original supply curve, fair decentralization, brilliantly scaled network specs, user-friendly cross-platform GUI wallet, and lots of other network improvements. It was after four months of its launch, in September 2014, **DuckNote was rebranded as DarkNote**. With the new branding, XDN added new unique features, like encrypted messaging, encrypted transaction comments, GUI wallet transfers aggregation, and many network improvements. DarkNote provided instant worldwide privacy protected transactions and untraceable encrypted messaging transfers with extremely low processing fees in a decentralized peer-to-peer network. Mathematics secured the XDN network (hybrid PoS/PoW) and empowered individuals to control their own finances and information. DarkNote provided the freedom to transact in total privacy. DarkNote was further improved and changed its name to **DigitalNote**. DigitalNote offered merged-mining compatible with Monero and was powered by the CryptoNight7 algorithm. However, mining and exchange were not the only ways of gaining DigitalNote coins. DigitalNote offered a staking option which was performed by locking some amount of funds for a determined period of time. It provided the network with stability and encouraged users to make long-term investments in the project. DigitalNote wallet was available as both console and graphic wallet solution for the users of the cryptocurrency. In Jan 2017, the lead developer of DigitalNote — known as dNote — disappeared leaving the community behind for good. It wasn’t the first time he disappeared (he had done so in the past) but this time never to return. It was very similar to how [Satoshi](https://en.wikipedia.org/wiki/Satoshi_Nakamoto) had left Bitcoin project to make sure it truly stayed a community project. Before he left, he had big plans for DigitalNote — he had said that many institutional investors, banks, insurance companies, pensions, hedge funds, endowments and mutual funds were about to invest in XDN and said that by March 2017 this was to occur. He had referred to his plans as ICCO (Initial Crowdfunded Coin Offering). His disappearance caused the ICCO initiative to fail and many of the long-time XDN fans left after being very disappointed. ## The Turn Around In early 2018, a mix of new and old team members — who appreciated the value of the project by heart — promised to revive the project and make XDN great again. It was the time when XDN hit an all-time high of 646 SATs. The journey was going to be hard — rebuilding the community and keeping the coin alive were the two main objectives. The first part of 2018 was spent fixing the protocol that wasn’t in very good shape. A fork was done in mid-2018 to update the Proof-of-Work algorithm to become consistent with Monero’s algorithm so that users could again dual-mine Monero and DigitalNote together. The fortune did not favor the coin, as it was 51% attacked and timestamp attacked then and again at multiple points throughout the year 2018. The team patched the Proof-of-Work algorithm and was ready to begin feature upgrades, but most of the community members left this project with one of the highest market capital at the time ($600 million at the peak). The team finally acquired talent and leadership in the second half of 2018 and formed a plan for success. At this point **XDN broke the shackles of its stubborn and unreliable CryptoNote technology of the past**, ushering in a new, fairer world with a **total code rebase to include features from Bitcoin and DASH** that would secure the long term future of XDN. DigitalNote XDN’s brand new Proof-Of-Work/Proof-Of-Stake (PoW/PoS) hybrid blockchain was created to improve security and blockchain stability both unifying and expanding possibilities in doing so while bolstering security and protection from a 51% attack. Delegates were incentivized to run Masternodes that helped process and further validate network transactions. The collateral required to operate a masternode was set at 2,000,000 XDN. Not only DigitalNote became a more autonomous system, but it is also became more efficient and effective. The unique selection of block creators allowed transactions to be validated in a matter of seconds. The new code base also introduced a small XDN project fund to help with development and project costs. This contribution became a byproduct of every block that was mined where 50 XDN was added to the fund. It allowed the team to pay for listings, marketing, and anything else that might arise in the future to keep the coin afloat. The big challenge in moving from CryptoNote based chain to Bitcoin core chain was to allow the community to swap the old XDN coins for the new XDN coins. This was not a simple process as the old codebase was flaky and we had no way of telling which addresses were active or even had a balance. Users were given a 6-month window to manually swap their coins. The exchanges like Bittrex were easy to swap while our community had to wait 7 more months as HitBTC swapped their coins to the new blockchain. At the end of the swap, 3,000,000,000 XDN were burnt, leaving a total circulatory supply of just over 5,300,000,000 XDN. The new core team consists of technology leaders, business leaders, marketing professionals, and technology developers, who have worked at many top companies. Together they have about 100 years of experience in Finance & Technology. The new team has brought a high degree of focus and renewed enthusiasm about making XDN one of the top blockchains in the industry. Since the new development team took over, they have totally revamped the DigitalNote XDN blockchain. DigitalNote is probably the only project to have ever successfully migrated from a CryptoNote-based codebase/chain to a Bitcoin-based codebase/chain. Moving to the new chain was a very rigorous and involved process - the team worked very closely with the users and community members, making sure the process to move on the new chain was widely communicated. Our community members helped users 24x7 to migrate to the new chain. That level of commitment from our team to the users was very foundational to the trust we've established with them. ## **The Current** The new DigitalNote blockchain has kept up with the growing needs of the crypto ecosystem. The project has further added a large number of capabilities to make it the most unique project to serve such a wide array of offerings: ### The Fast & Furious Cryptocurrency There aren't many examples when it comes down to a cryptocurrency whose transactions are instant and don't cost anything. XDN transactions are super fast, and each transaction costs only 0.02 XDN (which is $ 0.00004 at the time of writing this). ### Advanced Block Difficulty Retarget System This technology ensures a very tight window around the target block time and shrugs off "51% attacks" without any complaint, no matter how big the scale of the attack is. ### Staking DeFi is emerging as one of the core offerings in the digital assets space. DigitalNote has been a DeFi project much before the term became popular. Every block has 300 XDN staking reward — out of which 150 XDN is rewarded for wallet staking, 100 XDN for masternode staking, and 50 XDN goes to the project fund. #### Staking from QT Wallet Users are able to stake XDN right from their own QT wallet, and without any lock-ins. This is a great way to earn more XDN while helping secure the DigitalNote network. #### Staking with Masternodes Users can run a masternode for as little as 2,000,000 XDN. They not only earn 3-7% APR, but they also help make the overall network stronger by participating in the masternode network. Getting a masternode running takes only a few clicks and takes less than 5 minutes - all available within the Mobile Wallet. ### Peer-to-Peer Secure Messaging DigitalNote supports Secure Messaging right from the wallets. The messages are fully secure, they aren't stored on the network, thus making this capability ideal for securely exchanging messages between the two parties who wouldn't want their messages to be stored anywhere else but securely on their own local devices. ### Deepening DeFi Offerings #### Ethereum Ecosystem Interoperability DigitalNote successfully launched a new ERC-20 token called 2XDN to help leverage a range of features available across the chains. A total of 70 M tokens were distributed as a reward for XDN staking to the existing holders. A total of 70 M XDN was burned to ensure the total supply of tokens did not increase. ![2XDN ERC-20 token allows DigitalNote to interoperate with Ethereum Ecosystem](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MV2AbiZ7f6Ua6MLmpnT%2F-MV2J3bI6yy0sxKBckE2%2Fimage.png?alt=media\&token=ae0a84de-86f4-4e3a-93d0-65ef7b8f65d7) Here is a [video](https://www.youtube.com/watch?v=ruOTWrsSQO8) that explains DigitalNote’s DeFi plans. #### Binance Smart Chain / PancakeSwap integration DigitalNote built the capability to convert XDN to wXDN (wrapped XDN on the Binance Smart Chain), and vice-versa, to open up a universe of opportunities in the Binance/PancakeSwap ecosystem. ![XDN is well connected with the Binance/PancakeSwap ecosystem](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVIG9YHwqnPQ782GWfT%2F-MVIJfPCIlycKaKK2hY9%2FPancakeSwapCountdown.png?alt=media\&token=cec193a3-26d7-40d9-ae47-2cecb022e98f) DigitalNote has expanded it footprint in 2026 from its initial WXDN on BSC, to a new contract across BASE, SOLANA, ETHEREUM, ARBITRUM and POLYGON. ## **The Future** ### **Payments** The DigitalNote team is exploring partnerships that will allow to putting XDN & 2XDN at the forefront of crypto-payment networks and providers. A lot of good work is in progress on this front. ### **Mobile Wallets** Available for iOS and Andriod. QT wallet is very matured right now, and the mobile wallets complement it well in making the project more accessible. ### **Secure Messaging App** Being able to communicate securely has recently emerged one of the biggest areas of concern for the world. Thankfully, DigitalNote has a working system to meet this need (secure messaging is functional today on QT wallet and Web wallet). The project is working on building a mobile user experience to make it easier for users to use it while enriching the features. ### NFTs With our BEP-20 token 2XDN operating in Binance Smart Chain ecosystem, the team is very excited about the potential in the NFT (Non-Fungible Tokens) space and strategizing on how the project can help this line of opportunity that's presented to artists, game enthusiasts, collectors, and many others. ### Emerging Key Players DigitalNote is continuing to keep an eye on emerging key players in the crypto world. Just like the project established interoperability with Ethereum and Binance Smart Chain, the project is constantly analyzing interoperability opportunities with players like Polkadot, Elrond, Solana, Polygon etc. # The Current DigitalNote Ecosystem The DigitalNote Ecosystem comprises of a number of components and integrations. Here is a picture of a number of core components, processes, and integrations that make up the DigitalNote Ecosystem.
# XDN Network and Coin Specs Commonly asked questions about XDN network and coin specifications ## Network | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Codebase | BTC 0.17 | | Mainnet Port | 18092 | | RPC Port | 18094 | | Consensus | POW bmw512(wish) | | Block Time Adjustment | 2 minutes | | Difficulty Adjustment | VRX 3.0 w/Hybridchain swing (3.17min)MAX | | Max Block Size | minimum block size is 1.5MB maximum block size is 15.2MB every 25 blocks the chain calculates an average block size to use for the next 25 blocks set depending on chain utilization. | | Est TPS | Instant | ## Coin | | | | ----------------- | -------------------------- | | Current Supply | \~8,116,279,668 (Dec 2022) | | Maximum Supply | 10,000,000,000 | | Staking Reward | 100 per block | | Masternode Reward | 150 per block | ## Live Network Stats Live data and network statistics can be found here: # Ways to Earn XDN There are several avenues of earning XDN by participating in the XDN ecosystem. 1. Stake XDN right from your [QT Wallet](https://digitalnote.org/#wallets) 2. Run a MasterNode. You can do that on your own server or through the mobile wallet 3. You can [mine](https://digitalnote.org/#1487761188773-74d703cd-aec0) XDN 4. You can contribute to the wXDN/USDT through chain liquidity pools 5. You can earn bounties by taking part in [XDN Bounty program](https://digitalnote.org/#1487263359131-4ff256ce-c7e7) 6. Giveaways are available time to time. We announce them on twitter when they are available. So please follow our [twitter page](https://twitter.com/DigitalNoteXDN) to keep an eye on our announcements for future initiatives. 7. You can always buy XDN on a number of CEXs & DEXs listed [here](https://digitalnote.org/#exchanges) # Exchange Listings XDN is currently listed on a number of CEXs (Centralized Exchanges) and DEXs (Decentralized Exchanges). You can see the complete list [here](https://digitalnote.org/#exchanges). # Masternodes The XDN utility-driven Masternode XDN Masternodes are a fundamental part of the XDN protocol layer and are responsible for processing and validating transactions as well as approving and fulfilling cross-chain protocols. Running a masternode requires a collateral of 2,0000,000 XDN and are rewarded in the following ways: 1. Block rewards -- A percentage of new block rewards are paid to Masternodes by a serialized method which cycles through the list of active nodes. ## How to Setup Your Masternode You can set up an XDN Masternode in 5 minutes with our partners [AllNodes](https://www.allnodes.com/xdn/host) and [Ihostmn](https://ihostmn.com/index.php?ref=bMnD8mZG) There are 2 sides involved to successfully operate Masternodes: ### **Server Side** This is where all of the work is done. You can either setup and maintain your own server using a VPS, or you can pay a hosting provider to keep your node updated and running smoothly for you. Coins are **not stored** on the server side. You can find instructions setting up the server side here: ### **Client Side** This is your supported XDN wallet where your collateral is stored and remains under your full and complete control. Instructions for each individual wallet can be found on the following page: [QT Wallet MN setup](/support/masternode-setup/client-side/qt-wallet) # Benefits of Getting XDN on Other Chains Here are some of the major benefits of getting XDN on the Binance Chain & PancakeSwap 1. XDN will be available on a Decentralized Exchange (DEX). Anyone in the world will be able to buy XDN (as wXDN - the wrapped version of XDN). 2. Expansion of trading pairs - users will be able to swap wXDN directly with many other tokens listed on the BSC, Solana and EVM Chains. 3. Lower fees and faster transactions - compared to many other DEXs - wXDN will be able to leverage this as core offerings from respective Liquidity Pools. 4. Users will be able to **store their wXDN** with other coins **on their choice of wallets** (like Metamask, Trust, & [other wallets](https://docs.binance.org/wallets/bsc-wallets.html)). 5. DigitalNote will be able to further expand its DeFi (Decentralized Finance) offerings in the future by leveraging foundational capabilities like Liquidity Pool Rewards, Staking, Farming, etc. 6. XDN holders will have yet another choice to **earn a passive income** (today they earn by staking in QT wallet or via running an XDN masternode). They will be able to earn by contributing to a wXDN pool. 7. **Reduced dependency on CEXs** - tokens often get adversely affected by exchange or country-specific policies. DEX pools ensure users' ability to trade in the listed token is never affected. 8. By integrating with other chains, XDN already becomes a part of a wider Ecosystem. This helps with the efforts in the direction of listing with DEX & CEX. 9. wXDN will be able to leverage token explorers for high-level insights in real-time. 10. Project awareness and expansion of the community - XDN's presence on the wider tokenized Ecosystem will help spread more awareness about the DigitalNote ecosystem and attract new community members. # Supported Chains & Contract Addresses ## WXDN: Supported Chains & Contract Addresses WXDN is Wrapped DigitalNote — XDN represented as a token on other blockchains, redeemable 1:1 for native XDN at any time via the [DigitalNote Bridge](https://bridge.xdn-explorer.com). > ⚠️ **Always verify contract addresses on this page before adding a token or trading.** Anyone can create a token called "WXDN" — the only official contracts are listed below. ### Official WXDN contracts
ChainToken standardContract addressDecimals
BNB Smart Chain (BSC)BEP-200xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf18
BaseERC-200x75B999F3Df6100A47De7581626c022CBe173a54818
PolygonERC-200x75B999F3Df6100A47De7581626c022CBe173a54818
Arbitrum OneERC-200x75B999F3Df6100A47De7581626c022CBe173a54818
EthereumERC-200x75B999F3Df6100A47De7581626c022CBe173a54818
SolanaSPL67uww5rWac4Du7n6oVEjoAEvJwC6RUdeWkBHE1UrYKEs9
Note that WXDN uses the **same contract address** on Base, Polygon, Arbitrum and Ethereum. The BSC contract is the original WXDN contract and has a different address. The Solana mint address has its own format. ### Explorer links * BSC: [BscScan](https://bscscan.com/token/0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf) * Base: [BaseScan](https://basescan.org/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * Polygon: [PolygonScan](https://polygonscan.com/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * Arbitrum: [Arbiscan](https://arbiscan.io/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * Ethereum: [Etherscan](https://etherscan.io/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * Solana: [Solscan](https://solscan.io/token/67uww5rWac4Du7n6oVEjoAEvJwC6RUdeWkBHE1UrYKEs) ### Which chains does each wallet support? * **DigitalNote QT (desktop) wallet** — native XDN only. Use the bridge to move between XDN and WXDN. * **DigitalNote mobile wallet** — XDN, plus WXDN on **BSC only**. Do not send WXDN from other chains to the mobile wallet. * **MetaMask / other EVM wallets** — WXDN on BSC, Base, Polygon, Arbitrum and Ethereum. See \[Add WXDN to your wallet]. * **Phantom / Solana wallets** — WXDN (SPL) on Solana. # Add WXDN to your wallet ## Add WXDN to your wallet This guide shows how to make WXDN visible in your wallet on each supported chain. Adding a token does not move any funds — it only tells your wallet to display the balance. > ⚠️ Only use the contract addresses from \[Supported Chains & Contract Addresses]. Never trust addresses from chat groups, DMs, or search results. ### EVM chains (MetaMask and compatible wallets) #### 1. Switch to (or add) the network In MetaMask, open the network selector. Recent MetaMask versions include all of these networks built in — just enable them. If you need to add one manually, use [chainlist.org](https://chainlist.org) or these chain IDs: | Network | Chain ID | Native gas coin | | --------------- | -------- | --------------- | | BNB Smart Chain | 56 | BNB | | Base | 8453 | ETH | | Polygon | 137 | POL | | Arbitrum One | 42161 | ETH | | Ethereum | 1 | ETH | #### 2. Import the WXDN token 1. With the right network selected, choose **Import tokens** (Tokens tab → Import tokens). 2. Paste the WXDN contract address for that chain: * BSC: `0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf` * Base / Polygon / Arbitrum / Ethereum: `0x75B999F3Df6100A47De7581626c022CBe173a548` 3. Symbol (WXDN) and decimals (18) fill in automatically. Confirm with **Import**. Your WXDN balance for that chain now shows in the wallet. Repeat per network — the token must be imported on each chain separately. > 💡 Your MetaMask address is the same on every EVM chain, but your WXDN balances are separate per chain. WXDN on Base cannot be sent over the Ethereum network, and so on. To move WXDN between chains, use the [DigitalNote Bridge](https://bridge.xdn-explorer.com). ### Solana (Phantom and compatible wallets) Solana wallets display SPL tokens automatically once you hold them — no import step is needed. To confirm a token is genuine WXDN, check that its mint address is: `67uww5rWac4Du7n6oVEjoAEvJwC6RUdeWkBHE1UrYKEs` (WXDN on Solana uses 9 decimals; this is normal for SPL tokens and does not affect your redemption value.) ### Mobile wallet users The DigitalNote mobile wallet supports WXDN on **BSC only**. WXDN on Base, Polygon, Arbitrum, Ethereum or Solana will not appear in the mobile wallet — keep those balances in MetaMask/Phantom or bridge them. # Bridge XDN ↔ WXDN ## Bridge XDN ↔ WXDN The [DigitalNote Bridge](https://bridge.xdn-explorer.com) converts native XDN to WXDN on your chosen chain and back, always 1:1. > The previous bridge at wrapping.services has been retired. Bookmark **bridge.xdn-explorer.com** (wrap.digitalnote.org takes you to the same place). ### Before you start * **XDN → WXDN:** you need XDN in a wallet you control (QT or mobile wallet recommended — not an exchange \[VERIFY: are exchange withdrawals to bridge deposit addresses supported?]). * **WXDN → XDN:** you need a small amount of the destination chain's gas coin (BNB on BSC, ETH on Base/Arbitrum/Ethereum, POL on Polygon, SOL on Solana) and a native XDN address to receive funds. ### Wrap: XDN → WXDN 1. Open [bridge.xdn-explorer.com](https://bridge.xdn-explorer.com).
1. Select direction XDN → WXDN and choose the destination chain (only visible if > 1 chain enabled). 2. Enter the amount and your destination wallet address. 3. The bridge shows a one-time XDN deposit address. Send **exactly** the stated amount of XDN. 4. Wait for confirmations \[currently 15 XDN]. WXDN arrives at your address on the chosen chain. > ⚠️ Deposit addresses are single-use. Never reuse one for a second transfer. ### Unwrap: WXDN → XDN 1. Open the bridge, select WXDN → XDN and the chain your WXDN is on. 2. Enter the amount and your native XDN receiving address. 3. Send WXDN to the address shown / approve the transaction in your wallet. 4. After confirmations, XDN arrives at your XDN address. ### Fees & limits ### Troubleshooting # WXDN Security & Transparency ## WXDN: Security & Transparency WXDN (Wrapped DigitalNote) is designed to be a transparent, 1:1 wrapped representation of XDN. This page summarises how the token contracts are built and what protections are in place. Always cross-check the official contract addresses on \[Supported Chains & Contract Addresses]. ### How WXDN is backed Every WXDN is redeemable 1:1 for native XDN through the [DigitalNote Bridge](https://bridge.xdn-explorer.com). WXDN is not a separate coin — it is XDN represented on another chain, and wrapping/unwrapping does not change the total XDN supply. ### EVM chains (Ethereum, Base, Polygon, Arbitrum) The WXDN contract is a standard **ERC-20** token built on the widely-used, audited OpenZeppelin v5 libraries, with **18 decimals**. Its source code is **publicly verified** on each chain's block explorer, so anyone can read exactly how it works: * [Ethereum (Etherscan)](https://etherscan.io/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * [Base (BaseScan)](https://basescan.org/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * [Polygon (PolygonScan)](https://polygonscan.com/token/0x75B999F3Df6100A47De7581626c022CBe173a548) * [Arbitrum (Arbiscan)](https://arbiscan.io/token/0x75B999F3Df6100A47De7581626c022CBe173a548) What this means for holders: * **No per-holder freeze.** The contract has no ability to freeze or seize an individual holder's balance. * **Standard, predictable behaviour.** Transfers, approvals and balances follow normal ERC-20 rules, so WXDN works with MetaMask and any standard wallet or DEX. * **You can burn your own tokens**, and the contract supports gasless approvals (EIP-2612 "permit") for smoother interactions with apps that use it. * **Emergency safeguard.** Like many tokens, transfers can be paused in an emergency; under normal operation the token is fully transferable. Before launch, the contract was reviewed and run through an extensive behavioural test suite covering transfers, approvals, burning, ownership handling and edge cases, with no issues identified. ### Solana On Solana, WXDN is an **SPL Token-2022** mint with **9 decimals** (the standard Solana convention; it does not affect redemption value). Its metadata (name, symbol, logo) is stored on-chain. The most important holder protection on Solana: * **Freeze authority is permanently disabled.** No authority can ever freeze or lock your WXDN account — this is a one-way, irreversible setting on the mint. You can verify the Solana token here: [Solscan](https://solscan.io/token/67uww5rWac4Du7n6oVEjoAEvJwC6RUdeWkBHE1UrYKEs). ### Verify it yourself You never have to take our word for any of this. Open the explorer links above, confirm the contract address matches [\[Supported Chains & Contract Addresses\]](/supported-chains), and read the verified source directly. # Setting up XDN on Binance Smart Chain (BSC) This section covers how you can move your XDN to the Binance Smart Chain (BSC) and hold your XDN in your favorite wallet to participate in DeFi opportunities. **Note 1:** you can use any of the [wallets that support Binance Smart Chain](https://docs.binance.org/wallets/bsc-wallets.html). This tutorial will focus on Metamask wallet. **Note 2**: the Binance Smart Chain only works with BEP-20 addresses. Please make sure you use a BEP-20 address (beginning with '0x') NOT BEP-2 address (address beginning with 'bnb') to store or transact wXDN, BUSD, BNB or any other coins on Binance Smart Chain. ## Background **XDN** is now available on Binance Smart Chain - providing the fastest, most-affordable DEX trading experience anywhere in the world, limiting dependence on centralized exchanges. XDN BSC enables a high-performance matching engine, with hundreds of thousands of trades per second, instant execution, and front-running protection. Additionally, XDN BSC will save you money, with settlement costs of just about $0.1 - $0.15 per trade, 100-1000x cheaper than on Ethereum. With XDN BSC, you get to keep your profits, rather than giving them away to miners. Before you proceed, here is what we mean when we say XDN or wXDN: XDN - refers to XDN on the native XDN chain. wXDN - refers to XDN on the Binance Smart Chain (BSC) If you have general curiosity or questions on wXDN / Binance Smart chain, you can refer to following: [FAQ](https://wiki.digitalnote.org/faq-binance-smart-chain-and-pancakeswap-integration) [Benefits](https://wiki.digitalnote.org/benefits-of-getting-xdn-on-binance-chain-and-pancakeswap) ## Install & set up your Metamask wallet Skip this step if you already have a Metamask wallet installed and set up. * You can download a browser extension from following website: * You can follow these steps to get Metamask Wallet set up: **Note**: If you are using Trust wallet, here is a good reference on how to set it up for Binance Smart Chain: ## **Configure your Metamask wallet** Log in to MetaMask Skip this step if you are already logged in. **Step 1:** Log in to your MetaMask Wallet and click on “Expand View” to open in a new tab. In the event you have forgotten your password, you can restore your MetaMask Wallet using the secret backup phrase you should have saved during the account creation. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT6m3DDPZgMoUmBMy08%2F-MT71KLGNX7ROPb5O1iB%2FScreen%20Shot%202021-02-09%20at%201.24.03%20PM.png?alt=media\&token=933100bf-50d4-4475-9d1f-16077c6d5c91) **Step 2:** Click on “Network” to display all available networks and select “Custom RPC” from the available options. ![Click on “Networks” and select “Custom RPC”](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT6m3DDPZgMoUmBMy08%2F-MT7207Piq1w26VA6zJd%2FScreen%20Shot%202021-02-09%20at%201.27.05%20PM.png?alt=media\&token=5b708712-6d5c-44cb-975f-95f0ed8a3e1e) **Step 3:** In the section “New Network” click on “Show Advanced Options” and fill in the following information: * Network Name: Binance Smart Chain * New RPC URL: * Chain ID: 0x38 * Symbol: BNB Block Explorer URL: ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT6m3DDPZgMoUmBMy08%2F-MT73Kqyez71lYP2NUP0%2FScreen%20Shot%202021-02-09%20at%201.32.44%20PM.png?alt=media\&token=6fc292ff-1752-4458-9afc-ed8a33af031d) **Step 4:** Click “Save”. *Binance Smart Chain* Network is now properly set up in your MetaMask Wallet. Make sure to always have selected the *Binance Smart Chain* Network before pursuing the next step. ![Always make sure that the Binance Smart Chain network is selected in order to make this work.](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT6m3DDPZgMoUmBMy08%2F-MT755G0OhURPtoujxKu%2FScreen%20Shot%202021-02-09%20at%201.40.22%20PM.png?alt=media\&token=a73a9ff0-ad1f-4203-9cc6-8eba187fdf50) **Step 5:** Let's add Wrapped XDN token (wXDN) on the Metamask wallet - so that when you move it into the wallet, it shows in your account. This is very important step - else you tokens wouldn't show even if you have them in the account. Follow the screens below to achieve this. * Click "Add Token" at the bottom * Copy and past this value (the wXDN contract on BSC): 0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf * Click "Next" * Click "Add Token" on the next window * Go back to your account by using back arrow - and you should now see WXDN listed there with 0 amount. ![Click "Add Token" to be able to add wXDN to your wallet](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_mMDOUq65NmthaDNc%2FWallet1.png?alt=media\&token=b05f6e82-e407-4fa4-8e53-b672ee1d3799) ![Provide the contract address of wXDN token on Binance Smart Chain](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT6m3DDPZgMoUmBMy08%2F-MT77JxmbVITBVQpIEOl%2FScreen%20Shot%202021-02-09%20at%201.50.15%20PM.png?alt=media\&token=9d1ce826-7c0e-45ea-a244-85d537e0e44d) ![You will now see wXDN listed in your account](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_oMStZt4YqzIg1UDv%2FWallet3.png?alt=media\&token=dd1784db-c2d0-4284-8228-f10c6d92409e) **Step 6:** Copy your wXDN Address by clicking on the account name just before the three dots at the top (the area highlighted in blue in this example). This is going to be **your wXDN address** - which you will use to direct proceedings from your XDN swap. (Please note that it's the same address for that account across networks. So for example, you can use the same address on Ethereum as well as Binance Smart Chain!) ## **Swap your XDN for wXDN** * Go to the swapping service page [here](https://wrapping.services/get/xdn/) * Make sure that you have XDN in "**Swap** F**rom** field" and wXDN in "**Swap** **To** field". If not, then please click on the dual arrow between these two fields to make it that way. * Put the amount of XDN you want to swap (in picture below, you will get 1,000 wXDN for 1,000 XDN) * Provide your wXDN address (copy and paste the account address from **step 6** above. * You can choose "Advanced Options" link to provide your email id - if you want a confirmation of the swap to be sent on your email id. ![Provide the amount of XDN you are swapping and click Swap](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MTa-tLBvgtLCGvCmw0M%2F-MTa7q-JTZmD-Fjvbupp%2FScreen_1_a.png?alt=media\&token=f02f91e1-0384-44e0-a392-14729272e9f0) * Click swap and you will see this window: ![You will need to send the XDN you are swapping to the address presented in the box above](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_rePSCpDIqYREg6wk%2FScreen_3.png?alt=media\&token=4fb439df-6ae3-454c-8cf7-65188d363036) * Now you need to transfer amount of XDN you are swapping (in this case, exactly 1,000) to the XDN address shown in the screen. So go to your XDN wallet, or the exchange, and send XDN to the address presented. The image below is from BITTREX exchange ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MTa-tLBvgtLCGvCmw0M%2F-MTa9gm5gx7XsOeAn0ia%2FScren_4_a.png?alt=media\&token=702d8f10-834f-40b8-bf2e-0b7816809302) * **Caution 1**: While transferring, please add the 0.02 XDN transfer fees so that the address gets exactly 1,000 XDN (in the case above, we transferred 1,000.02 XDN) * **Caution 2:** The address is valid only for that session and changes every time - so please use this address **only** for this transaction - **DO NOT** reuse this address for another transaction) * Once you transfer exactly 1,000 XDN to this address, you will see the following confirmation: ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_t-HLQNsg7E0xOH8C%2FScreen_5.png?alt=media\&token=5a868c42-a5d3-4b8c-a2d1-10a2b993fea6) **Important Note:** After this confirmation, it will take up to 30 minutes for the wXDN coins to show up in your wallet. The reason is - even though XDN chain settles transactions instantly, we want to wait for 10 network confirmations (10 blocks must be processed on the chain) - to ensure 100% security for the conversion transaction. After the required network confirmations are met, you should receive wXDN and you should see in your account as shown here: ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_tMg4u1LuHDwZxPK6%2FWallet4.png?alt=media\&token=ffab7058-6283-49f6-b0c4-e56c9439996d) ## **Swap your wXDN for XDN - this requires a small fee in BNB** **Binance Smart Chain (**BSC) operates in a very similar way to the Ethereum chain, and the same wallet that you use on Ethereum also works on BSC. Transferring wXDN back to XDN will incur a fee in $BNB--good news is that the fee is much smaller than the gas fee one has to pay on the Ethereum chain. So to swap your wXDN for XDN, you will need a small amount of $BNB (Binance's native coin). 1. **Get some BNB** - BNB is the native token of BSC and is used to pay gas fees. See notes at the end of this page on how to get BNB. 2. Go back to the swapping service page [here](https://wrapping.services/get/xdn/) 3. Click the arrow such that you have WXDN in "**Swap** **From"** field and XDN in "**Swap** **To"** field 4. Put the amount of wXDN you want to swap (in picture below, you will get 1,000 XDN for 1,000 wXDN) 5. Provide your XDN address where you want your XDN to be sent. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_tboCPK_NT5fq_AwU%2FScreen1.png?alt=media\&token=9e917c01-6ab7-4533-afa9-d02c9a57f4f4) 6\. Click swap and you will see this window: ![You will need to send the wXDN you are swapping to the address presented in the box above](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_uvCWyYlmAO2-8S-y%2FScreen3.png?alt=media\&token=f5f6f632-673b-4f43-aa5f-df3a4249be2f) 7\. Now you need to transfer amount of wXDN you are swapping (in this case, exactly 1,000) to the XDN address shown in the screen. So go to your Metamask wallet, and send wXDN to the address presented. Follow the screens below to complete this: ![Click on "Send" ](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_w4y6TZbjndRZzp6K%2FScreen4.png?alt=media\&token=9a6ae0cd-a44b-4ec4-a026-9fc205476238) ![Send 1,000 wXDN to the address that was presented. ](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_we8FvrDlo9zR6_pN%2FScreen5.png?alt=media\&token=4d9cf611-bd68-4bd0-8c1a-fdd3e9f404b0) **Note**: If you have been using your wallet for the Ethereum network, it will take the transaction fees by default. So you may have to change it to the "going fees" at the time for BSC network ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_x9_cwp5oAaY7fsu4%2FScreen6.png?alt=media\&token=733efcff-9627-4cab-aebb-41a52b584af0) 8\. You will see a confirmation within few seconds after the transfer ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_xVwygvGI1IDdnoon%2FScreen7.png?alt=media\&token=6983cb94-5158-4921-abd6-5018a6214d6e) **Important Note:** After this confirmation, it will take up to 30 minutes for the XDN coins to show up in your wallet. The reason is - even though XDN chain settles transactions instantly, we want to wait for 10 network confirmations (10 blocks must be processed on the chain) - to ensure 100% security for the conversion transaction. After the required network confirmations are over, you should be able to see your XDN in your wallet or exchange. Your Metamask wallet will reflect the amount of wXDN that has left. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MT_mIqyV4eh0KbDA9h-%2F-MT_xwbfN2dmqFS7z6Gi%2FScreen8.png?alt=media\&token=fc80fbdb-097f-491c-bff5-984c5137df20) Note: You need to buy BNB on the Binance exchange. It is important to note that when you withdraw BNB to your Metamask, it must be sent to the BEP-20 network. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MUB3joufkBz0sufmHxh%2F-MUB5zQRZkAJUiljG15_%2FBinanceWithdraw.PNG?alt=media\&token=d78f3712-1eb4-4ffa-b5da-43cccdc18ffb) # Contributing to wXDN/BUSD Liquidity Pool on PancakeSwap By contributing to wXDN/BUSD Liquidity Pool, you not only earn a part of the trading fees on every transaction, but also earn additional rewards in proportion of your contribution to the pool. ![The wXDN/BUSD PancakeSwap pool allows you to contribute and earn](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVDm2U_ADNG8nAdqcO1%2F-MVDnFJHig3LqlfwY7ZK%2FPancakeSwapCountdown.png?alt=media\&token=8818e3b4-6c0f-4c76-abcd-15b725bc8737) **Note 1:** you can use any of the [wallets that support Binance Smart Chain](https://docs.binance.org/wallets/bsc-wallets.html). This tutorial will focus on Metamask wallet. **Note 2**: the Binance Smart Chain only works with BEP-20 addresses. Please make sure you use a BEP-20 address (beginning with '0x') NOT BEP-2 address (address beginning with 'bnb') to store or transact wXDN, BUSD, BNB or any other coins on Binance Smart Chain. ## Step 1: Get BUSD & wXDN in your wallet In order for you to be able to contribute to the pool, you will need to have both, wXDN and BUSD. If you want to contribute a total of $1000 to the pool, you should have no less than $500 worth of wXDN and 500 BUSD in your wallet. 1.1 If you haven't already connected your wallet with Binance Smart Chain, you can see the instructions to do it [here](https://app.gitbook.com/@xdnenduser/s/xdn-wiki/~/drafts/-MVCYcDvuBYn8fYrmZKe/setting-up-xdn-on-binance-smart-chain-bsc#install-and-set-up-your-metamask-wallet) 1.2 Decide how much you want to contribute to the pool. In this example, we are trying to contribute $1,100 to the pool. So that means we will need $550 worth of wXDN and $550 worth of BUSD (which is 550 BUSD given that BUSD is a Stablecoin pegged to USD). **Note**: both sides should be of the same value in your contribution. So if you were to contribute $2000 to the pool, you will contribute 1000 BUSD and $1000 worth of wXDN. 1.3 Ensure you have the amount you determined to contribute in your wallet (BUSD as well as wXDN). If not, move it to your BSC address on the wallet. If you don't have wXDN, you can follow instructions [here](https://app.gitbook.com/@xdnenduser/s/xdn-wiki/~/drafts/-MVCYcDvuBYn8fYrmZKe/setting-up-xdn-on-binance-smart-chain-bsc#swap-your-xdn-for-wxdn) on how to convert your XDN to wXDN. 1.4 You will need a very small amount of BNB in your account in order to pay for transaction fees on BSC chain. A $1 worth of BNB will be enough for this exercise. We recommend to getting $10 worth of BNB so that it's there to support many future transactions you may do in the future. You can buy BNB on Binance or can also buy BNB with your BUSD on [PancakeSwap](https://exchange.pancakeswap.finance/#/swap) itself as seen in the image below. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD4DFzrQNeWQK_wneG%2FPancakeSwap0.png?alt=media\&token=93193b6b-cab6-4d53-83ef-909b4f5ff221) Once you have both BUSD and wXDN, and a little bit of BNB in your wallet, you are now ready to go to PancakeSwap to connect your wallet. ## Step 2: Connect PancakeSwap to your wallet 2.1 Go to the liquidity page on [PancakeSwap](https://exchange.pancakeswap.finance/#/swap?outputCurrency=0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf) and click on the "Connect" button at the top right corner to connect your wallet. NOTE: Please ensure that you have the "Binance Smart Chain" selected. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVCWzIuN2ljX-dcugIG%2F-MVCZBfKf6PhbwwO8x8W%2FPancakeSwap01.png?alt=media\&token=ab18bad2-9c03-4b62-af92-dde0b8179a75) 2.2 Follow the instructions and you should be able to connect your wallet. Once your wallet is connected, you should be able to see your BSC account address in the top right corner (hidden in the screen below). Click on "Add Liquidity" button and you're ready to contribute to the pool ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVCbNHGTsnMW1i7I36h%2F-MVCcfy31iJSYFzazPtf%2FPancakeSwap02.png?alt=media\&token=1cbd681a-6d60-464d-b214-8ffef8dc3ba5) ## Step 3: Contribute to the wXDN-BUSD pool 3.1 You will be presented with the below screen. Put the amount you would like to contribute to the pool. You need to put either BUSD or wXDN - the other side will get calculated automatically based on the going ratio of the pool at that point (remember, you contribute equally to both sides.) We want to contribute $1,100, therefore, we put 550 BUSD and the PancakeSwap pool automatically calculated the wXDN needed to be 130,384 based on the going rate. **Note 1**: Since your wallet is connected to PancakeSwap, you can see the available quantities of BUSD and wXDN at the top in the boxes marked with red rectangles. **Note 2:** At the bottom, it shows that if your contribution goes through then how much it would be in terms of percentage to the overall pool. Since at the time of this documentation the feature is not open for general use and is open only for the testers and documentation, the total liquidity is small. So this contribution of $1,100 will be making up 48.12% of the pool once successfully done. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVCzFtPftRjjte4jguh%2FPancakeSwap03.png?alt=media\&token=a486c145-c80c-4815-9938-0dd1d3a7ba2e) 3.2 When you connected PancakeSwap to your wallet above, the PancakeSwap only has "view only" access to your wallet. It can only see what's in the wallet. For PancakeSwap to be able to pull the funds in the wXDN-BUSD pool, you will need to approve each move - BUSD and wXDN - simply by clicking each button. You can see this in the two screens below: **Note:** You will need a very small amount of BNB (about $0.25) to be able to do this transaction. Comparing this with fees on Ethereum based exchanges, this is negligible. ![Approving moving required BUSD from your wallet to the Pool](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD0tqyxsjqQjs21hMy%2FPancakeSwap04.png?alt=media\&token=138096c3-d2fa-41e3-9feb-f474ef229959) ![Approving moving required wXDN from your wallet to the Pool](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD1s-PwKusPJAeiuyP%2FPancakeSwap05.png?alt=media\&token=a25a4c7b-2463-478b-aaa9-52a9ee91fc92) 3.3 Now click on "Supply" button - you will see your wallet open. Please hit "confirm" to continue the transaction. This will put your contribution on the pool. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD59yYn6b_zOtJjNgU%2FPancakeSwap06.png?alt=media\&token=be436d84-2776-4792-95e8-3909c83c434e) 3.4 You are done. Your contribution is now in the pool. You are now earning on every trade and any additional rewards that are available for the contributors of the pool. Your contributions to the pool are visible at the bottom. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD5mXh5lzkI2r1h_N5%2FPancakeSwap07.png?alt=media\&token=a45c03b2-8f2f-40d8-abad-faab002911ef) ## Returning back to monitor or change your contribution If you close your screen to come back later to see your pool contribution details again, you will see your pool contribution under "Your Liquidity" (while your wallet is still connected). ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD72-We2yKu3rLFR-p%2FScreen%20Shot%202021-03-07%20at%202.18.09%20PM.png?alt=media\&token=50e9b3e8-bd75-4a41-8f9f-a5050580e75a) Clicking on the "WXDN/BUSD" dropdown will take you to the following screen - using which you can see the details, add more liquidity, or remove full or part of your contribution if you want. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVClFALfACS5kBCenag%2F-MVD7bg35wcHpQ1X9xpa%2FScreen%20Shot%202021-03-07%20at%202.20.39%20PM.png?alt=media\&token=adc94409-54e9-4cc6-8083-daae7a54d746) # Participating in wXDN/BUSD Pool Rewards on PancakeSwap Great opportunity to earn up to 1,000,000 wXDN just by contributing to the pool! ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVD8sRuBAkqR_NCAKh0%2Fimage.png?alt=media\&token=586f85e2-3865-4d63-8230-3230afbd380a) #### **What do you have to do to participate?** It is really easy, first you need to deposit a minimum of US $500 in combined liquidity in the Pancakeswap liquidity pool for wXDN/BUSD by the 17th of March 2021 at 11:59pm GMT. You must keep track on you combined Liquidity to ensure that it does not drop below US $500. You must keep over $500 in the pool for the entire 30-day period ending on 16th April 2021 at 11:59pm GMT to qualify for the share of 1,000,000 wXDN. We will take a snapshot of the pool every day and additional snapshots randomly throughout the liquidity promotion. **Note 1:** Your contribution should be a minimum of $500 at any point between Mar 17, 2021 - Apr 16, 2021 is the period **Note 2:** This is the first reward on the pool. We will be announcing more rewards after success of this one. #### **What will you need to join the wXDN/BUSD Pool?** 1. Your wallet will need to have all the BUSD you are planning to put in the pool. You can buy BUSD on Binance. If you can't locate it, please use this **BUSD BSC contract** to locate it: 0xe9e7cea3dedca5984780bafc599bd69add087d56 2. You will also need to have the equivalent value in wXDN in your wallet to deposit into the pool. * You will need to use to SWAP service to convert your XDN to wXDN. Please refer [here](https://wiki.digitalnote.org/setting-up-xdn-on-binance-smart-chain-bsc#swap-your-xdn-for-wxdn) for a detailed guide on how to do it. (If you don’t already have XDN, you can buy it on one the supported exchanges such as Bittrex, Whitebit or HitBTC). * You can also buy wXDN directly on PancakeSwap. Please refer Please refer [here](https://wiki.digitalnote.org/trade-wxdn-with-other-coins) for a detailed guide on how to do it. 3. You will need to then contribute to the wXDN/BUSD pool. You can see the instructions [here](https://wiki.digitalnote.org/contributing-to-wxdn-busd-liquidity-pool-on-pancakeswap) on how to contribute. #### **How exactly will I contribute to the wXDN/BUSD Pool?** You can follow detailed instructions [here](https://wiki.digitalnote.org/contributing-to-wxdn-busd-liquidity-pool-on-pancakeswap). #### **How much do I need to qualify for the Pooling rewards?** You will need a minimum of US $500 in combined liquidity between wXDN and BUSD. Let’s say if your combined pool contribution is US $600, you will add US $300 of BUSD and US $300 worth of wXDN. You will need to keep an eye on your contribution to ensure that it remains in balance as the price rises or falls. We recommend place more than the minimum in the pool to avoid you from dropping below the threshold. Fortunately, we are using BUSD which is a stable coin to minimize [impermanent loss](https://academy.binance.com/en/articles/impermanent-loss-explained). Remember that the impermanent loss may decrease the amount of liquidity you have in the pool - so it is wise to have more than the minimum of US $500 to ensure that you qualify (as in the example above, the pool contribution is $600, a little bit higher than the minimum required). #### **Is there a maximum limit?** There is no upper limit to your contribution at this time. #### **How much will I earn?** Each qualifying address will receive an equal share of the 1,000,000 wXDN pool for the period of the promotion. So for example, if you contributed $1000 during this time, and the average value of overall pool was $100,000 during this time, you will receive 1% of 1,000,000 wXDN – that is, 10,000 xXDN. #### How will I know when are the snapshots are taken? We will not disclose the exact date or time of the snapshots to prevent abuse. #### Do I have to keep my investment in the pool for the snapshots for the entire month? That’s right. You need to ensure that your account in the pool maintains the minimum threshold of $500 for the period of the liquidity pool promotion. # Trade wXDN with other coins You can now trade wXDN with any other coins on PancakeSwap. #### 1. Connect your wallet to PancakeSwap If you aren't aware how to connect your wallet, you can see the instructions [here](https://wiki.digitalnote.org/contributing-to-wxdn-busd-liquidity-pool-on-pancakeswap#step-2-connect-pancakeswap-to-your-wallet) #### 2. Go to PancakeSwap's [exchange page](https://exchange.pancakeswap.finance/#/swap?outputCurrency=0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf) ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVDBe7xVjhyV9aiV4QE%2FTrade.png?alt=media\&token=7830ccb5-f450-4737-a30f-d1433da41d79) #### 3. Select the pair you want to trade Choose the token you want to buy by selecting from the "To" list. If you don't see the token in the default list, please get the BSC contract address of the token to find it. In the "From" list, provide the coin or token you want to spend (sell). ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVDCH1NvOAvAdvqtXrY%2FTrade2.png?alt=media\&token=5cfcbdb1-e6d7-4fee-a018-347decd56b18) In this case, we will be buying wXDN with BNB. So this is how the screens looks like: ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVDD91IocLLqVNIxId7%2FScreen%20Shot%202021-03-07%20at%202.44.49%20PM.png?alt=media\&token=b5b4c983-eadf-415f-b2ef-54407a45e643) ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVDDRWBzdN8rcHKoOpf%2FTrade3.png?alt=media\&token=eaf65467-9504-4955-b266-fd1c84157c55) ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVD7o-HD_kY6_VFrEaR%2F-MVDDYUZFHX9oDi9_UHL%2FScreen%20Shot%202021-03-07%20at%202.46.34%20PM.png?alt=media\&token=9725fb36-44b0-4763-b0f6-e48169c7a365) Click on "Confirm" button and you get your wXDN in the wallet. # Swap BEP-2 for BEP-20 BNB Asset Step by step guide to swap BEP2 "Binance Chain Network" asset to BEP20 "Binance Smart Chain Network" ## How to use the Binance Chain to Binance Smart Chain Bridge Some Exchanges (Coinspot, HitBTC, etc) trade BNB on the "Binance Chain Network". You will notice that the addresses on the Binance Chain Network will start with "***bnb***". These tokens will not be able to be transferred directly to wallets like Metamask or TrustWallet without doing a conversion to the Binance Smart Chain. This page will cover the conversion process using the **Binance Chrome Extension**. **Please Note:** If you have an account on the Binance Exchange, then you can send your BNB coins there to convert. ### Part 1: Download and Install Binance Chain Chrome Extension 1. Go to [this address](https://chrome.google.com/webstore/detail/binance-chain-wallet/fhbohimaelbohpjbbldcngcnapndodjp?hl=en) in your Google Chrome or other compatible web browser #### Install Extension * Click “Add to” to add to your browser’s extensions, then read the warning in the notification box and if you agree, click “Add extension”. #### Accessing Extension * The Binance Chain Wallet chrome extension is now accessible from the top of your browser whenever you may need it. You may choose to ‘pin’ it to the top bar by clicking the jigsaw piece icon and clicking the pin icon next to the extension. ![Extension is located in the top bar to the right](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPfOgBPbY0s-M0Y-O-%2Fimage.png?alt=media\&token=713063e7-29cd-4213-80d2-73e9c567b05c) #### Create and Secure Wallet You may now choose to import an existing wallet or create a new one. For the purpose of this guide; we will be creating a new wallet, as we are only using this extension to bridge between BEP2 and BEP20. It will not be our main wallet, we will transfer our BEP20 token to our Metamask wallet as the final step * Create your wallet and select a strong password. ![Create wallet and input a strong password](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPg93dZ6zWLp3QVdqt%2Fimage.png?alt=media\&token=04a4ef28-26de-4125-9286-9d30dbf8214e) * Save your Mnemonic Phrase. This step is very important especially if you will be re-using this wallet/extension. If you do not properly backup this set of 12 words, you will have no way of recovering your wallet in the event of losing access to it! * Press Continue to proceed to phrase verification * Confirm your Mnemonic ![Backup your 12 word phrase and confirm 3 words on the next screen](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPh8hVt1IToRFMQTUH%2Fimage.png?alt=media\&token=d252951d-230f-402d-bc6c-6361313003ef) * Congratulations — your BC Wallet chrome extension is now ready to act as a bridge for your BEP2 and BEP20 assets. ### Part 2 Swapping BEP-2 to BEP-20 Now you will need to send your BEP2 asset to your new wallet from whatever exchange/wallet you have them on. #### Sending your BEP2 to Binance Chain Extension Wallet * Open up your Binance Chain chrome extension and ensure **“Binance Chain Network”** is selected. * Click on receive and copy your address. ![Copy your Binance Chain extension wallet address](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPhypL18YlgatoOHcM%2Fimage.png?alt=media\&token=77912391-6827-4f14-bf4d-8c0a767fe59e) * Paste your receiving address into the “To Address” of your exchange/wallet that you want to send your BEP2 assets from. * Confirm the details and send the transaction. * The BNB asset will soon arrive in your BC Chrome Extension wallet. #### Swapping your BEP2 to BEP20 * Swap the network to **“Binance Smart Chain”** on your BC Extension (near the top of the extension). * Click on “Receive” and copy your BSC address. ![Copy your BSC address; note the network change circled up the top](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPj8wBEnBJCgl-Xdyv%2Fimage.png?alt=media\&token=3a04f4ae-3978-4da8-827c-f390eaeadaf5) * Swap the network back to **“Binance Chain Network”** and click on **“Send”**. Select the BEP2 asset you would like to send. * Paste the BSC address that you copied above into the address field “Address” field. * A Note under the Address field will show that you are performing a cross chain transfer ![Cross Chain Transfer](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MVPbFTOnqDePBB5--i-%2F-MVPjjAv_l1bAa7pfpPL%2Fimage.png?alt=media\&token=521dce44-4d62-46ab-98a8-b7b3db4ffd41) * Enter the amount, confirm details and press “Send” * Swap back to **“Binance Smart Chain”** network and confirm the funds have arrived. * Finally you can now send your BSC BEP20 asset into your Metamask or Trustwallet as per normal. # FAQ: Binance Smart Chain & PancakeSwap Integration Here you can see answers to the frequently asked questions about wXDN/XDN, Binance Smart Chain, PancakeSwap. ## wXDN vs XDN **Is XDN going away?** No. XDN is the native coin of DigitalNote ecosystem and is core to the DigitalNote strategy. **Is wXDN a new coin being introduced?** No. wXDN is the same coin as XDN. To make it simple: wXDN is XDN on the Binance Smart Chain. **What is the contract address of wXDN on Binance Smart Chain?** wXDN's contract address is: 0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf **Will wXDN have a separate explorer than XDN explorer to view the wXDN activity?** Yes. wXDN is on the standard BscScan explorer. You can see the wXDN on BscScan [here](https://bscscan.com/token/0xbea2576f400b070c7cdf11d1cbb49de0c84e3). **Is the total supply of wXDN+XDN going to be more than total supply of XDN?** No. The total supply stays the same as the total supply of XDN. When you convert XDN to wXDN, your XDN is locked and no one will have access to it until you convert back from wXDN to XDN (you don't have to.) If you choose to convert wXDN to XDN, the amount of wXDN you are converting is burnt and an equal amount of XDN is unlocked and transferred to you. **Why do I see a big pool of wXDN on BSC scan?** DigitalNote has two options in terms of XDN->wXDN conversion: 1) to share the private key with the conversion service provider so that they can generate wXDN on the fly as users convert 2) Not share the private key with the conversion service provider and keep a mempool of 1B wXDN so that the users can still convert in realtime. In the best interest of the community and the project, we chose option two to ensure full security. So in other words, we will keep a mempool of up to 1B wXDN, and users convert their XDN to wXDN, the wXDN will be taken from the mempool. The mempool process will make sure that at no point there is any additional supply in the ecosystem than the total XDN supply. ## Binance Smart Chain Integration #### What is Binance Smart Chain? Binance Smart Chain brings cross-chain interoperability to the Binance ecosystem. It is an Ethereum EVM 100% compatible blockchain, and is very good at decentralized application (Dapp) development within many possible verticals including DeFi, NFT, Gaming, and many others. You can read more [here](https://docs.binance.org/smart-chain/guides/bsc-intro.html). #### Is Binance Smart Chain same as Binance Chain? No. However, it's one of the core components in the Binance ecosystem. You can read [here](https://www.binance.org/en/smartChain) how Binance Smart Chain and Binance Chain are complementary to each other in their [dual-chain architecture](https://www.binance.org/en). #### Why do we have to get XDN on Binance Smart Chain? You can read about the benefits [here](https://wiki.digitalnote.org/benefits-of-getting-xdn-on-binance-chain-and-pancakeswap) #### Will I lose ability to have my XDN back on exchanges? No. You will be able to convert your wXDN to XDN at any time at 1:1 basis. **Should I move my XDN to Binance Smart Chain?** The choice is totally yours. The bridge to Binance opens up a universe of opportunities for XDN. You may decide to: * Move to BSC to leverage pool contribution, or trade with other coins * Keep your XDN on the QT wallet to be able to stake it * Keep your XDN to run a Masternode to earn and contribute to the network security * Keep your XDN on centralized exchanges * Keep your XDN as a mix of some or all of above #### Why is there a fees on converting wXDN to XDN - while there is no fees on converting XDN to wXDN? There is minimal fees required by Binance Smart Chain when you convert wXDN to XDN - that's because this transaction happens on the Binance Smart Chain and requires BNB gas fees. On the other hand, XDN to wXDN conversion happens off the Binance chain, and the resulting tokens are deposited in your wallet's BEP20 address. ## PancakeSwap Integration #### What is PancakeSwap? PancakeSwap is a decentralized exchange that runs on Binance Smart Chain. You can read more about it [here](https://docs.pancakeswap.finance/). #### Why do we have to get XDN on PancakeSwap? You can read about the benefits [here](https://wiki.digitalnote.org/benefits-of-getting-xdn-on-binance-chain-and-pancakeswap) #### Will I be able to buy wXDN on PancakeSwap? Yes. In fact you can use your other tokens, not just BUSD, to buy wXDN. You can see the details [here](https://wiki.digitalnote.org/trade-wxdn-with-other-coins) on how to trade wXDN on the PancakeSwap. This is a direct link to the trading pair for [wXDN](https://exchange.pancakeswap.finance/#/swap?outputCurrency=0xbea2576f400b070c7cdf11d1cbb49de0c84e3bcf) on PancakeSwap # Wallets Current Release: https\://github.com/DigitalNoteXDN/DigitalNote-2/releases/tag/v2.0.0.8 ## Current Wallet Versions Current Release: * `DigitalNote-qt-2.0.0.8-win-x64.exe` (Windows 10+, x64) * `DigitalNote-qt-2.0.0.8-linux-x64` (Ubuntu 24.04+ / Debian 13+ / glibc 2.39+) * `DigitalNote-qt-2.0.0.8-linux-x64-compat` (Ubuntu 20.04+ / Debian 11+ / RHEL 9+ / glibc 2.31+) * `DigitalNote-qt-2.0.0.8-linux-arm64` (Ubuntu 22.04+ / Debian 12+ / glibc 2.35+, aarch64) * `DigitalNote-qt-2.0.0.8-macos-x64.dmg` (macOS 12 Monterey+, Intel) * `DigitalNote-qt-2.0.0.8-macos-arm64.dmg` (macOS 12 Monterey+, Apple Silicon) * `DigitalNoted-2.0.0.8-win-x64.exe` (Windows 10+, x64) * `DigitalNoted-2.0.0.8-linux-x64` (Ubuntu 24.04+ / Debian 13+ / glibc 2.39+) * `DigitalNoted-2.0.0.8-linux-x64-compat` (Ubuntu 20.04+ / Debian 11+ / RHEL 9+ / glibc 2.31+) * `DigitalNoted-2.0.0.8-linux-arm64` (Ubuntu 22.04+ / Debian 12+ / glibc 2.35+, aarch64) **Bootstrap File - Downloadable Blockchain** [WINDOWS BOOTSTRAP FILE ](https://github.com/DigitalNoteXDN/DigitalNote-2/releases/download/v2.0.0.8/bootstrap.tar.gz) # QT Wallet Using the QT wallet The XDN QT wallet is the one most cryptocurrency users have seen before. It offers a clean interface with a focus on full and complete functionality rather than design. ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRi-vu4Q_iEP6fitNb%2F-MGRlnon-aKYCwyisuiz%2FxdnQTwallet1.jpg?alt=media\&token=8a28aaf1-bc32-410c-b92f-53d3685a3c88) {% content-ref url="/pages/-MGQ599tVbiQ-yQxLxSq" %} [Installation and Updating](/wallet-functionality/qt-wallet/installation-and-updating) {% endcontent-ref %} {% content-ref url="/pages/-MGQ5Ok2yvD0rMXW4pF0" %} [Backup and Security](/wallet-functionality/qt-wallet/backup-and-security) {% endcontent-ref %} {% content-ref url="/pages/-MGQPokYOyiKwxxHkxQF" %} [Staking](/wallet-functionality/qt-wallet/staking) {% endcontent-ref %} {% content-ref url="/pages/-MGPssbNxkuKmG7Whu24" %} [Masternodes](/getting-started/masternodes) {% endcontent-ref %} {% content-ref url="/pages/-MGQU91V2BcmejGdsqQI" %} [Advanced Wallet Functions](/wallet-functionality/qt-wallet/advanced-wallet-functions) {% endcontent-ref %} # Installation and Updating QT wallet installation Download the latest release for your specific Operating System via the [XDN website](https://digitalnote.org/#wallets) or direct from [GitHub](https://github.com/DigitalNoteXDN/DigitalNote-2/releases/). For MacOS and Windows, simply click on the .exe/.dmg file to begin installation. For all others, unpack the .tar.gz or .zip file and copy the binary/executable files to the appropriate location to install for all users, or simply execute them from where ever you unpacked them if no other users need access. ## Releases ### Windows #### **DigitalNote-qt.win64.exe**
For Windows 64-bit architectures. This release includes an installer and is most likely the release you want to download if you are a Windows user. ### Mac #### **DigitalNote-Qt.dmg**
For OS X. This release includes an installer and is most likely the release you want to download if you are a Windows user. ### Linux #### **DigitalNote-qt.linux.x86-64** For Linux 64-bit architectures. Binary files are found in the /bin directory. ### Source Code If you wish to compile the binary/executable files yourself, the source code is available in .zip and .tar.gz compressed file formats. Note that you will also need to have all required and optional dependencies already installed in order to successfully compile from source code. # Backup and Security How to backup and secure your QT wallet {% content-ref url="/pages/-MGQ61o\_3xPr-0Kf8jg2" %} [Wallet Encryption](/wallet-functionality/qt-wallet/backup-and-security/wallet-encryption) {% endcontent-ref %} {% content-ref url="/pages/-MGQ63ShNNpPspvaOm2G" %} [Wallet Backup](/wallet-functionality/qt-wallet/backup-and-security/wallet-backup) {% endcontent-ref %} {% content-ref url="/pages/-MGQ64E\_YyALOqBs3cAT" %} [Wallet Restoration](/wallet-functionality/qt-wallet/backup-and-security/wallet-restoration) {% endcontent-ref %} # Wallet Encryption How to encrypt your QT wallet Encrypting your wallet.dat file will require that you enter a password in order to send any XDN. It is also a requirement if you wish to stake your XDN directly from your own wallet. Although you can perform this action at any time, it is recommended that you do it immediately upon starting a new xdn-qt wallet and before generating/using any receive addresses. Encrypting your wallet.dat file also changes your master seed, so any backups you created before encryption **WILL NOT** backup addresses you've created/generated after encryption. From the Settings menu, select "Encrypt Wallet..." to begin the process of encrypting your wallet.dat file. ![Select "Encrypt Wallet..." from the Settings menu](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRpBzEvq_i6ltxONtT%2F-MGRr-zzfpX6_Z7Jl-uP%2FxdnQTwalletEncrypt.jpg?alt=media\&token=265fafc0-20a8-4e5c-a414-b290616fcd73) ![Choose a very strong passphrase](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRpBzEvq_i6ltxONtT%2F-MGRrmnmqqMVmElv1UDp%2FxdnQTwalletEncrypt1.jpg?alt=media\&token=086b9b24-7240-4cf3-8b4a-9c297ebd06b5) ![Confirm that you wish to encrypt your wallet](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRpBzEvq_i6ltxONtT%2F-MGRs9byRTQM3DitU6k8%2FxdnQTwalletEncrypt2.jpg?alt=media\&token=2fa2cb7b-05d6-4afd-92f0-10264c042dc7) {% hint style="info" %} **NOTE:** After confirming you wish to encrypt your wallet, it may take a few moments to apply the encryption. {% endhint %} ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRsg3lH6CA4AeJLpXm%2F-MGRtjHS3J3tSdm5bGNL%2FxdnQTwalletEncrypt3.jpg?alt=media\&token=7d01a996-259a-4230-999c-e22e615a4fbc) Clicking OK on the final dialog box will close the wallet. The next time you open it you will be required to use your passphrase in order to send or stake your XDN, so do not lose it! ## Changing the QT Wallet passphrase Once your wallet is encrypted, you can later change the passphrase if you wish. From the Settings menu, select "Change Passphrase..." Make sure to replace your old wallet backups with the new one. ![Select "Change Passphrase..." from the Settings menu](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRtvirch4_CXuX-WYD%2F-MGRuqb1S9N_cbVCCkpS%2FxdnQTwalletChangePassphrase.jpg?alt=media\&token=9083301c-894c-44d2-af5d-492322a0a1b7) ![Fill in your current passphrase and choose a new one](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRtvirch4_CXuX-WYD%2F-MGRuw71V0vZAZ8GIS0q%2FxdnQTwalletChangePassphrase1.jpg?alt=media\&token=4df2e822-f2c7-4547-a883-0482639cbdbc) # Wallet Backup How to backup your QT wallet For the QT wallets, the file wallet.dat contains your private keys which grants access to your coins on the blockchain. If this file becomes corrupted or lost you will no longer be able to access your coins without restoring a valid backup. It is best to store your backed up wallet.dat somewhere other than the computer you normally use to run your wallet. SD cards, thumb drives and cloud backups are ideal candidates. Encrypting your wallet.dat before backing it up is strongly recommended. ## Backup Frequency Because all XDN wallets utilize HD key generation, you do not need to backup your wallet after generating 100 or 1000 receive addresses. All receive addresses you generate are based off of a single master private key which will grant you access to all future generated addresses. When encrypting your wallet.dat file, a new master key is generated and used from then on. This prevents anybody who may gain access to your previously unencrypted wallet.dat file from gaining control of addresses you've generated after encryption. Because of this, encrypting your wallet will require you to create a new backup of your wallet.dat. You should also delete any previously created backups that are not encrypted. {% hint style="warning" %} **NOTICE:** Changing your password will not require a new backup, but any old backups will still use their respective password. Therefore, it is strongly recommended that you replace any previous wallet.dat backups. {% endhint %} {% hint style="success" %} **TIP:** A sure way to protect any coins still on an old receive address that you've generated before encrypting your wallet is to send them to yourself using a newly generated receive address after encryption. {% endhint %} ## Core Wallet Backup You can backup your wallet.dat file from within the running xdn-qt application by selecting "Backup Wallet..." from the File menu. You will then be presented with a standard "Save file as" window where you can select a location and name for your backup file. ![Select "Backup Wallet..." from the File menu](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRv5yLTX0nMAHItoyH%2F-MGRvsew9J-zOgH_njZ3%2FxdnQTwalletBackup.jpg?alt=media\&token=30eb644c-3ea8-4660-9abd-f42eaa42b58f) ## Manual Wallet Backup You can manually copy your wallet.dat file to a new location by navigating to the XDN data directory and making a copy of the wallet.dat. The default location for this file is inside the wallets directory if it exists, otherwise, the root data directory (xdn). ### Windows {% hint style="success" %} **TIP:** Windows hides the AppData folder by default when using the graphical file explorer. In order to get inside the AppData folder, you can either type "%AppData%" into the search bar or check the box for "Hidden items" under the View menu to show hidden files in the file explorer window and navigate your way there. {% endhint %} C:\Users\\(your username)\AppData\roaming\xdn\wallets\wallet.dat or C:\Users\\(your username)\AppData\roaming\xdn\wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} ### MacOS {% hint style="success" %} **TIP:** MacOS hides the Application Support folder by default.\ 1\. On the top bar, left side of your screen click on "Go", then click on "Go to Folder".\ 2\. Type or copy-paste: \~/Library/Application Support/xdn/ {% endhint %} \~/Library/Application Support/xdn/wallets/wallet.dat or \~/Library/Application Support/xdn/wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} ### Linux \~/.xdn/wallets/wallet.dat or \~/.xdn/wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} # Wallet Restoration How to restore your QT wallet.dat file The method of restoring a Core wallet.dat file is essentially the reverse of manually backing it up. Default locations for each Operating System can be found below. ## Windows By default, the XDN data directory will be created as C:\Users\\(your username)\AppData\roaming\xdn\\ {% hint style="success" %} **TIP:** Windows hides the AppData folder by default when using the graphical file explorer. In order to get inside the AppData folder, you can either type "%AppData%" into the search bar or check the box for "Hidden items" under the View menu to show hidden files in the file explorer window and navigate your way there. {% endhint %} To restore a backed up wallet.dat file, simply copy it into the following location: C:\Users\\(your username)\AppData\roaming\xdn\wallets\wallet.dat or C:\Users\\(your username)\AppData\roaming\xdn\wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} ## MacOS Be default, the XDN data directory will be created as \~/Library/Application Support/xdn/ {% hint style="success" %} **TIP:** MacOS hides the Application Support folder by default. 1. On the top bar, left side of your screen click on "Go", then click on "Go to Folder". 2. Type or copy-paste: \~/Library/Application Support/xdn/ {% endhint %} To restore a backed up wallet.dat file, simply copy it into the following location: \~/Library/Application Support/xdn/wallets/wallet.dat or \~/Library/Application Support/xdn/wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} ## Linux By default, the XDN data directory will be created as \~/.xdn/ To restore a backed up wallet.dat file, simply copy it into the following location: \~/.xdn/wallets/wallet.dat or \~/.xdn/wallet.dat {% hint style="info" %} **NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used. {% endhint %} # Staking How to stake XDN with the QT wallet The XDN QT Wallet allows users to stake their holdings directly without ever giving up control of your funds. To find out potential staking rewards please check this calculator whch wil give you an estimate of what to expect. Yoi can tehn compare if it it better for you to run a Masternode or to Stake It is avisable to encrypt your wallet with a passphrase. If you do not encrypt your wallet, your coins will automataically stake as long as they are not reserved and the wallet remian online. (\\
and then check Reserve) If your wallet is encrypted, simply select "Unlock Wallet..." from the Settings menu. You will then be prompted to enter your wallet passphrase. ![Select "Unlock Wallet..." from the Settings Menu](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRvyXxRtQcu-gitzoD%2F-MGRwv7DxtKfShe87BIE%2FxdnQTwalletUnlock.jpg?alt=media\&token=459d012b-3e70-4f82-b753-bc23bc6fa408) ![check "For staking only" box and enter your passphrase](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGRygTeMrugLe7MGL6A%2F-MGS0Vfj-snyW0n79l-Q%2FxdnQTwalletUnlockStaking1.jpg?alt=media\&token=9fb1e9a1-f9df-4479-9edd-11052a432cd5) ![Staking is enabled](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGWJp_ycczW-Qp0dXHW%2F-MGWLXvYS1hGI1CQHHse%2FxdnQTwalletStaking1.jpg?alt=media\&token=08d19fa3-1bed-4229-b7ec-32e56078a497) {% hint style="warning" %} **IMPORTANT:** You must leave your wallet open and "unlocked for staking" in order to actively stake your coins! {% endhint %} # Advanced Wallet Functions Using advanced features of the QT wallet The QT wallet allows users complete control over all aspects of the network via a console in addition to some easy to use graphical features such as Coin Control. # Coin Control How to send from selected inputs Coin control is an advanced QT Wallet feature primarily used for selecting individual UTXO's (unspent transaction outputs) to be used when sending your coins. Additionally, you can also use coin control to specify a custom change address. ## Enabling Coin Control In order to enable coin control features, you must first navigate to the Options window under the Settings menu. ![Select "Options..." from the Settings menu](broken://files/-LnpbaUJLCafIcktRo5y) From the Options window, select the "Wallet" tab and check the box for "Enable coin control features". ![Check the box for "Enable coin control features"](broken://files/-Lnpd8CWWVnuyat1cah2) Now when you use the "Send" window, you'll notice a new row labeled "Coin Control Features" at the top.. ![QT Wallet Coin Control Features](broken://files/-LnpeWBADlm1DDS6zanx) ## Coin Selection Window By default, inputs are automatically selected whenever you want to send coins. This automatic selection will use the fewest number of available inputs to complete your transaction. You can change this behavior by clicking on the "Inputs..." button, which will take you to the Coin Selection window. You can view your inputs using either a Tree or List mode. ### Tree Mode Tree mode will combine all UTXO's that use the same address in order to save some space. You can expand the tree by clicking on the > before each checkbox. ![Coin Selection Tree View](broken://files/-LnpnECRNVKomejvmr-1) ### List Mode List mode will show each individual UTXO separately. ![Coin Selection List View](broken://files/-LnpnMwyuGpK_nMPX8y-) ## Using Coin Control In following example we are going to use Tree mode to select everything except a legacy address which begins with "G". ![Select the UTXO's you want to use](broken://files/-LnpjcX-8TxTVAuEbXRm) After clicking the OK button, you'll be brought back to the Send window. Now, fill in your send address and click the "Use available balance" button to use all the coins you've selected. You can also use a lesser amount if you'd like. ![Click the "Use available balance" Button to use the entire amount of selected UTXO's](broken://files/-Lnps8MgV3nLT9vIAu6F) Now that you've entered in an address and amount to send, just click the send button. ![Click the "Send" button to send your selected coins](broken://files/-Lnpu5cTtT4POvjCyfC2) ### Copying coin amounts for use elsewhere After selecting your desired inputs you can right click and copy the total amount if you wish to use it elsewhere, for example in creating an LPoS contract with your selected UTXO coins. ![Alternative method of copying the UTXO coin amount](broken://files/-LnpsufAlfadmKwacJPr) ## Custom Change Address The second use of the coin control feature is specifying a custom change address. This feature is not commonly used, however, there may be times where you'd like to utilize this ability. Let's say your wallet has a UTXO which contains 20 coins and you wish to send 19.5 to somebody. Because UTXO's must be entirely spent, the wallet will automatically select this UTXO to complete your 19.5 + fee transaction which would leave you with just under .5 XDN as change. Normally this change would be sent to a newly created address in your wallet as part of the transaction. By specifying a custom change address, your change will be sent to any address you choose. {% hint style="success" %} **TIP:** Automatically created change addresses **will not** show up under your Receive window's "Requested payments history". The only way to view all of your change addresses is by using coin control inputs. {% endhint %} To enable this feature, simply check the box and enter an address. **Please note that if this feature is selected and the address is empty or invalid, a newly created change address will be used instead.** # Command Line Options You can start your XDN QT Wallet with special parameters from the command line directly, or use them in the xdn.conf file. # Console Commands You can find a detailed, complete list of all console commands below, or by typing "help" in the console. Also, you can type "help \" in the console for detailed help on specific commands. # DigitalNote Mobile Wallet Using the Mobile Wallet The new DigitalNote wallet have been introduced for both Apple iOs and Android phones. The mobile wallets can be downloaded [here](https://digitalnote.org/#wallets): *Features of the mobile wallet:* *Supports XDN, wXDN and 2XDN* *Supports encrypted messaging* *Supports Rain, Thunders and Tipping* *Supports the DAO voting mechanise using 2XDN* *More features to be added....* # Official Social Accounts & Live Chats Visit the Official DigitalNote Channels Discord: Telegram: [t.me/XDNDN](http://t.me/XDNDN) Reddit: Twitter: # Social Media Outlets Twitter: \ Medium: \ Bitcointalk: \ Reddit: \ Facebook: # Syncing Issues If for whatever reason the following doesn't fix your issue, join the Discord server and ask in the **public channels only** for help. **Do not respond to any DMs** as scammers might try to trick you into giving them your funds! ## QT Wallet If you happen to be on the wrong chain (typically due to not updating your wallet in time before a mandatory update), your wallet may show an incorrect balance and transactions may fail to send properly. ### How to Resync First, verify that you are indeed on the wrong chain by comparing your block height to the [explorer.](https://xdn-explorer.com/) If they do not match, take the following steps: 1. Be sure you have the latest version of the wallet. If not, download it from or [GitHub](https://github.com/DigitalNoteXDN/DigitalNote-2/releases). 2. Make sure your wallet is not running and navigate to the XDN data directory. 3. If you don't have a backup of your wallet.dat file, now would be a good time to make a copy just in case you accidentally delete it while doing the next step. Check the [Wallet Backup](/wallet-functionality/qt-wallet/backup-and-security/wallet-backup) page for more details. 4. Delete the following from the data directory: - blocks (entire directory) - chainstate (entire directory) - banlist.dat - peers.dat 5. Start the wallet and let it sync. Using a broadband internet connection, it should take about 15 mins to complete. # Manually Adding Peers How to manually add peers in your QT wallet {% hint style="warning" %} If for whatever reason the following doesn't fix your issue, join the Discord server and ask in the **public channels only** for help. **Do not respond to any DMs** as scammers might try to trick you into giving them your funds! {% endhint %} ## QT Wallet A current list of available peers can be found here: ![Select a peer IP address to add](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGS76NkOggE3cVqnXFw%2F-MGS7mJaLzkacstMh1iv%2FxdnGetPeersExplorer.jpg?alt=media\&token=b9584282-27c9-4db3-9e97-ed81f6a4d84e) You can use the debug console to quickly add a peer that is geographically closest to you by typing: ``` addnode node_ip_or_dns_address add ``` ![Type "addnode node\_ip\_or\_dns\_address add" and press Enter](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGS2zmWWs9d-PeLxk9W%2F-MGS5icUxuWWgEkU5_lk%2FxdnDebugConsoleAdd.jpg?alt=media\&token=b9040b00-2a6f-4f64-8e58-346ba2165043) ![Successfully adding the 138.197.161.183 node](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGS2zmWWs9d-PeLxk9W%2F-MGS6JueRGhLP_Cs5ao2%2FxdnDebugConsoleAddComplete.jpg?alt=media\&token=b18b3f6d-eb0c-4d90-92a6-a2a9ee93b6cd) ![A list of currently connected peers can be seen in the "Peers" tab of "Debug Window"](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGS6YowzTs8EBWDYY1i%2F-MGS6toaKxFQBGdIILaR%2FxdnDebugConsoleCurrentPeers.jpg?alt=media\&token=1639d6ea-5462-4ece-a62e-b826fabf7c84) # Masternode Setup # Client Side Instructions for Masternode setup on QT Wallet {% content-ref url="/pages/-MGU42GZhTz1ZIyrLOaJ" %} [QT Wallet MN setup](/support/masternode-setup/client-side/qt-wallet) {% endcontent-ref %} # QT Wallet MN setup How to setup your Masternode using the QT wallet ## Setup with a hosting provider If you are using a provider, please refer to their specific setup instructions. This is typically the easiest method to get started with running master nodes. {% hint style="info" %} Note: In this example, we will be using as the hosting provider. {% endhint %} {% hint style="warning" %} Warning: To avoid issues you must be using the same wallet version as the host provider.\ In this example, we are using XDN version 2.0.0.6 {% endhint %} The first thing you'll need to do is create and fund an address with EXACTLY 2,000,000 XDN.\ On the receive tab in QT wallet click "New Address"
![Enter a label. In this example "MN1" is used.](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZnJmOsQnJwEGfYgh0%2F-MGZokMlBtureIUbvZEO%2FxdnQTwalletNewAddress2.jpg?alt=media\&token=cdcc61a9-17aa-42df-a7b1-4d301b25f357) ![New address "MN1" successfully added](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZnJmOsQnJwEGfYgh0%2F-MGZqGEPVhrTWDk68GKY%2FxdnQTwalletNewAddressComplete.jpg?alt=media\&token=793c7ca4-0c06-4205-9bf3-fb53ba436d9e) Send exactly 2,000,000 XDN to the new address "MN1" and wait for at least 15 confirmations then double click the transaction to get specifics. ![copy the Transaction ID up to the "-"](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZnJmOsQnJwEGfYgh0%2F-MGZrBgSpzB6FuR9qdMj%2FxdnQTwalletMN1Transaction2.jpg?alt=media\&token=2ac077f0-0b87-4119-9905-009eae1437f4) Log into your account at 1. Click "Setup Node" 2. Search for "XDN" 3. Click "DigitalNote" ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZnJmOsQnJwEGfYgh0%2F-MGZtjfPeevd1yYbKmWd%2FtrttSetupNode2.jpg?alt=media\&token=5e7d9ef7-8999-4f29-a308-3a30070b4388) ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZvxeg2JuklB_F4u6V%2F-MGZyJyFQOsJkdiAyj2E%2FMNsetupPasteTransID1.jpg?alt=media\&token=7074e62e-8ce1-4961-80e1-05dcd8a2e8ca) 1. Paste "transaction ID" from clipboard 2. ignore "Output ID" 3. Click "Setup Masternode" ![Success ](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MGZvxeg2JuklB_F4u6V%2F-MGZxfQOPSLjEleamEHV%2FFireShot%20Pro%20Screen%20Capture%20%23320%20-%20'trttNodes'%20-%20node_trittium_cc_masternode.jpg?alt=media\&token=7dfe32c7-6b63-44ba-ba43-f401db75da42) 1. Read instructions and make mental note of "service status on My nodes page" 2. Click "Done" ![Node status has changed to "waiting"](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_4OoeeAuqWeXb0cY1%2F-MG_6mxs6ZzpQf4l8MpI%2FMNsetupNodeReady1.jpg?alt=media\&token=87e166c2-6ca4-465e-9ec3-df3ed290d96a) 1. notice status is stated as "waiting" in 2 different locations 2. click "Start node" ![Click "Copy"](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_4OoeeAuqWeXb0cY1%2F-MG_7jNJSe1pGFXwEzX0%2FMNsetupNodeStart.jpg?alt=media\&token=d606dc3c-4ed0-4526-a2b3-0edefa578058) 1. Return to the XDN data directory:\ Windows: C:\Users\\(your username)\AppData\roaming\xdn \ MacOS: \~/Library/Application Support/xdn\ Linux: \~/.xdn 2. Using a text editor (notepad used here) open a new document and paste the configuration string provided by the hosting service ( ). ![masternode.conf](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_B1nFbVmCijsIcC6K%2F-MG_BcMXG8AGRzxB0kwm%2Fmasternode.conf.jpg?alt=media\&token=d088e590-8e7d-4fdd-af20-8399c066566d) 1. Save this document in the data directory as "masternode.conf". 2. If XDN wallet is running, close wallet. 3. Launch XDN wallet..(it you just closed an open wallet, wait 2 minutes before relaunching). 4. Navigate to the "Masternodes" tab in QT wallet then choose "My Master Nodes" tab. 5. If you do not see your master node click "Update". ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_B1nFbVmCijsIcC6K%2F-MG_DOB3L9ZgqOa57Raj%2FMNsetupLaunch.jpg?alt=media\&token=eb0ca446-3ba3-4c86-96a4-c8277b0d02f6) Even though QT wallet may appear synced it is best to wait at least 5 minutes before proceeding to next step ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_B1nFbVmCijsIcC6K%2F-MG_Dut8piReBs_nMBjS%2FMNsetupLaunch1.jpg?alt=media\&token=c78505c9-cd4b-4c4f-9361-90cbebed2848) 1. unlock wallet 2. click on/select your masternode(blue indicates selection) 3. click "Start" ![Click "OK"](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_B1nFbVmCijsIcC6K%2F-MG_F6Xlm4URroZRxr6w%2FMNsetupLaunchStarted.jpg?alt=media\&token=e930ee32-caf1-4cf2-8a50-883c7b7f77c0) ![Masternode is now running](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MG_B1nFbVmCijsIcC6K%2F-MG_FU6b0XbLZpq8E_Ih%2FMNsetupLaunchRunning.jpg?alt=media\&token=3aeb2423-214f-4f40-ba9e-28cff4e3fc78) ## Setup with your own VPS The first thing you'll need to do is create and fund an address with EXACTLY 2,000,000 XDN. # Server Side # VPS Install VPS Masternode installation instructions ## Manual Installation This guide will assume you are using Ubuntu 18.04 LTS as your VPS Operating System. Connect to your VPS using an SSH connection. [Putty](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) is a popular choice for Windows users to do this with. Your VPS host will provide you with a username and ip address to make this connection. Once you have logged in, you'll need to download XDN wallet. Next, unpack the download. # Hosting Services Masternode hosting services There are several services that offer to host your Masternodes for you. The major advantage of using a hosting service is that they will maintain server side updates and security for you. Please note that this list may not include every available provider, nor are any of them endorsed by the XDN team. Each hosting service will have step by step instructions on how to setup and deploy your Masternodes using their specific platform. If you know of a provider not on this list, please let a team member know about it so we can add them! * # Collaborate with XDN How to contribute to the project The XDN Core project operates an open contributor model where anyone is welcome to contribute towards development in the form of peer review, testing and patches. This document explains the practical process and guidelines for contributing. Firstly in terms of structure, there is no particular concept of "Core developers" in the sense of privileged people. Open source often naturally revolves around meritocracy where longer term contributors gain more trust from the developer community. However, some hierarchy is necessary for practical purposes. As such there are repository "maintainers" who are responsible for merging pull requests as well as a "lead maintainer" who is responsible for the release cycle, overall merging, moderation and appointment of maintainers. ### Contributor Workflow The codebase is maintained using the "contributor workflow" where everyone without exception contributes patch proposals using "pull requests". This facilitates social contribution, easy testing and peer review.\ \ To contribute a patch, the workflow is as follows: 1. Fork repository 2. Create topic branch 3. Commit patches The project coding conventions in the developer notes must be adhered to. In general [commits should be atomic](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_commit_convention) and diffs should be easy to read. For this reason do not mix any formatting fixes or code moves with actual code changes. Commit messages should be verbose by default consisting of a short subject line (50 chars max), a blank line and detailed explanatory text as separate paragraph(s), unless the title alone is self-explanatory (like "Corrected typo in init.cpp") in which case a single title line is sufficient. Commit messages should be helpful to people reading your code in the future, so explain the reasoning for your decisions. Further explanation [here](http://chris.beams.io/posts/git-commit/). If a particular commit references another issue, please add the reference. For example: `refs #1234` or `fixes #4321`. Using the `fixes` or `closes` keywords will cause the corresponding issue to be closed when the pull request is merged. Please refer to the [Git manual](https://git-scm.com/doc) for more information about Git. * Push changes to your fork * Create pull request The title of the pull request should be prefixed by the component or area that the pull request affects. Valid areas as: * *Consensus* for changes to consensus critical code * *Docs* for changes to the documentation * *Qt* for changes to xdn-qt * *Mining* for changes to the mining code * *Net* or *P2P* for changes to the peer-to-peer network code * *RPC/REST/ZMQ* for changes to the RPC, REST or ZMQ APIs * *Scripts and tools* for changes to the scripts and tools * *Tests* for changes to the xdn unit tests or QA tests * *Trivial* should **only** be used for PRs that do not change generated executable code. Notably, refactors (change of function arguments and code reorganization) and changes in behavior should **not** be marked as trivial. Examples of trivial PRs are changes to: * comments * whitespace * variable names * logging and messages * *Utils and libraries* for changes to the utils and libraries * *Wallet* for changes to the wallet code Examples: ``` Consensus: Add new opcode for BIP-XXXX OP_CHECKAWESOMESIG Net: Automatically create hidden service, listen on Tor Qt: Add feed bump button Trivial: Fix typo in init.cpp ``` Note that translations should not be submitted as pull requests, please see Translation Process for more information on helping with translations. If a pull request is not to be considered for merging (yet), please prefix the title with \[WIP] or use [Tasks Lists](https://help.github.com/articles/basic-writing-and-formatting-syntax/#task-lists) in the body of the pull request to indicate tasks are pending. The body of the pull request should contain enough description about what the patch does together with any justification/reasoning. You should include references to any discussions (for example other tickets or mailing list discussions). At this stage one should expect comments and review from other contributors. You can add more commits to your pull request by committing them locally and pushing to your fork until you have satisfied all feedback. ### Squashing Commits If your pull request is accepted for merging, you may be asked by a maintainer to squash and or [rebase](https://git-scm.com/docs/git-rebase) your commits before it will be merged. The basic squashing workflow is shown below. ``` git checkout your_branch_name git rebase -i HEAD~n # n is normally the number of commits in the pull # set commits from 'pick' to 'squash', save and quit # on the next screen, edit/refine commit messages # save and quit git push -f # (force push to GitHub) ``` If you have problems with squashing (or other workflows with `git`), you can alternatively enable "Allow edits from maintainers" in the right GitHub sidebar and ask for help in the pull request. Please refrain from creating several pull requests for the same change. Use the pull request that is already open (or was created earlier) to amend changes. This preserves the discussion and review that happened earlier for the respective change set. The length of time required for peer review is unpredictable and will vary from pull request to pull request. ### Pull Request Philosophy Patchsets should always be focused. For example, a pull request could add a feature, fix a bug, or refactor code; but not a mixture. Please also avoid super pull requests which attempt to do too much, are overly large, or overly complex as this makes review difficult. #### Features When adding a new feature, thought must be given to the long term technical debt and maintenance that feature may require after inclusion. Before proposing a new feature that will require maintenance, please consider if you are willing to maintain it (including bug fixing). If features get orphaned with no maintainer in the future, they may be removed by the Repository Maintainer. #### Refactoring Refactoring is a necessary part of any software project's evolution. The following guidelines cover refactoring pull requests for the project. There are three categories of refactoring, code only moves, code style fixes, code refactoring. In general refactoring pull requests should not mix these three kinds of activity in order to make refactoring pull requests easy to review and uncontroversial. In all cases, refactoring PRs must not change the behavior of code within the pull request (bugs must be preserved as is). Project maintainers aim for a quick turnaround on refactoring pull requests, so where possible keep them short, uncomplex and easy to verify. Pull requests that refactor the code should not be made by new contributors. It requires a certain level of experience to know where the code belongs to and to understand the full ramification (including rebase effort of open pull requests). Trivial pull requests or pull requests that refactor the code with no clear benefits may be immediately closed by the maintainers to reduce unnecessary workload on reviewing. ### "Decision Making" Process The following applies to code changes to the XDN Core project (and related projects such as libsecp256k1), and is not to be confused with overall XDN Network Protocol consensus changes. Whether a pull request is merged into XDN Core rests with the project merge maintainers and ultimately the project lead. Maintainers will take into consideration if a patch is in line with the general principles of the project; meets the minimum standards for inclusion; and will judge the general consensus of contributors. In general, all pull requests must: * Have a clear use case, fix a demonstrable bug or serve the greater good of the project (for example refactoring for modularisation); * Be well peer reviewed; * Have unit tests and functional tests where appropriate; * Follow code style guidelines ([C++](https://github.com/NixPlatform/NixCore/blob/master/doc/developer-notes.md), [functional tests](https://github.com/NixPlatform/NixCore/blob/master/test/functional/README.md)); * Not break the existing test suite; * Where bugs are fixed, where possible, there should be unit tests demonstrating the bug and also proving the fix. This helps prevent regression. Patches that change XDN consensus rules are considerably more involved than normal because they affect the entire ecosystem and so must be preceded by extensive mailing list discussions and have a numbered BIP. While each case will be different, one should be prepared to expend more time and effort than for other kinds of patches because of increased peer review and consensus building requirements. #### Peer Review Anyone may participate in peer review which is expressed by comments in the pull request. Typically reviewers will review the code for obvious errors, as well as test out the patch set and opine on the technical merits of the patch. Project maintainers take into account the peer review when determining if there is consensus to merge a pull request (remember that discussions may have been spread out over GitHub, mailing list and IRC discussions). The following language is used within pull-request comments: * ACK means "I have tested the code and I agree it should be merged"; * NACK means "I disagree this should be merged", and must be accompanied by sound technical justification (or in certain cases of copyright/patent/licensing issues, legal justification). NACKs without accompanying reasoning may be disregarded; * utACK means "I have not tested the code, but I have reviewed it and it looks OK, I agree it can be merged"; * Concept ACK means "I agree in the general principle of this pull request"; * Nit refers to trivial, often non-blocking issues. Reviewers should include the commit hash which they reviewed in their comments. Project maintainers reserve the right to weigh the opinions of peer reviewers using common sense judgement and also may weight based on meritocracy: Those that have demonstrated a deeper commitment and understanding towards the project (over time) or have clear domain expertise may naturally have more weight, as one would expect in all walks of life. Where a patch set affects consensus critical code, the bar will be set much higher in terms of discussion and peer review requirements, keeping in mind that mistakes could be very costly to the wider community. This includes refactoring of consensus critical code. Where a patch set proposes to change the XDN consensus, it must have been discussed extensively on the mailing list and IRC, be accompanied by a widely discussed BIP and have a generally widely perceived technical consensus of being a worthwhile change based on the judgement of the maintainers. #### Finding Reviewers As most reviewers are themselves developers with their own projects, the review process can be quite lengthy, and some amount of patience is required. If you find that you've been waiting for a pull request to be given attention for several months, there may be a number of reasons for this, some of which you can do something about: * It may be because of a feature freeze due to an upcoming release. During this time, only bug fixes are taken into consideration. If your pull request is a new feature, it will not be prioritized until the release is over. Wait for release. * It may be because the changes you are suggesting do not appeal to people. Rather than nits and critique, which require effort and means they care enough to spend time on your contribution, thundering silence is a good sign of widespread (mild) dislike of a given change (because people don't assume *others* won't actually like the proposal). Don't take that personally, though! Instead, take another critical look at what you are suggesting and see if it: changes too much, is too broad, doesn't adhere to the developer notes, is dangerous or insecure, is messily written, etc. Identify and address any of the issues you find. Then ask e.g. on IRC if someone could give their opinion on the concept itself. * It may be because your code is too complex for all but a few people. And those people may not have realized your pull request even exists. A great way to find people who are qualified and care about the code you are touching is the [Git Blame feature](https://help.github.com/articles/tracing-changes-in-a-file/). Simply find the person touching the code you are touching before you and see if you can find them and give them a nudge. Don't be incessant about the nudging though. * Finally, if all else fails, ask on Discord or elsewhere for someone to give your pull request a look. If you think you've been waiting an unreasonably long amount of time (month+) for no particular reason (few lines changed, etc), this is totally fine. Try to return the favor when someone else is asking for feedback on their code, and universe balances out. ### Release Policy The project leader is the release manager for each XDN Core release. ### Copyright By contributing to this repository, you agree to license your work under the MIT license unless specified otherwise in `contrib/debian/copyright` or at the top of the file itself. Any work contributed where you are not the original author must contain its license header with the original author(s) and source. # Report a Wallet Issue How to report wallet bugs Before reporting any potential issues first make sure you are using the current version of the specific software in which you are experiencing the issue. You may also want to join the XDN Discord chat and describe your specific issue in the appropriate support channel in order to help identify if the problem is user/configuration/other error or an actual bug. Doing so may also alert you to any known workarounds you might be able to use in the meantime. If you are sure that your issue is indeed a bug, your next step should be the corresponding [XDN GitHub repository](https://github.com/DigitalNoteXDN), ie: [DigitalNote-2](https://github.com/DigitalNoteXDN/DigitalNote-2), [xdn-installer](https://github.com/DigitalNoteXDN/xdn-installer), [digiquidus](https://github.com/DigitalNoteXDN/digiquidus), etc. Once there, click on the issues tab near the top of the page and check to see if there is an open issue already describing your problem. If none exists you will need a GitHub account in order to create a new issue. This will ensure that the development team is made aware of your bug report. Accounts are free and easy to setup. When opening a new issue, try your best to be descriptive and provide any relevant log file excerpts that can help detail your problem. The most likely source for this information will be found in the debug.log file in your XDN data directory. Developers may ask followup questions, so be sure to reply or your issue may be closed due to the lack of additional requested information. # Feature Requests How to request wallet and network features Feature requests are best submitted in exactly the same manner as [Wallet Issues](/proposals-and-feedback/report-a-wallet-issue) within the appropriate [XDN GitHub repository](https://github.com/DigitalNoteXDN). This will ensure that your idea is seen by the development team. Simply open a new issue and describe the feature you'd like to see added. A developer may then add the "enhancement" label to your post to differentiate it from other issues/bugs. # Frequently Asked Question: 2XDN ![](https://1538148958-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGPpojSzO5yjyD69OwB%2F-MJgyIIlkTwn9ymYbYNX%2F-MJhTF8e_VHunaHhPZjA%2FXDN-2XDN-FAQ.jpg?alt=media\&token=0a3c9506-c51a-4af5-b731-fe67c8123337) **Question 1: Why is 2XDN being created?** DeFi is becoming extremely popular way to bring additional features to the market. The XDN community determined that these new features could best be delivered by setting up a bridge of our native XDN blockchain to Ethereum platform via an ERC-20 token. Originally we introduced 2XDN as a popular ERC-20 Ethereum token. This bridge was to offer us a new universe of opportunities in the DeFi space and allow the XDN ecosystem to interact with mobile apps such as Komodo, Metamask, Exodus, Jaxx Liberty and integrate into Decentralized Exchanges (DEX), payment platforms, etc. Extremely high gas fees prompted us to move 2XDN to the BSC network. All holders at the time, 3rd April 2022 were granted 1:1 2XDN on the BSC network. The 2XDN contract on the BSC network is: 0xC14527D6E8BdFbE2c57c41Bd6014b80639cde364 **Question 2: Is 2XDN a fork of XDN?** Answer: No. XDN is the native blockchain of DigitalNote while 2XDN is a new BEP-20 token that will be launching on Binance Smart Chain to enhance overall offering of our DigitalNote suite of products. The token is going to be distributed as staking reward to XDN holders for the XDN they will be staking. **Question 3: Is the XDN coin going to be replaced by 2XDN after the staking reward?** Answer: NO. XDN is our core blockchain and will continue strongly after the 2XDN staking reward distribution. The 2XDN tokens will complement our XDN blockchain and make it more powerful by providing a bridge to a bigger DeFi / dApp ecosystem. **Question 4: How are 2XDN tokens being distributed?** Answer: 2XDN tokens are going to be distributed as staking reward to those who will be staking DigitalNote XDN coins at the block number 300,000 (we will refer to this as **superblock**) of DigitalNote XDN blockchain. **Question 5: Who is eligible for the 2XDN staking rewards?** Answer: Anyone staking more than 100K XDNs is eligible for the 2XDN staking rewards. **Question 6: Where can I track when exactly superblock (block 300,000) will happen for XDN?** Answer: You can visit and see the countdown to the **superblock** at the top of the page. (This info is no longer available as the distribution has already taken place) **Question 7: Where can I find the Lite Paper on 2XDN?** Answer: This is the original **Question 8: Will we see a combined QT wallet for XDN & 2XDN?** Answer: While we clearly see the added convenience that will provide to XDN/2XDN holders, the value from this feature doesn't justify prioritizing the effort and resources over other items in our backlog. Integrating 2XDN within our XDN QT wallet will require supporting BSC addresses in our wallet - and thereby either running a full BSC node or constantly having to integrate with a provider of "BSC Node as a Service" - none of which is aligned to our long term roadmap as of now. We will like our 2XDN token to be supported by standard BSC wallets and Exchanges, just how most of the existing BEP-20 tokens work today. **December 4, 2022 update**: Our new DigitalNote mobile wallet has significant features to build on processing and handling 2XDN and WXDN (wrapped XDN on the BSC network) **Question 9: Is the XDN max supply going to increase as part of this 2XDN staking rewards?** Answer: NO. The current max supply of our native XDN coin will actually reduce exactly by the number of total 2XDN rewarded. This is to make sure that cumulative supply of XDN & 2XDN remains the same before and after the SuperBlock rewards. So if all the 70 Million 2XDN tokens are distributed, we will burn 70 Million XDN. **Question 10: How many 2XDN will I get?** Answer: There are two scenarios: 1\) XDN being used as a collateral for running Masternode(s): will get one 2XDN for every 50 XDN (ratio of 1:50). So if you are running one Masternode (which requires to have 2 M XDN as collateral), you will receive 2M divided by 50 – that is, 40,000 2XDN. 2\) XDN **not** being used as a collateral for running a Masternode: will receive one 2XDN for staking every 100 XDN (ratio of 1:100). So if you are staking 2 M XDN, you will receive 20,000 2XDN **Question 11: Why are Masternode owners being rewarded more?** Answer: Masternodes are foundational to running our native DigitalNote blockchain. We want to incentivize XDN holders to run more Masternodes to make our blockchain even stronger. **Question 12: Will the price of 2XDN be the same as the price of XDN?** Answer: There is going to be no correlation between the prices of the two assets, they are two different classes of assets and are going to be listed differently. XDN will continue to list as native cryptocurrency of DigitalNote blockchain, while 2XDN will be listed as BEP-20 token (similar to other BEP-20 tokens like Chainlink, Maker, OMG, etc). **Question 13: Are exchanges going to support this 2XDN staking rewards?** Answer: After reviewing many exchanges and offers, we have decided that WhiteBIT is the best fit that can not only include 2XDN Staking rewards, but also fulfil all of our requirements. For users who have XDN on exchanges other than WhiteBIT– they will need to either leverage XDN Wallet (QT or web) or stake masternode(s) to participate. **Question 14: How will staking work at WhiteBIT?** Answer: Yes, that’s right. At XDN Block 300K, the exchange will take the snapshot of your current XDN staking and will calculate 2XDN per the 100:1 ratio and deposit it in your account. Answer: Here are some important steps in the process you need to fully understand: * You must stake XDN for 30 days. Your coins will be locked for this period to make it eligible for the 1% SMART Staking Bonus on XDN and the 2XDN * You can start staking at any time before SuperBlock (Block 300K) * You must be staking before SuperBlock (block 300 K) * You will earn one 2XDN per 100 XDN only if you stake for 30 days (nonstop) or more. * The XDN & 2XDN rewards will be deposited into your account after SuperBlock (block 300K) and on completion of your 30-day staking. * If you unlock your deposit before your 30 period is up, your funds will be returned to your main account but you will not qualify for the 1% SMART staking rewards on XDN nor the 1 x 2XDN per 100XDN that you stake. * You will only be paid your rewards after the 30 day SMART staking period expires **Question 15: How will I get the 2XDN staking reward if I am running XDN Masternode(s)?** Answer: In that case, you will fill the form below to provide all the details of your Masternodes. The 2XDN will be deposited into the Ethereum address you mention. **Note**: Please ensure that the address is Ethereum address and is from a wallet that supports ERC20 tokens. We have tested with these wallets and recommend one of these: **MetaMask Wallet, Trust Wallet, Alpha Wallet**. **Question 16: How will I get 2XDN staking reward if my XDN is in my XDN QT or Web Wallet?** Answer: There are three things you can do: 1\) If you have more than 2M XDN, you may want to run a Masternode. This will be a great option as you will get 2 times more 2XDN than usual. For XDN used in running Masternode(s), use the process in question 15 to register for the 2XDN staking reward. 2\) You can continue to have your XDN in the QT or Web wallet – you will have to register for the 2XDN staking reward in that case. We are currently testing a new release of our DigitalNote QT and web wallets which will have an option to register for the 2XDN staking reward. It will ask for the Ethereum address where you would want your 2XDN token to be deposited. **Note**: Please ensure that the address is Ethereum address and is from a wallet that supports ERC20 tokens. We have tested with these wallets and recommend one of these: **MetaMask Wallet, Trust Wallet, Alpha Wallet.** 3\) You can move your XDN from the DigitalNote wallet to WhiteBIT exchange (before superblock). This way you will get 2XDN staking reward without having to do anything else. **Note**: We recommend use of web wallet **if and only if** you can't use our QT wallet. The reason for that is - you will get staking XDN rewards for your coins in QT wallet. For web wallet, DigitalNote stakes the XDN so that users will be eligible for 2XDN, but there currently isn't a way to distribute the XDN rewards back to each wallet so any rewards earned from Web Wallet will go directly to dev fund. We are working on a future enhancement that will send the XDN staking rewards back to the wallets, but it wouldn't be available before SuperBlock event. **Question 17: What if my exchange doesn't support the 2XDN staking reward?** Answer: You may want to transfer your XDN to DigitalNote QT wallet or web wallet before the SuperBlock and once you have received the 2XDN staking reward, you may transfer your XDN back to the Exchange of your choice. **Question 18: What will be the total supply of 2XDN?** Answer: 70 million. **Question 19: What will happen if some people do not take advantage of the 2XDN staking reward.** Answer: It is difficult to predict how many people will take advantage of the 2XDN staking reward. If everyone takes advantage of the staking reward, there will be approximately 54,569,000 2XDN in circulatory supply. The unclaimed 2XDN will be burnt. After the burn, there will still be approximately 15,341,100 2XDN left to cover Staking efforts and Corporate use over the next 15 years. The final circulatory supply will be made known once the 2XDN staking reward distribution is complete and finalized. In addition, we will burn an amount of XDN equal to the new 2XDN tokens in circulation - that way the total supply of the two coins will be the same as XDN supply before the SuperBlock reward. **Question 20: Where will the new 2XDN token be listed?** Answer: To begin with, the token will be listed on WhiteBIT exchange and will be immediately available for trade. We are also going to have a **Uniswap pool** created for trading 2XDN. We are also working with many other exchanges and DeFi platforms. We hope that some of these additional exchanges will also list 2XDN for trading or swap. We will continue to update the community on this as more exchanges support 2XDN. **Question 21: What if I miss participating in the 2XDN staking reward? Will my XDN be useless?** Answer: If your XDN is on WhiteBIT, you will need to stake your XDN per the rules in 14) above to get 2XDN rewards. But if your XDN is on other exchanges, or it is on DigitalNote Wallet, or on Masternode, you will miss the opportunity to get 2XDN unless you follow the steps described in questions 15, 16, and 17 above. Even if you miss 2XDN staking reward, your XDN will remain intact. **Question 22: Do I have to encrypt my XDN wallet in order to stake for XDN?** No. You do not need to encrypt the wallet to stake. BUT if you have the wallet encrypted, **you need to unlock it to stake**. **Question 23: What is DigitalNote Deployer on 2XDN's *****etherscan.io***** page? What are those transactions with other addresses when 2XDN isn't distributed yet?** DigitalNote Deployer is the distribution address for the 2XDN staking reward - it will have 70M total supply at the beginning and will be used to distribute the 2XDN for SuperBlock staking reward. We have set up some ETH addresses as test addresses to be able to test the code that we have developed to support the new 2XDN token. The transactions listed are related to testing. # Merchandise Grad your cool XDN swag Updated Gear for 2020/2021 coming soon Thank you for your pantronage! # XDN Press/Media Kit Visit our github for Logos {% embed url="" %}