<h1>eCash Avalanche Tutorial</h1><h2>How to Generate Stake Proofs and Run an Avalanche Node</h2><h6><em>Posted on September 7, 2022</em></h6><p>The goal of this article is to explain how the eCash Avalanche protocol works, and give basic step-by-step instructions for getting started.</p><p>After reading this article, the reader should be able to:</p><ul><li>Understand the basics of how eCash’s Avalanche protocol works</li><li>Understand the role of Proofs, Delegations, and Nodes</li><li>Become familiar with the Electrum ABC Proof Editor</li><li>Generate your own Avalanche Proof</li><li>Use your Avalanche Proof to run a Bitcoin ABC node with Avalanche enabled</li></ul><p>In addition to this tutorial, there are also video guides explaining how to <a href="https://youtu.be/ls88OH3eGwQ">set up an eCash Avalanche node using a Virtual Private Server</a>, and how to <a href="https://youtu.be/3k5M4k8OF-I">create a Stake Proof for your eCash Node</a>.</p><p><strong>Note:</strong> There are no staking rewards at this time. Creating a Stake Proof simply allows you to run an eCash Avalanche node and have that node participate in Post-Consensus. This benefits the eCash network, and gives you some influence over consensus formation to decide which blocks are finalized in Post-Consensus. But it does not result in direct rewards from staking.</p><h2>What is Avalanche?</h2><p>Avalanche is a network protocol whose main property is to provide fast convergence between the participants. These participants are requested to vote on items and will eventually flip their position according to the vote result. Once a vote is conclusive, there is no way back and the voted item state is considered final. Avalanche provides a Byzantine fault tolerant protocol with well defined safety guarantees, as laid out in its <a href="https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV">white paper</a>.</p><p>In the context of eCash, the Avalanche protocol is being used in conjunction with Nakamoto consensus. This means that all items being voted on must follow the consensus rules, and Avalanche can take care of solving the conflicts. There are several use cases where the Avalanche protocol brings improvement to Nakamoto consensus:</p><p><strong>Post-Consensus:</strong> this refers to the decisions that occur after a block gets mined. This includes voting on the blocks to prevent reorgs.</p><p><strong>Pre-Consensus:</strong> this refers to the decisions that occur before a block gets mined. This includes voting on transactions to prevent double spends.</p><p>The eCash network roadmap plans for both the above mechanisms and more. At this stage only Post-Consensus is implemented.</p><h2>Stake Proofs</h2><p>While the Avalanche protocol itself has well defined safety guarantees, it requires some sort of method for Sybil resistance. In order to provide this Sybil resistance, the eCash avalanche network requires that every Peer that participates in Avalanche voting has an associated “Stake Proof”. More than one Avalanche Node can be associated with the same Proof, and from the perspective of the Avalanche voting protocol, the group of nodes associated with the same Proof is called an “Avalanche Peer”.</p><p>The Proof provides Sybil resistance by being associated with eCash coins (UTXOs). The Proof contains signatures from the private spending key for those coins. This means that only the person who knows the private key for the coin can add Stakes to the Proof. One Proof can be tied to many coins, which means that the coins don’t have to be moved in order to create the Stake Proof.</p><p>The mechanism by which Nodes are associated with a Proof uses Public Key Cryptography in which the Node signs messages that prove it possesses the private key corresponding to the Proof, known as the “Proof Master Key”. To facilitate key management, there are also “Delegations” which allow different nodes associated with the same Proof to use different keys. The relationship between Coins, Proofs, Delegations, and Nodes is shown below:</p><figure class="w-richtext-figure-type-image w-richtext-align-fullwidth" style="max-width:1280px" data-rt-type="image" data-rt-align="fullwidth" data-rt-max-width="1280px"><div><img src="https://strapi.fabien.cash/uploads/e_Cash_Avalanche_Tutorial_6ead69058d.jpeg" alt="eCash Avalanche Proofs, Nodes and Delegations" width="auto" height="auto" loading="auto"></div></figure><p>Note the one-to-many relationship between Nodes, the Proof, and staked coins (UTXOs) in this image. One Avalanche Proof can be used by several different eCash nodes. This is useful for providing redundancy, geographic diversity, and load balancing. Each Node, however, can only use one Proof. If you wish to use several staked coins with the same Node, even coins held in different wallets by different people, this can be done by adding all the different coin stakes into one Proof.</p><h2>Proof Format</h2><p>The Avalanche Proofs contain information within them in various fields as follows:</p><p><strong>Proof Sequence:</strong> This number is intended to be used when you want to replace a proof with another one. Once a UTXO has been embedded into a proof, it cannot be part of another proof. If 2 or more proofs are claiming the same UTXO, then the following rule applies:</p><ul><li>If the proof public key is identical, the highest sequence number takes precedence.</li><li>If the public key differs, the total staked amount takes precedence.</li><li>In practice, it is advised to use a sequence number of 0 for building your proof. Then if at some point you intend to make another one, for example to include more coins, you can increase the number to 1 to let the network know that it’s a deliberate move. Note that your earlier revision proof will be invalidated by the network and you should update all the nodes using it to the new revision.</li></ul><p><strong>Expiration:</strong> This sets a time at which your proof will be considered invalid.</p><p><strong>Master Public Key:</strong> This is the Master Key for the Proof. When generating a new Proof, Electrum ABC will automatically generate a Private Key from the wallet’s derivation path at <strong>.../2/0</strong>. The associated Public Key is included in the Proof. This Key is used by the Avalanche Node to prove that it has authority to participate in the protocol as a Peer representing this Proof.</p><p><strong>Payout Address:</strong> This is a valid XEC address that will be used to send the staking rewards (not available yet). Can be any standard type address that you own and want the coins to be sent to.</p><p><strong>Stakes:</strong> This is an array of the UTXOs to be attached to the proof. There are some limitations to these UTXOs:</p><ul><li>Limited to 1000 UTXOs per proof.</li><li>Each UTXO must have an amount greater or equal to 100 MegXEC (aka 100,000,000.00 XEC).</li><li>Each UTXO must have 2016 or more confirmations in the blockchain. This means that the coin must not have moved within the previous 2 weeks.</li><li>Only P2PKH UTXO type is supported, you cannot stake P2SH (often used for multisig) coins.</li></ul><h2>Generate a Proof using Electrum ABC</h2><p>As of version 5.1.5, Electrum ABC includes the Avalanche Proofs Editor for use with eCash Avalanche. The Proof Editor is a general tool that can be used to generate new Proofs, as well as load existing Proofs to inspect their contents and modify them to create new Proofs. For example, you could load an existing Proof, and add coins from the wallet to stake in the Proof.</p><figure class="w-richtext-figure-type-image w-richtext-align-fullwidth" style="max-width:769px" data-rt-type="image" data-rt-align="fullwidth" data-rt-max-width="769px"><div><img src="https://strapi.fabien.cash/uploads/e_Cash_Avalanche_Tutorial_d57cecaf8f.jpeg" alt="Electrum ABC Proof editor" width="auto" height="auto" loading="auto"></div></figure><p>In this tutorial, we will use two Electrum ABC wallets, along with the Proof Editor, to generate a Stake Proof. The reason for using two wallets is to keep the coin spending keys separate from the wallet that controls the Proof Master Key. This allows the Private Keys associated with spending the coins to be managed securely. The instructions here will assume that you are using an offline computer for the coin-holding wallet.</p><p>In order to manage these wallets separately, we will create Proof in a 3-step process:</p><ol><li>In the Proof wallet, create a skeleton Proof.</li><li>In the Coin-holding wallet, add Stakes to the Proof.</li><li>In the Proof wallet, sign the Proof with Proof Master Key.</li></ol><h3>Step 1: Create the Skeleton Proof</h3><p>This step is done on a regular computer connected to the internet. This will create a wallet that can be used to manage your Proofs, and create Delegations if you decide to do that later. Simply follow these steps:</p><ol><li>Create a new wallet. This will be your “Proof wallet”.</li><li>Open Tools &gt; Avalanche Proof Editor.</li><li>Review the fields and adjust them if desired. For example, you may want to change the Payout Address to one in another wallet, or adjust the expiration time.</li><li>Click Generate proof.</li><li>Save the Proof.</li></ol><h3>Step 2: Add Stakes to the Proof</h3><p>Online portion:</p><ol><li>Open a watch-only version of your coin-holding wallet. For example, this could be your regular Trezor wallet within Electrum ABC.</li><li>Open the ‘Coins’ tab, select the coins you want to stake, right click and click ‘Export coin details’ to export coins file. Make sure the coins you select meet the requirements for Staking: each coin must be at least 100,000,000.00 XEC and have at least 2016 confirmations.</li></ol><p>For the next steps, move to an offline computer. For example, you could use a “Live CD” to temporarily recreate your hardware wallet (Trezor or Ledger) within Electrum ABC, without saving the wallet or connecting to the internet. When moving to the offline computer, the information you will need is:</p><ul><li>Electrum ABC 5.1.5</li><li>The saved Proof</li><li>Coin details file</li></ul><p>You can save these to a memory stick for use on the offline computer.</p><p>Once you have recreated the coin-holding wallet on your offline computer, follow these steps to add your coins as Stakes in the Proof.</p><ol><li>In the Proof editor, click on the “Load proof” button.</li><li>Click OK on warning. It’s OK that this wallet doesn’t have the Proof Master Key, it just means you won’t be able to sign the final Proof at the end from this wallet.</li><li>Add coins from the Coin Details file you saved previously.</li><li>Click Generate proof.</li><li>Click Save Proof, Click OK on warning. You will need to save the Proof to a memory stick, or other medium to transfer it back to your online computer.</li><li>After the Proof has been saved, you can delete the wallet and/or wipe the entire offline computer.</li></ol><h3>Step 3: Sign the Proof with Proof Master Key</h3><ol><li>Back on your online computer, open Avalanche Proof wallet again.</li><li>Load the unsigned Proof that was saved from the offline computer (You should now see the private key in that field).</li><li>Click on Generate Proof. This will actually sign the entire Proof with the Proof Master Key.</li><li>Save the signed Proof</li></ol><p>Now you have an Avalanche Proof, and can run an eCash Avalanche node!</p><h2>Run an eCash Avalanche Node</h2><p>To run Avalanche, use <a href="https://www.bitcoinabc.org/releases/#0.26.0">Bitcoin ABC version 0.26.0</a> or greater, and simply restart your node with the following added to your bitcoin.conf file:</p><blockquote>avalanche=1<br>debug=avalanche<br># Proof dependent parameters<br>avaproof=&lt;your hex Proof&gt;<br>avamasterkey=&lt;your Master Private Key, WIF format&gt;<br></blockquote><p>(debug=avalanche is not strictly necessary, but will let you see Avalanche related message in your <strong>debug.log</strong> file. This line can be omitted if desired)</p><h3>Ensure the Node is Well Connected</h3><p>One thing to note, is that the Avalanche protocol relies on the node being well connected to the rest of the network. This is quite different from Nakamoto consensus, which only needs enough connectivity to be confident that it can get the longest Proof-of-Work chain. For your Avalanche to function effectively, and be of greatest value to the network, check the following:</p><ul><li>It should accept incoming connections. If it is behind a firewall, adjust the firewall settings to allow incoming connections.</li><li>Sometimes people run eCash nodes behind another “bridge node”. Running an Avalanche node with a Proof behind a bridge node is not helpful to the rest of the Avalanche network, since that node won’t be able to participate properly in Avalanche voting rounds.</li><li>Make sure that the <strong>maxconnections</strong> parameter isn’t set in your bitcoin.conf file. This can interfere with the proper functioning of the Avalanche networking code.</li><li>The Avalanche node should have high uptime, and be able to run continuously.</li></ul><h3>Adding a Delegation</h3><p>Another consideration is the option of running multiple nodes using Delegations. To Delegate your Proof to someone else’s node do the following:</p><ol><li>Ask the node operator for a Delegation PubKey.</li><li>Use Electrum ABC to Generate a Delegation to that PubKey by clicking “Generate a Delegation” within the Proof Editor.</li></ol><p>Then the person running the Delegated node can use the same Proof without having access to the Proof Master Key, by adding these lines to their bitcoin.conf file:</p><blockquote>avalanche=1<br>debug=avalanche<br># Proof dependent parameters<br>avaproof=&lt;the hex Proof&gt;<br>avadelegation=&lt;the hex Delegation&gt;<br>avamasterkey=&lt;the Master Private Key for the Delegation, WIF format&gt;<br></blockquote><h2>Monitoring your Avalanche Node</h2><p>Now that you have your node running, with Avalanche enabled and a Stake Proof, your node will be participating in the Avalanche protocol and helping to finalize blocks. You are now part of the network of Avalanche nodes that are enabling 1-block finalization, and protecting the network from 51% attacks.</p><p>To observe the status of Avalanche on your node, you can try some of the following commands:</p><p>./bitcoin-cli getavalancheinfo<br>./bitcoin-cli getavalanchepeerinfo<br>tail -n 100 ~/.bitcoin/debug.log<br></p><p>For more questions and to ask for help, you can join the <a href="https://discord.gg/d5EHW3PgTy">eCash Discord</a>. For questions and issues specific to the Bitcoin ABC node, try the <a href="https://t.me/eCashDevelopment">eCash Development Telegram group</a>. For questions and issues related to Electrum ABC, try the <a href="https://t.me/ElectrumABC">Electrum ABC Telegram group</a>. To monitor development progress, see <a href="https://www.avalanche.cash/">Avalanche.cash</a></p>

