<?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 C-Man on Medium]]></title>
        <description><![CDATA[Stories by C-Man on Medium]]></description>
        <link>https://medium.com/@cman.theman.1994?source=rss-6a47577ef8b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JQTmQ7e1X6XEYMzgK3K5hQ.png</url>
            <title>Stories by C-Man on Medium</title>
            <link>https://medium.com/@cman.theman.1994?source=rss-6a47577ef8b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:54:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cman.theman.1994/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[Give Your Helium or Crankk Gateway a Second Life with Sensmos]]></title>
            <link>https://medium.com/@cman.theman.1994/give-your-helium-or-crankk-gateway-a-second-life-with-sensmos-fa81275692ba?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa81275692ba</guid>
            <category><![CDATA[depin]]></category>
            <category><![CDATA[crankk]]></category>
            <category><![CDATA[helium-network]]></category>
            <category><![CDATA[lorawan]]></category>
            <category><![CDATA[sensmos]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 14:22:39 GMT</pubDate>
            <atom:updated>2026-10-10T14:22:39.737Z</atom:updated>
            <content:encoded><![CDATA[<p>If you already operate a <a href="https://www.helium.com/iot"><strong>Helium</strong></a> hotspot or a <a href="https://crankk.io/gateway"><strong>Crankk</strong></a> gateway, you may be able to put it to work for another project without buying new hardware or replacing your existing setup. <a href="https://sensmos.com/"><strong>Sensmos</strong></a> offers a way to forward LoRaWAN traffic to its network, pair your gateway with your Sensmos Wallet, and earn rewards in <a href="https://sensmos.com/token/"><strong>GALU</strong></a>.</p><p>Let’s look at what these projects are, why this integration is worth exploring, and how to set it up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wWzZ9yaLoZa8-nstvpXKw.png" /><figcaption>Credit: the Sensmos explorer</figcaption></figure><h3>What Is Sensmos?</h3><p><a href="https://sensmos.com/"><strong>Sensmos</strong></a> is an early-stage decentralized network built around connected nodes, sensors, and locally collected data. Its approach emphasizes data from the perspective of individual nodes, allowing participants to collect, share, and access information across the network. The project combines an Android application and wallet with its own hardware, open firmware, and a native token called <a href="https://polygonscan.com/address/0x9d797D0E642D9EADdbDbD34ACFCFd07bf0043c6C">GALU on Polygon</a>.</p><h3>What Is Helium?</h3><p><a href="https://www.helium.com/"><strong>Helium</strong></a> is a decentralized wireless network, and this article focuses exclusively on its IoT side, where LoRaWAN hotspots provide connectivity for low-power sensors and devices. Hotspots can earn IOT-related rewards through data transfer and, under the previous reward model, Proof-of-Coverage (PoC). However, <a href="https://github.com/helium/HIP/blob/main/0149-helium-utility-and-emissions-realignment.md">HIP 149</a>, approved in 2026, retires PoC rewards for both IoT and Mobile, making real network utility increasingly important to the reward model.</p><h3>What Is Crankk?</h3><p><a href="https://crankk.io/"><strong>Crankk</strong></a> is a decentralized IoT network built around LoRaWAN gateways, originally operating on the Kadena blockchain. Following <a href="https://www.kadena.io/">Kadena’s collapse</a>, which left its ecosystem and community severely affected, Crankk has become dormant, with communication from the team effectively non-existent despite its website remaining online. Given the project’s inactivity and the lack of updates, it is difficult to assess its future, although it’s possible that the project’s exposure to KDA contributed to its difficulties.</p><h3>Why Connect Existing Gateways to Sensmos?</h3><p>The idea is straightforward: use hardware you already own to contribute to another network.</p><p>By adding Sensmos as an additional packet-forwarding destination, your existing Helium/Crankk gateway can send received LoRaWAN packets to Sensmos while keeping its existing forwarding destinations intact. You then pair the gateway with your Sensmos Wallet in the Android app, allowing it to participate in Sensmos and become eligible for rewards in GALU, the project’s native token on Polygon.</p><p>There are important caveats. Sensmos is still at an early stage, its network adoption is limited, and GALU currently has extremely low market liquidity. At the time of writing, public decentralized-exchange listings showed <a href="https://app.uniswap.org/explore/tokens/polygon/0x9d797D0E642D9EADdbDbD34ACFCFd07bf0043c6C">liquidity measured in only a few dollars</a>, meaning that a displayed token price should not be confused with a realistic ability to sell meaningful amounts.</p><p>This is an opportunity to experiment with existing infrastructure, not a promise of income.</p><h3>Prerequisites</h3><p>Before starting, make sure you have:</p><ul><li>The Crankk software running on the Helium hotspot.</li><li>Access to the Crankk Local Dashboard.</li><li>The Sensmos app/APK installed and running on your phone (Android only, for now).</li></ul><h3>Step-by-Step Guide</h3><h3>I. The Sensmos App</h3><p><strong>1.</strong> Open the Sensmos app and unlock your <strong>Wallet</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9G3Ja652BIgXUAV33PYfQQ.png" /><figcaption>Credit: C-Man</figcaption></figure><p><strong>2.</strong> Go back to <strong>Nodes</strong> and hit the <strong>+</strong> (plus sign) button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ybjlfznYFkkCIfF8yqg12g.png" /><figcaption>Credit: C-Man</figcaption></figure><p><strong>3.</strong> Hit the <strong>Add LoRaWAN gateway</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTa3XDgRfVh7oGm-P6itzA.png" /><figcaption>Credit: C-Man</figcaption></figure><h3>II. The Crankk Local Dashboard</h3><p><strong>1.</strong> Log into the gateway’s Crankk Local Dashboard (http://gateway_IP:17080) and, by the <strong>Gateway</strong> tab, under the <strong>General Information</strong> table, hit the <strong>Setup Gateway</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdCaZTM1pJky-lIu0QddcQ.png" /><figcaption>Credit: C-Man</figcaption></figure><p><strong>2.</strong> In the <strong>Gateway Setup</strong> (or <strong>Gateway Configuration</strong> in <a href="https://discord.com/channels/1309415107448803348/1498359825648586875/1557259228685533315">Sic’s new Multimining Fork Dashboard</a> —<a href="https://discord.gg/wY3N2hCT3u"> join my Discord server</a> to access this link), by <strong>Forwards to</strong>, add the text:</p><pre>sensmos.com:1700</pre><p>Add it after a comma (,), with <strong>NO SPACES</strong>. The whole line should look like this:</p><pre>127.0.0.1:1700,127.0.0.1:1680,sensmos.com:1700</pre><p>Hit the <strong>Save</strong> button. The gateway will reboot to apply the new setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zhrSVeHWiVDK0Yi8sth3MA.png" /><figcaption>Credit: C-Man</figcaption></figure><p><strong>3.</strong> The last piece of information needed from the Crankk Local Dashboard is the <strong>Gateway ID</strong>, which can be found under the Gateway Animal Name. It has the format xxxxxxxxxxxxxxxx (16 characters).</p><h3>III. Back to the Sensmos App</h3><p><strong>1.</strong> In the <strong>Add LoRaWAN Gateway</strong> menu (point I.3. in this guide), insert the following:</p><ul><li><strong>Gateway ID:</strong> The ID from the Crankk Local Dashboard (point II.3.).</li><li><strong>Name:</strong> A name of your choice.</li><li><strong>Latitude/Longitude:</strong> Use the <strong>I’m at the gateway — use the phone’s position</strong> button if you’re at the same location as the gateway. This requires Location to be activated on your phone. Alternatively, check Google Maps or a similar service to determine the gateway’s actual position.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aD1tZAY_Hg1_rX9YA9h5Yg.png" /><figcaption>Credit: C-Man</figcaption></figure><p><strong>2.</strong> Hit the <strong>Pair with wallet</strong> button. If the steps have been completed correctly, the gateway will be detected and added to the <strong>Nodes</strong> menu in the Sensmos app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eb4b3PGkpAUSlcbKybgdkw.png" /><figcaption>Credit: C-Man</figcaption></figure><p>That’s it! Your gateway is now configured to forward packets to Sensmos while retaining its existing forwarding destinations.</p><h3>What Happens After Pairing?</h3><p>The gateway becomes part of the Sensmos network, helping deliver relevant LoRa frames and contributing to network coverage. According to the <a href="https://sensmos.com/docs/gateway/">official Sensmos gateway documentation</a>, a directly paired gateway can receive its own dashboard card, participate in coverage beacons, and earn rewards according to the project’s gateway reward rules.</p><p>Rewards are accounted for in GALU, an ERC-20 token on Polygon. You can review the <a href="https://sensmos.com/token/">GALU token contract and transparency information</a> to inspect the project’s on-chain supply and reward-pool information.</p><h3>Final Thoughts</h3><p>We already have the hardware spread across different locations. Helium and Crankk gateways have been deployed, powered on, and positioned to receive LoRaWAN traffic; Sensmos offers a way to put some of that existing infrastructure to additional use.</p><p>The integration is simple, does not require buying a new gateway, and lets operators experiment with another decentralized network. Sensmos is <strong>free to join</strong>, without <strong>future promises </strong>(no <strong>hype</strong>, nor <strong>FOMO,</strong> only <strong>building</strong>).</p><p>More integrations soon to come, if you already have compatible hardware, the cost of experimenting is minimal.</p><p><strong>Use what you already have, contribute where you can, and join an honest project.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa81275692ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fix: Secure Remote Access and Recovery for Headless MastChain Stations]]></title>
            <link>https://medium.com/@cman.theman.1994/fix-secure-remote-access-and-recovery-for-headless-mastchain-stations-ed9714e8317d?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed9714e8317d</guid>
            <category><![CDATA[remote-access]]></category>
            <category><![CDATA[matchain]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[depin]]></category>
            <category><![CDATA[tailscale]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Sun, 31 May 2026 14:07:17 GMT</pubDate>
            <atom:updated>2026-05-31T14:23:13.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtFi1Rj3BpkKSb2X-TfYQQ.jpeg" /></figure><p>One of the biggest challenges when running a DIY <a href="https://mastchain.io/">MastChain</a> station is not the initial setup — it’s maintaining the station after deployment.</p><p>Most operators use Raspberry Pi devices, mini PCs, or similar low-power Linux systems running <a href="https://github.com/jvde-github/AIS-catcher">AIS-Catcher</a> or <a href="https://github.com/mastchain/mastcontrol">Mastcontrol</a> software. Once everything is working, the station is often placed in an attic (or on the roof?), near an antenna, or somewhere out of sight. That’s when a new problem appears:</p><p><strong>How do you manage and troubleshoot your station when you’re not physically at home?</strong></p><p>This guide explains how I solved remote management and recovery for my MastChain station using <a href="https://tailscale.com/">Tailscale</a> and a <a href="https://s.click.aliexpress.com/e/_c3nqM6Vn">smart plug</a>, allowing full remote access without opening any ports on my router.</p><h3>The Problem</h3><p>After successfully deploying my MastChain station, I realized that all administration was limited to my local network.</p><p>I could access the AIS-Catcher dashboard and SSH into the device while at home, but as soon as I left my network, I lost visibility of the station.</p><p>This created several issues:</p><ul><li>Unable to check whether AIS-Catcher was still running (when a station appeared offline in the MastChain dashboard)</li><li>Unable to monitor station performance while away</li><li>No access to logs for troubleshooting (e.g. invalid received messages error codes)</li><li>No way to restart services remotely</li><li>Difficult to investigate unexpected outages</li><li>Physical access required for most maintenance tasks</li></ul><p>Opening ports on the router was one possibility, but I wanted a solution that was secure, easy to maintain, and accessible from any device.</p><h3>Symptoms</h3><p>If you’re facing the same issue, you may notice:</p><ul><li>AIS-Catcher Web UI only works on your local network</li><li>SSH access is unavailable outside your home</li><li>You might see that your station is offline in the <a href="https://app.mastchain.io/app/dashboard">MastChain Dashboard</a> but cannot investigate immediately</li><li>Router port forwarding feels unnecessarily complicated or insecure</li><li>You need someone at home to check the device whenever a problem occurs</li></ul><h3>The Fix: Tailscale</h3><p>Tailscale creates a private encrypted network between your devices.</p><p>Instead of exposing services to the internet, your MastChain station becomes accessible only to devices connected to your private Tailscale network.</p><p>The result is secure remote access without port forwarding, static IPs, or VPN configuration.</p><h3>Step 1: Install Tailscale</h3><p>On Debian-based systems (or open a terminal in a visual Linux environment):</p><pre>curl -fsSL https://tailscale.com/install.sh | sh</pre><h3>Step 2: Authenticate the Device</h3><p>Run:</p><pre>sudo tailscale up</pre><p>A URL will appear.</p><p>Open the URL in your browser and authorize the device for your Tailscale account.</p><p>Once completed, your MastChain station joins your private Tailscale network.</p><h3>Step 3: Verify Connectivity</h3><p>Check that the node is online:</p><pre>tailscale status</pre><p>You should see your station listed with a Tailscale IP address.</p><p>Example:</p><pre>100.x.x.x</pre><h3>Step 4: Access Your Station Remotely</h3><p>SSH access:</p><pre>ssh hostname@100.x.x.x</pre><p>Replace <em>hostname</em> with the system’s hostname and the IP with the one assigned by Tailscale.</p><p>You now have terminal access from anywhere in the world.</p><h3>Step 5: Access AIS-Catcher Remotely</h3><p>If AIS-Catcher is running on port 8100 (the generic one), simply open:</p><pre>http://100.x.x.x:8100</pre><p>Again, replace the IP with your station’s Tailscale address.</p><p>The dashboard should load exactly as if you were connected to your home network.</p><h3>Common Recovery Actions</h3><p>Once connected, most issues can be fixed remotely.</p><h3>Restart AIS-Catcher</h3><pre>sudo systemctl restart ais-catcher</pre><h3>Check Logs</h3><pre>journalctl -u ais-catcher -f</pre><h3>Check System Resources</h3><pre>htop</pre><h3>Restart Docker Containers</h3><p>in case a <a href="https://github.com/C-Man-The-Man/mastchain-ais">MastChain Docker build</a> is used</p><pre>docker restart &lt;container_name&gt;</pre><h3>Reboot the Entire System</h3><pre>sudo reboot</pre><p>For many operators, these commands solve 95% of issues without requiring physical access.</p><h3>The Remaining Problem</h3><p>There is one situation where software-based remote access cannot help:</p><p>The device becomes completely unresponsive.</p><p>Examples include:</p><ul><li>Kernel crashes</li><li>Hardware lockups</li><li>Power issues</li><li>Failed updates</li><li>Filesystem corruption</li><li>Network driver failures</li></ul><p>If SSH stops responding and Tailscale goes offline, remote access alone is no longer enough.</p><p>At this point, the only traditional solution is physically unplugging and reconnecting power.</p><p>Unless you add one more tool.</p><h3>Bonus Fix: Smart Plug Remote Power Cycling</h3><p>To achieve true remote recovery, I connected my MastChain station to a <a href="https://s.click.aliexpress.com/e/_c3nqM6Vn">smart plug</a>.</p><p>This allows me to remotely cut power and restore it, effectively performing a hard reboot from anywhere.</p><p>The setup is simple:</p><pre>Wall Outlet<br>      │<br>Smart Plug<br>      │<br>Power Supply<br>      │<br>Raspberry Pi / Mini PC</pre><p>If the station becomes completely unresponsive:</p><ol><li>Open the smart plug app</li><li>Turn the plug OFF</li><li>Wait 10–20 seconds</li><li>Turn the plug ON again</li></ol><p>The device reboots exactly as if someone unplugged and reconnected it manually.</p><h3>Recommended Combination</h3><p>For a <a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">DIY MastChain station</a>, the preferred setup is:</p><ul><li>MastChain node</li><li>AIS-Catcher</li><li>Tailscale</li><li>Smart Plug</li></ul><p>This combination provides:</p><p>✓ Secure remote access</p><p>✓ Remote monitoring</p><p>✓ Remote troubleshooting</p><p>✓ Remote service management</p><p>✓ Remote reboots</p><p>✓ Emergency power-cycle recovery</p><p>✓ No router port forwarding</p><p>✓ No public exposure of services</p><h3>Conclusion</h3><p>A MastChain station is often deployed as a headless device that may run for months without direct interaction. While initial setup is important, long-term maintainability is equally critical.</p><p>Using Tailscale solved the remote access problem by allowing secure access to AIS-Catcher and system services from anywhere. Adding a smart plug completed the setup by providing a recovery method for situations where the operating system becomes completely unresponsive.</p><p>Since implementing both solutions, I can monitor, troubleshoot, and recover my MastChain station without requiring physical access, making long-term operation significantly easier and more reliable.</p><p>I hope this helps other operators avoid unnecessary downtime and simplifies remote station management. <br>To join the MastChain network, please consider using my referral <a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5</a>, thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed9714e8317d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cum să montezi un nod MastChain DIY cu Docker folosind mastchain-config]]></title>
            <link>https://medium.com/@cman.theman.1994/cum-s%C4%83-montezi-un-nod-mastchain-diy-cu-docker-folosind-mastchain-config-8646d0386258?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8646d0386258</guid>
            <category><![CDATA[romania]]></category>
            <category><![CDATA[mastchain]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Tue, 05 May 2026 16:40:06 GMT</pubDate>
            <atom:updated>2026-05-05T16:40:06.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*Y2jsdh7JgHWaMuOSeye_mQ.png" /></figure><h3>Introducere</h3><p>În acest ghid vei învăța cum să implementezi un nod MastChain pentru recepția semnalelor AIS (Automatic Identification System) folosind un SDR (RTL-SDR) și Docker, automatizat:</p><p><a href="https://github.com/C-Man-The-Man/mastchain-config">— https://github.com/C-Man-The-Man/mastchain-config</a><br> — <a href="https://github.com/C-Man-The-Man/mastchain-ais">https://github.com/C-Man-The-Man/mastchain-ais</a></p><p>Obiectivul este să faciliteze o instalare reproductibilă, chiar și pentru utilizatori cu cunoștințe de bază de Linux.</p><h3>🧰 Cerințe hardware</h3><p>Vei avea nevoie de:</p><ul><li>1× RTL-SDR (receptor AIS), ori AirSpy etc.</li><li>1× antenă pentru banda maritimă (~162 MHz)</li><li>1× computer Linux (Raspberry Pi sau mini PC)</li><li>Conexiune stabilă la Internet</li><li>Sursă de alimentare adecvată</li></ul><h3>Unde poți cumpăra în România</h3><p>Am creat un alt ghid despre părțile necesare care pot fi gasite local in România <a href="https://medium.com/%40cman.theman.1994/mastchain-diy-node-%C3%AEn-rom%C3%A2nia-bricolaj-realist-cost-total-%C3%AEn-lei-092c86a0ebc3">https://medium.com/%40cman.theman.1994/mastchain-diy-node-%C3%AEn-rom%C3%A2nia-bricolaj-realist-cost-total-%C3%AEn-lei-092c86a0ebc3</a></p><p>💡 Recomandare: o antenă de calitate influențează mai mult performanța decât propriul SDR.</p><h3>🖥️ Instalarea sistemului</h3><h3>🐳 Instalarea Docker</h3><p>Pe Linux:</p><pre>sudo apt update<br>sudo apt install -y docker.io docker-compose<br>sudo systemctl enable docker<br>sudo systemctl start docker</pre><p>Opțional (folosirea Docker fără sudo):</p><pre>sudo usermod -aG docker $USER</pre><p>Închide sesiunea și autentifică-te din nou.</p><h3>📦 Instalarea mastchain-config</h3><p>Clonează repository-ul:</p><pre>git clone https://github.com/C-Man-The-Man/mastchain-config.git<br>cd mastchain-config</pre><h3>⚙️ Configurare</h3><p>Editează fișierul .env:</p><pre>nano .env</pre><p>Configurează variabilele relevante (în funcție de repository), cum ar fi:</p><ul><li>fus orar</li><li>parametri SDR</li><li>configurația containerelor</li></ul><h3>🚀 Execuție</h3><p>Rulează stack-ul:</p><pre>docker compose up -d</pre><p>Vezi logurile:</p><pre>docker compose logs -f</pre><h3>📡 Verificarea SDR-ului</h3><p>Verifică dacă dispozitivul RTL-SDR funcționează:</p><pre>rtl_test -t</pre><p>Dacă dispozitivul apare corect, sistemul este gata.</p><h3>🔍 Verificarea datelor AIS</h3><p>Poți verifica dacă se primesc semnale observând logurile containerului AIS:</p><pre>docker logs -f mastchain</pre><p>Ar trebui să vezi mesaje legate de semnale AIS detectate.</p><h3>⚠️ Considerații importante în România</h3><ul><li>Utilizare rețea electrică: 230V / prize tip F</li><li>Interferențe RF în orașe mari (precum Constanța)</li><li>Performanță mai bună cu antenă externă</li><li>Evită porturi USB 3.0 apropiate de SDR</li><li>O poziție ridicată îmbunătățește semnificativ recepția</li></ul><h3>🛠️ Rezolvarea problemelor comune</h3><h3>SDR nu este detectat</h3><p>Rulează:</p><pre>rtl_test -t</pre><ul><li>schimbă portul USB</li><li>repornește sistemul</li></ul><h3>Nu se primesc date AIS</h3><ul><li>verifică antena</li><li>verifică conexiunea</li><li>confirmă logurile containerului</li></ul><h3>Probleme cu Docker</h3><p>Repornește serviciile:</p><pre>sudo systemctl restart docker</pre><h3>📌 Concluzie</h3><p>Cu mastchain-config, implementarea unui nod MastChain AIS este simplificată semnificativ, permițând oricărui utilizator din Romania să contribuie la rețea cu o configurație reproductibilă bazată pe Docker.</p><p>Dacă acest articol ți-a fost util, ia în considerare utilizarea codului meu de referință pentru a te înregistra și a participa la proiect:</p><p><a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5</a></p><p>Mulțumesc!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8646d0386258" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MastChain DIY Node în România (bricolaj realist + cost total în Lei)]]></title>
            <link>https://medium.com/@cman.theman.1994/mastchain-diy-node-%C3%AEn-rom%C3%A2nia-bricolaj-realist-cost-total-%C3%AEn-lei-092c86a0ebc3?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/092c86a0ebc3</guid>
            <category><![CDATA[romania]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[decentralized]]></category>
            <category><![CDATA[maritime]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Fri, 01 May 2026 22:09:15 GMT</pubDate>
            <atom:updated>2026-05-01T22:09:15.944Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚢 Ce contează cu adevărat (nu marketing)</h3><p>Pentru AIS (~162 MHz), performanța vine din:</p><ul><li><strong>antenă corectă (VHF marină sau apropiată)</strong></li><li><strong>cablu coaxial bun (50Ω, pierderi puține/low loss)</strong></li><li><strong>izolarea zgomotului USB (extensie + ecranat)</strong></li></ul><p>Receptorul e <em>ultima</em> problemă, nu prima.</p><h3>🧰 Montaj complet (cu produse reale din România)</h3><h3>📡 1. Receptor SDR</h3><p>💰 ~249–960 Lei<br> ✔ Disponibil local</p><p><a href="https://www.emag.ro/receptor-radio-definit-programat-rtl-sdr-blog-v4-500-khz-1-7-ghz-3-2-mhz-metal-compact-5907364650238/pd/DJ5V053BM/">RTL-SDR Blog V4</a> <br><a href="https://www.emag.ro/sdr-radio-rtl-sdr-2832u-r820t2-500khz-1-7ghz-cu-antena-dg12/pd/D0HV24MBM/?ref=smart-history-ml_1_1&amp;provider=rec&amp;recid=rec_4_22f7484f0e583a26fa322035c789f31e5eb0a1e14886763e5baa61e170298495_1777667185&amp;scenario_ID=4">RTL-SDR 2832U R820T2 (antenă generic</a><a href="https://www.emag.ro/sdr-radio-rtl-sdr-2832u-r820t2-500khz-1-7ghz-cu-antena-dg12/pd/D0HV24MBM/?ref=smart-history-ml_1_1&amp;provider=rec&amp;recid=rec_4_22f7484f0e583a26fa322035c789f31e5eb0a1e14886763e5baa61e170298495_1777667185&amp;scenario_ID=4">ă</a><a href="https://www.emag.ro/sdr-radio-rtl-sdr-2832u-r820t2-500khz-1-7ghz-cu-antena-dg12/pd/D0HV24MBM/?ref=smart-history-ml_1_1&amp;provider=rec&amp;recid=rec_4_22f7484f0e583a26fa322035c789f31e5eb0a1e14886763e5baa61e170298495_1777667185&amp;scenario_ID=4"> inclusă)</a><br><a href="https://www.iqelectric.ro/echipamente-de-laborator/100khz-1-7ghz-rtl-in-banda-completa-sdr.html">RTL-SDR USB (antenă generică inclusă)</a></p><p>👉Link-uri pentru comenzi internaționale (recomandat) <a href="https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/">https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/</a></p><h3>📡 2. Antenă (unde România nu prea stă bine)</h3><h3>Variantă locală, adaptată:</h3><ul><li>Antenă CB / UHF (modificată pentru VHF)</li></ul><p>💰 ~178 Lei</p><p>👉 Nu e ideală (430–470 MHz), dar:</p><ul><li>funcționează <strong>acceptabil pentru a testa</strong></li></ul><h3>Variantă corectă (dacă găsești):</h3><ul><li>Antenă VHF marină (156–162 MHz)</li></ul><p>👉 Aici sincer:</p><ul><li>rar pe website-uri locale</li><li>trebuie căutată la magazine nautice / radioamatori</li></ul><p>Recomandat căutare pe pagini web internaționale, gen Aliexpress, Amazon, sunt destule exemple corecte pe <a href="https://discord.gg/RKBa9YQ9hJ">canalul de Discord oficial MastChain</a>.</p><h3>🔌 3. Cablu coaxial (Critic)</h3><p>Nu sări peste asta.</p><ul><li>RG58 (standard minim acceptabil)</li></ul><p>💰 ~3.4 Lei / metru</p><p>Recomandare:</p><ul><li>5–10 metri → ~20–35 Lei</li></ul><p>Magazine locale precum <a href="https://www.dedeman.ro/">Dedeman</a>, <a href="https://www.conexelectronic.ro/">Conex Electronic</a>, <a href="https://www.emag.ro/">eMag</a> etc.</p><h3>🔌 4. Extensie USB (ecranată)</h3><p>Aici lumea greșește masiv.</p><p>👉 Din experiență + comunitate:</p><blockquote><em>“unele cabluri nu sunt ecranate real”</em></blockquote><p>Recomandare:</p><ul><li>USB 2.0 (nu 3.0 → mai puțină interferență de zgomot/noise)</li><li>cu ferită</li></ul><p>💰 ~20–40 Lei (estimare realistă)<br>Magazine locale precum <a href="https://www.dedeman.ro/">Dedeman</a>, <a href="https://www.conexelectronic.ro/">Conex Electronic</a>, <a href="https://www.emag.ro/">eMag</a> etc.</p><h3>💸 💯 Cost total minimalist (România)</h3><pre>| Componentă       | Cost      |<br>|------------------|-----------|<br>| Receptor RTL-SDR | ~250 Lei  |<br>| Antenă           | ~180 Lei  |<br>| Coaxial (5–10m)  | ~25 Lei   |<br>| Extensie USB     | ~30 Lei   |</pre><h3>👉 TOTAL: ~485 Lei (~100–110€)</h3><h3>⚠️ Important</h3><p>👉 Setup-ul de mai sus = <strong>nivel amator</strong></p><p>Limitări:</p><ul><li>antena nu este optimă pentru AIS (varianta locală)</li><li>zgomot urban ridicat</li><li>distanță limitată</li></ul><h3>📈 Pentru performanță reală</h3><p>Ce face diferența:</p><ul><li>antenă marină dedicată</li><li>montaj la înălțime</li><li>cablu mai bun (LMR400)</li></ul><h3>🇷🇴 Concluzie sinceră</h3><p>Da — poți face un nod MastChain în România <strong>cu hardware local</strong>.</p><p>Dar:</p><ul><li>✔ receiver → ușor de găsit, deși recomand surse externe</li><li>⚠️ antene AIS → greu de găsit corect</li><li>✔ cabluri → disponibile și ieftine</li></ul><p>👉 Dacă optimizezi <strong>antenă + poziție</strong>, poate chiar și acest setup ieftin devine util.</p><h3>🚀 Context MastChain (important pentru articol)</h3><p>👉 MastChain pregătește un hardware dedicat, <a href="https://mastnode.com/product/mastnode/"><strong>MastNode</strong></a>:</p><ul><li>preț estimat: <strong>~$650 (~3000 Lei), </strong>fără transport</li><li>optimizat pentru AIS</li><li>plug &amp; play (fără bricolaj RF)</li></ul><h3>🧠 Concluzie finală (pentru cititor)</h3><p>Oare merită proiectul investiția? Vă las pe voi sa decideți. Deocamdată, <a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">MastChain</a> este în faza beta, testnet, a fost anunțat că în momentul în care se trece pe mainnet (pe Peaq), nu se vor mai putea înregistra stații DIY noi, se va putea participa numai cu aparate MastNode.</p><p>Dacă vă decideți să participați în testnet cu un bricolaj DIY, utilizați link-ul meu pentru a vă integistra <a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5</a>, vă mulțumesc anticipat.</p><p>Iar pentru partea de software, am creat un <a href="https://github.com/C-Man-The-Man/mastchain-config"><strong>script</strong></a><strong> </strong>care<strong> </strong>ajută în rularea programului<strong> </strong><a href="https://github.com/C-Man-The-Man/mastchain-ais"><strong>mastchain-ais</strong></a><strong> </strong>(Docker) pentru conveniență.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=092c86a0ebc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Fully Automated My Linux Mining Rig (Power Scheduling + Smart Plug)]]></title>
            <link>https://medium.com/@cman.theman.1994/how-i-fully-automated-my-linux-mining-rig-power-scheduling-smart-plug-b3499c460ced?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3499c460ced</guid>
            <category><![CDATA[crypto-mining]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[power-cycle]]></category>
            <category><![CDATA[power-schedule]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 15:37:39 GMT</pubDate>
            <atom:updated>2026-04-07T15:37:39.950Z</atom:updated>
            <content:encoded><![CDATA[<p>Running a <strong>Linux mining rig</strong> 24/7 isn’t always optimal.</p><p>Electricity prices fluctuate. Solar production varies. Sometimes you only want your system running during specific hours.</p><p>So I built a setup that:</p><ul><li>automatically shuts down the system</li><li>cuts power safely</li><li>powers it back on at a scheduled time</li><li>runs completely unattended</li><li>avoids paid services</li></ul><p>It follows my related <a href="https://gist.github.com/C-Man-The-Man/9ad15296a0e78f1727c5bab5b792607f">GitHub Gist</a> (check it out for simple copy/paste command lines).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYHntZe6AMbRtB7kMgvDxQ.png" /></figure><h3>The Problem</h3><p>Linux can easily:</p><ul><li>start services automatically</li><li>run scripts on schedule</li></ul><p>But there’s a limitation:</p><p>→ A powered-off computer cannot turn itself back on.</p><p>That means:</p><ul><li>cron won’t help</li><li>systemd won’t help</li><li>scripts won’t help</li></ul><p>You need something external.</p><h3>The Solution: Hybrid Automation</h3><p>I combined three layers:</p><h3>1. systemd (inside Linux)</h3><p>Handles clean shutdown</p><h3>2. BIOS setting</h3><p>Automatically boots the PC when power returns</p><h3>3. Smart plug</h3><p>Controls when electricity is available</p><h3>How It Works</h3><p>Here’s my daily cycle:</p><ul><li>22:00 → smart plug turns ON</li><li>PC receives power → boots automatically</li><li><a href="https://medium.com/@cman.theman.1994/how-to-auto-start-crypto-miners-on-linux-using-systemd-7103a53de0e0">miners start automatically (systemd services)</a></li><li>08:00 → Linux shuts down cleanly</li><li>08:05 → smart plug cuts power</li></ul><p>Then the cycle repeats.</p><h3>Step 1 — Enable Auto Power-On in BIOS</h3><p>Look for:</p><pre>Restore on AC Power Loss → Power ON</pre><p>This is what makes the system boot when the plug turns on.</p><h3>Step 2 — Schedule Shutdown with systemd</h3><p>Create a shutdown service:</p><p>Open a terminal</p><pre>sudo nano /etc/systemd/system/scheduled-shutdown.service</pre><p>Insert (copy/paste)</p><pre>[Unit]<br>Description=Scheduled System Shutdown<br><br>[Service]<br>Type=oneshot<br>ExecStart=/sbin/shutdown -h now</pre><p>Then trigger it daily with a timer:</p><p>Open a terminal</p><pre>sudo nano /etc/systemd/system/scheduled-shutdown.timer</pre><p>Insert</p><pre>[Unit]<br>Description=Daily Shutdown Timer<br><br>[Timer]<br>OnCalendar=*-*-* 08:00:00<br># Change to your desired shutdown time<br><br>Persistent=true<br><br>[Install]<br>WantedBy=timers.target</pre><p>This ensures the system always shuts down cleanly.</p><p>Enable timer:</p><pre>sudo systemctl daemon-reload<br>sudo systemctl enable scheduled-shutdown.timer<br>sudo systemctl start scheduled-shutdown.timer</pre><h3>Step 3 — Use a Smart Plug</h3><p>I use a programmable smart plug that:</p><ul><li>turns OFF at 08:05</li><li>turns ON at 22:00</li></ul><p>This gives the OS time to shut down before power is cut.</p><p>Stay on the safe side, the rig amperage should follow the 80% rule, to consume 20% less than the <a href="https://es.aliexpress.com/item/1005004546671453.html?channel=twinner">Smart Plug</a>’s maximum supported power output. (the link might not serve your needs)</p><h3>Important Detail Most People Miss</h3><p>Time synchronization.</p><p>Your smart plug uses your <strong>phone’s clock</strong>, while Linux uses <strong>NTP</strong>.</p><p>If they’re not aligned:</p><ul><li>shutdown and power cut may overlap</li><li>you risk hard power loss</li></ul><p>Make sure:</p><ul><li>your phone has automatic time enabled</li><li>Linux has NTP enabled</li></ul><h3>Why Not Just Use a Smart Plug Alone?</h3><p>Because cutting power directly is dangerous.</p><p>Without a proper shutdown:</p><ul><li>filesystems can corrupt</li><li>logs can break</li><li>miners can behave unpredictably</li></ul><p>The key is:<br>→ <strong>clean shutdown first, power cut second</strong></p><h3>Why This Setup Is Powerful</h3><ul><li>Fully autonomous operation</li><li>No manual interaction required</li><li>Works with any Linux machine</li><li>Remote control via smart plug</li><li>Fail-safe (power cut acts as backup)</li><li>Avoids paid services</li></ul><h3>Real Use Cases</h3><p>This setup is ideal if you:</p><ul><li>want to mine only during <strong>cheap electricity hours</strong></li><li>run your rig using <strong>solar energy</strong></li><li>reduce noise/heat during certain times</li><li>extend hardware lifespan</li></ul><h3>Final Thoughts</h3><p>This isn’t just a mining tweak — it’s a shift toward <strong>power-aware computing</strong>.</p><p>Once you control <em>when</em> your system runs, you start optimizing:</p><ul><li>cost</li><li>efficiency</li><li>sustainability</li></ul><p>And the best part:</p><p>→ it runs itself.</p><p>If you’re building automation setups like this, this is one of the simplest and most effective upgrades you can make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3499c460ced" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Auto-Start Crypto Miners on Linux Using systemd]]></title>
            <link>https://medium.com/@cman.theman.1994/how-to-auto-start-crypto-miners-on-linux-using-systemd-7103a53de0e0?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7103a53de0e0</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[autostart]]></category>
            <category><![CDATA[crypto-mining]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 21:56:18 GMT</pubDate>
            <atom:updated>2026-04-06T21:57:24.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rkM18dVELzSKXW89r_ZKSw.png" /></figure><p>If you’re running crypto miners on Linux, manually starting them after every reboot quickly becomes inefficient. More importantly, you lose reliability — crashes, system restarts, or temporary failures can interrupt your mining without you noticing.</p><p>In this guide, I’ll show you <a href="https://gist.github.com/C-Man-The-Man/b82c7c2c7f36837db402b0e607d9cff6">how to run your miners as <strong>systemd services</strong></a>, turning them into fully autonomous, production-grade processes.</p><p>This approach works for:</p><ul><li>CPU miners like <a href="https://github.com/xmrig/xmrig"><strong>XMRig</strong></a></li><li>GPU miners like <a href="https://github.com/Lolliedieb/lolMiner-releases/releases"><strong>lolMiner</strong></a></li><li>Or virtually any other mining software</li></ul><h3>What You’ll Achieve</h3><p>By the end of this setup, your miners will:</p><ul><li>Start automatically on boot</li><li>Restart automatically if they crash</li><li>Run with proper privileges (no manual sudo)</li><li>Log output cleanly (no need for open terminals)</li><li>Allow fine control over CPU, memory, and system priority</li></ul><h3>Why systemd?</h3><p>Most beginners use:</p><ul><li>screen</li><li>tmux</li><li>or cron @reboot</li></ul><p>These work — but they’re not robust.</p><p><strong>systemd gives you:</strong></p><ul><li>Process supervision (auto-restart)</li><li>Dependency control (start after network/GPU drivers)</li><li>Resource management (CPU priority, memory locking)</li><li>Centralized logging (journalctl)</li></ul><p>In short: it’s the <strong>correct, production-grade solution</strong>.</p><h3>Quick Setup (Overview)</h3><p>Here’s the minimal workflow:</p><pre>sudo nano /etc/systemd/system/miner_name.service<br>sudo systemctl daemon-reload<br>sudo systemctl enable miner_name<br>sudo systemctl start miner_name<br>journalctl -u miner_name -f</pre><p>This replaces:<br>→ opening terminals<br>→ typing commands manually<br>→ re-running miners after reboot</p><h3>The Core Concept</h3><p>A systemd service is just a configuration file that tells Linux:</p><ul><li>what to run</li><li>when to run it</li><li>how to manage it</li></ul><h3>Generic Miner Service Template</h3><p>This is a reusable template for any miner:</p><pre>[Unit]<br>Description=Miner_Name Autostart Service<br>After=network-online.target<br>Wants=network-online.target<br><br>[Service]<br>Type=simple<br>WorkingDirectory=/path/to/miner<br><br>ExecStartPre=/bin/sleep x<br># Delays startup in &quot;x&quot; seconds → ensures system, network, and drivers are ready<br># Useful when multiple miners are used, start GPU miners before CPU miners<br># Keep under 60 seconds to avoid timeout on start operations error (TimeoutStartSec)<br># For more delay time, unhash the next line<br># TimeoutStartSec=180<br># Make sure TimeoutStartSec is higher than ExecStartPre<br><br>ExecStart=/path/to/miner/executable-or-script<br># Main miner process<br># Some miners use executables to run (e.g. XMRig), some, scripts (e.g. lolMiner)<br><br>Restart=always<br># Restarts miner automatically if it crashes<br><br>RestartSec=10<br># Wait before restart → avoids crash loops<br><br>Nice=-x<br># CPU priority → negative = higher priority<br># Range: -20 (highest priority)  →  0 (default)  →  +19 (lowest priority)<br># Example usage: -5 for XMRig, -10 for lolMiner<br><br>IOSchedulingClass=best-effort<br>IOSchedulingPriority=0<br># Improves disk I/O responsiveness<br><br>OOMScoreAdjust=-XXX<br># Protects process from being killed under memory pressure<br><br>StandardOutput=journal<br>StandardError=journal<br># Sends output to system logs (journalctl)<br><br>[Install]<br>WantedBy=multi-user.target</pre><h3>GPU Miner Setup (e.g. lolMiner)</h3><p>GPU miners depend on drivers being initialized. If they start too early, they may fail.</p><p>That’s why we introduce a <strong>startup delay</strong>.</p><pre>ExecStartPre=/bin/sleep 30</pre><h3>Key optimizations:</h3><ul><li>Nice=-10<br>→ gives higher CPU priority to reduce latency</li><li>After=nvidia-persistenced.service<br>→ ensures GPU drivers are ready</li><li>OOMScoreAdjust=-500<br>→ reduces risk of being killed under memory pressure</li></ul><h3>CPU Miner Setup (e.g. XMRig)</h3><p>CPU miners like XMRig are heavily dependent on memory performance.</p><pre>LimitMEMLOCK=infinity</pre><p>This is critical.</p><h3>Why?</h3><p>RandomX (used by XMRig):</p><ul><li>uses large memory datasets</li><li>is extremely sensitive to latency</li></ul><p>If memory gets swapped to disk:<br>→ your hashrate drops significantly</p><h3>Key optimizations:</h3><ul><li>Nice=-5<br>→ balances performance and system responsiveness</li><li>LimitMEMLOCK=infinity<br>→ prevents memory swapping</li><li>OOMScoreAdjust=-1000<br>→ protects the miner from being killed</li></ul><h3>Monitoring Your Miners</h3><p>Instead of running miners in terminals, you use:</p><pre>journalctl -u miner_name -f</pre><p>This gives you:</p><ul><li>live output (like a terminal)</li><li>persistent logs</li><li>access to previous sessions</li></ul><h3>Check status:</h3><pre>systemctl status miner_name</pre><h3>Common Issues (and Fixes)</h3><h3>1. Service fails with timeout</h3><p>If you use long delays:</p><pre>ExecStartPre=/bin/sleep 120</pre><p>You may hit systemd’s timeout.</p><p>Fix:</p><pre>TimeoutStartSec=180</pre><h3>2. Low hashrate CPU miners (e.g. XMRig)</h3><p>Usually caused by:</p><ul><li>huge pages not enabled</li><li>memory not locked</li></ul><p>Fix:</p><ul><li>enable huge pages</li><li>ensure LimitMEMLOCK=infinity is set</li></ul><h3>3. GPU not detected (e.g. lolMiner)</h3><p>Cause: drivers not ready at startup</p><p>Fix:</p><pre>After=nvidia-persistenced.service</pre><h3>4. Permission errors</h3><p>Make sure binaries are executable:</p><pre>chmod +x executable_or_script</pre><h3>Best Practices</h3><ul><li>Start GPU miners <strong>before</strong> CPU miners</li><li>Use delays to avoid race conditions</li><li>Keep configs generic and reusable</li><li>Avoid running miners manually once systemd is configured</li></ul><h3>Real-World Result</h3><p>With this setup:</p><ul><li>Your system becomes <strong>fully autonomous</strong></li><li>No manual intervention required</li><li>Stable long-term mining</li><li>Clean monitoring and debugging</li><li>Avoids paid services</li></ul><h3>Final Thoughts</h3><p>This approach is not just about convenience — it’s about <strong>operational reliability</strong>.</p><p>Whether you’re running:</p><ul><li>a single machine</li><li>a dedicated mining rig</li><li>or experimenting with optimization</li></ul><p><strong>systemd</strong> gives you the control layer you actually need.</p><p>Clean. Stable. Autonomous mining. Avoiding paid services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7103a53de0e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cómo montar un nodo MastChain AIS con Docker usando mastchain-config]]></title>
            <link>https://medium.com/@cman.theman.1994/c%C3%B3mo-montar-un-nodo-mastchain-ais-con-docker-usando-mastchain-config-ff340688e629?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff340688e629</guid>
            <category><![CDATA[mastchain]]></category>
            <category><![CDATA[spain]]></category>
            <category><![CDATA[depin]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ship-tracking]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 14:53:19 GMT</pubDate>
            <atom:updated>2026-04-07T23:56:15.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUbzCrjR7UxuCQeJ0-An-g.png" /></figure><h4>Introducción</h4><p>En esta guía aprenderás cómo desplegar un nodo <a href="https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5">MastChain</a> para recepción de señales AIS (Automatic Identification System) utilizando un SDR (RTL-SDR) y Docker, usando el repositorio automatizado:</p><ul><li><a href="https://github.com/C-Man-The-Man/mastchain-config">https://github.com/C-Man-The-Man/mastchain-config</a></li><li><a href="https://github.com/C-Man-The-Man/mastchain-ais">https://github.com/C-Man-The-Man/mastchain-ais</a></li></ul><p>El objetivo es facilitar una instalación reproducible, incluso para usuarios con conocimientos básicos de Linux.</p><h3>🧰 Requisitos de hardware</h3><p>Necesitarás:</p><ul><li>1× RTL-SDR (receptor AIS)</li><li>1× Antena para banda marina (~162 MHz)</li><li>1× Ordenador Linux (Raspberry Pi o mini PC)</li><li>Conexión a Internet estable</li><li>Fuente de alimentación adecuada</li></ul><h3>Dónde comprar en España</h3><ul><li><a href="https://www.amazon.es/-/en/RTL-SDR-Blog-RTL2832U-Software-Defined/dp/B0CD745394/ref=sr_1_32?crid=2MV99N7K7CNZH&amp;dib=eyJ2IjoiMSJ9.ypbz59vgpTbLtV4UQrBRFxvo4tuJKY7MLPqOMBT_vCYetvb3AXF1YXBCDiqWJKXcv0VGupLeKL2DUJ3_TCHZXXz3MN-yOfu72xlVJodNmuOhT6Gr57AZclHhlXYPV-LJRz4PdGWpYC326WpiU1m_qF6JYUr9oZojtIxYg5lZHfgBO7RzsGvFQdDvA53_xyh6HtaE96jF1U6iGvU9FmkF-z1k2Isg4lVh_-M6SdBuES5xQHvuXYG69Z05UgDGIVfXaFuqxc7jifSav-gqiFNney5QwuwyJQrH9S3IZLM9HFA.Tj5k8mP49e3vc-8FHRIIdic4haWRhWZjpfRG1tfYVIw&amp;dib_tag=se&amp;keywords=rtl-sdr+blog+v4&amp;qid=1775140212&amp;sprefix=rtl-sdr+blog+v4%2Caps%2C93&amp;sr=8-32">RTL-SDR</a></li><li><a href="https://www.amazon.es/-/en/UAYESOK-Antenna-Waterproof-Fiberglass-Adjustable/dp/B091HS8TBV/ref=sr_1_4?crid=PO4B2VLFFIJO&amp;dib=eyJ2IjoiMSJ9.gYRL09qRJjO1quLvJ-ZhJfl2edMQH1YefYcmXlcbuxsrLzXn3WkXbWG99BuC1UFfU3u3J7542JP33rszjmiRAzNSr2xH_a_DlUq95gBFeiR4IMVo7oR9B2463eXeu_ipHtDVNjcenmyMDOqJElVi4z-WsRWO5WIQYMlhggx7Xuj9RxmwoGACjQsH3G9w3pLoIoykI-ge-eWGhFx8le6xABHTofG1oCH_GBGk1aiftJuFxs9ySxHnaaUFpqW7eKfHC_5LWEzSAX9UlsyPGFrD5IVdTXjRx7FdBO2vSWWoKQo.DLBgwH0z1vDw7eMnKWQ1NXpB8ygUvzAE_luZYdU23zY&amp;dib_tag=se&amp;keywords=outdoor+marine+antenna+vhf&amp;qid=1775140320&amp;sprefix=%2Caps%2C96&amp;sr=8-4">Antena AIS / VHF</a></li><li><a href="https://www.pccomponentes.com/placa-base-raspberry-pi-5-pi5-2gb-arm-cortex-a76-ddr4-micro-hdmi-wifi-5-bluetooth-50-gpio-40-pines">Raspberry Pi 5 (cheap)</a> + <a href="https://www.pccomponentes.com/raspberry-fuente-de-alimentacion-usb-c-27w-para-raspberry-pi-5">Fuente de Alimentación</a> + <a href="https://www.pccomponentes.com/sandisk-extreme-microsdxc-32gb-clase-10-uhs-i-adaptador">Tarjeta MicroSD</a></li></ul><p>💡 Recomendación: una antena de calidad influye más en el rendimiento que el propio SDR.</p><h3>🖥️ Instalación del sistema</h3><h3>🐳Instalar Docker</h3><p>En Linux:</p><pre>sudo apt update<br>sudo apt install -y docker.io docker-compose<br>sudo systemctl enable docker<br>sudo systemctl start docker</pre><p>Opcional (usar Docker sin sudo):</p><pre>sudo usermod -aG docker $USER</pre><p>Cerrar sesión y volver a entrar.</p><h3>📦 Instalación de mastchain-config</h3><p>Clonar el repositorio:</p><pre>git clone https://github.com/C-Man-The-Man/mastchain-config.git<br>cd mastchain-config</pre><h3>⚙️ Configuración</h3><p>Editar el archivo .env (si existe o se proporciona en el repo):</p><pre>nano .env</pre><p>Configurar variables relevantes (según el repositorio), como:</p><ul><li>zona horaria</li><li>parámetros SDR</li><li>configuración de contenedores</li></ul><h3>🚀 Ejecución</h3><p>Ejecutar el stack:</p><pre>docker compose up -d</pre><p>Ver logs:</p><pre>docker compose logs -f</pre><h3>📡 Verificación del SDR</h3><p>Comprobar que el dispositivo RTL-SDR funciona:</p><pre>rtl_test -t</pre><p>Si el dispositivo aparece correctamente, el sistema está listo.</p><h3>🔍 Verificación de datos AIS</h3><p>Puedes comprobar que se reciben señales observando los logs del contenedor AIS:</p><pre>docker logs -f mastchain</pre><p>Deberías ver mensajes relacionados con señales AIS detectadas.</p><h3>⚠️ Consideraciones importantes en España</h3><ul><li>Uso de red eléctrica: 230V / enchufes tipo F</li><li>Interferencias RF en ciudades grandes (Madrid, Barcelona)</li><li>Mejor rendimiento con antena exterior</li><li>Evitar puertos USB 3.0 cercanos al SDR</li><li>Ubicación elevada mejora significativamente la recepción</li></ul><h3>🛠️ Solución de problemas comunes</h3><h4>El SDR no se detecta</h4><ul><li>Ejecutar:</li></ul><pre>rtl_test -t</pre><ul><li>Cambiar puerto USB</li><li>Reiniciar el sistema</li></ul><h4>No se reciben datos AIS</h4><ul><li>Revisar antena</li><li>Verificar conexión</li><li>Confirmar logs del contenedor</li></ul><h4>Problemas con Docker</h4><ul><li>Reiniciar servicios:</li></ul><pre>sudo systemctl restart docker</pre><h3>📌 Conclusión</h3><p>Con mastchain-config, desplegar un nodo MastChain AIS se simplifica significativamente, permitiendo a cualquier usuario en España contribuir a la red con una configuración reproducible basada en Docker.</p><p>Si este artículo te ha resultado útil, considera usar mi código de referencia para registrarte y participar en el proyecto: https://app.mastchain.io/auth/sign-in?ref=xeX9FeN5</p><p>¡Gracias!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff340688e629" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Wingbits and Mastchain on the Same Host (Without USB Conflicts]]></title>
            <link>https://medium.com/@cman.theman.1994/running-wingbits-and-mastchain-on-the-same-host-without-usb-conflicts-974fee352190?source=rss-6a47577ef8b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/974fee352190</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[diy]]></category>
            <dc:creator><![CDATA[C-Man]]></dc:creator>
            <pubDate>Wed, 14 Jan 2026 20:32:11 GMT</pubDate>
            <atom:updated>2026-04-01T09:24:04.068Z</atom:updated>
            <content:encoded><![CDATA[<p>Running both <a href="https://wingbits.com/"><strong>Wingbits</strong></a><strong> (ADS-B aircraft tracking)</strong> and <a href="https://mastchain.io/"><strong>Mastchain</strong></a><strong> (AIS ship tracking)</strong> on the same computer is a common goal for <strong>BYOD/DIY</strong> enthusiasts in the <strong>DePIN </strong>(<strong>De</strong>centralized <strong>P</strong>hysical <strong>I</strong>nfrastructure <strong>N</strong>etworks)<strong> </strong>space. Both projects rely on USB SDR receivers, and at first glance, this setup seems straightforward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4avq_k_ix7sok0Wua829g.png" /></figure><p>In practice, many users encounter a frustrating issue:<br> <strong>both applications try to use the same SDR device</strong>, even when two different receivers are connected.</p><p>This article explains <em>why</em> that happens and presents a <strong>simple, reliable setup</strong> that works for everyday users, without deep technical knowledge.</p><p><a href="https://youtu.be/9QfN1wTNGIk?is=ZC3x-cfgJrl47avJ">Click here for the Wingbits/Mastchain video setup!</a></p><h3>The core problem (in simple terms)</h3><p>USB SDR receivers look very similar to the operating system. When more than one is plugged in:</p><ul><li>Some software can <strong>choose a device by serial number</strong></li><li>Other software can <strong>only grab the “first” device it sees</strong></li></ul><p>This difference is the root cause of most conflicts.</p><h3>How the two applications behave</h3><ul><li><strong>Wingbits</strong> (via readsb)<br> ✔ Can select a specific SDR using its <strong>serial number</strong><br> ✔ Very reliable when multiple receivers are present</li><li><strong>Mastchain </strong>(via librtlsdr)<br> ✖ Cannot reliably select a device by serial number<br> ✔ Always uses the <strong>first detected USB SDR</strong></li></ul><p>Because of this, Mastchain may unexpectedly attach to the ADS-B receiver unless the system is arranged carefully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zgMGpxHFrmQkk4qfdvgmQ.png" /><figcaption>The diagram use a Raspberry Pi 4 as an example, it assumes that the bottom blue USB port is detected and enumerated first by the host</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KwXKqVYFAOCpSHfaCweHQQ.png" /><figcaption>A shielded USB cable is recommended to be used with the AIS receiver, mostly any other commercial receiver can be used.</figcaption></figure><h3>The practical solution</h3><p>Instead of trying to force unsupported behavior, the solution is to <strong>work with how each application is designed</strong>.</p><h3>The approach</h3><ol><li><strong>Physically control device order</strong></li></ol><ul><li>Plug the <strong>AIS receiver</strong> into the USB port that enumerates first</li><li>Plug the <strong>ADS-B receiver</strong> into another port</li></ul><p><strong>2. Verify devices once</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*V5FK7P22pTq9YEPbS-gCgQ.png" /><figcaption>Tested on Raspberry Pi 4, in this specific case, a Crankk MNTD Gold gateway</figcaption></figure><p>Use a simple command (rtl_test -t) to confirm:</p><ul><li>Which device is “device 0”</li><li>Which serial number belongs to which receiver</li></ul><blockquote>For the command to properly work, rtl_test and udev rules have to be part of the system.</blockquote><p><strong>3. This approach was tested using Docker Containers</strong></p><p><a href="https://github.com/C-Man-The-Man/mastchain-ais"><strong>Mastchain container</strong></a><strong> build</strong></p><ul><li>Automatically uses device 0 (AIS receiver)</li><li>Built for exclusive Mastchain use</li><li>Web Viewer included</li><li>Configuration file config.json to edit parameters</li><li>Refer to the Readme file for detailed installation steps</li></ul><p><a href="https://github.com/C-Man-The-Man/wingbits-rtl-feeder"><strong>Wingbits containers</strong></a><strong> build</strong></p><ul><li>Explicitly selects the ADS-B receiver by <strong>serial number</strong> using an .env file</li><li>Forked specifically for this setup, but can be run independently</li><li>udev rules complete set and explained</li><li>Clear .env configuration file</li><li>Refer to the Readme file for detailed installation steps</li></ul><p>This setup is stable, repeatable, and survives reboots.</p><blockquote>Each repository includes step-by-step instructions, but this article is intended to show <strong>why</strong> the setup works — not overwhelm you with commands and instructions.</blockquote><h3>How the system fits together</h3><p><strong>In short:</strong></p><ul><li>One computer (tested on Ubuntu 24.04 and Raspberry Pi OS x64 environments, the Mastchain build should work on any x64 OS that supports Docker containers, but the Wingbits build doesn’t support Mac and Windows)</li><li>Two SDR receivers</li><li>Docker containers for better management</li><li>No conflicts</li></ul><p>Each application uses the receiver it is best suited to handle.</p><h3>Why this works well for non-technical users</h3><ul><li>No custom udev scripting required</li><li>No recompiling libraries</li><li>No complex command-line logic</li><li>Clear separation of responsibilities</li></ul><p>All configuration is handled through <strong>simple files</strong> and well-documented defaults.</p><h3>Summary</h3><p>If you want to run <strong>Wingbits and Mastchain on the same machine</strong>, the key is understanding that:</p><ul><li>Not all SDR software selects devices the same way</li><li>Physical USB order still matters</li><li>Explicit device selection (when supported) removes guesswork</li></ul><p>By combining <strong>intentional USB placement</strong> with <strong>containers designed for this use case</strong>, you get a clean, reliable solution that works for both technical and non-technical users alike.</p><blockquote>Notes: <br>- The <a href="https://jvde-github.github.io/AIS-catcher-docs/installation/docker/"><strong>AIS-Catcher-Controller</strong></a> build can be used instead on my <strong>Mastchain</strong> one if desired. <br>- Any other <strong>Wingbits</strong> build was not tested for the scope of dual-”mining” at the time this article was released, my fork adapted the <a href="https://github.com/sicXnull/wingbits-ultrafeeder"><strong>sicXnull’s Wingbits</strong></a> repository.</blockquote><h3>Update (April 2026)</h3><p><strong>Wingbits</strong> introduced a new **Beast encoding requirement**.</p><p>My Docker setup has been updated to support this automatically.</p><p>👉 If you followed this guide earlier, simply pull the latest version of my repo and restart your containers.</p><p>No hardware changes are required.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=974fee352190" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>