<?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 Trond Bjorøy on Medium]]></title>
        <description><![CDATA[Stories by Trond Bjorøy on Medium]]></description>
        <link>https://medium.com/@trondbjoroy?source=rss-ee3e08307261------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dGut3-hPRlwqJA_YrclkhA.jpeg</url>
            <title>Stories by Trond Bjorøy on Medium</title>
            <link>https://medium.com/@trondbjoroy?source=rss-ee3e08307261------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:14:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@trondbjoroy/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[Introducing Hathor Forge: A local development environment built for builders]]></title>
            <link>https://blog.hathor.network/introducing-hathor-forge-a-local-development-environment-built-for-builders-cf4db27b427b?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf4db27b427b</guid>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 12:31:01 GMT</pubDate>
            <atom:updated>2026-03-31T12:31:01.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1_3sjweMWugFCkYH33H1Ww.png" /></figure><p>Have you ever sat down to build something on a blockchain and spent the first hour doing everything except building? Spinning up a local node, connecting it to a wallet service, getting the mining service running, making sure all the ports are talking to each other. None of these steps are especially difficult in isolation, but together they create friction at exactly the moment when you should be moving fast.</p><p>That is the problem Hathor Forge is designed to solve.</p><p>Hathor Forge is a local blockchain development environment for Hathor Network. Think Ganache, but for Hathor. With a single command, or a single click, you have a fully running local network: a fullnode, a CPU miner producing blocks, a wallet headless service, and an MCP server for AI-assisted development. No configuration files to write. No ports to debug before you’ve written a line of application code.</p><p><strong>Zero configuration by default</strong></p><p>The fastest path to a running network is the CLI. If you have Nix, you don’t even need to clone the repository:</p><blockquote>nix run github:HathorNetwork/hathor-forge — — start</blockquote><p>That command starts everything. All services run locally on fixed ports, so nothing leaks to mainnet or testnet and nothing costs real HTR.</p><p>For developers who prefer a visual interface, there is also a desktop app, built with Tauri, with a dashboard, a wallet manager, an embedded block explorer, and an interactive Swagger UI for testing APIs. The app runs on macOS, Linux, and Windows (experimental), and you can switch between the CLI and the desktop depending on what you are doing and what kind of builder you are.</p><p><strong>A pre-funded faucet and wallets on demand</strong></p><p>The local fullnode starts with a pre-funded HD wallet that receives all mining rewards. From there, you can create as many test wallets as you need, fund them instantly through the faucet, and start sending transactions. No waiting, no requesting tokens from an external source, no rate limits.</p><p>If you have spent any time building on testnets, you will know this matters more than it sounds. External faucets can be slow, offline, or rate-limited, and that dependency on something outside your control is a constant source of friction. With Forge, the faucet is yours, the miner is yours, and the whole state of the chain is under your control. You can reset everything with a single command and start from a clean slate whenever you need to.</p><p><strong>Composable by design</strong></p><p>Not every project needs the full stack, and Forge doesn’t assume that it does. If you already have a node running somewhere and only need the wallet service locally, that is a single flag:</p><blockquote>nix run github:HathorNetwork/hathor-forge — — wallet-only — fullnode-url http://mynode:8080</blockquote><p>Each component can be toggled independently. Skip the miner if you want to control block production manually. Skip the wallet service if your application talks directly to the fullnode API. Connect to an external transaction mining service if you already have one running. Your preferred configuration can be persisted with — save-settings, so it is there the next time you open Forge without having to remember which flags you used last time.</p><p><strong>AI-assisted development through MCP</strong></p><p>Forge ships with a built-in MCP server. The Model Context Protocol lets AI assistants like Claude interact with the local environment programmatically, using the same tools a developer would use but without leaving the editor.</p><p>The MCP server exposes 26 tools across six categories: node control, miner control, wallet service control, wallet operations, faucet operations, and blockchain queries. Connecting it to Claude Code takes two commands:</p><blockquote>nix run github:HathorNetwork/hathor-forge — — start</blockquote><blockquote>claude mcp add — transport http hathor-forge <a href="http://127.0.0.1:9876/mcp">http://127.0.0.1:9876/mcp</a></blockquote><p>If you prefer a config file, you can add the server directly to your project’s .mcp.json and it will be available automatically. Claude Desktop users can copy the config from Settings → MCP Integration.</p><p>Once connected, you can ask Claude to start the blockchain, create a test wallet, and fund it with HTR, and it will handle all of that through the MCP tools without you switching context. For teams building and testing Nano Contracts, this means you can describe a test scenario in plain language and have the local environment set up to match it.</p><p>The ability to script and automate the local environment through natural language meaningfully accelerates iteration, particularly in the early stages of a project when you are constantly tearing down and rebuilding test states.</p><p><strong>What this means for building on Hathor</strong></p><p>At Hathor, our goal has always been to make it as easy as possible to build real products on the network. The time between having an idea and being able to test it on a running chain should be as short as possible, and that is what Forge is designed to deliver.</p><p>Whether you are writing a Nano Contract blueprint, integrating a custom token into an application, or simply learning how the network works, Forge gives you a safe and self-contained space to do it in. The block explorer and the Swagger UI mean you can observe what is happening on your local chain without building additional tooling. The wallet manager gives you a clean interface for managing test identities. The faucet removes the dependency on any external service.</p><p>We built Forge because developers asked for it, and we will keep improving it based on what builders actually need.</p><p><strong>Getting started</strong></p><p>Hathor Forge is open source and available now. You can find the repository, releases, and documentation at<a href="https://github.com/HathorNetwork/hathor-forge"> github.com/HathorNetwork/hathor-forge</a>. The latest release at the time of writing is v0.6.2.</p><p>If you run into issues or want to suggest a feature, the issue tracker is open.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf4db27b427b" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/introducing-hathor-forge-a-local-development-environment-built-for-builders-cf4db27b427b">Introducing Hathor Forge: A local development environment built for builders</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privacy is coming to Hathor]]></title>
            <link>https://blog.hathor.network/privacy-is-coming-to-hathor-c0d2440a47b8?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0d2440a47b8</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Fri, 20 Mar 2026 12:01:00 GMT</pubDate>
            <atom:updated>2026-03-20T12:01:00.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QY3nSktsMyjC1ONlTG-rGw.png" /></figure><p>Confidential transactions in blockchain has always been a hard problem. Not technically, in isolation, but as a design problem. Most networks that have tackled it have done so by adding layers of complexity that users are expected to navigate on their own: separate shielded pools, explicit shielding transactions, multiple address types, and a constant awareness of which “mode” their funds are in. The result is that privacy becomes a feature for the technically adventurous rather than a default for everyone.</p><p>We think that is the wrong approach, and we are building something different.</p><h3>What we are building</h3><p>We are introducing confidential transactions to Hathor, allowing transaction amounts and asset identifiers to be hidden onchain while keeping addresses public. This covers the vast majority of what businesses and developers actually need when they talk about financial privacy.</p><p>To be specific about what this means in practice: when a confidential transaction settles on Hathor, outside observers cannot determine how much was sent or which asset was transferred. The sender and receiver addresses remain visible. This is a deliberate choice. Hiding amounts and assets provides meaningful financial confidentiality, and it does so without sacrificing the network transparency that makes the ecosystem function.</p><p>Hiding sender and receiver addresses is a separate problem with different tradeoffs, and it is not part of this initial release. We may add it at a later stage if there is demand.</p><h3>Two privacy patterns for token creators</h3><p>We are discussing two options for how token issuers can handle privacy.</p><p>The first is having a fully private custom token, where confidentiality is enforced at the asset level for every transaction. There is no way to turn it off. If you are building a financial product where privacy is a fundamental requirement, you can issue a token that makes confidential transactions the only option, removing any ambiguity for the people using it.</p><p>The second pattern applies to all tokens on the network, including HTR. Every token will support both transparent and confidential transactions. Privacy will be on by default, though users can change their personal default setting in the wallet. This means that over time, confidential transactions become the norm rather than the exception, without forcing anyone’s hand.</p><h3>One address type, no shielding ceremony</h3><p>One of the clearest ways that other privacy networks create friction is through multiple address formats. Users end up with one address for transparent funds, another for shielded funds, and this is something they have to think about every time they move tokens. We are not doing that.</p><p>Hathor will introduce a single new address type that supports both transparent and confidential transactions. This will be the address format used for all future transactions going forward, regardless of whether they are shielded or not.</p><p>The other decision we made is that users will never interact with shielding or deshielding as explicit steps. The wallet handles privacy transitions automatically in the background. If a transaction needs to move between shielded and unshielded states, that happens without requiring any action or awareness from the user. You send a transaction. The wallet takes care of the rest.</p><h3>Fees and economics</h3><p>Confidential transactions are larger and more computationally intensive to verify than standard ones. Rather than absorb that cost in ways that create distortions elsewhere, we are applying a flat configurable fee whenever a transaction includes confidential components. This applies consistently across HTR and all types of custom tokens. The network prices the actual cost of what it is doing.</p><h3>What you can see and what you cannot</h3><p>Explorers remain useful under this model. Wallets will generate links to the explorer that include a URL parameter carrying the decryption information relevant to that user. The sender sees full transaction details. The receiver sees the outputs belonging to their address. Anyone else sees blinded amounts and assets. The transaction is still onchain and inspectable, just not in full.</p><h3>Selective disclosure and auditing</h3><p>Confidentiality without any mechanism for disclosure is not suitable for real financial applications. We are building selective disclosure into the protocol at multiple levels. We are considering different approaches so the final solution isn’t yet confirmed but this is what we are currently doing:</p><p>At the transaction level, users can generate a proof of payment that includes the transaction ID, blinding data, asset, and amount. This lets someone prove a specific payment happened and for exactly how much, without revealing anything else about their wallet.</p><p>At the address level, each address can have an auditing key that reveals all associated transactions, amounts, and asset types. This enables accounting and compliance workflows without granting any ability to move funds.</p><p>At the wallet level, institutions can use a master auditing key covering all derived addresses, enabling full portfolio audits. In all cases, viewing authority and spending authority remain completely separate.</p><h3>Why this matters for builders</h3><p>We have always said that Hathor’s job is to make it as easy as possible to build real financial applications on a blockchain. Confidential transactions are a prerequisite for a large class of those applications. A tokenized invoice, a private payroll system, a settlement layer for institutional trades: none of these can work if every counterparty can read every transaction in plain text.</p><p>What we are building gives developers the tools to create those applications without asking their users to become cryptography-aware. Privacy is the default. Compliance is built in. And none of it requires a separate product or an extra step.</p><p>Our privacy solution will let anyone create a privacy token out of the box, in a few seconds, making Hathor the easiest blockchain to launch and use private tokens.</p><p>We will have more to share on the technical implementation as development progresses. In the meantime, we welcome your inputs on our <a href="https://github.com/HathorNetwork/rfcs/blob/feat/shielded-outputs/text/0000-shielded-outputs.md">RFC</a>.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0d2440a47b8" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/privacy-is-coming-to-hathor-c0d2440a47b8">Privacy is coming to Hathor</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Web Wallet & Hardened Wallet Security]]></title>
            <link>https://blog.hathor.network/new-web-wallet-hardened-wallet-security-f85f25eee6c0?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/f85f25eee6c0</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[metamask]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[hathor-network]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 14:07:35 GMT</pubDate>
            <atom:updated>2025-12-30T14:07:35.882Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnvukdqpJKn8Dhx6WxLh8w.png" /></figure><p>Hathor’s wallets now ship with hardened JavaScript security powered by LavaMoat, and the new <a href="https://wallet.hathor.network/">Hathor Web Wallet</a> launches with the same protection through the <a href="https://snaps.metamask.io/snap/npm/hathor/snap/">Hathor MetaMask Snap</a> experience. The focus is to strengthen our wallet security by constraining what third‑party code is allowed to do inside the application.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9rGq6YbO9GU&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9rGq6YbO9GU&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2F9rGq6YbO9GU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=google" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c75c094ef911138b17c2b310940d9575/href">https://medium.com/media/c75c094ef911138b17c2b310940d9575/href</a></iframe><h3>What LavaMoat adds to Hathor wallets</h3><p>LavaMoat is a security toolkit that isolates dependencies and applies least‑privilege access to JavaScript modules. Instead of letting every library see the full environment, LavaMoat places each module in a compartment and grants only the capabilities it actually requires.</p><p>In Hathor’s wallets, this means each module runs in a controlled environment with a clearly defined set of permissions. A policy file describes which packages may access specific APIs, and core JavaScript features are locked down to prevent tampering with global behavior. If a dependency is ever compromised, its impact is tightly contained.</p><h3>Protecting against supply chain attacks</h3><p>Supply chain attacks often arrive through trusted packages, updates, or build steps, without touching the application’s own business logic. Recent examples in crypto include the attacks on <a href="https://quasa.io/media/trust-wallet-chrome-extension-compromised-7-million-stolen-in-sophisticated-supply-chain-attack">Trust Wallet’s Chrome extension</a>, the <a href="https://www.infosecurity-magazine.com/news/solana-library-supply-chain-attack/">@solana/web3.js npm</a> library and on <a href="https://www.blockaid.io/blog/attack-report-ledger-connect-kit">Ledger’s Connect Kit</a>. LavaMoat addresses this by treating dependencies as untrusted by default and then explicitly opting them into the access they need.</p><p>For our wallets, this helps prevent malicious code from moving laterally inside the application or reaching sensitive data such as keys and transaction details. Dependency is segmented into smaller trust zones, which significantly reduces the potential damage of a single compromised package.</p><h3>The new Hathor Web Wallet</h3><p>The new Hathor Web Wallet offers a clean, browser‑based interface for managing HTR, custom tokens, NFTs, and interacting with the Hathor ecosystem. It adopts the same LavaMoat‑hardened model as the existing wallets, so the browser experience benefits from compartmentalized dependencies and explicit permissioning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OcJZ4Hj4BcIKw7Bo1I1_dw.png" /></figure><p>The design aims for a familiar feel for users who already manage assets in the browser, while keeping our preference for clear workflows and predictable behavior. Behind the scenes, the same security mindset guides integration with shared libraries and supporting services.</p><h3>Powered by the Hathor MetaMask Snap</h3><p>The Hathor Web Wallet is built to work alongside the Hathor MetaMask Snap, which adds native support for Hathor assets directly inside MetaMask. With the Snap installed, you can manage HTR, create custom tokens, and interact with Nano Contracts from the MetaMask interface you already use.</p><p>Together, the web wallet and the Snap provide two coordinated entry points into the Hathor ecosystem. MetaMask handles keys and transaction signing with Hathor‑aware logic from the Snap, while the web wallet focuses on balance views, token management, and Hathor‑specific features and dApps. LavaMoat’s compartmentalization helps keep both surfaces resilient, even when they rely on broader JavaScript tooling.</p><h3>A layered security approach for Hathor</h3><p>LavaMoat fits into our broader security posture, which also includes hardened node behavior and careful peer management at the network layer. Within the wallets, LavaMoat adds a practical layer of defense against supply chain threats by constraining dependencies and enforcing clear boundaries.</p><p>For our users, the result is a wallet experience that is designed to keep keys and transactions protected while still feeling familiar and accessible. For developers, it lets you build features on top of a security model that assumes dependencies can misbehave and ensures that, if they do, the damage stays contained.</p><p><strong>***</strong></p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f85f25eee6c0" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/new-web-wallet-hardened-wallet-security-f85f25eee6c0">New Web Wallet &amp; Hardened Wallet Security</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking blockchain economics: Fees that fit your project]]></title>
            <link>https://blog.hathor.network/rethinking-blockchain-economics-fees-that-fit-your-project-6ec5d49ac867?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec5d49ac867</guid>
            <category><![CDATA[tokenomics]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Thu, 14 Aug 2025 14:02:35 GMT</pubDate>
            <atom:updated>2025-08-14T14:02:35.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sk1YQxk6jYJKSPKJc7ZXXA.png" /></figure><p>The cost and friction of blockchain networks have stifled mass adoption for years. On almost every major layer 1 users run into the same roadblocks: unpredictable and sometimes exorbitant gas fees, the constant requirement to maintain native token balances just to transact, and a total lack of flexibility for projects that want to craft a truly seamless user experience.</p><p><strong>Hathor solves these problems at both the protocol and dApp level with a flexible, modular fee structure built for developers, projects, and real users.</strong></p><h3>Fees that actually fit <strong>your</strong> use case</h3><p>The current blockchain fee model is broken. On networks like Ethereum and Avalanche, every transaction requires the user to pay gas in the chain’s native token (ETH or AVAX), even if the transaction is for a different token entirely. That means no matter which token ecosystem or dApp you want to use, you must acquire, store, and manage some amount of the native currency just for fees.</p><p>Failed or congested transactions only add insult to injury, consuming fees without delivering results or disclosing real costs behind friendly interfaces. Not only does this directly cost users money, it kills UX and causes onboarding headaches for any new dApp or token project.</p><p>It is worth noting that on Ethereum, Solana, and many other networks, some wallets and application-level tools provide the option for users to “pay” fees using other tokens. However, these tools work by automatically swapping the user’s chosen token into the required native token on the backend, and then paying the fee in the native token as mandated by network rules. From the network’s perspective, every transaction fundamentally requires the native token for gas, and the user must ultimately bear this conversion cost and complexity. Such approaches do not represent true protocol-level fee flexibility; instead, they layer additional abstractions without removing the underlying constraint.</p><p>Hathor’s model, on the other hand, brings flexibility and composability to blockchain economics.</p><h3>Incentives that drive ecosystem growth</h3><p>The fee distribution in Nano Contracts is just as groundbreaking:</p><p>70 percent of collected fees are burned to provide strong deflationary pressure and long-term value appreciation for all token holders. 30 percent goes directly to the authors of the blueprint that powers the contract, creating a sustainable, modular, and open marketplace for high-quality building blocks.</p><p>Where most Layer 1s simply burn all fees or pay them to miners and validators with no reward for developers, Hathor ensures that the people building the foundational components for the ecosystem get continuous, usage-based rewards. This is not just token grants or generosity, but a genuine open-source, incentive-aligned revenue model.</p><p><strong>Why does this matter?</strong></p><p>Blueprint developers are financially incentivized to maintain and improve their code, without needing to launch their own tokens or build and maintain entire dApps. This enables an explosion of modular, reusable, highly specialized blueprints, each optimized, audited, and built to scale.</p><h3>Nano Contracts: Pay fees in the asset you actually want</h3><p>Instead of being locked into a single fee token, Nano Contracts allow execution fees to be paid in any supported token. Need to execute a contract? Pay with USDC, your custom project token, or the community’s favorite asset. There is no need to keep HTR just for gas. From an onboarding and retention perspective, this is a game-changer.</p><p>How is this better than other blockchains?</p><p>Ethereum: Only accepts ETH gas fees. Users of USDT, DAI, or other ERC-20 tokens still must maintain ETH for gas. Failed and stuck transactions still consume gas, even if the network is jammed.</p><p>Solana, Avalanche, and SUI: Also require their native tokens (SOL, AVAX, or SUI) for all fees, regardless of what the transaction or dApp does.</p><p>Polygon: Offers some improvements in gas cost, but still only supports POL (replacing MATIC as the native token on Polygon) as gas at the protocol level.</p><p>Hathor: Any deposit-based token can be used as gas, so both DeFi and gaming projects can build frictionless user experiences and remove a major barrier for non-crypto natives.</p><h3>Token creation: Choose between feeless and fee-based</h3><p>Most blockchains either ignore or overcomplicate the economics of token creation and movement:</p><p>Ethereum: Every custom ERC-20 token transfer is subject to gas fees paid in ETH. Users must always pay, regardless of project needs.</p><p>Avalanche, Solana: Similar rules, every token gets the same fee treatment, charging the network’s base token for every transaction.</p><p>Not so on Hathor. When you create a new token, you choose:</p><p><strong>Deposit token: enable feeless transactions</strong></p><p>Lock up 1% of your token’s total supply as an HTR deposit (fully refundable if your token is later burned). All transfers of this token are subsequently feeless. No HTR or any other token is paid by users during transfers.</p><p><strong>Fee token: simple, usage-based payments</strong></p><p>Alternatively, create a token with no upfront deposit. Each transfer then pays a small fee: 0.01 HTR for every output that includes a fee token.</p><p>This design choice matters, as the token type is permanent and has real governance and product consequences; deposit tokens are perfect for high-frequency utility tokens where zero fees are central to the experience. Fee tokens, however, are great for memes, collectibles, and projects where transfer frequency is low or that wish to minimize initial capital amount.</p><p>When a transaction involves fees, the Hathor protocol allows payment in HTR by default, but you can also pay in any deposit-based token at a fixed ratio. Paying 1.00 of your deposit token covers the same as 0.01 HTR. This turns custom tokens into first-class citizens for network operation and gives projects the freedom to craft tailored economic flows.</p><p>Every transaction fee collected, whether from a Nano Contract, user transfer, or custom token operation is burned at the protocol level, removing it from circulation and ensuring long-term sustainability. Fee burning keeps token supply in check, aligns the interests of builders and holders, and prevents runaway inflation.</p><h3>Key takeaways and benchmarking</h3><p>No other major Layer 1 offers true pay-in-any-asset contract fees at the protocol layer. Networks like Ethereum, Solana, Avalanche, and Polygon all require their base token for every operation, regardless of front-end abstractions.</p><p>Native fee burning means ever-increasing deflationary support for the ecosystem.</p><p>Developers can monetize blueprints directly, powering world-class open source, modular app development.</p><p>Token projects choose the right economic model: up-front deposit for feeless mass adoption, or fee per transfer for low-cost launches.</p><p>Users never get stuck paying gas in tokens they do not understand or care about. This is the bridge to true mainstream usability.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec5d49ac867" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/rethinking-blockchain-economics-fees-that-fit-your-project-6ec5d49ac867">Rethinking blockchain economics: Fees that fit your project</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hathor — The only MEV-proof blockchain]]></title>
            <link>https://blog.hathor.network/hathor-the-only-mev-proof-blockchain-712172f8ac0a?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/712172f8ac0a</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[hathor]]></category>
            <category><![CDATA[mev]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 19:55:16 GMT</pubDate>
            <atom:updated>2025-07-24T19:57:41.593Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hathor Network, the only MEV-proof blockchain</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72DNRDFqt7DMzisX-ibkfw.png" /></figure><p>Maximal Extractable Value (MEV) attacks cost DeFi users billions annually through front-running, sandwich attacks, and transaction reordering. These attacks exploit blockchain’s transparent mempool and miners’ transaction ordering power. To date, MEV has been responsible for more than $1.3 billion in lost value for Ethereum users alone.</p><h3>Native MEV protection through novel transaction ordering</h3><p>Hathor’s DAG-based architecture provides comprehensive MEV protection through a revolutionary <strong>pseudo-random transaction ordering system</strong>. Unlike other blockchains that add MEV protection as an optional feature from third parties, our approach is built into the protocol level and decentralized. This is unique among layer 1s and makes Hathor<strong> the only MEV-proof blockchain</strong>.</p><p>Our MEV defense operates through a sophisticated transaction ordering mechanism that prevents attackers from manipulating the execution order. Here’s how it works:</p><p><strong>Topological ordering with randomization</strong>: Transactions are executed in topological order using a modified <a href="https://en.wikipedia.org/wiki/Topological_sorting">Kahn’s algorithm</a>. During each iteration, the algorithm maintains a set of transactions with no dependencies, from which one transaction is selected using a random number generator (RNG) seeded with the block’s hash.</p><p><strong>Consistent randomness across nodes</strong>: All Hathor full nodes shuffle transactions to determine execution order using a common RNG seed based on the latest block hash. This ensures that while the order appears random to attackers, all nodes arrive at the same shuffle order, maintaining consensus.</p><p><strong>Dependency-based ordering</strong>: The system creates a DAG of dependencies containing only nano transactions, derived from the DAG of funds (inputs). This allows users to enforce order on their own transactions while preventing them from enforcing order among other users’ transactions unless explicitly authorized.</p><p>Our MEV protection isn’t just theoretical; it’s been designed and engineered to be robust even as transaction volume and network complexity grow. The protocol ensures that every transaction, regardless of its origin or intent, is subject to the same fair ordering process. This means that even sophisticated attackers cannot game the system by flooding the network or by exploiting obscure transaction dependencies. The randomness is cryptographically strong and tied to the block hash, which makes it unpredictable and tamper-resistant.</p><h3>How it prevents MEV attacks</h3><p>The randomized ordering makes traditional MEV strategies ineffective:</p><p><strong>Sandwich attack prevention</strong>: In a typical sandwich attack, an attacker places a “pre” transaction before a target transaction and a “post” transaction after it to extract value. With Hathor’s system, attackers can’t guarantee their transactions will execute in the required order. The user’s buy order may execute first, while the attacker’s front-run and back-run transactions execute later, eliminating the profit opportunity.</p><p><strong>Front-running elimination</strong>: Since miners can’t predict the block hash in advance, they can’t control transaction ordering to their benefit either. The randomization occurs at the protocol level, making it impossible for miners to arrange transactions for MEV extraction.</p><p><strong>Limited attacker control</strong>: Even if attackers try to use dependency relationships to enforce order, the system’s design prevents them from reliably executing profitable MEV strategies. Placing a “post” transaction after specific target transactions becomes challenging since buy transactions may not have a predetermined order.</p><h3>Real-world implications</h3><p>This MEV protection by design has concrete benefits:</p><p><strong>Fair execution</strong>: Users get transactions executed at expected prices without invisible fees from MEV extraction.</p><p><strong>Reduced costs</strong>: Elimination of MEV-induced slippage means that, as a user, you receive more tokens than you would on other networks.</p><p><strong>True decentralization</strong>: No privileged actors can extract value through transaction reordering. Most L2s today rely on a centralized sequencer model. Contrary to the idea that these solutions are anti-MEV, they instead restrict MEV extraction to the sequencer itself and offer little protection for the users.</p><p><strong>Market efficiency</strong>: DeFi markets operate fairly without systematic exploitation of users.</p><p>For developers and projects building on Hathor, this means you can focus on delivering value to your users rather than defending against MEV bots and transaction manipulators. For users, it means greater trust in the fairness and transparency of every transaction. As DeFi continues to grow, MEV protection will become an essential feature, and we’re the first to make it a reality at the protocol level.</p><p>In the next post, we’ll cover Hathor’s new dynamic transaction model, which will give more utility to HTR and flexibility for token creators.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=712172f8ac0a" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/hathor-the-only-mev-proof-blockchain-712172f8ac0a">Hathor — The only MEV-proof blockchain</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nano Contracts: An architectural paradigm shift]]></title>
            <link>https://blog.hathor.network/nano-contracts-an-architectural-paradigm-shift-c13824841a82?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/c13824841a82</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[hathor]]></category>
            <category><![CDATA[hathor-network]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 19:08:08 GMT</pubDate>
            <atom:updated>2025-07-14T19:08:08.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E7gCX6hXXdOY80GDuCYObw.png" /></figure><p>This is the first in a series of articles talking about some of the novel concepts that make Nano Contracts unique. Unless otherwise specified, the features that we cover in these articles are production-ready and will go live when Nano Contracts are launched on mainnet. If you’re a developer or just interested in learning more about nanos, read on.</p><h3>Blueprints = building blocks</h3><p>Despite the promise of programmable money and automated execution, smart contracts still have flaws preventing mainstream adoption. High gas fees, complex development processes, security vulnerabilities, lack of reusability, and we could go on. With Nano Contracts, we take a fundamentally different approach to solve these problems through architectural innovation rather than incremental improvements and band-aids.</p><p>Traditional smart contracts bundle code and state together in a monolithic structure. Every contract deployment requires writing, testing, auditing, and deploying unique code, even for common use cases. The result is enormous inefficiency and barriers to entry.</p><p>Nano Contracts’ <strong>code-state separation </strong>is a fundamental architectural difference. The concept is simple yet profound: we separate the contract logic (blueprints) from contract instances (state). Think of blueprints as classes in object-oriented programming, where they define behavior once, then get instantiated multiple times with different parameters.</p><p>This makes Nano Contracts highly modular by design. Each contract is constructed from reusable blueprints, which act as independent building blocks that you can combine in countless ways. You build applications by assembling smaller, well-audited components, rather than writing monolithic code from scratch.</p><p>Here’s how this changes everything:</p><ul><li><strong>Blueprint developers</strong> write, test, and audit contract logic once.</li><li><strong>Contract creators</strong> simply instantiate contracts from existing blueprints by changing a few parameters.</li><li><strong>No coding required</strong> on the contract for most use cases, just parameter configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0QS8V9Wzgy8vOH2f" /></figure><p>Let’s look at <a href="https://dozer.finance/">Dozer</a> as a concrete example of how projects can reuse single pieces of code very easily. Here’s a list of contracts that were all created from Dozer’s liquidity pool blueprint on testnet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GnKHR6eELz8ie8Da" /></figure><p>These are all different pools created from a single blueprint, just changing a few parameters. You can view the full list of contracts created and their properties on the <a href="https://explorer.alpha.nano-testnet.hathor.network/nano_contracts/?search=27db2b0b1a943c2714fb19d190ce87dc0094bba463b26452dd98de21a42e96a0">nano testnet explorer</a>.</p><h3>Turing completeness meets radical simplicity</h3><p>In our co-founder and CTO Marcelo’s original vision, Nano Contracts would follow the Pareto Principle. The idea was that 80% of smart contract use cases are based on just 20% of the full possibilities, and Nanos would focus on offering a radically accessible solution to that 20%.</p><p>However, as development progressed, with anyone able to write their own blueprints, those limitations are no longer there. Anything you can build with regular smart contracts, you can do more easily with Nanos.</p><p>This means that despite their ease of use, Nano Contracts maintain <strong>full Turing completeness</strong>. They can solve any computational problem that can be expressed algorithmically, just like Ethereum’s smart contracts. The system can handle loops, conditional statements, complex data structures, and arbitrary logic operations.</p><p>This Turing completeness is important for several reasons:</p><p><strong>Universal computation capability</strong>: Any conceivable smart contract functionality can be implemented, from simple token transfers to complex DeFi protocols, prediction markets, and governance systems. There are no artificial limitations on what developers can build.</p><p><strong>Future-proof architecture</strong>: As new use cases emerge, Hathor can accommodate them without requiring protocol changes. Developers aren’t constrained by the platform’s current capabilities but can innovate freely within the bounds of computational possibility.</p><p><strong>Competitive feature parity</strong>: Nano Contracts can implement any functionality available on other smart contract platforms. This ensures developers don’t sacrifice capabilities when choosing Hathor over alternatives like Ethereum and Solana.</p><p><strong>Complex business logic support</strong>: Real-world applications often require intricate conditional logic, multi-step processes, and sophisticated data manipulation. Turing completeness ensures these requirements can be met regardless of complexity.</p><p>Nano Contracts’ strength lies in making this computational power accessible. While the underlying system can handle any computation, the blueprint model abstracts away the complexity for most users. You get the power of Turing completeness without the burden of dealing with it directly unless your specific use case demands it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2pk0uhp2pPCx282w" /><figcaption><em>Nano Contracts’ architecture</em></figcaption></figure><h3>Scalability through UTXO-based parallelization</h3><p>The scalability of Nano Contracts is fundamentally enhanced by leveraging the UTXO (unspent transaction output) model, which is distinct from the account-based model used by platforms like Ethereum.</p><p>How Nano Contracts achieve superior scalability:</p><ul><li><strong>True parallelism</strong>: each Nano Contract transaction locks only its specific UTXOs, allowing thousands of transactions to be processed in parallel. This removes the global bottleneck of sequential processing found in account based systems.</li><li><strong>Massive throughput</strong>: applications such as stablecoins, payment networks, and RWA tokenization benefit from high transaction throughput, since there is no need to wait for unrelated transactions to complete.</li><li><strong>No global state contention</strong>: state is isolated per contract instance, so there is no need for global account updates. This simplifies state management and reduces the risk of network congestion.</li></ul><p>Additional benefits of the UTXO model:</p><ul><li><strong>Enhanced privacy</strong>: transactions are naturally unlinkable, improving user privacy.</li><li><strong>Simplified scaling</strong>: the architecture supports natural sharding, enabling the network to scale horizontally without unnecessary layer 2 solutions or rollups.</li><li><strong>Resilience and reliability</strong>: parallelization reduces single points of failure and distributes load more effectively across the network.</li></ul><p>By combining the flexibility of smart contracts with the inherent scalability of UTXO-based systems, Nano Contracts offer a future-proof solution capable of supporting mainstream adoption and the next generation of dapps.</p><p>In the next article, we’ll talk about our anti-MEV solution, making Hathor <strong>the only layer 1 with built-in protection</strong>.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, solving significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">X</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c13824841a82" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/nano-contracts-an-architectural-paradigm-shift-c13824841a82">Nano Contracts: An architectural paradigm shift</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hathor’s EVM Bridge — Unlocking a world of possibilities with faster, cheaper cross-chain…]]></title>
            <link>https://blog.hathor.network/hathors-evm-bridge-unlocking-a-world-of-possibilities-with-faster-cheaper-cross-chain-342e7302e855?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/342e7302e855</guid>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Fri, 15 Mar 2024 12:58:57 GMT</pubDate>
            <atom:updated>2024-04-04T07:45:37.412Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hathor’s EVM Bridge — Unlocking a world of possibilities with faster, cheaper cross-chain transactions!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gG0YyWhowUMu_gbkO6jOIg.png" /></figure><p>As you all know by now, Hathor’s EVM bridge is nearing launch and we wanted to make sure that everyone understands why the bridge is important and the impact we hope it will have on Hathor’s ecosystem.</p><p>First of all, we’d like to talk about the bridge’s federator role and how you can become a federator!</p><p><strong>Tldr; If you are building something on Hathor, or considering to do so, you should </strong><a href="https://forms.gle/ZiwLN9KPZXfgHaK46"><strong>apply to become a federator here</strong></a><strong>!<br></strong>Update: We have reached the number of required federators and are currently not accepting any new applications.</p><h3>What are federators?</h3><p>The federators in the Hathor EVM Bridge play a crucial role in managing the secure and accurate transfer of tokens between Hathor and an EVM network (this could be Ethereum or any other EVM compatible network).</p><p>When a token moves from one chain to the other, federators coordinate the locking of the original token on the source chain and the minting of its representation on the destination chain. This ensures the token’s value is preserved across chains.</p><p>Federators operate on Hathor through a MultiSig (Multiple Signatures) mechanism, requiring a minimum number of federators to approve any transaction, including minting and melting tokens. This MultiSig setup enhances security by distributing the power to authorize transactions among multiple parties.</p><p>Federators are responsible for verifying all events and transactions before processing them. This includes ensuring that minted tokens on Hathor match the locked tokens on the EVM network in terms of amount and type, and that melt operations on Hathor allow for the corresponding unlock and transfer on Ethereum.</p><p>In case of transaction failures or rejections, federators coordinate the return of tokens to their original owners. This requires careful examination of the initial transactions to determine the rightful recipients and manage manual or automated return processes.</p><p>In essence, federators serve as the bridge’s operational core, ensuring that token transfers between Hathor and the EVM network are executed securely, accurately, and in compliance with the rules of both blockchains. They play a vital role in maintaining the integrity and value of tokens as they move across chains.</p><p>Federators will receive rewards in the form of a percentage of the fees paid by the user bridging a token. The exact numbers here are being discussed.</p><p>We will arrange a workshop for all federators. Here, the federator role will be explained in full detail and you will get your questions answered.</p><h3>Why should I care?</h3><p>So, why is the bridge important? We believe it’s a game-changer for Hathor, and here are some of the major benefits it will bring:</p><ul><li><strong>Increased interoperability</strong></li></ul><p>The primary advantage is the seamless interoperability between Hathor, Ethereum and other EVM networks. This allows for the transfer of assets, information, and smart contract calls across different networks, enabling a more connected and accessible ecosystem.</p><ul><li><strong>Expanded user base</strong></li></ul><p>By connecting to the EVM ecosystem, Hathor can tap into Ethereum’s substantial user base and market liquidity. We hope this exposure will help attract new users and developers to Hathor.</p><ul><li><strong>Enhanced liquidity</strong></li></ul><p>The bridge facilitates asset transfers between Hathor and other blockchains, which can significantly increase the liquidity of assets on Hathor. We are discussing collaborations with use cases already.</p><ul><li><strong>Stablecoins</strong></li></ul><p>We see the bridge as a necessary step towards bringing USD stablecoins to Hathor, and we are having discussions with stablecoin issuers about this.</p><ul><li><strong>Cross-chain dApps and services</strong></li></ul><p>Developers can create dApps and services that leverage the strengths of both EVM and Hathor. Maybe you have an idea for a dApp that might use Ethereum for EVM smart contract capabilities while utilizing Hathor for faster and feeless transactions?</p><ul><li><strong>Access to Ethereum’s DeFi ecosystem</strong></li></ul><p>Ethereum’s DeFi ecosystem is one of the most developed and sophisticated in this space. By using the bridge, projects building on Hathor can gain access to Ethereum’s DeFi platforms, tools, and services, expanding their financial service offerings.</p><ul><li><strong>Innovation and experimentation</strong></li></ul><p>We hope to see the bridge encourage innovation by allowing developers to experiment with novel, hybrid solutions that utilize the best features of both EVM and Hathor’s ecosystem.</p><ul><li><strong>Faster, free transactions</strong></li></ul><p>Transactions are faster and free when processed on Hathor. This should be particularly appealing for applications that require high throughput or lower transaction costs.</p><p>Those are some of the applications we could think of for the EVM bridge. We’re sure you will come up with other ideas that we didn’t think of yet. If you are planning to build something on Hathor that you think could benefit from the bridge, we’d love to hear from you!</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, and it solves significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">Twitter</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=342e7302e855" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/hathors-evm-bridge-unlocking-a-world-of-possibilities-with-faster-cheaper-cross-chain-342e7302e855">Hathor’s EVM Bridge — Unlocking a world of possibilities with faster, cheaper cross-chain…</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling the Hathor Wallets]]></title>
            <link>https://blog.hathor.network/scaling-the-hathor-wallets-c4ce31924c20?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4ce31924c20</guid>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Fri, 23 Feb 2024 13:40:19 GMT</pubDate>
            <atom:updated>2024-02-23T13:40:19.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8RLH_lsjbh85DNf49hpnw.png" /></figure><p><strong>TL;DR:</strong> As part of our efforts to better scale our wallets, we have rolled out several improvements to our wallets and their backend to prepare them for future growth and new features. The changes include a substantial upgrade to our wallets’ storage scheme that will benefit all use cases. This new solution redesigns how we interact with storage, focusing on modularity and asynchronous processing, resulting in an enhanced user experience and better performance.</p><p>Previously, the storage scheme made it difficult to manage persistent storage solutions, limiting its usability in a variety of use cases. The new approach has transformed these limitations. We have incorporated an asynchronous model, facilitating non-blocking calls to persistent storage. To effectively implement this, we had to refactor most of our calls. Additionally, our reliance on in-memory storage instances was reevaluated and altered, to create a more reliable and efficient system.</p><p>A significant benefit of this update is the improvement in our wallets’ internal functioning. While tackling the previous issues, we identified and rectified key performance challenges experienced by some of our use cases. This has resulted in a more reliable and high-performing wallet in every operating environment.</p><p>The new storage scheme is one of three core updates to the wallet-lib that brings about faster loads, better performance, and enhanced reliability. These changes are:</p><ul><li>Persistent storage: Incorporating a new storage scheme aids in efficiently managing data.</li><li>Enhanced address generation: Previously, deriving addresses consumed significant time and CPU capacity. The new model eliminates this issue, as addresses are pre-generated and saved, optimizing startup time.</li><li><a href="https://blog.hathor.network/simplifying-use-case-integrations-16fca2f6c854">Events Queue</a>: This, combined with persistent storage, ensures reliable integrations with a full node and enables wallet restarts with millions of transactions in less than a second. It eliminates the need to fetch entire transaction histories with each load, making the process more efficient.</li><li>The last update, which was implemented in the next release of the headless wallet, is the new address scanning policy: This policy is beneficial for use cases with numerous inactive addresses, such as exchanges, eliminating the need for a high gap limit (gap limit refers to the standard number of public addresses that are checked for transactions in the blockchain in order to calculate an account’s balance). This will make the service faster as it no longer needs to load thousands of inactive addresses unnecessarily.</li></ul><p>The new storage scheme is a significant step towards a higher-performing lib and enables us to implement faster wallets and services with less effort. Ultimately, this will lead to more reliable integrations for use cases and a better user experience.</p><p>In addition to the new storage scheme, we have developed the wallet service, a new backend for our wallets, which significantly improves loading speeds and prepares the wallets for new features in the future. Over the past months, we have gradually increased the rollout percentage of the wallet service for our mobile and desktop wallet users, and we expect to have all wallets running on this new backend soon. This upgrade will benefit all users who will experience a faster wallet, especially those with many addresses.</p><p>One user with a huge wallet consisting of around 11,000 addresses saw the wallet initialization time reduced from about 30 minutes(!) to 15 seconds after being added to the wallet service. Although that is an extreme case, the wallet service will surely improve the wallet UX for the majority of users.</p><p>The home screens of the wallets have also been updated to load the balance and history of each token asynchronously, further speeding up the initialization time.</p><p>With the recent improvements, we bring users some immediate benefits while simplifying the integration process for use cases. Altogether, we are confident that these changes prepare the wallet infrastructure for the future growth of Hathor Network.</p><p>***</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind, and it solves significant bottlenecks that prevent the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">Twitter</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4ce31924c20" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/scaling-the-hathor-wallets-c4ce31924c20">Scaling the Hathor Wallets</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hathor’s Feature Activation Process: Miners Lead the Way]]></title>
            <link>https://blog.hathor.network/hathors-feature-activation-process-miners-lead-the-way-d7f43b12978d?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7f43b12978d</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[hathor]]></category>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Fri, 29 Sep 2023 12:52:34 GMT</pubDate>
            <atom:updated>2023-09-29T12:52:34.905Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUFdwIwlvLXHlokJCilH9g.png" /></figure><p>In a decentralized environment like Hathor’s, there are sometimes important changes and upgrades to the protocol that the network participants must agree on before they can be implemented and deployed.</p><p>This is especially important for miners who are responsible for the network security. To facilitate the rollout of such changes, we needed to create a way for miners to signal that they agree and are prepared for a specific protocol upgrade.</p><p>We also had to come up with a way to add new features and changes to existing features that don’t go live as soon as the code is upgraded by the users who run full nodes. Instead, the changes have a specific moment in the blockchain when they become live and valid, e.g., from a given blockchain height and/or when a specific percentage of miners agree with the new feature by signaling support for it.</p><p>The act of signaling a block is basically saying that you agree and are prepared for a protocol upgrade. Bitcoin has this feature implemented and it’s easy for Bitcoin miners to share with the rest of the network that they agree and are ready for a protocol change.</p><p>Bitcoin miners signal their support for new features and network upgrades through a process known as “mining signaling” or “version bits signaling.” This mechanism allows miners to express their readiness and support for proposed changes to the Bitcoin protocol.</p><p>The most well-known example of mining signaling in Bitcoin is the activation of soft forks using the <a href="https://en.bitcoin.it/wiki/BIP_0009">BIP9</a> (Bitcoin Improvement Proposal 9) deployment mechanism. With BIP9, miners signal their readiness for a soft fork by setting specific bits in the version field of their mined blocks.</p><p>The feature activation implementation on Hathor is heavily inspired by BIP9 and <a href="https://en.bitcoin.it/wiki/BIP_0008">BIP8</a>. BIP9 was actually used to activate Taproot, Bitcoin’s latest update, and BIP8 is an improvement on top of it. We have had to make some adaptations to the concepts though, to make them work on our network. In short, we have learned from what worked for Bitcoin and tailored it to our needs.</p><p>One notable difference is that on Bitcoin, BIP 8/9 is only used for activating soft forks, i.e., backward-compatible changes. Hathor’s feature activation, on the other hand, will support hard forks as well, which are necessary to implement updates such as Nano Contracts.</p><p>In Q2, we designed our solution for feature activations. After creating a working proof of concept for it we implemented the solution on our testnet.</p><p>It will run here for some time, while we improve the feature activation process and test it on “fake” features to verify that everything is working as expected. Once we are happy with the results, we will perform the same tests on fake features on the mainnet. This will let us assess the process without actually changing anything in the full node operation. After running this <a href="https://github.com/HathorNetwork/rfcs/blob/master/projects/feature-activation/0004-phased-testing.md">phased testing</a> on both testnet and mainnet, we will use the feature activation process on an actual new feature on mainnet.</p><p>You can view the full design of the feature activation process on our <a href="https://github.com/HathorNetwork/rfcs/blob/master/projects/feature-activation/0001-feature-activation-for-blocks.md">GitHub</a>.</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind and solves significant bottlenecks preventing the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">Twitter</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7f43b12978d" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/hathors-feature-activation-process-miners-lead-the-way-d7f43b12978d">Hathor’s Feature Activation Process: Miners Lead the Way</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying use case integrations]]></title>
            <link>https://blog.hathor.network/simplifying-use-case-integrations-16fca2f6c854?source=rss-ee3e08307261------2</link>
            <guid isPermaLink="false">https://medium.com/p/16fca2f6c854</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[hathor-network]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Trond Bjorøy]]></dc:creator>
            <pubDate>Wed, 09 Aug 2023 18:43:31 GMT</pubDate>
            <atom:updated>2023-08-09T18:43:31.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4ookhS9GftYJFiPirLphw.png" /></figure><p><strong>TL;DR:</strong> We’ve developed the Event Queue, an efficient event management system equipped with APIs. This system simplifies integrations and interactions with the Hathor full node, eliminating the need for developers to write their own sync algorithm.</p><h3>The Challenge</h3><p>Until recently, applications that wanted to interact with the Hathor full node needed to write their own sync algorithm. They had to handle all contingencies, such as reorgs (blockchain events where one transaction history is replaced by another, often due to concurrent block-solving, resulting in temporarily divergent versions of the blockchain, known as a fork). Creating this algorithm could be complex, consuming several days of development.</p><p>When you wanted your application to interact with the full node, you had two choices:</p><ol><li>Establish a bidirectional communication via WebSocket.</li><li>Make use of the REST APIs.</li></ol><p>However, both methods came with their own sets of challenges:</p><ul><li>If a reorg occurred, your application had to identify all affected transactions and update them in the application’s database.</li><li>Event order couldn’t be guaranteed.</li><li>In the event of a connection drop, some events might be lost, necessitating a resync.</li></ul><h3>Our Solution: The Event Queue</h3><p>To overcome the issues above, we’ve introduced the Event Queue⁠ — a built-in event management system sending all events in the order of their occurrence. Its key features are:</p><ul><li>It detects events that matter to applications (Refer to the <a href="https://github.com/HathorNetwork/hathor-core/blob/docs/reliable-integration/EVENT_QUEUE.md#eventtype">Event Types</a> in our user docs).</li><li>All events are persisted by the full node, each with a unique incremental ID.</li><li>Both REST API and WebSocket API are available, providing a continuous event stream that can be queried.</li></ul><p>With the Event Queue, events are emitted such that your application doesn’t need to internally understand how to handle cases like reorgs. Instead, explicit changes are emitted, and the application can react appropriately.</p><p>Furthermore, the event order is assured. Hence, if the connection is lost, the application can request a new stream of events starting from the last successful event processed.</p><p>These features collectively simplify and strengthen your integration with Hathor and are another important step toward making blockchain easy.</p><p><strong>Please note:</strong> The Event Queue is currently in beta and is not recommended for production environments. We encourage you to begin using it in your test environment and we welcome any feedback you may have after testing the feature!</p><p>For a detailed guide, please read the <a href="https://github.com/HathorNetwork/hathor-core/blob/2aead426327a43fdaf07cc9971a02c7e3ba51b49/EVENT_QUEUE.md">user docs</a> on GitHub explaining how to set up the Events Queue for your application.</p><p>We also offer an event simulator to aid you in testing your integration with the Event Queue. This CLI tool emits simulated events via WebSocket, mirroring real use case scenarios.</p><p>Look out for a more comprehensive user guide on our <a href="https://hathor.gitbook.io/">GitBook</a> later as we move the feature of beta status.</p><p>***</p><p>Hathor Network is a PoW-based novel distributed ledger architecture that combines DAG and blockchain data structures. Our network’s unique design is built with scalability, usability, and decentralization in mind and solves significant bottlenecks preventing the broad adoption of the technology.</p><p>Hathor Network has been on mainnet since January 2020, experiencing exponential growth in the number of custom tokens, active wallets, and mining hash rate.</p><p>Please visit our <a href="https://hathor.network/">Website</a>, <a href="https://twitter.com/HathorNetwork">Twitter</a>, <a href="https://discord.gg/aWukZZX">Discord</a>, and <a href="https://t.me/HathorOfficial">Telegram</a> channel for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16fca2f6c854" width="1" height="1" alt=""><hr><p><a href="https://blog.hathor.network/simplifying-use-case-integrations-16fca2f6c854">Simplifying use case integrations</a> was originally published in <a href="https://blog.hathor.network/">Hathor Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>