large_63504652ae517fd14a9f4cf5_avalanche-proof.jpeg

medium_63504652ae517fd14a9f4cf5_avalanche-proof.jpeg

small_63504652ae517fd14a9f4cf5_avalanche-proof.jpeg

thumbnail_63504652ae517fd14a9f4cf5_avalanche-proof.jpeg

63504652ae517fd14a9f4cf5_avalanche-proof.jpeg

The goal of this article is to explain how the eCash Avalanche protocol works, and give basic step-by-step instructions for getting started.

eCash Avalanche Tutorial

<p>Avalanche is here.</p><p>On September 14th 2022, the <a href="https://e.cash/">eCash</a> network was upgraded to support the finalization of blocks using Avalanche Post-Consensus.</p><p>The launch of Avalanche Post-Consensus on the eCash Mainnet is a significant achievement, bringing tangible benefits for eCash miners, exchanges, and everyday users.</p><p>As of the writing of this article, over 80 Billion XEC has been staked to run voting Avalanche nodes and support the eCash network. For live Avalanche network statistics and to track the development of upcoming milestones, see <a href="https://avalanche.cash/">avalanche.cash</a>.</p><h2>Benefits for Miners</h2><p>Avalanche Post-Consensus brings 51% attack prevention to eCash. This is particularly important for miners. Because eCash is a minority chain sharing the same SHA256 mining algorithm as Bitcoin (BTC), it is more vulnerable to a malicious non-economically motivated attacker, who could attempt a blockchain reorganization. Though the network as a whole can recover from such an attack, it would be particularly disruptive to miners, who could lose blocks, costing them money.</p><p>Avalanche Post-Consensus solves this problem. Nodes come to consensus to “finalize” the blocks that they see on the network. In other words, it allows nodes to know that the blocks they see are also seen and accepted by the rest of the network. If conflicting blocks appear later, the Avalanche-using miners will come to consensus and ignore the late-appearing blocks. In this way, they defend the network against block withholding attacks, and blockchain reorganizations.</p><h2>Benefits for Exchanges</h2><p>Avalanche Post-Consensus also brings significant benefit for exchanges by bringing 1-block finality to eCash. This enables 1-confirmation deposits.</p><p>It is very important for exchanges to ensure that deposits are secure before they allow trading and withdrawal. This is typically done by requiring that deposit transactions have a certain number of blockchain confirmations before the funds can be traded.</p><p>With Avalanche Post-Consensus, there is now a secure way to verify customer deposits, using the Avalanche finalization status instead of “number of confirmations”. This will also cause deposits to be finalized with only 1 block confirmation. This will enhance exchange security by preventing re-org attacks and increase customer satisfaction by reducing deposit confirmation times. It will also enable easier arbitrage for traders, driving more volume and liquidity to the exchange. Happier customers are good for exchanges.</p><p>To start benefitting from Post-Consensus, exchanges should set up their eCash node to run Avalanche, and use the new isfinaltransaction RPC command to check whether deposits have been finalized or not. The isfinaltransaction RPC is forwards-compatible with future Avalanche upgrades.</p><h2>Benefits for Users</h2><p>In its current state, eCash already offers a cash-like experience for peer-to-peer transfers. For users sending XEC directly using a wallet such as <a href="https://cashtab.com/">Cashtab</a>, payments typically show up in a matter of seconds, with sub-cent fees.</p><p>What users can expect from the Avalanche Post-Consensus is that the cash-like experience will improve further as exchanges and other eCash services take advantage of the re-org protection and 1-block finality offered by Avalanche Post-Consensus. This will enable services to offer a faster and more cash-like payment experience.</p><p>Looking further into the future, the eCash experience should continue to improve even more with Pre-Consensus and other technologies in the pipeline. The purpose of all of these developments is to pursue eCash’s goal of being the most usable, secure and scalable form of electronic cash possible.</p><h2>Running Avalanche on eCash</h2><p>eCash node operators can activate Avalanche by upgrading to Bitcoin ABC 0.26.2 or higher, and setting the <strong>avalanche=1 </strong>parameter in their <strong>bitcoin.conf</strong> file. This will activate Avalanche in “poll only” mode, which means the node can query the network to find the finalization staus of blocks, but does not contribute to the Avalanche consensus.</p><p>Node operators who wish to contribute to the eCash network by participating in Avalanche can set up a staking node by following our written <a href="https://www.bitcoinabc.org/2022-09-07-avalanche-staking-tutorial/">Avalanche Staking Tutorial</a>, and the <a href="https://youtu.be/3k5M4k8OF-I">Stake Proof video guide</a>.</p><p>One of the characteristics of the Avalanche protocol is that its security relies on the nodes being well connected to the rest of the network. This means that it’s important, especially for staking nodes, to have a reliable internet connection, and to accept inbound connections. If you have a firewall, make sure to open port 8333. Also ensure that the <strong>maxconnections</strong> parameter is not set in your bitcoin.conf file.</p><p>For large stakers, it’s also a good idea to run more than one node for each Proof. A good option is to use remotely hosted servers. We have created a video guide to help users <a href="https://youtu.be/ls88OH3eGwQ">set up an eCash Avalanche node using a Virtual Private Server</a>.</p><h2>About Post-Consensus</h2><p>Post-Consensus is named that way because it is dealing with blocks <em>after</em> they are produced by miners. By contrast, Pre-Consensus (not yet implemented) is when the Avalanche protocol is used by nodes to come to consensus on transactions <em>before</em> blocks are produced.</p><p>With Avalanche Post-Consensus, nodes can come to consensus on the current live status of blocks that are visible on the eCash network. In other words, it allows nodes to know that the blocks they see are also accepted by the rest of the network. This information can then be used to defend the network against block withholding attacks, and blockchain reorganization attacks.</p><p>After Pre-Consensus is implemented in Bitcoin ABC, Post-Consensus will also be used to reject blocks that include transactions that conflict with transactions that were finalized via Pre-Consensus. This will allow users of the eCash network to benefit from near-instant transaction finalization, with confidence that finalized transactions cannot be reversed.</p><h2>About Avalanche</h2><p>Using a fast consensus protocol to do Pre-Consensus has been a long-standing item on the <a href="https://e.cash/roadmap-explained">eCash Roadmap</a> (and previously on the Bitcoin Cash roadmap). This is one of the improvements needed to power eCash to be a competitor and alternative to Central Bank Digital Currencies (CBDCs). When the <a href="https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV">Avalanche whitepaper</a> appeared in 2018, eCash founder Amaury Séchet and the Bitcoin ABC team recognized that this new protocol was what they had been searching for, as it fulfilled the needed requirements.</p><p>It should be noted that eCash’s Avalanche implementation is completely separate and distinct from the AVAX Avalanche project. They have no connection, other than both using the protocol described in the Avalanche whitepaper. Avalanche on eCash is an entirely new implementation which had to be developed from scratch by the Bitcoin ABC team.</p><p>In the case of eCash, Avalanche consensus is used for fast and live consensus needs, such as fast transaction finality. Proof-of-work based Nakamoto consensus is retained where it is superior, providing objective consensus criterion to enable decentralized node bootstrapping.</p><p>For more info and to monitor development progress, see <a href="https://www.avalanche.cash/">Avalanche.cash</a></p><p>‍</p>

