Pre-Dev-Update Thread! Yay! :D

Apparently this recognition was a bit too much for @Anselme 's petty and jealous workmates, and they are now trying to take away his achievement by reverting his PR

Well, you are welcome to try, but what once happened, cannot unhappen! And the PR numbers will only increase, no matter what you try!

(Although I must admit I doubted the original PR to begin with, as it was only four lines… Maybe it was done only to achieve the matching a current year event, without any real significance for the project… But a PR is a PR and if no one else seized the opportunity, it’s only their own fault.)

2 Likes

And another new release…

8 Likes

Rolling in like hot cakes :revolving_hearts:

7 Likes

And another new release…

This all bodes well for tomorrow :wink:

Will safe update work again? Can we do safe node install?

Edit: no and no :frowning:

but does it really matter?

8 Likes

And theres another release :slight_smile:

10 Likes

And the releases keep coming…

Dunno how many of the issues uncovered by last nights testnet have been addressed in this - but its extremely fast work in any case - well done and I look forward to poking at this either locally or in a testnet

8 Likes

Been seeing various things going on with chunk size testing. I may have missed it in an update but anybody know what’s up with that?

5 Likes

All I know is the latest from GitHub was putting chunks at a pretty impressive rate last night.
More testing needed

4 Likes

I hope so, because I think 1MB max chunk size is getting too small. Maybe 10MB might be a happy middle ground between small devices and future storage sizes. Also middle ground considering communication speeds [0.2 seconds at 400Mbps].

5 Likes

The tests are with reduced chunk size!

6 Likes

500kb to be exact

6 Likes

Juicy!!!

10 Likes

It is about time… god

5 Likes

Time to get the Telegram bot working!!

I can provide an interface through the bot for some people who want to act as admin.
You can enter new test-net name, and url. Clear the old data and restart it with new updated sn_node.
Main reason is that the XOR urls for wallets that are stored in that local db are not getting carried over to new testnets. So each time we want to play with new testnet the old data has to be purged.

FYI people if you have never made account before on Google/Azure/AWS they offer some great free trials for first 12 months. You can run a simple node on Azure B1s for a whole year (750H per month, basically free) and also similar on AWS EC2 t2.micro (or t3.micro where t2.micro is not available).

Azure also offers 2 64GB free (P6) SSD drivers which can be used with the B1s and many other services: https://azure.microsoft.com/en-us/pricing/free-services/

Great way to get familiar with logging into a remote server, which would cost you normally a few $ per month to run. You can use it to play around with testnets or make your own and see if you can access the cloud hosted one from your own home. It’s free, use it!!

4 Likes

Yep, once we know safe update is working 100% then I will update DBC-testing/DBC-baby-init.sh at main · safenetforum-community/DBC-testing · GitHub so it checks for the latest release and then we will have a one-liner that will set up a baby-fleming with the genesis DBC in a wallet ready to go :slight_smile:

4 Likes

cool thank you!!!

2 Likes

Just want to say it’s admirable that the team is still working this hard for over a decade already, keep it up!

11 Likes

Yaay!!! New release
Safe Network v0.1.0/v0.15.4/v0.17.10/v0.3.5/v0.79.0/v0.75.0/v0.77.0/v0.70.0

Looks like safe update is now working again - Fill yer boots!!!

13 Likes

Just remember, safe update will only work from this release onwards. Any binaries you currently have will have the old code.

9 Likes

Also
curl -so https://raw.githubusercontent.com/maidsafe/safe_network/main/resources/scripts/install.sh | bash is pointing to old binaries so don’t try that shortcut either :slight_smile: