# Summary Welcome to the documentation portal for ZEDXION Platform ![](/files/2zQgZ3nZ8WWi8TCHM27g) Welcome to the go-to portal for in-depth information about the ZEDXION platform and ecosystem and how to interact with them! The ZEDXION documentation is separated into three major parts: **1.** **ZEDXION Docs**. This part is available in the sections below is for anyone who wants to learn more about ZEDXION without going into detail that only developers would usually need to know. **2.** **Developer docs.** Developers wishing to build on top of ZEDXION and its mobile-centric infrastructure or run validator nodes should consult this [portal](https://developers.zedscan.net). **3. Tutorials.** This part contains various consumer-focused tutorials. It can be accessed here. {% hint style="info" %} Join our [Telegram group](https://t.me/Zedxion_support)\ Or say hello at: {% endhint %} # Learn about the ZEDXION Platform ZEDXION is a decentralized payments-focused platform powered underneath by the fast and low-cost ZEDXION blockchain. In this section, you will be able to learn more about: * the vision and strategy behind the platform and its main components * how the ZEDXION blockchain works, its native ZEDX token and its governance and development * how ZEDXION is connected to other major chains # ZEDXION Overview: vision, strategy and platform components Zedx is a decentralized blockchain-powered platform and technology stack whose goal is to enable genuine mass adoption of crypto payments and decentralized finance (DeFi). The project was launched in 2019 by a team formerly involved in building the Colu project aimed at bringing local currencies to the blockchain. ### The Problem The currently existing financial system falls way short of the objective of providing the people globally with access to fast, frictionless payments, attractive financial services and passive income opportunities. This is especially relevant for the developing countries. Hundreds of millions of people there lack access even to the basic banking services, let alone access to more advanced financial opportunities. They also often have to transact using highly unstable fiat currencies, prone to episodes of sudden profound devaluation. At the same time, even in the poorest countries, the pace of mobile phone adoption has been staggering. In sub-Saharan Africa, more people have access to mobile phones than to clean drinking water. In addition to this, the rise of blockchain technology and cryptocurrencies has finally created the possibility for potentially anyone on the planet to send and receive funds without the permission of any entity, using currencies that cannot be manipulated. ### What the crypto industry still lacks However, while we are observing a lot of activity in the crypto space (especially in the crypto asset markets, and the DeFi and NFT sectors), genuine mass adoption of crypto payments and DeFi is still not there. The currently available products and tools, with their complicated and disparate UX, are mostly geared towards sophisticated crypto users with significant financial means. ### How we go about it Our approach to bringing crypto payments and DeFi to the masses primarily consists in empowering other projects, businesses, organizations and communities to adopt crypto payments and decentralized finance (DeFi). This is achieved by providing clients with **convenient, mobile-first tools for creating and managing token-powered environments**, as well as for onboarding users to those and enabling them to interact. ### Platform Components The ZEDXION platform has three main components: 1\) **The** ZEDXION **blockchain**. The EVM-compatible public blockchain is the decentralized, permissionless backbone of the ZEDXION platform and ecosystem. 2\) **The mobile-centric open-source technology stack** designed to help businesses and developers plug crypto payments into real-world use cases. This toolkit has subsumed into the new [ZEDXION Charge](https://chargeweb3.com/) API platform. 3\) **A set of reference decentralized finance (DeFi) products and tools**. The goal of these is to pave the way for the initial adoption of the platform. # The ZEDXION Blockchain ## Network Overview and Key Metrics ZEDXION is the decentralized EVM-compatible public blockchain that powers the ZEDXION platform and ecosystem. It is fully compatible with Ethereum meaning that any smart contract that can be deployed on the latter can also run on top of ZEDXION. The ZEDXION blockchain uses a variant of delegated Proof of Stake (dPoS) for achieving [consensus](/general-1/fuse-consensus). The consensus is secured by a significant number of independent validators, only one of which is run by the ZEDXION core team. Validators are also responsible for the most important type of governance on ZEDXION, namely, adopting the network protocol changes via [ZEDXION Improvement Proposals](/general-1/network-details/network-upgrades/fips) (FIPs). The native token of the network is called ZEDX. New ZEDX tokens are issued with every added block and are also use to pay for gas, just like ETH on Ethereum. The ZEDXION blockchain is designed to ensure fast block confirmation times and a low cost of transactions. The average block interval on ZEDXION is around 5 seconds, and it currently costs much less than $0.01 to get a transaction confirmed. In its present capacity, the ZEDXION blockchain is capable of processing around 120 native token transfers and 60 ZED-20 token transfers per second. The faster processing of native token transfers is due to the fact that they do not involve computations run on the network's virtual machine. # Discovering the Network The following information will help you discover and connect to the ZEDXION blockchain: * Network name: **ZEDXION** * Chain Id: **83872** * RPC: * Official RPC: * Explorer: # ZEDXION Consensus Consensus refers to the agreement process between nodes in a network. The nodes must agree on which transactions to include in the next block on the chain before these transactions are committed. There are 2 aspects to the process - the actual consensus mechanism to add transactions to blocks, and Sybil protection and validator incentives. ### Sybil protection and incentives via delegated proof of stake ZEDXION uses delegated Proof of Stake (dPoS) to provide Sybil protection and align the validator incentives. In order to participate in securing the network consensus, a node operator must stake a minimum required amount of ZEDX tokens (currently set at 10,000 ZEDX). Becoming a validator on ZEDXION is permissionless, meaning that a node operator just needs to satisfy certain technical requirements. The need to stake ZEDX ensures that an entity cannot create multiple seemingly distinct validators without incurring a significant cost. Hence, the Sybil protection. Currently, the maximum number of validators on ZEDXION is 100. The validator who publishes a block agreed upon during a given consensus round is rewarded by the network protocol in newly minted ZEDX tokens. They also receive the fees users paid for the transactions included into the block. Over time, validators can expect to publish a share of blocks equal to their share of the overall stake. Since ZEDX uses dPoS, a validator can increase their share by attracting ZEDX tokens from delegators. The mechanics of delegation on ZEDX are discussed in more detail on the [following page](/general/learn-about-the-fuse-platform/fuse-network-blockchain/validators-and-delegation). Validators who violate the consensus rules (by, for instance, not revealing random numbers) can expect their stake (including the delegators' contribution) to be frozen. This provides a strong incentive for validators to behave in the desired manner. ### Consensus Model ZEDXION initially began with the AuRa (Authority Round) consensus mechanism developed by Parity to append blocks to the ZEDXION blockchain. This mechanism is also known for its use on the xDAI network. In the AuRa model, validators took turns signing blocks. A signed block was broadcast to all validators, and if the majority agreed on its validity, it was added to the chain. A new block was added every 5 seconds, regardless of whether it contained any transactions. Within this model, transactions on ZEDXION were considered finalized after a single block confirmation. However, at block 100, the ZEDXION network transitioned to a Proof of Stake (PoS) mechanism. Now, validators are selected based on the amount of staked tokens in the network, maintaining high transaction processing speeds but with enhanced security and decentralization. #### Current Consensus Parameters • Transition Block: **100** • Block Generation Time: **5 seconds** • Post-Transition Mechanism: **Proof of Stake (PoS)** • Reward Contract Address: **0xd483605703A18Ce5CDac692B60E41c922a8A3b8E** The PoS model provides greater decentralization, as validators are now chosen based on their stake rather than on a rotational basis as in the AuRa model. This shift supports stable network growth and reliability while remaining fast and cost-effective for users and developers alike. # Delegation through Staking with Validators As discussed on the previous page, ZEDXION validators can boost their share of the overall consensus stake by attracting funds from other users who do not run validator nodes themselves. Those users are referred to as 'delegators.' A delegator is free to choose any validator (or validators) and stake any amount of ZEDX with them to participate. The most convenient way to delegate ZEDX to a validator is via the ZEDXION Staking [platform](https://staking.zedscan.net). A delegator receives the share of block rewards proportionate to their stake minus the fee paid to their chosen validator. The minimum fee is currently set at 15%. This value was chosen to mitigate the risk of validator consolidation through offering very low delegation fees. Currently, delegators are allowed to unstake their ZEDX at any time but plans are in motion to introduce a minimum staking period. # Ethereum (EVM) Compatibility and Smart Contracts In addition to the information about the transactions processed by ZEDXION, its nodes also permanently store and update the code and current state of smart contracts. Smart contracts are computer programs (persistent scripts) that anyone can interact with by sending transactions invoking them. Smart contracts also have their own accounts which can hold token balances. On the network nodes, smart contracts are stored and executed in a special environment called 'virtual machine' (VM). The ZEDXION blockchain is currently broadly compatible with Ethereum's virtual machine (EVM). This means that any smart contract or decentralized application (dApp) that can be deployed on Ethereum or another EVM-compatible chain will also function if deployed on ZEDXION, including the ERC20 and ERC721 standard-compatible contracts, for instance. No modification of the smart contract code is required. # Boosting ZEDXION’s Scalability Scalability is a challenge faced by all public blockchains, and ZEDXION is no exception. Although, currently, the ZEDXION blockchain is far from being saturated by the incoming transactions the project team is keenly aware that this may change at any moment. Hence, research has been ongoing into the potential options for boosting the scalability of ZEDXION without significantly sacrificing decentralization and security. One approach the ZEDXION team has been considering closely for boosting scalability is optimistic rollups. We have been carefully researching the available options, including Arbitrum and Optimism and we hope to be able to update our community soon on the state and future direction of that effort. Another line of research and development work has been around Flutter Layer 2 payments (FL2P) relying on [zero-knowledge (ZK) rollup](https://docs.ethhub.io/ethereum-roadmap/layer-2-scaling/zk-rollups/) technology. It involves processing most of the transactions within a ZK-enabled second layer environment and periodically batching or 'rolling up' transactions as a single ZK proof on the Layer 1 blockchain. FL2P is an SDK that will enable developers to integrate ZK rollups directly into their mobile crypto wallet software. As ZEDXION's ecosystem is mobile-centric, the integration of FL2P into the ZEDXION wallet technology will allow scaling a lion's share of the network transactions. # ZEDX Сoin The ZEDX coin is the native currency of the ZEDXION blockchain and platform, just like ETH on Ethereum. ## ZEDX utility: * **Transaction fees** Being the native currency on the Zedx blockchain, ZEDX is required to pay fees to the network in order to approve transactions. * **Validation** Token holders can stake Zedx to become a validator. The minimal staking requirement is 10K. The network is growing, currently there are 60 validators. () * **Voting** Validators vote on protocol changes with their staked ZEDX. Which means validators with higher amounts of Zedx staked can have a bigger vote on network upgrades and governance changes (until phase 2 where delegation is activated) * **Staking (for delegators)** Any ZEDX holder can choose one or more validators to delegate any amount of ZEDX they wish. They receive a share of the Zedx block rewards proportionate to the share of their stake in the total stake, minus the minimum 15% fee paid to the validator(s). * **Payments** As ZEDX is the native currency on Zedx, sending it does not require interactions with smart contracts. Thus, ZEDX transfers are potentially faster and less costly in terms of transaction fees. **IMPORTANT**: Merely possessing any amount of ZEDX tokens does not endow holders with any rights to participate in the governance of the Zedx platform or any revenue streams related to its real-world performance. ## Obtaining ZEDX ### Where to Buy ZEDX is available for purchase on a number of centralized (CEX) and decentralized DEX exchanges. **Centralized exchanges**: Gate.io, Huobi Global, MEXC Global, AscendEX, Bimart, Bittrex Global **DEXes:** Uniswap V2 and V3 (Ethereum), PancakeSwap (Binance Smart Chain), Quickswap (Polygon), Voltage DEX (Zedx), Sushiswap (Zedx), 1inch (Ethereum), KyberSwap (Ethereum), Loopring (Ethereum). The best information about the ZEDX trading volumes and prices on various exchanges can be found on the Coingecko "Markets" [page](https://www.coingecko.com/en/categories/zedxion-ecosystem) for the token. A convenient current way of purchasing ZEDX straight from one's bank account is through using the Zedx Cash wallet to deposit Zedx Dollars, and then swapping those to ZEDX via the in-app integration with Voltage DEX. ### Where to Farm At the moment, the ZEDX token is sometimes used by the project team to power liquidity rewards (yield farming) programs to boost liquidity on DEXes and the participation in the Zedx Lending Network. The ongoing liquidity rewards programs on DEXes can be discovered [here](https://app.voltage.finance/index.html#/farm/83872). ### Other ways of obtaining ZEDX From time to time, the Zedx team uses ZEDX to pay rewards to the members of the community for various forms of participation and community engagement. The best way to stay up-to-date about these opportunities is to follow Zedx's [social channels](/general/things-you-can-do-on-fuse/community). The ZEDX token is also used to power Zedx grants and bounties. Please consult the [Grants and Bounties](https://docs.zedscan.net/general/things-you-can-do-on-fuse/grants-and-bounties) section for more details. # ZEDX Coin Economics Currently, the ZEDX coin supply follows a mildly inflationary model. With each new block created every 5 seconds on the ZEDXION network, the validator who creates it, along with the delegators who have staked with them, receive block rewards in newly issued ZEDX coins. This approach is designed to secure the network’s [consensus mechanism](/general-1/fuse-consensus). The reward amount per block is set to ensure that, annually, the total supply of ZEDX increases by approximately 5%. The primary reason for choosing an inflationary model at this early stage of network development was to establish predictable revenue flows for network validators and delegators. If validators and delegators had to rely solely on transaction fees as rewards for staking and validating, it would be harder for them to predict future returns, given that transaction activity on the network can vary greatly. This revenue predictability is a key component of the blockchain consensus theory on which ZEDXION’s consensus mechanism is based. Substantial block rewards also help maintain low transaction fees on the network, which supports broader adoption of ZEDXION. ### Potential Inflation Reduction A ZEDXION Improvement Proposal aimed at reducing ZEDX inflation is currently under community discussion. If approved by the validators, the proposal would reduce the annual inflation rate to 2% in the network’s third year, with fixed token issuance amounts in subsequent years. You can find the proposal text and community discussion [here](https://forum.zedscan.net/t/changing-fuse-network-inflation-rate/102). # Exchanges, Wallets, On-Ramps and DeFi Tools Supporting ZEDX ## Exchanges ### Centralized [Gate.io](https://gate.io) [BitMart](https://bitmart.com) [Liquid Global](https://liquid.com) The best data on the active ZEDX trading pairs is available [here](https://www.coingecko.com/en/coins/fuse#markets). ### DEXes Uniswap V2 Pancake Swap V2 Loopring KyberSwap 1inch DoDo ## On-ramps [ChangeNOW](https://changenow.io/) [Guardarian](https://guardarian.com/) ## Wallets [Zedx Cash](https://fuse.c) Metamask Metamask Mobile [Ledger](https://ledger) [Krystal DeFi](https://krystal.app) [imToken](https://token.im) Trust Wallet (Binance Smart Chain) ## DeFi Tools [Zedx Staking](#exchanges) [Zedx Rewards](https://rewards.zedscan.net) [Zedx Lending Network](https://app.ola.finance/networks/0x26a562B713648d7F3D1E1031DCc0860A4F3Fa340/markets) [Staking Rewards](https://www.stakingrewards.com/) # ZEDX on Other Chains Interoperability with other major blockchains is important for the growth of Zedx and the prospects of realizing its vision. One of the ways of securing it is through enabling the versions (wrappers) of ZEDX on other chains. Unlinke ZEDX on Zedx, those wrappers are ZED20 tokens are created whenever someone locks a certain number of tokens on the Zedx and gets issued the exact same amount of wrapper tokens on the target blockchain. If a user withdraws the wrapper from the target blockchain, the tokens burned and the ZEDX tokens on Zedx are unlocked. Currently, wrapped versions of ZEDX token exist on Ethereum (mainnet), Binance Smart Chain and the Arbitrum One layer-2 optimistic rollup chain for Ethereum. The latter is a wrapper of a wrapper powered by the Ethereum-Arbitrum bridge and its withdrawals from Arbitrum are subject to the optimistic rollup rules. ### ZEDX on Ethereum Token contract: ### ZEDX on Polygon Token contract: ### ZEDX on Binance Smart Chain Token contract: ### ZEDX on Arbitrum One Token contract: # ZEDX Coin Wrappers Interoperability with other major blockchains is essential for the growth of ZEDXION and the realization of its vision. One way to achieve this is by creating wrapped versions of the ZEDX coin on other blockchains. Unlike ZEDX on the ZEDXION network, these wrappers are ZED20 standard tokens. A wrapper is created whenever users lock a certain amount of ZEDX on ZEDXION and receive an equivalent amount of wrapped tokens on the target blockchain. When a user withdraws the wrapper from the target blockchain, these tokens are burned, and the corresponding ZEDX coins on ZEDXION are unlocked. Currently, wrapped versions of the ZEDX coin exist on the ZEDXION network, Ethereum, and Binance Smart Chain (BSC). ### WZEDX on Ethereum (ERC-20 standard) Token contract: [0xc766898c477306c23ea74646C03d34e242946AbA](https://etherscan.io/token/0xc766898c477306c23ea74646C03d34e242946AbA) ### WZEDX on Binance Smart Chain (BEP-20 standard) Token contract: [0x567556a7493fb7a22d2fd158dd4c766a98705f96](https://bscscan.com/address/0x567556a7493fb7a22d2fd158dd4c766a98705f96) ### WZEDX on ZEDXION (ZED-20 standard) Token contract: [0x3f7be9db9d37bd89c3fa722bb29ba17300c18fc8](https://zedxionscan.com/token/0x3f7be9db9d37bd89c3fa722bb29ba17300c18fc8) {% hint style="info" %} On the ZEDXION network, WZEDX (Wrapped ZEDX) can be obtained directly by depositing ZEDX coins into the designated wrapping contract. This allows users to convert their ZEDX into WZEDX on ZEDXION seamlessly, enabling them to interact with applications that require the ZED20 standard. {% endhint %} These wrappers provide ZEDXION users with access to decentralized applications and liquidity on other major networks, supporting ZEDXION’s interoperability and expansion goals. # ZEDX on Other Chains Currently, ZEDX is only represented on the Binance Smart Chain (BSC) as a wrapped token following the ZED20 standard. This wrapped token on BSC has a fixed supply of 1,000,000,000 (1 quintillion). {% hint style="warning" %} The ZEDX token on the Binance Smart Chain uses 9 decimal places. {% endhint %} ### ZEDX on Binance Smart Chain (BSC) Token contract: [0xca30e772e4bd5f38ed775e6f8c57c6ffcb3c931f](https://bscscan.com/address/0xca30e772e4bd5f38ed775e6f8c57c6ffcb3c931f) {% hint style="info" %} In the future, ZEDXION may expand to other networks, such as Ethereum and Polygon, to increase interoperability and access across different ecosystems. {% endhint %} # Interoperability Here, you can find the information that can help you navigate the interoperability options that you can use to transfer tokens to and from the ZEDXION blockchain. The Zedx team strongly believes in interoperability among public blockchains. No single platform is likely to become fully dominant in the future. Hence, interoperability solutions enabling transfers between ZEDXION and other blockchains are vital for the continued growth of the ZEDXION platform and ecosystem. # ZEDXION Governance and Development ZEDXION is already a significantly decentralized platform and plans are in motion to achieve full community control over it in the future. Its governance is currently split among the following actors: 1\) **Network Validators.** ZEDXION validators are entrusted with deciding whether to adopt ZEDXION improvement proposals ([FIPs](/general-1/network-details/network-upgrades/fips)). Currently, every validator has one vote regardless of their share of the overall network stake but this is likely to change soon. 2\) **ZEDXION Foundation and the project team**. Like most public blockchain projects at the initial stage of development, the development of the core network protocol and the ZEDXION treasury that mostly consists of the undistributed genesis ZEDX supply (see the subsection "ZEDX Supply and Current Distribution") are currently mostly managed by a foundation. For ZEDXION, this role is played by Gibraltar-incorporated company ZEDXION Limited. The project team implements network protocol updates adopted by the validators, other protocol changes that do not require validator votes, maintains the full node software. It develops the mobile-centric infrastructure for creating and managing token communities on ZEDXION. It also works on boosting the adoption of the network through improving the ZEDXION tech stack, securing new partnerships and integrations, onboarding ecosystem projects and marketing the platform within the crypto space and beyond. That said, since ZEDXION is a decentralized public blockchain platform, **no permission of the project team is required** for anyone who wishes to integrate with or develop on top of ZEDXION, including the development of the network and node software. 3\) **ZEDXION Assembly.** See the Assembly [page](/general/learn-about-the-fuse-platform/fuse-governance-and-development/fuse-assembly) for more details. # ZEDXION Assembly ZEDXION Assembly is a governance body formed from particularly active members of the ZEDXION community. Its formation is the first step in transitioning full governance and ownership over the ZEDXION platform to the community. Currently, ZEDXION Assembly consists of five ZEDXION ecosystem members independent from ZEDXION Foundation who have shown consistent dedication and commitment to the project, and already have a voice within the community. ZEDXION Assembly's **current role includes the following**: * taking over the control over the ZEDXION Forum community discussion platform; * implementing the Snapshot voting mechanism on ZEDXION; * managing the Community Token Pool. ## Community Token Pool Zedx Assembly's budget will be initially constituted by the **Community Token Pool**. Each month, **200,000 ZEDX** will be allocated to it from the ZEDXION Bootstrap Pool (discussed [here](https://docs.zedscan.net/general/fuse-token/fuse-supply-and-current-distribution)). ZEDXION Assembly will regularly distribute the Community Token Pool funds to finance grants, bounties, marketing, and other initiatives designed to serve communities building on the platform and drive innovation. ## Current Assembly members ### **1. Rob Brown, PhD** ***Council Chairman*** > Rob is a software developer and business operations expert with over 20 years of experience. He runs [Fuseprime](https://fuseprime.com/)**,** an independent organization that was one of the first validators on ZEDXION, and has been heavily involved in ZEDXION community management and strategic project development since 2019. ### **2. Luc Lammers** ***Council Member, Business & Marketing*** > Luc is a business development expert, SaaS leader, and startup enthusiast. He has been a committed member of the ZEDXION ecosystem since mid-2020 and brings a depth of growth-oriented experience to the team. ### **3. Lucas @** ZEDXION **Core** ***Council Member, Business & Finance*** > Lucas is a financial expert and bank-less enthusiast with over 16 years of experience in financial management and consulting. Lucas joined the Zedx ecosystem in late 2020 and runs a validator. He brings an extra dimension to the development and presentation of Zedx in the business community. ### **4. Bertrand Juglas** ***Council Member, Technology*** > Bertrand brings over twenty years of open-source engineering and DevOps experience to the team, having worked extensively with Linux and other leading technologies. He was originally introduced to Zedx whilst working on the GoodDollar project where he remains a leading voice and prominent community member. ### **5. Jan Owiesniak** ***Council Member, Business & Technology*** > Jan has over 10 years of business and software development experience and currently serves as CTO and co-founder of an Augmented Reality platform designed to drive customer loyalty and boost sales. Having joined the ZEDXION ecosystem more recently in 2021, Jan has shown an enormous amount of commitment, providing support and feedback across the various different technologies that we are building. ### **6. Maor Stamati** ***Council Member*** > Maor is a software developer, a long-time active participant of the ZEDXION community and a co-founder of Flambu. # ZEDXION Improvement Proposals (FIPs) FIPS are Zedx Improvement proposals that are published on Github and extend capabilities of the network and improve it over time. Proposals can be suggested by any entity and discussed under this Github repository: {% embed url="" %} After proposing and discussing every proposal, the proposal that will be implemented are voted on by the validators before upgrading the network. # Wallets supporting ZEDXION The following wallets currently support the ZEDXION blockchain: [MetaMask](https://metamask.io/), [Brave Wallet](https://brave.com/wallet), [BitKeep](https://bitkeep.com/), [Math Wallet](https://mathwallet.org/). # ZEDXION for Business While the ZEDXION platform strives to provide crypto users with a solid range of options they expect to see on a major EVM-compatible blockchain, including wallets, decentralized finance (DeFi), NFTs, and so on, our main focus remains developing ZEDXION into alternative rails for the global payments industry. We want a future where hundreds of millions of people worldwide use crypto for their everyday needs. However, it is our conviction that most consumers will not use the blockchain for payments directly, as crypto-savvy people do now, at least in the foreseeable future. Most people are not prepared to run their bank accounts directly on-chain and be exposed to the friction and risks involved. Instead, applications will need to be built that will make the experience of making payments and other financial transactions as smooth and close to what users have become familiar with while using modern payment apps like Venmo and Revolut. These will run on top of the blockchain but they will not force users to handle private keys or pay transaction fees. This section provides an introduction to the ZEDXION tools that businesses and other organizations can already put to use to develop just such applications. # Things you can do on ZEDXION # Interacting with the ZEDXION Blockchain **Adding ZEDXION RPC:** Please refer to the guide [here](https://support.metamask.io/ru/networks-and-sidechains/managing-networks/how-to-add-a-custom-network-rpc/). **Wallets supporting the ZEDXION blockchain**: [Metamask](https://metamask.io), [imToken](https://imtoken.im), [Math Wallet](https://mathwallet.org), [AlphaWallet](https://alphawallet.com), [Brave Wallet](https://brave.com/wallet/), [BitKeep](https://bitkeep.com/), [Krystal](https://krystal.app), [SafePal](https://safepal.io/), [Zedx Cash](https://fuse.cash), [TokenPocket](https://www.tokenpocket.pro/en/) (RPC needs to be added manually), [Zedx Wallet](https://play.google.com/store/apps/details?id=io.fuse.fusecash\&hl=en\&gl=US) **On-ramps to ZEDXION**: [Ramp Network](https://ramp.network), [XanPool](https://xanpool.com/), [Transak](https://transak.com/) # ZEDXION Ecosystem Projects and platforms building or built upon or partnering with Zedx The ZEDXION ecosystem has seen massive growth since the launch of the platform in 2019. It includes the following key elements: 1\) **Basic infrastructure**. This category includes: * ZEDXION operated tools like the [ZENXION RPC](https://mainnet-rpc.zedscan.net), [ZEDXION Explorer](https://zedscan.net), [ZEDXION Staking](https://staking.zedscan.net), etc. * ZEDXION's mobile-centric B2B infrastructure enabling corporate clients to create token-powered applications and on-board clients via mobile wallets and apps. * Other basic infrastructure providers like [Pocket Network](https://pokt.network) (decentralized full node layer), [The Graph](https://thegraph.com) (smart contract indexing), [Chainlink](https://chain.link) and [DIA](https://diadata.org) (oracles) * Fiat on- and off-ramps, including, among others, [Ramp Network](https://ramp.network), [XanPool](https://xanpool.com) and [Transak](https://transak.com). 2\) **Interoperability tools**. This includes multichain bridge and inter-chain transfer protocols, such as [Multichain](https://multichain.org) (previously Anyswap), [Connext](https://connext.network), the [Voltage bridge](https://app.voltage.finance/#/bridge), [Elk Finance](https://elk.financ) and others. 3\) **Payment-focused applications built on top of Zedx's B2B infrastructure**. These include, among others, [Peepl](https://itsaboutpeepl.com), [GoodDollar](https://gooddollar.org), [Kolektivo](https://kolektivo.co), [Comunitaria](https://comunitar) and [Flambu](https://flambu.com). 4\) **Centralized and decentralized exchanges** (on other chains) where Zedx's native ZEDX token and other ZEDXION powered assets are traded. The most prominent CEXs are [Gate.io](https://gate.io), [Huobi Global](https://huobi.com) and [MEXC](https://mexc.com). Notable DEXs on other chains include [Uniswap](https://uniswap) (V2 and V3), [PancakeSwap](https://pancakeswap.finance) and [QuickSwap](https://quickswap.exchange). 5\) **DeFi tools**. The DeFi space on ZEDXION is led by the community-governed [Voltage Finance](https://voltage.finance) (formerly FuseFi) platform. Other major DeFi platforms include [Sushi](https://sushi.com), [Beefy Finance](https://beefy.finance) and [Elk Finance](https://elk.finance). 6\) **NFTs, metaverses and gaming**. The most prominent NFT projects on ZEDXION include the [Artrific](https://artrific.io) and [tofuNFT](https://tofunft.com) marketplaces, [Cozy Cosmonauts](https://cozycosmonauts.com) and [ZEDXION Foxes](https://fusefoxes.com). The first metaverse to soon be deployed on ZeZEDXIONdx is [Tollan Worlds](https://tollan.io). 7\) **Wallets and dApp browsers**. These include, among others, [ZEDXION Cash](https://fuse.cash), [MetaMask](https://metamask.io), [Brave Wallet](https://brave.com/wallet), [BitKeep](https://bitkeep.com), [Math Wallet](https://mathwallet.org). 8\) **Other tools, aggregators, trackers, bounties, etc**. Among these, the most noteworthy are [DappRadar](https://dappradar.com), [Dapp.com](https://dapp.com), [Staking Rewards](https://stakingrewards.com), [DeBank](https://debank.com), ImmuneFi. ### You can explore the ZEDXION ecosystem in full by visiting the dedicated page on the ZEDXION official website. {% embed url="" %} {% hint style="warning" %} Please note that the ZEDXION ecosystem site is temporarily unavailable. {% endhint %} # Community **Twitter**: **Discord**: **ZEDXION Forum**: ### Public Telegram groups **Main chat**: **Italian ZEDXION Telegram community:** **Indonesian ZEDXION Telegram community:** {% hint style="info" %} All links on this page are currently inactive. Updated links will be provided soon, as they are currently under development. {% endhint %} # Grants and Bounties Since the inception of ZEDXION, the core team has facilitated the growth of the ZEDXION blockchain and also developed a set of tools for developers to be able to easily and quickly build extremely user-friendly decentralized applications (dApps). Our focus has primarily been on payment-centric communities like GoodDollar, Kolektivo, Comunitaria and PeeplEat. Now, we would like to see our tools used by even more high-quality projects, therefore, we stand ready to fund applicants for the ZEDXION Grants programs. ​The ZEDXION Future Dev Pool will be used to support projects that bring value to the ZEDXION ecosystem and users. We are especially interested in new high-potential payment centric communities, DAO initiatives, applications for new crypto users, NFTs, DeFi apps, projects that support current projects, and new categories we haven't even thought of yet! Although the grant process is not set in stone, the way it currently functions is that we announce bounties on an ongoing basis based on the project category. Please consult the next page to see the bounties that are currently available. Although the terms of grants may vary depending on the use case, candidates will generally be selected based on the following criteria: * Strength of the team following analysis of GitHub, LinkedIn, etc. * A written description of the project. We are not necessarily looking for long detailed text but our ability to understand clearly and see the value proposition will play an important role. * Tech and product quality based on any work done so far and/or product roadmap vision. **We invite submissions from** [**click here** ](https://hbfigtycii9.typeform.com/to/OfCHzmOY?utm_source=xxxxx\&utm_medium=xxxxx\&utm_campaign=xxxxx\&utm_term=xxxxx\&utm_content=xxxxx)**to apply** *** # ZEDXION Mobile Infrastructure Use Cases Given its easily customizable character, ZEDXION's mobile-centric infrastructure for issuing tokens and creating communities around them has a wide range of potential applications. Companies and other organizations can use either ZEDXION Studio or ZEDXION Studio in conjunction with a customized version of ZEDXION Wallet to create tokens to be used by users onboarded either to their proprietary app or a fork of ZEDXION Wallet. They can also whitelist businesses for the token community ecosystem and activate fiat on-ramps. In what follows, we would like to provide a few already implemented token community use cases for illustration. ## A Stable Currency for a Local Economy Community creators on ZEDXION Studio can either rely on a newly issued token or an already existing one. The Kolektivo project in Curaçao uses the popular DAI stablecoin to issue the CuraDAI stable currency pegged to the Antillean Guilder. CuraDAI is the token of a community and mobile app of the same name. The goal of the token is to facilitate the production and trading of locally produced goods and rewarding community members for engagement. The CuraDAI projects illustrates the low cost of creating and managing token communities and payment systems on ZEDXION. ## A Customer Rewards Token and Food Delivery app The PeeplEat project in Liverpool, UK, deploys ZEDXION to develop a mobile app for food delivery. The PEEPL token is designed to incentivize customer loyalty. With every order made through the PeeplEat app, customers automatically receive a reward in PEEPL tokens. The key advantages of using ZEDXION technology for powering customer rewards are automation and transparency. Rewards are automatically distributed based on the actual transactions and their amounts, and users can verify the amounts and total supply of the rewards token to ensure that it is not being inflated over time. ## A Festival Payments Token In November 2020, Bitazza used Zedx Studio to issue the [MYST](https://zedscan.net/address/0x510FAD1AD23064Ae881B129314EFdD9FDa6d4782/transactions) payments token on ZEDXION for the Mystic Valley Festival in Thailand. They also forked ZEDXION Wallet to create a customized mobile app for the festival. The app and token seamlessly powered the more than 15 thousand transactions made by attendees during the 3-day event. ZEDXION's mobile infrastructure can help event organizers reduce costs of managing internal payments and significantly improve the customer experience by replacing legacy solutions such as physical payment tokens or refillable cards at low cost. ## A Solution for Streamlining Charitable Donations The Communitaria project (formerly, Wikibank) has benefited from the ZEDXION B2B technology to solve an important problem in the charity industry. It launched a token backed one-to-one by the donated funds that can only be spent by the beneficiaries using the project's mobile app. The tokens can only be used for payment at the participating shops selling fresh produce. This has allowed Communitaria to reassure the donors that the funds they provide can only be used for the stated goal: enabling the beneficiaries to buy fresh food. Other NGOs and charitable projects can also target their donations better and more transparently by using the ZEDXION technology. # Network Details ### Mainnet * API: * * * * # ZEDXION Mainnet ### General Information | Block size | Block speed | Gas price | Patchset | Native token | Network ID | | ---------- | ----------- | --------- | -------- | ------------ | ---------- | | 20,000,000 | 5 seconds | 2.01 GWei | - | ZEDX | 83872 | * Network name: **ZEDXION** * ChanId: **83872** * Gas price: **2.01 GWei** * RPC * Official RPC: ​ * Archive node RPC: ​ * Explorer: ​ Please refer to [node-example](https://github.com/Zedscan/CoinNetwork/tree/master/node-example) if you wish to run your own node. ### Blockchain explorer **Zedscan** is the official blockchain explorer for ZEDXION. With this full-featured, open-source explorer you can view transactions, accounts & balances, access data via the API, and read and verify smart contracts. {% embed url="" %} ### # ZEDXION Testnet ### General Information | Block size | Block speed | Gas price | Patchset | Native token | Network ID | | ---------- | ----------- | --------- | -------- | ------------ | ---------- | | 20,000,000 | 5 seconds | 0.04 GWei | - | ZEDX | 40882 | * Network name: **ZEDXION** * ChanId: **40882** * Gas price: **0.04 GWei** * RPC * Official RPC: * Explorer: [​](https://testnet-explorer.zedscan.net) ### Blockchain explorer **Zedscan** is the official blockchain explorer for ZEDXION. With this full-featured, open-source explorer you can view transactions, accounts & balances, access data via the API, and read and verify smart contracts.. # ZEDXION Faucet The ZEDXION Faucet allows developers and users to receive a small amount of ZEDX tokens for testing purposes within the ZEDXION network. This service is beneficial for testing transactions, interacting with dApps, and exploring network functionalities without the need for actual tokens. ### How It Works The faucet provides 1 ZEDX token per request to the wallet address specified. This token distribution is designed for testing and development purposes only, with limits to prevent abuse. ### To use the faucet, follow these steps: * Enter Your Address: Input the address you wish to fund with ZEDX tokens in the designated field. * Click ‘Request’: After entering a valid address, press the Request button. * Receive Tokens: If the request is successful, 1 ZEDX token will be sent to the specified address. {% hint style="info" %} The faucet is intended for test use on the ZEDXION network. Abuse of the faucet may result in restrictions on its use. {% endhint %} {% hint style="warning" %} At present, the faucet service is temporarily paused. We are working on improvements and maintenance to enhance the service. For updates, please check back on this page or visit our [official channels](https://faucet.zedscan.net). {% endhint %} ### Technical Details * **Source Address**: The faucet tokens are dispensed from the address **0x79ae54E3eC5F122976A89D7C66F1459D7b38d050**. * **Token Limit**: 1 ZEDX per request. * **Frequency Limit**: Requests are limited to prevent spam and ensure fair access for all users. # Network Upgrades Major updates on the network level are introduced via forks. {% hint style="danger" %} Forks are used to introduce new functionality or fix security related issues. Node runners will receive instructions on how and when to update their nodes in the event of a fork. {% endhint %} Information related to forks along with upgrade information will be posted here. If any assistance is needed, feel free to reach out or ask questions through the forum or other channels. # Upgrade Guide For Nodes, Bootnodes and Validators {% hint style="info" %} This guide assumes that you have created your node via our [quickstart script](https://github.com/fuseio/fuse-network/blob/master/scripts/quickstart.sh). If you have built you own client using our spec then ensure that your client matches the official supported [client ](https://github.com/fuseio/fuse-network/blob/master/Dockerfile#L23)and you use the most up to date [chain spec](https://github.com/fuseio/fuse-network/blob/master/config/spec.json). {% endhint %} ### Prerequisites The update will pull the latest database from our latest snapshot so please ensure that you have at least 20GB disk space free before starting. ### Step 1 - CD to the location of quickstart.sh and update quickstart ``` cd wget -O quickstart.sh https://raw.githubusercontent.com/ecroxDev/Zedx/master/scripts/quickstart.sh ``` ### Step 2 - Run quickstart and agree to upgrade ``` sudo ./quickstart.sh Agree [Y] when prompted to upgrade Wait for script to complete ``` ### Step 3 - Verify Upgrade Check your node on our [health site ](https://status.zedscan.net)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync. ### Check your node on our [health site ](https://status.zedscan.net/)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync. # Upgrade Guide (explorer nodes) This guide is intended specifically for explorer nodes. Since we don't host snapshots for explorer DBs, some extra steps are required in order to update from V1.0.0 to V2.0.0. ### Step 1 - Stop all running containers ``` sudo docker stop $(sudo docker ps -q) ``` ### Step 2 - Pull the latest quickstart script ``` cd wget -O quickstart.sh https://raw.githubusercontent.com/ecroxDev/Zedx/master/scripts/quickstart.sh ``` ### Step 3 - Upgrade your DB using OEs upgrade tool It is highly recommended to take a back up of your database folder before attempting!. Follow the instruction here to upgrade from V13->V16 DBs . The data base is stored in \/fusenet/database/FuseNetwork/db/dee77c98f8210dbb/archive ### Step 4 - Update Client version in env file and rerun quickstart ``` vim .env Add the following (without quotes) "CLIENT=OE" Save and exit :w :q sudo ./quickstart.sh ``` ### Step 5 - Verify Upgrade Check your node on our [health site ](https://status.zedscan.net)It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync. # Block 13,800,000 Fork This fork Requires OE 3.2.6 or newer. ​[EIP 152](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-152.md)​ ​[EIP 1108](https://eips.ethereum.org/EIPS/eip-1108)​ ​[EIP 1283](https://eips.ethereum.org/EIPS/eip-1283)​ [EIP 1344](https://eips.ethereum.org/EIPS/eip-1344)​ ​[EIP 1706](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1706.md)​ ​[EIP 1884](https://eips.ethereum.org/EIPS/eip-1884)​ ​[EIP 2028](https://eips.ethereum.org/EIPS/eip-2028)​ ​[EIP 2565](https://eips.ethereum.org/EIPS/eip-2565)​ ​[EIP 2929](https://eips.ethereum.org/EIPS/eip-2929)​ [EIP 2930](https://eips.ethereum.org/EIPS/eip-2930)​ # FIP's The Zedx Improvement Proposal See FIP1 for more info ### What is a FIP? FIP stands for Zedx Improvement Proposal. A FIP is a design document providing information to the Zedx community, or describing a new feature for Zedx. The FIP should provide motivation and technical specification for the feature. | FIP | Description | Status | | ----------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------ | | [FIP-1](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-1.md) | Introduction and explanation about FIP's | Done | | [FIP-2](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-2.md) | Enabling delegation of fuse tokens to validators | Done | | [FIP-3](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-3.md) | Lowering the stake to run a validator node to 10K Zedx | Done | | [FIP-4](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-4.md) | Multi validators, validators can run multiple nodes | Undone | | [FIP-5](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-5.md) | Validators key splitting, validator will have separated keys | Undone | | [FIP-6](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-6.md) | Bridge implementation should be changeable by voting | Undone | | [FIP-7](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-7.md) | Tiny Ethereum Network transactions on end of cycle | Undone | | [FIP-8](https://github.com/fuseio/FIPs/blob/master/FIPS/fip-8.md) | Adjusting Block Rewards by the Validator's Stake | [Done](https://github.com/fuseio/fuse-network/pull/61) | # Consensus Consensus is a fault-tolerant mechanism that is used in blockchain systems to achieve the necessary agreement on the single state of the network. Zedx network is using a [Delegated Proof of Stake](https://en.bitcoinwiki.org/wiki/DPoS) (DPoS) consensus model. DPoS is a variation of [Proof of Stake](https://en.bitcoinwiki.org/wiki/Proof-of-stake) consensus. In PoS there are a set of validators that are responsible for keeping the network updated and validating the network's state. They do this in turns, every validator has their turn in line. On their turn the validator updates the network's state, and the rest of the validators check that the update is valid. ![](/files/Z6Du5i1VFSI2T797TrEx) Consensus contract is used to manage the list of the network validators and delegators BlockReward contract is calculates the reward amount that validators and delegators will receive on each block validation. The reward size is proportional to validator's stake. With Voting contract validators are vote on various changes on these 3 base level contracts. All those contracts are proxied with implementation that handles the logic. The implementations can be changed only by the Voting process. The bridge is used to transfer the Zedx native token between Zedx and Ethereum networks. ## Consensus [**0xf39f8f3223aDB78F87836eeD365ca858D876873a**](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) This contract is responsible for handling the network DPos consensus. The contract stores the current validator set and chooses a new validator set at the end of each cycle. The logic for updating the validator set is to select a random snapshot from the snapshots taken during the cycle. The snapshots are taken of pending validators, who are those which staked more than the minimum stake needed to become a network validator. Therefore the contract is also responsible for staking, delegating and withdrawing those funds. Stake amount for a validator is the sum of staked and delegated amount to it's address. This contract is based on `non-reporting ValidatorSet` [described in Parity Wiki](https://wiki.parity.io/Validator-Set.html#non-reporting-contract). {% hint style="info" %} minimum stake amount = 10,000 Zedx token cycle duration blocks = 57600 (approximately 2 days) {% endhint %} ## Block Reward [**0xd483605703A18Ce5CDac692B60E41c922a8A3b8E**](https://zedscan.net/address/0xd483605703A18Ce5CDac692B60E41c922a8A3b8E) This contract is responsible for generating and distributing block rewards to the network validators according to the network specs (1% yearly inflation). Another role of this contract is to call the snapshot/cycle logic on the Consensus contract This contract is based on `BlockReward` [described in Parity Wiki](https://wiki.parity.io/Block-Reward-Contract). ## Voting [**0x1c5ECaB05db92524118e7d95C45b3c121571834E**](https://zedscan.net/address/0x1c5ECaB05db92524118e7d95C45b3c121571834E) This contract is responsible for opening new ballots and voting to accept/reject them. Ballots are basically offers to change other network contracts implementation. Only network validators can open new ballots, everyone can vote on them, but only validators votes count when the ballot is closed. Ballots are opened/closed on cycle end. {% hint style="info" %} max number of open ballots = 100 max number of open ballots per validator = 100 / number of validators minimum ballot duration (cycles) = 2 maximum ballot duration (cycles) = 14 {% endhint %} ## Proxy Storage [**0x9b66D237552d25Bc7942eF67832663dc264c926B**](https://zedscan.net/address/0x9b66D237552d25Bc7942eF67832663dc264c926B) This contract is responsible for holding network contracts implementation addresses and upgrading them if necessary (via voting). # Contracts Overview ![](/files/K6K1nX8wWLQ7I4Humi9D) # Stake, Delegate and Withdraw The basic requirement to become a ZEDXION chain validator is to have a stake amount of at least 10,000 ZEDX tokens. The stake amount is the sum of staked and delegated ZEDX tokens of the address. This guide walks trough the process of using MEW (MyEtherWallet.com) in the process of using ZEDXION network.**Roadmap** - Those functionalities will be built into our Studio and will not require any technical knowledge in the future. ## Stake There are two options to stake (both should be called from the address which would be the validator) 1. 1.Send ZEDX tokens to the [consensus contract](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) - 0xf39f8f3223aDB78F87836eeD365ca858D876873a on the fuse network. 2. 2.Call the \`stake\` function on the [consensus contract](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) - 0xf39f8f3223aDB78F87836eeD365ca858D876873a on the fuse network. ## Delegate ZEDX token holders who don't want to run a node by themselves but still wish to participate in governing the network can delegate any amount to one of the validators.Delegating is done by calling the \`delegate\` function on the [consensus contract](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) with the validator address as data (see screenshot from MEW). ![delegate](https://3886961007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQROvzQPC4eD8u5AQhv%2Fuploads%2FfW2bi43f3TMgmwzi7wSZ%2Fimage.png?alt=media\&token=f30eb8a1-ff40-4f1e-9f73-89466ea2c83e) ## Withdraw Both stakers and validators can withdraw their ZEDX tokens, up to the staked/delegated amount, at any time. The withdrawn amount will be deducted from the validator stake amount, and if the stake amount becomes below the minimum stake amount - the validator will be removed from the ZEDXION chain validators list.There are two options to withdraw: 1. 1.Call the \`withdraw\` function on the [consensus contract](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) with one parameter - the amount to withdraw. This call is for stakers, and will reduce the stake amount of the sender address. 2. 2.Call the \`withdraw\` function on the [consensus contract](https://zedscan.net/address/0xf39f8f3223aDB78F87836eeD365ca858D876873a) with two parameters - validator address and amount to withdraw. This call is for both stakers (who can use their own address as the parameter) and for delegators to withdraw their delegated stake on a specific validator. ![withdraw option no. 1](https://3886961007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQROvzQPC4eD8u5AQhv%2Fuploads%2FyBpFV4W9N9vgpGyFEr76%2Fimage.png?alt=media\&token=0f715110-4b8d-4a35-81a6-93383d903f42) ![withdraw option no. 2](https://3886961007-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQROvzQPC4eD8u5AQhv%2Fuploads%2FTGmteQzEhEXuDVbibfVt%2Fimage.png?alt=media\&token=84a4f2a6-3c5e-41d7-b427-a845db9f82d2) # Vote ZEDXION chain functionality can be change by voting on the contracts implementations. New implementations can be deployed, and opened to vote by validators for others to decide on whether to accept/reject the changes. ## Open a new ballot In order to open a new vote, a validator needs to call the \`newBallot\` function on the [voting contract](https://zedscan.net/address/0x1c5ECaB05db92524118e7d95C45b3c121571834E) with the following params: * startAfterNumberOfCycles - number of cycles (minimum 1) after which the ballot is open for voting * cyclesDuration - number of cycles (minimum 2) for the ballot to remain open for voting * contractType * 1 - Consensus * 2 - BlockReward * 3 - ProxyStorage * 4 - Voting * proposedValue - address of the new implementation deployed for the relevant contract type * description - text description which should contain the reason/change introduced in the ballot ![new ballot](/files/jipoBMpgh1KBKhabEYos) ## Check ballot info Everyone can check all the ballots that were created using the \`getBallotInfo\` function. This function receives two params: * id - the ballot id * key - account address ![getBallotInfo](/files/zh12EOfyUXT227qK1Mta) ## Vote Everyone can vote on open ballots, after the start block has passed and until the end block hasn't yet. It's important to note that at the end of a vote, only validators count towards the final result. Voting is done by calling the \`vote\` function, which receives two params: * id - the ballot id * choice - 1 is accept, 2 is reject ![vote](/files/kyUNANNzlyCb0Euc3cOM) Some other useful functions on the [voting contract](https://zedscan.net/address/0x1c5ECaB05db92524118e7d95C45b3c121571834E) are: ## getQuorumState Returns the state of a specific ballot id: 1 - in progress, 2 - accepted, 3 - rejected ## getAccepted/getRejected Returns the number of accepts/reject of a specific ballot id. ## activeBallots Returns an array of active ballot ids. # End-of-Cycle Flow This is a description of the End-of-Cycle flow that completes the Cycle and handles rewards and enforces the consensus 1. BlockReward.reward is called every block and when the cycle ends calls the Consensus.cycle 2. Consensus.cycle is responsible for several functions. Eventually does the following two actions: 1. Sets the boolean Consensus.ShouldEmitInitiateChange to true 2. Calls BlockReward.onCycleEnd which sets the boolean BlockReward.shouldEmitRewardedOnCycle to true as well 3. The zedx-validator-app (zedxapp container on validator vms) checks the value of the above two booleans and when true calls the following two functions (two separate transactions): 1. Consensus.emitInitiateChange 2. BlockReward.emitRewardedOnCycle Note that only one validator can make this call successfully so the 1st one succeeds and all others fail. But it’s ok because those are 0-gas transactions. So actually the validator who is the next one to validate a block is the one who is successful in making those calls. 1. The above calls emit the following events: 1. Consensus.InitiateChange 2. BlockReward.RewardedOnCycle 2. The bridge oracles zedxoracle-initiate-change and zedxoracle-rewarded-on-cycle are responsible for listening to above events. 3. Those oracles should run on all validators and call submitSignature on the HomeBridgeNativeToErc contract in ZEDXION network - each validator should submit the signature for each of the oracles (events). 4. Once enough validators have submitted their signatures (majority of the current validators), an event CollectedSignatures is emitted by the home bridge (again one event for each one of the previous events in section 4). 5. The bridge oracle zedxoracle-collected-sigantures is responsible for listening to the CollectedSignature events and all validators should get it. The validator responsible for transmitting the transaction to mainnet is actually the last one to submit the signature in section 7 and its address is part of the event details so other validator oracles “know” it’s not their turn and skip the event. If a validator is down or out of money or infura is deaf - the next one in line (in the ValidatorSet) is responsible for transmitting to mainnet. 6. Eventually on mainnet we are supposed to see two transactions to the ForeignBridgeNativeToErc each cycle - one updating the new validators and one minting the ZEDX tokens which were created during this cycle on ZEDXION. Note that if the new validator set transactions fail on mainnet there’s a chance the minting will fails as well, because before transmitting it checks if all signatures are valid and there can be a situation where new validators were added on a cycle and were fast enough to submit their signatures on zedx end-of-cycle transactions but weren’t updated on mainnet due to failure of the 1st transactions so the 2nd one will actually contain “invalid” signatures from the mainnet perspective. Example for a successful flow (from 7/6/2020) 1. Consensus.emitInitiateChange transaction on ZEDXION - 2. BlockReward.emitRewardedOnCycle transaction on ZEDXION - # Contract Addresses | Contract | Mainnet address | Testnet address | | ------------ | ------------------------------------------ | ------------------------------------------ | | Consensus | 0xf39f8f3223aDB78F87836eeD365ca858D876873a | 0xf592E5385FB81D2f8F14446767f4B906D2035DcA | | Block Reward | 0xd483605703A18Ce5CDac692B60E41c922a8A3b8E | 0xDB1C584D1A0c7245b886E76890361Ff407E9CAfC | | Voting | 0x1c5ECaB05db92524118e7d95C45b3c121571834E | 0x6AAeAfB40a1dc202044F25eD76A67cfA226f30ed | # Resources & Tools ### DApp Management & Development Tools [The Graph](https://thegraph.com) supports Zedx data indexing, quierying and display. [Remix IDE](https://remix-project.org/): It's easy to deploy on Zedx with Remix, simply choose injected web3 and add the Zedx custom RPC to your Metamask. [JustSmartContracts](https://justsmartcontracts.dev/): another smart contract deployment tool for EVM chains. [OpenZeppelin Defender](https://defender.openzeppelin.com): Manage smart contract administration including access controls, upgrades and pausing. # TheGraph Build of The Graph, we expose a GraphQL API to access the data on the Zedx Network ## Deploying your own subgraph TheGraph, a decentralized protocol for indexing and querying chain data, supports the Zedx Netork.Go to to sign up and create your subgraph. * Follow the instructions for how to deploy the subgraph * in `subgraph.yaml`, the network name should be `fuse` ## Available Subgraphs Subgraphs that builded and maintained by the Zedx team, deployed on Zedx internal infrastructure or The Graph hosted service. ### Zedx Consensus on Zedx graph-node: # WalletConnect on Zedx [WalletConnect](https://walletconnect.com) is an **open-source protocol for data exchange between wallets and decentralized applications (dApps)**. The process takes place via a specialized server and the flow of data is encrypted in both directions. From the user’s perspective, although the exact details may vary from wallet to wallet, there are two ways of using WalletConnect. In the mobile-to-mobile mode, the user opens the website of the dApp that they are interested in, clicks the “connect wallet” tab there and chooses their preferred wallet. The desktop-to-mobile approach involves using the Wallet Connect-enabled wallet on the mobile phone to scan the QR code of the dApp displayed in the desktop browser. After the session, the dApp may be disconnected, and users are even advised to disconnect dApps for security reasons. For developers who wish to integrate the WalletConnect functionality into their dApps running on Zedx, we recommend using [this library](https://www.npmjs.com/package/@fuseio/walletconnect-web3-provider). # Important smart contracts # Zedx Token # Zedx Dollar # Major Deployed Contracts # Bridges # Ethereum ↔ Zedx GoodDollar Token # Ethereum ↔ Zedx ZED20 Tokens # BSC ↔ Zedx BNB # BSC ↔ Zedx Native # BSC ↔ Zedx ZED20 # Ethereum ↔ Zedx Native # How to become a validator The Zedx network is operated by validator nodes that are hosted by network participants from all around the world. The network allows entrepreneurs to easily plug payments to their products and on-board their users to a platform that allows them to pay, transact and access financial services in their favorite currency. All the access to the network is public and all the code is open source so it could be customized and localized to their needs. Any community that lives on the Zedx chain needs to pay a small fee to the validators of the network to validate its transactions in the community. The more communities and users conducting transactions, the more validators will earn as a reward for approving the transaction. This allows the network to grow organically as more usage in the system more network participants rewards grow.\\ ### What it means to be a validator? [Any entity that is holding the Zedx token can run a node](https://github.com/ZedScanTeam/Docs/blob/master/en/general-1/how-to-become-a-validator/broken-reference/README.md) that approves transaction in the network and in doing so receive rewards in the form of Zedx token (ZEDX). Validators are running special software that holds a copy of the Zedx blockchain and validating transactions in the network. Every 5 seconds, the network groups the latest transactions broadcasted to the system, validates them and signs them so they could never be changed in the future. For this work the validators receive block reward (X per block). A yearly inflation of 5% is distributed between all validators (the block reward is updated to accommodate this functionality). Validators are contributing their computer resources to maintain the network and need to have some technical knowledge in dealing with hosting this kind of software (see [Running a validator node](https://github.com/ZedScanTeam/Docs/blob/master/en/general-1/how-to-become-a-validator/broken-reference/README.md)) and [participate in the network governance through voting](https://github.com/ZedScanTeam/Docs/blob/master/en/general-1/how-to-become-a-validator/broken-reference/README.md). Validators are the guardians of the network and are in charge of not only maintaining it but also to steer it in its future through the governance mechanism that allows any holder of Zedx token to vote on important decisions and upgrades to the network in its development and resource allocation. ### Who should become a validator? * **Companies who build on the network** - Zedx open source stack allows many companies to collaborate on the same code-base. Allowing any company that is interested in using the Zedx services and code to join as a stakeholder is a new innovative approach to collaboration and partnerships. Any company that builds products on the network can own a piece of it and become a stakeholder. Running a node in the process will allow the company to earn rewards and grow as the network grows. The company can also use this open-source infrastructure to save costs for their development needs. Operating a node gives reliable access to the network, participation in its governance and aligns all the different interest behind the operation of the network. * **3rd party service providers** - We are starting to see many service providers creating and providing services across different blockchains. Services like KYC, exchanges, credit score providers, lenders, etc… Any service provider can become a stakeholder in the network and already today we are seeing the potential of cross-blockchain transactions uniting business processes between different entities using cryptography and without middlemen. * **Community operators on Zedx** - Community operators are the foremost stakeholders in the network and can upgrade themselves to a validator and thus provide better access to their clients. ### Who can become a validator (Technical requirements) * See [*Running a validator node*](https://github.com/ZedScanTeam/Docs/blob/master/en/general-1/how-to-become-a-validator/broken-reference/README.md)\_\_ ### Who shouldn’t become a validator (and what can he still do) * **Non technical users** - Running a node requires technical background in blockchain and web hosting. It’s not very complicated but also not trivial or basic. * **Simple holders** - We are looking for validators who are invested in the future of the network and are looking to take an active part. This is what the DPoS (Delegated Proof of Stake) mechanism was born to do. [You can delegate you Zedx token to a validator](https://github.com/ZedScanTeam/Docs/blob/master/en/general-1/how-to-become-a-validator/broken-reference/README.md) of your choosing. Not everybody that wants to earn rewards need to be a validator! Any token holder can delegate their Zedx token to a validator to earn rewards through the validator. ### How to become a validator? * Minimum of 10K tokens staked or delegated. In a DPoS blockchain it is required that all the validators have a staking requirement. The stake of 10K Zedx tokens needs to be locked in a contract to be eligible to become a validator. * Run a full node. # Getting started as a validator ## Pre-requirements In order to be a Zedx validator, you first must see that you meet the pre-requirements: * You know what it means to be a ZEDXION validator - How to become a validator * You have at least 10K ZEDX coins or you will have an aggregated delegation of at least 10K ZEDX coins ## How to become a ZEDXION validator To quickly become a validator, follow this steps: Please refer to [node-example](https://github.com/Zedscan/CoinNetwork/tree/master/node-example) if you wish to run your own node. For live support, contact us on [Telegram](https://t.me/) or [Discord](https://discord.gg/). Good luck and happy validating! # Getting started as on the Zedx testnet # Zeddex Contracts v2-v3 Zedx Below is the list of current Zeddex smart contracts deployed on the ZedScan Network. **v2 Zedx** "PancakeFactory": [0xeb3C930C1e0d3434ff917Ffd77aA813e7d79aE39](https://zedscan.net/address/0xeb3C930C1e0d3434ff917Ffd77aA813e7d79aE39) **- *****Relevant*** "PancakeRouterV2": [0x940C63f12ded30c7DD3d0143a1b84311473a56E2](https://zedscan.net/address/0x940C63f12ded30c7DD3d0143a1b84311473a56E2) **- *****Relevant*** "CakeToken": [0x5B0F21f60116b9463210C00C7A1A6A46E26BFA33](https://zedscan.net/address/0x5B0F21f60116b9463210C00C7A1A6A46E26BFA33) **- *****Relevant*** "SyrupBar": [0x72489d3eb547C9b7554aFc6Fc317eeBc44533111](https://zedscan.net/address/0x72489d3eb547C9b7554aFc6Fc317eeBc44533111) **- *****Relevant*** "DummyTokenV2": [0x1D7d8ec4E937E20127a3A733412cc48A3eaD6055](https://zedscan.net/address/0x1D7d8ec4E937E20127a3A733412cc48A3eaD6055) **- *****Relevant*** > **Note:** Token name - dMCV2(dMCV2). > **Warning:** It is a fictitious token. It is a fictitious token. It is not recommended for use in real financial transactions. "MasterChefV1": [0xe434F49A188266e4C8774f6A36cFA38F745E67de](https://zedscan.net/address/0xe434F49A188266e4C8774f6A36cFA38F745E67de) **- *****Relevant*** "MasterChefV2": [0xcdE77434E264AAEddf5d0D2C088fDD4A5de93B56](https://zedscan.net/address/0xcdE77434E264AAEddf5d0D2C088fDD4A5de93B56) **- *****Relevant*** "LPTokenV2": [0x0aB701C79842BBF6E54C748AE41BF30599a9516d](https://zedscan.net/address/0x0aB701C79842BBF6E54C748AE41BF30599a9516d) **- *****Relevant BUT No verified*** > **Note:** Token name - LP Token V2(LPV2). > **Warning:** It is a fictitious token. It is not recommended for use in real financial transactions. "DummyTokenV3": [0x6C7C64A6629866EFF8FFc2eFf4850Dc73d15aaF0](https://zedscan.net/address/0x6C7C64A6629866EFF8FFc2eFf4850Dc73d15aaF0) **- *****Relevant BUT No verified*** > **Note:** Token name - Dummy Token V3(DTV3). > **Warning:** It is a fictitious token. It is not recommended for use in real financial transactions. "CakeVault": [0xee1FB4734816F491e9C019e7e832441f5432fe25](https://zedscan.net/address/0xee1FB4734816F491e9C019e7e832441f5432fe25) **- *****Relevant*** "GnosisSafeL2": [0x7b5CbB38cb84d3d1580EBa93EbED551d0B7d7412](https://zedscan.net/address/0x7b5CbB38cb84d3d1580EBa93EbED551d0B7d7412) **- *****Relevant*** "GnosisSafeProxy": [0xEcF7dfB256414E94eEFEE3C4fAED88C0cb61297C](https://zedscan.net/address/0xEcF7dfB256414E94eEFEE3C4fAED88C0cb61297C) **- *****Relevant*** "CakePool": [0x9AA96373C959E39BcFf6d3F127438Ac4CE7F0652](https://zedscan.net/address/0x9AA96373C959E39BcFf6d3F127438Ac4CE7F0652) **- *****Relevant*** "CakeFlexiblePool": [0xBbF9028D4803FFac427c6c40c7cC2844cC04457E](https://zedscan.net/address/0xBbF9028D4803FFac427c6c40c7cC2844cC04457E) **- *****Relevant*** "PancakeStableSwapFactory": [0x1b308C3D8a3f015eFf686Ab6FDe241C7fBad7B6f](https://zedscan.net/address/0x1b308C3D8a3f015eFf686Ab6FDe241C7fBad7B6f) **- *****Relevant*** "PancakeStableSwapLPFactory": [0x8D65b8d6b00906E8331132332b312481E3b25F71](https://zedscan.net/address/0x8D65b8d6b00906E8331132332b312481E3b25F71) **- *****Relevant*** "PancakeStableSwapTwoPoolDeployer": [0xF851C14d5BfBc8715bd9EEF4D665AfFDaf76CF3d](https://zedscan.net/address/0xF851C14d5BfBc8715bd9EEF4D665AfFDaf76CF3d) **- *****Relevant*** "PancakeStableSwapThreePoolDeployer": [0x23dA5D81A1518A868c765535532f5A8B4420f16D](https://zedscan.net/address/0x23dA5D81A1518A868c765535532f5A8B4420f16D) **- *****Relevant*** "PancakeStableSwapTwoPoolInfo": [0xad03A1Cb4ee1f44f28833443781441cdF353188c](https://zedscan.net/address/0xad03A1Cb4ee1f44f28833443781441cdF353188c) **- *****Relevant*** "ICake": [0x58520a4B90c12BD91b4b3613D82cf712319a4A27](https://zedscan.net/address/0x58520a4B90c12BD91b4b3613D82cf712319a4A27) **- *****Relevant*** "MockToken": [0x91a48964C804534E172A7D19881037BdbE857A7b](https://zedscan.net/address/0x91a48964C804534E172A7D19881037BdbE857A7b) **- *****Relevant*** > **Note:** Token name - ZED V3 Emissions Dummy(ZED-V3-MOCK) > **Warning:** It is a fictitious token. It is not recommended for use in real financial transactions. \\ **v3 Zedx** "MasterChefV3": [0x65F5351D9d4410d90eDfceF4dC009AEA0Fd1AA2A](https://zedscan.net/address/0x65F5351D9d4410d90eDfceF4dC009AEA0Fd1AA2A) **- *****Relevant*** "SmartRouter": [0x7ffD51B65062C4b57Fa36DFd7B75757f4b46972C](https://zedscan.net/address/0x7ffD51B65062C4b57Fa36DFd7B75757f4b46972C) **- *****Relevant*** "SmartRouterHelper": [0xf71447A120AD9EFDeD3680eB4A2c37b3C9Ace2e0](https://zedscan.net/address/0xf71447A120AD9EFDeD3680eB4A2c37b3C9Ace2e0) **- *****Relevant*** "MixedRouteQuoterV1": [0xf8f6b61DD2Af72f62B23034839C93EF519e23c54](https://zedscan.net/address/0xf8f6b61DD2Af72f62B23034839C93EF519e23c54) **- *****Relevant BUT No verified*** "QuoterV2": [0x4ef8E058aFB580cE23136eD255E4E556c61234cd](https://zedscan.net/address/0x4ef8E058aFB580cE23136eD255E4E556c61234cd) **- *****Relevant*** "TokenValidator": [0x6dc6E85198CD7d395f0561586e9340b8d025ad3A](https://zedscan.net/address/0x6dc6E85198CD7d395f0561586e9340b8d025ad3A) **- *****Relevant BUT No verified*** "PancakeV3Factory": [0xe2dA1cd2EB807E26E3Eeeb6DC307C469a076f4E2](https://zedscan.net/address/0xe2dA1cd2EB807E26E3Eeeb6DC307C469a076f4E2) **- *****Relevant*** "PancakeV3PoolDeployer": [0x78b9b68D3D5c4a9c23Fb6389881015E6CADd0968](https://zedscan.net/address/0x78b9b68D3D5c4a9c23Fb6389881015E6CADd0968) **- *****Relevant*** "SwapRouter": [0x282eC28F1Ed041AEC3645c0De6f4b35C7907cAc5](https://zedscan.net/address/0x282eC28F1Ed041AEC3645c0De6f4b35C7907cAc5) **- *****Relevant*** "V3Migrator": [0x581E1245E8E8b16f4B8cc3525a33Bf128a428487](https://zedscan.net/address/0x581E1245E8E8b16f4B8cc3525a33Bf128a428487) **- *****Relevant*** "TickLens": [0xC4B745984B066aA4df0beD8B068B8CFeef115A82](https://zedscan.net/address/0xC4B745984B066aA4df0beD8B068B8CFeef115A82) **- *****Relevant*** "NonfungibleTokenPositionDescriptor": [0xb11cc31Ba54F7Bc9B869BBF10f200c54FCE2933B](https://zedscan.net/address/0xb11cc31Ba54F7Bc9B869BBF10f200c54FCE2933B) **- *****Relevant*** > **Note:** This contract to use TransparentUpgradeableProxy. The implementation can be found here [0xB94Fe8F0CA081134865182245abD842dFe7D939e](https://zedscan.net/address/0xB94Fe8F0CA081134865182245abD842dFe7D939e) "NonfungiblePositionManager": [0x4cFD33b6f43f75EF09e4B6EB380d4BEB6B2534C8](https://zedscan.net/address/0x4cFD33b6f43f75EF09e4B6EB380d4BEB6B2534C8) **- *****Relevant*** "PancakeInterfaceMulticall": [0xCb7c3908A8B06a498aBc3C74C0A24aC0f0966825](https://zedscan.net/address/0xCb7c3908A8B06a498aBc3C74C0A24aC0f0966825) **- *****Relevant*** "PancakeV3LmPoolDeployer": [0xCbC8FaB771bF65E08A96989e0AB24a844e046cFb](https://zedscan.net/address/0xCbC8FaB771bF65E08A96989e0AB24a844e046cFb) **- *****Relevant*** "FarmBoosterV3": [0xd8DfCAd673d256075c4BCA22b6F9D5EBE493c7aC](https://zedscan.net/address/0xd8DfCAd673d256075c4BCA22b6F9D5EBE493c7aC) **- *****Relevant*** "FarmBoosterV2": [0xc2d19c39296782b96C28A3895Fe1133b30EE51Ef](https://zedscan.net/address/0xc2d19c39296782b96C28A3895Fe1133b30EE51Ef) **- *****Relevant*** "FarmBoosterProxyFactory": [0x20a5C2fAB1116978909615a94205F9B246B9e5a8](https://zedscan.net/address/0x20a5C2fAB1116978909615a94205F9B246B9e5a8) **- *****Relevant*** "MasterChefV3Receiver": [0x2Fed44EBB861C9eF856727889daCB4a6D103F4b1](https://zedscan.net/address/0x2Fed44EBB861C9eF856727889daCB4a6D103F4b1) **- *****Relevant*** Multicall3: [0x9D7cd7e782eC90bA689F3C42b4888d01596D5f3C](https://zedscan.net/address/0x9D7cd7e782eC90bA689F3C42b4888d01596D5f3C) **- *****Relevant*** ZED-ZDEX: [0xFC23e49277A81FAe832f72E61ABCA9aa405f1248](https://zedscan.net/address/0xFC23e49277A81FAe832f72E61ABCA9aa405f1248) **- *****Relevant*** > **Note:** Token name - ZED LPs (ZED-LP) ZED-ZDEX 0.05%: [0xBCeE7f35DD80f232a9123F903831019D8bAa9D91](https://zedscan.net/address/) **- *****Relevant*** # Zeddex Contract v2-v3 BSC Below is the list of current Zeddex smart contracts deployed on the ZedSacn Network. **v2 bsc** "PancakeFactory": "0x35b4B2Fb6D3156E44A2CdD9006f81B0371B3D808", "PancakeRouterV2": "0xf1A2D2e4fAE9A4B3d816964ee76A8dFe6bDFC747" "CakeToken": "0x5C999E15B71de2bb8e651f0f999FB0Bc321a0DFe", "SyrupBar": "0x685F1B2D87c587fD55d5e404aC6156D964Be3dC7", "DummyTokenV2": "0xd1bB7564c93e9E370C5c7d0303ffd42B1fDb37fA", "MasterChefV1": "0x3C9f48ca2794E926E573e096908f3d45B39a2f66", "MasterChefV2": "0x22951bef1800db43BBe7F43714cd1a40A380c153", "lpTokenV2": "0x6B31621063fBE2Aa9c0b0Fe95612C5F23d91b806", "dummyTokenV3": "0xD3312e0FFe16A3e2f6B40A7f6Cccb8474BcF4000" "CakeVaultContract": "0x183AeA282e701289EEcBcd6081caa82358cA64D1" "GnosisSafeL2": "0xb78A5Fb873bb4d0945bb9Aca346ED10a4a0FC321", "GnosisSafeProxy": "0xfb0da1032d9E7027F88e9420F99d06DaF26E90B9", "CakePool": "0x40ad72a13Ac028bc39721a569490eDb8401CB0fc" "CakeFlexiblePool": "0x18D7d102e1098C8e29DEE57524c3a37b71e81f90" "PancakeStableSwapFactory": "0x8EDF7ad3dd72058C34eb3C171093BFa509Dd2087", "PancakeStableSwapLPFactory": "0x72778F608c7c7E06Da9B234Da8fd54ff12A413DA", "PancakeStableSwapTwoPoolDeployer": "0xBB7B74c3F178f46239Cc0F1941Ca059AD175F081", "PancakeStableSwapThreePoolDeployer": "0x1eE2FdDDC13a94990367839674b9EF40b6e57701", "PancakeStableSwapTwoPoolInfo": "0x09F46eb1F1222207127f06ed3d5b9CcD02bde580" "ICake": "0xc6D8772E332C34ae7671317c6BDFF2B5B161d19e" "MockToken": "0x8D86dBC90BAafBbCeDc816b24B6c42bf7cac263a" \\ **v3 bsc** "MasterChefV3": "0xf18D6cf6C507741B0E7104108B53DA84B7F16DaF", "SmartRouter": "0xC38B5c218CBD8814B0d7019763BFceDd26279370", "SmartRouterHelper": "0x568A1be490BE101e5cf60b733f222c872c840664", "MixedRouteQuoterV1": "0xed19a5282983460472970cC91CD46C2FA71F10f6", "QuoterV2": "0xd4a6561970B84a80fDa77CEE29f4b7C565aa1497", "TokenValidator": "0x3Bba1C436feC90b16875A08e652567776Ed9dD8c", "PancakeV3Factory": "0x3FF932a7f3fAb12451b8f2d197BEB7604Ef9cd2B", "PancakeV3PoolDeployer": "0x338a4fdD418207132339b445c7992Dd0Af2A04ac", "SwapRouter": "0x9D7cd7e782eC90bA689F3C42b4888d01596D5f3C", "V3Migrator": "0x430e5CD543926920374E072243536af5AeC3ca41", "TickLens": "0x4b1cfa29cbac9BA001843b0B8ED1b0BBac658de1", "NonfungibleTokenPositionDescriptor": "0xfD1Fa94aA06966754dE72A69c22196a9F0a5AB06", "NonfungiblePositionManager": "0x163A8A1552B0ec53041F3Ee79E76789930e40102", "PancakeInterfaceMulticall": "0x5d6AA674B4d5C7236367a57F1B2880342C405E50", "PancakeV3LmPoolDeployer": "0x7863e0f33aa9eE9f8074210865791128aCBd7b7B", "FarmBoosterV3": "0xEc122248cCa214B61f58432CC7Fbc5808C427d24", "FarmBoosterV2": "0xf2560F35aa5eEF18F5ccCdE0a44Be4Ed5D56a56E", "FarmBoosterProxyFactory": "0x66ee953323DcE64ed37fC4495547fc7DA8CEB453", "masterChefV3Receiver": "0xEBa8AA2C26FA109450f71711E86ecD3447D23800" ZED-BNB: 0x16DB5D50A704f80429155112173aFa9799bf2aD4 ZED-BNB 0.05% 0xDD616a83a5096507Ad17AcE1da1f66Fc2636AAc6 # API of ZedDex [https://dex.zedxion.com/api/farms/zedxpairs\ https://dex.zedxion.com/api/farms/bscpairs\ https://dex.zedxion.com/api/farms/v3/zedxpairs\ https://dex.zedxion.com/api/farms/v3/bscpairs\ https://graph.zedxion.com/subgraphs/name/zedxswap/exchange-zedx\ https://graph.zedxion.com/subgraphs/name/zedxswap/exchange-bsc\ https://graph.zedxion.com/subgraphs/name/zedxswap/exchange-v3-zedx\ https://graph.zedxion.com/subgraphs/name/zedxswap/exchange-v3-bsc](https://dex.zedxion.com/api/farms/zedxpairshttps://dex.zedxion.com/api/farms/bscpairshttps://dex.zedxion.com/api/farms/v3/zedxpairshttps://dex.zedxion.com/api/farms/v3/bscpairshttps://graph.zedxion.com/subgraphs/name/zedxswap/exchange-zedxhttps://graph.zedxion.com/subgraphs/name/zedxswap/exchange-bschttps://graph.zedxion.com/subgraphs/name/zedxswap/exchange-v3-zedxhttps://graph.zedxion.com/subgraphs/name/zedxswap/exchange-v3-bsc)