One big blocker we have found is an OS limit on the number of open files (sockets being files). There is some things that can be done, such as multiplexing, but it is not as easy as it sounds.
It’s an interesting area as well, just for info, when SAFE was first conceived, I actually pondered for a while to write the vaults like a virus. The notion being it would spread across the net and just create the network, of course, there were a ton of negatives, but it was an interesting idea.
In some ways, yes, but even ipv6 will traverse NAT and currently ISP’s will probably want to make sure that stays the same, it allows blocking etc. This part of the net has amazed me, where either government pressure or very bad OS security or human complacency has never fixed the “everyone is direct connected”.
Again if these events were linked to data stored/accessed then it is probably the best way to measure the sections needs. Not simple, but I think on the right track. This is linked to this:
There is a strong notion and push to not have safecoin as data items, but as integers in the client managers. Then the disability is very simple.
What would be really nice is a way to have accounts very simple to set up, some kind of credit for storing stuff that is not junk, or perhaps some human provable interactions, like surveys or something. None of these are simple, but its always a thought.
In terms of vaults, it would be brilliant to allow them to just start automatically and earn quickly, I would think this will be possible though, if such vaults were handling lots of client interaction, getting old data that may be missing from the section, or confirming all members have the data they should and so on. I see these actions as value and therefor should be rewarded. So starting a vault that perhaps does not really join, but does a load of work for say 4 hours can earn enough safecoin to create a single account perhaps.
These areas do need to happen, whether for V1 or not, I am not sure, but if we as a community can find those answers then coding them is not a problem, if the design is done and the algorithm worked out with any side effects (hopefully none) known, then the code part is just the mechanical thing we do and the devs can do really well and quickly.