If I may ask, what is your next step?
Everything is done for now but when we get the next task set your at the front of the line. What are your general thoughts on Zenoribbon? There is a booklet describing Zenoribbon at zenoribbon.freeforums.net. The next task set might not be for a few months because a security app will have to be written designed for more easy manual verifications than what we were able to do with the tasks on this thread.
Zenoribbon is part of Zeronet, which as an oversimplified explanation is a layer over Tor that makes it easy to provide anonymous web hosting service which would include transaction ledger service for Zenoribbon. And both Zenoribbon and Zeronet are part of Rainbow Road, which is a plan for decentralization of all power structures.
I meant what are your next steps for your project? The idea behind it interests me and I’m just curious as to where you go from here.
My overall thoughts is the idea is very promising, but as someone mentioned before, any time you have something manually done you open yourself up to potential scammers. It does seem that you have thought that part out so it isn’t as big of a worry as it might be.
One focus right now beyond a manual review security system (as currently uses the TweetNaCl page) is to release a general purpose "universal" API so that any and all "Service Cogs" can connect to each other which would include cogs for transaction of the claimchain ledger. A service cog is basically a web service (like chaimclain ledger evaluation service) that can just as easily be run solely for a local machine as it can be offered as a paid remote service. So, that API will likely use sockets so that there is little difference when a service is run locally compared to remotely.
A service cog will start out as a compliant python script that can function as an anonymous Tor service (in this case for Zenoribbon transaction processing). We really want such services to also be set up if possible, very importantly, over proxy service using one or more hops to enable regular browser interactions without .onion which is not yet widely supported by browsers. The point is to make it easy to set up and resell a device computing power for uncensored web hosting purposes, over Tor or proxy service. The general attitude is that if their is a will, there is a way. And if there is long hard work and dedication to such ends, this will all be accomplished.
The API uses a RAMDISK for memory with the encouragement for all Zenoribbon (or Zeronet) related service cogs to exclusively store all variables on the RAMDISK in human-readable text format. Transparency and total comprehension are really a key feature for Zenoribbon at all angles. The RAMDISK has been coded for release for Linux but has not been released yet. Technically its not a RAMDISK and is actually a tmpfs system, but Windows does not support that and so will need to be a RAMDISK on Windows. That code is due to be released in July.
