# Table of Contents - [Wallet | Taraxa Project](#wallet-taraxa-project) - [Welcome! | Taraxa Project](#welcome-taraxa-project) - [Set up validator node | Taraxa Project](#set-up-validator-node-taraxa-project) - [Become a Validator | Taraxa Project](#become-a-validator-taraxa-project) - [Ledger | Taraxa Project](#ledger-taraxa-project) - [Metamask | Taraxa Project](#metamask-taraxa-project) - [Taraxa's Network Connection Details | Taraxa Project](#taraxa-s-network-connection-details-taraxa-project) - [Consensus node hardware requirements | Taraxa Project](#consensus-node-hardware-requirements-taraxa-project) - [Taraxa Grant Program | Taraxa Project](#taraxa-grant-program-taraxa-project) - [Smart Contracts | Taraxa Project](#smart-contracts-taraxa-project) - [Register node directly on-chain | Taraxa Project](#register-node-directly-on-chain-taraxa-project) - [Liquid Staking | Taraxa Project](#liquid-staking-taraxa-project) - [Ficus Root Bridge | Taraxa Project](#ficus-root-bridge-taraxa-project) - [Staking | Taraxa Project](#staking-taraxa-project) - [Node upgrade & reset | Taraxa Project](#node-upgrade-reset-taraxa-project) - [Audit Report | Taraxa Project](#audit-report-taraxa-project) - [Solicit delegation | Taraxa Project](#solicit-delegation-taraxa-project) - [On-chain contracts | Taraxa Project](#on-chain-contracts-taraxa-project) - [Start building on Taraxa! | Taraxa Project](#start-building-on-taraxa-taraxa-project) - [Register node via community site | Taraxa Project](#register-node-via-community-site-taraxa-project) - [Staking directly on-chain | Taraxa Project](#staking-directly-on-chain-taraxa-project) - [Connecting to Taraxa | Taraxa Project](#connecting-to-taraxa-taraxa-project) --- # Wallet | Taraxa Project [PreviousWelcome!](/) [NextMetamask](/wallet/metamask) Last updated 1 year ago Was this helpful? [](#taraxa-supports-all-eth-compatible-wallets) Taraxa supports all ETH-compatible wallets ----------------------------------------------------------------------------------------------- The Taraxa network is backwards-compatible with Ethereum, that means any ETH-compatible wallet that allows you to add a custom, EVM-compatible network will work with Taraxa! This means that, * All Ethereum wallets can be used on Taraxa * All Taraxa wallets can used on Ethereum Pretty straightforward 😊 [](#word-of-advice-get-a-hardware-wallet) Word of advice: get a hardware wallet ------------------------------------------------------------------------------------ Given all the hacks and scams in crypto, we recommend that everyone get a hardware wallet. Since the private key on a hardware wallet is never exposed, it is much safer (not fool-proof, nothing is fool-proof unfortunately) than a software wallet on a phone or PC. [](#getting-started) Getting started ----------------------------------------- Here are a few examples of wallets supported by Taraxa. πŸ’΅ [![Cover](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FYt28invr5oRr1aWVySVF%252F800px-MetaMask_Fox.svg%255B1%255D.png%3Falt%3Dmedia%26token%3D0d70a631-e2f2-40d1-b0d6-dfef01dde25e&width=245&dpr=4&quality=100&sign=f3b46459&sv=2)\ \ Metamask](/wallet/metamask) [![Cover](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FLqlOGTemdkYMuWI868O9%252FLedger-Nano-X-Gear%255B1%255D.jpg%3Falt%3Dmedia%26token%3D4f3f367f-56b5-460d-b9dd-a9f02734dcdb&width=245&dpr=4&quality=100&sign=e387489e&sv=2)\ \ Ledger (hardware wallet)](/wallet/ledger) --- # Welcome! | Taraxa Project [](#taraxa-is-the-next-gen-layer-1) Taraxa is the next-gen Layer-1 ----------------------------------------------------------------------- Taraxa is an EVM-compatible smart contract platform based on t-Graph consensus utilizing blockDAG, with many world-first technical innovations. Founded by two Stanford Engineers in 2018, Taraxa launched its mainnet on April 3, 2023 and has since consistently built up awareness and market traction, gaining widespread recognition for its innovations on top of the next-gen blockDAG architecture, * First Native EVM Integration in blockDAG * First PoS blockDAG * First Dynamic blockDAG Proposal Rate * First True Finality in blockDAG These innovations give Taraxa unsurpassed throughput at scale without security or decentralization tradeoffs, paving the way for the next infrastructural upgrade from blockchain to blockDAG. Taraxa’s vibrant community has been building DeFi and social analytics dApps organically during the bear market as the development team continues to focus on driving awareness, adoption, building demonstrative dApps, and rounding out necessary infrastructure tech such as cross-chain bridging. [](#undefined) ------------------ [](#solving-real-world-problems) Solving real-world problems ----------------------------------------------------------------- It is our firm belief that technologies are meant to solve real world problems, and cannot be developed in isolation. The applications we build, will build, and will enable our community to build, will (and do) have concrete functionality implications to how the public ledger infrastructural layer is designed and implemented. To this end, the application and the ledger need to be tightly coupled to create the most optimized outcomes. This is why we created Taraxa. [](#join-the-ecosystem) Join the ecosystem! ------------------------------------------------ #### [](#for-users-check-out) For users, check out, * Our most recent development roadmap #### [](#for-developers-check-out) For developers, check out, [NextWallet](/wallet) Last updated 8 months ago Was this helpful? Get started with Taraxa's πŸ‘‹ [creating a wallet for Taraxa](/wallet) [Stake your TARA](/staking) [Network explorer](https://explorer.mainnet.taraxa.io/) [Building on Taraxa](/develop/start-building-on-taraxa) [Becoming a Validator](/become-a-validator) [technical architecture](/tech-whitepaper/taraxa-architecture) --- # Set up validator node | Taraxa Project [PreviousBecome a Validator](/become-a-validator) [NextConsensus node hardware requirements](/become-a-validator/consensus-node-hardware-requirements) Last updated 11 days ago Was this helpful? [](#full-consensus-node) Full Consensus Node ------------------------------------------------- Instructions relating to running a validator node on the Mainnet are mostly identical or highly similar than those for the . Here's how you can install a node on Linux. Copy mkdir -p mainnet/config cd mainnet wget https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.yml docker-compose up -d docker-compose logs Because the Taraxa network state has gotten very large, it takes quite a long time to sync. An alternative is to sync from a snapshot, which will drastically cut down on the amount of syncing time and can get your node up & running much more quickly. \>> << [](#lite-consensus-node-beta) Lite Consensus Node (beta) ------------------------------------------------------------- You could also choose to run a lite-version of the consensus nodes, with ~90% SSD savings. It operates exactly the same as a full node, but prunes most of the historical states, keeping just a few recent Periods. Please follow the . > Lite node requires pruning, and you need to restart your lite node for pruning to start. It's recommended to set up a script to periodically restart the lite node to keep disk space usage to a mininum. Because the Taraxa network state has gotten very large, it takes quite a long time to sync. An alternative is to sync from a snapshot, which will drastically cut down on the amount of syncing time and can get your node up & running much more quickly. \>> << 🌱 βš™οΈ [Testnet](/node-setup/testnet_node_setup) [Latest snapshots](/node-setup/syncing-from-snapshot) [Latest snapshots](/node-setup/syncing-from-snapshot) [instructions on light consensus nodes](/node-setup/lite-consensus-node-beta#1.-lite-consensus-node-on-the-taraxa-mainnet) --- # Become a Validator | Taraxa Project [PreviousTaraxa's Network Connection Details](/wallet/taraxas-network-connection-details) [NextSet up validator node](/become-a-validator/set-up-validator-node) Last updated 2 months ago Was this helpful? [](#becoming-a-validator-on-the-mainnet) Becoming a Validator on the Mainnet --------------------------------------------------------------------------------- We've launched our Mainnet network! You can now join the Mainnet as a validator. To become a validator, you need to do and be aware of the following, * (requires KYC), OR [](#quick-faqs) Quick FAQs ------------------------------- ### [](#do-validator-operators-need-to-put-up-collateral-or-self-stake) Do Validator operators need to put up collateral or self-stake? There is a 1,000 TARA self-staking requirement to register with the on-chain DPoS contract. At the time of this writing 1,000 TARA isn't a lot of money, and this is not meant to be collateral, but rather to deter spamming attacks on the DPoS contract. ### [](#how-do-validators-produce-blocks) How do Validators produce blocks? Validators receive delegation of TARA tokens. A minimum delegation of 500k TARA is required to start producing blocks, and each Validator can take on a maximum of 80 million TARA of delegated stake. The more delegated TARA a Validator has, the more likely and more frequently it will produce blocks. ### [](#how-are-validators-rewarded) How are Validators rewarded? Validators charge a commission, which is a percentage of the total staking yields that come from the TARA that has been delegated to it. ### [](#where-can-i-see-a-list-of-current-validators) Where can I see a list of current Validators? You can see a list of current Validators, their delegation, yields efficiency and commissions on the . 🌱 [Set up a validator node](/become-a-validator/set-up-validator-node) [Register your validator node on the community site](/become-a-validator/register-node-via-community-site) [Register your validator node by directly interacting with the on-chain DPoS contract](/become-a-validator/register-node-directly-on-chain) [Solicit delegation](/become-a-validator/solicit-delegation) [Node upgrade & reset operations](/become-a-validator/node-upgrade-and-reset) [Taraxa Community Site's Staking section](https://community.taraxa.io/staking) --- # Ledger | Taraxa Project [PreviousMetamask](/wallet/metamask) [NextTaraxa's Network Connection Details](/wallet/taraxas-network-connection-details) Last updated 2 years ago Was this helpful? [](#create-a-taraxa-wallet-on-ledger) Create a Taraxa wallet on Ledger --------------------------------------------------------------------------- Since Taraxa is ETH-compatible, all you need to do is create a regular ETH wallet on Ledger. We'll use this in conjunction with Metamask to get up & running on the Taraxa network! Here are a few guides you should look through, * If you're completely new to Ledger, please check out their guide * Once you get your device set up and running, you'd want to follow onto your Ledger device, you can follow this official guide from Ledger on how to do * After you have the Ethereum app installed, you should follow , make sure the accounts are Ethereum accounts Now that you have an Ethereum wallet on your Ledger, let's connect it with Metamask to get it working with the Taraxa network. [](#connect-ledgers-with-taraxa-through-metamask) Connect Ledger's with Taraxa through Metamask ---------------------------------------------------------------------------------------------------- Because the Taraxa Network is ETH-compatible, the Ethereum App actually works fine with the Taraxa Network, but needs to work through Metamask. Here's how it works, it's pretty simple, * You have an ETH address on your Ledger hardware wallet, if you're new to Ledger you can check out their official guides according to which hardware device you have * Follow the guide by following Ledger's official documentation * Use Metamask to send / receive TARA, and it will be signed by your wallet on the Ledger ETH app This works because the Taraxa network is compatible with Ethereum's address and cryptography, so when Metamask sends a request for signature for the Taraxa network to the Ledger's ETH app, everything just works. πŸ’΅ [Getting Started](https://support.ledger.com/hc/en-us/sections/4404369606801-Getting-Started?docs=true) [Ledger's guide on how to install the Ethereum app](https://support.ledger.com/hc/en-us/articles/360009576554-Ethereum-ETH-?support=true) [Ledger's guide on adding new accounts to the hardware wallet](https://support.ledger.com/hc/en-us/articles/4404389482641-Add-your-accounts?docs=true) [Getting Started](https://support.ledger.com/hc/en-us/sections/4404369606801-Getting-Started?docs=true) [How to access your Ledger Ethereum (ETH) account via Metamask](https://support.ledger.com/hc/en-us/articles/4404366864657-Set-up-and-use-MetaMask-to-access-your-Ledger-Ethereum-ETH-account?docs=true) [Add the Taraxa network into Metamask](/wallet/metamask) --- # Metamask | Taraxa Project [PreviousWallet](/wallet) [NextLedger](/wallet/ledger) Last updated 2 months ago Was this helpful? [](#create-a-taraxa-wallet-on-metamask) Create a Taraxa wallet on Metamask ------------------------------------------------------------------------------- Since Taraxa is ETH-compatible, all you need to do is create a regular ETH wallet on Metamask. Here's the official guide from Metamask on , if you don't already have one you'd like to use with Taraxa. [](#adding-custom-networks-in-metamask) Adding Custom Networks in Metamask ------------------------------------------------------------------------------- Most ETH-compatible wallets allow you to add a "custom network". As long as that network is ETH-compatible - which Taraxa is - everything just works. You have two options to add Taraxa as a custom network into Metamask: adding it , or doing it manually yourself. [](#undefined) ------------------ [](#add-taraxa-to-metamask-via-chainlist) Add Taraxa to Metamask: via Chainlist ------------------------------------------------------------------------------------ The first way to get add the Taraxa network onto Metamask is via . We highly recommend that you reference . Here's a step-by-step guide for adding Taraxa to Metamask via Chainlist, * Go to * Click on "Connect Wallet" on the upper-right corner * Choose "Metamask" in the pop-up * Once Metamask is connected, your wallet address will show up on the upper right corner * Next, search for "Taraxa" in the search bar, and you should be able to see Taraxa's Mainnet and Testnet networks in the search results * Click on "Add Chain" for the network you wish to join, for example, the Taraxa Mainnet * Next, Metamask will ask if you'd like to switch to the new network * Finally, when you open the Metamask browser plugin, you should be able to see "Taraxa Mainnet" at the top, and you're done! [](#undefined-1) -------------------- [](#add-taraxa-to-metamask-via-custom-networks) Add Taraxa to Metamask: via Custom Networks ------------------------------------------------------------------------------------------------ Here's a step-by-step guide for adding Taraxa to Metamask via manually configuring custom networks, * Open the Metamask browser plugin, click on the network selector button, which will show you a list of networks, at the bottom, there's a "Add Network" button, click on that * A browser tab will pop out and show Metamask's Add a Network settings, choose "Add a network manually" at the bottom * Here you'll see a brief form for you fill in details of Taraxa's network * After saving, open the Metamask browser plugin, you should be able to see "Taraxa Mainnet" at the top, and you're done! You'll see a Metamask pop-up, here's where you can confirm the are correct, and then click on "Approve" You also have the option to simply add the Taraxa network into Metamask manually. The end result is exactly the same. We highly recommend that you reference . You can reference the connection details in the page, here is a screenshot for connecting to the Taraxa's mainnet network, once you finished entering the connection details just click on "Save" πŸ’΅ [How to create an additional account in your wallet](https://metamask.zendesk.com/hc/en-us/articles/360015289452-How-to-create-an-additional-account-in-your-wallet) [via Chainlist](https://chainlist.org/chain/841) [Chainlist](https://chainlist.wtf/) [Metamask's Chainlist Documentation](https://metamask.zendesk.com/hc/en-us/articles/360058992772) [Chainlist](https://chainlist.wtf/) [Taraxa network's connection details](/wallet/taraxas-network-connection-details) [Metamask's Custom Network Documentation](https://metamask.zendesk.com/hc/en-us/articles/360043227612-How-to-add-a-custom-network-RPC#h_01G63GGJ83DGDRCS2ZWXM37CV5) [Taraxa's network connection details](/wallet/taraxas-network-connection-details) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FR10SEdPXYeQQB0lc2rGw%252Fimage.png%3Falt%3Dmedia%26token%3D84dfc4ee-7bf1-4deb-9487-e16937bff72f&width=768&dpr=4&quality=100&sign=8771f39&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252F7mhg443zjE5UUsbFkpRD%252Fimage.png%3Falt%3Dmedia%26token%3Db49df3a2-d38e-413f-8e17-a5704aa1a5a1&width=768&dpr=4&quality=100&sign=fbf9b0d7&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FOvWRWYrbEZUQ2vPWXb1K%252Fimage.png%3Falt%3Dmedia%26token%3Db7df565b-c6b3-4726-a29c-50c4cdf40544&width=768&dpr=4&quality=100&sign=d6258972&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FTYtkMemKfGAli4zlnOdU%252Fimage.png%3Falt%3Dmedia%26token%3D093ca388-6f0a-4129-98ad-779cac47e3e9&width=768&dpr=4&quality=100&sign=84ae4d77&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FoccMv6JA6HeFycJSilAQ%252Fimage.png%3Falt%3Dmedia%26token%3Dd730e67c-66d7-4639-9b6d-4bd09e91ce9e&width=768&dpr=4&quality=100&sign=2702834&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FcHQUfiQpqmJheDxMsQtN%252Fimage.png%3Falt%3Dmedia%26token%3D74daffd3-d837-486f-b917-05b8c6a10e68&width=768&dpr=4&quality=100&sign=1f744db7&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252Fzx4UQKP4wXCD3VcL2yaK%252Fimage.png%3Falt%3Dmedia%26token%3D288f0868-52d3-4ccd-9bd2-335faff05ca4&width=768&dpr=4&quality=100&sign=f33a0861&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FeGIanjXMFOpU78EXaJ36%252Fimage.png%3Falt%3Dmedia%26token%3D13c4c8b5-5792-4667-9fef-51c1bb4e3da2&width=768&dpr=4&quality=100&sign=c2c0da24&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FQRMuIVMvprm765KxHKbq%252Fimage.png%3Falt%3Dmedia%26token%3Db3445458-6b04-4f8b-a26a-a31d086f0c90&width=768&dpr=4&quality=100&sign=81e7e0f0&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FFy5DSWJobnAayCbmtPDc%252Fimage.png%3Falt%3Dmedia%26token%3Defb07642-77ce-43d1-b8e4-d7f6b4ed1db9&width=768&dpr=4&quality=100&sign=2424dac3&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FIACgCuWKoA1mX0wd9peu%252Fimage.png%3Falt%3Dmedia%26token%3Daef7f4f0-fc50-45d9-8a84-404e1f0c0fd1&width=768&dpr=4&quality=100&sign=4053ad6d&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FISuYOgLMxasNIaFzUE2J%252Fimage.png%3Falt%3Dmedia%26token%3D5f4627c7-be58-4cd2-9f1d-c79532bce7b6&width=768&dpr=4&quality=100&sign=3ee0047&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FswEKPEJm6L3bcod377VD%252Fimage.png%3Falt%3Dmedia%26token%3Db290230b-8d51-423e-b6c7-14a0c795f703&width=768&dpr=4&quality=100&sign=1c3f817b&sv=2) --- # Taraxa's Network Connection Details | Taraxa Project [PreviousLedger](/wallet/ledger) [NextBecome a Validator](/become-a-validator) Last updated 1 year ago Was this helpful? [](#taraxa-mainnet-connection-details) Taraxa MAINNET connection details ----------------------------------------------------------------------------- * Name: Taraxa Mainnet * RPC: * Chain ID: 841 * Currency Symbol: TARA * Explorer: [](#taraxa-testnet-connection-details) Taraxa TESTNET connection details ----------------------------------------------------------------------------- * Name: Taraxa Testnet * RPC: * Chain ID: 842 * Currency Symbol: TARA * Explorer: πŸ’΅ [https://rpc.mainnet.taraxa.io/](https://rpc.mainnet.taraxa.io/) [https://explorer.mainnet.taraxa.io/](https://explorer.mainnet.taraxa.io/) [https://rpc.testnet.taraxa.io/](https://rpc.testnet.taraxa.io/) [https://explorer.testnet.taraxa.io/](https://explorer.testnet.taraxa.io/) --- # Consensus node hardware requirements | Taraxa Project [](#lite-consensus-node) Lite Consensus Node ------------------------------------------------- Minimum system requirements for the Lite Consensus Node is, * 4 CPU * 8GB Memory * 100GB SSD Most consensus nodes on the network are lite consensus nodes. The only difference between a lite node and a full node is that the lite node prunes historical state upon node restart (many community nodes periodically restar their lite nodes), while the full nodes keep everything. Beyond the state pruning, there is otherwise no difference between the full consensus node and the lite consensus node. [](#full-consensus-node) Full Consensus Node ------------------------------------------------- Minimum system requirements for the Full Consensus Node is, * 4 CPU * 8GB Memory * 1.5TB SSD The full node's state db grows very quickly, especially when transaction load is high. Over time the storage requirements will keep growing. We of course encourage you to run a full node if storage is not too big of a concern for you, just be aware that the disk requirement will keep growing. [PreviousSet up validator node](/become-a-validator/set-up-validator-node) [NextRegister node via community site](/become-a-validator/register-node-via-community-site) Last updated 2 months ago Was this helpful? 🌱 πŸ–₯️ --- # Taraxa Grant Program | Taraxa Project [PreviousAudit Report](/ficus-root-bridge/audit-report) [NextStart building on Taraxa!](/develop/start-building-on-taraxa) Last updated 8 months ago Was this helpful? [](#mission) Mission ------------------------- Taraxa is an open-source, permissionless Layer-1 ecosystem that promotes and supports the development and adoption of useful and creative ways to leverage decentralization to solve problems. To this end, the Taraxa community has voted to institute a Grant Program to help seed promising projects built using the Taraxa network. [](#undefined) ------------------ [](#application) Application --------------------------------- Any individual, team, and organizations of any type are welcome to apply to the Taraxa Grant Program. The initial application into the Taraxa Grant Program will require the following details, * Core team members' profiles * A Taraxa Community Site account with successfully passed KYC * A working prototype or demo of what they want to build * Benefits your project will bring to the Taraxa ecosystem and its community * Technical and go to market roadmaps * Measurable milestones tied to use of funds used for grant disbursements \>> << [](#undefined-1) -------------------- [](#review-process) Review Process --------------------------------------- Applications will be reviewed on a rolling basis. We may reach out to you to request additional information and/or schedule a call as necessary. The team will typically respond to applications within 2-3 weeks. Applicants will be notified of decisions via email. [](#undefined-2) -------------------- [](#evaluation-criteria) Evaluation Criteria ------------------------------------------------- Taraxa Grant Program is meant to fund projects that are, * Decentralized: only truly permissionless and decentralized projects will be considered. * Open-source: only projects founded on the idea of open collaboration and innovation will be considered. * Uniquely contributes to Taraxa’s ecosystem: projects that add unique value to the Taraxa ecosystem will be prioritized. This can be a truly unique piece of technology or application, or it could simply be something that Taraxa’s ecosystem sorely lacks but already exists elsewhere. * Clear use of funds: thoughtful, practical, and truthful explanation of how funds will be used to accomplish measurable milestones. * Ability to execute: convince us that you have what it takes to not just execute but also persist till your vision comes to fruition. Taraxa Grant Program is NOT meant to be used for, * Marketing: to ensure regulatory compliance, grants will only be given to fund technical development, not marketing. * Substitute for venture funding: to ensure that ecosystem projects simultaneously can stand on their own with sufficient market and user validation, as well as minimizing the long-term undue influence of the Taraxa Grant Program on any ecosystem project, ensuring their independence. [](#undefined-3) -------------------- [](#grant-disbursement) Grant Disbursement: ------------------------------------------------ All grant funds will be disbursed through Taraxa's to the applicant's account with an approved KYC. Grants are disbursed according to the achievement of measurable milestones tied to use of funds as agreed upon between the applicant and the dev team conducting reviews. The Taraxa dev team will be available to meet with grant recipients on a regular basis, not only to receive updates on projects but also to see what help beyond the funds the dev team can help to provide. \>> << πŸ’₯ [Apply for a grant!](https://www.taraxa.io/grant/apply) [Community Site](https://community.taraxa.io/) [Apply for a grant!](https://www.taraxa.io/grant/apply) --- # Smart Contracts | Taraxa Project [PreviousConnecting to Taraxa](/develop/connecting-to-taraxa) [NextRemix](/develop/smart-contracts/remix) Last updated 2 years ago Was this helpful? [](#taraxa-is-eth-compatible) Taraxa is ETH-Compatible! ------------------------------------------------------------ Since the Taraxa network is compatible with Ethereum's RPC specifications, almost all tools in the ETH ecosystem will just work with Taraxa without any problems. [](#resources-to-get-started-asap) Resources to get started ASAP --------------------------------------------------------------------- Here are some resources to get you started on deploying smart contracts on Taraxa. * Remix: * Hardhat: simply update and add Taraxa as a JSON-RPC network, with * Truffle: simply update and add Taraxa as a JSON-RPC network, with πŸ““ [step-by-step example with Remix](/develop/smart-contracts/remix) [Hardhat's configuration](https://hardhat.org/hardhat-runner/docs/config) [Taraxa's network connection details](/wallet/taraxas-network-connection-details) [Truffle's configuration](https://trufflesuite.com/docs/truffle/reference/configuration/) [Taraxa's network connection details](/wallet/taraxas-network-connection-details) --- # Register node directly on-chain | Taraxa Project [PreviousRegister node via community site](/become-a-validator/register-node-via-community-site) [NextSolicit delegation](/become-a-validator/solicit-delegation) Last updated 1 year ago Was this helpful? You can register a validator node by directly communicating with the on-chain DPoS contract and skip the community site altogether. Here are instructions on how to do this. ### [](#id-0.-important-wallet-used-to-register-a-node-is-the-owner-of-that-node) 0\. IMPORTANT: wallet used to register a node is the owner of that node Validator node registration is an on-chain transaction. The wallet you use to register a node is the "owner" of that node. This means once a node is registered, the "owner wallet" is now required to, * Change the validator node's commission rate * Claim commission rewards earned by the validator node A single owner wallet can register multiple validator nodes and become their owner, this makes it easy to manage multiple validator nodes in aggregate. **Please safeguard your validator nodes' owner wallet!** ### [](#id-1.-upload-the-dpos-contract-solidity-interface-into-remix) 1\. Upload the DPoS contract Solidity interface into Remix Go to , and upload Taraxa's DPoS contract's Solidity interface. In the pop-up, paste in the following link to the Taraxa DPoS contract Solidity interface, Copy https://raw.githubusercontent.com/Taraxa-project/taraxa-evm/master/taraxa/state/contracts/dpos/solidity/dpos_contract_interface.sol After it's been uploaded you should be able to see it in the IDE on the right side, ### [](#id-2.-compile-the-interface) 2\. Compile the interface Make sure the interface file is selected, Go into the compiler section by clicking on the icon on the left side. Once you're in the section, double check the big blue compile button indeed says "Compile dpos\_contract\_interface.sol". If the Compile button doesn't say that, that means the interface file wasn't selected in the file explorer section as indicated above, please go back and make sure the right file is selected. Click the Compile button. Once it has been compiled you should see a green checkmark on the compiler icon on the left sidebar, and additional options will show up below the compile button. ### [](#id-3.-set-up-the-interface) 3\. Set up the interface Once you've switched your Metamask to the Taraxa Mainnet, go to the "Deploy & Run Transactions" section in Remix. At the top, change "Environment" to "Injected Provider - Metamask". Once you've done that, make sure to double-check that * The wallet under "Account" is the wallet you want to use, since setting up a validator node will require gas fees but also a 1000-TARA minimum self-delegation, so make sure the wallet connected has sufficient funds * The right compiled interface from the previous step is loaded. Look at the "Contract (Compiled by Remix)" section and make sure the filename is the same as the one in the file explorer. Next, we tell Remix where the DPoS contract is located. Go the "At Address" field towards the bottom of the screen, and enter the following address. This is where Taraxa's precompiled DPoS contract is located. Copy 0x00000000000000000000000000000000000000fe Go ahead and click the "At Address" button, and it should show up under "Deployed Contracts". Go ahead and expand the interface by clicking on the chevron ">" and you'll see a list of all the commands you can send to the contract. ### [](#id-4.-set-the-self-delegation-value) 4\. Set the self-delegation value When a new validator node is registered, there's a 1000 TARA self-delegation requirement. This means 1000 TARA will need to be delegated from the registration wallet, or the owner wallet, to the DPoS contract. Within the "Deploy & Run Transactions" section of Remix, navigate back towards the top and you'll see a "Value" field. This field defines how many tokens will be transferred to the contract in this transaction. Set the following, * Value to 1000, since we're self-delegating 1000 TARA * Unit to "Ether", this may be confusing but since Remix isn't aware of the Taraxa Network's token name, it calls all tokens for EVM-compatible networks "Ether", don't worry, it's sending TARA (since you're on the Taraxa Network) Once these values are set let's move to the next step. ### [](#id-5.-register-a-validator-node) 5\. Register a validator node Now we register a validator. Let's run a few tests first. Assume that the validator is completely new (hence we're registering one), let's see if the network thinks it is an eligible validator. As an example, assume the validator's public address is: `0xd423413a6b4bb11e584d7de3acce40d95da6c3b1`. Let's try calling `getValidator`, with the node's public address, On the right side, we get an error as returned value, "Validator does not exist", which is expected since this is a brand new node. Now let's register this node by calling the `registerValidator` function. The function takes 6 arguments, we're going to enter the first 4 and leave the last two blank, since the last two really has no impact on the node's function or economics, and are simply informational. Here are instructions on how to find the node's, The commission field takes in an integer that is 100 multiplied by the commission percentage, here are a few examples of how a commission percentage is translated into the parameter entered into the `registerValidator` function, * 0.01% commission -> 1 * 1% commission -> 100 * 10% commission -> 1000 * 100% commission -> 10000 We get all the information and enter it into the fields, **BUT DON'T PRESS TRANSACT YET**. Press the "transact" button and check for the results in the console, located the bottom-right side of the page. If the transaction is successful, you should see a green checkmark at the top, the status message indicating the transaction has been successfully executed. ### [](#id-6.-confirm-validators-registration) 6\. Confirm validator's registration Let's confirm the validator's registration by calling the `getValidator` function again. Simply enter the validator node's public address into the function's parameter input field and press "call". Two things to note here, * The returned value at the bottom is not an error, which means the validator has been registered After compilation, make sure you log into Metamask and switch the network to Tarxa Mainnet. If you aren't sure how to do that, please check out the . _**Remember:**_ _whatever wallet you use to register the validator node, this wallet is the_ _._ The network ID is indeed in the "Custom network" tag under the Environment dropdown, and which goes into the "validator" field which goes into the "proof" field which goes into the "vrf\_key" field, don't forge to add a `0x` in front of the wallet's output Part of the returned value is an 256-bit unsigned integer that indicates the current delegation (see underlined number in the screenshot above). Since we just registered the node with a 1000 TARA delegation, we'd expect that there would be 1000 \* 10^18 wei delegated to this node, and indeed that is what it is (count the zeros ) You have just registered a validator node. 🌱 ⛓️ πŸ˜„ πŸŽ‰ πŸŽ‰ [wallet guide on adding Taraxa networks into Metamask](/become-a-validator/register-node-directly-on-chain) [Taraxa's network ID](/wallet/taraxas-network-connection-details) [Public address](https://docs.taraxa.io/node-setup/node_address) [Proof of ownership](/node-setup/proof_owership) [VRF key](/node-setup/vrf_key) [_owner of that node_](/become-a-validator/register-node-directly-on-chain#0.-important-wallet-used-to-register-a-node-is-the-owner-of-that-node) [Remix](https://remix.ethereum.org/) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FZR5MWNYu2SDxkB5jfSMh%252Fimage.png%3Falt%3Dmedia%26token%3D9fc666c2-9b9e-4212-8938-1718d54dc9bc&width=768&dpr=4&quality=100&sign=c7749a51&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FcCLG4EHimWL3OTf82NWs%252Fimage.png%3Falt%3Dmedia%26token%3D4d4bd607-77e9-4fb1-b230-3f0521348755&width=768&dpr=4&quality=100&sign=d368743c&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FDVA1XXHAHQs8FnZLhVcb%252Fimage.png%3Falt%3Dmedia%26token%3D32131f18-9acd-430a-98dc-3c82202d86f8&width=768&dpr=4&quality=100&sign=1be803a7&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FobGWXAR0icVKImIy2KD1%252Fimage.png%3Falt%3Dmedia%26token%3Df8e96a69-30ad-49a9-a907-c51221c4a11e&width=768&dpr=4&quality=100&sign=4389decb&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FNIUQETu96JjEZA4FddFG%252Fimage.png%3Falt%3Dmedia%26token%3D5ccc11a7-26b6-4a1e-ac2a-5aca9f11d350&width=768&dpr=4&quality=100&sign=7717d2d1&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FBbbDcxYuPPzsbup2u7pN%252Fimage.png%3Falt%3Dmedia%26token%3D649376af-53c6-46f8-bdb3-5fc4998d37fc&width=768&dpr=4&quality=100&sign=53c6cf13&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FNDFpFfqgvBHqQzJdDBAP%252Fimage.png%3Falt%3Dmedia%26token%3D5f0b033a-6a34-4b78-8bf6-0c6b55ea28b0&width=768&dpr=4&quality=100&sign=81d71cb8&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FpHnVCLPdQooMGIYFxgCK%252Fimage.png%3Falt%3Dmedia%26token%3D5f5eb86b-9690-4f2a-9276-399ffdd36a78&width=768&dpr=4&quality=100&sign=689fcee4&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252Fa1W1RvuNkCxNObXPiN3U%252Fimage.png%3Falt%3Dmedia%26token%3Dd6479ed6-8140-40ac-8999-94c1544bfde5&width=768&dpr=4&quality=100&sign=f4e2d179&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FPfqODvpMAoGi4klXzLwr%252Fimage.png%3Falt%3Dmedia%26token%3Def3dcff6-5990-4296-99b4-70975d9f2cc3&width=768&dpr=4&quality=100&sign=5fd89525&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FCGFIz9ElFRUAVOGQ7kBP%252Fimage.png%3Falt%3Dmedia%26token%3Dece7c9c3-5dd3-4686-be34-2d0754a8f6f7&width=768&dpr=4&quality=100&sign=d1cd45a9&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252F421eXPwXSVHZdL3pe4c7%252Fimage.png%3Falt%3Dmedia%26token%3D621ca7c4-fd63-4632-b0c1-2c074b12932b&width=768&dpr=4&quality=100&sign=5f4a30a5&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FqQGNozkOUR6lQ3X6CXUb%252Fimage.png%3Falt%3Dmedia%26token%3D3d8983f4-743c-4f52-9141-693ecdd0eefa&width=768&dpr=4&quality=100&sign=15f75aa9&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FSlK2MYvetq3RKj8DOomY%252Fimage.png%3Falt%3Dmedia%26token%3D8112e3b1-68bc-4fff-bbf7-740522500e4f&width=768&dpr=4&quality=100&sign=1a5f1b18&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FrBfnelubMFEDYk3rFLPC%252Fimage.png%3Falt%3Dmedia%26token%3D49c690f7-5bd1-4850-a249-472870920a23&width=768&dpr=4&quality=100&sign=b811135f&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FDFt23ZhNMVtFGmv8ZuDk%252Fimage.png%3Falt%3Dmedia%26token%3Da772fb9a-a9b7-489f-a191-2019f5a8608c&width=768&dpr=4&quality=100&sign=813e94c7&sv=2) --- # Liquid Staking | Taraxa Project [PreviousStaking](/staking) [NextStaking via community site](/staking/staking-via-community-site) Last updated 2 months ago Was this helpful? After the Cornus Upgrade, the Taraxa Layer-1 network officially supports liquid staking. Here are the available liquid staking protocols on the Taraxa network. ### [](#undefined) ### [](#lara-protocol) LARA Protocol Stake via the , it's 1-click staking, with the option to auto-compounding your yields back into staking, automatically picks the most reliable & highest-yield validators, and receive a liquid staking token, no KYC, no login required. πŸ’° πŸ’§ [liquid staking protocol LARA](https://app.laraprotocol.com/) --- # Ficus Root Bridge | Taraxa Project [PreviousStaking directly on-chain](/staking/staking-directly-on-chain) [NextBridge usage guide](/ficus-root-bridge/bridge-usage-guide) Last updated 8 months ago Was this helpful? Introducing Taraxa's , a native, generalized, fully permissionless bridge connecting the Ethereum and Taraxa ecosystems. For a detailed description of the bridge's technical and commercial advantages, please . In this documentation we'll cover the following topics, * Deploying new assets onto the Ficus Root Bridge (coming soon...) πŸŒ‰ [Ficus Root Bridge](https://bridge.taraxa.io/) [refer to this article](https://www.taraxa.io/posts/consensus/taraxas-fully-permissionless-ficus-root-cross-chain-bridge-efb88b6d60568cd33f1e440d9adf5e38) [Using the Ficus Root Bridge - a step by step guide](/ficus-root-bridge/bridge-usage-guide) [Core on-chain Bridge contract addresses](/ficus-root-bridge/on-chain-contracts) --- # Staking | Taraxa Project [PreviousNode upgrade & reset](/become-a-validator/node-upgrade-and-reset) [NextLiquid Staking](/staking/liquid-staking) Last updated 2 months ago Was this helpful? [](#how-to-stake-tara) How to Stake TARA --------------------------------------------- There are 3 options available to you when staking TARA, earning staking yields, and helping to secure the Taraxa network all at the same time. Win-win-win. 1. Liquid staking: stake via the , it's 1-click staking, with the option to auto-compounding your yields back into staking, automatically picks the most reliable & highest-yield validators, and receive a liquid staking token, no KYC, no login required. 2. Community site: stake by delegating directly to validators of your choice, through , but it is geo-fenced and requires KYC due to regulatory compliance. 3. On-chain: by interacting with the on-chain DPoS contract, requires some technical knowledge, works through the Remix app. [](#taraxa-staking-tl-dr) Taraxa Staking tl;dr --------------------------------------------------- * Staking TARA means directly delegating your TARA tokens into validator nodes * After the Aspen Upgrade, staking yields are dynamically adjusted. As of this writing it has an APR of ~14-15%, and it will continue to decay over time because Aspen caps the overall supply of TARA. Learn about the . * Staking yields will be shared between staker and validators (they will take a commission) * Staking yields , please note that this is higher than what's stated in the section, the dev team is working to build a community voting infrastructure to facilitate community-proposed & voted-on updates to the economics * You can redeem your yields through the [](#stake-to-secure-the-network) Stake to Secure the Network! ------------------------------------------------------------------ Staking (delegating your TARA to validators) is a critical part of Taraxa's consensus mechanism, which uses proof of stake (PoS) to guard against Sybil attacks. In plain language, staking makes attacking a network expensive, and aims to make attacking a network so expensive that the cost far outstrips the benefits. When you stake, not only are you helping to secure the network against attacks, you are also earning a yield (rewards) for your efforts. Please follow the guide below to stake and help secure the Taraxa network! [](#undefined) ------------------ πŸ’° [liquid staking protocol LARA](https://app.laraprotocol.com/) [the community site](/staking/staking-via-community-site) [stake directly on-chain](/staking/staking-directly-on-chain) [Aspen Upgrade](https://www.taraxa.io/aspen) [community site's claim section](https://community.taraxa.io/redeem) [economics rewards](/tech-whitepaper/economic-model#5-5-rewards) --- # Node upgrade & reset | Taraxa Project [PreviousSolicit delegation](/become-a-validator/solicit-delegation) [NextStaking](/staking) Last updated 2 months ago Was this helpful? ### [](#the-instructions-below-are-for-full-taraxa-nodes.-here-are-the-instructions-for-lite-taraxa-nodes) The instructions below are for Full Taraxa nodes. Here are the . [](#id-1.-node-upgrade) 1\. Node Upgrade --------------------------------------------- The development team will release regular technical updates. To update the node please run the following commands in the `mainnet` directory: Copy wget -O docker-compose-new.yml https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.yml && mv docker-compose-new.yml docker-compose.yml sudo docker-compose down sudo docker-compose pull sudo docker-compose up -d sudo docker-compose logs -f [](#id-2.-node-reset) 2\. Node Reset ----------------------------------------- The mainnet as a network will never be reset. However, sometimes your individual node's state may have been corrupted - e.g., you were too late to a major upgrade, then you might want to reset your node and re-index. Copy cd ~/taraxa-ops-master/taraxa_compose wget -O docker-compose-new.yml https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.yml && mv docker-compose-new.yml docker-compose.yml sudo docker-compose down -v sudo docker-compose pull rm -f config/mainnet.json sudo docker-compose up -d sudo docker-compose logs -f 🌱 πŸ› οΈ [instructions for Lite Taraxa nodes](/node-setup/lite-consensus-node-beta) --- # Audit Report | Taraxa Project [PreviousOn-chain contracts](/ficus-root-bridge/on-chain-contracts) [NextTaraxa Grant Program](/taraxa-grant-program) Last updated 8 months ago Was this helpful? Here is Trail of Bits' audit report for Taraxa's Ficus Root Bridge. πŸŒ‰ πŸ”Ž [https://github.com/trailofbits/publications/blob/master/reviews/2024-07-taraxa-bridge-smart-contracts-v2-securityreview.pdf](https://github.com/trailofbits/publications/blob/master/reviews/2024-07-taraxa-bridge-smart-contracts-v2-securityreview.pdf) --- # Solicit delegation | Taraxa Project [PreviousRegister node directly on-chain](/become-a-validator/register-node-directly-on-chain) [NextNode upgrade & reset](/become-a-validator/node-upgrade-and-reset) Last updated 2 years ago Was this helpful? Each validator node must have a minimum of 500,000 TARA in delegation, otherwise it will not be eligible to participate in consensus. You may delegate this to your own node, or more commonly solicit delegation from the Taraxa community. Here are a few social channels where the Taraxa community congregates, * Taraxa's * Taraxa's * Taraxa's 🌱 πŸ“£ [Discord server](https://www.taraxa.io/discord) [Telegram group](https://www.taraxa.io/tg) [official Twitter](https://twitter.com/taraxa_project) --- # On-chain contracts | Taraxa Project [PreviousBridge usage guide](/ficus-root-bridge/bridge-usage-guide) [NextAudit Report](/ficus-root-bridge/audit-report) Last updated 7 months ago Was this helpful? The dev team is publishing all on-chain contracts critical to the operation of the bridge to maximize transparency as well as to minimize risk of fraud. [](#bridge-infrastructure-contracts) Bridge infrastructure contracts ------------------------------------------------------------------------- These contracts are part of the core infrastructure. They are upgradable so from time to time the code they point to may change, but these addresses will stay the same. On the Ethereum network, * ETH\_bridge: `0x359CF536b1fd6248ebAd1449E1B3727caB33A01d` * TARA\_client: `0xcDF14446F78ea7EBCaa62Fdb0584e4D2e536B999` On the Taraxa network, * TARA\_bridge: `0xe126E0BaeAE904b8Cfd619Be1A8667A173b763a1` * ETH\_client: `0x7157233800c3c1f2ac8b12Cefe2cBE796C04446B` * BeaconLightClient: `0x97Eb8E024bE036eCdb25aDf842C5D6241189FB53` [](#asset-contracts-deployed-by-the-core-dev-team) Asset contracts deployed by the core dev team ----------------------------------------------------------------------------------------------------- The Ficus Root Bridge is fully permissionless, which means anyone can deploy asset connector contracts and register them with the bridge contracts. But since these deployments are completely permissionless and anonymous, there is no way for anyone to know if the asset connectors are fraudulent. Here we publish a list of asset connector contracts that are deployed by the core Taraxa development team for maximum transparency. This list will grow over time as the core development team deploy more. On the Ethereum network, * TARA token on ETH: `0x2F42b7d686ca3EffC69778B6ED8493A7787b4d6E` On the Taraxa network, * ETH token on TARA: `0x39b1fC930C43606af5C353e90a55db10bCaF4087` * USDT (Tether) token on TARA: `0x69D411CbF6dBaD54Bfe36f81d0a39922625bC78c` πŸŒ‰ πŸ“œ [Ficus Root Bridge](https://bridge.taraxa.io/) --- # Start building on Taraxa! | Taraxa Project [PreviousTaraxa Grant Program](/taraxa-grant-program) [NextConnecting to Taraxa](/develop/connecting-to-taraxa) Last updated 7 months ago Was this helpful? [](#tl-dr-wheres-the-example) tl;dr where's the example? ------------------------------------------------------------- Here's a . [](#building-on-taraxas-evm-compatible-network-super-easy) Building on Taraxa's EVM-compatible Network = super easy ------------------------------------------------------------------------------------------------------------------------ Hi! Thanks for checking out Taraxa's Layer-1 network. Here are a few quick links to get you started right away. * using tools you're already familiar with such as Metamask and Ledger * Get some on the Taraxa Explorer * via our dev deployed RPC endpoint, or running a node of your own * is super easy, all ETH-compatible tools just work * Using via video walkthroughs * highlights Taraxa's near-100% compatibility with ETH's RPC specs, with a few minor quirks & exceptions Let's get building! πŸš€ [step-by-step smart contract deployment example](/develop/smart-contracts/remix) [Create a wallet](/wallet) [testnet tokens from the faucet](https://testnet.explorer.taraxa.io/faucet) [Connecting to the Taraxa network](/develop/connecting-to-taraxa) [Deploying a smart contract](/develop/smart-contracts) [common ETH frameworks and a few dApp deployment examples](/develop/common-frameworks-and-examples) [Taraxa RPC specifications](/develop/taraxa-rpc-specs) --- # Register node via community site | Taraxa Project [PreviousConsensus node hardware requirements](/become-a-validator/consensus-node-hardware-requirements) [NextRegister node directly on-chain](/become-a-validator/register-node-directly-on-chain) Last updated 2 months ago Was this helpful? > To comply with recent SEC rulings, United States persons and persons from OFAC-sanctioned regions cannot receive token rewards from running nodes. All participants will be required to pass KYC to receive rewards. You don't, however need to use the community site. You may . If you still wish to use the community site, please follow the steps below. ### [](#id-0.-important-wallet-used-to-register-a-node-is-the-owner-of-that-node) 0\. IMPORTANT: wallet used to register a node is the owner of that node Validator node registration is an on-chain transaction. The wallet you use to register a node is the "owner" of that node. This means once a node is registered, the "owner wallet" is now required to, * Change the validator node's commission rate * Claim commission rewards earned by the validator node A single owner wallet can register multiple validator nodes and become their owner, this makes it easy to manage multiple validator nodes in aggregate. **Please safeguard your validator nodes' owner wallet!** ### [](#id-1.-register-an-account-on-the-community-site) 1\. Register an account on the community site Navigate to the and register an account. ### [](#id-2.-pass-kyc) 2\. Pass KYC ### [](#id-3.-register-your-validator-node) 3\. Register your validator node You'll see a node registration prompt asking for several pieces of node-specific information. Here are instructions on how to find the node's, Note that, the container name is different from the testnet. In the mainnet, instead of `taraxa_compose_node_1`, it's `mainnet_node_1`. Per usual this name may be different in different environments, so to be sure you've got the right container name, just execute `docker ps`. ### [](#id-4.-setting-the-commission) 4\. Setting the commission The last entry to registering a node is setting its commission, which is the portion of the staking yield that goes to the node operator. You can enter a range of value between 0 to 100. ### [](#id-5.-self-delegation-requirement) 5\. Self-delegation requirement Once you click "Submit" in the node registration pop-up, the on-chain transaction will require that the operator delegate 1000 TARA to their own validator node - so make sure you have enough in the wallet to complete the on-chain registration of the validator node. This self-delegation requirement is not meant to be a financial burden, but purely to guard against spamming. To claim rewards (e.g., staking commission, yields) from the community site, you must pass KYC. It is in the . _A reminder, you can skip the community site and directly_ _._ Navigate to the section of the community site and select "Register a Mainnet Node". Here are some . This is a purely economic decision on the part of the validator operators, it's advisable to review how much commission other validators are charging first by going to the of the community site. 🌱 🚩 [profile section](https://community.taraxa.io/profile) [_register your node on-chain by interacting with the DPoS contract_](/become-a-validator/register-node-directly-on-chain) [run a node](https://community.taraxa.io/node) [Public address](https://docs.taraxa.io/node-setup/node_address) [Proof of ownership](/node-setup/proof_owership) [VRF key](/node-setup/vrf_key) [information on commissions](https://docs.taraxa.io/faq/mainnet-candidate#c0e0) [delegation section](https://community.taraxa.io/delegation) [register a node by directly interacting with the on-chain DPoS contract](/become-a-validator/register-node-directly-on-chain) [community site](http://community.taraxa.io/) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FcozcqOL8o4IwCviKxuMn%252F1.%2520register.png%3Falt%3Dmedia%26token%3De0a38535-58e7-4075-a9c8-553cc48a08c3&width=768&dpr=4&quality=100&sign=dafc31d6&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FDlMezcZoqOHz7wVvTsdy%252F2.%2520kyc.png%3Falt%3Dmedia%26token%3D99f63458-bbde-41a3-8b8c-7bc68667e5f8&width=768&dpr=4&quality=100&sign=5d993228&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FagHkYFeI0FWtEIAgKBFO%252F3.%2520register%2520a%2520validator.png%3Falt%3Dmedia%26token%3Dfceb5276-ff9c-475d-a183-b4c71b1f1daa&width=768&dpr=4&quality=100&sign=31045a6d&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FFgL6SBhKAiUURJWwW2vt%252F3.%2520enter%2520node%2520details.png%3Falt%3Dmedia%26token%3D63fe538f-5f21-4ded-a41e-5a4d38a287ce&width=768&dpr=4&quality=100&sign=bc88f511&sv=2) --- # Staking directly on-chain | Taraxa Project [PreviousStaking via community site](/staking/staking-via-community-site) [NextFicus Root Bridge](/ficus-root-bridge) Last updated 8 months ago Was this helpful? You can delegate to validator nodes by directly communicating with the on-chain DPoS contract and skip the community site altogether. Here are instructions on how to do this. ### [](#id-1.-upload-the-dpos-contract-solidity-interface-into-remix) 1\. Upload the DPoS contract Solidity interface into Remix Go to , and upload Taraxa's DPoS contract's Solidity interface. In the pop-up, paste in the following link to the Taraxa DPoS contract Solidity interface, Copy https://raw.githubusercontent.com/Taraxa-project/taraxa-evm/master/taraxa/state/contracts/dpos/solidity/dpos_contract_interface.sol After it's been uploaded you should be able to see it in the IDE on the right side, ### [](#id-2.-compile-the-interface) 2\. Compile the interface Make sure the interface file is selected, Go into the compiler section by clicking on the icon on the left side. Once you're in the section, double check the big blue compile button indeed says "Compile dpos\_contract\_interface.sol". If the Compile button doesn't say that, that means the interface file wasn't selected in the file explorer section as indicated above, please go back and make sure the right file is selected. Click the Compile button. Once it has been compiled you should see a green checkmark on the compiler icon on the left sidebar, and additional options will show up below the compile button. ### [](#id-3.-set-up-the-interface) 3\. Set up the interface Once you've switched your Metamask to the Taraxa Mainnet, go to the "Deploy & Run Transactions" section in Remix. At the top, change "Environment" to "Injected Provider - Metamask". Once you've done that, make sure to double-check that * The wallet under "Account" is the wallet you want to use. Make sure you use the wallet that contains the TARA you wish to delegate. * The right compiled interface from the previous step is loaded. Look at the "Contract (Compiled by Remix)" section and make sure the filename is the same as the one in the file explorer. Next, we tell Remix where the DPoS contract is located. Go the "At Address" field towards the bottom of the screen, and enter the following address. This is where Taraxa's precompiled DPoS contract is located. Copy 0x00000000000000000000000000000000000000fe Go ahead and click the "At Address" button, and it should show up under "Deployed Contracts". Go ahead and expand the interface by clicking on the chevron ">" and you'll see a list of all the commands you can send to the contract. ### [](#id-4.-verifying-the-validator-node) 4\. Verifying the validator node Before you delegate to a validator node, let's make sure it has actually been registered in the DPoS contract. We're going to do this by calling the `getValidator` function on the validator you wish to delegate to. For example, if I wanted to delegate to a validator node whose public address is: `0xd423413a6b4bb11e584d7de3acce40d95da6c3b1`, we simply enter this address into the function. We click on the "call" button to send the query to the DPoS contract, and we get the return value below the call. Here's how to interpret it. * First, the returned value at the bottom is not an error! Which means the validator has been registered. * Part of the returned value is an 256-bit unsigned integer that indicates the current delegation (see underlined number in the screenshot above). Note that, all values on the blockchain are stored as unsigned 256-bit integers, so there are no decimals, that's why the numbers look so big because they need to also represent 10^18 decimal places as part of the integer value. Just take this number and remove 18 zeros from the end, and you'll see that, in this example, this validator node has 1000 TARA delegated to it. Since 1000 TARA is a required self-delegation from the node owner, that means this node has not received any delegation since registration. * Since the minimum delegation required to participate in consensus is 500,000 TARA, that means in this example, this node is not yet eligible to participate in consensus. If the validator node has passed the minimum threshold, then you can also check it on the explorer to see its past block production history. ### [](#id-5.-delegating-to-the-validator) 5\. Delegating to the validator After verifying the validator node indeed exists on the network, we can now delegate to it by calling the `delegate` function. First, we enter the number of TARA to be delegated into the node. Within the "Deploy & Run Transactions" section of Remix, navigate back towards the top and you'll see a "Value" field. This field defines how many tokens will be transferred to the contract in this transaction. Set the following, * Value to whatever you wish to delegate, in this example we're going to use 1000 since it's the minimum delegation amount. * Unit to "Ether", this may be confusing but since Remix isn't aware of the Taraxa Network's token name, it calls all tokens for EVM-compatible networks "Ether", don't worry, it's sending TARA (since you're on the Taraxa Network) Next, we enter the validator node's public address into the `delegate` function below. After pressing the "transact" button, the output is seen on the right side in Remix's console. If the transaction is successful, you should see a green checkmark at the top-left corner. If you expand the output, you'll that the "status" has a successful output, and in the "va" field you should see the exact amount (with 18 extra zeros at the end) that you delegated. Let's verify that the delegation has indeed worked, by calling the `getValidator` function on the validator node again. Now it has 2000 TARA delegation (once again, reminder there are 18 extra zeros after the number), which is exactly 1000 TARA more than before we started. ### [](#id-6.-claiming-staking-yields) 6\. Claiming staking yields To claim staking yields, use the `claimRewards` function. Make sure the wallet connected is the wallet used to stake. Note that, you'll need to claim rewards from every validator you delegated to. In our example, since the validator only has 2000 TARA delegation, it isn't eligible to participate in consensus yet so the reward claimed was 0, which is expected. ### [](#id-7.-re-delegating-your-stake) 7\. Re-delegating your stake If for whatever reason, you want to move your delegation from one node to another - e.g., if the original node you delegated to has shut down, you can use the `reDelegate` function. Just enter the public addresses for the validator node you want to remove delegation from, to, and the amount (remember to add 18 zeros at the end of this!), and press "transact". You should always verify the results by using the `getValidator` function as usual. ### [](#id-8.-un-delegating-your-stake) 8\. Un-delegating your stake You can also remove your delegation and return the staked TARA back into your wallet by using the `unDelegate` function. Note that, after calling the unDelegate function, it'll take 700,540 blocks (~30 days) for the delegated tokens to unlock. After the time has elapsed and tokens unlocked, you can claim the tokens via the `confirmUndelegate` function, which requires that you enter the same validator node's public address again. A few things to note, * Un-delegate initiates a removal of a defined amount of delegated tokens from the validator node * Once you initiate un-delegation, there's a delay of 700,540 blocks (~30 days) delay before you can claim your tokens * If you simply wish to shift delegation from an under-performing node to one that performs better, you should consider using re-delegation which only has a few PBFT block delay (a few seconds) * You can un-delegate, using the same wallet, from multiple validators simultaneously * You can NOT un-delegate, using the same wallet, from the same validator multiple times - you'd have to either cancel the un-delegation (at the top of the community staking page), or wait till the current un-stake delay has fully elapsed and execute a new un-stake After compilation, make sure you log into Metamask and switch the network to Tarxa Mainnet. If you aren't sure how to do that, please check out the . _**Remember:**_ _whatever wallet you use to register the validator node, this wallet is the_ _._ The network ID is indeed in the "Custom network" tag under the Environment dropdown, and If the returned value is an error, DO NOT delegate to this address. This node either does not exist at all, or it has not been registered. Everything worked! πŸ’° ⛓️ πŸ›‘ πŸ›‘ πŸŽ‰ [wallet guide on adding Taraxa networks into Metamask](/become-a-validator/register-node-directly-on-chain) [Taraxa's network ID](/wallet/taraxas-network-connection-details) [_owner of that node_](/staking/staking-directly-on-chain#0.-important-wallet-used-to-register-a-node-is-the-owner-of-that-node) [Remix](https://remix.ethereum.org/) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FZR5MWNYu2SDxkB5jfSMh%252Fimage.png%3Falt%3Dmedia%26token%3D9fc666c2-9b9e-4212-8938-1718d54dc9bc&width=768&dpr=4&quality=100&sign=c7749a51&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FcCLG4EHimWL3OTf82NWs%252Fimage.png%3Falt%3Dmedia%26token%3D4d4bd607-77e9-4fb1-b230-3f0521348755&width=768&dpr=4&quality=100&sign=d368743c&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FDVA1XXHAHQs8FnZLhVcb%252Fimage.png%3Falt%3Dmedia%26token%3D32131f18-9acd-430a-98dc-3c82202d86f8&width=768&dpr=4&quality=100&sign=1be803a7&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FobGWXAR0icVKImIy2KD1%252Fimage.png%3Falt%3Dmedia%26token%3Df8e96a69-30ad-49a9-a907-c51221c4a11e&width=768&dpr=4&quality=100&sign=4389decb&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FNIUQETu96JjEZA4FddFG%252Fimage.png%3Falt%3Dmedia%26token%3D5ccc11a7-26b6-4a1e-ac2a-5aca9f11d350&width=768&dpr=4&quality=100&sign=7717d2d1&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FBbbDcxYuPPzsbup2u7pN%252Fimage.png%3Falt%3Dmedia%26token%3D649376af-53c6-46f8-bdb3-5fc4998d37fc&width=768&dpr=4&quality=100&sign=53c6cf13&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FNDFpFfqgvBHqQzJdDBAP%252Fimage.png%3Falt%3Dmedia%26token%3D5f0b033a-6a34-4b78-8bf6-0c6b55ea28b0&width=768&dpr=4&quality=100&sign=81d71cb8&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FpHnVCLPdQooMGIYFxgCK%252Fimage.png%3Falt%3Dmedia%26token%3D5f5eb86b-9690-4f2a-9276-399ffdd36a78&width=768&dpr=4&quality=100&sign=689fcee4&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252Fa1W1RvuNkCxNObXPiN3U%252Fimage.png%3Falt%3Dmedia%26token%3Dd6479ed6-8140-40ac-8999-94c1544bfde5&width=768&dpr=4&quality=100&sign=f4e2d179&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FPfqODvpMAoGi4klXzLwr%252Fimage.png%3Falt%3Dmedia%26token%3Def3dcff6-5990-4296-99b4-70975d9f2cc3&width=768&dpr=4&quality=100&sign=5fd89525&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FDixHTKQyL29TNEg6DSyr%252Fimage.png%3Falt%3Dmedia%26token%3Dc9b948fd-849b-4639-8fd6-aca6f95c2932&width=768&dpr=4&quality=100&sign=125de756&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FNkfIp8l7Rc9cFemadl8O%252Fimage.png%3Falt%3Dmedia%26token%3D606d4ffb-035e-46d8-8486-2be7bee87765&width=768&dpr=4&quality=100&sign=d9d0d11&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FYEcnGGEOA1p327ItdRd2%252Fimage.png%3Falt%3Dmedia%26token%3Db0d622bf-255e-46ff-89e7-776061a64512&width=768&dpr=4&quality=100&sign=73868b8b&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FsMD0k8yjxiyhqeJmhy5G%252Fimage.png%3Falt%3Dmedia%26token%3Dcfab921b-0376-4088-af79-ec6b01e9260f&width=768&dpr=4&quality=100&sign=b745afc5&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FhdsOzEXGJyTjzYyKuQeU%252Fimage.png%3Falt%3Dmedia%26token%3D8676314d-ee99-4ba0-adfc-64317037b639&width=768&dpr=4&quality=100&sign=852bc682&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252F7bAhJu3aTWXIiiEArUOO%252Fimage.png%3Falt%3Dmedia%26token%3Daaa44954-4766-4fe6-b064-b81224db943b&width=768&dpr=4&quality=100&sign=20c6c659&sv=2) ![](https://docs.taraxa.io/~gitbook/image?url=https%3A%2F%2F902105633-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MJepYMaCjWn_0Y0r41o%252Fuploads%252FTWBt1dSGiCPIHLiEHs44%252Fimage.png%3Falt%3Dmedia%26token%3D1532724a-faa0-4e3d-82a4-e44ad633f11c&width=768&dpr=4&quality=100&sign=a5aadf88&sv=2) --- # Connecting to Taraxa | Taraxa Project [PreviousStart building on Taraxa!](/develop/start-building-on-taraxa) [NextSmart Contracts](/develop/smart-contracts) Last updated 2 years ago Was this helpful? [](#connecting-to-taraxas-eth-compatible-network) Connecting to Taraxa's ETH-Compatible Network ---------------------------------------------------------------------------------------------------- There are two ways to connect to Taraxa's network, * Via dev-deployed RPC endpoints * Via your own mainnet / testnet nodes Since Taraxa's network is almost 100% ETH-compatible, you can simply follow . The ETH-compatibility with Ethereum also means that almost all tools from the Ethereum ecosystem work with Taraxa. You can use, for example, , and to connect to and interact with the Taraxa Network. There are a few minor exceptions and quirks to Taraxa's ETH-compatibility, you can find them in our . [](#connect-via-rpc-endpoints-provided-by-the-dev-team) Connect via RPC endpoints provided by the dev team --------------------------------------------------------------------------------------------------------------- You may use the RPC endpoints provided by Taraxa's core development team. Right now these are being provided as is and free of charge, this may change later of course with plenty of notice given to the community. * Mainnet: * Testnet: More details on , including chain-ids etc. [](#connect-via-your-own-nodes) Connect via your own Nodes --------------------------------------------------------------- You could also set up your own nodes on the Mainnet or Testnet. This give you a lot of flexibility in working with your DApp. If these nodes are being used primarily for RPC connections, they do NOT need to participate in consensus. Therefore there is no need to register them on the community site, or seek delegation for the mainnet nodes. Here are node setup instructions, The default RPC port on the Taraxa node is "7777". So if you're running this on your own node on the node's local machine, you'd send the RPC request to `localhost:7777`. Setting up a Setting up a πŸ”— [Ethereum's JSON-RPC documentation](https://ethereum.org/en/developers/docs/apis/json-rpc/#usage-example) [Web3.js](https://web3js.org/) [ethers.js](https://docs.ethers.io/v5/) [Web3.py](https://web3py.readthedocs.io/en/latest/) [full RPC specification](/develop/taraxa-rpc-specs) [https://rpc.mainnet.taraxa.io](https://rpc.mainnet.taraxa.io) [https://rpc.testnet.taraxa.io/](https://rpc.testnet.taraxa.io/) [Taraxa's network connections](/wallet/taraxas-network-connection-details) [mainnet node](/become-a-validator) [testnet node](/node-setup/testnet_node_setup) ---