After a successful DialNet we’re looking to test our reworked payment process. Now instead of badly guesstimating costs on the network, we ask each and every node how much they’d like and pay that. (This can be tweaked to avoid bad actors easily enough). As such, every node will receive rewards for PUTs directly! (Note: you...
The DialNet testnet, launched this morning, contains some improvements to the issue of dialling unroutable peers - the one that was causing some nodes to remain chunkless. We have what we believe to be a fix in place now which we want to test out. It will still need some tweaking for performance, but we want to try it in the...
Over the past weeks we have seen some nodes that do not receive records. On further inspection, it seemed like peers of such nodes didn’t add them to their routing table. In essence this means those nodes aren’t seen as part of the network, but function like clients. When a new node connects to its peers, those peers have to...
We continue to refine features ready for the next testnet, notably introducing pay-per-chunk and UTXO. Paying per chunk means treating each chunk individually rather than the client bundling them into a merkle-tree and asking nodes for a quote on that file. Now clients query each node in the close group for the price of storing...
Your ideas needed... Pricing seems a simple problem, at least if a human can be in the loop but how can a massive network of simple nodes (think ants) come up with pricing based on a handful of those nodes and not let crafty humans or AIs game the system?
Thanks to all of you who have mucked in with testing ThePriceIsRightNet. It really is a massive help, and once again you’ve uncovered some unexpected issues. Indeed, this one has been a bit of a curate’s egg - good in parts. Starting with the good, all our nodes are still alive with no serious CPU or memory issues. As...
The next testnet, which should be launched any day now, will look at variable store costs. As a quick refresher, when nodes get full, the price of data storage increases in order to attract more nodes onto the network; conversely, when there is plenty of space on the network, the store cost falls. Before it stores a chunk of...
Thanks to everyone who’s participated in the DataPaymentNet testnet. It has performed its role magnificently, telling us that the fundamentals of data payments are sound, even if the UX leaves a little to be desired still. We’ve lost a few nodes after a replication spike the community spotted last night. But we’ve still...
Thanks to everyone who’s participated in the DataPaymentNet testnet. It has performed its role magnificently, telling us that the fundamentals of data payments are sound, even if the UX leaves a little to be desired still. We’ve lost a few nodes after a replication spike the community spotted last night. But we’ve still...
Another testnet is under way, we’re keeping an eye to see if our recent improvements are improving stability. Do join in if you have time. Nodes still have to be run from the cloud until libp2p has better QUIC support, but clients can run from anywhere. We’re hoping to see improved node stability, but we’re still seeing...
It’s getting a bit repetitive, but once again this week we can report that the NodeDiscoveryNet testnet is still up and running. A bit rough round the edges and in need of refinement, sure, but the foundations are feeling very solid. This stability is no longer a surprise, but after many years of excitement as we’ve...
One of the changes we’re working through this week concerns the updated version of libp2p, which brings some welcome improvements to AutoNAT - detecting and enabling nodes that are behind a firewall or router to join. We will soon be able to distinguish between global and private IP addresses, which was an issue before....
A good week of bug fixes and tweaks in preparation for our next testnet: NodeDiscoveryNet, which will look at how nodes find each other on the network. We’ve found a cause of excessive memory usage. We thought that nodes were only sending messages to the eight closest nodes to them, whereas they were actually sending messages...
As we speak, InstallNet is still humming along nicely, and we’ve already drawn some useful lessons from it, tested some assumptions, and made plans for improvements. The current iteration is really to test the safeup process that @ChrisO has been putting together to automate the installation of safe client, safenode and...
The general idea is that you have lots of ‘normal’ nodes and some which are able to adapt (using a generic algorithm or one of the more recent open ended evolutionary algorithms). This is in some ways an old topic, but the recent design changes, which include instant join of new nodes and a generally quicker time to earning...
Our next testnet, InstallNet, is a bit mundane in comparison to previous runs, but nonetheless does serve an important purpose. We would like to introduce and test the installation processes for the new network components. Objectives: Ensure the processes function correctly on multiple platforms Explore the user experience for...
The Safe Network is the world’s first autonomous data network, its mission is to protect everyone’s data and ensure that it stays online forever. It enables the creation of decentralized websites and applications and therefore enables the Internet as it should be....