<?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 Goldie on Medium]]></title>
        <description><![CDATA[Stories by Goldie on Medium]]></description>
        <link>https://medium.com/@oGGoldie?source=rss-e29ac408a633------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yDs1hnyGZJ9mAbXh3rqxBQ.jpeg</url>
            <title>Stories by Goldie on Medium</title>
            <link>https://medium.com/@oGGoldie?source=rss-e29ac408a633------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:23:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oGGoldie/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[Flux Titan Staking Guide]]></title>
            <link>https://medium.com/@oGGoldie/flux-titan-staking-guide-e0fb6ead6254?source=rss-e29ac408a633------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0fb6ead6254</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[flux-protocol]]></category>
            <category><![CDATA[flux]]></category>
            <dc:creator><![CDATA[Goldie]]></dc:creator>
            <pubDate>Wed, 20 Jul 2022 16:31:23 GMT</pubDate>
            <atom:updated>2022-07-20T17:07:27.426Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this article, I will guide you through the process of staking your FLUX coins via Titan staking, a way to earn rewards on your flux tokens known as ‘Proof of Useful Stake’</em></p><p><strong>If you wish to learn more about Flux Titan, and how Titan nodes operate, please see this informative article written by the Flux Foundation: </strong><a href="https://fluxofficial.medium.com/flux-titan-nodes-beta-go-live-on-july-20th-af1fa9ee5d54">Flux Titan nodes beta go live on July 20th! | by Flux Official | Jul, 2022 | Medium</a></p><h3>Prerequisites</h3><p>In order to stake FLUX via Titan, you must meet the following requirements:</p><ol><li>A minimum of 50 FLUX (Must be native FLUX)</li><li>A maximum of 10,000 FLUX per single stake</li><li>A maximum of 20,000 FLUX total staked</li><li>Zelcore Wallet (can be downloaded from here: <a href="https://zelcore.io/">Home — Zelcore</a>)</li><li>A valid zellID</li></ol><h3>Lets get started</h3><h3>Step 1 - Navigate to the Flux dashboard and login</h3><p>Titan staking is all done via the FluxOS dashboard, which runs on and is accessible from every node on the Flux network.</p><p>Navigate to home.runonflux.io, which will pull up the FluxOS dashboard of a random node: <a href="https://home.runonflux.io/">FluxOS Dashboard (runonflux.io)</a></p><p>You’ll be presented with a page which shows some information about the node you’re currently viewing. In order to stake your Flux, you’ll need to login with your ZellID</p><p>Click the fingerprint looking icon shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcZpIx7Km96f46h9jEsfww.png" /></figure><p>This will open up Zelcore, which will prompt you to login if you have not already done so</p><p>Next, a popup should appear within Zelcore, asking for you to input your ZellID pin. Enter your pin and click “Sign and Send”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NXUbLuP7nHLK2MbujxnlkQ.png" /></figure><p>You should now be logged in to FluxOS with your ZellID</p><h3>Step 2 - Navigate to the Titan page</h3><p>On the left-hand side of the dashboard page, you should see a navigation menu. Find “Marketplace”, click on it, and click the “Marketplace” link that appears in the drop down</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*I_Oy2O8sFijMS3vSPY_sGw.png" /></figure><p>Next, click “Shared Nodes” from the list of catagories</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*A96c_puQfHzfgY2d7-vYfw.png" /></figure><p>You will now be on the Titan staking page</p><p><em>Note: You can also navigate to this page via this link: </em><a href="https://home.runonflux.io/apps/shared-nodes"><em>FluxOS Dashboard (runonflux.io)</em></a></p><h3>Step 3 - Stake your Flux</h3><p>From this page, you can view how many Titan nodes are live, how much FLUX is staked, your active stakes, and more. Take some time to explore this page</p><p>To get your FLUX staked, firstly you need to create a new stake.</p><p>Click the “Stake Flux”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3heF6XtujUYj8eA3xltzw.png" /></figure><p>This will open up a window.</p><p>This first page allows you to configure your stake amount. Enter in the amount of FLUX you wish to lock up and click Next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qhxvVwuaLoG7YBVpi25FGQ.png" /></figure><p>This next page allows you to choose your lockup duration. You can see longer lock-ups will earn a higher yield. There is also an option to auto-reinvest your stake after the lockup period expires.</p><p>Once you have configured these, click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJHZNNQjlTWFuM1xboJhmg.png" /></figure><p>Next, you will need to sign the stake with your ZellID. Click the fingerprint button, and enter your pin in Zelcore like you did before to sign into FluxOS initially.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIgi429onKOdEDFTRXZyaA.png" /></figure><p>Next, you’ll need to register your stake. Please be sure to read the warning on this page. Once sent, your FLUX cannot be unlocked until the lockup period has ended. This is set in stone.</p><p>Click the “Register Stake” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7vamL6B2SoixeXkVqG-Vw.png" /></figure><p>The page will change to show registration received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1NEsJpVgSX8r7JA6v-LrA.png" /></figure><p>Click next</p><p>Finally, you need to actually send your FLUX to be staked. FLUX staked in Titan is sent to a multi-sig wallet. This wallet is completely safe and cannot be accessed.</p><p>You can choose to either manually create the transaction, making sure to send to the correct wallet address and containing the message in the transaction memo, or you can click the fingerprint button to automatically be taken to Zelcore with a pre-configured transaction ready for you to sign and send.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MHRfThPuCnvX7Xnqm7SlPw.png" /></figure><p>If you click the fingerprint button, a pop-up will appear in Zelcore with a payment request. Click “Proceed to pay”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ha9Eah9r194LmRKG9AgaQ.png" /></figure><p>This will open a send transaction with all the info pre-configured. Simply click send.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHykm7pjOVLbbNS6VpvR3g.png" /></figure><p>Now go back to the FluxOS dashboard, and click finish. This will bring up a prompt asking you to check you’ve sent the FLUX. Click yes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3zQ4NKx_P58Ry4vHvLf_g.png" /></figure><h3>Step 4 - Wait for your Flux to confirm</h3><p>Once you have finished the staking process, you should see your stake appear in the active “Active Stakes” table within your dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CDtuFAAfgbKFK8xRX26oyg.png" /></figure><p>Before your stake can start, your FLUX needs to be completely confirmed. This requires 30 confirmations from the Flux blockchain of your transaction. Each block takes roughly 2 minutes to be found, and therefore your stake will go live after around 60 minutes.</p><p>Once your stake is fully confirmed and live, it will appear as such:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zthhabO4NZNNJLXcgkhodA.png" /></figure><h3>Step 5 - Redeem your earnt FLUX</h3><p>To be continued…</p><h3>Conclusion</h3><p>Congratulations, you are now actively contributing to the future of Web3 and the Flux network by providing Flux towards Proof of Useful Staking.</p><p>Learn more about flux at <a href="https://runonflux.io/">Flux — Decentralized Cloud Infrastructure (runonflux.io)</a></p><p>If you are having any issues, feel free to hop into the Flux Offical discord and post a question in the support channel <a href="https://discord.io/runonflux">https://discord.io/runonflux</a></p><p>Or ping me directly on Discord @Goldie ¯\_(ツ)_/¯#0001</p><p><em>Note: This guide is not official or from the Flux team, I am just a community member who wants to help :)</em></p><h4>If you found it helpful, please consider chucking me a flux or 2 ❤️</h4><h4>t1fj6hgzxSEJEqwgWCyF8TJ57zRwffEneGF</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*UaCVCmTCS_dTsRWS" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0fb6ead6254" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flux Node Halving Post Mortem]]></title>
            <link>https://medium.com/@oGGoldie/flux-node-halving-post-mortem-e90aae365370?source=rss-e29ac408a633------2</link>
            <guid isPermaLink="false">https://medium.com/p/e90aae365370</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[flux]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Goldie]]></dc:creator>
            <pubDate>Sat, 16 Apr 2022 16:51:47 GMT</pubDate>
            <atom:updated>2022-04-16T16:51:47.386Z</atom:updated>
            <content:encoded><![CDATA[<p><em>With more than 10,000+ nodes now deployed on the Flux network, Flux continues to cement itself as </em><strong><em>THE</em></strong><em> Web 3.0 project to take the world by storm. Demand for Web 3.0 infrastructure is on the rise, and with the conclusion of the latest halving of Flux node collateral, Flux has yet again proven its ability to scale.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jO37PAY0SVi9fvHI5IaMQw.png" /></figure><p>Demand for Flux has never been higher, with the price of the Flux utility token soaring to new all time highs. Pre-halving, it was apparent that the Flux team were facing a new problem, in that the utility token required for node collateral was becoming unaffordable for a majority of new members of the Flux community.</p><p>The original <a href="https://www.youtube.com/watch?v=Ilp8Ca-dtQ0">Flux economic model</a> was designed to ensure sustainable tokenomics and create various avenues of scaling the network. After much consideration and analysis, the team decided the next best way forward would be to hold a Node halvening and system requirement update.</p><p>The pre-halving Node structure can be seen below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nDaQV8M8HJ4VWOL_.png" /></figure><p>The team came up with a revised node structure and timeline that would scale the Flux network by increasing the number of nodes and computational resources while allowing new people coming into the ecosystem to participate in a decentralized manner.</p><p>The post-halving (and current model at the time of writing this) can be seen below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LcuAZG3_God7FbrTUvdZ5g.png" /></figure><p>The halving official kicked off March 13th 2022, at the block height 1076532, with Cumulus nodes taking the lead in implementing the new structure.</p><p>Here is the full timeline for the transition period</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eREOSx-ieEG8unFgfociBg.png" /></figure><h3>How Effective was the Halving?</h3><p><em>Note: All screenshots pre-halving are from a </em><a href="https://web.archive.org/web/20220313202301/https://home.runonflux.io/dashboard/overview"><em>WayBackMachine snapshot taken on March 13th</em></a><em>, though the stats actually show for the 11th of January 2022.</em></p><h4>Pre-Halving</h4><p>On the 11th of January 2022, the Flux network was around 2760 nodes strong, with about 50% of the total nodes being Cumulus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YEld3n0DPC9BN-2z0D4zHw.png" /></figure><p>85,780,000 total Flux was locked up in Flux Nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bB4DAHDrMU7bFN82102-zw.png" /></figure><p>Below you can see the network stats from the 11th of January 2022. As you can see, Flux bolstered some impressive numbers and respectable computing power.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zEp2KiOkIkjWt-xNYC9ylw.png" /></figure><h4>Post-Halving</h4><p>Now that we have seen the network before the halving, let’s now take a look at the state of play post-halving (all data taken from today, April 16th 2022, from the <a href="https://home.runonflux.io/dashboard/overview">dashboard</a>)</p><p>In terms of total nodes on the network, this number has almost quadrupled in the 3 months from the previous screenshots, with just under 10,100 nodes now online. Cumulus nodes make up over 70% of the network currently, and the rate of growth for the network has averaged more than 160 new nodes per day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ZVboHa5wakTw_FFIlmz4g.png" /></figure><p>In terms of locked up supply, the total amount of Flux locked up is actually 40K lower than in the previous example, exemplifying the ability for Flux to scale and adapt to changing economics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kqMBPTBwMo4VgnziPZAhCg.png" /></figure><p>The next screenshot is the most telling. The raw processing power and computational capacity of the Flux network has scaled massively. Total Cores is up by more than x7.5 since January, as well as RAM and SSD storage rocketing to impressive numbers. Flux is now the biggest Web 3.0 network in existence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NaMIp7W4qYkAOphfqnpAzg.png" /></figure><p>It is worth noting that post-halving, the Flux network is now host to 7,000+ instances, with the ability to host more than 1.2 Million instances.</p><h4>The Result</h4><p>It’s clear from these numbers alone that the halving has been a massive success for Flux, exceeding expectations across the board.</p><p>The halving has allowed Flux to increase the number of nodes and computational resources while allowing new people to come into the ecosystem to participate in a decentralized manner.</p><h3>The future</h3><p>The Flux network is primed to shoot for centre stage in the Web 3.0 space. With Project Titan and Cirrus on the horizon, and many new announcements in the pipeline for the rest of 2022 and into 2023, Flux is the place to be. The success of the node halving has enabled Flux to further decentralise and scale, allowing for enterprise grade performance on a network owned by the people, for the people.</p><p>To learn more about Flux, visit the official Flux website: <a href="https://runonflux.io/">Flux — Decentralized Cloud Infrastructure (runonflux.io)</a></p><p>For the most up-to-date stats on the Flux network, visit the Flux dashboard: <a href="https://home.runonflux.io/dashboard/overview">FluxOS Dashboard (runonflux.io)</a></p><p>Join the Flux official Discord: <a href="https://discord.io/runonflux">https://discord.io/runonflux</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e90aae365370" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flux 10,000 Node Celebration AMA Summary]]></title>
            <link>https://medium.com/coinmonks/flux-10-000-node-celebration-ama-summary-8aa88d350728?source=rss-e29ac408a633------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aa88d350728</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[flux]]></category>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Goldie]]></dc:creator>
            <pubDate>Sat, 16 Apr 2022 10:18:33 GMT</pubDate>
            <atom:updated>2022-04-23T07:24:31.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgAAfwUohODYtuKy63LPjw.png" /></figure><p><strong>To celebrate Flux reaching 10,000 live nodes, Daniel held an impromptu AMA.</strong></p><p><em>You can watch back the AMA on YouTube here: </em><a href="https://www.youtube.com/watch?v=ipC4UKwUnSk"><em>https://www.youtube.com/watch?v=ipC4UKwUnSk</em></a></p><h4>What is Flux?</h4><p>Flux is a comprehensive suite of decentralized computing services and blockchain-as-a-service solutions. The Flux ecosystem consists of: Fluxnodes’ decentralized infrastructure, FluxOS cloud operating system, Zelcore self-custody multi-asset wallet and blockchain app suite, and finally the Flux blockchain for on-chain governance, economics, and parallel assets to provide interoperability with other blockchains and DeFi access.</p><p>Flux provides the critical, high availability infrastructure for the New Internet. Projects and development teams are not forced to rely on the Flux blockchain to utilize FluxOS, so they have access to necessary infrastructure while maintaining all the unique properties of their own chains. Flux makes up one important piece of a well-balanced distributed computing portfolio focused on the next generation of the Internet.</p><h3>Here is a written summary of the AMA</h3><h4>Question: If all the available Flux tokens are locked up in nodes, how will app developers pay to deploy their app on the Flux network?</h4><p>This particular situation is extremely unlikely, due to the economics of Flux and financial markets in general. However, Flux has the ability to be divisible into Micro Flux, down to 0.0000001 FLUX. Much like how bitcoin has satoshis, Flux may be traded in the Micro rather than in whole tokens.</p><p>As for the payment of deployment, this can be evaluated and adapted to match the current price and availability of Flux to ensure the system works.</p><h4>Question: How will the Flux economic model change when the last Flux is mined?</h4><p>It is estimated that the last Flux token will be mined in around 125 years time. Between now and then, there is plenty of time to make decisions to adapt the economic model to suit the current landscape.</p><h4>Question: When can we expect the new internet speeds benchmarks to be implemented?</h4><p>The Flux team plan to gather quantitive data of internet speeds across all nodes on the network before enforcing this benchmark, however this benchmark will be necessary for Flux to provide enterprise grade performance.</p><p>The Flux team assures that the internet speeds benchmark will be as low as feasible, without any compromise to the output of the Flux network as an industry leading Web3 computing network.</p><h4>Question: Will node operators be rewarded a share of the incoming Flux from developers paying for dApp deployment?</h4><p>Currently, the cost to launch a dApp on the Flux network is at break even. This price model is to draw in new developers and get the Flux network working. It is planned that this Flux income stream will go back to the foundation (which now has over 50 developers and team members) to allow for the continued support and development of Flux, however in the future, a community xDAO can be used to allocate this Flux income stream.</p><h4>Question: What is the plan for additional revenue streams for node operators?</h4><p>Currently, node operators are paid the Flux block reward in a round robin queue system. There is no plan to change this, and as more nodes come online, the income from this stream is likely to decrease further. However, there will be two other ways for node operators to increase their income in the future.</p><p>Firstly, nodes will be further specialised into class, where each class will focus on a specific use case or function. For example, a currently unannounced node tier will be picked to run project Thunder, a data persistence node which will focus on storage of data and databases long term (such as NFT media). These classes will each have their own tiers and benchmark requirements, and will result in additional incentives for the operator.</p><p>Secondly, Flux Labs projects and marketplace apps will provide rewards to node operators in their project’s reward token, much like the current KDA and Presearch on flux nodes.</p><h4>Question: Will it be possible to make data and codebase private when deployed on project Thunder?</h4><p>Yes. Persistent storage nodes will store data securely and privately, however the current running test of Thunder nodes does not yet store data privately.</p><h4>Question: How does Flux plan to combat the dilution of block rewards for nodes, to the point where an operator may be waiting months between node rewards?</h4><p>Flux has no plans to change the economic structure of Flux or block rewards. As previously mentioned, more nodes results in more opportunities for node operators to actively generate income.</p><p>However, Titan nodes can provide investors some stability and resistance to varying APY or the issue of missed rewards due to nodes going offline, locking collateral for 3 months, 6 months, or 1 year at a time.</p><h4>Question: Will we be able to view the dApps currently running on the Flux network and how much resources they are using?</h4><p>Yes! Jetpack 2.0 will provide a dashboard with metrics and data of dApps running on the network in real time, as well as the network’s capacity and processing power. This live data can be used to generate comparisons between Flux and the other Web3 projects or Web2 products, such as AWS or Microsoft Azure. API integrations for all this data and more are also planned for Jetpack 2.0.</p><h4>Question: What prevents illegal data being hosted on Flux?</h4><p>Currently, everything deployed on the Flux network is vetted by the Flux dev team. However, in the future, anything deployed onto Flux will need to adhere to the community terms of service, governed by an xDAO.</p><p>Ultimately, Flux is not responsible or liable for what is deployed on the Flux network, as no one entity controls or owns Flux. The responsibility and ownership of data on the Flux network goes back to the user who deployed it in the first place (which can be tracked using ZelID).</p><h4>Question: Will NFTs be coming to Flux?</h4><p>NFTs are made up of two pieces; the smart contract/token that governs and represents the NFT on the blockchain, and the digital media linked to the token.</p><p>With plans for ZelCore to support NFTs, Flux is well suited to provide the backend decentralised data storage and persistence for NFT media through upcoming project Thunder.</p><h4>Question: Is there a limit to how many Parallel Assets can be deployed on Flux?</h4><p>No, Flux would love to have a Parallel Asset on every chain it possibly can, and allow Flux to interconnect chains and Web3.</p><h4>Question: Are there going to be anymore Parallel Asset airdrops after the initial 10?</h4><p>There are no plans to continue running Parallel Asset airdrops after the tenth airdrop has completed. Additionally, every snapshot proceeding the May 5th snapshot will give an increasingly lower percentage of PAs to total Flux balance, as a part of Flux’s deflationary economic model.</p><h4>Question: Will there be a maximum amount of Titan nodes?</h4><p>Initially, Titan nodes will only be deployable by trusted community members, the foundation, and trusted partners. This will be temporary to allow Flux to ensure the smooth functionality of Titan nodes and that the proper working systems are in place.</p><p>After this trial period, a limited number of Titan nodes will exist on the network, which the Flux team will keep tabs on to ensure they are functioning correctly and setup correctly under the hood. These nodes will be deployed staggered, to ensure both that they are spread across all regions of the world, and that they don’t all expire simultaneously.</p><h4>Question: Will Titan nodes be situated with consideration to green energy or renewable solutions?</h4><p>Yes! Flux plans to make a massive push for greener tech, and part of this will be planning Titan nodes around greener tech. Flux strives to reduce the carbon footprint of running all this technology, and PoUW is another example where Flux intends to not let a single byte go to waste.</p><h4>Question: Can you provide more details on PoUW (Proof of Useful Work) and when we can expect more from it?</h4><p>PoUW will revolutionise the way we mine cryptocurrencies. PoUW will utilise the entire computing capacity of graphics cards to provide useful work to the Flux network (such as graphics intensive tasks such as rendering videos or generating computer simulations). This will all be possible with a new mining algorithm that is still in development. Flux plans to make this algorithm Open Source, changing the cryptosphere forever. More details are planned for Q3-Q4.</p><h4>Question: Are there any details about the M-group marketing announcement?</h4><p>Flux decided to partner with M-Group as part of a greater strategy for Flux to focus more on enterprise customers. Flux will be changing how it markets to give a more coherent and professional standard of marketing. This can already be felt in the likes of Flux’s medium articles, which have made more of a focus on the technical and logistical details, as well as changes to the Flux team internally.</p><p>This does not mean Flux is ditching its retail marketing strategy, quite the opposite in-fact. The Flux Army provide a strong community push and Flux ambassadors continue to play a key part of the Flux marketing push around the world.</p><h4>Question: If a Venture Capital wanted to get involved with Flux, how best could they go about it?</h4><p>Buy! The Flux team do not sell tokens, and have never sold tokens. Flux can only be bought publicly.</p><h4>Question: Are there any plans to hold public developer meetings?</h4><p>Yes. Flux plans to hold public developer meetings, likely on a Saturday, that you can tune into and have limited interaction with.</p><h4>Question: Are Multi-sig wallets in the plan for Flux and ZelCore?</h4><p>Multi-sig wallets are planned for both Flux and ZelCore. Titan nodes will require multi-sig wallets for their shared collateral lockups, and currently Flux multi-sig wallets do exist in a test environment.</p><h4>Question: How do I go about joining the Flux team?</h4><p>The best way would be to join the Flux Official Discord and grab a moderator who can point you in the right direction.</p><h4>Question: Will there be incentives to run Flux nodes on bare-metal (at home hosting)</h4><p>Yes. More details will be announced in Q3.</p><p>As an added point, Cirrus nodes will almost exclusively run on bare-metal.</p><h4>Question: How will Flux know if you are hosting at home, as opposed to hosting with a cloud provider?</h4><p>This will be left largely up to the community to decide. IP address is the easiest vector, but the Flux team are hard at work with other solutions. More to be announced Q3.</p><h4>Question: Is there any plans for a ZelCore hardware wallet?</h4><p>It is on the shortlist. It is planned for ZelCore to provide the UI frontend of a hot-wallet, and then the hardware wallet to provide the cold storage for your assets. This integration will allow users to utilise all the functionality of ZelCore and Flux nodes, with the protection and ownership of a hardware wallet. Planned for sometime next year.</p><p>To learn more about Flux, visit <a href="https://runonflux.io/index.html">Flux — Decentralized Cloud Infrastructure (runonflux.io)</a></p><blockquote>Join Coinmonks<a href="https://t.me/coincodecap"> Telegram Channel</a> and<a href="https://www.youtube.com/c/coinmonks/videos"> Youtube Channel</a> learn about crypto trading and investing</blockquote><h3>Also, Read</h3><ul><li><a href="https://coincodecap.com/best-cardano-wallets">Best Cardano Wallets</a> |<a href="https://coincodecap.com/bingbon-copy-trading"> Bingbon Copy Trading</a></li><li><a href="https://coincodecap.com/p2p-crypto-exchanges-in-india">Best P2P Crypto Exchanges in India</a> |<a href="https://coincodecap.com/baby-shiba-inu-wallets"> Shiba Inu Wallets</a></li><li><a href="https://coincodecap.com/crypto-affiliate-programs">Top 8 Crypto Affiliate Programs</a> |<a href="https://coincodecap.com/etoro-vs-coinbase"> eToro vs Coinbase</a></li><li><a href="https://coincodecap.com/best-ethereum-wallets">Best Ethereum Wallets</a> |<a href="https://coincodecap.com/telegram-crypto-bots"> Cryptocurrency Bots on Telegram</a></li><li><a href="https://coincodecap.com/leveraged-token-exchanges">Best Exchanges to Trade Leveraged Tokens</a> |<a href="https://coincodecap.com/buy-floki-inu-token"> Buy Floki</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aa88d350728" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/flux-10-000-node-celebration-ama-summary-8aa88d350728">Flux 10,000 Node Celebration AMA Summary</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flux Multi-Node Server Setup]]></title>
            <link>https://medium.com/@oGGoldie/flux-multi-node-server-setup-7cd8887fe268?source=rss-e29ac408a633------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cd8887fe268</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[flux-protocol]]></category>
            <category><![CDATA[flux]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Goldie]]></dc:creator>
            <pubDate>Mon, 28 Mar 2022 08:39:56 GMT</pubDate>
            <atom:updated>2022-05-02T05:43:08.637Z</atom:updated>
            <content:encoded><![CDATA[<h4>Setup a dedicated server to run multiple instances of Flux node, with only 1 public IP address (Hetzner Specific)</h4><p><em>In this article, I will guide you through the process of setting up a dedicated server to run multiple flux node instances, each running within a VM (virtual machine), setup to use UPnP (Universal Plug and Play) to operate with just a single public IP address.</em></p><p><strong>If you are not planning to run multiple nodes on a single system, this is the wrong guide for you. Follow Step 1 (Installing Ubuntu instead) and then follow this guide instead: </strong><a href="https://medium.com/@mmalik4/flux-light-node-setup-as-easy-as-it-gets-833f17c73dbb"><strong>Flux Light Node Setup — As easy as it gets !! | by Ali Malik | Medium</strong></a></p><h3>Prerequisites</h3><h3>1. The required Flux collateral per node you wish to host</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibFDHANAN3wcTkVSQ-n_0Q.png" /></figure><p>For every node you host, you will need to lock up the required Flux collateral for that node’s tier per node. For more information, please see: <a href="https://medium.com/@mmalik4/flux-light-node-setup-as-easy-as-it-gets-833f17c73dbb">Flux Light Node Setup — As easy as it gets !! | by Ali Malik | Medium</a></p><h3><strong>2. A dedicated server to run your node instances</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SiCZJGynIVDiXykcQ5iZHg.jpeg" /></figure><p>In this guide, I will walk you through the setup of an <a href="https://www.hetzner.com/dedicated-rootserver/ax101/configurator#/">AX101 from Hetzner</a>. This server can handle up to 2 Stratus nodes, or a combination of all 3 tiers (to a maximum of 8 nodes, as per Flux’s maximum per public IP). See here for details on all possible configurations: <a href="https://docs.google.com/spreadsheets/d/1HGrywkl71zMxOYboRAWGUzhQLU0IJ0pH7i5m4QqEcfA/edit#gid=1384548292">Copy of FLUX Node Profitability — Google Sheets</a></p><p>You are free to use whatever hardware and provider you like, however you may find some steps are different (especially the initial setup). When in doubt, always refer to the provider’s documentation</p><p>Alternative providers: <a href="https://docs.google.com/spreadsheets/d/1KJf9yI7RGl01ZgkWA8qVPQUwChEfe0JK2UGfubnq4Fw/edit#gid=0">FluxNodesRentingOptions — Google Sheets</a></p><p><em>Note: When you purchase your server, make sure to get it without an OS. We will be reinstalling over the top of any OS the server comes with anyways.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*umzd7-9vI0_kMBlqk3twOw.jpeg" /></figure><h3>3. One additional IP address</h3><p>You will require a 2nd public IP address from your provider. Hetzner offer additional IP addresses at $2 a month per extra address. This can be purchased after you have access to your server. This is required.</p><h3>Lets get started</h3><h3>Step 1 - Initial setup and OS install</h3><p>When you first get your server, you wont have an OS (instead your host machine will have a “<a href="https://docs.hetzner.com/robot/dedicated-server/troubleshooting/hetzner-rescue-system/">rescue-system</a>”). For our purposes, we will need to install Proxmox with RAID 0.</p><h3>Step 1.1 - Create an SSH connection to your server</h3><blockquote><em>For this process, you’ll need an SSH application. You can either use Windows CMD, or an SSH application such as </em><a href="https://www.putty.org/"><em>PuTTY</em></a><em>. The choice is yours. In this guide, I’ll be using Windows Terminal, which you can get from the Microsoft app store here: </em><a href="https://www.microsoft.com/en-gb/p/windows-terminal/9n0dx20hk701?activetab=pivot:overviewtab"><em>Get Windows Terminal — Microsoft Store en-GB</em></a></blockquote><p>Open your SSH application, and create a connection with the IP address supplied to you from Hetzner (this will be sent as an email). The username will be root, IP address that which is given in the email, and password will also be in the email</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TClKJ_FIyQZJJYEUw9iGcA.png" /></figure><h3>Step 1.2 - installimage</h3><p>Run the command installimage</p><p>A GUI will appear with a list of operating systems. For our purposes, we will be installing Proxmox</p><p>Use the arrow keys to traverse to Other (!!NO SUPPORT!!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*Hc21uNVUKeQ4nD3CRY4i6A.png" /></figure><p>Press enter and select Proxmox-Virtualization-Enviroment-on-Debian-Bullseye</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*7GTd4QSArK-KHmZ39j7k7A.png" /></figure><p>Don’t worry about the warnings about the image not being supported by Hetzner.</p><p>On the next screen, you’ll be presented a config file that you can edit to change parameters of the installation. Make the following changes:</p><ol><li>Change SWRAIDLEVELto 0</li><li>Under Partitions/Filesystems, after all the #’s, remove the line PART /home ext4 all</li><li>Change PART / ext4 2014Gto PART / ext4 all</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*kefgkBqKv0oCHxQ1hsnlww.png" /></figure><p>Once you are done, press F10 and select Yes</p><p>Ignore the following warnings, they are just telling you the drives will be wiped.</p><p>Let the installation run. This can take up to 10 minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*bKdJSFLXMwJZ5gaji6oEXw.png" /></figure><p>Once the installation is complete, enter the command rebootto restart the server and boot into Proxmox. The server can take 5 minutes or more to restart. You will not be able to establish an SSH connection during this time</p><p>To check Proxmox has installed correctly, re-establish an SSH connection with your server, using the same credentials. root@Proxmox~# should be shown in the terminal window.</p><p><em>Note: If you get an error warning you that Remote Host Identification has change, you’ll need to run the command </em>ssh-keygen -R &lt;host&gt;<em> in the command prompt, where </em>&lt;host&gt;<em> is the IP address of your server</em></p><p>To access your Proxmox web interface, go to <a href="https://your/">https://&lt;your</a>IP&gt;:8006 where &lt;yourIP&gt; is the public IP address you used to SSH to your server</p><h3>Step 2 - Proxmox network configuration</h3><p>Now we have Proxmox installed, we need to setup the network. We will create 2 interfaces within Proxmox and edit the /interfaces file</p><h3>Step 2.1 - Record your MAC address</h3><p>Create an SSH connection to your server, ensuring you are root within Proxmox</p><p>Run the command ip -o link and note down the MAC address of the network interface of your server. This will be the address that looks like XX:XX:XX:XX:XX:XX with numbers and letters, at the end of the of the line with an interface called something similar to “enp7s0”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ep2N0gg5XaB2_4wnKngUbg.png" /></figure><h3>Step 2.2 - Edit the interfaces file</h3><p><strong>Note: Be very careful in this step to ensure all addresses are correctly inputted. Any mistakes will cause your server to become unreachable over the internet. If this happens, you will need to contact Hetzner support to request a KVM connection, where you can either restart from Rescue, or try to fix your mistake in the interfaces file. You have been warned.</strong></p><p>Create an SSH connection to your server, ensuring you are root within Proxmox</p><p>Enter the command nano /etc/network/interfaces</p><p>This will open your interfaces file. Delete everything in this file and paste in the following:</p><pre>source /etc/network/interfaces.d/*</pre><pre>auto lo <br>iface lo inet loopback<br>  <br>iface &lt;NIC NAME (WILL BE SOMETHING LIKE &quot;enp7s0&quot;)&gt; inet manual  </pre><pre>auto vmbr0 <br>iface vmbr0 inet static   <br>address &lt;HOST IP/CIDR (THIS WILL BE PRESENT WHEN YOU FIRST OPEN THE FILE&gt;<br>gateway &lt;GATEWAY IP (PROVIDED BY HETZNER, MOUSE OVER YOUR SERVER&#39;S IP FOR INFO)&gt;  <br>bridge-ports &lt;NIC NAME&gt;  <br>bridge-stp off   <br>bridge-fd 1   <br>hwaddress &lt;MAC (PREVIOUSLY RECORDED)&gt;<br>pointopoint &lt;GATEWAY IP&gt;</pre><pre>auto vmbr100 <br>iface vmbr100 inet manual   <br>bridge-ports none   <br>bridge-stp off   <br>bridge-fd 0</pre><p>Change the values enclosed with &lt;&gt; to those of your server.</p><p>Once done, press <em>CTRL + X,</em> press <em>y</em>, then press <em>enter.</em></p><p>Now enter reboot to reboot your server</p><p>This is how my interfaces file looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*lG4NYVS2G_8n4pudEOpCPg.png" /></figure><p>Ensure that you can still access your server, both through SSH and your internet browser before proceeding</p><h3>Step 3 - Create the Virtual Router</h3><p>At this point, we are ready to create the Virtual Router. This VM will control all network traffic to and from your node VMs, and will act as the gateway for your node network. We will be using OPNsense, however feel free to use any other router software such as pfsense</p><p><em>Note: You can choose to download the file locally and then upload it to your server (steps 3.1.a and 3.2.a) or handle everything on the server (step 3.1.b) Whichever method you go for, feel free to skip the other method’s steps</em></p><h3>Step 3.1.a - Download the OPNsense Image (locally)</h3><p>This method will have you download the .iso file to your local device, and then upload to the server. This is easier, however the file is over 1GB and so if you have a slow internet connection, I recommend you skip to Step 3.1.b where we will do the same process straight from the server</p><p><strong>Skip to step 3.1.b if you wish to do this step on the server</strong></p><p>You will need to download the OPNsense image and upload it to your server first.</p><p>Navigate to the OPNsense downloads page here: <a href="https://opnsense.org/download/">Download — OPNsense® is a true open source firewall and more</a></p><p>Select amd64, dvd, and a location close to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7rJm_lmp3inV7rPEn2xv1g.png" /></figure><p>Download this file and extract the .iso file to a directory that is easy to navigate to (right click the .bz2 file and click extract files… then choose a path).</p><h3>Step 3.2.a - Upload the ISO file (locally)</h3><p>Now in your Proxmox server, navigate to the <em>ISO images</em> section by clicking on your storage (called <em>local</em>), and then <em>ISO images</em>. From here, click <em>upload</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCthbVI-9nyTa90D1iPnFw.png" /></figure><p>In the upload window, select your ISO file you just downloaded and click <em>upload</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*jpvvQuCVQ2LF7phYJXNbTg.png" /></figure><p>The upload may take sometime, depending on your network speeds. Wait until the upload is complete to proceed.</p><h3>Step 3.1.b- Download and upload the ISO file (on host)</h3><p><strong>Skip if you have completed steps 3.1.a and 3.2.b</strong></p><p>This process can be done entirely on your server, which is the way I suggest, however it is more technical.</p><p>Open an SSH window to your server, and type the command cd /var/lib/vz/template/iso</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*cZQyiKjavujlrzrU_yZEYg.png" /></figure><p>Now, go to step 3.1.a and follow it to the point where you are asked to click download. Instead of downloading this file, we are going to right click and copy link</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*vmShb8sTWO6WLgVmqNbYjQ.png" /></figure><p>Now type wget &lt;PasteYourLinkHere&gt; where you replace with your link (without the &lt;&gt;)</p><p>After a minute, the download should be complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yp3JpJ1w4Pif-UXl8DnrPQ.png" /></figure><p>As you can see, the file is now in the directory, however we need to decompress it.</p><p>Run the following commands</p><ol><li>sudo apt install bzip2 This may do nothing, that is ok</li><li>bzip2 -d &lt;filename.bz2&gt; Where &lt;filename.bz2&gt; is the name of the file you just downloaded. You can see that in the line above or by typing ls -a</li></ol><p>After you’ve ran the second command, nothing will appear to happen for a minute or two. Just wait until the text appears again on the left</p><p>To verify this has worked, type ls -a where you should see the .iso file without the .bz2 extension</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*1lpoPDDhSaqvzVIIjsRMsw.png" /></figure><h3>Step 3.3 - Configure the VM</h3><p>In the top right corner, click <em>Create VM</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uWCRiXOnQRZRmicOfZ0X1w.png" /></figure><p>Give the VM and ID of <em>999 </em>and a suitable name. Click Next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NrcOlCa4kiaVUDZxIjpDPg.png" /></figure><p>In OS, select the OPNsense ISO file we’ve just uploaded and click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHnHxSXUYfdU31dsFu97TQ.png" /></figure><p>Leave everything as default in the System tab</p><p>In the Disks tab, change the disk size to 8 (this is 8GB) and click next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ccmNQzrrgViQhjTtQCBo6A.png" /></figure><p>In the CPU tab, give the VM 2 sockets per core.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPJ2U5YIgFos2d8GLXYX0A.png" /></figure><p>In the Memory tab, change the Memory to 2048 and click next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36oCN8W8PBKKD7WbjEemnQ.png" /></figure><p>Now, if you’re using Hetzner, go to your additional IP address (if you haven’t ordered one yet, this is the time) and either click <em>request separate MAC</em> or, if you have already done this, mouse over your additional IP address and copy the MAC address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53ri5Vfk_CJmm_iGpyasQA.png" /></figure><p>Ensure that Bridge is set to vmbr0 and then paste your MAC address into the MAC address field. Click next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZncQ_h5rKjDwZAW8Ccfvhg.png" /></figure><p>Ensure everything is set correctly and click finish</p><h3>Step 3.4 - Add a second network card</h3><p>Now that you have created your VM, you will see it on the left with the ID and name you gave it. We must now add a second network card, which will be our vmbr100, which will connect the LAN that will hold our VMs in.</p><p>Click on your router VM, then click Hardware, then add, and select Network Device</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eY6TgCrKWVnxyeyT6p4Bg.png" /></figure><p>Set the Bridge to vmbr100 and click add</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*zW6I0xuqSkwNjYTzu7Bx_g.png" /></figure><p>You have successfully added your Virtual Router VM</p><h3>Step 4 - Configure OPNsense</h3><p>Now that we have the network setup, and a VM running OPNsense with the correct network interfaces, we now need to setup OPNsense to allow us to run multiple nodes in the same LAN</p><h3>Step 4.1 - OPNsense installer</h3><p>In Proxmox, click on your router VM and press start in the top right corner.</p><p>Now go to the Console tab of your VM, and wait until the text appears on screen</p><p>After the boot has finished, you will be prompted to login. Type installer and press enter</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kl9pvqiBUnufOC5C0_Iydw.png" /></figure><p>For the password, type opnsense</p><p>In the next screen, select the keyboard layout you wish to use</p><p>On the next screen, leave the setting on default (GPT/UEFI Hybrid) and press enter</p><p>In UFS Configuration, select da0, which should have 8GB of space. Press enter</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rLnqnSHG9Xs0oppAnVYTxg.png" /></figure><p>Select yes to confirm the warning on the next page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YH9sqDDVeroTb14VxLBe5g.png" /></figure><p>Once the installation is complete, you can choose to change the root password and then select Complete install.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YH9sqDDVeroTb14VxLBe5g.png" /></figure><p>The machine will now reboot</p><h3>Step 4.2 - OPNsense WAN interface</h3><p>Boot the VM, and open the Console tab to access the VM.</p><p>If you have left the credentials as default, login with the username root and password opnsense</p><p>For now, WAN need to be assigned to vtnet0, and LAN needs to be unassigned (we will set the LAN later)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Q2NNMi9iSlxerDFjQ35Tg.png" /></figure><p>Select option 1.</p><p>We do not wish to configure LAGGs or VLANs, so press N and enter for both</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xh5gn7zFJCBwsX1UG3Klpg.png" /></figure><p>For our WAN interface, enter vtnet0</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z1cgbyVNJ3NxGSb7PmUXzA.png" /></figure><p>For our LAN interface, skip by pressing enter</p><p>Skip the optional interface by pressing enter again.</p><p>If the assignment looks correct, enter y</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-teriTAlaFXLkZyI4CRxg.png" /></figure><p>The router will now configure the interfaces. Once this has finished, ensure your interfaces are now correct</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86mGpwi24nVQ1864MPkXYg.png" /></figure><p>We will be assigning the LAN later</p><h3>Step 4.3 - Ports</h3><p>To access the web gui interface of your OPNsense router, type <a href="https://youripaddress/">https://youripaddress</a> where your ip address is that of the router (found in the previous step as the WAN IP address</p><p>Login with your credentials (root and opnsense by default)</p><p>Once logged in, click on Firewall, NAT, Port Forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dx-jjwj3_EYsIBJddn3UTA.png" /></figure><p>On the right, click add another record.</p><p>In this form, change the following fields:</p><ol><li>Destination = WAN address</li><li>Destination port range = from (other) 80 to (other) 443</li><li>Redirect target IP = 192.168.1.1</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nf7TWnAf7U6ODBScGuEhDw.png" /></figure><p>Click save and then apply changes on the next page.</p><p>Your port forwarding tables should now look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcsiKZ-JP4pOH6JSI3OxhA.png" /></figure><h3>Step 4.4 - Enable SSH (OPTIONAL)</h3><p>You can add a third rule to forward SSH connections (port 22) in the same way as we did in the previous step. This will allow you to SSH into your router, which you can then SSH hop to your nodes.</p><p>Configure a third rule like you see below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Euo-OFqeEWbUY_PDm52FBg.png" /></figure><p>Next, navigate to administration, which is located in the settings tab of System, and do the following changes:</p><ol><li>Enable Secure Shell</li><li>Permit root user login</li><li>Permit password login</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4JY5Q3a0Gfh2oOG4OWW2g.png" /></figure><p>Click save</p><p>You can now access your router over an SSH connection. To test this, open an SSH window, now using your router’s IP address and login credentials.</p><p>To access the shell, select option 8</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0UlsIFrf3g8Z9Tlyqi_ug.png" /></figure><h3>Step 4.5 - LAN interface</h3><p>You can now hop back over to your console in Promox for your router</p><p>Once logged in, run option 1 again</p><p>Like before, say no to both LAGG and VLAN</p><p>Set WAN to vtnet0 like before</p><p>Set LAN to vtnet1</p><p>Again skip the optional interface</p><p>Ensure your interfaces are correct and then allow the configuration to proceed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*GUKP7ncGPvHqHkSnGufzPw.png" /></figure><p>Your LAN and WAN interfaces should now be setup correctly</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cp7KCgz9vFGzyM_3G5Id1w.png" /></figure><p>Reboot the router</p><h3>Step 4.6 - Enable UPnP on the router</h3><p>The next step is to setup UPnP. This will allow us to host multiple nodes (up to 8) on a single Public IP address</p><p>In the OPNsense web gui, navigate to the status section in firmware and click <em>check for updates</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ey1n5gfsYp_qQmEJchJLBQ.png" /></figure><p>After a couple seconds, a pop-up will appear. Close this pop-up and then, at the bottom of the screen, click <em>update</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3GHQgZGZv23paZa5RuR6ww.png" /></figure><p>Click ok to the firewall pop-up</p><p>Wait for the updates to complete and device to reboot</p><p>Once the router has rebooted, under Plugins, search for upnp and click install</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQC3FmX5llIrC0vSJP5fLA.png" /></figure><p>Let the install complete and then refresh your browser page.</p><p>Next, navigate to Universal Plug and Play settings, under Services and make the following changes:</p><p><strong><em>Note: For number 8, you cannot copy and paste Entry 1 as the “-” used by the router is a different character from the “-” used in medium’s blog</em></strong></p><ol><li>Enable = ticked</li><li>Allow UPnP Port Mapping = ticked</li><li>Allow NAT-PMP Port Mapping = ticked</li><li>External interface = WAN</li><li>Interfaces (generally LAN) = LAN</li><li>Log NAT-PMP = ticked</li><li>Use system time = ticked</li><li>Entry 1 = allow 1–65000 192.168.1.1/24 1–65000</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p1-cht_qe2gIqZ3dVWBdhQ.png" /></figure><p>Ensure you’ve configured everything correctly and click save</p><h3>Step 4.7 - Disable DHCP</h3><p>Although this step is not entirely necessary, it will make things massively easier later on</p><p>Navigate to [LAN] in DHCPv4, within services</p><p>Ensure the setting Enable is not ticked</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WunUYZzm5wYkaFsQMxQ-ww.png" /></figure><p>Click save at the bottom of the page</p><h3>Step 5 - Create VMs for your nodes</h3><p>At this stage, you are ready to start creating VMs that will host your nodes. Each node needs its own VM, and depending on the node tier you wish the VM to run will change what hardware configurations the VM will need</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lbHJ3JGa3MNXTNv1.png" /></figure><p>For purposes of this guide, I will be setting up cumulus nodes.</p><h3>Step 5.1 - Download and install Ubuntu 20.04</h3><p>Much like what we had to do for OPNsense, we need to download and upload the Ubuntu .iso to our server to give to our VMs. This can be done much more simply than in previous steps, however feel free to complete this step however you see fit</p><p>Navigate to Ubuntu’s download page here: <a href="https://ubuntu.com/download/server">Get Ubuntu Server | Download | Ubuntu</a></p><p>Click Download Ubuntu Server</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*M4-JtTzUVfa1QxbG49Leng.png" /></figure><p>This will start a download and take you to another page. You can cancel this download and instead right click and copy link</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B8LuPCx69WTOR0W5GRlLaQ.png" /></figure><p>Now in Proxmox, navigate to ISO Images, which is in your local storage, and click download from URL</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yc8Ou6GS_YjMNUqd1HdZaA.png" /></figure><p>Paste your link and click Query URL. This should automatically pull the .iso file we need. Now click download</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*AB6fionLpM-lEZqfqmo-qw.png" /></figure><p>After the download is complete, we have the image we need to install Ubuntu onto our VMs</p><h3>Step 5.2 - Create the first VM</h3><p>Click create VM and go through the tabs, configuring the VM like you did for the Router, but instead using the hardware requirements for your node of choice</p><p><em>Note: It is better to have some overhead in your hardware. I suggest you give each VM 20GB extra than is required, and feel free to give a little extra RAM if you can spare it.</em></p><p>For OS, select our Ubuntu ISO image we just downloaded</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0VTRNEuMM1GRei1y4hlYg.png" /></figure><p>Leave System as default</p><p>Disks will depend on your node tier. For my, I wish to setup a Cumulus node, and so will give the VM 240GB (220GB minimum + 20GB overhead)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hr7sFosL-YuKwHTRG-4gbw.png" /></figure><p>In CPU, give your VM their required cores and threads. For a Cumulus, this would be 2 cores with 2 threads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qumuxMlFwgtF-ouhZICmow.png" /></figure><p>For RAM, give your server the required RAM for the tier. For a Cumulus, this would be 8GB (which is 8192MiB)</p><p><em>Note: 1GB = 1024MiB</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUdv5LIxhAUPoYhq4auNHA.png" /></figure><p>In Network, ensure to set all your VMs to Bridge vmbr100</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ve83QYNSn0YWYdHbU579zw.png" /></figure><p>Click next then Finish.</p><h3>Step 5.3 - Install Ubuntu OS</h3><p>Navigate to the console tab of your newly created VM and start the machine</p><p>After initialization, you will be presented with a list of languages. If this is not the case, you have done something wrong.</p><p>Select your preferred language and press enter</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7OqWXoZ0jt1lcORVeEc5g.png" /></figure><p>On the next page, select your preferred keyboard layout and select done</p><p>For IPv4, Select edit, then manual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3nMYBozM5j7KC3lAMoaLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*mrmQfzVJ5LsNotlh0hvJSA.png" /></figure><p>Now you will need to configure the IP addressing of your VM. Set each setting to the following:</p><ol><li>Subnet = 192.168.1.0/24</li><li>Address = 192.168.1.X where X is between 2 to 254 inclusive, and unique to this VM</li><li>Gateway = 192.168.1.1</li><li>Name Servers = 8.8.8.8</li><li>Search Domains = 8.8.4.4</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*OykZSeRBVRSl2WY_.png" /></figure><p>Select Save</p><p>Skip past proxy configuration</p><p>Skip past Ubuntu Mirror Archive</p><p>In guided storage configuration, ensure Use entire disk is selected, and the disk shown has the size you gave your VM. Ensure also that Set up this disk as an LVM group is ticked</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*R7zqgVYMUbo-wTkkm-D5mg.png" /></figure><p>On the next page, a few changes need to be made</p><p>At the top of the page, select the “<em>/</em> “ mount point (it will have a size of 100GB) and select <em>Unmount</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*LTHDovDZOTQGW4tqngm_wQ.png" /></figure><p>Next, select <em>Ubuntu-lv</em> under devices (it will have a size of 100GB), and select <em>Edit</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4XyFNaFc6q5is4HboOc3mg.png" /></figure><p>Within the edit window, increase the <em>size </em>to the max value (you can just make this number huge and Ubuntu will reduce it to the max size)</p><p>Then set the mount to “<em>/ </em>”. Click Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*M9gBmWwEzklrndyCwyccrQ.png" /></figure><p>Ensure that the “/ “ directory has enough Size to meet the system requirements of your node. Then click Done</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dD4HDauw_io0YPC06FQidA.png" /></figure><p>Select continue on the confirmation pop-up</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*QqhMIh0rBIxyKjpV47AWew.png" /></figure><p>Now edit the fields on the next page. These can be whatever you want, but make sure to remember your username and password</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Id8UrUV1cSGhjE951Xg2XA.png" /></figure><p>Skip the Ubuntu advantage token page</p><p>OPTIONAL - If you wish to be able to SSH into your VM (HIGHLY RECOMMENDED), select Instal OpenSSH Server</p><p><em>Note: You’ll have needed to follow the previous optional steps for SSH in order for SSH to work correctly</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDoW2DaZdseYuahMPsy04A.png" /></figure><p>On the next page, press tab to skip the list of options and select done</p><p>Now allow the VM to install Ubuntu. The installation may take up to 10 minutes. Once it has finished, you will be prompted to reboot the machine.</p><p>Once you select reboot, a list of errors will appear. This is normal. Press enter to continue</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*EQUnblXpi2pZm2mLeKwonw.png" /></figure><p>Once your VM has rebooted, use the previously set credentials to login to the machine.</p><h3>Step 5.4 - Update and Upgrade Ubuntu</h3><p>Now that Ubuntu is installed onto your VM, you’ll need to update the OS and any files.</p><p>Run the command sudo apt update &amp;&amp; sudo apt dist-upgrade</p><p>You’ll be prompted for your user password, enter it and let the command roll</p><p>Once the VM has pulled all the updates, it will ask if you wish to continue. Enter Y</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*_KL3JnNBdG0YwCTWwlvddw.png" /></figure><p>Once the updates are finished, enter the command sudo reboot to reboot your VM</p><p><strong><em>A note on SSH: If you wish to SSH into your nodes, you’ll need to first establish an SSH connection with your router, press option 8, then SSH into your nodes from here. You cannot access the nodes without accessing the router.</em></strong></p><p><strong><em>The syntax for an SSH connection in CLI is </em></strong><strong><em>SSH username@address</em></strong></p><p><strong><em>The username will be whatever you set when installing the OS (or </em></strong><strong><em>root for root access)</em></strong></p><p><strong><em>For example:</em></strong></p><p>SSH to Router</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKE_9yhAglj3s5RtD9r9pQ.png" /></figure><p>SSH to Node</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*48fr8q8TkL3cyV9_5dO75g.png" /></figure><p>To leave the node and go back to the router, type exit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*ekeCqjjwNG7LoHaomOFF4A.png" /></figure><h3>Step 6 - Install Flux</h3><p>At this point, you are ready to install flux onto your node. You should follow this awesome guide by Ali Malik on how to install flux: <a href="https://medium.com/@mmalik4/flux-light-node-setup-as-easy-as-it-gets-833f17c73dbb">Flux Light Node Setup — As easy as it gets !! | by Ali Malik | Medium</a></p><p><em>Note: Ensure you are connected to the VM you intend to install Flux onto. For now, just setup 1 machine from start to finish. We can create clones of this VM in the future</em></p><p>Be sure to complete all the steps of this guide, and then return to this guide at the end of that guide to configure UPnP on your flux nodes</p><p><em>Helpful tip: If you need to change from your user account to root, use the command </em>sudo su -</p><p><strong>Give zelcore your router’s public IP address for the node’s IP</strong></p><p><strong>You will fail benchmarks until you enable UPnP</strong></p><h3>Step 7 - UPnP and Flux</h3><p>At this stage, you will have just completed the flux node install, and are ready to enable UPnP on your node</p><h3>Step 7.1 - Run option 14</h3><p>In the multitoolbox, run option 14</p><p>After a few seconds, a pop window will appear. Select Enable UPnP Mode</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*SI2WxXkAk89kpHjp0CyRMA.png" /></figure><p>Now you will need to select a port to use. Each node will need to run a different port.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lyunc60FHENUFRexALmWkA.png" /></figure><p>If you configured everything correctly, flux should auto detect your router address as 192.168.1.1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01TAYCdbKa9NiTIwUeysVQ.png" /></figure><p>Select Yes and allow UPnP to install</p><p>Congratulations. You are done. This node will now run on flux.</p><h3>Step 8 - Create clone-able VMs (OPTIONAL)</h3><p>At this stage, your first node is now fully operational. This final optional step will allow you to create a template of your VM, so that you may create multiple nodes quickly and have the ability to scale</p><p><em>Note: This process will destroy your initial VM. This is fine, as we will create a clone of the template, which will be virtually identical to the VM before it was made into a template</em></p><p><em>Note 2: You cannot create a template out of a cumulus node, and then try to change the hardware and deploy a Nimbus node. You must configure the VM with the tier in mind, set it up, and then create a template from it. If you wish to have a template of all 3 tiers, you must initially setup 3 separately speced VMs</em></p><h3>Step 8.1 - Create a template</h3><p>In Proxmox, right click your running VM and click Shutdown</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*md1itNeCTnQ_5-0urP-37Q.png" /></figure><p>Your node will now shutdown. Next, right click and click Convert to template</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*cG4ICXpbMXz_e_hRbmDaPg.png" /></figure><p>This will irrevocably covert your VM into a template.</p><h3>Step 8.2 - Clone your Node</h3><p>To create a VM from this template, right click and click clone</p><p>Change mode to Full clone and give the VM a suitable name. Click Clone</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*TNWBx-KE2fKVGnr32NIrEg.png" /></figure><p>Your cloned machine will now appear in the list powered off. Power on the machine and either connect through the console, or establish an SSH connection to the VM (you can find the IP address of your cloned device by first logging into it from the Proxmox web Console)</p><h3>Step 8.3 - Change IP address</h3><p>Each VM needs a unique IP address. To change the IP address of your VM, enter the following command:</p><p>sudo nano /etc/netplan/00-installer-config.yaml</p><p>This will open a file, much like the /interfaces file we edited earlier. Here, it should already be pre-populated with information. All we are going to change, is the addresses from 192.168.1.100 to something else</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QyqMauc26ZAZ4KyfIdlWA.png" /></figure><p>Once you have changed the IP address, hit CTRL + X, y, then enter</p><p>Now type sudo netplan apply</p><p><em>Note: If you are connected to your machines via SSH, your SSH connection will now become unresponsive until it times out. This is because the target IP address of your machine has changed</em></p><h3>Step 8.4 - Change Flux Config</h3><p>As your node is a clone of a machine that already has Flux fully installed, there is no need to re-install flux. Periodically, you may wish to refresh your templates as flux updates</p><p>Open the Flux Multitoolbox and select option 8</p><blockquote>bash -i &lt;(curl -s <a href="https://raw.githubusercontent.com/RunOnFlux/fluxnode-multitool/master/multitoolbox.sh">https://raw.githubusercontent.com/RunOnFlux/fluxnode-multitool/master/multitoolbox.sh</a>)</blockquote><p>Here, you will amend your node’s details for the node you are trying to setup in zelcore</p><p>After this has ran, re-call the toolbox and run option 14</p><p>Enable UPnP mode</p><p>It is essential we choose a port that is not currently in use by any other of your nodes. I will select 16127 for this particular machine</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfVkHjJFSU4i_Iueda0ZDQ.png" /></figure><p>Make sure your router’s IP address is 192.168.1.1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgFvEbWbVjjAFV81T0AyRQ.png" /></figure><p>Let this finish running, and then call the multibox a final time.</p><p>Now call option 4. We are reinstalling watchdog to ensure it is properly functioning, and to have this new node give notifications for itself.</p><p>Configure Watchdog however you wish</p><h3>Conclusion</h3><p>Congratulations for making it this far, you’ve completed the installation.</p><p>Learn more about flux at <a href="https://runonflux.io/">Flux — Decentralized Cloud Infrastructure (runonflux.io)</a></p><p>If you are having any issues, feel free to hop into the Flux Offical discord and post a question in the support channel <a href="https://discord.io/runonflux">https://discord.io/runonflux</a></p><p>Or ping me directly on Discord @Goldie ¯\_(ツ)_/¯#0001</p><p><em>Note: This guide is not official or from the Flux team, I am just a community member who wants to help :)</em></p><h3>This guide took a long time to write. If you found it helpful, please consider chucking me a flux or 2 ❤️</h3><h3><strong>t1fj6hgzxSEJEqwgWCyF8TJ57zRwffEneGF</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OIbc_q-K3VKKxKRg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cd8887fe268" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>