<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zach Hildreth on Medium]]></title>
        <description><![CDATA[Stories by Zach Hildreth on Medium]]></description>
        <link>https://medium.com/@zach_62507?source=rss-2448f3f359e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kct4UgK-drvc6xnE</url>
            <title>Stories by Zach Hildreth on Medium</title>
            <link>https://medium.com/@zach_62507?source=rss-2448f3f359e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:55:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zach_62507/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Testnet V2 — Test 1 Server Setup]]></title>
            <link>https://medium.com/x-cash/testnet-v2-test-1-server-setup-86acd0e9a2f2?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/86acd0e9a2f2</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dpos]]></category>
            <category><![CDATA[dpop]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 21:58:44 GMT</pubDate>
            <atom:updated>2022-12-21T21:58:44.994Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testnet V2 — Test 1 Server Setup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*vo_KT4w2fthiarwi.png" /></figure><p>Dear Community, We are taking the time to write today, to explain how to setup a server for the testnet V2.</p><p>The process is almost the same as the mainnet, and you will be able to follow the mainnet tutorials to setup this server, however this article will tell you during the tutorials what to do differently.</p><h3>Server Setup</h3><p>First you will need to follow this tutorial</p><p><a href="https://docs.xcash.foundation/dpops/server-setup">https://docs.xcash.foundation/dpops/server-setup</a></p><p>their are no changes to this, although their is a note. You will need certain ports open on the server. Their is a firewall included that opens these ports, however some server companies force you to declare open ports on their GUI on their dashpanel as well. You can use an online tool to confirm after setup if your ports are open.</p><p>For mainnet you need the following ports open: 18280,18281,18283 (possibly 80 if running shared delegate)</p><p>For testnet you need the following ports open: 18280,18281,18283,18286 (possibly 80 if running shared delegate)</p><p>What is 18286? this is another empty wallet for turbo tx queries that gets generated when you install. The key is never shown to you at the final summary page, as your not suppose to ever use this wallet. Please do not send xcash to that wallet on port 18286 as its open to the internet. The purpose of this wallet is to expose the xcash-rpc-wallet commands for each delegate to the internet (the non safety concerning ones) this way the merchant tool for turbo tx can query and verify quick tx.</p><h3>Install The Node</h3><p>Next you will need to follow this tutorial</p><p><a href="https://docs.xcash.foundation/dpops/node-installation#installer-script">https://docs.xcash.foundation/dpops/node-installation</a></p><p>Here are the changes:</p><p><a href="https://docs.xcash.foundation/dpops/node-installation#installer-script">https://docs.xcash.foundation/dpops/node-installation#installer-script</a></p><p>for this part use this command instead of the one given</p><p>source &lt;(curl -sSL <a href="https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/remote-data/scripts/autoinstaller/autoinstaller.sh">https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/remote-data/scripts/autoinstaller/autoinstaller.sh</a>) &amp;&amp; sudo systemctl stop xcash-dpops</p><h3>Set The Start Time</h3><p>Now its time to set the start time. If your started the testnet with us at launch date, you will be familiar with this process.</p><p>#1 Change the start time and date (5PM Paris time, January 16, 2023)</p><p>sudo nano /lib/systemd/system/xcash-dpops.service &amp;&amp; sudo systemctl daemon-reload</p><p>On the line:</p><p>ExecStart=~/xcash-official/xcash-dpops/build/xcash-dpops --block-verifiers-secret-key &lt;BLOCK_VERIFIER_SECRET_KEY&gt;</p><p>add the flag -- start-time 123 0 16 15 56 at the end of the line.</p><p>The line should look like :</p><p>ExecStart=~/xcash-official/xcash-dpops/build/xcash-dpops --block-verifiers-secret-key &lt;BLOCK_VERIFIER_SECRET_KEY&gt; --start-time 123 0 16 15 56</p><p>#3 Restart DPOPS</p><p>sudo systemctl restart xcash-dpops &amp;&amp; journalctl --unit=xcash-dpops -n 100 --follow --output cat</p><h3>Register Delegate</h3><p>Next you will need to follow this tutorial</p><p><a href="https://docs.xcash.foundation/dpops/register-delegate">https://docs.xcash.foundation/dpops/register-delegate</a></p><p>There are no changes</p><h3>Voting and Conclusion</h3><p>Note if your going to vote and following <a href="https://docs.xcash.foundation/dpops/vote-and-staking">https://docs.xcash.foundation/dpops/vote-and-staking</a> make sure you use the old mainnet syntax of voting (without the extra amount|all parameter) as its not implemented until we start the testnet minting process</p><p>Once you setup the server just view the logs (journalctl --unit=xcash-dpops -n 100 --follow --output cat) to make sure it says “Waiting for the specific start time”, and wait for the testnet to start. We look forward to testing the various features of the testnet V2 with the community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86acd0e9a2f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/testnet-v2-test-1-server-setup-86acd0e9a2f2">Testnet V2 — Test 1 Server Setup</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testnet V2 — Test 1 Information]]></title>
            <link>https://medium.com/x-cash/testnet-v2-test-1-information-452168df45e0?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/452168df45e0</guid>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[dpos]]></category>
            <category><![CDATA[rbf]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Mon, 21 Nov 2022 17:11:38 GMT</pubDate>
            <atom:updated>2022-11-21T17:11:38.141Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testnet V2 — Test 1 Information</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*7o8vbv2FvMGtaHl1.png" /></figure><p>Dear Community, We are taking the time to write today, to announce what we are going to be testing on the testnet V2. The snapshot has just happened almost about 3 hours ago!!! I want to thank everyone that is still interested in the project and supporting the testnet, as we will have many fun new features to try out on this testnet cycle.</p><h3><strong>Code Link</strong></h3><p>Here is the code link for the changes to xcash on this testnet as of now. We will use the “remote-data” branch of both repos:</p><p><a href="https://github.com/X-CASH-official/xcash-core/commits/remote-data">https://github.com/X-CASH-official/xcash-core/commits/remote-data</a><br><a href="https://github.com/X-CASH-official/xcash-dpops/commits/remote-data">https://github.com/X-CASH-official/xcash-dpops/commits/remote-data</a></p><h3><strong>Non Protocol Changes</strong></h3><p>Before we can start testing new protocols, we need to test many DPOPS enhancements and improvements made by the community and the team. These are already in the code and will be running day 1 when the first block is created. These include:</p><p>Various upgrades to work with Ubuntu 22.04 (the new LTS).<br>Various improvements to how networking code works.<br>Performance improvements on certain functions of the code.</p><p>We will run this for about a week or two to make sure its stable and that we have enough participants.</p><h3>Protocol Changes and Additions</h3><p>Once this is finished we will start testing the new protocols and features of xcash and xcash dpops. These will include (in this order we will test them):</p><h3><strong>DPOPS Split Balance Voting</strong></h3><p>Xcash always listens to the community, and tries to adapt the product to what the community wants. I personally heard multiple community members over the year ask for this specific feature. This will allow one to now vote for one delegate but only allocate a certain amount of the wallet to them, and keep the other part for spending trading etc. The wallet will know when you send a tx to only use the xcash marked as “savings” not the xcash marked as “staking”. When the “savings” xcash is 0, the wallet will not be able to send any xcash until you clear the marks on the wallet using a new command.</p><p>It sounds a little complicated but is really simple.</p><p>Old commands for vote and revote:</p><blockquote>vote &lt;delegates_name|delegates_public_address&gt;<br>revote</blockquote><p>New commands for vote and revote:</p><blockquote>vote &lt;delegates_name|delegates_public_address&gt; &lt;amount|all&gt;<br>revote &lt;amount|all&gt;</blockquote><p>with the new command “clear_staked_balance” that will remove all marks and allow one to use any previous staked amount for sending. Note it will not remove the vote, but will just remove the marks so one can send from the staking xcash (and will break the reserve proof like voting in version 1)</p><p>Note this will not currently work for voting for multiple delegates from the same wallet, but this innovation allows for this to happen at a later date once this first production is ready. This just allows one to not have to make 2+ wallets for their staking and spending xcash.</p><h3>Turbo TX</h3><p>These are tx that take a few seconds to confirm on the network. Using our unique blockchain structure of DBFT and UTXO unspent system, we have possibly created a system for quick tx on our network, that can be confirmed through the delegates using a tool. This will be very important for merchant applications especially in person stores as users can pay for items in seconds with full verification from the merchant that their can be a reversal. For those that know about RBF tx on bitcoin style blockchains, this system is superior to it and eliminates all of the risk.</p><p>Do these replace the instant payments we saw in a video long ago? No its a enhancement as we can have layer 1instant payments, and layer 2 instant virtual payments as seen in the video. Those are still a work in progress.</p><p><strong>A rough draft of the documentation</strong> from my internal setup can be found here <a href="https://docs.xcash.foundation/turbotx/get-started">https://docs.xcash.foundation/turbotx/get-started</a> as this will give more details about what this protocol is (RBF vs this) and the user/delegate interaction process. (the theory of innovation can be found at <a href="https://docs.xcash.foundation/turbotx/introduction">https://docs.xcash.foundation/turbotx/introduction</a>)</p><h3><strong>Xcash Namespace Protocol / Public TX 2.0</strong></h3><p>We have talked about this one in the past, but it essentially a namespace service run by the delegates. A user can register a namespace and this will automatically include .xcash, .sxcash and .pxcash extensions (and any others we develop in the future). Users will then be able to use these in different ways:</p><p>.xcash — give this to a user (instead of your public address) to have them be able to send payments to you.</p><p>.sxcash — give this to a user to have them be forced to send you a private tx.</p><p>.pxcash — give this to a user to have them be forced to send you a public tx.</p><p><strong>A rough draft of the documentatio</strong>n from my internal setup can be found here <a href="https://docs.xcash.foundation/remotedata/get-started">https://docs.xcash.foundation/remotedata/get-started</a> as this will give more details about what this protocol is and the user/delegate interaction process.</p><h3>Whats Next?</h3><p>Besides reading the documentation drafts to familiarize yourself with the new protocols, on Monday December 5, 2022 we will post an article stating how to setup your server. If your planning on participating black Friday is a great time to look into getting a server (any Ubuntu 18.04 and up will work including 22.04). I will use the time between Nov 21 and December 5, to write this tutorial and setup the testnet and seed nodes, and fix any remaining problems if their are any that appear. The testnet is still scheduled for January 2 as of now, but stay tuned to all of the articles if that changes for any reason.</p><p>We look forward to testing the various features of the testnet V2 with the community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=452168df45e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/testnet-v2-test-1-information-452168df45e0">Testnet V2 — Test 1 Information</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testnet Refresh V2]]></title>
            <link>https://medium.com/x-cash/testnet-refresh-v2-3c1797f91f70?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c1797f91f70</guid>
            <category><![CDATA[xcash-dpops]]></category>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[testnet]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Sat, 22 Oct 2022 22:24:10 GMT</pubDate>
            <atom:updated>2022-10-22T22:24:10.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*k_zvMiG_Y1-yDkII.png" /></figure><p>Dear Community,</p><p>We are taking the time to write today, to announce the new testnet schedule and reward structure for the Testnet V2.</p><p>As we discussed in the beginning of the year, we will have a refresh of the testnet about every six months and will have different things to test during every version of the testnet.</p><p>For the next testnet (V2) we will test many things, such as Ubuntu 22.04 compatibility and many community xcash dpops improvements on github. We also have two protocols and one new DPOPS voting feature to test. <strong>We will make a separate announcement on these once the snapshot has taken place.</strong></p><p>The <strong>testnet snapshot</strong> will be at block height <strong>980000</strong> which is estimated to happen around <strong>November 21, 2022</strong> that is about <strong>4 weeks from today</strong>.</p><p>The testnet will then start producing blocks on <strong>January 2, 2023 </strong>that is about <strong>10 weeks from today and 6 weeks from the snapshot</strong>.</p><p>This will give about 4–5 weeks (6 weeks but will take a week or two for me to setup seed nodes and make sure everything is working) for everyone to setup their delegate and vote after the snapshot has taken place. <strong>We will detail the changes and all protocols we will test in the testnet V2, the same time the snapshot takes place, in another article</strong>.</p><p>This way everyone has the full schedule of what will be tested for the next months and can decide if they want to participate in the testnet V2. We have set the dates to be around the holidays and to give enough time for anyone who wants to participate to setup their server and ask any question they might have.</p><h3>How To Prepare For The Snapshot</h3><p><strong>You will need to have any xcash you want to be cloned onto the testnet in a wallet you have the private keys for (not xbank or exchanges and not wxcash) only paper, mobile, CLI and GUI would be supported.</strong></p><p><strong>QUESTION: I already have a mainnet delegate, and a voting wallet with my xcash, can I use the same setup on the testnet?</strong></p><p>Yes. At this point since DPOPS is on mainnet and deemed secure it should be fine to reuse your data. Of course their is no guarantee some kind of bug in the code or testnet code will exist that allows a testnet participant to view sensitive data, but we are not too worried about this, and will be using our seed nodes (wallet and VRF keys) on the mainnet for the testnet as well.</p><p>We also suggest you start looking for what server you might want to use, this way you are ready after the snapshot to setup and vote or have people vote for you. The same requirements for xcash dpops will work, and we will support and encourage to use Ubuntu 22.04 (the latest LTS)</p><h3>New Testnet Reward Structure</h3><p>Its important that we have the full testnet amount and full participation of the community (50 servers), to test these new protocols. These will require everyone to be active and fully engaged. Because of this, the new structure of rewards will be the following:</p><p><strong>The first block of each day in the month (according to UTC time), will be worth 300,000 mainnet xcash</strong>. This has been decided as the best way to ensure participation each day from the community, and the fairest way to have the contest. It also adds some excitement each day, as you have a new chance each day to win!</p><p>This will be easy to log as we all will have logs of this on our xcash dpops servers. Everyone can verify with the following terminal command:</p><pre>journalctl --unit=xcash-dpops -n 1100000 --output cat | grep -A 18 &quot;00:00:20 UTC&quot;</pre><p>This has been chosen as the best way for now to do the “contest” because it is random and the VRF system can pick the winners. It also does not take any previous participation in to consideration, but at the same time rewards constant participation.</p><p><strong>The xcash will be sent to the test delegates public address on the mainnet</strong>, sometime in the following month (so make sure to back these up when installing your testnet server at the print out of details at the end of the installation)</p><p>We are looking forward to the next testnet cycle (testnet V2) and hope that everyone is as excited as we are to test the next protocol.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c1797f91f70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/testnet-refresh-v2-3c1797f91f70">Testnet Refresh V2</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Half Recap, Second Half Look Ahead]]></title>
            <link>https://medium.com/x-cash/first-half-recap-second-half-look-ahead-818b6e5d7425?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/818b6e5d7425</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dpos]]></category>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[xcash-dpops]]></category>
            <category><![CDATA[cryptocurrency-news]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Mon, 27 Jun 2022 14:55:32 GMT</pubDate>
            <atom:updated>2022-06-27T14:55:32.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*V-m7jr8D29PzUhTY.png" /></figure><p>Dear Community, we are taking the time to write today, to give a first half of the year review and a look ahead to the second half of the year.</p><p>In the first half of the year there was a lot of internal stuff to do. The team restructuring was started and completed. You will be able to see the team members and their roles once we release the new website.</p><p>There was a lot of coding to be worked on, and unfortunately their were no new releases, but most projects that the team were working on are about 80%+ done at this time.</p><p>There also was the process of restructuring some of the servers. This is still a work in progress.</p><h3>Second Half of the Year</h3><p>The second half of the year should be much more exciting as the work we have done in the first half of the year will be ready to be released. <strong>Starting in July,</strong> <strong>you will see X-Cash take on a new release schedule that has not been done in the coin’s history.</strong> Traditionally, we have always had a few projects being worked on by different team members at the same time and have had releases every quarter or two, due to the nature of the projects. This will change in this second half of the year as we have a larger team, working on more projects. The timing worked out to where most people are finishing around the same time. Because of these two factors we can now for this second half of the year transition to a more stable and timed release schedule.</p><p>We don’t want to list each release here today or what the frequency of the release schedule will be, but all categories of xcash have been worked on, and will be improved in this second half of the year, including:</p><p>X-Cash blockchain<br>X-Cash second layer protocols<br>X-Cash tools and building tools<br>X-Cash products (X-Bank, X-Payments, etc etc)<br>Existing X-Cash services</p><p>The testnet will be revamped with a new protocol test this year (hopefully two new protocols), extra X-Cash DPOPS functions, and a new reward structure as well.</p><p>Of course, we are still working on marketing and exchanges as well. In the first half of the year there was a few marketing efforts, including this yahoo news article about our project.</p><p><a href="https://www.yahoo.com/now/x-cash-innovative-privacy-centered-124000661.html">https://www.yahoo.com/now/x-cash-innovative-privacy-centered-124000661.html</a></p><p>We also worked on exchanges as well. We really want to find one that will work for the community and be one that the community will want to use, so it will take extra time as we go one or two at a time, talking with the exchanges, the team, and the Paris founders about, etc etc. This is a weekly thing were working on.</p><p>Once again, I want to thank everyone who continually supports this project.</p><p>We will be releasing an article about each new release or piece of information, so make sure to stay up to date every week, to not miss a release.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=818b6e5d7425" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/first-half-recap-second-half-look-ahead-818b6e5d7425">First Half Recap, Second Half Look Ahead</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XCASH Core and DPOPS Update]]></title>
            <link>https://medium.com/x-cash/xcash-core-and-dpops-update-26bba67fa3ee?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/26bba67fa3ee</guid>
            <category><![CDATA[cores]]></category>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[dpop]]></category>
            <category><![CDATA[lhf]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 14:10:25 GMT</pubDate>
            <atom:updated>2022-03-14T15:05:38.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oGWQwu58tJcs4grYB2PGRg.png" /></figure><p>Dear Community,<br>Today we are releasing xcash-core 2.2.0 and xcash-dpops 1.2.0</p><p><strong>Note: You will need to update before block height 910000 which is expected to happen around Wednesday, March 23, 2022 03:00:00 UTC</strong></p><h3>XCASH-CORE Update 2.2.0</h3><p>Some highlights of this update:<br>- Updated hashes so xcashd can sync, before we fixed the issue.<br>- xcashd syncing improvements at block 910000<br>- Removed most mining code. Test show virus false positives dropped as well.<br>- Fixed the docker file<br>- Boost 1.77.0 compatibly<br>- GCC 11 compatibility<br>- Fixed debug build not working</p><p>You can read the full list, and how to install at <a href="https://github.com/X-CASH-official/xcash-core/releases/tag/2.2.0">https://github.com/X-CASH-official/xcash-core/releases/tag/2.2.0</a></p><h3><strong>XCASH-DPOPS Update 1.2.0</strong></h3><p>Some highlights of this update (and the 1.1.0 update):<br>- Fixed synchronize-database-from-network-data-node parameter<br>- Added delegate error reporting parameter<br>- Added limits to shared delegates API for pagination<br>- Fixed syncing stability at time 1648221480 (Friday, March 25, 2022 15:18:00 UTC)<br>- Fixed autoinstaller custom paths<br>- Fixed autoinstaller search strings for finding install locations to make them more robust</p><p>Instructions on how to update xcash-dpops is at <a href="https://discord.com/channels/470575102203920395/746277791556698182/952931355401015376">https://discord.com/channels/470575102203920395/746277791556698182/952931355401015376</a></p><p>Thank you everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26bba67fa3ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/xcash-core-and-dpops-update-26bba67fa3ee">XCASH Core and DPOPS Update</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Q1 Review and Look Ahead]]></title>
            <link>https://medium.com/x-cash/q1-review-and-look-ahead-9da87d284434?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9da87d284434</guid>
            <category><![CDATA[x-cash]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Sat, 12 Mar 2022 15:58:06 GMT</pubDate>
            <atom:updated>2022-03-13T21:06:12.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*1r9ma0oXURzuuZNSXtSvEw.png" /></figure><p>Dear Community, We are taking the time to write today, to give a quarter 1 review and a look ahead to quarter 2 and the future. In Q1, there was a lot of internal work being done. Below is the following sections of what the team has worked on in Q1.</p><h3>Team Restructuring</h3><p>The process of team restructuring is just about complete. Both Paris Founders are still very much a part of this team, but they are taking a step back to concentrate on Flowdesk growth. This idea was proposed <br>by Guilhem, and everyone is on the same page, there are no internal fights or anything like that. We are all behind x-cash! Guilhem is still the CEO, but it was decided for Zach to step up and make day-to-day decisions for a more efficient direction of the coin. The majority of x-cash infrastructure is still compensated by the Paris team. They will stop by in the Discord occasionally or as time permits, as they still have roles, just not as many as before. New personnel has been added from the community as well to help x-cash grow and plan for the future. Zach also took the time this month to “re-energize” the team. That information will stay private, but the bulk of it was a 5-page speech outlining the future of x-cash.</p><p>No one has left the team, Dennis took some time off to take care of a personal issue, and he will be back soon enough. Existing members of the team are very capable of running x-bank and even adding <br>features while Dennis is out.</p><p>We are also working on a new xcash.foundation website, and we will publish another article on the new personnel once we have the website done.</p><h3>Coding</h3><p>The team has been really busy this past month or two. One of the topics is the new xcash.foundation website. It will include new wording, to keep with trends in the markets, and will have the full contributors list with pictures or avatars, as well as many other adjustments. We have numerous tasks that team members are doing in parallel. For example, we have been looking at new exchanges with <a href="http://twitter.com/x">@x</a>-$1 and <a href="http://twitter.com/CACO">@CACO</a>, and also have been working on concrete simple and fitting plans on marketing with <a href="http://twitter.com/Zurg">@Zurg</a>. These will be pushed out once we have the new website. In the pipeline, we have two that we believe will help our growth with minimal expenditure. Zach has been busy with the test net development and improvement. We just published an update to merge the test net to the master (v1.1.1). Updated were geared more towards the delegates, and you can check out the full changelog here.<br><a href="https://discord.com/channels/470575102203920395/746277791556698182/947325332841725982">https://discord.com/channels/470575102203920395/746277791556698182/947325332841725982</a></p><p>Zach is also making progress on the GUI wallet. <a href="http://twitter.com/miaumiau">@miaumiau</a> has been resolving many angular issues and adding numerous improvements for the wallet. We have also been trying to work on phase X (get the c++ code into the angular wallet to remove the RPC dependency) Zach made some progress on this, but it is still a work in progress and not enough for a full wallet at this point (one of the issues is that we can’t get tx but did everything else!) If the team gets stumped, we might do a big RFC on this, so watch this for if you are out there and want to make some x-cash by helping us out.</p><p><a href="http://twitter.com/Lovro">@Lovro</a> has been extremely busy with rewriting x payments to use slash commands, as this is a requirement starting from April of 2022. He plans on working with DPOPS connectivity and many other related projects to come throughout this year. Look for his article on the x-payment road map soon.</p><p>He has also built a python library for development using xcash. It includes wallet, daemon and dpops functions.</p><p><a href="https://github.com/X-CASH-official/XCASH-Ecosystem-api-wrapper">GitHub - X-CASH-official/XCASH-Ecosystem-api-wrapper: XCASH Ecosystem Api wrapper for python</a></p><p><a href="http://twitter.com/Twinkie">@Twinkie</a> has been working on the monitoring/profiling systems for x-bank and x-payments, which will help us better understand what our programs are using resource-wise and what we can optimize to increase efficiency.</p><p><a href="http://twitter.com/franciscom">@franciscom</a> has been working on many things as he has a good knowledge of technologies and can bounce around to where his expertise is needed. His main area has been x-bank testing and fixes, and other areas that will be revealed in the future.</p><h3>Next Protocol</h3><p>The next protocol instant payment&#39;s development is close to completion (as you saw from the video released last summer). We are working on trying to resolve a decentralized signing process for releasing payments (there is a persisting issue where just one delegate can freeze the wallet). The idea of just the seed nodes holding the wallet is not acceptable, as this will be the system for smart contract x-cash as well, so it needs to be done properly. Zach has been working on the voting as time permits, but we know this is the least exciting protocol for normal users, therefore it’s a low priority. There is a new idea for a protocol that we haven’t brought up before, that Zach will be researching as well.</p><p>Key features of this protocol would be:<br>- XCASH namespace creation. This will allow for users to purchase .xcash names in the namespace and send transactions to an easy to remember name instead of a address.<br>- namespace entries can be registered with any available delegate. Each delegate can set their own price, and users will be able to register with the current block producer, or wait for a cheaper one.<br>- Integration of Public TX 2.0 That will allow you to create wallets that can only receive public or only receive private transactions (using .pxcash and .sxcash namespaces). This can be important for business use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*lZQbPZ2zxl3xaSRaK2KiLA.png" /></figure><p>The protocol is currently being researched and developed by zach, as we thought the community would enjoy this protocol rather than voting, while we are still researching instant payments. The protocol will be deployed to an internal testnet first, and then will be deployed to the public testnet after.</p><h3>Conclusion</h3><p>As one can see, we are working very hard and have a lot of exciting things coming up.</p><p>Once again, I want to thank everyone who continually supports this project, and for the testnet delegates that are voluntary running nodes without any compensation (besides the monthly contest). We could not have done DPOPS without you, and are very thankful you are here for the testnet and upcoming protocol. If you see or know anything that can be improved, please reach out to us. X-CASH team wants to hear your thoughts and ideas on how this project can be improved and advanced. Remember, this is an open-source project and all contributions are welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9da87d284434" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/q1-review-and-look-ahead-9da87d284434">Q1 Review and Look Ahead</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DPOPS Testnet Instructions]]></title>
            <link>https://medium.com/x-cash/dpops-testnet-instructions-ada912abba8e?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ada912abba8e</guid>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[dpop]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Fri, 17 Dec 2021 13:43:08 GMT</pubDate>
            <atom:updated>2021-12-17T19:12:21.192Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHLgH9LmyNSy4pxJRT7Mcw.png" /></figure><p><strong>Dear Community,</strong></p><p>Today we would like to explain how to setup your node for the testnet. This is about the same process as setting up a node for the mainnet, but we will be using the “dpops-test” branch. You can follow any of the official tutorials for more in depth coverage of setting up a server, delegate or voting, registering etc, but this article will give the basics for full testnet participation.</p><p>You can view the delegates website for the testnet at <a href="http://dpops-test-delegates.xcash.foundation/">http://dpops-test-delegates.xcash.foundation</a></p><h3>Step 1</h3><p>Once you have a server ready, use the “dpops-test” branch autoinstaller to setup the server with the dpops code specifically for the testnet (make sure to use the default paths for everything as this is not fully tested yet on custom paths)</p><pre>source &lt;(curl -sSL <a href="https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/dpops-test/scripts/autoinstaller/autoinstaller.sh">https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/dpops-test/scripts/autoinstaller/autoinstaller.sh</a>)</pre><p>This will take about an hour but can depend on your server speed and internet speed.</p><h3>Step 2</h3><p>Now you need to stop xcash-dpops and xcash-rpc-wallet from running</p><pre>sudo systemctl stop xcash-dpops xcash-rpc-wallet</pre><h3>Step 3</h3><p>Now you need to edit the service file for dpops</p><pre>sudo nano /lib/systemd/system/xcash-dpops.service &amp;&amp; sudo systemctl daemon-reload</pre><p>just go to the end of the line that starts with ExecStart and add to the end of the line</p><pre>--start-time 122 1 8 16 56</pre><p>example my line looks like (if my key was all 0&#39;s)</p><pre>ExecStart=/root/xcash-official/xcash-dpops/build/xcash-dpops --block-verifiers-secret-key 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 --start-time 122 1 8 16 56</pre><h3>Step 4</h3><p>Note for this step, you can view your wallets password at any time by running</p><pre>cat /lib/systemd/system/xcash-rpc-wallet.service</pre><p>You can also view your DPOPS private key by running</p><pre>cat /lib/systemd/system/xcash-dpops.service</pre><p>The private key will be the 128 byte key and the public key will be the last 64 bytes of the 128 byte key</p><p>Now its time to register your delegate. You will need to open the delegate wallet to do this (replace YOURPASSWORD with your password from the install output)</p><pre>cd ~/xcash-official/xcash-wallets &amp;&amp; ~/xcash-official/xcash-core/build/release/bin/xcash-wallet-cli --wallet-file delegate-wallet --password “YOURPASSWORD”</pre><p>Once the wallet is fully synced and at the wallet prompt register the delegate by run the following</p><pre>delegate_register &lt;delegates_name&gt; &lt;delegates_IP_address&gt; &lt;delegates_public_key&gt;</pre><p>Where the following are</p><pre>&lt;delegates_name&gt; = any delegate name you want<br>&lt;delegates_IP_address&gt; = the ip of the server or a domain with an A record with the ip of the server<br>&lt;delegates_public_key&gt; = the delegate public key from the installation step</pre><p>this can take up to five minutes</p><p>then exit once your done (if you dont need to vote from this wallet)<br>type “exit” in the wallet</p><h3>Step 5</h3><p>Now you need to vote for your own delegate or get others to vote for you. If you want to vote it is recommended to download the testnet binaries to your local computer and open your wallet on your local computer (not the server).<br>you can download the testnet binaries from<br><a href="http://176.9.146.216/windows-bin.zip">windows-bin.zip</a><br><a href="http://176.9.146.216/linux-bin.zip">linux-bin.zip</a></p><p>The best way to connect to the testnet blockchain is to use a testnet remote node to vote. Once the binaries have been downloaded you can run the following to restore your wallet file. (its important you dont use an existing wallet file because it will have a cache for the mainnet, so you need to reimport your wallet to a new file)</p><p>Unzip the binaries and navigate to the folder in a CMD window or terminal and then run</p><p>Linux</p><pre>./xcash-wallet-cli --trusted-daemon --daemon-address dpops-test-1.xcash.foundation:18281 --restore-deterministic-wallet</pre><p>Windows</p><pre>xcash-wallet-cli --trusted-daemon --daemon-address dpops-test-1.xcash.foundation:18281 --restore-deterministic-wallet</pre><p>Then fill out the questions and let is fully scan the 880000 testnet blocks. Once done you can vote.</p><p>To vote run</p><pre>vote &lt;delegate_name&gt;</pre><p>This can take up to 1 hour</p><h3>Step 6</h3><p>Once you have registered and voted for your delegate it is now time to run the rpc-wallet and the xcash-dpops</p><pre>sudo systemctl restart xcash-rpc-wallet &amp;&amp; sleep 60s &amp;&amp; sudo systemctl restart xcash-dpops</pre><h3>Step 7</h3><p>You should be done and syncing from other dpops servers and ready to go. check the logs to make sure (you should see it has fully sycned the databases and has a message saying “Waiting for the specific start time”</p><pre>journalctl --unit=xcash-dpops -n 100 --output cat --follow</pre><p>If you have any questions ask a team member or in the general community!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ada912abba8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/dpops-testnet-instructions-ada912abba8e">DPOPS Testnet Instructions</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DPOPS Testnet Schedule]]></title>
            <link>https://medium.com/x-cash/dpops-testnet-schedule-35e79cc4de93?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/35e79cc4de93</guid>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[cryptonote]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Thu, 25 Nov 2021 15:02:38 GMT</pubDate>
            <atom:updated>2021-11-25T15:02:38.384Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tt12llmJderY8igK.png" /></figure><p>Dear Community,</p><p>Today I wanted to update you on the schedule for the DPOPS testnet. It will be crucial to have a public testnet up as we get closer to working on the next protocol. It will also provide us a sandbox to test updates.</p><p>I wanted to share this info at this time, since usually their are many sales on servers and VPS during this black Friday week.</p><h3>Schedule</h3><p><strong>Part 1 — Snapshot</strong><br>This will be when the snapshot takes place <strong>at block 880000</strong>. This is estimated to happen <strong>around Dec 8th</strong>.</p><p><strong>Part 2 — Voting opens</strong><br>This will be <strong>on December 20th</strong>. Between the snapshot and this date I will need to setup the testnet code, websites, servers and get the seed nodes running in registration mode. During this time I will ask some beta testers by DM (ones I have asked before to test things) to try to register and vote to confirm it is setup correctly</p><p><strong>Part 3 — Testnet starts</strong><br>This will be <strong>on January 8th</strong>. You will want to register and vote before this date. We will make sure it works and then do the test to upgrade to the HF and upgrade the server tools a few days later.</p><p><strong>We will need 50 servers as we want to run the same config as the mainnet. The official servers will only be the 5 seed nodes, so we need 45 servers from the community to participate. If not we may bump up the incentive reward or lower the server amount and dates might have to be moved</strong></p><h3>What do I need to do for each part?</h3><p><strong>Part 1 </strong>— Get a server if you want to participate. Make sure you have xcash that you want in addresses you have the keys for before this block height occurs. Once it occurs wait for the voting to open</p><p><strong>Part 2</strong> — You can start to register delegates, and possible get people to vote for you if they want to.</p><p><strong>Part 3</strong> — Be ready to start!</p><h4>Where can I get more info like instructions for each part config for systemd etc etc?</h4><p>Make sure to register on discord. This is where I will provide live info and commands for each part, and any changes that may happen or changes to the schedule. This is also where the commands will be given once the testnet starts for what and when were going to try it.</p><h3>Questions</h3><p><strong>#1 Can I use xcash on both chains?</strong><br>YOU CAN USE XCASH MAINNET ON THE TESTNET AT THE SAME TIME. meaning if you have a wallet with 100M you can use it on the testnet and keep it on the mainet as well. Just keep in mind that any newly created xcash on either chain after block 880000 will not be able to be used on both chains</p><p><strong>#2 Do voters or delegates get anything by participating in the testnet</strong><br>You do not get to keep any produced xcash on the testnet to the mainnet, and voters wont get any real xcash. The only rewards given will be once a month, the top 3 delegates in each stats category on the website will be sent 1M mainnet xcash at the end of each month. If delegates want their voters to participate in the testnet, they will need to setup their own deals with their voters.</p><p><strong>#3 What server can I use?</strong><br>This will have the same requirements as the mainnet.</p><p>Thank you everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35e79cc4de93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/dpops-testnet-schedule-35e79cc4de93">DPOPS Testnet Schedule</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Update: Core and DPOPS 2021 into 2022]]></title>
            <link>https://medium.com/x-cash/project-update-core-and-dpops-2021-into-2022-5fd2c5f63195?source=rss-2448f3f359e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fd2c5f63195</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dpop]]></category>
            <category><![CDATA[x-cash]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Zach Hildreth]]></dc:creator>
            <pubDate>Fri, 15 Oct 2021 01:50:53 GMT</pubDate>
            <atom:updated>2021-10-15T13:14:41.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XIMLdmlee3xXsqvR.png" /><figcaption>xcash project update</figcaption></figure><h3><strong>Dear community,</strong></h3><p>Today, we are starting a three part series of what to expect from X-Cash technology wise.</p><p>Today we will discuss what is upcoming with the DPoPS infrastructure and X-Cash Core for the end of the year and the start of next year.</p><h3><strong>What is DPoPS?</strong></h3><p>The <a href="https://medium.com/x-cash/x-cash-2-0-dpops-release-announcement-631795f2e8b1">DPoPS</a> (standing for Delegated-Proof-of-Private Stake) is a brand new and unique Delegate-Proof-of-Stake consensus integrated into X-Cash, an open-source fork of <a href="https://github.com/monero-project/monero">Monero</a> which has since the beginning of the project brought new innovation to the privacy coin space (notably <a href="https://x-network.io/whitepaper/XCASH_Yellowpaper_Hybrid-tx.pdf">FlexPrivacy</a>, public &amp; private transactions on the same blockchain, from the same wallet).</p><h3><strong>Updates for the end of the year</strong></h3><p>Our plans for DPOPS (and <a href="https://github.com/X-CASH-official/xcash-core">xcash-core</a>) until the end of year is to make it more stable, resolve any known issues, and add any performance or compatibility update. There are a few issues remaining at this time, and DPoPS needs to be 100% bug free before we add protocols on top of it. This is mainly due to the fact that protocols like instant send payments not only interact on top of DPoPS, but use a stripped down base of the core code from DPOPS in their code base.</p><p>The plan is to include all of these into a xcash-core 2.1.0 update and a xcash-dpops 1.1.0 update that will be released at the same time. To review the code already added to these branches, they are located at</p><p><a href="https://github.com/X-CASH-official/xcash-core/tree/2.1.0">https://github.com/X-CASH-official/xcash-core/tree/2.1.0</a><br><a href="https://github.com/X-CASH-official/xcash-dpops/tree/1.1.0">https://github.com/X-CASH-official/xcash-dpops/tree/1.1.0</a></p><p>These updates will include (currently added but not limited to):</p><p><strong>xcash-core</strong></p><ul><li>Various enhancements to the server and syncing blocks methods</li><li>Latest boost and other libraries compatibility</li><li>Latest Ubuntu Linux compatibility</li><li>latest GCC compatibility</li><li>Fix Docker file</li><li>Various updates to remove cryptnote legacy warnings and various C++ deprecated warnings, or libraries warnings</li></ul><p><strong>xcash-dpops</strong></p><ul><li>Various enhancements to the server and syncing blocks methods</li><li>Latest Ubuntu Linux compatibility</li><li>latest GCC compatibility</li><li>Merge farmage PR #61 <a href="https://github.com/X-CASH-official/xcash-dpops/pull/61">https://github.com/X-CASH-official/xcash-dpops/pull/61</a> that adds a cache for db DBFT checking</li><li>Merge snakeway PR #62 <a href="https://github.com/X-CASH-official/xcash-dpops/pull/62">https://github.com/X-CASH-official/xcash-dpops/pull/62</a> that fixes some thread unsafe problems</li><li>Updated all DPOPS tools to latest versions (mongo, mongo tools, mongoc driver, nodejs)</li><li>Fix all unit test</li></ul><h3><strong>Testnet Release Date</strong></h3><p>We have for months needed to setup a testnet for the future of XCash. Not only to have a testnet of the live blockchain, but to safely test new updates and protocols to the DPOPS base protocol. We will also eventually need a testnet once smart contracts are released and other higher level features that will involve the community of developers.</p><p>We will use this large update and end of the year timing to setup a testnet and run this update on the testnet before we deploy it to the mainnet. There has been a lot of community support for running a testnet and we really appreciate the community support in the alpha and beta stages, and we want to draw long support for the testnet, just like the block reward is keeping the mainnet support going.</p><p>We really want people dedicated to keeping the testnet going. A lot of people have expressed interest in running testnet nodes as extra servers and to continue to run their mainnet servers, or some people have only wanted to participate in the testnet. There are also voters who don&#39;t have enough to participate in the mainnet but would like to run a server.</p><p>We also don’t want to run 20 servers like we did in the alpha with only 10–15 ‘community servers’, as we have seen, the more realistic conditions the better.</p><p>We have come up with a solution that we think will work great for all of the above.</p><p>We will run a “open testnet” where anyone can run a server. The requirement is to be in the top 50 to produce blocks just like the mainnet. We will use a forked xcash blockchain (height will be close to current height when we start) and the blockchain will be re forked from the mainnet after 50000 blocks have been produced on the testnet, or 6 months if issues arrive during the testnet. This is to stay current with the xcash values of the mainnet. Everyone will be able to use their mainnet xcash values on the forked testnet (xcash value prior to the snapshot) and will move up and down the ranks just like the mainnet.</p><p>We don’t expect servers to have voters like the mainnet, but we expect small voters and or people who are not currently participating at all, to try to participate in the testnet, since the pressure to run a node is very little and your knowledge of the xcash ecosystem will grow.</p><p>The incentive to participate in the testnet will be three different types of rewards (with real mainnet xcash) will be awarded each month to the delegate&#39;s address on the mainnet.<br>Basically the top delegate on each of the categories at the end of the month (last block of the month) will be awarded <strong>1 million xcash</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcFoDpE0MqgyxwFg8tf93g.png" /></figure><p><a href="http://delegates.xcash.foundation/statistics">http://delegates.xcash.foundation/statistics</a></p><p>We think that this will give incentive for smaller voters or people not participating in the DPoPS to run their own server on the testnet.</p><p>No release date has been given for the testnet and there is still some work to be done on the 2.1.0 and 1.1.0 branches, but we will let you know in advance before the testnet snapshot for round 1.</p><h3><strong>Next Protocol</strong></h3><p>Zach had a lot of time during the beta testing phase of DPoPS to research and work on some of the next protocols.</p><p>As we have seen with the instant send video (<a href="https://www.youtube.com/watch?v=eemT3A3kGeg">https://www.youtube.com/watch?v=eemT3A3kGeg</a>), that protocol is about 80% done and is almost ready for alpha. We also have another protocol that has not been mentioned until now. We believe that a voting protocol would be very useful for the community. It allows the team to propose a question to the community, and for the community to let their DPoPS delegate know what they want. Then the DPoPS delegates vote and the results are not artificially inflated since we carried out the vote on the xcash blockchain using the delegates and DPoPS infrastructure.</p><p>Those will be the next protocols, as both have coding done. We have not made a decision yet on which one, but of course we would love to hear the communities feedback on which one they think is more important at this stage.</p><p>Let us and Zach know on discord as this will be useful info.</p><p>If you have already not seen the demo of the instant send payments on xcash, you can watch that on Zach’s YouTube channel (Zachy Zone)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeemT3A3kGeg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeemT3A3kGeg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeemT3A3kGeg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c0c9727885aea11403582c4dc05d77b/href">https://medium.com/media/4c0c9727885aea11403582c4dc05d77b/href</a></iframe><h3><strong>Wait what about a rebase?</strong></h3><p>A rebase (updating the xcash-core base Monero code from 13.0.4 to the latest) is always on the table with the modular design. Since most features will be built on top of DPOPS (which is created from scratch) it will be possible to rebase to another version of Monero at any time. As of now this is not in the immediate plans, but as time goes on and protocols get built, it will make sense at some point to rebase. We have not seen any features yet that makes us want to rebase, but future talked about features like StringCT (ability to set the RingCT count to greater than 1000 not less than 100) will be a big reason to rebase</p><p>Thank you everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fd2c5f63195" width="1" height="1" alt=""><hr><p><a href="https://medium.com/x-cash/project-update-core-and-dpops-2021-into-2022-5fd2c5f63195">Project Update: Core and DPOPS 2021 into 2022</a> was originally published in <a href="https://medium.com/x-cash">X-Cash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>