Yes, “the apps are coming” has to be the new mantra. There’s an early network mem issue the team are trying to crush right now, but this is a good progress IMO.
Network up
Stabilise
app API and bindings at the ready
apps launch
more engagement
As @mav notes, the massive engagement will be folk browsing the network and then using apps that also mutate/add data. That’s a near term for us now, when this PITA mem issue is crushed. Great to see the network up though, step 1 always had to be that. So a wee bit of spit and polish there then the exciting part, apps!!!
and browsing/fetching data should be somewhat performant I think there might be an exposed flank hidden currently that could require a tweak in the incentive scheme (pay faster nodes better than slow nodes; which automatically would resolve the issue of over-provisioning and running overloaded systems because those wouldn’t earn well and run at a loss) …
btw that solution for “cross-compiling for python” in the self encryption repo does look impressively well integrated with rust
Are there any APIs or even any basic basic docs on how a custom app might be made?
Let’s say i wanted to make a simple html site that has a word on it and lets users change tha word. Something like that would help me learn lots of the basics, of paying for data, user mgmt etc
Could anyone even point me to the basic basics? Would starting to get comfortable with Rust be the way? Then looking at Autonomi github posts or something?
The network will reset in January, and posisble some other times along the way.
But, currently there’s no reputation / credibility system in place, so as long as your node is doing the job, it’ll start earning as soon as it’s holding and providing access to the data it’s responsible for. No need to build up a history like there was with the previously planned node ageing
In addition to what @DavidMc0 said, the history of reputation was bound up with elders, sections and node ageing. The reputation was required to know which nodes would be suitable for being an elder and by consensus a node could become an elder to control the section.
That whole concept has gone and nodes are individuals living in the world of XOR addresses. They have neighbours and so on, and they make decisions on their own. By following “the rules” the other nodes will continue to talk to your node and live in happy connection with others and be productive. Occasionally one node will see another as not working right and “shun” it, not talk to it any more and your node may do that to other nodes.
Its this working together with the same same set of “rules” to follow that allows the individuals to work independently yet together to work, rather like ants as individuals working together. Yea I know they keep a queen captive to grow the ant colony and Autonomi doesn’t have that.
@joshuef Some observations without comment since the memory issue and high bandwidth issues are known about and the QUIC window size has not had a chance to be changed yet.
high upload bandwidth when compared with any recent testnet
/metrics function of nodes is not reporting wallet balance or payments received correctly. Typically over stating the amount when compared with the blockchain amount earned
memory issue happens occasionally where a node will require GBs of RAM. On my system they keep running since I have plenty of RAM but on smaller systems those nodes surely will suffer OOM closedown
Queued packets in router is between 6 and 20 MB and my router has 100’s of MB for buffer and as expected no dropped packets, because of plenty of buffer space, has been recorded in router stats
my nodes are seeing high numbers of bad nodes out there High compared to previous non 4MB max record sized networks
I had a website publishing and browsing demo called awe working prior to that, although it was unreliable due to bugs in Registers part of the API and general unreliability of the network. They’ve been trying to fix those but since the switch to ERC20 I’m unable to test that without putting a lot of work in and my attention is elsewhere for the time being. Much of the API use of awe should still be valid - so you could learn by looking at that if you are ok with Rust (good idea to be IMO). See Website builders - an invitation to awe
I’m down to 4/5 nodes on my home machines 8gb ram and 45 on my dedicated hetzner 128gb ram slowly dropping over the days and still got this wave pattern on cpu load.
I think there might be an exposed flank hidden currently that could require a tweak in the incentive scheme (pay faster nodes better than slow nodes; which automatically would resolve the issue of over-provisioning and running overloaded systems because those wouldn’t earn well and run at a loss) …
slowly dropping over the days and still got this wave pattern on cpu load.