<?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 Serkan A. on Medium]]></title>
        <description><![CDATA[Stories by Serkan A. on Medium]]></description>
        <link>https://medium.com/@AlglSerkan?source=rss-e7f48181c487------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6Hqx40j6-haV6KMjoTOb1A@2x.jpeg</url>
            <title>Stories by Serkan A. on Medium</title>
            <link>https://medium.com/@AlglSerkan?source=rss-e7f48181c487------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:23:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@AlglSerkan/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[Initia: Deploy your Future of Interwoven Rollup L2 (A.K.A: Minitia) in 10 minutes]]></title>
            <link>https://medium.com/@AlglSerkan/deploy-your-future-of-interwoven-rollup-a-k-a-minitia-in-10-minutes-71113dddd883?source=rss-e7f48181c487------2</link>
            <guid isPermaLink="false">https://medium.com/p/71113dddd883</guid>
            <category><![CDATA[rollup]]></category>
            <category><![CDATA[initia]]></category>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[modular]]></category>
            <category><![CDATA[l2]]></category>
            <dc:creator><![CDATA[Serkan A.]]></dc:creator>
            <pubDate>Thu, 04 Jul 2024 11:47:23 GMT</pubDate>
            <atom:updated>2024-07-07T11:28:20.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0WjFeAw2RCZAqCmPT2tpw.png" /></figure><h3>What is Initia?</h3><p>Initia is a blockchain platform (Layer 1) designed with advanced technology (Layer 2) to support a network of connected, modular sub-networks. This setup boosts scalability, efficiency, and flexibility within the Initia ecosystem. The unique Initia technology stack ensures smooth integration between Layer 1 and Layer 2, enabling developers to create mechanisms that align the interests of both users and developers. Essentially, Initia incorporates specific Layer 2 solutions (minitias) directly into its foundational Layer 1, making it a network of interconnected rollups.</p><h3>Initia’s Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPShNXMJo1v5suJb2iKVow.png" /></figure><p>Initia’s architecture, also known as Omnitia, integrates Minitias into a robust two-layer platform. Here’s a breakdown of its components:</p><p><strong>Initia Orchestration Layer (Layer 1)</strong>: Known as the “Initia Base Chain,” this foundational blockchain layer oversees network security, consensus, governance, interoperability, liquidity, and inter-chain messaging.</p><p><strong>Initia Rollups (Layer 2s)</strong>: These are referred to as “Minitia” or mini Initias. They are Layer 2 solutions built on the Initia Base Chain to enhance scalability and transaction throughput. Minitias can operate in EVM, MoveVM, or WasmVM environments, leveraging the CosmosSDK.</p><p><strong>Initia Optimistic Rollup Framework (OPinit Stack)</strong>: The OPinit Stack is Initia’s Optimistic Rollup (OR) framework, developed using the CosmosSDK. It ensures the security of Initia Rollups through fraud proofs and rollbacks.</p><p><strong>Interoperability/Bridging Middleware</strong>: Combining the Inter-Blockchain Communication (IBC) protocol with selected bridge providers, this middleware facilitates seamless cross-chain asset and data transfers, as well as interactions between Layer 1 and Layer 2s within Omnitia.</p><p>This architecture enables a cohesive ecosystem where Initia’s Layer 1 and Layer 2 solutions work in tandem to support scalable and interoperable blockchain applications.</p><p>Let’s dive into deploy your own minitia in 10 minutes.</p><h3>Setting up &amp; Starting the Minitia</h3><p>In this step, we’re going to install dependencies, choose your virtual machine (move, wasm, evm) and start minitia via cli.</p><p><a href="https://go.dev/doc/install">Install go (v1.22+)</a></p><p>Download and specify minitia vm. ( I preferred to use MoveVM)</p><pre>export VM=move # one of &quot;move&quot;, &quot;wasm&quot;, or &quot;evm&quot;<br>export MINITIA_VERSION=&quot;0.2.16&quot;<br><br>git clone https://github.com/initia-labs/mini$VM.git<br><br>cd mini$VM<br>git checkout v$MINITIA_VERSION<br>make install<br><br>#verify your installation<br>minitiad version</pre><p>The minitaid CLI provides a utility launch command to simplify the initial setup sequences of minitia. It is designed to automate the process of setting up and configuring your minitia environment.</p><blockquote>Before launching, we must create and fund 5 wallets for validator, bridge executer, output submitter, batch submitter and challenger.</blockquote><p>The launch command allows customization of the minitia and related configurations and parameters through a config.json file.</p><p>Here is the sample config.json file I have created and used for this guide. I have created 5 wallet for testing purpose.</p><pre>{<br>  &quot;l1_config&quot;: {<br>    &quot;chain_id&quot;: &quot;initiation-1&quot;,<br>    &quot;rpc_url&quot;: &quot;https://initia-testnet-rpc.polkachu.com:443&quot;,<br>    &quot;gas_prices&quot;: &quot;0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff&quot;<br>  },<br>  &quot;l2_config&quot;: {<br>    &quot;chain_id&quot;: &quot;oldbutgold-1&quot;,<br>    &quot;denom&quot;: &quot;umin&quot;,<br>    &quot;moniker&quot;: &quot;operator&quot;<br>  },<br>  &quot;op_bridge&quot;: {<br>    &quot;output_submission_start_time&quot;: &quot;2024-07-02T13:00:00.113678+03:00&quot;,<br>    &quot;output_submission_interval&quot;: 3600000000000,<br>    &quot;output_finalization_period&quot;: 3600000000000,<br>    &quot;batch_submission_target&quot;: &quot;l1&quot;<br>  },<br>  &quot;system_keys&quot;: {<br>    &quot;validator&quot;: {<br>      &quot;address&quot;: &quot;init1gfhfujxen8jqgllud3f08fdt88n36t49vzv28a&quot;,<br>      &quot;mnemonic&quot;: &quot;bomb dinner absent siren talent unlock grant enable congress legend gallery change tongue digital invest noise journey now useless please leave quote equip once&quot;<br>    },<br>    &quot;bridge_executor&quot;: {<br>      &quot;address&quot;: &quot;init1tga248dnp4gl5lrw5hyxu8z6v3jkga24awgkhg&quot;,<br>      &quot;mnemonic&quot;: &quot;trash pair report cancel letter bus huge pepper liar swallow tonight muffin carpet hammer response include wood matrix pool country turtle service city shy&quot;<br>    },<br>    &quot;output_submitter&quot;: {<br>      &quot;address&quot;: &quot;init15a3nzt7xjx3ghzj3hc0f66c6cxrfsatfsw7qjl&quot;,<br>      &quot;mnemonic&quot;: &quot;duck seat aisle oblige until sound vacant lake fever blue post olive stick measure matrix speak nation pill broken waste gown senior scare lawn&quot;<br>    },<br>    &quot;batch_submitter&quot;: {<br>      &quot;address&quot;: &quot;init154xvgcpdcaf5uat9tkwz26szsjlwr9ct36ukfs&quot;,<br>      &quot;mnemonic&quot;: &quot;decrease camera butter gorilla reunion club asthma rigid alpha net level elite universe tribe universe spoon lobster cousin spend earn dose auction memory hedgehog&quot;<br>    },<br>    &quot;challenger&quot;: {<br>      &quot;address&quot;: &quot;init193r4nky4thmza3s94udzsc93glrt3450wnt4hp&quot;,<br>      &quot;mnemonic&quot;: &quot;absurd business salad monkey wine load certain large hub captain eternal problem check mother stamp coach valid diagram educate voyage crawl bulk access rifle&quot;<br>    }<br>  },<br>  &quot;genesis_accounts&quot;: [<br>    {<br>      &quot;address&quot;: &quot;init1gfhfujxen8jqgllud3f08fdt88n36t49vzv28a&quot;,<br>      &quot;coins&quot;: &quot;100000000umin&quot;<br>    },<br>    {<br>      &quot;address&quot;: &quot;init1tga248dnp4gl5lrw5hyxu8z6v3jkga24awgkhg&quot;<br>    },<br>    {<br>      &quot;address&quot;: &quot;init15a3nzt7xjx3ghzj3hc0f66c6cxrfsatfsw7qjl&quot;<br>    },<br>    {<br>      &quot;address&quot;: &quot;init154xvgcpdcaf5uat9tkwz26szsjlwr9ct36ukfs&quot;<br>    },<br>    {<br>      &quot;address&quot;: &quot;init193r4nky4thmza3s94udzsc93glrt3450wnt4hp&quot;<br>    }<br>  ]<br>}</pre><p>You must change the following config items in configs.json</p><p><strong>l2_config -&gt; chain_id</strong> the chain ID of the minitia being deployed.</p><p><strong>l2_config -&gt; denom</strong> the base token denom to use for the minitia</p><p><strong>Launch minitiad</strong></p><pre>export L1_CHAIN_ID=initiation-1 #replace with the desired Initia L1 chain ID<br>minitiad launch $L1_CHAIN_ID - with-config config.json</pre><p>Once the launch steps successfully completes, two artifact files will be generated in the directory $HOME/.minitia/artifactand you should get an output similar to the one below:</p><pre>############################################<br>Artifact written to<br>* /Users/initia/.minitia/artifacts/config.json<br>* /Users/initia/.minitia/artifacts/artifact.json<br><br>{<br> &quot;BRIDGE_ID&quot;: &quot;105&quot;,<br> &quot;EXECUTOR_L1_MONITOR_HEIGHT&quot;: &quot;2050600&quot;,<br> &quot;EXECUTOR_L2_MONITOR_HEIGHT&quot;: &quot;55&quot;<br>}</pre><p><strong>Starting the Minitia</strong></p><p>We can now start running our minitia. This process will begin running the minitia and producing blocks.</p><pre>minitiad start</pre><h3>OPInit Programs</h3><p>The OPinit Stack is bolstered by four dedicated bot programs:</p><ul><li>Bridge Executor</li><li>Output Submitter</li><li>Batch Submitter</li><li>Challenger</li></ul><p><strong>Install dependencies</strong></p><p><a href="https://nodejs.org/">NodeJS</a> (v20+)</p><p><a href="https://www.postgresql.org/">PostgreSQL</a></p><p><strong>Clone and build OPInit bots</strong></p><pre>git clone https://github.com/initia-labs/OPinit-bots.git<br>cd OPinit-bots<br>npm install<br>npm run build</pre><h3>Bridge Executor</h3><p>The bridge executor is the core component in minitia rollup, which is charge of following operations via <a href="https://github.com/initia-labs/OPinit/blob/main/specs/l2_bridge.md">L2 Bridge Module</a>:</p><ul><li>Finalize L1 deposit transaction to L2.</li><li>Construct withdraw tx storage Merkle Tree.</li><li>Compute L2 output root.</li><li>Provide the withdrawal proofs (Merkle Proofs) to users.</li></ul><p><strong>1.Set Bridge Executor Config on </strong><strong>.env.executor</strong></p><pre><br>touch .env.executor</pre><p>Here is the sample <strong>.env.executor</strong> file I have created and used for this guide.</p><pre>TYPEORM_CONNECTION=postgres               # database connection (currently only support `postgres`)<br>TYPEORM_HOST=localhost                    # database host<br>TYPEORM_USERNAME=minitia                 # database username<br>TYPEORM_PASSWORD=minitia                 # database password<br>TYPEORM_DATABASE=minitia                  # database name<br>TYPEORM_PORT=5432                         # database port<br>TYPEORM_SYNCHRONIZE=true                  # synchronize database schema<br>TYPEORM_LOGGING=false                     # enable logging<br>TYPEORM_ENTITIES=dist/orm/*Entity.js      # entity path<br><br>L1_GAS_PRICES=0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff # default 0.15uinit<br>L1_CHAIN_ID=initiation-1<br>L2_CHAIN_ID=oldbutgold-1 # need to be same as in config.json<br>L1_LCD_URI=https://lcd.initiation-1.initia.xyz<br>L1_RPC_URI=https://rpc.initiation-1.initia.xyz<br>L2_LCD_URI=http://127.0.0.1:1317<br>L2_RPC_URI=http://127.0.0.1:26657<br><br>BRIDGE_ID=105 # need to be same as in $HOME/.minitia/artifacts/artifacts.json<br><br>EXECUTOR_PORT=5001<br>ENABLE_ORACLE=true<br>EXECUTOR_MNEMONIC=&#39;trash pair report cancel letter bus huge pepper liar swallow tonight muffin carpet hammer response include wood matrix pool country turtle service city shy&#39;         # need to be same as in $HOME/.minitia/artifacts/artifacts.json<br><br># optional config<br> EXECUTOR_L1_MONITOR_HEIGHT=2031212 # I set nearest block height to do not monitor old blocks<br># EXECUTOR_L2_MONITOR_HEIGHT=0<br># SLACK_WEB_HOOK=&#39;&#39;</pre><p><strong>2.Run the Executer</strong></p><pre>npm run prod:executor</pre><p>You should see the similar output after successfully run.</p><pre>024-07-04T11:14:57.537Z [info - Executor]: executor_l1_monitor syncedHeight 2053390<br>::ffff:127.0.0.1 - - [04/Jul/2024:11:15:00 +0000] &quot;POST /api/v0/swarm/peers?timeout=2500ms HTTP/1.1&quot; 404 9<br>2024-07-04T11:15:00.835Z [info - Executor]: executor_l1_monitor syncedHeight 2053400<br>2024-07-04T11:15:02.401Z [info - Executor]: [resurrect - resurrector] No unconfirmed txs found<br>::ffff:127.0.0.1 - - [04/Jul/2024:11:15:03 +0000] &quot;POST /api/v0/swarm/peers?timeout=2500ms HTTP/1.1&quot; 404 9<br>2024-07-04T11:15:03.488Z [info - Executor]:<br>          [handleNewBlock - executor_l1_monitor] Succeeded to update oracle tx in height<br>          currentHeight: 2053403<br>          latestHeight: 2076183<br>          txhash: 2D4DF36889CE035BB5B49BE6CC060EFD1CC4108A4229D1D05DE5EF75B43A3CF3<br><br>2024-07-04T11:15:03.504Z [info - Executor]: [checkSubmissionInterval - executor_l2_monitor] Output index not matched<br>2024-07-04T11:15:03.979Z [info - Executor]: [checkSubmissionInterval - executor_l2_monitor] Output index not matched<br>::ffff:127.0.0.1 - - [04/Jul/2024:11:15:06 +0000] &quot;POST /api/v0/swarm/peers?timeout=2500ms HTTP/1.1&quot; 404 9<br>2024-07-04T11:15:07.291Z [info - Executor]: executor_l1_monitor syncedHeight 2053410</pre><h3>Output Submitter</h3><p>The output submitter takes the output information recorded by the bridge executor and submits them to the Initia L1 to ensure that the minitia’s block are finalized. This is done at a regular, configurable interval.</p><p><strong>1.Set Output Submitter Config on </strong><strong>.env.output</strong></p><pre>touch .env.output</pre><p>Here is the sample <strong>.env.output</strong> file I have created and used for this guide.</p><pre>TYPEORM_CONNECTION=postgres               # database connection (currently only support `postgres`)<br>TYPEORM_HOST=localhost                    # database host<br>TYPEORM_USERNAME=minitia                 # database username<br>TYPEORM_PASSWORD=minitia                 # database password<br>TYPEORM_DATABASE=minitia                   # database name<br>TYPEORM_PORT=5432                         # database port<br>TYPEORM_SYNCHRONIZE=true                  # synchronize database schema<br>TYPEORM_LOGGING=false                     # enable logging<br>TYPEORM_ENTITIES=dist/orm/*Entity.js      # entity path<br><br>L1_GAS_PRICES=0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff<br>L1_CHAIN_ID=initiation-1<br>L2_CHAIN_ID=oldbutgold-1 # need to be same as in config.json<br>L1_LCD_URI=https://lcd.initiation-1.initia.xyz<br>L1_RPC_URI=https://rpc.initiation-1.initia.xyz<br>L2_LCD_URI=http://127.0.0.1:1317<br>L2_RPC_URI=http://127.0.0.1:26657<br><br>BRIDGE_ID=105 # need to be same as in $HOME/.minitia/artifacts/artifacts.json<br><br>OUTPUT_SUBMITTER_MNEMONIC=&#39;duck seat aisle oblige until sound vacant lake fever blue post olive stick measure matrix speak nation pill broken waste gown senior scare lawn&#39;</pre><p><strong>2.Run the Output Submitter</strong></p><pre>npm run prod:output</pre><p>You should see the similar output after successfully run.</p><pre>activate  .env.output<br>Starting worker in mode: output<br>Listening on port 8081 for metrics<br>2024-07-04T11:18:31.044Z [info - Output]: successfully submitted! output index: 6, output root: Hj4gt0geO0S9ILtO9rgY0/TVyDMnLlh0OjQqqMV7fbs= (2168, 2452)<br>2024-07-04T11:18:41.889Z [info - Output]: waiting for output index from DB: 7, processed block number: 2452<br>2024-07-04T11:18:52.118Z [info - Output]: waiting for output index from DB: 7, processed block number: 2452<br>2024-07-04T11:19:02.526Z [info - Output]: waiting for output index from DB: 7, processed block number: 2452<br>2024-07-04T11:19:12.831Z [info - Output]: waiting for output index from DB: 7, processed block number: 2452</pre><h3>Batch Submitter</h3><p>The batch submitter handles aggregating transaction data stored by other bots into batches and submitting them to either the Initia L1 or Celestia to ensure <a href="https://celestia.org/what-is-da/">data availability</a>. I used Initia L1 for this guide.</p><p><strong>1.Set Batch Submitter Config on </strong><strong>.env.batch</strong></p><pre>touch .env.output</pre><p>Here is the sample <strong>.env.batch</strong> file I have created and used for this guide.</p><pre>TYPEORM_CONNECTION=postgres               # database connection (currently only support `postgres`)<br>TYPEORM_HOST=localhost                    # database host<br>TYPEORM_USERNAME=minitia                 # database username<br>TYPEORM_PASSWORD=minitia                 # database password<br>TYPEORM_DATABASE=minitia                   # database name<br>TYPEORM_PORT=5432                         # database port<br>TYPEORM_SYNCHRONIZE=true                  # synchronize database schema<br>TYPEORM_LOGGING=false                     # enable logging<br>TYPEORM_ENTITIES=dist/orm/*Entity.js      # entity path<br><br>L1_GAS_PRICES=0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff<br>L1_CHAIN_ID=initiation-1<br>L2_CHAIN_ID=oldbutgold-1 # need to be same as in config.json<br>L1_LCD_URI=https://lcd.initiation-1.initia.xyz,<br>L1_RPC_URI=https://rpc.initiation-1.initia.xyz,<br>L2_LCD_URI=http://127.0.0.1:1317<br>L2_RPC_URI=http://127.0.0.1:26657<br><br>BRIDGE_ID=105 # need to be same as in $HOME/.minitia/artifacts/artifacts.json<br><br>PUBLISH_BATCH_TARGET=l1<br><br># important: submitting to InitiaL1 needs gas fee and inititation-1 uses below gas prices<br>BATCH_GAS_PRICES=0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff<br><br>BATCH_PORT=5002<br><br>BATCH_SUBMITTER_MNEMONIC=&#39;decrease camera butter gorilla reunion club asthma rigid alpha net level elite universe tribe universe spoon lobster cousin spend earn dose auction memory hedgehog&#39;<br><br># if you use &#39;celestia&#39; as DA, set following configs<br># PUBLISH_BATCH_TARGET=celestia<br># BATCH_CHAIN_ID=arabica-11<br># BATCH_LCD_URI=https://api.celestia-arabica-11.com<br># BATCH_CHAIN_RPC_URI=https://rpc.celestia-arabica-11.com<br># BATCH_GAS_PRICES=&#39;0.2utia&#39;<br># BATCH_DENOM=utia<br># CELESTIA_TOKEN_AUTH=eyJ...<br># CELESTIA_NAMESPACE_ID=00000000000000000000000000000000000000000000000123456789</pre><p><strong>2.Run the Batch Submitter</strong></p><pre>npm run batch</pre><p>You should see the similar output after successfully run.</p><pre>2024-07-03T12:57:15.388Z [info - Batch]: creating connection default to minitia@localhost:5432<br>Listening on port 5002<br>Listening on port 8082 for metrics<br>2024-07-03T12:57:21.067Z [info - Batch]: 1th batch (1, 1) is successfully saved<br>2024-07-03T12:59:01.097Z [info - Batch]: waiting for output index from DB: 2<br>2024-07-03T13:00:41.131Z [info - Batch]: waiting for output index from DB: 2<br>2024-07-03T13:02:21.164Z [info - Batch]: waiting for output index from DB: 2<br>2024-07-03T13:04:01.197Z [info - Batch]: waiting for output index from DB: 2</pre><h3>Challenger</h3><p>The challenger bot is responsible for monitoring and detecting invalid output proposals that are made by the output submitter and preventing them from being recorded on the Initia L1. If an invalid output is detected, it creates a record of it and sends a MsgDeleteOutput transaction on the L1 to dispute the proposal.</p><p><strong>1.Set Challenger Config on </strong><strong>.env.challenger</strong></p><pre>touch .env.challenger</pre><p>Here is the sample <strong>.env.challenger</strong> file I have created and used for this guide.</p><pre>TYPEORM_CONNECTION=postgres               # database connection (currently only support `postgres`)<br>TYPEORM_HOST=localhost                    # database host<br>TYPEORM_USERNAME=minitia                 # database username<br>TYPEORM_PASSWORD=minitia                 # database password<br>TYPEORM_DATABASE=minitia                   # database name<br>TYPEORM_PORT=5432                         # database port<br>TYPEORM_SYNCHRONIZE=true                  # synchronize database schema<br>TYPEORM_LOGGING=false                     # enable logging<br>TYPEORM_ENTITIES=dist/orm/*Entity.js      # entity path<br><br>L1_GAS_PRICES=0.15move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff<br>L1_CHAIN_ID=initiation-1<br>L2_CHAIN_ID=oldbutgold-1 # need to be same as in config.json<br>L1_LCD_URI=https://lcd.initiation-1.initia.xyz<br>L1_RPC_URI=https://rpc.initiation-1.initia.xyz<br>L2_LCD_URI=http://127.0.0.1:1317<br>L2_RPC_URI=http://127.0.0.1:26657<br><br><br>BRIDGE_ID=105 # need to be same as in $HOME/.minitia/artifacts/artifacts.json<br><br>CHALLENGER_MNEMONIC=&#39;absurd business salad monkey wine load certain large hub captain eternal problem check mother stamp coach valid diagram educate voyage crawl bulk access rifle&#39;</pre><p><strong>2.Run the Challenger</strong></p><pre>npm run challenger</pre><p>You should see the similar output after successfully run.</p><pre>npm run challenger<br><br>&gt; @initia/rollup@0.1.17 challenger<br>&gt; WORKER_NAME=challenger node dist/worker/challenger/index.js<br><br>activate  .env.challenger<br>2024-07-04T11:18:34.763Z [info - Challenger]: challenger_l2_monitor syncedHeight 2010<br>2024-07-04T11:18:34.777Z [info - Challenger]: challenger_l2_monitor syncedHeight 2020<br>2024-07-04T11:18:34.889Z [info - Challenger]: challenger_l2_monitor syncedHeight 2030<br>2024-07-04T11:18:34.898Z [info - Challenger]: challenger_l2_monitor syncedHeight 2040</pre><p>CONGRATULATIONS! YOU HAVE SUCCESSFULLY CONFIGURED AND RUNNING YOUR FIRST MINITA!</p><p>To safeguard against spam and maintain network stability, we must set min-gas-prices. In previous config file, we set denom as umin. Let’s set min gas price 0.15umin to our minitia.</p><blockquote>In our genesis config, we set 100000000umin coins to our validator wallet.</blockquote><p>Create and execute message to opchild.</p><pre>echo &quot;{<br>  \&quot;messages\&quot;: [<br>    {<br>      \&quot;@type\&quot;:\&quot;/opinit.opchild.v1.MsgUpdateParams\&quot;,<br>      \&quot;authority\&quot;: \&quot;init1gz9n8jnu9fgqw7vem9ud67gqjk5q4m2w0aejne\&quot;,<br>      \&quot;params\&quot;: {<br>        \&quot;max_validators\&quot;: 100,<br>        \&quot;historical_entries\&quot;: 10000,<br>        \&quot;min_gas_prices\&quot;: [{\&quot;amount\&quot;: \&quot;0.15\&quot;, \&quot;denom\&quot;: \&quot;umin\&quot;}],<br>        \&quot;bridge_executor\&quot;: \&quot;$(minitiad keys show bridge_executer -a)\&quot;,<br>        \&quot;admin\&quot;: \&quot;$(minitiad keys show validator -a)\&quot;,<br>        \&quot;fee_whitelist\&quot;: [\&quot;$(minitiad keys show bridge_executer -a)\&quot;, \&quot;$(minitiad keys show output_submitter -a)\&quot;, \&quot;$(minitiad keys show batch_submitter -a)\&quot;]<br>      }<br>    }<br>  ]<br>}&quot; &gt; messages.json</pre><p>Execute</p><pre>minitiad tx opchild execute-messages \<br>  ./messages.json \<br>  --from validator \<br>  --chain-id oldbutgold-1 \<br>  --gas-prices 0.15umin \ <br>  --gas auto --gas-adjustment 1.4</pre><p><strong>Last things you might be know:</strong></p><p>Ok, great! We launched our minitia but how we use local explorer: <a href="https://docs.initia.xyz/build-on-initia/general-tutorials/using-the-initia-local-explorer">https://docs.initia.xyz/build-on-initia/general-tutorials/using-the-initia-local-explorer</a></p><p>Do you want to create your NFT collection in your chain?</p><p>Here is the sample command that I used for you. I just created collection with 1000 amount can be minted.</p><pre>minitiad tx move execute 0x1 simple_nft create_collection \<br>  --args &quot;string:celebration option&lt;u64&gt;:1000 string:oldbutgold string: bool:true bool:true bool:true bool:true bool:true bool:true decimal128:0.05&quot; \<br>  --from validator \<br>  --gas-prices 0.15umin \<br>  --node http://127.0.0.1:26657 --chain-id oldbutgold-1</pre><p>Thanks for reading!</p><p>Serkan</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71113dddd883" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Initia: Running Your First Node]]></title>
            <link>https://medium.com/@AlglSerkan/initia-running-your-first-node-5b3bdd6cd61f?source=rss-e7f48181c487------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b3bdd6cd61f</guid>
            <category><![CDATA[testnet]]></category>
            <category><![CDATA[incentivized-testnet]]></category>
            <category><![CDATA[initia]]></category>
            <category><![CDATA[validator]]></category>
            <category><![CDATA[cosmos]]></category>
            <dc:creator><![CDATA[Serkan A.]]></dc:creator>
            <pubDate>Sat, 29 Jun 2024 18:11:47 GMT</pubDate>
            <atom:updated>2024-07-07T11:20:19.075Z</atom:updated>
            <content:encoded><![CDATA[<h4>This document is a guide and review of my experience setting up and running a node on Initia’s Public Testnet.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2U821lx9d9Sksh3AFpefBg.png" /></figure><p>Six weeks ago, Initia announced its Incentivized Testnet. I couldn’t miss the opportunity to earn my place in Initia’s Genesis Validator Set come mainnet launch. However, there were a few challenges, such as the community being quite large and many people wanting to run validator nodes. Fortunately, the Initiation Validator Program consists of 5 phases over the course of 8 weeks. Each phase requires validators to contribute in different ways and they are scored based on the completion of tasks and the quality of their performance.</p><p>Approximately 13,000 validator nodes had been set up. It was a huge participation for public testing, but problems arose! Many participants did not adhere to hardware requirements and likely rented low-cost VPS from Hetzner or Contabo. Unfortunately, this caused issues with syncing and processing blocks due to bad peers. The good news is that the team started an elimination process and selected around 400 operators. This was my first experience during phase 1. I maintained my node, upgraded it when new versions were released, voted on governance proposals, ensured high uptime, and provided oracle prices for the other phases, hoping to be selected as a genesis validator.</p><blockquote>Please be aware: Initia’s Incentivized Testnet participation has ended for validators.</blockquote><blockquote><strong><em>End of 8 weeks, incentivized testnet for validators has been completed. I maintained uptime, submitted oracle prices, and participated in governance voting. Around 200 validator operators have been selected to active set in groups of 50–60. The team collected these on-chain data to examine their performance. Although I have enough high specification server, I almost 5 blocks missed for 100 blocks. I guess that it was caused by bad peers on network. Some validators misconfigured indexer and it caused low uptime.</em></strong></blockquote><h3>Let’s Dive into Setting Up and Running a Node Step-by-Step</h3><h4>Hardware/OS Requirements:</h4><ul><li><strong>CPU:</strong> 16 cores</li><li><strong>Memory:</strong> 32GB RAM</li><li><strong>Disk:</strong> 2 TB NVMe/SSD Storage with Write Throughput &gt; 1000 MiBps</li><li><strong>Bandwidth:</strong> 100 Mbps</li></ul><blockquote>I bought a dedicated server from Hetzner auction. The server has high specifications: AMD Ryzen 9 5950X 16-core 32-thread CPU, 128GB DDR4 RAM, and 3.84 TB SSD. There was no initial setup cost, and I pay just $76/monthly. I installed Ubuntu 24.04 LTS.</blockquote><h4>Update Packages:</h4><pre>sudo apt update &amp;&amp; sudo apt upgrade -y<br>sudo apt install curl git wget htop tmux build-essential jq make lz4 gcc unzip -y</pre><h4>Install Go:</h4><pre>cd $HOME<br>VER=&quot;1.21.3&quot;<br>wget &quot;https://golang.org/dl/go$VER.linux-amd64.tar.gz&quot;<br>sudo rm -rf /usr/local/go<br>sudo tar -C /usr/local -xzf &quot;go$VER.linux-amd64.tar.gz&quot;<br>rm &quot;go$VER.linux-amd64.tar.gz&quot;<br>[ ! -f ~/.bash_profile ] &amp;&amp; touch ~/.bash_profile<br>echo &quot;export PATH=$PATH:/usr/local/go/bin:~/go/bin&quot; &gt;&gt; ~/.bash_profile<br>source $HOME/.bash_profile<br>[ ! -d ~/go/bin ] &amp;&amp; mkdir -p ~/go/bin</pre><h4>Checkout and Build Initia:</h4><pre>git clone https://github.com/initia-labs/initia<br>cd initia<br>git checkout v0.2.21<br>make build</pre><h4>System Link:</h4><pre>mkdir -p $HOME/.initia/cosmovisor/genesis/bin<br>mv /root/initia/build/initiad $HOME/.initia/cosmovisor/genesis/bin/<br>sudo ln -s $HOME/.initia/cosmovisor/genesis $HOME/.initia/cosmovisor/current -f<br>sudo ln -s $HOME/.initia/cosmovisor/current/bin/initiad /usr/local/bin/initiad -f</pre><h4>Install Cosmovisor:</h4><pre>go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@v1.5.0</pre><h4>Create Service File:</h4><pre>sudo tee /etc/systemd/system/initiad.service &gt; /dev/null &lt;&lt; EOF<br>[Unit]<br>Description=Initia node service<br>After=network-online.target</pre><pre>[Service]<br>User=$USER<br>ExecStart=$(which cosmovisor) run start<br>Restart=on-failure<br>RestartSec=10<br>LimitNOFILE=65535<br>Environment=&quot;DAEMON_HOME=$HOME/.initia&quot;<br>Environment=&quot;DAEMON_NAME=initiad&quot;<br>Environment=&quot;UNSAFE_SKIP_BACKUP=true&quot;<br>Environment=&quot;PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:$HOME/.initia/cosmovisor/current/bin&quot;</pre><pre>[Install]<br>WantedBy=multi-user.target<br>EOF</pre><h4>Enable Service:</h4><pre>sudo systemctl daemon-reload<br>sudo systemctl enable initiad.service</pre><h4>Initialize Node:</h4><p>A moniker is a human-readable name for your node. It can contain only ASCII characters and cannot exceed 70 characters. Your private key is generated during initialization and is saved in ~/.initia/config/priv_validator_key.json. Remember to backup your private key if you are running a validator node. If a private key is lost, the node may never be recoverable from a hardware failure. Plan your backup when running a Testnet node, and secure your private key safely for the mainnet.</p><pre>initiad config set client chain-id initiation-1<br>initiad config set client node tcp://localhost:15657<br>initiad config set client keyring-backend test<br>initiad init [moniker] --chain-id initiation-1</pre><h4>Set Up External Address:</h4><p>To allow access from external nodes to your node through the P2P network, config.toml has to be modified. By entering the public IP/Port into the p2p.external_address field, the network settings will allow external nodes to access your node.</p><pre>sed -i -e &#39;s/external_address = \&quot;\&quot;/external_address = \&quot;&#39;$(curl httpbin.org/ip | jq -r .origin)&#39;:26656\&quot;/g&#39; ~/.initia/config/config.toml</pre><h4>Set Minimum Gas Prices:</h4><p>The minimum gas price accepted by the validator to process a transaction and prevent spamming.</p><pre>sed -i -e &quot;s|^minimum-gas-prices *=.*|minimum-gas-prices = \&quot;0.15uinit,0.01uusdc\&quot;|&quot; $HOME/.initia/config/app.toml</pre><h4>Genesis File:</h4><p>The genesis file is named genesis.json and must be relocated to the ~/.initia/config directory. Should the HOME directory for Initia be configured to a different location, ensure to move the genesis file to the appropriate config directory within that set location.</p><pre>curl -Ls https://initia.s3.ap-southeast-1.amazonaws.com/initiation-1/genesis.json &gt; $HOME/.initia/config/genesis.json</pre><h4>Seed &amp; Peers:</h4><pre>SEEDS=&quot;2eaa272622d1ba6796100ab39f58c75d458b9dbc@34.142.181.82:26656,c28827cb96c14c905b127b92065a3fb4cd77d7f6@testnet-seeds.whispernode.com:25756&quot;<br>PEERS=&quot;45d4bd57afe12aa862a2252b32617aa06013f857@49.165.90.94:25756,59a6e2a34fcebf1605a26059d40bff20bf620b36@37.27.107.22:26656,a4b6849e58ff2b96ca35487a675db90e86134c51@88.99.137.151:26656,95071a39cab00a428c532c682c6cd05618f5a9f4@46.4.80.48:25756,1e07b92a4c3bc1d66c2257a3b2378f80a7bdc1a2@135.181.239.149:26656&quot;<br>sed -i -e &quot;s/^seeds *=.*/seeds = \&quot;$SEEDS\&quot;/; s/^persistent_peers *=.*/persistent_peers = \&quot;$PEERS\&quot;/&quot; $HOME/.initia/config/config.toml</pre><h4>Snapshot:</h4><p>Snapshots allow a new node to join the network by recovering the application state from a backup file. A snapshot contains a compressed copy of the chain data directory. To keep backup files as small as possible, the snapshot server is periodically state-synced.</p><pre>initiad tendermint unsafe-reset-all --home $HOME/.initia<br>curl -L https://snapshots.kjnodes.com/initia-testnet/snapshot_latest.tar.lz4 | tar -Ilz4 -xf - -C $HOME/.initia</pre><h4>Addrbook:</h4><p>It is highly recommended to copy addrbook.json to $INITIA_HOME/config/addrbook.json for fast peer connection.</p><pre>wget https://initia.s3.ap-southeast-1.amazonaws.com/initiation-1/addrbook.json<br>mv addrbook.json ~/.initia/config/addrbook.json</pre><h4>Start Service &amp; Check Logs:</h4><pre>sudo systemctl daemon-reload<br>sudo systemctl restart initiad<br>sudo journalctl -u initiad.service -f --no-hostname -o cat</pre><h4>Create or Restore Wallet:</h4><p>In order to create a validator, you have to create or recover a wallet and fund it with GAS tokens via <a href="https://faucet.testnet.initia.xyz/">the faucet</a> (Gitcoin score must be greater than 20) for the testnet. The INIT token will be used as a gas token on the mainnet.</p><pre># Create a new wallet<br>initiad keys add [wallet-name]</pre><pre># or restore a new wallet<br>initiad keys add wallet --recover</pre><h4>Becoming Validator:</h4><pre>initiad tx mstaking create-validator \<br>  --amount=5000000uinit \<br>  --pubkey=$(initiad tendermint show-validator) \<br>  --moniker=[your moniker] \<br>  --chain-id=initiation-1 \<br>  --commission-rate=0.05 \<br>  --commission-max-rate=0.10 \<br>  --commission-max-change-rate=0.01 \<br>  --from=[wallet-name] \<br>  --identity=[keybase-id] \<br>  --website=&quot;&quot; \<br>  --details=&quot;&quot; \<br>  --node=http://localhost:657 \<br>  --gas-adjustment 1.4 \<br>  --gas=2000000 \<br>  --fees=563000move/944f8dd8dc49f96c25fea9849f16436dcfa6d564eec802f3ef7f8b3ea85368ff \<br>  -y</pre><h4>Check Status of Your Node:</h4><p>Syncing and processing blocks take some time depending on your server specifications and peers. You can check your sync status with the following command. catching_up must be false and all blocks synced with the latest block. If your node does not catch up for some time, you should change your peers and download the latest snapshot.</p><pre>initiad status | jq &#39;.sync_info&#39;</pre><pre># Response should be like<br>{<br>  &quot;latest_block_hash&quot;: &quot;2AF656E3A6CE94DC1C54ECA71A04FAF79F7BDE924377270D0A795565AC06E039&quot;,<br>  &quot;latest_app_hash&quot;: &quot;F9D4D51A25EF0011B1B1CB196A33A3186ABC5A9EB776A1A64DF0E70BDCEA24A0&quot;,<br>  &quot;latest_block_height&quot;: &quot;1867818&quot;,<br>  &quot;latest_block_time&quot;: &quot;2024-06-29T17:47:37.70374895Z&quot;,<br>  &quot;earliest_block_hash&quot;: &quot;48B64E41963BF7B8732D067D4DD6003D27C166E5BE95C43265B6BC54D3E4CBF2&quot;,<br>  &quot;earliest_app_hash&quot;: &quot;DEDC82AEB9377B4542528A05709D588F1A3B0539028301660ADCFA930FEDC470&quot;,<br>  &quot;earliest_block_height&quot;: &quot;408402&quot;,<br>  &quot;earliest_block_time&quot;: &quot;2024-05-29T01:20:04.566288257Z&quot;,<br>  &quot;catching_up&quot;: false<br>}</pre><p><strong>Congratulations</strong> on successfully setting up your first Initia Validator Node!</p><p>For troubleshooting, consult the official documentation first. If needed, seek assistance on the official Discord server or feel free to reach out to me directly on our Discord community.</p><p>Here you can read article about deploy intervowen rollup (A.K.A minitia) in 10 minutes.</p><p><a href="https://medium.com/@AlglSerkan/deploy-your-future-of-interwoven-rollup-a-k-a-minitia-in-10-minutes-71113dddd883">Initia: Deploy your Future of Interwoven Rollup L2 (A.K.A: Minitia) in 10 minutes</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b3bdd6cd61f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lorem Ipsum]]></title>
            <link>https://medium.com/@AlglSerkan/lorem-ipsum-304b2eb11c62?source=rss-e7f48181c487------2</link>
            <guid isPermaLink="false">https://medium.com/p/304b2eb11c62</guid>
            <dc:creator><![CDATA[Serkan A.]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 11:28:28 GMT</pubDate>
            <atom:updated>2016-03-21T11:28:28.329Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Lorem Ipsum</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/16/1*tRvPpt8ODA5mEHYCL4BUjA.png" /><figcaption>asdadsasdasd</figcaption></figure><p><strong>Lorem Ipsum</strong> is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry’s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p><p>It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using ‘Content here, content here’, making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for ‘lorem ipsum’ will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).</p><p>Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of “de Finibus Bonorum et Malorum” (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, “Lorem ipsum dolor sit amet..”, comes from a line in section 1.10.32.</p><p>The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from “de Finibus Bonorum et Malorum” by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=304b2eb11c62" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>