<?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 Ievgen Pushkin on Medium]]></title>
        <description><![CDATA[Stories by Ievgen Pushkin on Medium]]></description>
        <link>https://medium.com/@pushkin.evgenii01?source=rss-7e4cf16f0e8f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_wuT2mW_RfZTre_uIJbtiA.jpeg</url>
            <title>Stories by Ievgen Pushkin on Medium</title>
            <link>https://medium.com/@pushkin.evgenii01?source=rss-7e4cf16f0e8f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:05:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pushkin.evgenii01/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[What is Sentient and Why Does Web3 Need Its Own AI?]]></title>
            <link>https://medium.com/@pushkin.evgenii01/what-is-sentient-and-why-does-web3-need-its-own-ai-0d7677cda802?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d7677cda802</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Sat, 16 Aug 2025 12:30:55 GMT</pubDate>
            <atom:updated>2025-08-16T12:30:55.295Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-9Ox3aMs-RAwepd6Sf1lQ.png" /></figure><p>AI is everywhere today: ChatGPT and other models are popular, but they are centralized. For Web3, this is a problem: the blockchain ecosystem needs open, decentralized, and privacy-preserving solutions. <strong>Sentient</strong> is a project that aims to close this gap.</p><h3>1. The Problem of Centralized AI</h3><ul><li><strong>Closed systems.</strong> The architecture of the models is inaccessible</li><li><strong>Censorship.</strong> Responses are filtered and restricted</li><li><strong>No control over data.</strong> User queries are not always kept private</li><li><strong>No Web3 integration.</strong> Centralized AI services are not built into decentralized ecosystems</li></ul><h3>2. The Solution: Sentient</h3><p>Sentient is creating an open ecosystem layer for Web3 AI:</p><ul><li><strong>OML (Open, Monetizable, Loyal)</strong><br> — <em>Open</em>: free access to model logic<br> — <em>Monetizable</em>: cryptographic fingerprinting rewards authors for the use of their models<br> — <em>Loyal</em>: models remain tied to the community, not corporations</li><li><strong>Fingerprinting (OML-1.0).</strong> A library described in the roadmap that enables monetization and proof of model ownership</li><li><strong>Builder Program.</strong> A program for developers: they can create agents through the Sentient Agent API and connect to the user ecosystem</li></ul><h3>3. Sentient Chat — What is Confirmed</h3><ul><li><strong>The product name is confirmed.</strong> Official sites mention “Sentient Chat” as part of the integration via the Agent API</li><li><strong>Agent interface.</strong> The Builder Program specifies that agents can pass intermediate events back to the client</li></ul><h3>4. Why This Matters for Web3</h3><ul><li><strong>Transparency.</strong> OML makes models verifiable</li><li><strong>Monetization.</strong> Fingerprinting ensures authors are rewarded</li><li><strong>Community.</strong> The Builder Program brings developers into the ecosystem, while Sentient Chat provides a user-facing entry point</li><li><strong>Infrastructure.</strong> Sentient is building a protocol, not a single closed product</li></ul><h3>Conclusion</h3><p>Sentient is Web3-AI infrastructure:</p><ul><li><strong>OML</strong> provides openness, monetization, and loyalty of models</li><li><strong>Fingerprinting</strong> turns models into verifiable digital assets</li><li><strong>Builder Program</strong> engages developers in creating agents and integrating them via API</li><li><strong>Sentient Chat</strong> is confirmed as the user-facing interface for working with agents</li></ul><p>Unlike centralized AI services, Sentient builds a protocol based on cryptography, decentralization, and community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d7677cda802" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summit by Seismic: The Consensus Client They Wish They Had from Day One]]></title>
            <link>https://medium.com/@pushkin.evgenii01/summit-by-seismic-the-consensus-client-they-wish-they-had-from-day-one-963b0f2a0d03?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/963b0f2a0d03</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[summit]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 14:53:20 GMT</pubDate>
            <atom:updated>2025-08-04T14:53:20.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRnm8LB43tIs5-JeBRHtRw.png" /></figure><p>These days, dozens of new blockchains are being built. Some optimize for AI, some for DePIN or DeFi. But <strong>Seismic</strong> took a different path from the very beginning:<br> they’re building a <strong>Layer 1</strong> where <strong>privacy, encrypted computation, and cryptography</strong> are not afterthoughts — they’re the foundation.</p><p>Seismic is building a chain that lets developers launch scalable EVM-based applications with <strong>privacy by default</strong> — encrypted transactions, secure computation, and cryptographic guarantees at the protocol level. That’s the core.<br>Everything else, including consensus, was <strong>secondary</strong>. They just needed something that worked.</p><p>But during the launch of their <strong>devnet</strong>, it became clear: none of the available consensus clients were both:</p><ul><li><strong>fast enough</strong> to keep up with modern networks</li><li>and <strong>easy to integrate</strong> with execution clients like Reth</li></ul><p>So they built <strong>Summit</strong> — the consensus client they wish they’d had from day one.</p><h3>What Was Missing from Existing Options</h3><p>When looking for consensus solutions, the Seismic team faced a typical dilemma:</p><ul><li>Ethereum’s Beacon Chain is battle-tested but slow and tightly coupled to its ecosystem</li><li>Cosmos’ Tendermint is fast but doesn’t work out of the box with EVM clients</li><li>Newer protocols like HotStuff or Bullshark are complex, heavyweight, and experimental</li></ul><p>In every case, you either sacrifice performance or spend months integrating.</p><p>But Seismic had other priorities: <strong>something fast, simple, and practical.</strong></p><h3>What Is Summit</h3><p><strong>Summit</strong> is a standalone consensus client designed to plug into any EVM execution client that supports the <strong>Engine API</strong> (like Reth or Geth). Its sole responsibility is to coordinate agreement across the network — deciding which block comes next and ensuring everyone agrees.</p><p><em>Think of it like this: a blockchain has two core components:</em></p><ul><li>The <strong>execution layer</strong> (e.g., Reth), which processes transactions and updates state</li><li>The <strong>consensus layer</strong> (in this case, Summit), which ensures that all participants agree on the order of blocks</li></ul><p><em>Summit focuses purely on the second task — and it does it quickly and transparently.</em></p><h3>Key Features of Summit</h3><h3>1. Simplex Protocol — no timeouts, no waiting</h3><p>Summit uses an <strong>adaptive consensus protocol</strong> that moves forward as soon as the network is ready — instead of waiting for fixed timeouts.</p><p><em>Most blockchains wait “just in case,” even when the network could move faster. Simplex skips the delay: if the network is ready, the block goes through This saves time and increases performance.</em></p><h3>2. Sub-second block times</h3><p>Real-world benchmarks show Summit producing blocks in <strong>870–1290 milliseconds</strong> — significantly faster than Ethereum.</p><p><em>For users, that means near-instant transactions.<br>For builders, it opens the door to latency-sensitive apps: games, messaging, micro-payments, etc.</em></p><h3>3. EVM Compatibility</h3><p>Summit works with any execution client that implements the <strong>Engine API</strong> — including <strong>Reth</strong>, <strong>Geth</strong>, and others.</p><p><em>That means you can keep using familiar tools and infrastructure — while upgrading your consensus speed.</em></p><h3>4. BLS12–381 Cryptography</h3><p>Validator key management uses modern BLS12–381 cryptography — the same standard used by Ethereum.</p><p><em>In simple terms: secure, efficient validator operations with minimal overhead.</em></p><h3>5. Built on Commonware</h3><p>Summit didn’t reinvent the wheel. It builds on primitives from <strong>@commonwarexyz</strong>, drawing architectural inspiration from their <strong>Alto</strong> project.</p><p><em>This made development faster and more stable — while relying on proven, reusable building blocks.</em></p><h3>Comparison: Turnkey vs Fast</h3><p>Here’s how Seismic illustrates the position of Summit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A3Pq_ChHPmXAoRUbX8V6GQ.png" /></figure><p><em>“Turnkey” means you can plug the consensus layer in without rewriting your architecture.<br>“Fast” means it performs at the speed modern applications expect.<br></em><strong><em>Summit combines both.</em></strong></p><h3>Benchmarks (Performance Tests)</h3><p>These tests were run on AWS across multiple regions, with 100 KB blocks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDC9zwC99BwDosainYGigQ.png" /></figure><p><em>Performance improves as more nodes join — and the bottleneck isn’t consensus, but rather how quickly the mempool feeds data.<br> In short, </em><strong><em>Summit is faster than the rest of the stack can keep up with.</em></strong></p><h3>How Summit Works</h3><p>Summit doesn’t care about what’s inside the blocks. It doesn’t process transactions.<br> Its job is to coordinate:</p><ul><li>who proposes the next block</li><li>how blocks are confirmed</li><li>when finality is achieved</li></ul><p><em>Think of it like a meeting moderator: it doesn’t contribute content, but keeps everything moving and synchronized.</em></p><p>Summit connects to execution clients via the <strong>Engine API</strong>, following Ethereum’s modular client architecture.</p><h3>What’s Next</h3><p>Seismic plans to:</p><ul><li>Add <strong>dynamic validator sets</strong> via staking contracts (like Ethereum)</li><li>Introduce <strong>DKG-based threshold signatures</strong> for higher security and throughput</li><li>Complete a full audit by <strong>Q4 2025</strong></li></ul><h3>Conclusion</h3><p>Summit isn’t trying to be revolutionary. It’s trying to be <strong>useful</strong>.<br> It wasn’t built out of ambition — it was built out of necessity:<br> <strong>Seismic needed a consensus layer that wouldn’t hold the rest of the system back.</strong></p><p>Their real focus remains: encrypted computation, privacy-preserving architecture, and cryptographic soundness.</p><p>But to get there — they needed a foundation.<br><strong>Summit is that foundation.</strong><br>And now, it’s available to others too.</p><p><strong>Resources:</strong><br> 🌐 Website: <a href="https://www.seismic.systems/">https://www.seismic.systems</a><br> 📂 GitHub: <a href="https://github.com/SeismicSystems/summit">https://github.com/SeismicSystems/summit</a><br> 🐦 Twitter (X): <a href="https://x.com/SeismicSys">https://x.com/SeismicSys</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=963b0f2a0d03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privacy Without the Rewrite: How Inco Adds Confidentiality to Web3 Without Breaking UX]]></title>
            <link>https://medium.com/@pushkin.evgenii01/privacy-without-the-rewrite-how-inco-adds-confidentiality-to-web3-without-breaking-ux-1d9d7a5c70b0?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d9d7a5c70b0</guid>
            <category><![CDATA[l1]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 13:39:56 GMT</pubDate>
            <atom:updated>2025-07-25T13:39:56.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11tY2hJBa2Yhal8-Dp3Ixg.png" /></figure><p>Privacy has been a long-standing issue in Web3. Most blockchains are public by design: addresses, transactions, balances — everything is open and traceable. In some cases, that’s fine. But when it comes to salaries, DAO voting, business logic, or gameplay — transparency becomes a vulnerability.</p><p>There are already privacy-focused solutions based on zero-knowledge proofs or custom Layer 1 networks. But most of them require a complete migration to a new ecosystem: new VM, new languages, new mental models. Developers have to relearn tools; users have to accept new interfaces. All of that — just to hide some data.</p><p><strong>Inco offers an alternative</strong>: a privacy layer that integrates into existing chains without replacing them. No new chain. No new language. No disruption to UX.</p><h3>Inco’s Approach: Selective Privacy Within Familiar Infrastructure</h3><p>Inco doesn’t build a new blockchain.<br> Instead, it extends existing EVM-compatible networks with support for encrypted data and operations. This is done through its custom virtual machine — <strong>eEVM</strong>, which introduces new encrypted types:</p><ul><li>euint — encrypted integers</li><li>ebool — encrypted boolean values</li><li>eaddress — encrypted wallet addresses</li></ul><p>Smart contracts written in Solidity can use these types and perform operations on them: addition, comparison, private randomness generation. These operations are executed inside a <strong>Trusted Execution Environment (TEE)</strong> — a secure enclave inside the processor that ensures computations are private and isolated from external access.</p><p>What matters: the developer continues to use familiar tools — Hardhat, Remix, MetaMask. Privacy is applied <strong>only where it’s needed</strong>. Everything else remains public and unchanged.</p><h3>A Practical Example: dApp With Private Logic</h3><p>Suppose you’re building a DAO voting app.<br> By default, votes are public — anyone can see who voted and how. That may not always be ideal.</p><p>With Inco, you can hide the individual votes while still publishing the overall result. No one knows how a specific address voted, but the final tally remains verifiable.</p><p>The same logic applies to games with hidden states (like cards in hand), or payroll systems where salary data shouldn’t be public.</p><h3>What Does the User See?</h3><p>From a user’s point of view — nothing changes. They interact with the app as usual: connect a wallet, click buttons, sign transactions.</p><p>The difference is under the hood. Certain values are encrypted and not publicly visible. But the user doesn’t feel any friction — which is exactly the goal. Privacy isn’t a layer on top; it’s embedded into the workflow.</p><h3>Who Is This Useful For?</h3><ul><li>dApp developers who want privacy without leaving Ethereum</li><li>DAOs implementing confidential voting</li><li>Web3 companies issuing on-chain salaries</li><li>GameFi projects that require hidden game mechanics</li><li>Infra teams working with sensitive user data</li></ul><h3>Want to Go Deeper?</h3><p>If you’re building contracts or want to understand how eEVM works, what operations are supported, and how Inco Lightning is implemented — the documentation is open:</p><p>📎 <a href="https://docs.inco.org/home">docs.inco.org</a></p><p>Privacy in Web3 isn’t a luxury or a complication. It’s a necessity if we want to build serious applications — financial, strategic, or governance-based.Inco makes privacy available without asking you to rebuild everything from scratch.This is not a new ecosystem — it’s an <strong>upgrade to the one we already use</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d9d7a5c70b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MEMORY IS OVERLOADED]]></title>
            <link>https://medium.com/@pushkin.evgenii01/memory-is-overloaded-490e547a3788?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/490e547a3788</guid>
            <category><![CDATA[memories]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 12:18:32 GMT</pubDate>
            <atom:updated>2025-07-24T12:18:32.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pImp0WG1vAxOns7e-WMhIQ.png" /></figure><h3>Memory overload isn’t just a metaphor</h3><p>Modern blockchains face a fundamental problem:<br><strong>data is stored inefficiently, expensively, and without logical context.</strong></p><p>Every transaction, every NFT, every onchain file adds to a growing mass of disconnected information — hard to access, hard to trust, hard to manage.</p><p>But solving this isn’t about “adding more space.”<br>We need a <strong>new memory architecture</strong> — structured, programmable, and verifiable.</p><h3>Irys: The Programmable Datachain</h3><p><strong>Irys is not just data storage.</strong><br>It’s a blockchain where data becomes an active participant in logic and execution.</p><p>According to Irys documentation, the protocol combines:</p><ul><li>💾 <strong>Reliable storage</strong> (via Arweave + Publish Ledger)</li><li>🧩 <strong>Built-in execution logic</strong> (Submit Ledger + IrysVM)</li><li>🔁 <strong>Updatable references</strong> (mutable references)</li></ul><h3>Irys Architecture: How it Works</h3><h3>1. Submit Ledger → Publish Ledger</h3><p>When data is uploaded to Irys, it flows through two distinct layers:</p><ul><li><strong>Submit Ledger</strong>: verification, logic execution, temporary anchoring</li><li><strong>Publish Ledger</strong>: permanent storage and immutability</li></ul><p>This layered approach separates compute from storage, improving scalability without compromising integrity.</p><h3>2. Programmable Data</h3><p>Any data object on Irys can include executable logic:</p><ul><li>Access conditions</li><li>Smart contract triggers</li><li>Event-driven behaviors</li></ul><p><strong>Example:</strong><br>Upload a file that can only be accessed after a DAO vote or on-chain payment.</p><p>This isn’t storage — it’s <strong>onchain automation</strong></p><h3>3. Mutable References</h3><p>Traditional systems offer static or overwritten data.<br> Irys introduces <strong>mutable references</strong>:</p><ul><li>You create a reference (link) that can be updated</li><li>Every version is stored and cryptographically verifiable</li><li>This enables flexibility without sacrificing transparency</li></ul><h3>4. IrysVM: The Data-Aware Virtual Machine</h3><p><strong>IrysVM</strong> is an EVM-compatible environment where smart contracts can:</p><ul><li>Natively access stored data</li><li>Execute logic embedded in data objects</li><li>Interact with mutable references as first-class citizens</li></ul><p>This reduces fragmentation between logic and storage — opening use cases like dynamic NFTs, pay-per-use AI models, and onchain licensing.</p><h3>What This Means for Users and Developers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PV0p7obYf-Ip1GHcEiLUzg.png" /></figure><h3>Why It Matters</h3><p>Memory overload isn’t just about space.<br>It’s about lack of structure, missing logic, and lost trust.<br><strong>Irys addresses these problems at the protocol level</strong>, not as a patch or plugin.</p><h3>Final Thoughts</h3><p>The next time you see “Memory is overloaded”, ask yourself:<br>Do we really need more storage or do we need a way to <strong>organize, control, and activate</strong> the data we already have?</p><p>Irys offers exactly that.<br>A programmable datachain.<br>Where memory isn’t a burden — it’s a tool.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490e547a3788" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Thought Out Loud: It’s Like Web3 Forgot Something]]></title>
            <link>https://medium.com/@pushkin.evgenii01/a-thought-out-loud-its-like-web3-forgot-something-76f1ffb227e9?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/76f1ffb227e9</guid>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 13:49:23 GMT</pubDate>
            <atom:updated>2025-07-18T13:49:23.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOptUHjggyLWRZ-tRXpUWg.png" /></figure><p>All of Web3 talks about transparency</p><p>Smart contracts are open, every transaction is visible, and the blockchain is a ledger anyone can verify. But here’s the paradox: <strong>sometimes transparency is the problem</strong>.</p><p>We store user data publicly<br>We vote publicly<br>We send tokens — and the whole world sees who sent what, where, and how much</p><p>It works. But it works <strong>a little too well</strong> to be safe.</p><h3>Where’s the Privacy in Web3?</h3><p>Almost everything we do in Web3 is visible to everyone.<br> That might be convenient for auditors and traders — but not for people.</p><ul><li><strong>Salaries</strong> in tokens are public</li><li><strong>Votes</strong> can be traced back to wallets</li><li><strong>Games</strong> can’t include secrets — decks, moves, points are all exposed</li><li><strong>DeFi competition</strong> becomes a bot war, not a fair user experience</li></ul><p>What was once considered a “feature” has become a <strong>real blocker for the next phase of Web3</strong>.</p><h3>Inco: Privacy as a Layer</h3><p>Inco is not just another blockchain.<br> It’s a <strong>privacy layer</strong> that can be integrated into existing networks like Ethereum, Base, or Polygon.</p><p>With Inco, developers can:</p><ul><li>Encrypt on-chain smart contract data</li><li>Perform private computations</li><li>Do this <strong>without migrating</strong> to a new chain</li><li>Use familiar tools like Solidity, MetaMask, Hardhat</li></ul><p>In short: Inco brings privacy to Web3 <strong>without breaking everything that already works</strong></p><h3>How Does It Work? A Look at Inco Lightning</h3><p>Let’s look at one of Inco’s core products — <strong>Inco Lightning</strong>.<br> It’s a fast way to add privacy to smart contracts using <strong>TEE (Trusted Execution Environment)</strong> — a secure zone inside a processor that runs computations without revealing inputs or results.</p><p>Imagine you want to add two numbers but don’t want anyone to see them — not the inputs, not the output.<br> With Inco, that’s possible. The data is encrypted, processed privately inside TEE, and only you see the result.</p><p>This is done using special encrypted variables.<br> Instead of regular data types, you use types like <strong>euint</strong> (encrypted unsigned integer).<br> Instead of standard math or logic, you use built-in functions that know how to work with encrypted values.</p><p>Inco Lightning supports:</p><ul><li><strong>Private data</strong> types: addresses, numbers, booleans</li><li><strong>Encrypted operations</strong>: addition, multiplication, comparison</li><li><strong>Randomness</strong>: private random number generation (essential for games, lotteries, etc)</li></ul><p>Most importantly, developers don’t need to learn a new stack.<br> It works with existing EVM-compatible chains.</p><p>That means users get:<br> 🔐 Private token balances<br> 🗳️ Encrypted voting<br> 🎮 Games where you can actually hide your moves</p><p>And all of this is already live in the testnet.</p><h3>👀 But Can It Be Trusted?</h3><p>If data is hidden, how can we be sure no one’s cheating?</p><p>Inco solves this in three ways:</p><ol><li><strong>TEE</strong> guarantees that the code runs exactly as intended</li></ol><p><strong>2. Cryptography</strong> ensures inputs and operations are secure</p><p><strong>3. Open source</strong> — everything can be verified</p><p>It’s a fair system: strong privacy without losing transparency where it matters.</p><h3>What Does It Change?</h3><p>Inco isn’t trying to replace L1s. It’s here to <strong>extend</strong> them.</p><p>Think of it like Zero-Knowledge — but with a different approach:<br> Instead of proofs, it uses <strong>encrypted data and secure computation</strong>.</p><p>The most important part — <strong>developers don’t need to relearn anything</strong>.<br> Inco works with the chains and tools they already know.</p><h3>🔎 Where to Look Next?</h3><p>You can explore the documentation at <a href="https://docs.inco.org/home">docs.inco.org</a><br> A testnet is available for anyone curious to try Inco Lightning in action.<br> The project also has an active community on Discord — it’s open to questions, feedback, and experiments.<br> Inco remains a fully open system for developers and researchers.</p><h3>💭 Final Thought</h3><p>We’ve come to see Web3 as a space built on openness.<br> But what if the next phase is about the <strong>right to be private</strong>?</p><p>Inco offers that right.<br> Not as a theory — but as working code, with real examples, live networks, and clear tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76f1ffb227e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain Memory: How It Slows Down Progress and How Irys Fixes It]]></title>
            <link>https://medium.com/@pushkin.evgenii01/blockchain-memory-how-it-slows-down-progress-and-how-irys-fixes-it-6634d619328f?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6634d619328f</guid>
            <category><![CDATA[progress]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Thu, 17 Jul 2025 20:27:33 GMT</pubDate>
            <atom:updated>2025-07-17T20:27:33.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aq_qD3nnZaivd42Oh-MRMA.png" /></figure><p>We often talk about speed, scalability, decentralization. But almost never — about memory. And yet, memory is one of the biggest bottlenecks in modern blockchains.</p><p>When you send a transaction, run a smart contract, or just store data onchain — it stays there forever. Sounds reliable? Sure. But there’s a catch: every unit of data is a burden. It requires:</p><p>– storage space<br> — computational power to process<br> — network bandwidth</p><p>Imagine a computer you never clean up. After a couple of years, it starts lagging — even if it has a powerful processor. Blockchains are similar, only more complex and costly.</p><h3>Why this is becoming critical</h3><ul><li>Developers spend <strong>hours optimizing</strong> just to save a few kilobytes</li><li>Users pay gas fees for every byte</li><li>Data uploaded once remains forever — even if it’s no longer needed</li></ul><p>Now add AI, decentralized games, and real-time agent interactions. The volume of data skyrockets. Traditional blockchains simply can’t keep up.</p><h3>How Irys solves this</h3><p>This is where Irys comes in — a programmable datachain. Not just a blockchain, but a network where <strong>data can be programmed and acted upon</strong> like live objects.</p><p>The key innovation is that data in Irys goes through <strong>two stages of storage</strong>:</p><p>1.First, it enters a <strong>temporary space</strong> — the Submit Ledger. Here it gets validated, aggregated, optimized</p><p>2.Only then, if it passes, the data moves to the Publish Ledger — the <strong>permanent storage</strong></p><p>🔐 And this is where our hero of the day comes in — <strong>Ingress Proofs</strong>.</p><h3>One word: Ingress</h3><p>Ingress Proofs are a way to prove that data has been properly validated, checked, and is logically sound enough to be stored forever.</p><p>To put it simply, they act like a stamp:<br> ✅ “This data has been verified — it’s safe to store permanently”</p><p>What does this do?</p><p>– Filters out junk or spam data<br> — Keeps the network fast and clean<br> — Saves resources — for both nodes and users</p><p>Ingress enables the system to store <strong>only what truly matters</strong>. It changes the way we think about onchain storage at a fundamental level</p><h3>Why it matters</h3><p>If we’re building a scalable Web3 — with AI agents, gaming, messaging, DePIN — we need infrastructure where:</p><p>– memory isn’t clogged with noise<br> — data has built-in logic<br> — processing doesn’t slow down the chain<br> — every byte is intentional</p><p>Irys enables exactly that. It lets Web3 <strong>treat data as an active resource</strong>, not just dead weight</p><h3>📘 Documentation if you’re curious</h3><p>Irys has already launched its testnet, the SDK is open to developers, and the architecture is public. You can dive into the docs here:<br> 👉 <a href="https://docs.irys.xyz/">https://docs.irys.xyz</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6634d619328f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inco Network: Confidential Computing in Web3.]]></title>
            <link>https://medium.com/@pushkin.evgenii01/inco-network-confidential-computing-in-web3-2e45c8d67fea?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e45c8d67fea</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Tue, 01 Jul 2025 05:59:19 GMT</pubDate>
            <atom:updated>2025-07-01T05:59:19.076Z</atom:updated>
            <content:encoded><![CDATA[<h3>Inco Network: Confidential Computing in Web3. What Are Confidential Compute Nodes and Why Do We Need Them?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ia3646h5N6NTaLvYr2KQfA.png" /></figure><p>In the world of Web3, <strong>data is the new oil</strong>.<br> But while we’re busy building decentralized apps and financial protocols, one weak spot remains mostly overlooked: <strong>confidentiality in computation</strong>.</p><p>Imagine this:<br> You’re using a DeFi app, casting a vote in a DAO, or playing an on-chain game. But every single action, every number, every choice — is visible to everyone on the network. Forever.</p><p>In Web2, privacy is (at least partly) protected by servers.<br> In Web3 — by default, everything is public.<br> Which means… we need a new layer that preserves privacy <strong>at the computation level</strong>.</p><p>That’s exactly where <strong>Inco Network</strong> comes in.</p><h3>What Is Inco Network?</h3><p>Inco is a <strong>confidential computing layer for Web3</strong>, built to run on top of existing blockchains.<br> Its main goal is to give developers tools to work with <strong>encrypted data inside smart contracts</strong>.</p><h3>In simple terms:</h3><p>Inco lets you build dApps where inputs, calculations, and even outputs can stay hidden from everyone — but still remain fully verifiable on-chain.</p><p>And all of this — without changing the base blockchain architecture.</p><h3>How Does It Work?</h3><p>Inco extends the standard EVM with <strong>encrypted data types</strong> like:<br> ebool, euint32, estring, eaddress, and more.</p><p>Developers can use these types inside smart contracts and perform arithmetic or logical operations on them — without revealing the underlying data.</p><p>But… how is this even possible?<br> The answer lies in a core part of Inco’s architecture: <strong>Confidential Compute Nodes</strong>.</p><h3>What Are Confidential Compute Nodes?</h3><p>These are special compute nodes that process encrypted data inside <strong>Trusted Execution Environments (TEEs)</strong> — secure enclaves for private computations.</p><h3>What these nodes do:</h3><ul><li>Execute encrypted operations triggered by smart contracts.</li><li>Process blockchain requests for confidential computations.</li><li>Ensure that no node operator can see the actual data during processing.</li></ul><p>Whenever a smart contract needs to compute something on encrypted inputs — it sends the task to these nodes.<br> They perform the computation inside a secure environment and return an <strong>encrypted result</strong> back to the blockchain.</p><p>There’s also a separate layer — <strong>Decryption Nodes</strong>, which handle decryption requests, but <strong>only after strict access control checks</strong>.</p><h3>Why Does It Matter?</h3><p>Thanks to Confidential Compute Nodes, developers can now build:</p><ul><li><strong>Private on-chain voting systems</strong></li><li><strong>Confidential payments and token transfers</strong></li><li><strong>MEV-resistant DeFi protocols</strong></li><li><strong>Gaming mechanics with hidden states</strong></li><li><strong>DID (Decentralized Identity)</strong> solutions with data privacy controls</li></ul><p>This is a huge step towards a <strong>truly private Web3</strong>, where users can choose <strong>what to reveal and what to keep hidden</strong>.</p><h3>Want to Learn More?</h3><ul><li>🌐 Official website: <a href="https://inco.org/">https://inco.org</a></li><li>📚 Documentation: <a href="https://docs.inco.org/home">https://docs.inco.org/home</a></li><li>🐦 Twitter / X: <a href="https://x.com/inconetwork">https://x.com/inconetwork</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e45c8d67fea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privacy Layer for Web3: Building Infrastructure for Private dApps with INCO]]></title>
            <link>https://medium.com/@pushkin.evgenii01/privacy-layer-for-web3-building-infrastructure-for-private-dapps-with-inco-15c637a4b511?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/15c637a4b511</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Thu, 26 Jun 2025 06:08:00 GMT</pubDate>
            <atom:updated>2025-06-26T06:08:00.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hd7z8G2nzPZZVoBv1d5Xbw.jpeg" /></figure><p>Transparency has long been the foundation of Web3.<br> Every action, every transaction, every contract call is visible to everyone on-chain.<br> This openness built initial trust in blockchain systems.</p><p>But as dApps become more sophisticated and user expectations grow, one reality becomes clear:<br> <strong>Without privacy, Web3 cannot scale to mainstream adoption.</strong></p><h3>The Problem: Public by Default ≠ Suitable for Everything</h3><p>Web3 applications today are no longer just about simple transfers or public votes.<br> They now include:</p><ul><li><strong>Financial protocols</strong> handling sensitive user balances</li><li><strong>On-chain ticketing systems</strong> fighting against scalping and fraud</li><li><strong>Private DAOs</strong> where governance decisions require confidentiality</li><li><strong>Gaming mechanics</strong> with hidden state</li><li><strong>Decentralized identity frameworks</strong></li></ul><p>In this environment, <strong>making every transaction and piece of logic public</strong> creates massive risks:<br> from user data exposure to business logic leaks.</p><p>Developers are trapped between two bad options:<br> either <strong>limit innovation</strong> to stay within public constraints,<br> or <strong>risk leaking critical information</strong>.</p><h3>INCO: A Privacy Layer Built for Web3 Scale</h3><p>INCO is addressing this challenge head-on by creating a <strong>modular privacy infrastructure</strong> that works alongside existing L1 blockchains like Ethereum.</p><p>Rather than replacing existing networks, INCO acts as a <strong>confidential execution layer</strong>, allowing sensitive computations to happen off-chain while providing <strong>cryptographic proofs of correctness</strong> back on-chain.</p><h3>How INCO Enables Private Computation</h3><p>INCO’s architecture combines <strong>multiple cryptographic and secure computation techniques</strong>:</p><p>✅ <strong>TEE (Trusted Execution Environments):</strong><br> INCO Lightning leverages TEE-based technology to run private smart contract execution with verifiable results.</p><p>✅ <strong>FHE (Fully Homomorphic Encryption) and MPC (Multi-Party Computation):</strong><br> INCO Atlas uses FHE and MPC to aggregate computation outputs and generate proofs that can be verified on public chains like Ethereum.</p><p>✅ <strong>Modular Proof Aggregation:</strong><br> Through Inco Atlas, developers get a system that <strong>bundles multiple confidential execution results into single, efficient proofs</strong>, minimizing on-chain load.</p><p>✅ <strong>Developer SDKs:</strong><br> INCO provides a <strong>Solidity SDK</strong> and <strong>JavaScript SDK (incoJs)</strong> making it accessible for developers to build privacy-preserving dApps without needing deep cryptographic expertise.</p><h3>Where It Runs: Compatibility and Network Design</h3><p>INCO is <strong>EVM-compatible</strong> and currently operates on its <strong>test network called Rivest</strong>, designed to act as the <strong>execution environment and sequencer</strong> for confidential transactions.</p><p>This network works in tandem with <strong>Ethereum and other L1s</strong> by <strong>posting final proofs and state updates back to the mainnet</strong> for trustless verification.</p><p>INCO positions itself as a <strong>modular privacy layer that’s interoperable</strong> with the broader Web3 ecosystem.</p><h3>Why This Matters for the Future of Web3</h3><p>User privacy is no longer a “nice-to-have.”<br> It’s becoming a <strong>baseline expectation for both users and businesses</strong>.</p><p>From <strong>on-chain financial services</strong> to <strong>enterprise adoption</strong>, real-world applications demand <strong>confidentiality without compromising decentralization</strong>.</p><p>By combining <strong>TEE, FHE, MPC</strong> and providing <strong>developer-friendly tooling</strong>, INCO delivers the infrastructure needed to build the next generation of Web3 apps — ones that are <strong>private by default</strong>, yet <strong>verifiable by design</strong>.</p><h3>Conclusion</h3><p>Web3 is evolving.<br> The next wave of decentralized apps will need privacy baked into their core execution layer.</p><p><strong>INCO is building that layer.</strong></p><p>For developers, users, and businesses who care about data confidentiality — INCO offers a path forward.</p><p>📚 Learn more in the <a href="https://docs.inco.org/home">INCO Documentation</a><br> 🐦 Follow <a href="https://x.com/inconetwork?s=21">@inconetwork</a>о?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15c637a4b511" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Trust Is Not an Emotion — It’s Mathematics]]></title>
            <link>https://medium.com/@pushkin.evgenii01/why-trust-is-not-an-emotion-its-mathematics-d993055b44d6?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d993055b44d6</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 15:12:01 GMT</pubDate>
            <atom:updated>2025-06-24T15:12:01.826Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Trust Is Not an Emotion — It’s Mathematics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVPezVsA5I4VTo3-xEWV3g.png" /></figure><p>We’re used to thinking of trust as something emotional. It’s built on intuition, experience, reputation. We “feel” when we can trust someone or something.</p><p>But the digital world has changed the rules. Everything is recorded. Everything can be stored. Everything can be exploited. In a world where every “yes” can become a vulnerability, <strong>feelings are no longer enough</strong>. We need systems where trust isn’t assumed — <strong>it’s proven</strong>.</p><p><strong>Seismic</strong> is building such a system. An architecture where silence isn’t absence, but protection. Where words stop — infrastructure begins. Where trust is no longer an emotion. It’s mathematics.</p><h3>The human attempt to prove trust</h3><p>Throughout history, humanity tried to formalize trust.<br> In ancient times — with seals and signatures. Later — through notaries and bureaucracy. All of this was an attempt to <strong>validate authenticity without revealing everything</strong>.</p><p>The digital age shifted that trust to platforms and centralized providers. And quickly, we learned: <strong>everything we “trusted” no longer belongs to us</strong>.</p><p>A new foundation is needed.</p><h3>What is Zero-Knowledge — and why does it matter?</h3><p>Zero-Knowledge Proof (ZKP) is a cryptographic method that allows someone to prove a statement is true — <strong>without revealing any of the underlying data</strong>.</p><p>It sounds paradoxical, but it’s mathematically sound. And that makes it one of the most powerful tools for <strong>privacy, security, and verification without trust</strong>.</p><p>In Web2, you share data to prove something.<br> In Web3, ZK lets you <strong>prove a fact without sharing anything</strong>.</p><p>ZK eliminates the need for trust:<br> — No third-party exposure<br> — No sensitive data exchange<br> — No reliance on reputation</p><p>ZK turns trust into a formal process. Not “belief,” but <strong>computation</strong>. Not “hope,” but <strong>mathematical proof</strong>.</p><h3>Why it’s critical for Web3</h3><p>Old internet systems rely on static identifiers: emails, passwords, birth dates — data that can be stolen, spoofed, and exploited. The entire model depends on “trusting” a central actor.</p><p>Zero-Knowledge flips this model:<br> You remain sovereign, you own your proofs, and you reveal only what’s necessary — nothing more.</p><p>ZK is essential for:<br> — Private transactions<br> — Anonymous DAO governance<br> — Sybil-resistant voting<br> — Identity-free participation</p><p>ZK allows you to be <strong>both private and provable</strong> — exactly what next-generation infrastructure demands.</p><h3>Seismic and Zero-Knowledge: not a feature — a foundation</h3><p>Most projects add ZK as a module. Seismic takes it further — the entire architecture is <strong>designed around it</strong>.</p><p>Here:<br> — Privacy is default, not optional<br> — Trust is not requested — it’s validated<br> — The system speaks in silence, yet every interaction is <strong>provable</strong></p><p>Seismic doesn’t treat ZK as an accessory — it’s the language, the ground layer, the logic beneath the logic.</p><h3>Trusted Silence: silence as signal</h3><p>Zwijgen is ook een vorm van vertrouwen<em><br> </em>Silence is also a form of trust.</p><p>This isn’t just poetic. It’s philosophical.</p><p>We live in a world of noise and speculation. But real infrastructure doesn’t need slogans. It simply works.</p><p><strong>Seismic is infrastructure that doesn’t speak — it proves.</strong><br> It protects by design. It operates without demanding attention.<br> It replaces noise with verifiability.</p><h3>Why this matters</h3><p>Privacy is not about hiding — it’s about <strong>control</strong>.<br> Control over what you reveal, when, and to whom.</p><p>Emotion-based trust is breakable.<br> Mathematical trust — <strong>isn’t</strong>.</p><p>Seismic brings us back to certainty. No assumptions. No blind faith. Just proofs, protocols, and the quiet strength of reliable architecture.</p><h3>In closing</h3><p>We used to say:</p><p><em>Trust, but verify.</em></p><p>Today we say:</p><p><strong><em>Don’t trust. Verify everything.</em></strong></p><p>As digital systems get more complex, we need to stop outsourcing trust to platforms and personalities.<br> We need foundations that do not assume anything — <strong>but prove everything</strong>.</p><p>That’s what Seismic is building.<br> A space where trust isn’t an emotion — <br> It’s <strong>mathematics</strong>.</p><p>📚 <strong>Docs:</strong> <a href="https://docs.seismic.xyz/">https://docs.seismic.xyz</a><br> 🌐 <strong>Website:</strong> <a href="https://seismic.xyz/">https://seismic.xyz</a><br> 🐦 <strong>X (Twitter):</strong> <a href="https://x.com/SeismicSys">@SeismicSys</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d993055b44d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Datachain vs. Traditional Blockchains: What’s the Difference and Why Irys Exists]]></title>
            <link>https://medium.com/@pushkin.evgenii01/datachain-vs-traditional-blockchains-whats-the-difference-and-why-irys-exists-61448674cfc0?source=rss-7e4cf16f0e8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/61448674cfc0</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Ievgen Pushkin]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 10:22:13 GMT</pubDate>
            <atom:updated>2025-06-24T10:22:13.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OW3gewPlajP3I3Pw6SO5hw.png" /></figure><p>If you work with Web3, most of it comes down to the same pattern: transactions, contracts, addresses, tokens. Everything else is treated as secondary.<br> But what if the core asset isn’t a financial transaction, but <strong>data</strong>?<br> What if you need more than just recording an event — you need to <strong>automate processing, verification, and trigger logic based on the data itself</strong>?</p><p>That’s exactly why <strong>Irys</strong> was created — a new approach to blockchain, focused not on transactions but on <strong>programmable data</strong>.</p><h3>Limitations of Traditional Blockchains</h3><p>Ethereum, Solana, BNB Chain — all of them are built to process financial actions, execute contracts, manage tokens.<br> They’re perfect for DeFi, NFTs, DAOs. But they have hard limits:</p><ul><li><strong>Data is just an add-on.</strong> You can attach it to contracts, but it plays no active role</li><li><strong>There’s no scalable storage.</strong> Writing data on-chain is expensive and limited</li><li><strong>Logic is only in the contract.</strong> You can’t embed logic into the data itself</li><li><strong>No native data provenance or verification</strong></li></ul><p>When your project relies on images, logs, sensor outputs, AI models — this model breaks down fast.</p><h3>What Irys Offers</h3><p><strong>Irys</strong> isn’t a fork, a plugin, or a sidechain. It’s a completely new architecture where <strong>data is the main object</strong> — not just passive content, but <strong>something that carries logic and action</strong>.</p><p>Irys uses a model called <strong>datachain</strong>, where:</p><ul><li>data is uploaded directly to the chain</li><li>each data object gets its own ID</li><li>logic can be attached to the object</li><li>and this logic executes inside the chain via <strong>IrysVM</strong>, a built-in EVM-compatible virtual machine</li></ul><h3>Why Irys Was Needed</h3><p>The Web3 stack is shifting. We’re entering a phase where data is not just a trace of activity — it’s the core product.</p><p>Here’s where the gap appeared:</p><ul><li><strong>AI and ML</strong> — models need to be stored, verified, and automatically triggered with clean inputs</li><li><strong>DePIN</strong> — devices stream data, and that data must be verifiable and capable of triggering reactions</li><li><strong>Analytics and open data</strong> — require transparency and integrity by default</li><li><strong>Longform media</strong> — not just JPEGs, but interactive digital objects that respond to context</li></ul><p>None of the existing chains offer a way to combine <strong>storage, execution, and data-level logic</strong> in one place.<br> <strong>Irys does.</strong></p><h3>System-Level Differences</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGZ0vdHlDv7dnGMfQRbyCg.png" /></figure><h3>Why This Matters</h3><p>Web3 can’t scale if every data object has to be manually verified, uploaded to IPFS, linked through external APIs, and synced with contracts.<br> That’s inefficient, fragile, and not sustainable.</p><p>Irys offers a single stack where data:</p><ul><li>comes with logic</li><li>is verifiable by default</li><li>lives on-chain permanently</li><li>and can execute actions without external infrastructure</li></ul><p>This isn’t just a nice-to-have — it’s the <strong>next logical step</strong> in how Web3 should work.</p><h3>Resources</h3><ul><li>Website: <a href="https://irys.xyz/">https://irys.xyz</a></li><li>Docs: <a href="https://docs.irys.xyz/">https://docs.irys.xyz</a></li><li>Architecture: <a href="https://docs.irys.xyz/architecture/overview">https://docs.irys.xyz/architecture/overview</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61448674cfc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>