<?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 ZkNoid on Medium]]></title>
        <description><![CDATA[Stories by ZkNoid on Medium]]></description>
        <link>https://medium.com/@zknoid?source=rss-514b792ab87d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*p5hCNC3CJiEebT_-i6gUWw.png</url>
            <title>Stories by ZkNoid on Medium</title>
            <link>https://medium.com/@zknoid?source=rss-514b792ab87d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:26:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zknoid/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[Wizard Battle 3-Month Roadmap]]></title>
            <link>https://medium.com/zknoid/wizard-battle-3-month-roadmap-8a85123d3b35?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a85123d3b35</guid>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[announcements]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 12:56:26 GMT</pubDate>
            <atom:updated>2026-01-30T12:56:26.822Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckVInxmPsidnGW6FLMpLPg.png" /></figure><p>Wizard Battle is approaching the end of its core development phase. The foundational systems — turn-based combat logic, wizard classes, core stats, gear framework, and zk-based battle verification — are already implemented and being internally tested.</p><p>Throughout 2025, our focus was on proving that a fully verifiable PvP game can feel responsive, verifiable, and fair without compromising gameplay. With the core mechanics now complete, Wizard Battle is entering a phase focused on public testing, balancing battle and economic systems, and introducing a competivive setting at full launch.</p><p>This article outlines our planned milestones for the next three months:</p><h3>February 2026 — Public Testnet &amp; Core Gameplay Validation</h3><p><strong>Goal:</strong> Open Wizard Battle to the public and validate core gameplay under real load.</p><h4>Planned Milestones</h4><ol><li>Core PvP/PvE gameplay loop available to all testnet users</li></ol><p>Earn resources → Craft items → Equip them in provably fair battles</p><p>2. Introduction of crafting mechanics</p><p>3. Implementation of NFT items based on Avalanche:</p><ul><li>Resources</li><li>Gear</li><li>Weapons</li></ul><p>4. zkProofs on Mina verifying:</p><ul><li>Ownership of equipped items</li><li>Correct initial battle state</li><li>Valid execution of combat rounds</li></ul><p>5. Public Testnet launch on Mina</p><p>6. Onboarding flow for new players</p><p>February will mark Wizard Battle’s transition from internal testing to public interaction. This phase is designed to surface real gameplay feedback and technical signals that cannot be replicated in closed testing.</p><p>For the Mina ecosystem, this provides:</p><ul><li>A live example of NFT items used inside a zkApp</li><li>Practical insight into integrating ownership, crafting, and gameplay logic</li><li>Real zkApp activity driven by non-financial use cases</li></ul><p>Feedback collected during this phase will directly inform balance adjustments and performance optimizations.</p><h3>March 2026 — Economy, Tournaments</h3><p><strong>Goal:</strong> Enable player-to-player interaction and structured competition.</p><h4>Planned Milestones</h4><ol><li>In-game market system for item trading</li><li>Controlled player-to-player exchanges</li><li>Tournament framework</li><li>Post-testnet balancing of combat and economic parameters</li></ol><p>This phase focuses on validating trust-minimized competition. Wizard Battle will demonstrate that:</p><ul><li>Tournament outcomes can be independently verified</li><li>Rankings are provably correct, rather than trust-based</li><li>Player economies can function without centralized custody</li></ul><h3>April 2026 — Mainnet Preparation &amp; Launch Event</h3><p><strong>Goal:</strong> Prepare Wizard Battle for mainnet deployment and community launch.</p><h4>Planned Milestones</h4><ol><li>Final gameplay balance adjustments</li><li>Performance optimizations</li><li>Security reviews and deployment preparation</li><li>Wizard Battle Mainnet deployment</li><li>Community event tied to launch</li></ol><p>April is focused on moving Wizard Battle from testnet to production. The mainnet launch will:</p><ul><li>Introduce a fully playable zkGame to Mina</li><li>Showcase turn-based zkApps operating in a live environment</li><li>Provide a long-running, interactive use case for zk beyond DeFi</li></ul><p>The launch event is designed to bring together players, developers, and ecosystem partners, highlighting what is possible when zero-knowledge technology is applied directly to gameplay.</p><h3>Looking Ahead</h3><p>This 3-month roadmap is focused on turning Wizard Battle into a fully playable, player-owned, and verifiable game on Mina.</p><p>Each milestone is designed to deliver usable features, generate meaningful on-chain activity, and provide clear learning signals for the wider ecosystem.</p><p>As development progresses, we’ll continue sharing updates, technical insights, and next steps.</p><p>Thank you for being part of the journey — and stay tuned!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a85123d3b35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/wizard-battle-3-month-roadmap-8a85123d3b35">Wizard Battle 3-Month Roadmap</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZkNoid in 2025]]></title>
            <link>https://medium.com/zknoid/zknoid-in-2025-37970939ef8a?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/37970939ef8a</guid>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Fri, 09 Jan 2026 12:37:20 GMT</pubDate>
            <atom:updated>2026-01-09T12:37:20.046Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckHbvOgpyAAyq8aDqMYNAg.png" /></figure><p>During 2025, ZkNoid made remarkable steps in developing our vision for the future of zkGaming, building and releasing new titles, and growing our community around them.</p><p>In this article, we will go through our 2025 milestones. Let’s jump straight in!</p><h3>Our Vision</h3><p>Online gaming has evolved into one of the most competitive and high-stakes digital environments in the world. Yet as gaming has grown, so has a fundamental flaw in its architecture: privacy has been sacrificed for convenience.</p><p>At ZkNoid, this realization became the starting point for our vision of zkGaming.</p><p>We believe privacy is foundational to fair play! When player strategies, rankings, or loadouts are visible, competition is inherently compromised. Privacy does not hide skill, instead it protects it by ensuring outcomes are determined by gameplay, not leaked information.</p><p>Competitive gaming also suffers from broken trust. Leaderboards, tournaments, and rewards depend on centralized validation, forcing players to trust opaque systems.</p><p>Zero-knowledge technology provides the missing layer. zkProofs enable:</p><ul><li>Proof of victory without exposing tactics</li><li>Proof of eligibility without revealing identity</li><li>Proof of fairness without centralized oversight</li></ul><p>This replaces surveillance with cryptographic verification.</p><p>Our vision is to build games that are fair-by-default, privacy-preserving, and verifiable. Instead of “watching everything,” zkGaming proves only what is necessary.</p><p>zkGaming is already becoming reality. The ecosystem is already seeing:</p><ul><li>zk-based reputation systems</li><li>Privacy-preserving matchmaking</li><li>Verifiable game state transitions</li><li>Trustless, private in-game asset transfers</li></ul><p>At ZkNoid, we are building on these foundations to create the next generation of competitive games.</p><p>We believe that the future of gaming is private and verifiable. That’s the vision we are building towards.</p><h3>Game Development</h3><p>In 2025, the Zknoid team was focused on developing 4 main projects:</p><p>1. <a href="https://app.zknoid.io/games/lottery/global"><strong>Lottery L1</strong></a> was the first zkGame to go mainnet last year. The launch was an astounding success! In the very first round alone, 183 players participated, purchasing a total of 344 Lottery tickets. And after a month of operation, the stats were truly impressive:</p><p>To celebrate the mainnet launch of the L1 Lottery game, we hosted the ZkNoid Lottery Festival from January 27th to February 7th. This two-week extravaganza was packed with special events, competitions, AMA sessions, and a ton of Lottery gift code giveaways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RIYeD60D-v46XQZG2w147A.png" /></figure><p>2. <strong>Meme token festival</strong>. At the beginning of March, we teamed up with <a href="https://minatokens.com/">MinaTokens</a> to launch two meme tokens on Mina: <a href="https://minatokens.com/token/B62qqL3V1g63YonwvghXrERzUANeKWYTDq8KxHxvqb26ZqNDXL1NpJ7">Frozen Frogs</a> and <a href="https://minatokens.com/token/B62qqoMiKci7aA2cUYontX7SmNgquk9QPkya8vSaHHKPxC7Tv51Tf7h">Fire Dragons</a>. This launch was not just about introducing new tokens. It was accompanied by a 2-week festival that allowed players to rally with their team and participate in daily mini quests and competitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7ICAToBFSXLG6lam1yfAw.png" /></figure><p>At the end of the festival, nearly 5 million tokens were in the game and the Fire Dragons emerged victorious!</p><p>3. <a href="https://orbirium.zknoid.io/"><strong>Orbirium</strong></a> was announced in July as a collaboration between ZkNoid, <a href="https://silvana.one/">Silvana</a>, and <a href="https://zeko.io/">ZekoLabs</a>. As a web3 idle crafter running on SUI and Zeko simultaneously, it was able to combine ultra-fast interactions on SUI with provably fair logic by settling on Zeko.</p><p>This layered architecture, developed by the ZkNoid team, proved that web3 players can enjoy speed, reliability, and security all at once — something most blockchain games struggle to balance.</p><p>In November, Orbirium went live on SUI and then shortly joined Zeko at their ZekoBoom Testnet Contest, marking a new phase for the game. With Zeko allocating a special airdrop pool for top Orbirium players, competition intensified, resulting in impressive final stats at the event’s conclusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h9i3bPEot6impyoTNLklYw.png" /></figure><p>4. Finally, last year, we begun development of our largest zkGame so far — <strong>Wizard Battle</strong>. This turn-based PvP strategy game is designed to deliver a web2-like experience within the web3 landscape.</p><p>In Wizard battle, players will immerse themselves in a magical world filled with spellcasting, strategic gameplay, and intense duels. Each player will assume the role of a powerful wizard, equipped with unique abilities and spells that can be customized to suit their playstyle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lXpPu4A5QgTpefMcfTedA.png" /></figure><p>The development phase of Wizard Battle is coming to an end and we plan to release it in testnet in Q1 this year! Stay tuned for more news coming soon!</p><h3>Community Events &amp; Educational Content</h3><p>Throughout 2025, ZkNoid placed a strong emphasis on <strong>transparency, </strong>community growth, and education within the Mina ecosystem.</p><p>We invested in open communication through live AMA sessions that helped us gather feedback, explain decisions, and align our roadmap with the needs of the ecosystem.</p><p>Key community AMAs of 2025:</p><ul><li><a href="https://x.com/i/spaces/1lDxLlngQoZxm">“Countdown to ZkNoid Lottery mainnet”</a> hosted by <a href="https://x.com/MinaProtocol">Mina Protocol</a></li><li><a href="https://x.com/i/spaces/1yNGagLgMllxj">“ZkNoid Lottery updates”</a> with <a href="https://x.com/minacryptocom">ZKOK</a></li><li><a href="https://x.com/i/spaces/1OdKrDEmoWkJX">“NFT gaming on Mina Protocol”</a> by <a href="https://x.com/minacryptocom">ZKOK</a></li><li><a href="https://x.com/i/spaces/1nAJEgVqXeVKL">“INTERZONE ASSOCIATE — MAPC x ZkNoid : Wizard Battle&amp; World-Building”</a> with <a href="https://x.com/MinatyAPC">A.P.C.</a></li><li><a href="https://x.com/i/spaces/1rmxPyzeLVqKN">“ZkNoid Community AMA”</a> with <a href="https://x.com/minacryptocom">ZKOK</a></li><li><a href="https://x.com/i/spaces/1MYxNlbnEOPGw">“The furure of zkGaming”</a> hosted by <a href="https://x.com/ZKVProtocol">ZkVerify</a></li><li><a href="https://x.com/i/spaces/1zqJVdoyggnKB">“Can gaming bring culture to ZK and ZK power to games?”</a> with <a href="https://x.com/zkulture_xyz">ZKulture</a></li></ul><p>Education was another major focus. We published technical and non-technical content aimed at helping both developers and players better understand zero-knowledge technology, zkApps, and web3 gaming.</p><p>Key educational content of 2025:</p><ul><li><a href="https://medium.com/zknoid/mina-action-reducers-guide-batch-reducers-6a818ecbeb2f">Mina Action &amp; Reducers Guide: Batch reducers</a></li><li><a href="https://medium.com/zknoid/how-to-play-the-l1-lottery-game-a86e366f4136">How to Play the L1 Lottery Game</a></li><li><a href="https://medium.com/zknoid/ui-ux-design-design-challenges-in-web3-6cee5ab2f17e">UI/UX Design: design challenges in web3</a></li><li><a href="https://medium.com/zknoid/custom-tokens-on-mina-c605ddd24da9">Custom Tokens on Mina</a></li><li><a href="https://medium.com/zknoid/zknoid-meme-token-contest-the-ultimate-showdown-of-climate-preferences-cd4724947df6">ZkNoid Meme token contest: The Ultimate Showdown of Climate Preferences</a></li><li><a href="https://medium.com/zknoid/tokens-on-mina-minatokens-launchpad-85ed1cf8175a">Tokens on Mina: MinaTokens Launchpad</a></li><li><a href="https://medium.com/zknoid/inside-orbirium-the-three-layer-architecture-behind-the-game-aad287510554">Inside Orbirium: The Three-Layer Architecture Behind the Game</a></li><li><a href="https://medium.com/zknoid/wizard-battle-the-age-of-the-arena-ac1897ddc715">Wizard Battle: The Age of the Arena</a></li><li><a href="https://medium.com/zknoid/wizard-battle-architecture-building-a-provable-rpg-game-536260fa4802">Wizard Battle Architecture: Building a Provable RPG Game</a></li><li><a href="https://medium.com/zknoid/dynamic-proof-management-b0341d1080c0">Dynamic proof management</a></li></ul><h3>Conclusion</h3><p>Looking back on 2025, we’re proud of the progress we’ve made and the milestones we’ve reached together. It was a year of building, shipping, and learning — laying strong foundations for what comes next.</p><p>As we move into 2026, our focus shifts to an ambitious roadmap filled with new events, game launches, and exciting projects currently in development. An updated 2026 roadmap will be shared soon, offering a closer look at what’s ahead.</p><p>We want to extend our sincere thanks to our community, partners, and supporters. Your feedback, participation, and belief in our vision continue to shape everything we build. Empowering users and pushing the boundaries of web3 gaming remains at the core of our mission.</p><p>With a new year underway, we’re excited for the journey ahead and grateful to have you with us. 2026 holds a lot in store and we can’t wait to share what’s coming next!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37970939ef8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/zknoid-in-2025-37970939ef8a">ZkNoid in 2025</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamic proof management]]></title>
            <link>https://medium.com/zknoid/dynamic-proof-management-b0341d1080c0?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0341d1080c0</guid>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <category><![CDATA[zkp]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 13:09:13 GMT</pubDate>
            <atom:updated>2025-12-18T12:57:15.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsNKW_2quFtMPdByaeMSRg.png" /></figure><p>Today we’re diving into another neat part of the Mina toolkit — <strong>dynamic proofs</strong>.</p><p>In the typical zk flow, you generate a proof type, wire it directly into your smart contract, and call verify(). Something like this:</p><pre>@method async myMethod(proof: MyProof) {<br> proof.verify()<br>}</pre><p>The downside is that the proof type is now hard-wired into the contract. You can’t just easily swap it out or accept other proof types without re-deploying or re-writing logic.</p><p>Another problem comes, when you are trying to change proof type, that was hardcoded. By changing proof you are also changing verification key, witch mean you can’t simply swap proofs type on your contract.</p><pre>export class AddOneStaticProofContract extends SmartContract {<br>    @state(Field) state = State &lt; Field &gt; ();<br><br>    init() {<br>        super.init();<br>        this.state.set(Field(1n));<br>    }<br><br>    @method async updateState(proof: AddOneProof) {<br>        proof.verify();<br><br>        proof.publicInput.state.assertEquals(<br>            this.state.getAndRequireEquals(),<br>            &#39;Invalid state&#39;<br>        );<br><br>        this.state.set(proof.publicOutput.state);<br>    }<br>}<br><br>export class DoubleStaticProofContract extends SmartContract {<br>    @state(Field) state = State &lt; Field &gt; ();<br><br>    init() {<br>        super.init();<br>        this.state.set(Field(1n));<br>    }<br><br>    @method async updateState(proof: DoubleProof) {<br>        proof.verify();<br><br>        proof.publicInput.state.assertEquals(<br>            this.state.getAndRequireEquals(),<br>            &#39;Invalid state&#39;<br>        );<br><br>        this.state.set(proof.publicOutput.state);<br>    }<br>}<br><br>// AddOneStaticProofContract verification key hash:<br>// 17890159346071614686578630735112703184082245709514494972254037860557458178111<br>// DoubleStaticProofContract verification key hash:<br>// 734714936652101656545925174125381253807189360953984519596323743813311734778</pre><p>What if you need something more flexible — say, a proof that can change over time, or even better, <strong>an open-ended set of proofs</strong> that your program can accept?</p><p>That’s exactly the challenge ZkNoid ran into while developing <strong>Wizard Battle</strong>. Each spell is its own zk program. During a match, different spells can be cast, and the set of allowed spells needs to evolve dynamically.</p><p>To handle this, we’ve desighed a smart contract that stores a <strong>Merkle tree of verification keys</strong>. We can update this tree however we like (e.g., add or retire spells), and our contract will accept a state update from <strong>any</strong> zk program whose verification key is included in that Merkle set. This gives us a clean way to keep the contract stable while letting the ecosystem of valid proofs evolve.</p><h3>Dynamic proof implementation</h3><p>First, let’s start with a simple template.</p><p>The idea is to keep a <strong>Merkle tree of verification keys</strong> inside the contract so we can add, replace, or retire which proof types are accepted without redeploying the contract logic. We’ll also keep a single state field for whatever your zk program updates.</p><pre>/**<br> * DynamicProof Contract<br> *<br> * This contract maintains a Merkle tree of verification keys.<br> * It has:<br> * - A state field storing the Merkle root of verification keys<br> * - Methods to update the verification key tree<br> */<br><br>// Define the height of the Merkle tree (8 levels = 256 leaves)<br>export const TREE_HEIGHT = 8;<br><br>// Create a MerkleWitness class for this tree height<br>export class VKMerkleWitness extends MerkleWitness(TREE_HEIGHT) {}<br><br>export class DynamicProofExample extends SmartContract {<br>    // State: single field representing the Merkle root of verification keys<br>    @state(Field) vkTreeRoot = State &lt; Field &gt; ();<br><br>    // State of the ZkProgramm as single field<br>    @state(Field) state = State &lt; Field &gt; ();<br><br>    init() {<br>        super.init();<br>        // Initialize with an empty tree root<br>        const emptyTree = new MerkleTree(TREE_HEIGHT);<br>        this.vkTreeRoot.set(emptyTree.getRoot());<br>    }<br><br>    /**<br>     * Update a verification key in the tree at a specific index<br>     * @param index - The index in the tree to update<br>     * @param currentVK - The current verification key at this index<br>     * @param newVK - The new verification key to set<br>     * @param witness - Merkle witness proving the current state<br>     */<br>    @method async updateVerificationKey(<br>        index: Field,<br>        currentVK: VerificationKey,<br>        newVK: VerificationKey,<br>        witness: VKMerkleWitness<br>    ) {<br>        // Get current root from state<br>        const currentRoot = this.vkTreeRoot.getAndRequireEquals();<br><br>        // Verify the witness with current VK matches current root<br>        const calculatedRoot = witness.calculateRoot(currentVK.hash);<br>        calculatedRoot.assertEquals(<br>            currentRoot,<br>            &#39;Invalid merkle witness for current VK&#39;<br>        );<br><br>        // Calculate new root with the new VK<br>        const newRoot = witness.calculateRoot(newVK.hash);<br><br>        // Verify index is within bounds (0 to 2^TREE_HEIGHT - 1)<br>        witness.calculateIndex().assertEquals(index, &#39;Index mismatch with witness&#39;);<br><br>        // Update state with new root<br>        this.vkTreeRoot.set(newRoot);<br>    }<br><br>    /**<br>     * Add a new verification key to the tree<br>     * This is a convenience method that assumes the slot is currently empty (Field(0))<br>     * @param index - The index in the tree to add the VK<br>     * @param newVK - The new verification key to add<br>     * @param witness - Merkle witness for the empty slot<br>     */<br>    @method async addVerificationKey(<br>        index: Field,<br>        newVK: VerificationKey,<br>        witness: VKMerkleWitness<br>    ) {<br>        // Call updateVerificationKey with Field(0) as current VK<br>        await this.updateVerificationKey(<br>            index,<br>            VerificationKey.empty(),<br>            newVK,<br>            witness<br>        );<br>    }<br>}</pre><p><strong>This this gives us</strong></p><ul><li>vkTreeRoot stores the Merkle root of all allowed verification keys.</li><li>updateVerificationKey replaces a key at a specific index, checking a Merkle witness against the current root.</li><li>addVerificationKey is a convenience wrapper for inserting into an empty slot (using VerificationKey.empty())</li></ul><p>Next, we define a <strong>dynamic proof shape</strong> and an updateState method that accepts any proof whose verification key is included in our Merkle set.</p><pre>export class MyPublicInput extends Struct({<br>    state: Field,<br>}) {}<br><br>export class MyPublicOutput extends Struct({<br>    state: Field,<br>}) {}<br><br>export class MyDynamicProof extends DynamicProof &lt;<br>    MyPublicInput,<br>    MyPublicOutput &gt;<br>    {<br>        static publicInputType = MyPublicInput;<br>        static publicOutputType = MyPublicOutput;<br>        // Set to 0/1/2 depending on whether the CHILD verifies other proofs<br>        static maxProofsVerified = 0 as<br>        const;<br>        // Allow all features as &quot;maybe&quot; to be compatible with side-loaded VKs<br>        static featureFlags = FeatureFlags.allMaybe;<br>    }<br><br>...<br><br>@method async updateState(<br>    proof: MyDynamicProof,<br>    vk: VerificationKey,<br>    witness: VKMerkleWitness<br>) {<br>    // Verify the witness with current VK matches current root<br>    const curRoot = witness.calculateRoot(vk.hash);<br>    curRoot.assertEquals(<br>        this.vkTreeRoot.getAndRequireEquals(),<br>        &#39;Invalid merkle witness for current VK&#39;<br>    );<br><br>    // Verify the proof<br>    proof.verify(vk);<br><br>    // Check input state matches expected state<br>    proof.publicInput.state.assertEquals(<br>        this.state.getAndRequireEquals(),<br>        &#39;Invalid state&#39;<br>    );<br><br>    // Update state with new state<br>    this.state.set(proof.publicOutput.state);<br>}<br><br></pre><ul><li>MyDynamicProof declares the public input/output types and sets featureFlags to allMaybe, making it compatible with side-loaded verification keys. maxProofsVerified = 0 means this proof does <strong>not</strong> verify other proofs.</li><li>updateState takes three things:</li></ul><ol><li>the dynamic proof,</li><li>its vk (verification key), and</li><li>a Merkle witness proving the vk is in our allowed set.</li></ol><ul><li>We first check the witness against the stored vkTreeRoot.</li><li>Then we verify the proof with proof.verify(vk).</li><li>We assert that the proof’s <strong>public input</strong> state matches the contract’s current state.</li><li>Finally, we set the contract’s state to proof.publicOutput.state.</li></ul><p>Next, let’s define a small <strong>batch of ZkPrograms</strong>:</p><ul><li><strong>AddOne</strong> — adds 1 to the state</li><li><strong>Double</strong> — multiplies the state by 2</li><li><strong>Square</strong> — squares the state</li></ul><pre>export const AddOne = ZkProgram({<br>    name: &#39;add-one&#39;,<br>    publicInput: MyPublicInput,<br>    publicOutput: MyPublicOutput,<br>    methods: {<br>        doSomething: {<br>            privateInputs: [],<br>            async method(<br>                _inp: MyPublicInput<br>            ): Promise &lt; {<br>                publicOutput: MyPublicOutput<br>            } &gt; {<br>                return {<br>                    publicOutput: new MyPublicOutput({<br>                        state: _inp.state.add(1),<br>                    }),<br>                };<br>            },<br>        },<br>    },<br>});<br><br>export const Double = ZkProgram({<br>    name: &#39;double&#39;,<br>    publicInput: MyPublicInput,<br>    publicOutput: MyPublicOutput,<br>    methods: {<br>        doSomething: {<br>            privateInputs: [],<br>            async method(<br>                _inp: MyPublicInput<br>            ): Promise &lt; {<br>                publicOutput: MyPublicOutput<br>            } &gt; {<br>                return {<br>                    publicOutput: new MyPublicOutput({<br>                        state: _inp.state.mul(2),<br>                    }),<br>                };<br>            },<br>        },<br>    },<br>});<br><br>export const Square = ZkProgram({<br>    name: &#39;square&#39;,<br>    publicInput: MyPublicInput,<br>    publicOutput: MyPublicOutput,<br>    methods: {<br>        doSomething: {<br>            privateInputs: [],<br>            async method(<br>                _inp: MyPublicInput<br>            ): Promise &lt; {<br>                publicOutput: MyPublicOutput<br>            } &gt; {<br>                return {<br>                    publicOutput: new MyPublicOutput({<br>                        state: _inp.state.mul(_inp.state),<br>                    }),<br>                };<br>            },<br>        },<br>    },<br>});</pre><p>Each program shares the same public input/output types, which is exactly what our MyDynamicProof expects.</p><p>That’s it, our program is ready to use. Let’s write a test to show the flow from deployment to updating the verification-key tree.</p><h3>Testing the flow</h3><p>First, we set up accounts, compile the zk programs to get their <strong>verification keys</strong>, and spin up a local Mina instance. We also keep a <strong>local Merkle tree</strong> to mirror what the contract stores on-chain.</p><pre>describe(&#39;DynamicProof&#39;, () =&gt; {<br>            let deployerAccount: Mina.TestPublicKey,<br>                deployerKey: PrivateKey,<br>                senderAccount: Mina.TestPublicKey,<br>                senderKey: PrivateKey,<br>                zkAppAddress: PublicKey,<br>                zkAppPrivateKey: PrivateKey,<br>                zkApp: DynamicProofExample,<br>                localMerkleTree: MerkleTree,<br>                addOneVk: VerificationKey,<br>                doubleVk: VerificationKey,<br>                squareVk: VerificationKey;<br><br>            beforeAll(async () =&gt; {<br>                // Compile all ZkPrograms before running tests<br>                addOneVk = (await AddOne.compile()).verificationKey;<br>                doubleVk = (await Double.compile()).verificationKey;<br>                squareVk = (await Square.compile()).verificationKey;<br>                if (proofsEnabled) await DynamicProofExample.compile();<br>            });<br><br>            beforeEach(async () =&gt; {<br>                const Local = await Mina.LocalBlockchain({<br>                    proofsEnabled<br>                });<br>                Mina.setActiveInstance(Local);<br>                [deployerAccount, senderAccount] = Local.testAccounts;<br>                deployerKey = deployerAccount.key;<br>                senderKey = senderAccount.key;<br><br>                zkAppPrivateKey = PrivateKey.random();<br>                zkAppAddress = zkAppPrivateKey.toPublicKey();<br>                zkApp = new DynamicProofExample(zkAppAddress);<br><br>                // Initialize local merkle tree to track state<br>                localMerkleTree = new MerkleTree(TREE_HEIGHT);<br>            });<br><br>            async function localDeploy() {<br>                const txn = await Mina.transaction(deployerAccount, async () =&gt; {<br>                    AccountUpdate.fundNewAccount(deployerAccount);<br>                    await zkApp.deploy();<br>                });<br>                await txn.prove();<br>                await txn.sign([deployerKey, zkAppPrivateKey]).send();<br>            }<br>}</pre><p>Next lets add AddOne and Double verification keys</p><pre>console.log(&#39;Add addOne vk to merkle tree&#39;);<br>let addOneWitness = new VKMerkleWitness(localMerkleTree.getWitness(0n));<br><br>localMerkleTree.setLeaf(0n, addOneVk.hash);<br>// Add AddOne VK transaction<br>const tx1 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.addVerificationKey(addOneVk, addOneWitness);<br>});<br>await tx1.prove();<br>await tx1.sign([senderKey]).send();<br><br>console.log(&#39;Add double vk to merkle tree&#39;);<br>let doubleWitness = new VKMerkleWitness(localMerkleTree.getWitness(1n));<br>localMerkleTree.setLeaf(1n, doubleVk.hash);<br>// Add Double VK transaction<br>const tx2 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.addVerificationKey(doubleVk, doubleWitness);<br>});<br>await tx2.prove();<br>await tx2.sign([senderKey]).send();</pre><p>Now we add the AddOne and Double verification keys to the Merkle tree.</p><pre>console.log(&#39;Update state with AddOne proof&#39;);<br>let addOneProof = await AddOne.addOne(<br>    new MyPublicInput({<br>        state: Field(1n)<br>    })<br>);<br>let addOneDynamic = MyDynamicProof.fromProof(addOneProof.proof);<br><br>let freshAddOneWitness = new VKMerkleWitness(<br>    localMerkleTree.getWitness(0n)<br>);<br><br>let tx3 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.updateState(addOneDynamic, addOneVk, freshAddOneWitness);<br>});<br>await tx3.prove();<br>await tx3.sign([senderKey]).send();<br><br>expect(zkApp.state.get().toBigInt()).toEqual(2n);<br><br>console.log(&#39;Update state with Double proof&#39;);<br>let doubleProof = await Double.double(<br>    new MyPublicInput({<br>        state: Field(2n)<br>    })<br>);<br>let doubleDynamic = MyDynamicProof.fromProof(doubleProof.proof);<br><br>let freshDoubleWitness = new VKMerkleWitness(<br>    localMerkleTree.getWitness(1n)<br>);<br><br>let tx4 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.updateState(doubleDynamic, doubleVk, freshDoubleWitness);<br>});<br>await tx4.prove();<br>await tx4.sign([senderKey]).send();<br><br>expect(zkApp.state.get().toBigInt()).toEqual(4n);</pre><p>We compute a Merkle <strong>witness</strong> for each slot, mirror the update in our <strong>local</strong> tree, and submit a transaction that calls addVerificationKey(...) on the contract.</p><p>Now let’s prove the gate actually works.</p><p>First, we try to update the contract with a <strong>Square</strong> proof <strong>before</strong> its verification key is added to the Merkle tree. That transaction should fail. However, when we later add squareVk to the tree, the same update should succeed.</p><pre>console.log(<br>    &#39;Try to update state with Square proof that was never added to the merkle tree&#39;<br>);<br>let squareProof = await Square.square(<br>    new MyPublicInput({<br>        state: Field(4n)<br>    })<br>);<br>let squareDynamic = MyDynamicProof.fromProof(squareProof.proof);<br><br>let squareWitness = new VKMerkleWitness(localMerkleTree.getWitness(2n));<br><br>// This should fail because squareVk was never added to the merkle tree<br>await expect(<br>    Mina.transaction(senderAccount, async () =&gt; {<br>        await zkApp.updateState(squareDynamic, squareVk, squareWitness);<br>    })<br>).rejects.toThrow();<br><br>// State should remain unchanged at 4 since the transaction failed<br>expect(zkApp.state.get().toBigInt()).toEqual(4n);</pre><p>Now, when we insert <strong>squareVk</strong> into the on-chain VK set, recompute a fresh witness, and re-run the update, the transaction shoud pass.</p><pre>// Add squareVk to the merkle tree<br>console.log(&#39;Add square vk to merkle tree&#39;);<br>localMerkleTree.setLeaf(2n, squareVk.hash);<br>// Add squareVK transaction<br>const tx6 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.addVerificationKey(squareVk, squareWitness);<br>});<br>await tx6.prove();<br>await tx6.sign([senderKey]).send();<br><br>console.log(&#39;Update state with Square proof&#39;);<br>let freshSquareWitness = new VKMerkleWitness(<br>    localMerkleTree.getWitness(2n)<br>);<br><br>let tx7 = await Mina.transaction(senderAccount, async () =&gt; {<br>    await zkApp.updateState(squareDynamic, squareVk, freshSquareWitness);<br>});<br>await tx7.prove();<br>await tx7.sign([senderKey]).send();<br><br>expect(zkApp.state.get().toBigInt()).toEqual(16n);</pre><h3>Summary</h3><p>In this article, we walked through <strong>dynamic proofs</strong> in Mina which allow your contract to accept proofs from multiple zk programs without hard-wiring a single proof type into your contract.</p><p>We built a smart contract that stores a <strong>Merkle tree of verification keys</strong>, so you can add, replace, or retire which programs are allowed over time.</p><p>Then we implemented three simple zk programs: <strong>AddOne</strong>, <strong>Double</strong>, and <strong>Square</strong> which share the same public input/output types, making them compatible with a DynamicProof.</p><p>Finally, we tested the full flow: compiling programs to get their verification keys, inserting keys into the Merkle tree, and verifying that updates fail when a key isn’t included and succeed once it is. The result is a clean, modular pattern for evolving your zkApp safely, perfect for cases like feature flags, plug-in logic, or game “spells” that come and go.</p><p>Hope this was useful, see you next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0341d1080c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/dynamic-proof-management-b0341d1080c0">Dynamic proof management</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly Recap: November 2025]]></title>
            <link>https://medium.com/zknoid/monthly-recap-november-2025-cb269ef188c9?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb269ef188c9</guid>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 14:43:33 GMT</pubDate>
            <atom:updated>2025-12-04T14:43:33.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4YIj1pxSznEE8ZuxuH9lA.png" /></figure><p>November was a milestone-packed month for ZkNoid! With major feature implementations, contract optimizations, UI upgrades, and the successful launch of Orbirium, this has been one of our most productive months yet.</p><p>Here’s a breakdown of everything that happened, and what’s coming next.</p><h3>Orbirium Launch</h3><p>The highlight of the month was the launch of <a href="https://orbirium.zknoid.io/">Orbirium</a>, our web3 idle crafter built in collaboration with <a href="https://silvana.one/">Silvana</a> and <a href="https://zeko.io/">ZekoLabs</a>.</p><p>The first 2 weeks saw a massive influx of players. Look at these stats!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IMXNnUNE8hxlzQvlbn4Pg.png" /></figure><p>All this amounts to almost 850,000 TXs on SUI!</p><p>Following launch, the team shifted into rapid-iteration mode: fixing bugs, smoothing the experience, improving backend performance, and polishing the UI based on early player feedback.</p><h3>ZkNoid at ZekoBoom</h3><p>After the first 2 weeks after launch, Orbirium officially entered the ZekoBoom Testnet Contest, marking a new phase for the game.</p><p>With Zeko allocating a special airdrop pool for top Orbirium players, competition intensifies. A dedicated leaderboard tracks every Black Orb crafted, and at the end of the event rewards will be distributed based on player rankings.</p><h4><strong>How to score points</strong></h4><ol><li>Play the game → <a href="https://orbirium.zknoid.io/">https://orbirium.zknoid.io/</a></li><li>Login using your Mina, EVM wallets, or socials</li><li>Progress through the resource tree</li><li>Craft Black Orbs</li><li>Rise up the leaderboard to increase your chance for rewards</li></ol><p>Follow <a href="https://x.com/ZkNoid">ZkNoid</a> and <a href="https://x.com/ZekoProtocol">Zeko</a> for all updates and more game stats!</p><h3>Development Updates</h3><h4>Orbirium</h4><p><strong>Contracts &amp; Backend</strong></p><ul><li>Transaction batching implemented reducing overhead and improving on-chain performance.</li><li>Optimized contract gas usage, lowering the cost of high-frequency actions.</li><li>Server-side signature validation for clicks added to enhance security and prevent misuse.</li></ul><p><strong>UI &amp; UX Enhancements</strong></p><ul><li>New login UI, including a dedicated event login page.</li><li>Notification mute toggle added.</li><li>Energy system UI improved with clearer tracking and visibility.</li></ul><p><strong>Analytics</strong></p><ul><li>PostHog analytics integrated, enabling better insights into player behavior.</li><li>Zeko Event authorization keys implemented.</li><li>Extensive testnet preparation &amp; polishing ahead of broader deployment.</li></ul><p><strong>Fixes &amp; Polishing</strong></p><ul><li>Various minor game fixes improving stability.</li><li>Live game issues resolved post-launch.</li><li>Fixed panning &amp; UI quirks on mobile devices.</li></ul><h4>Wizard Battle</h4><p><strong>Smart Contracts</strong></p><p>New infrastructure for the next evolution of Wizard Battle is now in place:</p><ul><li>Vault contracts and base game contracts.</li><li>Game item registry contract.</li><li>Game items contracts.</li><li>Resource contracts.</li><li>Character contracts.</li></ul><p>These systems will support crafting, progression, inventory, and combat mechanics.</p><p><strong>Gameplay Enhancements</strong></p><ul><li>Hitmarks added for clearer combat feedback.</li><li>Engine improvements resulting in better performance.</li><li>New animation features.</li></ul><p><strong>UI &amp; Experience</strong></p><ul><li>Inventory UI implemented.</li><li>Tips UI to help guide new players.</li><li>Crafting pages added for upcoming resource and item systems.</li><li>Desktop-style loading screens for a more polished start-up experience.</li></ul><h3>Looking Ahead</h3><p>With Orbirium live at ZekoBoom, the next month will focus on:</p><ul><li>Continued support for Orbirium during the contest.</li><li>Continuing developing Wizard Battle and finalizing systems for the alpha launch.</li><li>Preparing documentation for our vision of Orbirium V2!</li></ul><p>Exciting things are on the horizon. We’re just getting started!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb269ef188c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/monthly-recap-november-2025-cb269ef188c9">Monthly Recap: November 2025</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orbirium Launches November 18th on SUI & Zeko]]></title>
            <link>https://medium.com/zknoid/orbirium-launches-november-18th-on-sui-zeko-a625037e9fef?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a625037e9fef</guid>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[airdrop]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[zeko]]></category>
            <category><![CDATA[zknoid]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 13:14:30 GMT</pubDate>
            <atom:updated>2025-11-14T14:05:02.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewPbZlCC0PZW9-TJOW9-XQ.png" /></figure><p>Orbirium, a zk-powered idle crafter built by <a href="https://medium.com/www.zknoid.io/">ZkNoid</a> in collaboration with <a href="https://silvana.one/">Silvana</a> and <a href="https://zeko.io/">ZekoLabs</a> is launching next week as a featured side event in the Zeko Boom Contest.</p><blockquote>Starting Tuesday, November 18th, players will dive into the world of Orbirium!</blockquote><h3>What Is Orbirium?</h3><p>Orbirium challenges players to optimize production chains and automate resource flows to forge as many Black Orbs as possible. They’re the key to climbing the leaderboard and earning Zeko rewards!</p><p>But Orbirium isn’t just another idle crafter. Every action — collecting, upgrading, and crafting is processed on <a href="https://sui.io/">SUI</a> and settled on Zeko, combining the strengths of both networks:</p><ul><li>Ultra-fast, low-latency interactions powered by SUI</li><li>Provably fair, tamper-proof game state secured by Zeko</li></ul><h3>Gameplay</h3><p>At its core, Orbirium is a strategic idle crafter built around resource optimization and automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWUKt8khBCFGTJA7IK5U7A.jpeg" /></figure><p>Players begin with just one basic resource: wood. From there, the crafting tree gradually expands, revealing new materials, upgrades, recipes, and eventually high-tier components needed to craft Black Orbs.</p><p>Each resource has 3 possible upgrades:</p><ul><li>Click Power. Increases the amount of resources gathered with each manual click.</li><li>Auto mining. Grants an increasing passive stream of resources.</li><li>Storage. Increases the auto mining storage size.</li></ul><blockquote><em>Each upgrade point scales efficience linearly. Each 10th upgrade doubles the total </em>coefficient<em>!</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*-HT622AaydtQMcTWvXAHhQ.png" /></figure><p>To ensure the game stays fair for players with different schedules, Orbirium introduces a daily Energy system. Each action consumes Energy which resets daily. This means success is determined by smart decisions and optimized production.</p><p>Each decision matters:</p><ul><li>Invest resources into upgrades that accelerate production.</li><li>Balance between short-term gains and long-term efficiency.</li><li>Automate chains to maximize Black Orb output even while you’re offline.</li></ul><p>The ultimate goal? Crafting Black Orbs — rare, high-tier artifacts that represent mastery over all resource flows.</p><h3>Zk+SUI Synergy Architecture</h3><p>Orbirium’s technical foundation blends performance with cryptographic security. Its three-tier system is designed for real-time gameplay with verifiable outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ed5SPFIR_kD7N27oHDaA_A.png" /></figure><h4>1. Application Layer (Client)</h4><p>The gameplay interface operates directly in the browser or app client. It manages the crafting UX, automation logic, and user interactions, ensuring a responsive and intuitive experience.</p><h4>2. SUI Layer (Execution)</h4><p>SUI handles fast in-game transactions such as crafting actions, upgrades, and resource movements.</p><p>Its low-latency architecture makes it ideal for rapid, incremental idle-game mechanics.</p><h4>3. Zeko Layer (Settlement)</h4><p>Periodically, SUI game state is verified and settled on Zeko using zero-knowledge proofs.</p><p>This provides:</p><ul><li>Immutable proof of player progress</li><li>Prevention of stat manipulation</li><li>Transparent, fair leaderboard outcomes</li></ul><p>This hybrid approach allows Orbirium to combine SUI’s speed with Zeko’s zero-knowledge security, pioneering a new model of zk-integrated gaming.</p><p>Dive deeper into the three-layered architecture <a href="https://medium.com/zknoid/inside-orbirium-the-three-layer-architecture-behind-the-game-aad287510554">here</a>.</p><h3>How to Earn Black Orbs</h3><p>There are two ways to earn Black Orbs:</p><h4>1. Unlock New Resources</h4><ul><li>Every new resource you discover in the crafting tree rewards you with Black Orbs.</li><li>Higher-tier resources yield more.Up to 38 Black Orbs can be earned just by completing the tree.</li></ul><h4>2. Craft Black Orbs Directly</h4><ul><li>Once the entire crafting tree is unlocked, you can focus on producing Black Orbs themselves.</li><li>Master and automate your resource flow to maximize production and dominate the leaderboard.</li></ul><p>Stay tuned — the forge opens November 18th!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a625037e9fef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/orbirium-launches-november-18th-on-sui-zeko-a625037e9fef">Orbirium Launches November 18th on SUI &amp; Zeko</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wizard Battle Architecture: Building a Provable RPG Game]]></title>
            <link>https://medium.com/zknoid/wizard-battle-architecture-building-a-provable-rpg-game-536260fa4802?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/536260fa4802</guid>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <category><![CDATA[blockchain-game]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 12:41:42 GMT</pubDate>
            <atom:updated>2025-11-07T12:41:42.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZgB6Wdd3aus-32zIe98MXQ.png" /></figure><p>Wizard Battle is a web3 strategy game where players engage in PvP and PvE duels to reclaim lost knowledge of this magic world. It combines tactical combat, crafting, and character progression within a provably fair, on-chain environment.</p><p>In this article, we’ll explain how the game works under the hood: real-time duels, state synchronization, item crafting, economic systems, and zero-knowledge verification.</p><p>We’ll start by exploring the Battle Architecture — how players interact, move, and cast spells in a trust-minimized environment.</p><p>Next, we’ll look at the Non-Battle Architecture — crafting, trading, and on-chain item management.</p><p>Finally, we’ll dive into the technical framework and long-term vision, describing how Wizard Battle is built to evolve into a fully decentralized, provable, and fun multiplayer experience.</p><h3>How it’s made</h3><p>The game’s architecture is built around two main layers:</p><ul><li><strong>Battle architecture</strong> — where players interact, move, and cast spells.</li><li><strong>Non-battle architecture</strong> — where items, crafting, and the in-game economy live on-chain.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73k6HnGhZCCR59R7JbVH7g.png" /></figure><p>While the current implementation still uses some centralized components, the entire system is designed for future decentralization and full zero-knowledge validation.</p><h3>Battle Architecture</h3><p>At the core of Wizard Battle lies an optimistic approach: during the match, we trust players’ local states. Each player keeps their entire game state on their device and only shares partial information (the public state) depending on gameplay visibility rules.</p><p>For example, a wizard is always invisible, meaning their position doesn’t appear in the public state. This model preserves both privacy and integrity, enabling mechanics that would be impossible in traditional transparent blockchain games.</p><h4>Player State</h4><p>A player’s state includes:</p><ul><li>Selected wizard</li><li>Chosen skills and their cooldowns</li><li>The map</li><li>Current position</li><li>Character attributes (HP, max HP, strength, agility, etc.)</li></ul><p>The public portion of this state is automatically derived from game logic and visibility rules. Everything else remains private and verifiable only through post-match checks.</p><h4>Turn Sequence</h4><p>Each turn follows this universal sequence:</p><ol><li>Players apply local spells (which don’t require network sync).</li><li>They send their actions to the server.</li><li>The server broadcasts all actions to every player.</li><li>Each client applies those actions locally.</li><li>Players send their updated public state back.</li><li>The server shares all new public states among players.</li><li>Clients synchronize and prepare for the next turn.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/359/1*3p5HWSy4aF-z3e0eqxNX0w.png" /></figure><p>All players perform actions at the same time, ensuring fairness while keeping deterministic logic.</p><h4>Timeout Manager</h4><p>To prevent deadlocks, we introduced a <strong>Timeout Manager</strong>. It acts as a central authority that gives every player <strong>2 minutes </strong>to submit their turn.</p><p>If a player fails to respond in time, the Timeout Manager ends the match and marks that player as the loser. This system prevents griefing and ensures that matches never stall indefinitely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TkhU3Gt1YzPB6UpQmmIKw.png" /></figure><h4>State Commit and Verification</h4><p>Every turn, players submit a <strong>state commit</strong> — a cryptographic hash of their entire game state (public and private) signed with their session key. These commits become proof checkpoints used for post-match validation.</p><p>Because the full state remains private during gameplay, WB relies entirely on <strong>post-match verification</strong>. Only after the game ends can players reveal their data and confirm that all actions were valid and rule-compliant.</p><h4>Session Keys</h4><p>Each match uses a locally generated session key, signed by the player’s main wallet once at the start. These keys are stored and used locally throughout the match, eliminating the need to sign every action on-chain and keeping gameplay fluid while maintaining cryptographic authenticity.</p><h4>Randomness and Fairness</h4><p>Some spells rely on pseudorandom behavior. For these, we use a <strong>hash-chain–based random</strong> source: the server generates a chain of hashes and reveals them in reverse order, one per turn.</p><p>This approach makes outcomes both unpredictable and provable after the game.</p><p>For now, we don’t plan to replace this system since it’s deterministic, lightweight, and easy to verify.</p><h4>Number of Players and Scalability</h4><p>While Wizard Battle currently focuses on <strong>1v1</strong> battles, the architecture scales naturally to <strong>NxM matches</strong> or even <strong>PvE</strong> modes. Each player essentially operates on their own board, without collisions or shared line-of-sight, which makes simultaneous turns trivial to extend to multiple participants.</p><h4>Game Completion and Verification Paths</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qi_t5RW9X7tJ7YokHvUpQ.png" /></figure><p>At the end of a match, players can finalize results through two possible verification modes:</p><p><strong>1. Optimistic Path</strong></p><p>For most players, performance and UX come first.</p><p>The optimistic path lets players submit all their actions to the server, which checks validity and finalizes the match. If fraud is detected, a single invalid transition is enough to prove cheating.</p><p><strong>2. ZK Path</strong></p><p>Advanced players can choose the zero-knowledge path, using <a href="https://www.o1labs.org/o1js">o1js</a> to generate recursive proofs verifying that all turns followed the game’s rules without revealing any private data.</p><p>We’d love to make the ZK path the default, but proof generation is still too heavy for many players, so we currently let users toggle between both modes manually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKEIro83r_07sMjz9B1BAA.png" /></figure><h4>Deposits and Slashing</h4><p>Before a match begins, each player deposits a small amount (e.g., 1 MINA) into a smart contract.</p><p>This deposit partly covers transaction fees and acts as a stake for honest behavior. If no fraud is found, players keep their deposit. If cheating is detected through either verification pathб the entire deposit is slashed. This system enforces fairness through economic incentives.</p><h4>Post-Match Disputes and Replays</h4><p>After the game, players enter a <strong>dispute window</strong> (initially one day, later one hour or less) during which they can reveal all submitted states and actions.</p><p>Any other player can verify the integrity of those actions or challenge suspicious data. A full <strong>replay system</strong> will also be introduced, allowing anyone to re-simulate a match from the disclosed actions and seeds which can be useful for tournaments, audits, or community-driven anti-cheat checks.</p><h4>Data Storage and Availability</h4><p>In the first version, all game data (actions, commits, and results) will be stored on our game server.</p><p>Later, we plan to introduce a <strong>data availability layer</strong>, where match proofs and commits could be stored in decentralized storage such as <a href="https://ipfs.tech/">IPFS</a> or <a href="https://arweave.org/">Arweave</a>, with only essential hashes anchored on-chain.</p><h3>Non-Battle Architecture</h3><p>Outside of combat, Wizard Battle runs on EVM-compatible smart contracts that handle crafting, trading, and item management.</p><h4>Items and Crafting</h4><p>All items and resources follow the <a href="https://ethereum.org/ru/developers/docs/standards/tokens/erc-1155/"><strong>ERC-1155</strong></a> standard.</p><p>There are two main types:</p><ul><li><strong>Crafting resources</strong> — used purely for crafting or trading.</li><li><strong>Wearable items</strong> — equipment that can be attached to a character to enhance stats such as HP, damage, or agility.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvUR6_RuZ82K40MezO-oVg.png" /></figure><p>In the current version, a centralized server fetches on-chain data, signs it, and provides verified item information to the battle client. This bridge ensures that items remain authentic while keeping battles fast and seamless.</p><h4>Framework and Technology</h4><p>Wizard Battle is built on <a href="https://www.o1labs.org/o1js">o1js</a>, chosen for its convenience and support for recursive proofs, which allows chaining multiple turns into a single compact proof.</p><p>Proof generation times and hardware benchmarks are still being measured, and future updates will include optimizations to improve the player-side experience.</p><h3>Our Long-Term Vision</h3><p>Wizard Battle aims to become both a fun, competitive game and a reference architecture for future zk-powered multiplayer experiences.</p><p>Our long-term goals are to:</p><ol><li>Deliver genuinely engaging, skill-based gameplay.</li><li>Build a player-owned, decentralized in-game economy.</li><li>Develop a reusable <strong>ZK multiplayer framework</strong> for other developers.</li></ol><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=536260fa4802" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/wizard-battle-architecture-building-a-provable-rpg-game-536260fa4802">Wizard Battle Architecture: Building a Provable RPG Game</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly Recap: October 2025]]></title>
            <link>https://medium.com/zknoid/monthly-recap-october-2025-7873330cb49f?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7873330cb49f</guid>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <category><![CDATA[zkapps]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 13:47:59 GMT</pubDate>
            <atom:updated>2025-11-04T13:47:59.928Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6vCMVS4bqHsw3o0nNdqRw.png" /></figure><p>October was a month of breakthroughs, polish, and player engagement across the ZkNoid ecosystem.</p><p>From deeper core mechanics in Wizard Battle to a packed Poker Night and new developer resources, the team continued building into the future of zkGaming.</p><p>Let’s dive into this month’s highlights:</p><h3>Wizard Battle Development</h3><p>October’s work focused on bringing combat and progression systems closer to their final form enhancing the game both visually and mechanically.</p><h4><strong>Core Gameplay</strong></h4><ul><li>Implemented movement &amp; spell mechanics, including different movement speeds for the Arcane Sorcerer and Shadow Archer.</li><li>Added cooldown systems to balance abilities and create more tactical depth.</li><li>Fully implemented the Shadow Archer hero complete with attacks, skills, and animations.</li><li>Inventory and Hero Gear pages have been implemented</li></ul><h4><strong>Backend &amp; Contracts</strong></h4><ul><li>The matchmaking system received major improvements for speed and accuracy.</li><li>Optimized performance across backend systems.</li><li>Started development on EVM smart contracts.</li><li>Performed a round of minor gameplay fixes for stability.</li></ul><h4><strong>Design &amp; UX</strong></h4><ul><li>Complete redesigns for the main page and game interface for a more intuitive and immersive player experience.</li><li>Introduced a full inventory system and UI, connecting crafted items and gear with player stats.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oF_y7cRUXt7WCHt5nxEV4g.png" /></figure><ul><li>Enhanced asset visuals, improving overall polish and consistency.</li><li>Revamped map generation process, introducing new tiles for diverse terrain layouts.</li><li>Added tooltips and hitmarks to improve combat clarity and responsiveness.</li><li>Enhanced turn UX, adding visualizations for available actions</li></ul><h4><strong>Art &amp; Sound</strong></h4><ul><li>Archer animations finalized for all abilities and attacks.</li><li>Added sound design for core interactions, attacks, and ambient effects.</li><li>Designed the Gear Crafting UI, for the upcoming expansion of item and progression systems.</li></ul><h3>Documentation &amp; Ecosystem</h3><p>This month also brought major progress to ZkNoid’s public documentation.</p><p>Developers can now explore updated pages detailing ZkNoid’s architecture, games, and guides.</p><blockquote>Read the updated docs here: <a href="http://docs.zknoid.io/"><em>docs.zknoid.io</em></a></blockquote><h3>Community Highlights</h3><p>October wasn’t all work, the ZkNoid community also gathered for some fun!</p><ul><li><strong>Poker Night II</strong> drew over 500 participants, all competing for a $100 prize pool. The event once again showed the community’s enthusiasm for ZkNoid’s blend of gaming and web3 social experiences.</li><li>The team also held a meetup with o1js co-CEO <a href="https://x.com/deepthiskumar8"><strong>Deepthi</strong></a>, breefing her on our development status and roadmap, and hearing valuable feedback and news of the Mina developer ecosystem.</li></ul><h3>Looking Ahead</h3><p>With the new mechanics and systems in place, Wizard Battle is heading toward its next big phase:</p><ul><li>Contract integration for verifiable ownership and crafting</li><li>Loot drops &amp; NPC market development</li><li>Playtests and closed beta preparations</li></ul><p>Meanwhile, our second project — Orbirium is getting ready to go live next month.</p><p>Stay tuned to ZkNoid to be among the first to play!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7873330cb49f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/monthly-recap-october-2025-7873330cb49f">Monthly Recap: October 2025</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly Recap: September 2025]]></title>
            <link>https://medium.com/zknoid/monthly-recap-september-2025-b17640a018c1?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b17640a018c1</guid>
            <category><![CDATA[mina-protocol]]></category>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[report]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Tue, 07 Oct 2025 12:55:02 GMT</pubDate>
            <atom:updated>2025-10-07T12:55:02.583Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d3XNRl8JIfuZeje5y_9Y9A.png" /></figure><p>As summer turns to fall, the ZkNoid team continues to push forward refining gameplay, strengthening systems, and preparing for next Wizard Battle milestones.</p><p>Last month’s focus was on:</p><ul><li>Engine improvements</li><li>Implementing core gameplay logic</li><li>New mechanics and gameplay features</li></ul><p>Let’s dive into what the team accomplished in September:</p><h3>Wizard Battle Progress</h3><p>September was a month of major technical and gameplay milestones for Wizard Battle.</p><p>The team focused on refining how the game feels — movement, combat, and synchronization of all received key upgrades to make the experience smoother and more immersive.</p><h4>Core Gameplay &amp; Systems</h4><ul><li>New movement mechanics were fully integrated.</li><li>A death handling system now manages eliminations and round transitions.</li><li>State serialization &amp; de-serialization ensures accurate data transfer across sessions.</li><li>Matchmaking issues that previously blocked some players from joining matches have been resolved.</li><li>The Timeout Manager system now controls phase transitions and automatically calculates victory or defeat based on battle outcomes.</li><li>PvE bot logic was upgraded to allow two-step decision-making.</li><li>A battle arena collector system now clears abandoned arenas and optimizes performance in ongoing matches.</li></ul><p>These upgrades ensure every match runs reliably and efficiently which is vital for both the upcoming test phases and full-scale release.</p><h4>Game Engine</h4><p>A massive leap forward was made on the core engine. The new ZkNoid game engine is custom built to include all new game modes coming to Wizard Battle.</p><p>Key improvements include:</p><ul><li>A more robust animation system, enhancing the visual flow of attacks and skills.</li><li>Performance upgrades to ensure smooth rendering and frame stability.</li><li>State handling optimizations that make the game more scalable.</li><li>A modernized engine UI framework for faster iteration and future updates.</li></ul><p>Together, these backend and visual changes give Wizard Battle a solid technical foundation ready for upcoming large-scale testing.</p><h4>UI &amp; Design</h4><p>The visual side of Wizard Battle took a big leap this month, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVzeVQjZk--gUVVOTAgfPg.png" /></figure><ul><li>The main game map was completed, tying together the various in-game locations.</li><li>A new main page UI was introduced.</li><li>The in-battle game page was refined.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*9ce2q7cuPQDyvylyWK-Cxg.png" /></figure><ul><li>Items and resources required for upgrades crafting were designed.</li></ul><h4>Game Design</h4><p>The gameplay loop of Wizard Battle continues to deepen. This month, the team finalized several major systems:</p><ul><li><strong>Leveling &amp; Gear</strong> will be the backbone of our progression system</li><li><strong>Crafting &amp; Loot</strong> systems that facilitate smooth and balanced progression.</li><li><strong>Expeditions</strong> — an exploration mode that will allow players to venture beyond the Arena in search of rare materials for crafting.</li></ul><h3>Community</h3><p>Outside of development, we continued to strengthen ties within the ZK community.</p><p>On October 2nd, ZkNoid hosted its first <a href="https://x.com/ZkNoid/status/1973729851732341089"><strong>Poker Night</strong></a>, which drew in over 250 players competing for glory and a share of $150 in prizes. The event was a huge success, bringing together players and ZK enthusiasts in a relaxed yet competitive atmosphere.</p><p>We also joined the “<a href="https://x.com/i/spaces/1zqJVdoyggnKB">Can Gaming Bring Culture to ZK and ZK Power to Games</a>” AMA hosted by <a href="https://x.com/zkulture_xyz">ZKulture</a>. By discussing the philosophy of ZK in gaming, fair play, and how zero-knowledge tech is reshaping how games are built we were able to spread our belief that ZK is not just a technology — it’s a culture of privacy, transparency, and fairness!</p><h3>Looking Ahead</h3><p>October is set to bring major visible progress to Wizard Battle.</p><p>The team is focusing on implementing items and loot drops, refining the main game page, and completing both the character and inventory pages. On the creative side, new animations for the Archer and enhanced sound design will bring the battlefield to life.</p><p>Meanwhile, work continues on the crafting system, including pages and illustrations for Orbs, Gems, and Armor as well as balancing the NPC Market<strong> </strong>to ensure fair item pricing and progression. Together, these updates will push Wizard Battle closer to its next major milestone: the first playable test of the full game loop.</p><p>Meanwhile, Orbirium is inching closer to launch with testing on Zeko integration underway.</p><p>The foundation is stronger than ever, and the months ahead promise to be transformative for both games in the ZkNoid ecosystem.</p><p>Stay tuned — the magic is only getting started.</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b17640a018c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/monthly-recap-september-2025-b17640a018c1">Monthly Recap: September 2025</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly Recap: August 2025]]></title>
            <link>https://medium.com/zknoid/monthly-recap-august-2025-3080440eb0e5?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3080440eb0e5</guid>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[sui]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[blockchain-gaming]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Fri, 05 Sep 2025 12:14:38 GMT</pubDate>
            <atom:updated>2025-09-05T12:47:46.368Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQThNY5Fy_JrRjrVlzxcRA.png" /></figure><p>This month was a major leap forward for Wizard Battle, as we moved closer to turning our vision into a fully complete strategy experience. At the same time, Orbirium saw balancing improvements, feature upgrades, and we are now standing just one step away from launch.</p><p>Here’s a breakdown of this month’s achievements:</p><h3>Wizard Battle Progress</h3><p>On the development side, we’ve been focused on making the game feel alive and responsive.</p><p>A new dynamic tilemap system now powers map creation, while matchmaking and game sessions were successfully integrated to ensure smooth multiplayer flow.</p><p>We also rolled out a new tilemap editor for level creation, added save slots to allow persistence across different play sessions, and introduced a profile system along with an XP progression system to make each battle more meaningful.</p><p>Authentication has also taken a big step forward with the integration of Mina AppKit, enabling smooth sign-in experiences tied directly to the game’s ecosystem.</p><p>We also introduced skill logic for the Arcane Sorcerer hero, opening the door for more complex skill interactions, and continued refining the codebase with bug fixes, refactoring, and improvements to session handling.</p><p>Finally, we resolved multiple issues with in-game windows, ensuring a cleaner and more stable user experience.</p><h4>Backend</h4><p>Behind the scenes, the backend evolved significantly. Matchmaking logic and game sessions are now supported at the server level, with a simple bot already in place to help us test and balance gameplay.</p><p>Our CI/CD pipeline became more robust, and deployment pipelines were streamlined with better server setups and direct integration between Vercel and the game server.</p><h4>Game design &amp; UX</h4><p>On the design front, Wizard Battle started to shine visually. Animations for the first character was completed. The main game page was redesigned, and we began work on key interfaces such as character and inventory pages.</p><p>This visual overhaul ties directly into our new progression system that includes armor, orb crafting, NPC markets, and expeditions.</p><p>The game design and documentation side also matured, with the concept for crafting items like Orbs, Gems, and Armor being created. Initial designs for Expeditions and the NPC Market have been finalized, giving us a clearer blueprint of how Wizard Battle’s economy and progression loops will feel.</p><h4>Wizard Battle Roadmap</h4><p>With the foundation now in place, here’s what lies ahead:</p><ul><li><strong>September</strong> — Proving, rating-based matchmaking, smarter PvE bots, and the first full pass at crafting mechanics.</li><li><strong>October</strong> — Item implementation, random loot drops, redesigned main game page, and making the game’s smart contract base.</li><li><strong>November</strong> — Testnet preparation, community testing, balancing feedback, and iteration.</li><li><strong>December </strong>— Contract refinement and expedition &amp; market mechanics.</li><li><strong>Q1 2026</strong> — Mainnet launch</li></ul><h3>Orbirium Updates</h3><p>While Wizard Battle has been in the spotlight, Orbirium hasn’t been standing still. We introduced balancing changes that make crafting and resource progression more engaging.</p><p>On the features side, Orbirium got sonner-like toasts for cleaner notifications, music and music controls for a richer atmosphere, advanced image caching for smoother performance, and auto-clicker protection with captcha to ensure fairness in gameplay.</p><p>What’s left is the Silvana integration, which will handle transferring the game state from Sui to Zeko. Once that’s complete, Orbirium will finally be ready to go live at Zeko Boom!</p><h3>Community &amp; Ecosystem</h3><p>August was also a big month for community and ecosystem engagement.</p><p>Beyond development, we shared our vision with the broader ecosystem — joining a <a href="https://x.com/ZkNoid/status/1961383364050428337">zkVerify AMA</a> to discuss ZK’s role in gaming.</p><p>We also published 2 articles:</p><ul><li><a href="https://medium.com/zknoid/wizard-battle-the-age-of-the-arena-ac1897ddc715">Wizard Battle: The Age of the Arena</a> - A lore article that dives deep into the origins of Wizard Battle’s magical world</li><li><a href="https://medium.com/zknoid/inside-orbirium-the-three-layer-architecture-behind-the-game-aad287510554">Inside Orbirium: The Three-Layer Architecture Behind the Game</a> - A technical overview of Orbirium’s layered architecture in detail.</li></ul><h3>Looking Ahead</h3><p>With matchmaking, sessions, and core systems now in place, the stage is set for the next phase of Wizard Battle: expanding gameplay mechanics, polishing balance, and preparing for testing in a closed environment.</p><p>For Orbirium, the SUI-Zeko state transfer is the final key before launch.</p><p>It’s been a month of progress, and the momentum is only building. Stay tuned and follow ZkNoid to stay in the loop as we can’t wait to show you what’s next!</p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3080440eb0e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/monthly-recap-august-2025-3080440eb0e5">Monthly Recap: August 2025</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wizard Battle: The Age of the Arena]]></title>
            <link>https://medium.com/zknoid/wizard-battle-the-age-of-the-arena-ac1897ddc715?source=rss-514b792ab87d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac1897ddc715</guid>
            <category><![CDATA[zkapps]]></category>
            <category><![CDATA[zknoid]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[mina-protocol]]></category>
            <category><![CDATA[blockchain-gaming]]></category>
            <dc:creator><![CDATA[ZkNoid]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 14:30:10 GMT</pubDate>
            <atom:updated>2025-08-28T14:30:10.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHHE87iIf8weDKRTwJEktQ.png" /></figure><p>Before the first spellbook was written or the first wizard’s staff was carved, magic existed as a wild, untamed current running through the world. It was unpredictable, dangerous, and impossible for mortals to control.</p><p>Everything changed with the discovery of <strong>Orbirium</strong> — an ancient celestial forge drifting in the void between realms. When humanity unlocked its secrets, raw magical chaos could finally be shaped into Arcane Orbs: stable vessels of pure magic, each embodying a specific essence of the arcane: fire, water, nature, illusion, and more.</p><p>With these Orbs, magic became something that could be wielded…</p><h3>The Golden Era of Orbs</h3><p>For centuries, the Orbirium forge burned bright, producing Orbs that were traded, stolen, and fought over. Civilizations rose around those who could command them. Magical schools, royal courts, and secret cults all schemed for control.</p><p>But such abundance could not last. The Astral Mechanism that powered the forge began to fade. No new Orbs emerged. Some whispered humanity’s greed had drained it; others spoke of a cosmic cycle beyond mortal influence.</p><p>Now, Orbs are relics — rare, sought after, and deadly in the wrong hands. Those who wield them are no mere magicians. They are <strong>Wizards</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UaRAnxt_YqMADvr5G9st6Q.png" /></figure><p>Each Orb was unique. Black Orbs channeled primordial chaos; Red Orbs burned with rage; Blue Orbs bent time, and perception; White Orbs shone with light and restoration. Others — green, violet, and stranger still — tapped into nature, gravity, illusion, and the spirit.</p><h3>Age of the Arena</h3><p>In this new age, Orbirium no longer chooses the worthy. Wizards must fight for their right to wield magic.</p><blockquote>The forge is silent. The Orbs are fading. Only those strong enough to survive the Arena will uncover what lies beyond the last Orb.</blockquote><p>The arena emerged as the proving ground for these rival powers. An ever-shifting battleground charged with the residual energy of Orbirium, it is as dangerous as the Wizards who fought within it. Cliffs, forests, marshes, and lakes could be turned into weapons or shields by the skilled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_PzSOWT9ZoVX6yk2ELfIUg.png" /></figure><p>Here, battles are won not only with magic, but with cunning, timing, and mastery of the terrain.</p><p>Victory in the Arena means more than glory. Each duel brings prestige, rare knowledge, and whispers of the path to reawaken the silent forge. Some say the Champion of the Arena will stand at the very edge of rediscovering the true source of all magic.</p><h3>Wizard Battle Begins</h3><p>Wizard Battle is an upcoming web3 tactical strategy game and a sequel to Orbirium where every move matters and every choice can mean victory or defeat.</p><p>Choose your wizard, master their unique powers, defeat opponents in the arena, and rise through the ranks to claim the title of Champion. The fate of magic itself may rest in your hands.</p><p><strong>The battle for the last Orb will begin soon.</strong></p><p><a href="https://www.zknoid.io/">Website</a> | <a href="https://docs.zknoid.io/docs">Docs</a> | <a href="https://x.com/zknoid">Twitter</a> | <a href="https://discord.gg/AFvypCkU">Discord</a> | <a href="https://t.me/ZkNoid">Telegram</a> | <a href="https://zknoid.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac1897ddc715" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zknoid/wizard-battle-the-age-of-the-arena-ac1897ddc715">Wizard Battle: The Age of the Arena</a> was originally published in <a href="https://medium.com/zknoid">ZkNoid</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>