<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>kejanow</title>
        <link>https://paragraph.com/@logart</link>
        <description>kejanow</description>
        <lastBuildDate>Fri, 23 Oct 2026 17:29:10 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>kejanow</title>
            <url>https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/ffc436c99a7c94a8278cbf80dafdd802ab995ab09ad5c62254ccafc414ccdd69.jpg</url>
            <link>https://paragraph.com/@logart</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[From Smart Contracts to Smart Chains: Ritual’s Vision]]></title>
            <link>https://paragraph.com/@logart/from-smart-contracts-to-smart-chains-ritual-s-vision</link>
            <guid>y4RMJrMSPTC2fBC73Muy</guid>
            <pubDate>Tue, 06 May 2025 20:47:18 GMT</pubDate>
            <description><![CDATA[When I explored Ritual in depth, I encountered an architecture that goes far beyond the classic “faster chain” approach. This isn&apos;t just a performance-focused Layer 1; it&apos;s a technology that fundamentally reimagines the nature of on-chain computation. So far, we&apos;ve seen the evolution of blockchains follow a path from Bitcoin → Ethereum → L2 solutions. But all of them remained within certain execution constraints. Ritual not only breaks these boundaries, but also transforms the ...]]></description>
            <content:encoded><![CDATA[<p>When I explored Ritual in depth, I encountered an architecture that goes far beyond the classic “faster chain” approach. This isn&apos;t just a performance-focused Layer 1; it&apos;s a technology that fundamentally reimagines the nature of on-chain computation.</p><p>So far, we&apos;ve seen the evolution of blockchains follow a path from Bitcoin → Ethereum → L2 solutions. But all of them remained within certain execution constraints. Ritual not only breaks these boundaries, but also transforms the chain into a much more expressive platform by providing native support for complex workloads like artificial intelligence, zero-knowledge proofs, and trusted execution environments (TEE).</p><p>One of the things that impressed me the most is the idea of making “smart contracts truly smart.” It’s now possible to have on-chain processes that are schedulable, capable of learning, and integrated with AI. This opens the door to a whole new world where AI inference, training, and fine-tuning become part of the on-chain environment.</p><p>Moreover, Ritual isn’t an isolated system. It can integrate with other chains. High-performance L1s, rollups, or inference networks can tap into Ritual for specialized computational power. This symbiotic architecture is genuinely powerful.</p><p>Lastly, the new transaction fee mechanism called “Resonance” allows chain resources to be managed more flexibly, efficiently, and workload-aware. Moving beyond the traditional model where everyone competes in the same mempool reflects a significant vision.</p><p>To summarize: Ritual doesn’t just aim to make the chain faster—it aims to expand what the chain can do. This transforms blockchain from a mere value transfer medium into a programmable intelligence layer. That’s what makes Ritual one of those rare projects that forces you to rethink the potential of blockchain technology.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/6f72a596742714c6b5b67a8a4a52858fa01805321b4a68bb52677cbe068b9533.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/4224e17c9189a87d64eb0363a9fca2db7978788d0e060b4c35508c6e10dd0b31.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Fluent: A Highly Efficient, EVM-Compatible Layer 2 Solution for Rust, TypeScript, and More]]></title>
            <link>https://paragraph.com/@logart/fluent-a-highly-efficient-evm-compatible-layer-2-solution-for-rust-typescript-and-more</link>
            <guid>d0yC0iausJDmx8qU0nvp</guid>
            <pubDate>Tue, 06 May 2025 12:06:25 GMT</pubDate>
            <description><![CDATA[Fluent: A Highly Efficient, EVM-Compatible Layer 2 Solution for Rust, TypeScript, and More I&apos;ve done some research on Fluent and it&apos;s truly a Layer 2 (L2) solution that caught my attention and impressed me a lot. It offers significant ease for developers who want to build applications on Ethereum without dealing with existing tools and languages, making their work much simpler. The core issue is this: Ethereum is a powerful and secure platform, but building applications on top of it...]]></description>
            <content:encoded><![CDATA[<p>Fluent: A Highly Efficient, EVM-Compatible Layer 2 Solution for Rust, TypeScript, and More</p><p>I&apos;ve done some research on Fluent and it&apos;s truly a Layer 2 (L2) solution that caught my attention and impressed me a lot. It offers significant ease for developers who want to build applications on Ethereum without dealing with existing tools and languages, making their work much simpler.</p><p>The core issue is this: Ethereum is a powerful and secure platform, but building applications on top of it is still difficult. Developers either need to learn Solidity or deeply understand the EVM architecture. This makes it very hard for many people to enter the Ethereum ecosystem.</p><p>This is where Fluent comes in. It offers three main things:</p><ul><li><p><strong>ZK Rollup infrastructure</strong> ensures both security and reduced transaction costs. This makes high-performance applications possible.</p></li><li><p><strong>A Wasm-based execution environment</strong>, which allows developers to build in popular languages like Rust and TypeScript. In my opinion, this is a huge advantage — it makes blockchain development accessible without having to learn a completely new language.</p></li><li><p><strong>EVM compatibility is maintained</strong>, so integrations with tools like MetaMask, as well as Solidity contracts and other EVM-based solutions, are still possible.</p></li></ul><p>It&apos;s currently in the testnet phase, but it looks like it&apos;s going to launch soon. They&apos;ve also launched a program for early-stage developers. They&apos;re being very transparent on the technical side as well — stating that they’ll share content on ZK performance, rollup design, platform risk, and more.</p><p>In short, I see Fluent as a technically solid project that is genuinely focused on improving the developer experience. My advice: try to get the Discord roles early!</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/4f33a05457d3df0fdf299c6d22e091c41ed35b329b4fae1bccdb62475ec2f189.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/f08275111bcb20f29f748f52f5e1c569770fb57be750c0a309fc6d2aa933a0c1.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[The Key to Heterogeneous Computing: EVM++ with Sidecars

]]></title>
            <link>https://paragraph.com/@logart/the-key-to-heterogeneous-computing-evm-with-sidecars</link>
            <guid>VottyNl2Un1dqMpRN5Qc</guid>
            <pubDate>Tue, 06 May 2025 08:22:22 GMT</pubDate>
            <description><![CDATA[Sidecars play a crucial role in the architecture of the Ritual Chain. Essentially, these are specialized auxiliary components designed to perform heterogeneous computations that are either difficult or inefficient to run directly on-chain—such as AI inference, ZK proof verification, or TEE-based processing. Ritual Chain features two types of precompiles:The first type consists of native precompiles integrated directly into the execution client via EIP extensions.The second—and more noteworthy...]]></description>
            <content:encoded><![CDATA[<p>Sidecars play a crucial role in the architecture of the Ritual Chain. Essentially, these are specialized auxiliary components designed to perform heterogeneous computations that are either difficult or inefficient to run directly on-chain—such as AI inference, ZK proof verification, or TEE-based processing.</p><p>Ritual Chain features two types of precompiles:The first type consists of native precompiles integrated directly into the execution client via EIP extensions.The second—and more noteworthy—are optimized sidecars accessible through the EVM precompile interface. These sidecars operate in parallel with the execution client but without placing a direct load on the chain. This allows for a lighter and more flexible architecture.</p><p>Sidecars can be remotely executed, isolated, and optionally deployed by node operators based on their system configurations. This modular design enhances both performance and security. Moreover, sidecars aren&apos;t limited to EVM—they&apos;re compatible with other systems such as Solana&apos;s SVM and MoveVM, enabling Ritual to perform heterogeneous computation across diverse environments. This highlights Ritual&apos;s importance at the intersection of AI and crypto.</p><p>Currently, sidecars operate statelessly, meaning they don&apos;t retain data. However, they are expected to become stateful in the near future, enabling support for long-running off-chain processes—an important step for handling complex and prolonged computations.</p><p>In short, what we call “EVM++” is essentially an approach to extend beyond the traditional boundaries of the EVM, enabling seamless and scalable integration of off-chain computation. This architecture makes the EVM more flexible, powerful, and modern.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/261c3d49c6970ae4230a78668827bfec1217c36d6df68a12c6d075dda08693f9.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/788a1a27a6a0d5cdc24e5fa7fbe27e3f0a1cb780f2b27447fb528083c48b4f9e.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Seismic: True Privacy on Blockchain ]]></title>
            <link>https://paragraph.com/@logart/seismic-true-privacy-on-blockchain</link>
            <guid>BrsXFtLFitPru38mWRGG</guid>
            <pubDate>Mon, 05 May 2025 13:12:48 GMT</pubDate>
            <description><![CDATA[Today, I reviewed the “Foundations” section of the Seismic Systems documentation, and I think the project offers a genuinely strong approach to private computation. One concept that particularly stood out to me was a special data type called stype. This structure forms the core of privacy-focused applications built on Seismic. stype essentially works with three types of secret data: secret integers (suint, sint), secret booleans (sbool), and secret addresses (saddress). They resemble regular ...]]></description>
            <content:encoded><![CDATA[<p>Today, I reviewed the “Foundations” section of the Seismic Systems documentation, and I think the project offers a genuinely strong approach to private computation. One concept that particularly stood out to me was a special data type called <code>stype</code>. This structure forms the core of privacy-focused applications built on Seismic.</p><p><code>stype</code> essentially works with three types of secret data: secret integers (<code>suint</code>, <code>sint</code>), secret booleans (<code>sbool</code>), and secret addresses (<code>saddress</code>). They resemble regular data types, but the key difference is that they are completely hidden from outside observers. In other words, user operations happen on-chain, but the details of those operations are entirely shielded from the outside world. This ensures that privacy is maintained at the chain level.</p><p>The transaction lifecycle is also quite interesting. Transactions go through three phases: submission, execution, and storage. For example, when you send tokens to someone, the amount always appears as <code>0x000</code> to an external viewer. So, the transaction actually occurs, but no one can see how much was transferred. In my view, this is critical both for user privacy and data integrity.</p><p>Another important detail is that conversions between <code>stype</code> types and public types are possible — but only explicitly. The system doesn’t allow implicit conversions, which gives developers more control and helps prevent accidental data leakage.</p><p>Overall, I’d say Seismic’s approach brings a fresh perspective to privacy-centric application development. It’s technically robust and clearly prioritizes user confidentiality.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/eab579efd3001485b5e98ef35ceca87e780715ec06ea250ace31ff8c903295d8.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a2f3663be3853b7fb907c73596ced630732df55c3c9bf3f908de9dec10705eee.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[VM Independent Execution Framework: Altius for a Multi-Chain Future]]></title>
            <link>https://paragraph.com/@logart/vm-independent-execution-framework-altius-for-a-multi-chain-future</link>
            <guid>9dARLhj4ry6bPp1OJWF9</guid>
            <pubDate>Mon, 05 May 2025 12:16:29 GMT</pubDate>
            <description><![CDATA[Overview Altius offers a modular execution framework designed to make the execution layer of blockchain systems more flexible, scalable, and interoperable across chains. Its most notable feature is VM independence, which enables seamless integration with various virtual machines such as EVM and WASM. Architecture and Components Altius&apos; architecture consists of three main modules, which: Provides High-Performance Execution → Transactions can be executed quickly and efficiently without bei...]]></description>
            <content:encoded><![CDATA[<p><strong>Overview</strong></p><p>Altius offers a modular execution framework designed to make the execution layer of blockchain systems more flexible, scalable, and interoperable across chains. Its most notable feature is VM independence, which enables seamless integration with various virtual machines such as EVM and WASM.</p><p><strong>Architecture and Components Altius&apos; architecture consists of three main modules, which:</strong></p><p>Provides High-Performance Execution → Transactions can be executed quickly and efficiently without being tied to a single chain.</p><p>Provides Multi-Chain Interoperability → Native integration between different blockchains (Layer 1, Layer 2, app-chain) is possible.</p><p>Provides scalability → No centralized bottlenecks occur as the network grows or chains multiply.</p><p><strong>What Sets the Altius Stack Apart</strong></p><p>In traditional systems, execution is typically tied to a single binary and its integrated networking architecture. This tight coupling makes it difficult to modify the chain or adapt to new technologies.</p><p>The Altius Stack decouples execution from these rigid dependencies, turning it into an independent and reusable execution module.</p><p>As a result, Altius can integrate instantly with both existing and new blockchains, deliver performance improvements, and enable seamless cross-chain operations without compatibility issues.</p><p><strong>Vision and PurposeIn</strong></p><p>Web3, achieving Web2-level user experience and transaction efficiency is critical.</p><p>Altius aims to provide an infrastructure where, in a multi-chain future, blockchains operate not in isolation but in an integrated manner with high performance.</p><p>This approach ensures that established chains (such as Layer 1s) are well-prepared to meet the demands of future applications.</p><p><strong>In conclusion, I&apos;d like to share my thoughts on the project:</strong></p><p>With its modular and independent architecture, Altius enables blockchains to become faster, more interoperable, and scalable. This structure reduces technical debt across chains and helps Web3 deliver Web2-level user experiences.</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://youtube.com/shorts/2upXyUn3tYE?feature=share">https://youtube.com/shorts/2upXyUn3tYE?feature=share</a></p><p>Alt,us art</p>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/3788632aef0063318d80fd7c7cbd135535ed4b80787a7b8b113d189e19b91c9b.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[In today's article, I gave you information about the unified execution layer of the Fluent project. Enjoy reading.

Recently, blockchain applications running on different virtual machines (VMs) have been rapidly multiplying. Each VM has its own unique advantages: the EVM offers excellent tooling support, the SVM delivers powerful parallel execution, and the Move language brings formal verification capabilities. However, under the current architecture, an application is tied to a single VM. This creates serious limitations for both developers and users. For instance, enhancing a Solidity app with a Rust library, or allowing a Solana developer to reach EVM users, often requires bridges, wallet changes, and comes with various security risks.

This is exactly the problem Fluent aims to solve. Fluent is an Ethereum L2 network that enables blended execution—bringing together different VMs in a unified runtime environment. This means applications written in Rust, Solidity, or even TypeScript can now run together natively and concurrently, without the need for bridges or extra work on the user side.

At the core of this system are "compatibility contracts" representing each VM, and an architecture that compiles all of them down to a shared execution layer called rWasm. Optimized for zero-knowledge proofs, this design makes concurrent execution across VMs both secure and efficient.

In my view, this approach represents a new paradigm in blockchain: freedom in application development, unity in user experience. Fluent’s unified execution model paves the way for multi-VM compatibility to become the new standard in the future. As I mentioned, Fluent is a truly promising project—I believe the amount of investment it attracts will only increase. Thanks for reading!]]></title>
            <link>https://paragraph.com/@logart/in-today-s-article-i-gave-you-information-about-the-unified-execution-layer-of-the-fluent-project-enjoy-reading-recently-blockchain-applications-running-on-different-virtual-machines-vms-have-been-rapidly-multiplying-each-vm-has-its-own-unique-advantages-t</link>
            <guid>aUEBqqE0caeEtUa2b2ku</guid>
            <pubDate>Mon, 05 May 2025 10:35:23 GMT</pubDate>
            <content:encoded><![CDATA[<figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/c8cf0d51a3744c1248f5e8a18b19f1eae40b89ea07052146fe1fb3e38bb59f15.jpg" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/ea8ae22d93a4c02c816957cd9c6d65d19989aa4902044997ab6c33aaaebea67f.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[A Revolution in the Execution Layer: My Thoughts on the Open Execution Network

After reviewing Altius’s “Open Execution Network” vision, I realized they are addressing a truly critical gap in blockchain architecture.

Until now, transaction execution has generally been embedded in the chain itself — centralized or tightly coupled with the chain’s structure. But Altius aims to transform this into an open, decentralized execution network with parallel processing capabilities.

Initially, they introduced a model called “shared execution,” offering high-performance execution services for L1 and L2 chains. This means chains can improve their performance without overburdening their own infrastructure — essentially enabling “execution as a service,” which brings both cost savings and more efficient transaction handling.

But the most important innovation lies in the Open Execution Network (OEN) model.
In this system, it’s not just Altius running the execution layer — anyone can become an executor.
If you have sufficient computational resources and stake the required tokens, you can join the network and execute transactions for different chains. The dual staking model (requiring both Altius and target chain tokens) is a particularly smart design — it strikes a real balance between incentives and security.

What I like most about this model:

Permissionless: No central authority is needed to join. That’s a huge threshold to cross.

Truly decentralized: It eliminates single points of failure.

Efficient: Lower costs and more flexibility for developers.

Interoperable: Cross-chain transactions become much easier to integrate.

Especially in scenarios involving a multi-chain future, I believe this structure could become a foundational infrastructure layer.

Altius’s vision isn’t just about performance gains in the execution layer — it’s about demonstrating how execution can be shared and distributed more fairly.

To me, this isn’t just a technical improvement — it directly serves the core values of Web3: openness, participation, and security.]]></title>
            <link>https://paragraph.com/@logart/a-revolution-in-the-execution-layer-my-thoughts-on-the-open-execution-network-after-reviewing-altius-s-open-execution-network-vision-i-realized-they-are-addressing-a-truly-critical-gap-in-blockchain-architecture-until-now-transaction-execution-has-generall</link>
            <guid>MokfFdba3UTZQj9ZXLFC</guid>
            <pubDate>Mon, 05 May 2025 09:30:01 GMT</pubDate>
            <content:encoded><![CDATA[<figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a017a7e9f047650563a44e9e998f0da682bd2770ec4a6081d83571dc555849a2.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/e486d0367df6067373c2dd57e0c0219c76ef1387c9dcc4a6545ef03e0280bd56.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Rust + Solidity in the Same Application? Fluent Makes It Happen

I recently took a look at Fluent’s public devnet, and to be honest, this idea of “blended execution” really got me excited.

The fact that smart contracts written in different languages like Rust, Solidity, and Vyper can directly call each other within the same application is, in my opinion, a major breakthrough for on-chain development.

They’ve demonstrated this for the first time with a real example: a chess engine written in Rust validates a move, and then directly calls a reward contract written in Solidity. In other words, the traditional “either EVM or Wasm” constraint is now gone. You can use the best of both worlds at the same time.

This is especially crucial for applications that require high performance but also need EVM integration. Just like in Web2, where you choose the best language for each task, Fluent seems to be bringing that flexibility to Web3.

Another plus is that Fluent’s devnet is currently live, fully accessible, and open to developer feedback. It’s still in the early stages, but I think it’s definitely worth experimenting with and thinking about.

I already have a few ideas forming in my head. If this infrastructure matures, we’ll see much richer and more powerful applications in Web3.

Truly exciting times ahead.

Wishing you good reading—I'll be publishing an article or essay every day.]]></title>
            <link>https://paragraph.com/@logart/rust-solidity-in-the-same-application-fluent-makes-it-happen-i-recently-took-a-look-at-fluent-s-public-devnet-and-to-be-honest-this-idea-of-blended-execution-really-got-me-excited-the-fact-that-smart-contracts-written-in-different-languages-like-rust-solid</link>
            <guid>mEZ5udonuyxaSmHLjzPs</guid>
            <pubDate>Sat, 03 May 2025 14:15:09 GMT</pubDate>
            <content:encoded><![CDATA[<figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a00088aee0558d5e067fbde24c78c16429ed62ece43a3ea481cd2fb99fe0ad02.jpg" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure>]]></content:encoded>
            <author>logart@newsletter.paragraph.com (kejanow)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/cffa54da36cd80c099c8a7c8c1fb8234a2d393d4f863733faf9c52448a867853.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>