large_6335d9ece86886df3ff2dac7_avalanche-live.jpeg

medium_6335d9ece86886df3ff2dac7_avalanche-live.jpeg

small_6335d9ece86886df3ff2dac7_avalanche-live.jpeg

thumbnail_6335d9ece86886df3ff2dac7_avalanche-live.jpeg

6335d9ece86886df3ff2dac7_avalanche-live.jpeg

On September 14th 2022, the eCash network was upgraded to support the finalization of blocks using Avalanche Post-Consensus.

Avalanche Post-Consensus on eCash

<p>September was a phenomenal month where we were able to achieve huge milestones! </p><p>‍</p><p>Did you miss any of the updates? </p><p>‍</p><p>Let’s take you through a recap!&nbsp; </p><p>‍</p><h2> Key Highlights - Cashtab Wallet</h2><p>‍</p><p>Chronik implementation milestones:</p><p>UTXO handling migration to Chronik (completed)</p><p>Transaction history via Chronik (50% complete)</p><p>‍</p><p>UX Improvements:</p><p> Real-time user update notifications</p><p> New hamburger menu</p><p>‍</p><h2> Key Highlights - Bitcoin ABC Node Software</h2><p>‍</p><p>  Bitcoin ABC releases versions 0.26.0 introducing Avalanche Post-Consensus — bringing 1-block finality and 51% attack prevention to eCash!</p><p>‍</p><p>  Bitcoin ABC releases versions 0.26.1 &amp; 0.26.2 bringing several RPC and logging improvements and new RPCs allowing node operators easily query if a transaction/block is finalized by Avalanche voting.</p><p>‍</p><p><a href="https://bitcoinabc.org/releases/">https://bitcoinabc.org/releases/</a></p><p>‍</p><p>‍ eCash JSON-RPC Libary for developers by eCash dev <a href="https://twitter.com/pungentaura">@pungentaura</a></p><p>‍</p><p>This library serves as a tiny layer between an application and an eCash node daemon.</p><p>‍</p><p>JavaScript: <a href="https://www.npmjs.com/package/ecash-rpc">https://www.npmjs.com/package/ecash-rpc</a></p><p>Python: <a href="https://pypi.org/project/ecashrpc/">https://pypi.org/project/ecashrpc/</a></p><p>‍</p><h2> Key Highlights - Electrum ABC Wallet</h2><p>‍</p><p>  Electrum ABC 5.1.5 is released bringing improvements to the Avalanche Proof Editor tool, minor bug fixes, and making explorer.e.cash the default block explorer.</p><p>‍</p><p><a href="https://www.bitcoinabc.org/electrum/">https://www.bitcoinabc.org/electrum/</a></p><p>‍</p><h2> Key Highlights - Avalanche on eCash</h2><p>‍</p><p>⚙️ On Sep 14th at 12:00 UTC, Avalanche Post-Consensus went live on eCash Mainnet! </p><p>‍</p><p> Avalanche.cash</p><p>‍</p><p> eCash Avalanche Staking Tutorial&nbsp;</p><p> <a href="https://www.bitcoinabc.org/2022-09-07-avalanche-staking-tutorial/">https://www.bitcoinabc.org/2022-09-07-avalanche-staking-tutorial/</a></p><p>‍</p><p> Avalanche Post-Consensus on eCash - Benefits for Miners, Exchanges, and Everyday People</p><p> https://www.bitcoinabc.org/2022-09-29-avalanche-post-consensus/</p><p>‍</p><p>eCash Avalanche Node Setup Part 1: Learn How to Setup a VPS eCash Node</p><p> https://youtube.com/watch?v=ls88OH3eGwQ&nbsp;</p><p>‍</p><p>eCash Avalanche Node Setup Part 2: Learn How to Stake your XEC Coins by Creating an Avalanche Stake Proof &amp; Configuring your Node to Use it:&nbsp;</p><p> <a href="https://www.youtube.com/watch?v=3k5M4k8OF-I&t=0s">https://www.youtube.com/watch?v=3k5M4k8OF-I&amp;t=0s</a></p><figure class="w-richtext-figure-type-video w-richtext-align-fullwidth" style="padding-bottom:56.206088992974244%" data-rt-type="video" data-rt-align="fullwidth" data-rt-max-width="" data-rt-max-height="56.206088992974244%" data-rt-dimensions="854:480" data-page-url="https://www.youtube.com/watch?v=3k5M4k8OF-I&t=0s"><div><iframe allowfullscreen="true" frameborder="0" scrolling="no" src="https://www.youtube.com/embed/3k5M4k8OF-I?start=0" title="Avalanche Node Setup Part 2: Create a Stake Proof for your eCash Node"></iframe></div></figure><p>‍</p><h2> eCash Avalanche Network Overview</h2><figure class="w-richtext-figure-type-image w-richtext-align-fullwidth" style="max-width:1600px" data-rt-type="image" data-rt-align="fullwidth" data-rt-max-width="1600px"><div><img src="https://strapi.fabien.cash/uploads/e_Cash_Monthly_Recap_September_2022_a3f956e6e7.png" width="auto" height="auto" loading="auto"></div></figure><p>‍</p><p>Total Staked: 84.3B XEC</p><p>Number of Nodes: 38</p><p>Number of Peers: 22</p><p>‍</p><p>Avalanche.cash</p><p>‍</p><h2> Key Highlights - News/Media</h2><p>‍</p><p>eCash founder Amaury Séchet &amp; eCash dev Antony Zegers joined Hayden Otto to discuss Avalanche Post-Consensus on eCash!</p><p> <a href="https://www.youtube.com/watch?v=cbhXNfSznAI">https://www.youtube.com/watch?v=cbhXNfSznAI</a></p><figure class="w-richtext-figure-type-video w-richtext-align-fullwidth" style="padding-bottom:56.206088992974244%" data-rt-type="video" data-rt-align="fullwidth" data-rt-max-width="" data-rt-max-height="56.206088992974244%" data-rt-dimensions="854:480" data-page-url="https://www.youtube.com/watch?v=cbhXNfSznAI"><div><iframe allowfullscreen="true" frameborder="0" scrolling="no" src="https://www.youtube.com/embed/cbhXNfSznAI" title="Avalanche Post-Consensus on eCash (XEC) w/ Amaury Séchet & Antony Zegers"></iframe></div></figure><p>‍</p><p> 이캐시, 오는 14일 아발란체 메인넷 도입</p><p> <a href="http://datanet.co.kr/news/articleView.html?idxno=176340">http://datanet.co.kr/news/articleView.html?idxno=176340</a></p><p>‍</p><p>上线雪崩共识，eCash迎来里程碑时刻</p><p><a href="https://mp.weixin.qq.com/s/v3AmSoz40gR946dMpIiLig">https://mp.weixin.qq.com/s/v3AmSoz40gR946dMpIiLig</a></p><p>‍</p><h2> Key Highlights - Community &amp; Milestones</h2><p>‍</p><p> We officially kicked off the Contribution Rewards Program, welcoming everyone to contribute and win from our 100M XEC reward pool.</p><p>‍</p><p> eCash hits 6K+ members milestone on r/eCash!</p><p>‍</p><h2>Towards October</h2><p>‍</p><p>What a month it's been for eCash! </p><p>‍</p><p>We'd like to thank the eCash community for all their support! Building continues, much more to come in October. Stay tuned!</p><p>‍</p>

eCash Monthly Recap - September 2022
eCash Monthly Recap - September 2022
eCash Monthly Recap - September 2022

Key Highlights - Cashtab Wallet

Key Highlights - Bitcoin ABC Node Software

Key Highlights - Electrum ABC Wallet

Key Highlights - Avalanche on eCash

eCash Avalanche Network Overview

Key Highlights - News/Media

Key Highlights - Community & Milestones

Towards October

You may also like
You may also like
You may also like

eCash Avalanche Tutorial

Avalanche Post-Consensus on eCash

eCash Monthly Recap - September 2022eCash Monthly Recap - September 2022eCash Monthly Recap - September 2022

Key Highlights - Cashtab Wallet

Key Highlights - Bitcoin ABC Node Software

Key Highlights - Electrum ABC Wallet

Key Highlights - Avalanche on eCash

eCash Avalanche Network Overview

Key Highlights - News/Media

Key Highlights - Community & Milestones

Towards October

You may also likeYou may also likeYou may also like

eCash Avalanche Tutorial

Avalanche Post-Consensus on eCash

eCash Monthly Recap - September 2022
eCash Monthly Recap - September 2022
eCash Monthly Recap - September 2022

You may also like
You may also like
You may also like