Was just looking at the https://safenetwork.tech/ website and looks like it is quite out of date for the road map and still has farming as a part of the network.
Are we far away from getting to a place where some resources can be feed up to get things upto date?
Guessing you would be the man to ask @JimCollinson
Is this something that may be advanced with PRs from the community?
Im thinking of feeding all the latest updates into Chat GPT (other LLMs are available both on and offline) and seeing what it spits out.
Seems like this is a crap prompt for Wizard v1.1…
Please look at these updates from the SAFE network and summarise them to give a comprehensive overview of the project at present. These updates are in date order and often supercede each other as development progresses.
Then I cut n pasted 4 updates from April May… Its been 20 mins and no action… I gave it 8 threads…
I need to explore this screen in more depth - and try to understand what each setting means
The last four updates sumarised by Claude 2. Not bad, although its guess as to what DBC stands for is off.
Please look at these updates from the SAFE network and summarise them to give a comprehensive overview of the project at present. These updates are in date order and often supercede each other as development progresses.
paste.txt
16.65 KB
Here is a summary of the key points from the SAFE network development updates:
The SAFE network team has been running multiple testnets to test stability and functionality of nodes, data replication, payments, and other core components. The latest testnets have shown improved stability compared to prior versions.
A key focus recently has been implementing the ability for clients to pay for data storage and transfer using Data Balance Certificates [should be Digital Bearer Certificates] (DBCs). This includes obligatory payment for chunk uploads, storing DBCs in record stores, and refactoring to optimize the client chunking process.
The team continues to work on fixes and optimizations to further improve node stability, reduce memory usage, handle edge case bugs, and enhance the user experience. This includes investigating issues like connection errors, record parsing failures, and replication spikes.
Ongoing work is happening on conflict-free replicated data types (CRDTs) like Registers, making registers content-addressable, concurrent fetching of spend proofs, and other enhancements.
There is increased collaboration with the Rust libp2p team on fixes for things like excessive connections, port reuse, and NAT traversal. QUIC support in libp2p is still pending but should help simplify nodes.
Looking ahead, plans include integrating SimpleX for DBC transfers, dynamic data pricing, decentralized identity, personal AIs, and more. But the core focus remains on testnet stability and performance at this stage.
Overall, the project seems to be making steady progress in getting the core networking components tested and stabilized before moving to larger scale testing and additional features. Community involvement and feedback has been instrumental in the iterative development process.
Maybe correct it to Digital Bearer Certificates for unwary readers.
We are working on it yes!
Is there any support for different languages in the new version?
Privacy. Security. Freedom
Not quite at that stage yet
