Update 3rd October, 2024

This week we kicked off phase two of the Beta Rewards program. This one is open to everyone who wants to start up a node or two. Or in some cases 2,000. We currently have more than 137,000 nodes operational — these records are falling like ninepins. :bowling:

Some avid tinkerers will have noticed that although the nominal node size for this experiment is 32GB (plus 3GB for logs) they can start up multiple nodes on a small disk. Should node operators do this, as things start to get crowded in terms of resources, we would expect to see nodes being shunned. How that pans out in terms of earnings will be interesting to see. And while we would encourage participants to allocate the full 32GB space they are committed to, we are ramping up data uploads and carefully measuring drop off as we do.

Hopefully most of you who have tried have been able to get nodes connecting now. Most should have a few hundred chunks per node in the record store and possibly have earned a few nanos. If not, try the different connection methods available via the Launchpad (Options | Change Mode). The most foolproof method is custom ports, so long as you’re happy with port forwarding on your router.

Speaking of the Launchpad, there’s a new version (v0.3.18) ready for your downloading pleasure.

On top of a bunch of tweaks, UX improvements, and one or two fixes, the Launchpad will now show you more useful stats and metrics for each node, along with the nanos each have earned. Very handy!

The current experiment will run until Tuesday, when we will be launching another combination of node and chunk size TBD.

General progress

The team has been focused on migrating to the autonomi library, including building a new CLI to operate with this codebase. We’re also continuing with the EVM integration, moving forwards with integrating Wasm into the APIs, as well as stripping out legacy code.

@chriso is mostly engaged with making sure the test releases are running smoothly for our node/chunk size experiments, ably assisted by @shu who ran a capacity and growth analysis for the number of uploaders vs network size.

@qi_ma has been looking at the distribution of payments and running tests on the EVM integration.

@roland raised a PR to add a metric that tells node operators if the node has recently been marked as bad and is likely to be shunned. He also worked on EVM testing with Qi.

Meanwhile, @bzee stripped out the old auditor and faucet code from the codebase, and tested local EVM payments and the APIs involved in readiness for building the vault API with the Scratchpad data type.

@rusty.spork has been mostly fielding questions about node sizing and other Beta issues.

@anselme has been working on the new CLI which plugs into the new autonomi crate, replacing the sn_node interface. Once complete, this will have much the same functionality as the existing CLI for put, get, transfers, interrogating the wallet, etc.

@mick.vandijke demonstrated successful EVM payments to the team. He also made some updates to the features of autonomi, updated the readme with usage instructions and looked into failing tests for autonomi when running with the registers, vault and file features. And he fixed a bug where the Launchpad was showing zero nanos on restart.

Ermine is making progress with Wasm including getting the test client running on the browser with test results output to the console for debugging. He’s currently working through library choices and syntax errors.

@mazzi continues to refine the Launchpad, creating a new popup that warns the users that the nodes will be reset when changing the connection mode. He also got the Discord bot up-to-date for the new Beta testing program.

Finally, @joshuef has been debugging the EVM tests and improving payment simulations.

52 Likes

Am I first?!

First? Let’s see.

25 Likes

View and publish websites on Autonomi

Available until the next reset:

Note: once the ‘safecoin’ token has been removed awe will no longer work so have a go while you can.

33 Likes

Thanks so much to the entire Autonomi team for all of your hard work! :sweat_drops:

Good luck to everyone with your Beta Rewards! :four_leaf_clover:

17 Likes

Thanks for the update.

As ever thanks to all involved in this, whether you got a mention or not :slight_smile:

Avanti !!!

12 Likes

I feel my future decentralized, autonomous, self-healing private data stored forever for my Ai dApps and great grandchildren will be here before I know it; so excited!

My intergalactic guides and future selves (They use the SAFE and blockchain for time travel) tell me Autonomi development is on a proper course and they want to thank every single contributor for building a feature to our HUman legacy that will stand the ultimate test of tiME.

Let’s all finish building this gift to the world with grace and beauty.

13 Likes

Thx 4 the update Maidsafe devs

:clap: :clap: :clap:

Really love the node size increase and experimentation :kissing_heart:

keep coding/hacking/testing supants

10 Likes

161,000 nodes now!

16 Likes

Jim, any chance of providing a faucet - we can help with the uploads, at the current size it’s going to be hard to achieve in the 1 week - or we can provide a wallet address, and you can send a few tokens to that, to ensure there’s no faucet wrangling :eyes:

9 Likes

Thanks for the update and for the hard work for the team, an hour ago Jim announced that the network had reached 155,000 nodes :clap: :clap: :clap:

I don’t know if this bug has been eliminated in Windows, with me it looks like this:

  • after about 1.5 days my 5 nodes earned 2 nanos and the same amount was indicated by the Discord bot.

  • I then wanted to add 2 nodes but the commands in Launchpad were unresponsive so I reset the nodes and re-added 7 nodes, after the reset Launchpad indicated 0 nanos but the Discord bot still indicated 2 nanos.

Should this be the case now that this bug has been fixed?

Another error seems to be the current indication of the bot on Discord:

  • After running these 7 nodes, Launchpad showed 4 Nanos of income this morning, and together with the 2 Nanos earned earlier, the Discord bot should show 6 Nanos,

-Meanwhile, it shows only 4 nanos of earnings:

obraz

5 Likes

The disco bot is “total” Nanos earned during the current test period - Tuesday → Tuesday (with a variable delay of mins to days :eyes: for it to update the nanos earned by the nodes )

The launchpad shows the current Nanos earned since the nodes were reset, it has no visibility of what was earned before the reset.

hope that helps

6 Likes

I understand that the bot works with a delay but this is its own disagreement, because if after the reset of the Discord nodes the bot was still showing 2 nanos (Launchpad reset to 0 and Discord bot did not reset earnings). this means that now after earning another 4 nanos it should be showing 6, right?
(In the morning the bot was even showing only 3 nanos and recently updated to 4).

In that case, what does this information mean?

2 Likes

If te launchpad is umnresponsive, just try quitting it and reopening, before resetting your nodes.

The Launchpad is just the UI for the nodes, nodes are services that run in the background.

5 Likes

Thanks, I understand. And can you explain how the Discord bot works? After resetting the nodes, the bot was still showing 2 nanos earned earlier i.e. the bot didn’t reset them, and now after restarting the nodes and earning another 4 nanos the bot doesn’t add the previous
earnings and shows 4 instead of 6.

How does the total nano count work?

1 Like

If you have your discord username in the launchpad, as soon as your node earns a nano, it sends it back to maidsafe, and it gets counted by the bot.

The launchpad counts it as well, but when you reset the nodes, the launchpad’s counter resets as well… but your nanos are with maidsafe, and counted on the leaderboard.

The caveat here is that the bot can take several hours to report new nano’s it’s received back (especially with a big network) so there can be a reporting lag there.

3 Likes

The j and i the other way around anti-dutchies
@mick.vandijke

3 Likes

Forgive me :rofl:

1 Like

Consider Mick redutchified.

3 Likes