<?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"><channel><title><![CDATA[What else would you like to see on the Zano roadmap?]]></title><description><![CDATA[<p dir="auto">I'm curious to find out what else the community would like to see being focused on by the Zano team.</p>
<p dir="auto">Please note that the core team works on improving the blockchain itself. Projects built on top of it are mostly done by others.</p>
<p dir="auto">Roadmap link: <a href="https://zano.org/roadmap" rel="nofollow ugc">https://zano.org/roadmap</a></p>
]]></description><link>https://forum.zano.org/topic/9/what-else-would-you-like-to-see-on-the-zano-roadmap</link><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Jul 2026 15:49:25 GMT</lastBuildDate><atom:link href="https://forum.zano.org/topic/9.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 15 Jul 2026 12:26:27 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to What else would you like to see on the Zano roadmap? on Mon, 20 Jul 2026 18:44:33 GMT]]></title><description><![CDATA[<p dir="auto">The updated roadmap is ambitious, and the Zano Execution Layer could eventually add substantial utility to the ecosystem. My concern is not its potential value, but the order of priorities.</p>
<p dir="auto">The published roadmap does not yet appear to reflect the recent change in the post-quantum planning environment. Following Majorana 2, Microsoft now aims to achieve a scalable quantum computer by 2029. Separately, Executive Order 14412 has made post-quantum migration a current United States engineering programme, with a federal pilot due by the end of 2027 and migration deadlines for high-value and high-impact systems in 2030 and 2031.</p>
<p dir="auto">None of those dates proves that Ed25519 will be broken in 2029, 2030 or 2031. They do, however, show that waiting for a demonstrated cryptographically relevant quantum computer before beginning architectural preparation would be an unsafe strategy.</p>
<p dir="auto">Zano also has a specific custody exposure that should be distinguished from address privacy. Each unspent output publishes a one-time public key P = xG. The permanent wallet address may remain hidden, but if elliptic-curve discrete logarithms became tractable, the corresponding one-time spending secret x could be recovered directly from the output. Zenith's shorter block times and faster confirmations do not remove that exposure.</p>
<p dir="auto">I therefore believe that post-quantum custody and migration should become a core roadmap priority, particularly while HF7 and Zenith are still being prepared. The first objective need not be a complete post-quantum reconstruction of Zarcanum and Zenith. It should be a protected custody destination, probably beginning with a hybrid output requiring both classical and post-quantum authorization, together with wallet migration, backup and recovery support.</p>
<p dir="auto">This may require postponing lower-priority expansion work where it competes for the same core developers, wallet engineers, cryptographic reviewers, testing capacity or hard-fork coordination. The Execution Layer is the clearest example: it may be valuable later, but it does not protect existing Zano outputs or prepare the base layer for cryptographic migration.</p>
<p dir="auto">Projects developed by genuinely independent teams would not necessarily need to stop. The point is that base-layer custody and migration should take precedence wherever resources overlap.</p>
<p dir="auto">This is not an argument against Zenith. On the contrary, Zenith may be the best opportunity to introduce the versioning, migration paths and architectural separation required for an orderly post-quantum transition.</p>
]]></description><link>https://forum.zano.org/post/92</link><guid isPermaLink="true">https://forum.zano.org/post/92</guid><dc:creator><![CDATA[Yep]]></dc:creator><pubDate>Mon, 20 Jul 2026 18:44:33 GMT</pubDate></item><item><title><![CDATA[Reply to What else would you like to see on the Zano roadmap? on Thu, 16 Jul 2026 05:52:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ren888yin" aria-label="Profile: ren888yin">@<bdi>ren888yin</bdi></a> Yes</p>
]]></description><link>https://forum.zano.org/post/45</link><guid isPermaLink="true">https://forum.zano.org/post/45</guid><dc:creator><![CDATA[acf]]></dc:creator><pubDate>Thu, 16 Jul 2026 05:52:18 GMT</pubDate></item><item><title><![CDATA[Reply to What else would you like to see on the Zano roadmap? on Thu, 16 Jul 2026 04:29:56 GMT]]></title><description><![CDATA[<p dir="auto">be cool to get the escrow live again, i realise it was put on hold due to lack of use but now that people can vibecode it could offer some really cool things to be built on Zano</p>
]]></description><link>https://forum.zano.org/post/42</link><guid isPermaLink="true">https://forum.zano.org/post/42</guid><dc:creator><![CDATA[htzano]]></dc:creator><pubDate>Thu, 16 Jul 2026 04:29:56 GMT</pubDate></item><item><title><![CDATA[Reply to What else would you like to see on the Zano roadmap? on Wed, 15 Jul 2026 19:56:38 GMT]]></title><description><![CDATA[<p dir="auto">Great thread! Here is my short prayer on the private Hyperliquid idea.</p>
<p dir="auto">Hyperliquid is transparent. Zano is private. Let us merge them.</p>
<p dir="auto">HF6 brings Gateway Addresses – exchanges can finally integrate.</p>
<p dir="auto">Zarcanum gives private staking no one else has.</p>
<p dir="auto">Confidential Assets hide everything: sender, amount, asset type.</p>
<p dir="auto">Ionic Swaps execute trades atomically with zero visibility.</p>
<p dir="auto">No front-running. No MEV. No whales hunting your liquidation.</p>
<p dir="auto">Bridge native ZANO cross-chain via trustless Bridgeless.</p>
<p dir="auto">Build a perps exchange where positions stay hidden.</p>
<p dir="auto">Institutions trade size without revealing strategy.</p>
<p dir="auto">Retail trades without getting eaten.</p>
<p dir="auto">Who builds this? The Zano army does. Let us go.</p>
]]></description><link>https://forum.zano.org/post/36</link><guid isPermaLink="true">https://forum.zano.org/post/36</guid><dc:creator><![CDATA[god]]></dc:creator><pubDate>Wed, 15 Jul 2026 19:56:38 GMT</pubDate></item><item><title><![CDATA[Reply to What else would you like to see on the Zano roadmap? on Wed, 15 Jul 2026 16:31:59 GMT]]></title><description><![CDATA[<p dir="auto">Will Zano be able to be added to more mainstream crypto wallets after HF6?</p>
]]></description><link>https://forum.zano.org/post/30</link><guid isPermaLink="true">https://forum.zano.org/post/30</guid><dc:creator><![CDATA[ren888yin]]></dc:creator><pubDate>Wed, 15 Jul 2026 16:31:59 GMT</pubDate></item></channel></rss>