Flux — The Web3 Cloud
Flux’s core values and ethos center around the rise of Web 3.0 — By, and For the People. Its aim is to evoke the power of corporations and restore it to the common people. The Flux Cloud is decentralized, based on thousands of single servers from all over the world that are all connected in one operating system. Individuals are the backbone of the technology, so to speak. They provide the cloud with computational resources via home-based bare metal machines or rented servers and are incentivized by 50% of the total block reward.
To this date, the decentralized cloud of Flux is supported by over 14,000 nodes around the globe. Its total available computational resources amount to around 110,000 Cores, 300 TB of RAM, and over 7 PT (Petabytes) of SSD. It is a Web 3.0 cloud powerhouse that can be used to deploy applications in a decentralized and censor-resistant manner. There are plenty of advantages of using Flux instead of traditional Web2 infrastructure providers:
- All applications are redundant and have automatic failovers in case of any outages.
- The Flux Cloud is agnostic to code language as it uses Docker Hub containers as an on-ramp.
- The Flux Cloud automatically keeps applications up to date with the respective container.
- The Flux Cloud offers competitive pricing.
Fuse — A digital Economy
Fuse is an enterprise-grade, use-case agnostic, reliable, and secure decentralized EVM-compatible public blockchain. Gas fees average around $0.001, while transaction speeds are below 5 seconds.
It is designed for entrepreneurs and organizations that want to experiment, launch and scale Web3 apps. Anyone can build on the Fuse Blockchain and leverage enterprise-ready, decentralized tech — be it existing crypto projects, start-ups, or blue-chip companies.
The Fuse SDK lets companies plug Web3 services and crypto payments into their existing mobile products with business-ready smart contract wallets, eliminating the complexities of Web3. The network’s utility token is the Fuse Token (FUSE) — an ERC-20 token. It can be used as a medium of exchange, as payment to the Fuse Network to approve transactions, or to participate in the network’s staking mechanism.
Over 100 decentralized service providers power the Fuse ecosystem, from token bridges and DEXs to NFT marketplaces, fiat on-ramps, and DID identifiers. This gives project teams and startups all the tooling required to build and scale dApps on an EVM-compatible blockchain.
Enough introduction! Let us go ahead with the guide on how to deploy your very own Fuse RPC Node via the Flux Marketplace in very few steps!
- We first need to head over to https://home.runonflux.io/
- Once here, we need to login using our ZelID. Available for us via Zelcore https://zelcore.io/ (Remember to use always the official links)
- If you do not have an account created in Zelcore, you firstly need to download and install the app
- Next (mandatory for your wallet’s safety), enable d2FA on the App section inside Zelcore.
- Now you can authenticate by clicking on the fingerprint button or manually by signing the message manually on your Zelcore Wallet with the ZelID App
- Now that you have been authenticated, head over to https://home.runonflux.io/apps/registerapp and look for the FuseRPC Application — You will find it under the ‘RPC Node’ category. You will see something remarkably like this:
- Click on “Start Launching Marketplace App.”, you get something like:
- You can click “Next” or copy the Registration Message if you want to sign the message manually using your ZelID App, and then click “Next.”
- Here, you can click the fingerprint button to sign the request for the application. If you have done this manually, paste the signed message from the earlier step onto your ZelID.
- You will now see the monthly cost for your application. Click on “Register Flux App.”
- You will be given payment information in FLUX. Payment is made through the FLUX blockchain using FLUX coins.
- Select “Pay with Zelcore” to make the payment for the application.
- You’re done! We now need to wait for your Fuse RPC Node to be spawned on an available node, which usually takes around 10–30 minutes
Usage of the Fuse RPC Node
- When you’re logged in with your ZelID at https://home.runonflux.io, go to the “Global Apps” menu tab on the left-hand side. From there, go to the “My Apps” tab, where you can manage and visit your Fuse RPC Node deployments. Click on the arrow pointing down to see your application specifications and the IPs running it.
- More importantly, you see your “Automatic Domains” which were generated by the Flux-Domain-Manager (FDM). You’ll need the first one listed there, in our case fuserpc1678359486247.app.runonflux.io. This https endpoint is load balancing between your three Fuse RPC Nodes (If they are synced 100%)
→ https://fuserpc1678359486247.app.runonflux.io
- As you can see, your Fuse RPC Node is redundant, which means it is always running on a minimum of three instances simultaneously. That means you could use each individual IP as a RPC endpoint as well. Click on “Visit App” to get to its http endpoint. Examples:
→ http://202.61.206.54:38545/
→ http://65.108.226.248:38545/
- You can check the logs of the individual IPs to ensure that the Node is syncing properly.
- Visit one IP by clicking on “Visit FluxNode”
- Log in with your ZelID
- Navigate to “Apps”, “Local Apps”, “My Local Apps”
- Click “Manage”, “Manage App”, “Log File”
- You should see something similar like this (The RPC Node is syncing):
[Peer|eth66|22161432|168.119.255.108:30303], with AuRa step 335675902
H2023–03–09 16:31:50.2115|Peers | with known best block: 14 | all: 14 |
.2023–03–09 16:31:50.2115|Syncing state nodes
J2023–03–09 16:31:50.2115|Sync peers — Initialized: 14 | All: 14 | Max: 50
===[Active][Sleep ][Peer (ProtocolVersion/Head/Host:Port) ][Transfer Speeds (L/H/B/R/N/S) ][Client Info (Name/Version/Operating System/Language) ]
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
[ N ][ ][Peer|eth66|22161432| 74.118.143.170:30303][ 13| 53| | | 627| ][Nethermind/v1.14.7+c3233f25/linux-x64/dotnet6.0.14]
[ N ][ ][Peer|eth66|22161432| 141.95.126.215:30305][ 15| 107| 190| 430| 825| ][Nethermind/v1.14.3–49-bd6037fa9–20230130/X64-Linux/6.0.11]
[ N ][ ][Peer|eth66|22161432|135.181.158.232:30303][ 34| 198| 109| 170| 104| ][OpenEthereum/v3.3.5-stable/x86_64-linux-musl/rustc1.59.0]
[ N ][ ][Peer|eth66|22161432| 167.99.141.69:30303][ 6| 144| 150| 523| 305| ][OpenEthereum/v3.3.5-stable/x86_64-linux-musl/rustc1.59.0]
[ N ][ ][Peer|eth66|22161432|168.119.152.181:30303][ 5| 244| 199| 817| 283| ][OpenEthereum/v3.3.5-stable/x86_64-linux-musl/rustc1.59.0]
[ N ][ ][Peer|eth66|22161432|168.119.255.108:30303][ 5| 170| 120| 502| 223| ][Nethermind/v1.14.7+e76e5b45/linux-x64/dotnet6.0.13]
[ N ][ ][Peer|eth66|22161431| 3.77.55.22:30303][ 263| 120| | | 123| ][Nethermind/v1.14.7+c3233f25/linux-x64/dotnet6.0.14]
[ N ][ ][Peer|eth66|22161431| 3.121.55.130:30303][ 632| 148| 171| 114| 41| ][Nethermind/v1.14.7+c3233f25/linux-x64/dotnet6.0.13]
[ N ][ ][Peer|eth66|22161431| 3.125.148.125:30303][ 408| 99| 205| 358| 47| ][OpenEthereum/v3.3.5-stable/x86_64-linux-musl/rustc1.59.0]
2023–03–09 16:31:50.3452|Changing state StateNodes to FastSync, StateNodes at processed:0|state:0|block:0|header:22161399|chain difficulty:131072|target block:22161432|peer block:22161432|peer total difficulty:7541144535317427134228060853125825857586058730
T2023–03–09 16:31:50.3452|Sync mode changed from StateNodes to FastSync, StateNodes
2023–03–09 16:31:51.1360|State Sync 00.00:46:50 | 3173.55MB | branches: 58.98 % | kB/s: 644 | accounts 725391 | nodes 46635918 | diagnostics: 10.14.28ms
c2023–03–09 16:31:51.2340|Downloaded 22161400 / 22161432 | current 0.24bps | total 204.11bps
2023–03–09 16:31:51.5045|Changing state FastSync, StateNodes to StateNodes at processed:0|state:0|block:0|header:22161400|chain difficulty:131072|target block:22161432|peer block:22161432|peer total difficulty:7541144535317427134228060853125825857586058730
T2023–03–09 16:31:51.5045|Sync mode changed from FastSync, StateNodes to StateNodes
2023–03–09 16:31:52.1400|State Sync 00.00:46:51 | 3174.07MB | branches: 58.98 % | kB/s: 526 | accounts 725391 | nodes 46643743 | diagnostics: 5.14.28ms
2023–03–09 16:31:53.1582|State Sync 00.00:46:52 | 3174.85MB | branches: 58.98 % | kB/s: 764 | accounts 725391 | nodes 46655438 | diagnostics: 2.14.28ms
- Remember, your Fuse RPC Node is only subscribed for 22,000 Flux blocks initially, which is ~ 44,000 minutes (about 1 month). You will need to renew payment after the first month, so your Node does not get kicked off the network. We give you the choice to renew it for a longer terms after the first deployment for up to one whole year.
- Visit https://home.runonflux.io/ and log in with your ZelID
- Navigate to “Apps”, “Global Apps”, “My Apps”
- Click “Manage”, “Manage App”, “Update Specifications”
- Leave all the variables like they are, except the PERIOD field — Adjust it to your preference. Next click on “Compute Update Message”
- Sign the Message with the ZelID App and click “Update Flux App” after
- Click “Pay with Zelcore” to make the Flux Payment
- Voilà your Node has been renewed for your chosen duration
Have Fun supporting the Fuse Blockchain with decentralized infrastructure!
Learn more about Flux at www.runonflux.io
Learn more about Fuse at https://www.fuse.io/