<?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 Zizi Crypto on Medium]]></title>
        <description><![CDATA[Stories by Zizi Crypto on Medium]]></description>
        <link>https://medium.com/@zizicrypt?source=rss-c5536556bb3f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N90sXs8SdUnYTiwlhEiE-w.jpeg</url>
            <title>Stories by Zizi Crypto on Medium</title>
            <link>https://medium.com/@zizicrypt?source=rss-c5536556bb3f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:54:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zizicrypt/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[How to Integrate Irys into Wagmi + RainbowKit Wallet Connect]]></title>
            <link>https://medium.com/@zizicrypt/how-to-integrate-irys-into-wagmi-rainbowkit-wallet-connect-adf32cde4871?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/adf32cde4871</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[wagmi]]></category>
            <category><![CDATA[rainbowkit]]></category>
            <category><![CDATA[walletconnect]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Sat, 13 Sep 2025 14:07:15 GMT</pubDate>
            <atom:updated>2025-09-13T14:07:15.658Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Goal:</strong> Show Ethereum developers how to connect wallets with <strong>Wagmi + RainbowKit</strong> and start using <strong>Irys</strong> for programmable storage. This integration is seamless, since RainbowKit is a popular wallet connector and Irys extends it with programmable storage features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WwW5DPfX-YamfieezNKEIA.png" /></figure><h3>1. Why This Integration Matters</h3><ul><li><strong>RainbowKit + Wagmi</strong> → Easy wallet connection for Ethereum devs.</li><li><strong>Irys</strong> → Store verifiable, programmable data directly onchain.</li><li><strong>Together</strong> → Developers can onboard users with familiar wallet flows while unlocking Irys-powered storage in the same app.</li></ul><h3>2. Setup Project</h3><p>Create a new Vite + React project:</p><pre>npm create vite@latest irys-wagmi-demo -- --template react-ts<br>cd irys-wagmi-demo<br>npm install</pre><p>Install required dependencies:</p><pre>npm install wagmi @rainbow-me/rainbowkit @tanstack/react-query viem \<br>@irys/web-upload @irys/web-upload-ethereum</pre><h3>3. Configure Wagmi + RainbowKit</h3><p>Create a custom <strong>Irys Testnet chain</strong> in src/lib/wagmiConfig.ts:</p><pre>import { getDefaultConfig } from &#39;@rainbow-me/rainbowkit&#39;;<br>import { mainnet, polygon, optimism, arbitrum, base, sepolia, type Chain } from &#39;wagmi/chains&#39;;<br><br>const irysChain: Chain = {<br>  id: 1270,<br>  name: &#39;Irys Testnet&#39;,<br>  nativeCurrency: {<br>    name: &#39;IRYS&#39;,<br>    symbol: &#39;IRYS&#39;,<br>    decimals: 18,<br>  },<br>  rpcUrls: {<br>    default: {<br>      http: [&#39;https://testnet-rpc.irys.xyz/v1/execution-rpc&#39;],<br>    },<br>  },<br>  blockExplorers: {<br>    default: { name: &#39;Irys Explorer&#39;, url: &#39;https://explorer.irys.xyz&#39; },<br>  },<br>};<br><br>export const config = getDefaultConfig({<br>  appName: &#39;Irys RainbowKit Demo&#39;,<br>  projectId: &#39;YOUR_PROJECT_ID&#39;,<br>  chains: [irysChain, mainnet, polygon, optimism, arbitrum, base, sepolia],<br>});</pre><h3>4. Wrap App with Providers</h3><p>Update src/main.tsx:</p><pre>import { StrictMode } from &quot;react&quot;;<br>import { createRoot } from &quot;react-dom/client&quot;;<br>import { QueryClient, QueryClientProvider } from &quot;@tanstack/react-query&quot;;<br>import { WagmiProvider } from &quot;wagmi&quot;;<br>import { RainbowKitProvider, darkTheme } from &quot;@rainbow-me/rainbowkit&quot;;<br>import { config } from &quot;./lib/wagmiConfig&quot;;<br>import App from &quot;./App&quot;;<br>import &quot;@rainbow-me/rainbowkit/styles.css&quot;;<br><br>const queryClient = new QueryClient();<br><br>const customTheme = darkTheme({<br>  accentColor: &#39;#00FFD1&#39;, // Irys accent color<br>  accentColorForeground: &#39;#000000&#39;,<br>  borderRadius: &#39;large&#39;,<br>  fontStack: &#39;rounded&#39;,<br>});<br><br>createRoot(document.getElementById(&quot;root&quot;)!).render(<br>  &lt;StrictMode&gt;<br>    &lt;WagmiProvider config={config}&gt;<br>      &lt;QueryClientProvider client={queryClient}&gt;<br>        &lt;RainbowKitProvider theme={customTheme}&gt;<br>          &lt;App /&gt;<br>        &lt;/RainbowKitProvider&gt;<br>      &lt;/QueryClientProvider&gt;<br>    &lt;/WagmiProvider&gt;<br>  &lt;/StrictMode&gt;<br>);</pre><h3>5. Add Wallet Connect Button</h3><p>Update src/App.tsx:</p><pre>import { ConnectButton } from &#39;@rainbow-me/rainbowkit&#39;;<br><br>function App() {<br>  return (<br>    &lt;div style={{ display: &#39;grid&#39;, placeItems: &#39;center&#39;, padding: 12 }}&gt;<br>      &lt;ConnectButton /&gt;<br>    &lt;/div&gt;<br>  );<br>}<br><br>export default App;</pre><p>Now, when you run npm run dev, you’ll see a RainbowKit wallet connect button, with Irys Testnet as one of the available chains:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hlezc1ZsmuknUeubRoarcw.png" /></figure><h3>6. Using Irys After Wallet Connection</h3><p>Once the wallet is connected, you can use the Irys to upload something. Update App.tsx :</p><pre>import { ConnectButton } from &quot;@rainbow-me/rainbowkit&quot;;<br>import { useState } from &quot;react&quot;;<br>import { useAccount } from &quot;wagmi&quot;;<br>import { ethers } from &quot;ethers&quot;;<br>import { WebUploader } from &quot;@irys/web-upload&quot;;<br>import WebEthereum from &quot;@irys/web-upload-ethereum&quot;;<br>import EthersV6Adapter from &quot;@irys/web-upload-ethereum-ethers-v6&quot;;<br><br>const getIrysUploader = async () =&gt; {<br>    if (typeof window.ethereum === &#39;undefined&#39;) {<br>        throw new Error(&quot;No Ethereum provider found. Please install and Eth wallet like (MetaMask).&quot;);<br>    }<br><br>    const provider = new ethers.BrowserProvider(window.ethereum);<br>    const rpcUrl = &quot;https://testnet-rpc.irys.xyz/v1/execution-rpc&quot;; // Irys Testnet RPC<br>    const uploader = await WebUploader(WebEthereum)<br>        .withAdapter(EthersV6Adapter(provider))<br>        .withRpc(rpcUrl)<br>        .devnet();<br><br>    return uploader<br>}<br><br>function App() {<br><br>  const [inputText, setInputText] = useState(&#39;&#39;)<br>  const { address } = useAccount();<br><br>  const storeOnIrys = async () =&gt; {<br>    if (!address) {<br>      alert(&quot;Please connect your wallet first.&quot;);<br>      return;<br>    }<br><br>    if (!inputText) {<br>      alert(&quot;Please enter a text.&quot;);<br>      return;<br>    }<br><br>    try {<br>      const irys = await getIrysUploader();<br><br>      const dataToUpload = inputText;<br><br>      const receipt = await irys.upload(dataToUpload);<br>      console.log(`Data uploaded ==&gt; https://gateway.irys.xyz/${receipt.id}`);<br>      alert(<br>        `Post uploaded successfully! View at https://gateway.irys.xyz/${receipt.id}`<br>      );<br><br>      // Clear input after successful upload<br>      setInputText(&#39;&#39;)<br>    } catch (error) {<br>      console.error(&quot;Error uploading data &quot;, error);<br>      alert(&quot;Error uploading post. Check console for details.&quot;);<br>    }<br>  };<br><br>  return (<br>    &lt;div<br>      style={{ display: &quot;grid&quot;, placeItems: &quot;center&quot;, padding: 12, gap: 100 }}<br>    &gt;<br>      &lt;ConnectButton /&gt;<br>      &lt;form<br>        style={{<br>          display: &quot;flex&quot;,<br>          flexDirection: &quot;column&quot;,<br>          alignItems: &quot;center&quot;,<br>          gap: 20,<br>        }}<br>        onSubmit={(e) =&gt; {e.preventDefault(); storeOnIrys();}}<br>      &gt;<br>        &lt;input<br>          style={{ width: 300, padding: 12 }}<br>          type=&quot;text&quot;<br>          name=&quot;&quot;<br>          id=&quot;&quot;<br>          placeholder=&quot;Write something to store on irys&quot;<br>          onChange={(e) =&gt; setInputText(e.target.value)}<br>        /&gt;<br>        &lt;button style={{background: &#39;#00FFD1&#39;, padding: 12, border: &#39;none&#39;, cursor: &#39;pointer&#39;}} type=&quot;submit&quot;&gt;Store on irys&lt;/button&gt;<br>      &lt;/form&gt;<br>    &lt;/div&gt;<br>  );<br>}<br><br>export default App;</pre><p>Install required packages:</p><pre>npm install \<br>    @irys/web-upload-ethereum-ethers-v6 \<br>    ethers@6</pre><p>Also, Install Polyfill Packages:</p><pre>npm install --save-dev \<br>    vite-plugin-node-polyfills</pre><p>Modify your vite.config.js to include the polyfills:</p><pre>import { defineConfig } from &#39;vite&#39;<br>import react from &#39;@vitejs/plugin-react&#39;<br>import { nodePolyfills } from &#39;vite-plugin-node-polyfills&#39;;<br><br>// https://vite.dev/config/<br>export default defineConfig({<br>  plugins: [<br>    react(),<br>    nodePolyfills({<br>      globals: {<br>        Buffer: true,<br>      }<br>    })<br>  ],<br>})</pre><p>Restart you app: npm run dev , open on the Browser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbwkUoacstPkTWMVD08JyA.png" /><figcaption>Finished App, Upload Written text to Irys</figcaption></figure><p>Now write something and Store on Irys, You’d get an alert with the link to the gateway where it’s stored. In this case the Irys Devnet.</p><p>You can easily extend this by:</p><ul><li>Modify to upload files. <a href="https://docs.irys.xyz/build/d/sdk/upload/uploadFile">Read More</a></li><li>Attach tags. <a href="https://docs.irys.xyz/build/d/features/tags">Read More</a></li></ul><h3>7. Wrap-Up</h3><p>By integrating <strong>Wagmi + RainbowKit</strong> with Irys:</p><ul><li>Developers keep familiar wallet flows.</li><li>Users can connect with OKX, MetaMask, Rainbow, Coinbase Wallet, etc.</li><li>Irys powers verifiable, programmable storage underneath.</li></ul><p>👉 This integration lowers the barrier for Ethereum developers to add <strong>storage + programmability</strong> to their dApps with almost no extra steps.</p><h4>Happy building with Irys 💚!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adf32cde4871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Fund Your Irys Account with Popular Test Tokens.]]></title>
            <link>https://medium.com/@zizicrypt/how-to-fund-your-irys-account-with-popular-test-tokens-94102720042c?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/94102720042c</guid>
            <category><![CDATA[token]]></category>
            <category><![CDATA[devnet]]></category>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[iry]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 22:59:43 GMT</pubDate>
            <atom:updated>2025-09-15T22:33:05.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7qhJM2LaelT2Fwil0G-Cww.png" /></figure><p>If you’re building with Irys, one of the first things you’ll need to do is fund your Irys account. Funding allows you to cover the cost of uploading data to the network. You can either fund upfront (preload your account balance) or use lazy-funding (fund per upload).</p><p>In this guide, we’ll take the upfront funding, and walk through how to fund your Irys account on testnet using Sepolia ETH. <br>Checkout lazy funding: (<a href="https://docs.irys.xyz/build/d/sdk/payment/fund#lazy-funding">Irys docs</a>)</p><h3>1. Initilize and Install</h3><p>First, make sure you have <strong>Node.js </strong>and <strong>Npm </strong>installed. Then, initialize a new project:</p><pre>npm init -y</pre><p>Then install the required Irys SDK packages:</p><pre>npm install @irys/upload @irys/upload-ethereum dotenv</pre><p>We’ll also use dotenv to safely manage your private key.</p><h3>2. Set Up Environment Variables</h3><p>In your project root, create a .env file and add your wallet private key(eth):</p><pre>PRIVATE_KEY=your_testnet_private_key_here</pre><p>⚠️ Never commit .env files to GitHub.</p><h3>3. Connect to Irys with Testnet Tokens</h3><p>Irys supports multiple tokens for payments (ETH, MATIC, AVAX, SOL, etc.) across devnets, (see <a href="https://docs.irys.xyz/build/d/features/supported-tokens#devnet">Irys Docs</a>).</p><p><strong>Important:</strong> Always use a <strong>testnet RPC</strong> when working with devnet tokens. If you don’t provide an RPC, the SDK will likely default to mainnet, and you’ll get an “insufficient funds” error. Example below is with <strong>Sepolia Testnet</strong></p><p>Create a Js file to start irys configuration, e.g lib/irys.js and add:</p><pre>import { Uploader } from &quot;@irys/upload&quot;<br>import { Ethereum } from &quot;@irys/upload-ethereum&quot;<br>import &quot;dotenv/config&quot;<br><br>const getIrysUploader = async () =&gt; {<br>  const rpcUrl = &quot;https://ethereum-sepolia-rpc.publicnode.com&quot;;<br><br>  const irysUploader = await Uploader(Ethereum)<br>    .withWallet(process.env.PRIVATE_KEY)<br>    .withRpc(rpcUrl)<br>    .devnet();<br><br>  return irysUploader;<br>};<br><br>export default getIrysUploader</pre><p>For other tokens (Polygon, Aptos, Solana, etc.), replace Ethereum with the respective SDK import (see <a href="https://docs.irys.xyz/build/d/sdk/setup">Irys docs</a>).</p><h3>4. Fund Your Account</h3><p>Create another JS file in the root dir to handle funding, e.g fund.js <br>Then add the logic:</p><pre>import getIrysUploader from &quot;./lib/irys.js&quot;;<br><br>const fundAccount = async () =&gt; {<br>  const irysUploader = await getIrysUploader();<br><br>  try {<br>    console.log(&quot;Funding...&quot;)<br>    const fundTx = await irysUploader.fund(irysUploader.utils.toAtomic(0.01));<br>    console.log(<br>      `Successfully funded ${irysUploader.utils.fromAtomic(fundTx.quantity)} ${<br>        irysUploader.token<br>      }`<br>    );<br>  } catch (error) {<br>    console.log(&quot;Error when funding &quot;, error);<br>  }<br>};<br><br>fundAccount();</pre><p>This will send a transaction to fund your Irys account with 0.01 Sepolia ETH. You can always adjust the amount.</p><p>Full code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CkehygFEdaJyqyudANN5_w.png" /></figure><p>Run you code:</p><pre>node &lt;fileName&gt; e.g fund.js</pre><p>Output of this TX if successful:</p><pre>mac@MACs-MacBook-Pro funding_accounts % node fund.js<br>[dotenv@17.2.2] injecting env (1) from .env -- tip: ⚙️  load multiple .env files with { path: [&#39;.env.local&#39;, &#39;.env&#39;] }<br>Successfully funded 0.01 ethereum</pre><p>So if you go back to check your wallet (the one associated with the Private_key, in .env), you should see 0.01 deducted from you wallet.</p><p><strong>Congratulations you’ve successfully funded you account</strong></p><h3>5. Check Balance</h3><p>To verify even further, let’s check the Balance of our Irys Account.<br>Create another file in the root dir checkBalance.js and Add:</p><pre>import getIrysUploader from &quot;./lib/irys.js&quot;;<br><br>const getBalance = async () =&gt; {<br>  const irys = await getIrysUploader();<br><br>  const balance = await irys.getBalance();<br>  const humanReadable = irys.utils.fromAtomic(balance);<br><br>  console.log(&quot;balance&quot;, balance);<br>  console.log(&quot;humanReadable&quot;, humanReadable);<br>};<br><br>getBalance()</pre><p>Run the file:</p><pre>node checkBalance.js</pre><p>Expected Output:</p><pre>mac@MACs-MacBook-Pro funding_accounts % node checkBalance.js <br>balance 10000000000000000<br>humanReadable 0.01<br>mac@MACs-MacBook-Pro funding_accounts %</pre><h3>6. Handling Common Issues</h3><ul><li><strong>Forgot RPC</strong> → Defaults to mainnet → “insufficient funds” error. Always provide a <strong>testnet RPC</strong>.</li><li><strong>Omitted </strong><strong>.devnet()</strong> → Funding may still work but with error logs. Add .devnet() for smooth funding.</li><li><strong>Slow confirmations</strong> → Free/public RPCs can lag. Try another RPC from <a href="https://chainlist.org/">Chainlist</a> or use a paid RPC:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IV8eCjhOYMwLDHsuxfIAvg.png" /></figure><h3>7. Supported Tokens on Devnet</h3><p>On devnet, uploads are paid with <strong>free faucet tokens</strong> and data is deleted after ~60 days. Supported tokens include:</p><ul><li>Ethereum (Sepolia) — ethereum</li><li>Polygon (Amoy) — matic</li><li>Arbitrum Sepolia — arbitrum</li><li>Avalanche Chain — avalanche</li><li>Solana — solana</li><li>Near — near</li><li>Algorand — algorand</li><li>Aptos — aptos</li></ul><p>Many more (see full list in <a href="https://docs.irys.xyz/build/d/features/supported-tokens">docs</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFf_d8Ix8b4TXttMUyXbdQ.png" /></figure><h3>Resources</h3><ol><li>Get Sepolia Eth test token: <a href="https://sepolia-faucet.pk910.de/#/">https://sepolia-faucet.pk910.de/#/</a></li><li>Bridge from Sepolia Eth to get <a href="https://bridge.arbitrum.io/?destinationChain=arbitrum-sepolia&amp;sanitized=true&amp;sourceChain=sepolia">Arbitrum Sepolia ETH</a></li><li>Get Irys Token: <a href="https://irys.xyz/faucet">https://irys.xyz/faucet</a>:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jf0M7UQIBV-ArP1TSw7-yg.png" /></figure><h3>Conclusion</h3><p>You’ve now funded your Irys account with test tokens! 🚀</p><p>From here you can:</p><ul><li>Upload data (strings, files, JSON, images) directly to Irys, <a href="https://medium.com/@zizicrypt/simple-way-to-store-data-on-irys-8bd7a3fd2637">Learn more</a>.</li><li>Or stick with lazy-funding per upload, <a href="https://docs.irys.xyz/build/d/sdk/payment/fund#lazy-funding">Learn more</a>.</li></ul><h4>Happy building with Irys 💚!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94102720042c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Economics of Verifiable Storage: Why Builders Are Choosing Irys]]></title>
            <link>https://medium.com/@zizicrypt/the-economics-of-verifiable-storage-why-builders-are-choosing-irys-ccb521e82080?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccb521e82080</guid>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[cost-effective]]></category>
            <category><![CDATA[verifiability]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Sat, 30 Aug 2025 23:41:11 GMT</pubDate>
            <atom:updated>2025-08-30T23:41:11.818Z</atom:updated>
            <content:encoded><![CDATA[<p>For builders in the Web3 space, choosing a storage layer is a strategic decision that goes far beyond technical specifications. The economic model, reliability, and verifiability of a storage solution directly impact a project’s long-term sustainability. While innovative projects like Filecoin, Arweave, Walrus, and Story Protocol have advanced the decentralized storage landscape, each has made different design trade-offs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANErUMvJclS6Ng1okCWR5Q.png" /></figure><blockquote>This guide explores the key differentiators between Irys and these other solutions, to help you determine the right fit for your application.</blockquote><p>A builder’s guide to the storage landscape</p><h4>Arweave: The permanence pioneer</h4><p>Arweave pioneered the concept of permanent, immutable data storage through a one-time payment. This model is ideal for applications where long-term, archival-style storage is the primary requirement.</p><ul><li><strong>Trade-off:</strong> While Arweave ensures durability, it was not built for instant, verifiable retrieval needed by high-demand dApps.</li><li><strong>How Irys complements Arweave:</strong> Irys was initially integrated with Arweave but has since evolved into a sovereign L1. It still interoperates with Arweave for permanence, but its architecture is now independent, optimized for programmability, instant retrieval, and verifiable proofs. While Arweave’s design focuses on guaranteed permanence, Irys’s focuses on programmable data with millisecond-level speed and verifiable receipts.</li></ul><h4>Filecoin: The marketplace of storage</h4><p>Filecoin offers a robust, incentivized storage market where users can purchase storage from a network of providers. It’s effective for developers who need to manage large datasets and prioritize economic flexibility.</p><ul><li><strong>Trade-off:</strong> The price discovery mechanism can lead to unpredictable costs, and retrieving data from storage providers can introduce significant latency, harming dApp user experience.</li><li><strong>How Irys differs:</strong> In contrast, Uploads under 100KiB are <strong>free</strong>. Beyond that, costs are <strong>flat and predictable</strong> — no bidding markets, no token speculation. This predictability and performance is a deliberate design choice suited for applications that need low-latency access and a predictable cost structure.</li></ul><h4>Walrus: Hot data on Sui</h4><p>Walrus is designed specifically to optimize “hot data” storage within the Sui ecosystem. It leverages Sui’s high-performance architecture for quick access to binary blobs, making it a specialized solution for applications within that network.</p><ul><li><strong>Trade-off:</strong> Walrus’s dependency on the Sui ecosystem means that its economic model and security are tied to the underlying L1.</li><li><strong>How Irys offers a sovereign alternative:</strong> Builders using Walrus are inherently building on Sui’s economic and security foundation. Irys, as a sovereign Layer 1, eliminates external dependencies, ensuring that its storage logic runs natively and independently.</li></ul><h4>Story Protocol: IP assets and licensing</h4><p>Story Protocol is an IP management system that uses its own L1 to manage the ownership and licensing of intellectual property. While it anchors data attestations on-chain, its primary function is not general-purpose data storage.</p><ul><li><strong>Trade-off:</strong> For applications centered on data-intensive workloads rather than IP management, a solution focused purely on storage and verifiability is more appropriate.</li><li><strong>Focus on core function:</strong> Story Protocol and Irys solve fundamentally different problems. Irys focuses on building a backbone for verifiable data, while Story Protocol is building an IP layer. For projects needing a reliable, low-latency data layer, Irys is the more direct solution.</li></ul><h3>Irys: The economics of verifiable storage, solved</h3><p>Irys is a programmable data chain that integrates execution with storage on a sovereign Layer 1. This architecture is designed to address the key pain points faced by builders.</p><ol><li><strong>Predictable cost model:</strong> Unlike volatile storage markets, Irys provides a stable pricing model. This allows startups and enterprises to accurately budget for data storage, turning cost modeling from a gamble into a predictable accounting exercise.</li><li><strong>Instant and verifiable retrieval:</strong> While Irys can still interoperate with Arweave, it now provides its own sovereign storage and execution layer. Every upload returns a verifiable receipt that can be checked onchain, giving builders trustless guarantees.</li><li><strong>Sovereign architecture:</strong> As a native L1 datachain, Irys eliminates external dependencies. This ensures that storage logic is handled natively and efficiently, without the “double tax” of paying for both storage and execution on separate networks.</li></ol><h3>Why this matters for builders</h3><ul><li><strong>For startups:</strong> Predictable pricing means you can model costs directly into your runway, building without the fear of token price spikes.</li><li><strong>For dApps:</strong> Verifiable receipts mean your contracts can trust storage as much as they trust token balances, enabling things like pay-per-access, licensing, and composable data apps.</li><li><strong>For enterprises: </strong>Stable economics and verifiable proofs make decentralized storage adoptable in real-world workflows, from supply chain verification to immutable data auditing.</li></ul><h3><strong>Conclusion</strong></h3><p>Verifiable storage isn’t just a buzzword — it’s the foundational layer for sustainable, trustless infrastructure. While Filecoin, Arweave, Walrus, and Story Protocol have all pushed the boundaries of decentralized storage, they have made different trade-offs in terms of cost, speed, and dependencies.</p><p>Only Irys delivers verifiable storage with truly predictable economics on a sovereign, purpose-built Layer 1. For builders who need a reliable, cost-effective, and trustless data backbone, the economic argument for Irys is clear.</p><h4>Happy building with Irys 💚!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccb521e82080" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Way to Store Data on Irys]]></title>
            <link>https://medium.com/@zizicrypt/simple-way-to-store-data-on-irys-8bd7a3fd2637?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bd7a3fd2637</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[programmable]]></category>
            <category><![CDATA[iry]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 22:10:04 GMT</pubDate>
            <atom:updated>2025-08-26T22:10:04.060Z</atom:updated>
            <content:encoded><![CDATA[<p>Irys makes it easy to upload data onchain, with free uploads under 100KiB and predictable costs beyond that. In this short guide, we’ll walk through a simple example using <strong>Arbitrum</strong> as the payment chain. You can use other ones like <a href="https://docs.irys.xyz/build/d/sdk/setup#aptos">Aptos</a>, <a href="https://docs.irys.xyz/build/d/sdk/setup#berachain">Berachain</a>, <a href="https://docs.irys.xyz/build/d/sdk/setup#bnb">BNB</a>, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PixZtWcUDbrbKIe5f_8qZQ.png" /></figure><h3>Prerequisite</h3><ul><li>NodeJS and NPM installed</li><li>A text editor (Vscode)</li><li>A Metamask wallet</li></ul><h3>1. Setup</h3><p>Make a new folder, and initialise a Js project:</p><pre>mkdir simple-irys-upload &amp;&amp; cd simple-irys-upload<br>npm init -y</pre><p>Install dependencies:</p><pre>npm install @irys/upload @irys/upload-ethereum</pre><h3>2. Create index.js</h3><p>This script connects to Irys, uploads a string, and prints a link to the uploaded data.</p><pre>import { Uploader } from &quot;@irys/upload&quot;;<br>import { Arbitrum } from &quot;@irys/upload-ethereum&quot;;<br>import &quot;dotenv/config&quot;;<br><br>const getIrysUploader = async () =&gt; {<br>  const irysUploader = await Uploader(Arbitrum).withWallet(process.env.PRIVATE_KEY);<br>  return irysUploader;<br>};<br><br>const UploadDataToIrys = async () =&gt; {<br>  const irys = await getIrysUploader();<br><br>  const dataToUpload = &quot;Hirys World&quot;;<br><br>  try {<br>    console.log(&quot;Uploading...&quot;);<br>    const receipt = await irys.upload(dataToUpload);<br><br>    console.log(&quot;✅ Upload successful!&quot;);<br>    console.log(`View it at: https://gateway.irys.xyz/${receipt.id}`);<br>  } catch (error) {<br>    console.log(`Error uploading data `, error);<br>  }<br>};<br><br>UploadDataToIrys()</pre><h3>3. Add Your Wallet</h3><p>Create a .env file and add your private key (make sure this is a test wallet, not your main one):</p><pre>PRIVATE_KEY=&quot;your-arbitrum-wallet-private-key&quot;</pre><p>Then install dotenv so Node can load it:</p><pre>npm install dotenv</pre><p>Update the top of index.js:</p><pre>import &quot;dotenv/config&quot;;</pre><h3>4. Run It</h3><pre>node index.js</pre><p>If successful, you’ll see output like:</p><pre>✅ Upload successful!<br>View it at: https://gateway.irys.xyz/abc123...</pre><p>Click the link and you’ll be asked to download the small file. <br>Save it and open it to see your data.</p><p>Everytime you acces the Url, you’d be able to see your Data.</p><h3>5. Notes</h3><ul><li>Uploads under <strong>100KiB are free</strong>. For larger uploads, you’ll need to fund your Irys account.</li><li>You can upload <strong>strings, Buffers, or streams</strong> — not just plain text.</li></ul><h3>Conclusion</h3><p>This guide showed the simplest possible upload.</p><p>Learn more on Irys Docs:<br><a href="https://docs.irys.xyz/build/d/quickstart">https://docs.irys.xyz/build/d/quickstart</a></p><h4>Happy building with Irys 💚!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bd7a3fd2637" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Irys! Here is a Rank-Up Guide for you]]></title>
            <link>https://medium.com/@zizicrypt/welcome-to-irys-here-is-a-rank-up-guide-for-you-dda0e3b2e09e?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dda0e3b2e09e</guid>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 15:35:23 GMT</pubDate>
            <atom:updated>2025-07-29T15:35:23.539Z</atom:updated>
            <content:encoded><![CDATA[<h4>“No shortcuts. No noise. Just growth.”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5Nz4m54BWhnRjPgs3SNoQ.png" /></figure><p>In Irys, your rank isn’t a badge. it’s a reflection Of your consistency. <br>Your intent. Your resonance with Iryna.</p><p>Let’s walk through the path of growth, one rank at a time 👇</p><h3>🟣 Deshi (Beginner)</h3><p>You’ve just arrived. Welcome.<br>Now’s your time to <em>observe, ask, and engage</em>.</p><p><strong>To rank up:</strong></p><ul><li>Introduce yourself in the server</li><li>Ask questions and share discoveries</li><li>Show up to events, reply to others, build curiosity</li></ul><p><strong>The goal:</strong> Prove that you’re <em>here for more</em> than airdrops. <br>Show presence. Show promise.</p><h3>🔴 Shugo (Advocate)</h3><p>You’ve grasped Irys’s vision. Now you’re contributing.<br> You don’t just talk — you <em>build, teach, and vibe.</em></p><p><strong>To rank up:</strong></p><ul><li>Create threads, memes, guides, or videos</li><li>Join community calls, vibe sessions, or regional tasks</li><li>Help new Deshi understand what Irys <em>is</em></li></ul><p><strong>The goal:</strong> Bring value consistently. <br><em>Speak the language of the protocol.</em></p><h3>🟡 Senshi (Protector)</h3><p>Now you’re not just a contributor — you’re a protector.<br>You hold the culture down and inspire the next wave.</p><p><strong>To rank up:</strong></p><ul><li>Mentor Deshi and Shugo</li><li>Lead tasks, events, and internal projects</li><li>Guide the tone, values, and rhythm of Irys</li></ul><p><strong>The goal:</strong> Lead through presence and example. <br>You <em>are</em> Irys in motion.</p><h3>🔵 Shihan (Master)</h3><p>Few make it here. But if you do, you’re shaping the ecosystem.<br>Iryna sees you. She trusts you.</p><p><strong>To rank up:</strong></p><ul><li>Build systems, not just content</li><li>Guide other ranks across regions and projects</li><li>Influence community structure, governance, and expansion</li></ul><p><strong>The goal:</strong> Become a force of alignment. <br>You <em>don’t just follow the path — you build it.</em></p><h3>Remember</h3><ul><li>Roles aren’t given on request. They’re <em>observed and earned</em>.</li><li>It’s not about loudness — it’s about <em>resonance</em>.</li><li>The more aligned you are with Irys’s vision, the faster you rise.</li></ul><p>Stay consistent. <br>Stay real. <br>Stay Irys. (✧ᴗ✧) 💚</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dda0e3b2e09e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of Partitions for Irys]]></title>
            <link>https://medium.com/@zizicrypt/overview-of-partitions-for-irys-d4745901a8ac?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4745901a8ac</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[partition]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 22:40:17 GMT</pubDate>
            <atom:updated>2025-06-25T22:40:17.086Z</atom:updated>
            <content:encoded><![CDATA[<h3>Wetin Be Partitions?</h3><p>For inside Irys network, partitions na the main building blocks wey dey run the protocol. Dem be like the big units wey dey organize data and make am verifiable. Every 16TB partition na the key structure for Irys multi-ledger system, e dey help miners to prove say dem dey store data well for the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f8kKJdulchp_ypaRAywAkw.png" /></figure><p>Partitions get two big roles:</p><ul><li><strong>Manage Storage: </strong>Dem dey handle empty space and dey share ledger data everywhere for network.</li><li><strong>Make Sure e Verifiable:</strong> Partitions na the foundation for trust for Irys, e dey connect miner promises to specific data. This one make users fit check partitions to confirm say their data dey replicated and safe.</li></ul><p>Plus, by giving specific miners their own partitions, Irys dey ensure:</p><ul><li><strong>Direct Accountability:</strong> Miners dey tie money to the partitions dem dey manage, so dem go try hard to do am well.</li><li><strong>Fast Access:</strong> Miners fit locate and bring out data quick for programmable data work, so e dey available when you need am.</li></ul><p>By holding storage, verifiability, and data access, partitions no just dey work — dem dey vital for Irys to stay reliable and grow big.</p><h3>Why Partitions Matter?</h3><p>Partitions na the practical base for Irys multi-ledger storage layer. Dem dey make data work easy, fault-tolerant, verifiable, and cheap with fixed cost — things every developer need to trust the network.</p><h4>Smart Scaling</h4><p>Irys dey use partitions to manage storage and copy of data ledgers, plus e dey bring miners to add empty space before e even need am.</p><p>This capacity dey move dynamic, so:</p><ul><li>E dey always get enough space for network demand.</li><li>Extra space no dey pile up, keeping costs steady by making sure miners get fair pay.</li></ul><p>This system dey make scaling smooth and pocket-friendly, so developers no go meet surprise bills or limits as their storage grow.</p><h4>Reliable Redundancy</h4><p>Partitions for Irys dey spread evenly across network, so data copies dey replicated global. This redundancy dey give:</p><ul><li><strong>Fault-Tolerant:</strong> E no go fail if disaster like hurricane or earthquake hit one place.</li><li><strong>Globally Accessible:</strong> Ledger data dey available everywhere, making fast retrieval and support for programmable data.</li></ul><p>By spreading data evenly, Irys dey increase strength and optimize access, so users and miners fit interact with data well, no matter where dem dey.</p><h4>Cost Stability</h4><p>Every step for partition life — pledging, packing, mining, and orderly exit — get purpose. Miners dey commit resources and get reward based on how reliable and good dem perform.</p><p>This setup dey keep costs predictable for users and stop behavior wey fit disturb network. You sabi wetin you dey get, and you sabi wetin you dey pay.</p><h4>Flexible Storage for Real Needs</h4><p>Irys dey support capacity partitions (standby storage) and data partitions (active ledger data), giving storage options for different needs — short-term or permanent.</p><p>By building data ledgers with partitions, protocol dey get clear data ranges wey:</p><ul><li><strong>Fit Be Dynamically Incentivized:</strong> Miners fit get reward to store specific partitions or stop get pay when e no need again.</li><li><strong>Enable Permanent and Term Storage: </strong>This flexibility make Irys fit handle both permanent and time-based data in one protocol, matching developer and app demands.</li></ul><p>This partition way dey make resources use well, aligning with app needs without extra wahala.</p><h3>How Partitions Dey Work</h3><h4>Types of Data Partitions</h4><p>Irys dey use two main types:</p><ul><li><strong>Capacity Partitions:</strong> Standby storage wey dey wait to be used when need arise.</li><li><strong>Data Partitions:</strong> Active for ledger storage and verification.</li></ul><p>Each data ledger slot fit assign up to 10 partitions for data replication. This replication dey make sure data no just dey store, but e dey store reliable across global nodes.</p><p>With standby capacity and many data partitions, Irys fit grow with demand, keep data available, and support programmable data smart contract work well.</p><h4>Replication</h4><p>Each data ledger slot get multiple partitions, so same data dey exist in different places. If one partition spoil, data still dey safe elsewhere for network.</p><p>Replication dey make data fault-tolerant and strong, giving safety net against loss and keeping uptime for all users.</p><p>E also dey spread data global, making fast retrieval by nodes during programmable data work. This dey ensure smooth interaction and availability for smart contract.</p><h4>Partition Lifecycle</h4><p>Each partition for Irys network dey follow clear life cycle, bringing order and predictability for how data dey manage, access, and store.</p><h4>Initial Set Up And Pledging</h4><p>Miners dey start by setting up at least one partition storage for their machine, preparing am to meet protocol standard. When e ready, dem dey pledge am to Irys and wait for Partition ID.</p><p>Partition ID assignment dey allow miners to start packing, next step for their commitment. Unassigned pledges dey return, keeping system organized.</p><p>This first commitment dey set base level of accountability for the rest of the life.</p><h4>Packing through Matrix Packaging</h4><p>After assignment, miners dey prepare partitions with Matrix Packing. This process dey put unique miner ID inside each partition, making sure each copy for network dey different and verifiable.</p><p>The big job of Matrix Packing na to prove — and encourage — say miners dey store unique partition copies. By making partitions easy to check, e dey lay strong base for secure storage wey dey last through mining and block making.</p><h4>Mining and Block Production</h4><p>When partitions don pack, miners dey always generate storage proofs — crypto evidence wey show say dem dey maintain their data well.</p><p>These proofs no dey check data itself, but dey prove to network say miners dey keep their storage promise.</p><p>By submitting valid proof, miners fit produce block and collect reward. This system dey tie mining pay to steady, verifiable storage, aligning miner goals with network trust.</p><h4>Ledger Assignment</h4><p>As data storage demand grow, Irys dey assign capacity partitions to active data roles for ledgers. This process dey favor miners wey don show reliable work, rewarding steady contribution and boosting network strength.</p><p>These incentives dey stop bad behavior, improving network performance and supporting programmable data quick response.</p><h4>Orderly and Disorderly Departures</h4><p>Miners fit leave in two ways:</p><ul><li><strong>Orderly Departure:</strong> Miner dey submit formal leave request, allowing Irys to reassign storage without wahala. After wait time, their pledge dey refund, keeping network balance.</li><li><strong>Disorderly Departure:</strong> If miner dey misbehave (e.g., neglect or bad act), dem forfeit stake. Protocol quick reallocate storage to keep data safe.</li></ul><p>Both ways dey managed by protocol to protect data integrity and global spread — key for fast, responsive programmable data.</p><h4>Happy reading 💚 from Irys</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4745901a8ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pourquoi Irys existe et comment il résout les problèmes de complexité, de stagnation, de…]]></title>
            <link>https://medium.com/@zizicrypt/pourquoi-irys-existe-et-comment-il-r%C3%A9sout-les-probl%C3%A8mes-de-complexit%C3%A9-de-stagnation-de-b53b9b42109b?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b53b9b42109b</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[irysvm]]></category>
            <category><![CDATA[iry]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 00:03:26 GMT</pubDate>
            <atom:updated>2025-06-22T00:03:26.582Z</atom:updated>
            <content:encoded><![CDATA[<h3>Pourquoi Irys existe et comment il résout les problèmes de complexité, de stagnation, de centralisation et de coût des données</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RKhqAXagaJBXJxdVq1WoZA.png" /></figure><h4>Le Problème de la Complexité</h4><p>Les développeurs sont confrontés à un labyrinthe de solutions de stockage fragmentées. Chaque système ajoute des couches de complexité, entraînant des coûts plus élevés, des processus plus lents et des goulets d’étranglement qui étouffent l’innovation. Gérer ces systèmes disparates dépasse largement une simple gêne : c’est une barrière majeure à l’échelle effective des applications.</p><h4>Le Problème des Données Statiques</h4><p>Les données sans prise en charge d’interactions significatives sont des données figées. Les premières chaînes de données (datachains) ont traité le stockage et l’exécution comme des mondes séparés. Cette nature statique limite le potentiel des données, rendant difficile la création d’applications qui s’engagent sur ces données. C’est un système conçu pour le stockage, pas pour l’innovation.</p><h4>Le Problème de la Centralisation</h4><p>Une véritable décentralisation signifie qu’aucune entité ne détient trop de pouvoir. Pourtant, les premières générations de chaînes de données sont dominées par quelques acteurs, risquant des manipulations et réduisant la confiance et la sécurité promises par le système. Cette centralisation compromet les principes mêmes pour lesquels les blockchains ont été conçues.</p><h4>Le Problème des Coûts Imprévisibles</h4><p>Des coûts imprévisibles et élevés sont le cauchemar des développeurs. Construire des applications qui reposent sur des données en chaîne (onchain) devrait être une entreprise économiquement viable, mais les frais de stockage fluctuants rendent difficile l’établissement d’un budget et la planification de projets à long terme. Sans stabilité des coûts, l’innovation est freinée, et de nombreuses idées prometteuses ne quittent jamais le stade de la conception.</p><h3>Comment Irys Résout Ces Problèmes</h3><h4>Résoudre le Goulet d’Étranglement de la Complexité</h4><p>Chaque inefficacité coûte du temps et de l’argent. Aujourd’hui, les développeurs luttent avec des systèmes disjoints, assemblant des solutions de stockage fragmentées juste pour faire fonctionner leurs applications. Cette complexité épuise les ressources, ralentit les progrès et augmente les coûts. Irys propose une réponse claire et directe : un réseau unifié optimisé pour le stockage (données) et l’exécution (contrats intelligents) — ce qui permet, pour la première fois, aux contrats intelligents d’accéder nativement aux données stockées sur le même réseau.</p><p>Cette intégration élimine les allers-retours inutiles entre protocoles, permettant aux développeurs de rationaliser leur flux de travail, de réduire les dépenses et de se concentrer entièrement sur l’innovation.</p><h4>Résoudre la Stagnation des Données Statiques</h4><p>Au cœur d’Irys se trouve une architecture multi-ledger qui optimise la transition des données de la validation temporaire au stockage permanent. Ce système est conçu pour équilibrer efficacité, fiabilité et rentabilité, tout en posant les bases d’applications avancées nécessitant des données programmables.</p><p>Toutes les données sur Irys passent d’abord par le Submit Ledger, un espace où elles sont temporairement conservées pour validation. Une fois vérifiées, elles gagnent leur place dans le Publish Ledger, où elles deviennent permanentes et, surtout, fiables. Imaginez cela comme une promotion des données à travers un cycle de vie, de l’utilisation temporaire à une permanence vérifiée, devenant partie d’un système interconnecté plus large.</p><p>Bien qu’Irys commence avec deux ledgers, son protocole est conçu pour s’adapter. Les développeurs et utilisateurs peuvent s’attendre à la création de ledgers supplémentaires adaptés à des besoins spécifiques, qu’il s’agisse de stockage à court ou long terme. Cette approche dynamique garantit que, à mesure que l’utilisation croît, Irys évolue en réponse à une demande réelle, et non à des hypothèses.</p><p>De cette manière, Irys ne se contente pas de se préparer à l’avenir : elle est façonnée par les besoins de ceux qui la construisent.</p><h4>Résoudre la Menace de la Centralisation</h4><p>La centralisation compromet la promesse fondamentale des blockchains : un pouvoir distribué, des systèmes sans confiance et une résilience contre les points de défaillance uniques. Lorsque le contrôle est concentré entre quelques mains, le système devient vulnérable à la manipulation.</p><p>C’est un défaut fondamental que les premières générations de chaînes de données n’ont pas efficacement résolu.</p><p>Irys prend des mesures proactives pour prévenir la centralisation grâce à son mécanisme de consensus unique, combinant Proof of Work (PoW) et Proof of Stake (PoS).</p><p>Voici comment :</p><ul><li><strong>Stake-Activated Mining:</strong> Les mineurs doivent miser des ressources pour activer une adresse de minage sur le réseau, signalant leur engagement.</li><li><strong>Distribution Contrôlée de la Puissance de Hachage: </strong>Le protocole impose qu’aucune adresse de minage ne contrôle plus de 10 % de la puissance de hachage du réseau. Cela garantit une distribution du pouvoir et limite le risque qu’une seule entité domine.</li><li><strong>Engagements Progressifs: </strong>Ajouter une nouvelle partition à une adresse de minage existante est nettement plus rentable que de créer une nouvelle adresse. Cette conception rend économiquement peu avantageux pour les mineurs d’opérer plusieurs adresses, supprimant tout incitant financier à le faire.</li></ul><h4>Résoudre le Fardeau des Coûts Imprévisibles</h4><p>Dans le monde des affaires, l’incertitude est un tueur. On ne peut pas budgéter, planifier, ni innover quand les coûts fluctuent sauvagement. La plupart des blockchains laissent les développeurs deviner, avec des frais de stockage qui varient de manière imprévisible et menacent de faire dérailler les projets avant même leur lancement. Irys met fin à cela. Nous avons construit un système où la tarification n’est pas un mystère, mais une promesse. Chaque bloc sur Irys porte une horodatage et la meilleure approximation du prix USD/IRYS par le mineur. Ces estimations de prix sont suivies dans le temps, et grâce à une Exponential Moving Average (EMA), nous stabilisons le coût du stockage. Cela signifie une tarification prévisible et fiable.</p><p>Mais nous n’en sommes pas restés là. Les mineurs sont incités à garder leurs estimations de prix précises. S’ils signalent une valeur erronée, leurs blocs peuvent être rejetés par d’autres mineurs. C’est un système auto-correcteur qui maintient tout le monde honnête et stabilise vos coûts. Les développeurs n’ont plus à parier sur le stockage.</p><p>Avec Irys, vous savez exactement ce que vous obtenez et ce que cela va coûter.</p><h3>Conclusion</h3><p>En explorant les défis des solutions de stockage actuelles et la manière dont Irys y répond, il devient évident que cette plateforme simplifie le développement décentralisé. Grâce à son réseau unifié, son architecture adaptable, sa décentralisation efficace et sa tarification stable, Irys aide les développeurs à surmonter les obstacles. Que vous soyez un développeur curieux ou un bâtisseur motivé, je vous invite à découvrir Irys : consultez les <a href="https://docs.irys.xyz/learn/what/what-a-datachain-is">docs</a> Irys ou rejoignez la communauté sur <a href="https://discord.gg/irys">Discord</a>. Partagez vos projets avec @irys_xyz et travaillons ensemble à améliorer Web3. Qu’allez-vous construire avec Irys ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b53b9b42109b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Data Licensing System with IrysVM]]></title>
            <link>https://medium.com/@zizicrypt/building-a-data-licensing-system-with-irysvm-b76d5d993188?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b76d5d993188</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[iryssdk]]></category>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[irysvm]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Fri, 20 Jun 2025 00:28:20 GMT</pubDate>
            <atom:updated>2025-06-20T22:37:27.592Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Use smart contracts to enforce pay-per-access rules for on-chain data</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9XzOQw9qwEaxcbIFDqCG3g.png" /></figure><h4>Prerequisites</h4><ul><li>Node.js v18+</li><li>MetaMask (with Irys Tesnet Tokens— get some <a href="https://irys.xyz/faucet">here</a>)</li><li>Basic terminal skills</li></ul><h3>1. Project Setup</h3><pre># Create project folder<br>mkdir irys-data-license &amp;&amp; cd irys-data-license<br><br># Initialize npm and install dependencies<br>npm init -y<br>npm install @irys/sdk ethers@6 hardhat @nomicfoundation/hardhat-toolbox dotenv crypto-js</pre><h3>2. Smart Contract (IrysVM Interaction)</h3><p>Create contracts/DataLicense.sol:</p><pre>// SPDX-License-Identifier: MIT<br>pragma solidity ^0.8.0;<br><br>contract DataLicense {<br>    mapping(bytes32 =&gt; address) public dataOwners;<br>    mapping(bytes32 =&gt; uint256) public accessFees;<br>    mapping(bytes32 =&gt; bytes) private decryptionKeys;<br><br>    event DataRegistered(bytes32 indexed dataId, address owner);<br>    event AccessGranted(bytes32 indexed dataId, address user, bytes key);<br><br>    function registerData(bytes32 dataId, uint256 fee, bytes memory key) external {<br>        dataOwners[dataId] = msg.sender;<br>        accessFees[dataId] = fee;<br>        decryptionKeys[dataId] = key;<br>        emit DataRegistered(dataId, msg.sender);<br>    }<br><br>    function payForAccess(bytes32 dataId) external payable {<br>        require(msg.value &gt;= accessFees[dataId], &quot;Insufficient payment&quot;);<br>        bytes memory key = decryptionKeys[dataId];<br>        require(key.length &gt; 0, &quot;No key available&quot;);<br>        payable(dataOwners[dataId]).transfer(msg.value);<br>        emit AccessGranted(dataId, msg.sender, key);<br>    }<br><br>    function getDecryptionKey(bytes32 dataId) external view returns (bytes memory) {<br>        require(dataOwners[dataId] == msg.sender || accessFees[dataId] == 0, &quot;Not authorized&quot;);<br>        return decryptionKeys[dataId];<br>    }<br>}</pre><p><strong>Key IrysVM Feature: </strong>This leverages IrysVM for smart contract execution, storing only a compact data ID (bytes32) on-chain while the actual content (encrypted) lives on Irys, reducing gas costs by 90% compared to full on-chain storage.</p><h3>3. Configure Hardhat</h3><p>Create hardhat.config.js:</p><pre>require(&quot;@nomicfoundation/hardhat-toolbox&quot;);<br>require(&quot;dotenv&quot;).config();<br><br>module.exports = {<br>  solidity: &quot;0.8.20&quot;,<br>  networks: {<br>    irys: {<br>      url: &quot;https://testnet-rpc.irys.xyz/v1/execution-rpc&quot;,<br>      chainId: 1270,<br>      accounts: [process.env.PRIVATE_KEY]<br>    }<br>  }<br>};</pre><p>Create .env:</p><pre>PRIVATE_KEY=&quot;YOUR_METAMASK_PRIVATE_KEY&quot;<br>CONTRACT_ADDRESS=&quot;YOUR_DEPLOYED_CONTRACT_ADDRESS&quot;</pre><h3>4. Deploy Contract</h3><p>Create scripts/deploy.js:</p><pre>const hre = require(&quot;hardhat&quot;);<br><br>async function main() {<br>  const License = await hre.ethers.getContractFactory(&quot;DataLicense&quot;);<br>  const license = await License.deploy();<br>  <br>  console.log(`Contract deployed to: ${license.target}`);<br>  console.log(`Explorer: https://testnet-explorer.irys.xyz/address/${license.target}`);<br>}<br><br>main().catch((error) =&gt; {<br>  console.error(error);<br>  process.exitCode = 1;<br>});</pre><p>Run deployment:</p><pre>npx hardhat run scripts/deploy.js --network irys</pre><p>Expected Output:</p><pre>Contract deployed to: 0xDD...0c9<br>Explorer: https://testnet-explorer.irys.xyz/address/0xDD...0c9</pre><p><strong>Note: </strong>This deployment uses Hardhat to interact with IrysVM, enabling the smart contract to run on the Irys testnet.</p><h3>5. Upload Data to Irys</h3><p>Create upload.js:</p><pre>import Irys from &#39;@irys/sdk&#39;;<br>import { ethers } from &#39;ethers&#39;;<br>import * as dotenv from &#39;dotenv&#39;;<br>import { randomBytes } from &#39;crypto&#39;;<br>import { createCipheriv, createDecipheriv } from &#39;crypto&#39;;<br><br>dotenv.config();<br><br>async function upload() {<br>  try {<br>    const provider = new ethers.JsonRpcProvider(&quot;https://testnet-rpc.irys.xyz/v1/execution-rpc&quot;);<br>    const wallet = new ethers.Wallet(process.env.PRIVATE_KEY, provider);<br>    const irys = new Irys({ url: &quot;https://node1.irys.xyz&quot;, token: &quot;ethereum&quot;, key: wallet.privateKey, config: { providerUrl: &quot;https://testnet-rpc.irys.xyz/v1/execution-rpc&quot;, timeout: 60000 } });<br><br>    console.log(&quot;Connected to Irys with address:&quot;, irys.address);<br><br>    // original content<br>    const originalContent = &quot;This is the premium content you paid 0.01 ETH to view! :)&quot;;<br>    const key = randomBytes(32);<br>    const iv = randomBytes(16);<br><br>    // encrypt content<br>    const cipher = createCipheriv(&#39;aes-256-cbc&#39;, key, iv);<br>    let encrypted = cipher.update(originalContent, &#39;utf8&#39;, &#39;hex&#39;);<br>    encrypted += cipher.final(&#39;hex&#39;);<br>    const dataToUpload = `${encrypted}:${iv.toString(&#39;hex&#39;)}`;<br><br>    const tags = [{ name: &quot;Content-Type&quot;, value: &quot;text/encrypted&quot; }, { name: &quot;Encryption&quot;, value: &quot;aes-256-cbc&quot; }];<br>    const receipt = await irys.upload(dataToUpload, { tags });<br><br>    console.log(`<br>      Data uploaded successfully!<br>      ID: ${receipt.id}<br>      Key (for contract): ${key.toString(&#39;hex&#39;)}<br>      View (encrypted): https://gateway.irys.xyz/${receipt.id}<br>    `);<br>  } catch (error) {<br>    console.error(&quot;Upload failed:&quot;, error);<br>  }<br>}<br><br>await upload();</pre><p><strong>Note: </strong>We’re using the upload function from IrysSDK to store encrypted data on the Irys network.</p><p>Run upload:</p><pre>node upload.js</pre><p>Expected Output:</p><pre>Connected to Irys with address: 0x33...de<br>Uploading data...<br><br>      Data uploaded successfully!<br>      ID: Bk...o<br>      Key (for contract): &lt;hex-key&gt;<br>      View (encrypted): https://gateway.irys.xyz/BkD...o</pre><p><strong>Verification:</strong> The gateway link shows encrypted data; content is inaccessible without decryption.</p><h3>6. Register the Data</h3><p>Create register.js:</p><pre>import { ethers } from &#39;ethers&#39;;<br>import * as dotenv from &#39;dotenv&#39;;<br><br>dotenv.config();<br><br>async function register(dataId, key) {<br>  try {<br>    // 1. Validate input<br>    if (!dataId || !process.env.CONTRACT_ADDRESS) throw new Error(&quot;Missing dataId or CONTRACT_ADDRESS in .env&quot;);<br><br>    // 2. Initialize provider<br>    const provider = new ethers.JsonRpcProvider(&quot;https://testnet-rpc.irys.xyz/v1/execution-rpc&quot;, 1270);<br>    const signer = new ethers.Wallet(process.env.PRIVATE_KEY, provider);<br><br>    // 3. Contract setup with full ABI<br>    const contract = new ethers.Contract(<br>      process.env.CONTRACT_ADDRESS,<br>      [<br>        &quot;function registerData(bytes32 dataId, uint256 fee, bytes memory key) external&quot;,<br>        &quot;function accessFees(bytes32) view returns (uint256)&quot; // Added back<br>      ],<br>      signer<br>    );<br><br>    // 4. Check if already registered<br>    const existingFee = await contract.accessFees(ethers.id(dataId));<br>    if (existingFee &gt; 0) {<br>      console.log(&quot;⚠️ Data already registered with fee:&quot;, ethers.formatEther(existingFee));<br>      return;<br>    }<br><br>    // 5. Register with 0.01 ETH fee and key<br>    const tx = await contract.registerData(ethers.id(dataId), ethers.parseEther(&quot;0.01&quot;), key); // This interacts with IrysVM to register the data ID and key in the smart contract.<br>    console.log(`<br>      📝 Registration sent!<br>      TX Hash: ${tx.hash}<br>      Explorer: https://testnet-explorer.irys.xyz/tx/${tx.hash}<br>    `);<br>    await tx.wait();<br>    console.log(&quot;✅ Registration confirmed!&quot;);<br>  } catch (error) {<br>    console.error(&quot;Registration failed:&quot;, error.message);<br>  }<br>}<br><br>// Usage: node register.js &lt;dataId&gt; &lt;hex-key&gt;<br>const dataId = process.argv[2];<br>const key = Buffer.from(process.argv[3], &#39;hex&#39;);<br><br>if (!dataId || !key) {<br>  console.log(&quot;Usage: node register.js &lt;dataId&gt; &lt;hex-key-from-upload&gt;&quot;);<br>  process.exit(1);<br>}<br><br>await register(dataId, key);</pre><p>Run register (Remember to update your CONTRACT_ADDRESS in .env):</p><pre>node register.js &lt;dataId: BkD...o&gt; &lt;hex-key-from-upload-log&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHRcZrdOqEd4ML6Ky7cotg.png" /></figure><h3>7. Frontend Integration</h3><p>Create frontend/index.html:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>&lt;head&gt;<br>  &lt;title&gt;Irys Paywall&lt;/title&gt;<br>  &lt;script src=&quot;https://cdn.jsdelivr.net/npm/ethers@5.7.2/dist/ethers.umd.min.js&quot;&gt;&lt;/script&gt;<br>  &lt;script src=&quot;https://cdnjs.cloudflare.com/ajax/libs/crypto-js/4.1.1/crypto-js.min.js&quot;&gt;&lt;/script&gt;<br>  &lt;script src=&quot;https://cdn.jsdelivr.net/npm/canvas-confetti@1.5.1/dist/confetti.browser.min.js&quot;&gt;&lt;/script&gt;<br>  &lt;style&gt;<br>    body { font-family: Arial; max-width: 600px; margin: 0 auto; padding: 20px; }<br>    #content { padding: 20px; border: 1px solid #eee; margin: 20px 0; min-height: 100px; }<br>    button { padding: 10px 15px; background: #4CAF50; color: white; border: none; cursor: pointer; }<br>    button:disabled { background: #cccccc; }<br>  &lt;/style&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>  &lt;h1&gt;Premium Content&lt;/h1&gt;<br>  &lt;div id=&quot;content&quot;&gt;🔒 Content locked - Payment required&lt;/div&gt;<br>  &lt;button id=&quot;payButton&quot;&gt;Pay 0.01 ETH to Unlock&lt;/button&gt;<br>  &lt;p id=&quot;message&quot;&gt;&lt;/p&gt;<br>  &lt;script src=&quot;app.js&quot;&gt;&lt;/script&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><h3>8. Test the Paywall</h3><p>Create frontend/app.js:</p><pre>document.addEventListener(&#39;DOMContentLoaded&#39;, async () =&gt; {<br>  const CONTRACT_ADDRESS = &quot;YOUR_DEPLOYED_CONTRACT_ADDRESS&quot;;<br>  const DATA_ID = &quot;YOUR_DATA_ID&quot;;<br><br>  const contractABI = [<br>    &quot;function accessFees(bytes32) view returns (uint256)&quot;,<br>    &quot;function payForAccess(bytes32) payable&quot;,<br>    &quot;function getDecryptionKey(bytes32) view returns (bytes)&quot;<br>  ];<br><br>  const contentDiv = document.getElementById(&quot;content&quot;);<br>  const payButton = document.getElementById(&quot;payButton&quot;);<br>  const messageP = document.getElementById(&quot;message&quot;);<br><br>  if (!window.ethereum) {<br>    messageP.textContent = &quot;Please install MetaMask!&quot;;<br>    return;<br>  }<br><br>  try {<br>    const provider = new ethers.providers.Web3Provider(window.ethereum);<br>    await provider.send(&quot;eth_requestAccounts&quot;, []);<br>    const signer = provider.getSigner();<br>    const contract = new ethers.Contract(CONTRACT_ADDRESS, contractABI, signer);<br><br>    const dataIdBytes = ethers.utils.id(DATA_ID);<br>    const fee = await contract.accessFees(dataIdBytes);<br>    if (fee.toString() === &quot;0&quot;) throw new Error(&quot;Data not registered&quot;);<br><br>    payButton.onclick = async () =&gt; {<br>      payButton.disabled = true;<br>      messageP.textContent = &quot;Processing payment...&quot;;<br><br>      try {<br>        const tx = await contract.payForAccess(dataIdBytes, { value: fee }); // Interacts with IrysVM to process the payment transaction.<br>        messageP.textContent = `Waiting for confirmation (TX: ${tx.hash})...`;<br>        const receipt = await tx.wait();<br>        if (receipt.status === 1) {<br>          const keyHex = await contract.getDecryptionKey(dataIdBytes); // Retrieves the decryption key from IrysVM after payment.<br>          const response = await fetch(`https://gateway.irys.xyz/${DATA_ID}`);<br>          const encryptedData = await response.text();<br>          const [encrypted, ivHex] = encryptedData.split(&#39;:&#39;);<br><br>          const CryptoJS = window.CryptoJS;<br>          const key = CryptoJS.enc.Hex.parse(keyHex.slice(2));<br>          const iv = CryptoJS.enc.Hex.parse(ivHex);<br>          const encryptedBytes = CryptoJS.enc.Hex.parse(encrypted);<br>          const decrypted = CryptoJS.AES.decrypt({ ciphertext: encryptedBytes }, key, { iv: iv }).toString(CryptoJS.enc.Utf8);<br><br>          contentDiv.textContent = decrypted;<br>          payButton.style.display = &quot;none&quot;;<br>          messageP.textContent = &quot;Unlocked! Enjoy the content!&quot;;<br>          if (window.confetti) window.confetti();<br>        } else {<br>          throw new Error(&quot;Transaction failed&quot;);<br>        }<br>      } catch (error) {<br>        messageP.textContent = `Error: ${error.message.split(&quot;(&quot;)[0]}. Check MetaMask.`;<br>        console.error(&quot;Transaction error:&quot;, error);<br>        payButton.disabled = false;<br>      }<br>    };<br><br>  } catch (error) {<br>    messageP.textContent = `Error: ${error.message.split(&quot;(&quot;)[0]}`;<br>    console.error(error);<br>  }<br>});</pre><p>Run the System:</p><pre>npx serve frontend</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhQtFb0mvi5G40W4IPKWow.png" /></figure><p>Visit <a href="http://localhost:3000.">http://localhost:3000</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsB_qp69kg6tPKr14YNmBw.png" /></figure><h3>User Flow:</h3><ul><li>Accept MetaMask connection prompt, if it comes</li><li>Click “Pay 0.01 ETH,” sign the transaction, and wait for confirmation.</li><li>Content unlocks with confetti after payment.</li></ul><h3>Conclusion</h3><p>We’ve built a secure pay-per-access system where:</p><ul><li>Data is encrypted and stored affordably on Irys using the IrysSDK.</li><li>Payments are enforced on-chain via IrysVM smart contracts.</li><li>Creators earn automatically, with content unlocking only after payment.</li><li>A fun confetti effect celebrates the unlock!</li></ul><h4>Resources:</h4><ul><li><a href="https://docs.irys.xyz/">Irys Documentation</a></li><li><a href="https://github.com/MITCHYUGAN/IRYS-DATA-LICENSE-Tutorial">GitHub Repo</a></li></ul><h4>Happy building with Irys 💚!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b76d5d993188" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a React App with Irys on Vite: A Step-by-Step Guide to Uploading Data to the Programmable…]]></title>
            <link>https://medium.com/@zizicrypt/building-a-react-app-with-irys-on-vite-a-step-by-step-guide-to-uploading-data-to-the-programmable-c3acad7e077b?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3acad7e077b</guid>
            <category><![CDATA[iry]]></category>
            <category><![CDATA[data-chains]]></category>
            <category><![CDATA[vites]]></category>
            <category><![CDATA[programmable]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Fri, 09 May 2025 23:47:10 GMT</pubDate>
            <atom:updated>2025-08-25T21:36:44.103Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a React App with Irys on Vite: A Step-by-Step Guide to Uploading Data to the Programmable Datachain</h3><p>Irys is revolutionizing blockchain with its programmable datachain, combining affordable data storage and smart contract execution in a single network. As a developer, you can leverage Irys to build data-driven dApps, especially for use cases like AI, NFTs, or DeFi. In this guide, I’ll walk you through setting up a React app using Vite to connect to Irys’s testnet, authenticate with MetaMask, and upload data to the datachain. We’ll also explore adding metadata tags to categorize your uploads, making them queryable for future use. This tutorial is perfect for developers looking to explore Irys’s capabilities on its alpha testnet. Let’s get started!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXeQDQpCh-kPxr3KefNKtg.png" /></figure><h3>Why Build with Irys?</h3><p>Irys is the world’s first programmable datachain, designed to make data active and usable by smart contracts. Unlike traditional datachains that only store data, Irys integrates storage and execution via IrysVM, a fork of the Ethereum Virtual Machine (EVM). This means you can store large datasets affordably and interact with them programmatically — perfect for building scalable, data-intensive applications. In this guide, we’ll use Irys’s SDK to upload data to the testnet, demonstrating how easy it is to get started.</p><h3>Prerequisites</h3><p>Before we begin, ensure you have:</p><ul><li>Node.js (v16 or higher) and npm installed.</li><li>A MetaMask wallet with testnet ETH (e.g., Sepolia ETH for funding on Irys’s devnet).</li><li>A code editor like VS Code.</li><li>Basic familiarity with React and JavaScript.</li></ul><h3>Step 1: Set Up a React + Vite Project</h3><p>Let’s create a new React project using Vite, a fast and lightweight build tool.</p><h4>Create a New Project:</h4><p>Open your terminal, create a directory, and initialize a Vite project:</p><pre>mkdir irys-vite<br>cd irys-vite<br>npm create vite@latest .</pre><ul><li>Select React as the framework.</li><li>Choose JavaScript (or TypeScript if preferred).</li><li>Once the setup completes, install dependencies:</li></ul><pre>npm install</pre><h4>Start the Development Server:</h4><p>Run the following to ensure your project is set up correctly:</p><pre>npm run dev</pre><p>Open <a href="http://localhost:5173/">http://localhost:5173</a> in your browser to confirm the default React app is running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Vs3Yc5GhaZY5FM-BG9cfA.png" /></figure><h3>Step 2: Install Irys SDK and Dependencies</h3><p>To interact with Irys, we need to install the Irys SDK, Ethers for wallet integration, and Axios for network requests.</p><p>Run the following command to install all required packages:</p><pre>npm install \<br>    @irys/web-upload \<br>    @irys/web-upload-ethereum \<br>    @irys/web-upload-ethereum-ethers-v6 \<br>    ethers@6 \<br>    axios</pre><ul><li>@irys/web-upload provides the core functionality for uploading data to Irys.</li><li>@irys/web-upload-ethereum enables Ethereum-based payments.</li><li>@irys/web-upload-ethereum-ethers-v6 adapts Ethers v6 for Irys.</li><li>ethers@6 helps connect to MetaMask.</li><li>axioshandles HTTP requests.</li></ul><h3>Step 3: Add Node Polyfills for Vite</h3><p>Vite doesn’t automatically polyfill Node.js core modules like crypto, stream, or path, which are required by the Irys SDK. Let’s add these polyfills.</p><h4>Install Polyfill Packages:</h4><pre>npm install --save-dev \<br>    crypto-browserify \<br>    stream-browserify \<br>    os-browserify \<br>    path-browserify \<br>    vite-plugin-node-polyfills</pre><h4>Update vite.config.js:</h4><p>Modify your vite.config.js to include the polyfills:</p><pre>import { defineConfig } from &#39;vite&#39;;<br>import react from &#39;@vitejs/plugin-react&#39;;<br>import { nodePolyfills } from &#39;vite-plugin-node-polyfills&#39;;<br><br>export default defineConfig({<br>  plugins: [<br>    react(),<br>    nodePolyfills({<br>      globals: {<br>        Buffer: true,<br>        global: true,<br>        process: true,<br>      },<br>      protocolImports: true,<br>    }),<br>  ],<br>  resolve: {<br>    alias: {<br>      crypto: &#39;crypto-browserify&#39;,<br>      stream: &#39;stream-browserify&#39;,<br>      os: &#39;os-browserify/browser&#39;,<br>      path: &#39;path-browserify&#39;,<br>    },<br>  },<br>});</pre><h4>Restart the Development Server:</h4><p>Stop the server (Ctrl+C) and restart it:</p><pre>npm run dev</pre><h3>Step 4: Connect to Irys and Authenticate with MetaMask</h3><p>Now, let’s modify App.jsx to connect to Irys’s devnet and authenticate with MetaMask. We’ll also add functionality to check your balance on the Irys network.</p><p>Replace the contents of src/App.jsx with the following:</p><pre>import { useState } from &quot;react&quot;;<br>import { ethers } from &quot;ethers&quot;;<br>import { WebUploader } from &quot;@irys/web-upload&quot;;<br>import { WebEthereum } from &quot;@irys/web-upload-ethereum&quot;;<br>import { EthersV6Adapter } from &quot;@irys/web-upload-ethereum-ethers-v6&quot;;<br><br>function App() {<br>  const [walletStatus, setWalletStatus] = useState(&quot;Not connected&quot;);<br>  const [irysStatus, setIrysStatus] = useState(&quot;Not connected&quot;);<br>  const [balance, setBalance] = useState(&quot;Not checked&quot;);<br>  const [irysUploader, setIrysUploader] = useState(null);<br><br>  const connectWallet = async () =&gt; {<br>    if (typeof window.ethereum === &#39;undefined&#39;) {<br>      setWalletStatus(&quot;No Ethereum provider found. Please install MetaMask.&quot;);<br>      return;<br>    }<br><br>    try {<br>      const provider = new ethers.BrowserProvider(window.ethereum);<br>      await provider.send(&quot;eth_requestAccounts&quot;, []);<br>      const signer = await provider.getSigner();<br>      const address = await signer.getAddress();<br>      setWalletStatus(`Connected: ${address}`);<br>    } catch (error) {<br>      console.error(&quot;Error connecting to wallet:&quot;, error);<br>      setWalletStatus(&quot;Error connecting to wallet&quot;);<br>    }<br>  };<br><br>  const connectIrys = async () =&gt; {<br>    if (typeof window.ethereum === &#39;undefined&#39;) {<br>      setIrysStatus(&quot;No Ethereum provider found. Please install MetaMask.&quot;);<br>      return;<br>    }<br><br>    try {<br>      const provider = new ethers.BrowserProvider(window.ethereum);<br>      const rpcURL = &quot;https://rpc.sepolia.dev&quot;; // Use a current RPC URL from chainlist.org<br>      const uploader = await WebUploader(WebEthereum)<br>        .withAdapter(EthersV6Adapter(provider))<br>        .withRpc(rpcURL)<br>        .devnet();<br>      setIrysUploader(uploader);<br>      setIrysStatus(`Connected to Irys: ${uploader.address}`);<br>    } catch (error) {<br>      console.error(&quot;Error connecting to Irys:&quot;, error);<br>      setIrysStatus(&quot;Error connecting to Irys&quot;);<br>    }<br>  };<br><br>  const checkBalance = async () =&gt; {<br>    if (!irysUploader) {<br>      setBalance(&quot;Please connect to Irys first.&quot;);<br>      return;<br>    }<br>  <br>    try {<br>      const balanceInmIrys = await irysUploader.getLoadedBalance(); // Use getLoadedBalance instead<br>      const balanceFormatted = irysUploader.utils.fromAtomic(balanceInmIrys); // Convert from mIRYS to IRYS<br>      setBalance(`Balance: ${balanceFormatted} ${irysUploader.token}`);<br>    } catch (error) {<br>      console.error(&quot;Error checking balance:&quot;, error);<br>      setBalance(&quot;Error checking balance&quot;);<br>    }<br>  };<br><br>  return (<br>    &lt;div style={{ padding: &quot;20px&quot; }}&gt;<br>      &lt;h1&gt;Irys Programmable Datachain Demo&lt;/h1&gt;<br>      &lt;button onClick={connectWallet}&gt;Connect Wallet&lt;/button&gt;<br>      &lt;p&gt;{walletStatus}&lt;/p&gt;<br>      &lt;button onClick={connectIrys}&gt;Connect Irys&lt;/button&gt;<br>      &lt;p&gt;{irysStatus}&lt;/p&gt;<br>      &lt;button onClick={checkBalance}&gt;Check Balance&lt;/button&gt;<br>      &lt;p&gt;{balance}&lt;/p&gt;<br>    &lt;/div&gt;<br>  );<br>}<br><br>export default App;</pre><h4>What’s Happening Here?</h4><ul><li><strong>Wallet Connection:</strong> The connectWallet function uses Ethers to connect to MetaMask and retrieve the user’s address.</li><li><strong>Irys Connection:</strong> The connectIrys function connects to Irys’s devnet using an RPC URL (you might need to update rpcURL with a current one from <a href="https://chainlist.org/">chainlist.org</a> if you encounter RPC errors).</li><li><strong>Balance Check:</strong> The checkBalance function retrieves your balance in mIRYS (Irys’s atomic unit) on the devnet.</li></ul><h4>Test It Out</h4><ul><li>Ensure MetaMask is installed and set to the Sepolia testnet.</li><li>Run npm run dev and open the app in your browser.</li><li>Click “Connect Wallet” to authenticate with MetaMask.</li><li>Click “Connect Irys” to connect to the devnet.</li><li>Click “Check Balance” to see your mIRYS balance (you may need to fund your account using the testnet faucet first).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*knk1OtG_cBo9I7N1R4ZBdg.png" /></figure><h3>Step 5: Fund Your Irys Account</h3><p>Before uploading data, you need to fund your Irys account with testnet tokens. Let’s add a function to fund your account with 0.01 ETH (testnet ETH on Sepolia).</p><p>Add the following function to App.jsx above the return statement:</p><pre>const fundAccount = async () =&gt; {<br>  if (!irysUploader) {<br>    alert(&quot;Please connect to Irys first.&quot;);<br>    return;<br>  }<br><br>  try {<br>    const fundTx = await irysUploader.fund(irysUploader.utils.toAtomic(0.01));<br>    alert(`Successfully funded ${irysUploader.utils.fromAtomic(fundTx.quantity)} ${irysUploader.token}`);<br>  } catch (error) {<br>    console.error(&quot;Error when funding:&quot;, error);<br>    alert(&quot;Error when funding&quot;);<br>  }<br>};</pre><p>Add a button to trigger this function in the JSX:</p><pre>&lt;button onClick={fundAccount}&gt;Fund Account (0.01 ETH)&lt;/button&gt;</pre><h4>Test the Funding</h4><ul><li>Click “Fund Account (0.01 ETH)” after connecting to Irys.</li><li>Approve the transaction in MetaMask (ensure you have Sepolia ETH).</li><li>Check your balance again to confirm the funds were added.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1P8nPQNOuJaQShOUSkuXw.png" /></figure><h3>Step 6: Upload Data with Metadata Tags</h3><p>Now, let’s upload a simple string to Irys’s devnet and add metadata tags to categorize it. Metadata tags make your data queryable via GraphQL, which is useful for organizing uploads.</p><p>Add the following function to App.jsx above the return statement:</p><pre>const uploadData = async () =&gt; {<br>  if (!irysUploader) {<br>    alert(&quot;Please connect to Irys first.&quot;);<br>    return;<br>  }<br><br>  const dataToUpload = &quot;Hello, Irys Programmable Datachain!&quot;;<br>  const tags = [{ name: &quot;application-id&quot;, value: &quot;IrysDemoApp&quot; }];<br><br>  try {<br>    const receipt = await irysUploader.upload(dataToUpload, { tags });<br>    alert(`Data uploaded ==&gt; https://gateway.irys.xyz/${receipt.id}`);<br>  } catch (error) {<br>    console.error(&quot;Error when uploading:&quot;, error);<br>    alert(&quot;Error when uploading&quot;);<br>  }<br>};</pre><p>Add a button to trigger the upload:</p><pre>&lt;button onClick={uploadData}&gt;Upload Data&lt;/button&gt;</pre><h4>What’s Happening Here?</h4><ul><li>We’re uploading a string (“Hello, Irys Programmable Datachain!”) to Irys’s devnet.</li><li>The tags array adds an application-id tag, which helps categorize this upload as part of “IrysDemoApp.” You can query this later using GraphQL.</li><li>The receipt.id provides a transaction ID, which you can use to access the data at https://gateway.irys.xyz/&lt;receipt.id&gt;.</li></ul><h4>Test the Upload</h4><ul><li>Click “Upload Data” after funding your account (minimum of 0.01).</li><li>Approve the transaction in MetaMask.</li><li>Once successful, visit the URL in the alert to view your uploaded data. You’ll be prompted to save the file. Go ahead and then open it in Notepad to see your message.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrmwIQd6ZsF0gXGSwDhAGA.png" /></figure><h3>Step 7: Explore Further with Irys</h3><p>You’ve now connected to Irys’s devnet, funded your account, and uploaded data with metadata tags! Here are some next steps to dive deeper:</p><ul><li>Upload Files or Folders: Use irysUploader.uploadFile or irysUploader.uploadFolder to store images, videos, or entire directories (see the <a href="https://docs.irys.xyz/build/d/quickstart">Irys docs</a> for examples).</li><li>Experiment with Programmable Data: Write a Solidity smart contract using IrysVM to interact with your uploaded data, as shown in the <a href="https://docs.irys.xyz/build/programmability/programmable-data">Programmable Data Quickstart</a>.</li><li>Query Your Data: Use GraphQL to query your uploads by the application-id tag at a gateway like <a href="https://gateway.irys.xyz./">https://gateway.irys.xyz.</a></li></ul><p>Irys’s testnet (Chain ID: 1270, RPC: <a href="https://testnet-rpc.irys.xyz/v1/execution-rpc)">https://testnet-rpc.irys.xyz/v1/execution-rpc)</a> is EVM-compatible, so you can use tools like MetaMask and Ethers to build more complex dApps.</p><h3>Conclusion</h3><p>Irys makes it easy to build data-driven applications by combining storage and execution in a single programmable datachain. In this guide, we set up a React app with Vite, connected to Irys’s devnet, and uploaded data with metadata tags — all in a few simple steps. As a Technical Educator in Irys’s Datapunk Guilds Program, I’m excited to create more tutorials and workshops to help developers explore this innovative platform. Join the Irys community by following <a href="https://x.com/irys_xyz">@irys_xyz</a> on X and start building on the testnet today</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3acad7e077b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring Irys’s Programmable Datachain in the Role of the Developer: A Guide on Programmable Data…]]></title>
            <link>https://medium.com/@zizicrypt/exploring-iryss-programmable-datachain-in-the-role-of-the-developer-a-guide-on-programmable-data-5cb56fb1ec6f?source=rss-c5536556bb3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cb56fb1ec6f</guid>
            <category><![CDATA[programmable]]></category>
            <category><![CDATA[irs-reporting]]></category>
            <category><![CDATA[data-chains]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Zizi Crypto]]></dc:creator>
            <pubDate>Fri, 09 May 2025 10:58:10 GMT</pubDate>
            <atom:updated>2025-05-09T11:01:09.865Z</atom:updated>
            <content:encoded><![CDATA[<h3>Exploring Irys’s Programmable Datachain in the Role of the Developer: A Guide on Programmable Data and IrysVM</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4xfkgNAB2t2ZXDJlF_osBA.png" /></figure><p>Irys(the very first programmable datachain in history) is the game-changer. AI was the best for developers; the applications of traditional technology worked only as a storage utility, while Irys, on the other hand, is data activation. It showcases the programmability aspect of the data, where smart contracts have the power to relate to the data directly. My plan here is to show you what programmable data is, how IrysVM enables it, and why it is a necessity for developers. So let’s take a dive into Irys’s datachain and explore an innovative solution for your next project!</p><h3>What Is a Programmable Datachain?</h3><p>A datachain represents the epitome of a blockchain design that is storage-optimized in a way that transaction costs do not inflate, unlike heavy-execution blockchains such as Ethereum or Solana where storage costs for them could go through the roof. Data storage on chain seemed pretty simple in the early days, for example, Arweave or Filecoin, what that was actually doing was it was economically solving the storage problem; however, the data was merely stored, it was at rest and with the menace of being locked up, it was not in a position to interact with the applications or smart contracts.</p><p>A typical datachain would make data active through programmability. The data on Irys goes beyond being stored because it can carry not only instructions but also properties that enable it to act, change, and work in any application. Data is a living being that can do such things as: it can enforce rights, automate royalties, grant access, or execute logic through smart contracts. This is what brings out the concept of Irys’s programmable datachain, and undoubtedly, it is a very viable solution for developers of the dApps of the future that need data to do more than just exist.</p><h3>How Irys Enables Programmable Data with IrysVM</h3><p>IrysVM is the engine that powers Irys’s programmable data by being a virtual machine optimized to run storage and execution with coherence. IrysVM has a completely new approach, one that integrates both data and contract execution, and it is not shared with blockchains, where data and smart contract execution are kept separate. The latter brings them together in a single network, leading to direct data accessibility and contract execution at a fraction of the cost.</p><h4>Why IrysVM Matters</h4><p>IrysVm offers the same functionalities as Ethereum Virtual Machine (EVM) except for one important difference: it is designed to get all the necessary information from Irys’s data record. This allows smart contracts to communicate with the local data without external systems, having to bear the additional costs and complexity that they normally do. Here’s how it works:</p><ul><li><strong>Direct Data Access:</strong> Smart contracts on IrysVM can access the Publish Ledger by using such methods as range specifiers (e.g., &lt;partition_index&gt;:&lt;offset&gt;:&lt;chunk_count&gt;), ensuring efficient retrieval.</li><li><strong>Embedded Properties:</strong> Data on Irys carries programmable metadata, such as ownership rights, access controls, or royalty rules, which smart contracts can enforce automatically.</li><li><strong>Cost Efficiency:</strong> IrysVM separates storage and computation into different processing lanes, preventing competition for blockspace and keeping transaction costs predictable.</li></ul><p>For developers, this means you can build applications where data is functional, adaptable, and affordable — perfect for use cases like AI, NFTs, or DeFi.</p><h4><strong>A Practical Example:</strong> Automating NFT Royalties</h4><p>Let’s say you’re building an NFT marketplace on Irys. You want to ensure creators receive royalties automatically on every sale. Here’s how Irys’s programmable data makes this possible:</p><ul><li><strong>Upload NFT Metadata:</strong> You upload the NFT’s metadata (e.g., image, description) to Irys’s Submit Ledger. Once verified, it’s promoted to the Publish Ledger, where it’s permanently stored.</li><li><strong>Embed Royalty Rules:</strong> Using IrysVM, you attach programmable metadata to the NFT data, specifying a 5% royalty for the creator’s wallet address.</li><li><strong>Smart Contract Execution:</strong> A smart contract on IrysVM references this data during a sale, automatically enforcing the royalty by transferring 5% of the sale price to the creator.</li></ul><p>On a traditional datachain, you’d need to store the metadata offchain or on an expensive execution chain, then use an external system to enforce royalties — adding complexity and cost. Irys simplifies this by keeping everything onchain, making data programmable, and reducing fees.</p><h3>Why Developers Should Care</h3><p>Irys’s programmable datachain, powered by IrysVM, opens up new possibilities for developers:</p><ul><li><strong>Simplified Workflows:</strong> No more piecing together fragmented storage and execution systems. Irys combines both in one network, saving time and money.</li><li><strong>New Use Cases:</strong> Programmable data enables applications like AI models with onchain training data, NFT marketplaces with automated royalties, or DeFi protocols with verifiable data feeds — all at a lower cost.</li><li><strong>Predictable Costs:</strong> Irys’s pricing model (e.g., $0.01/MB for programmable data during testnet) and separate blocklanes ensure stable fees, even as your app scales.</li></ul><p>See Irys as a platform where developers can innovate without the usual blockchain headaches. It’s a datachain that doesn’t just store data — it brings it to life.</p><h3>Get Started with Irys</h3><p>Irys is currently in testnet, and it’s the perfect time to explore its programmable datachain. Here’s how to get started:</p><ol><li><strong>Join the Community:</strong> Follow <a href="https://x.com/irys_xyz">@irys_xyz</a> on X and join <a href="https://discord.gg/irys">Discord </a>to stay updated on testnet developments.</li><li><strong>Explore the Docs:</strong> Check out <a href="https://docs.irys.xyz/">docs.irys.xyz</a> for developer guides on interacting with IrysVM and uploading data.</li><li><strong>Build Something:</strong> Try uploading data to the Submit Ledger and writing a simple smart contract on IrysVM to interact with it. Start small, like embedding ownership metadata, and scale from there.</li></ol><h3>Conclusion</h3><p>Irys’s vision of a programmable datachain is inspiring, and I’m excited to contribute as a Technical Educator in their Datapunk Guilds Program. I’ll be creating more guides, hosting webinars, and supporting devs in building on Irys. Follow me on X(<a href="https://x.com/zizicrypt">@zizicrypt</a>) for more Web3 insights, and let’s shape the future of data onchain with Irys!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cb56fb1ec6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>