Rainbow Rock is a guide book for people seeking meaning in life and wanting to develop them self as a person, with tips for living life in general. This is just released and published anonymously as a free book. I'd love to hear people's thoughts on this book.

Here is the (free online) book: https://www.free-ebooks.net/philosophy/Rainbow-Rock

I provided a bonus because you went the extra mile with color coding and additional instructions. The extra effort is appreciated.

Thanks very much, I suppose I will create a Zenoribbon coding thread to copy all our developments to. I appreciate that offer and will keep you in my IM contact list!

As I just mentioned in the above comment, a coder (Triturian) is coding a communications-by-socket API that should be able to work as both a (paid or unpaid) remote service and as a local service. That API will allow the transaction ledger services to be automated and anonymous. So, the application API is being coded before the application itself.

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.

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.

Well there is nothing broken with your message. Its just that any long hash copied and pasted from this forum seems to have space added when pasting the text. Tasks 3 and 4 are canceled as described above in my response to sinereinzz so you're now done with all tasks, thank you for your time! Optionally you can let me know if you understand the concept behind retrocast messaging transactions. I will relay payment within 24 hours.

Task 2 Complete, thanks for your time! Tasks 3 and 4 and canceled but everyone will be paid as if they were done. While Zenoribbon now technically exists by the homestead claim, which was published as a retrocast message, and there was technically a transaction (the containerization), we don't plan more transactions until we design an EASY way to transact it manually. Manual transactions are supposed to be easy, but are not. So, we will design a better signature verification system. It will be nearly identical to the TweetNaCl page, but with warnings and instructions. Its up to feathertone, who puts together the security kit. feathertone already has a great RSA signature app but it the key lengths are unacceptable and so we'll get a Wireguard type kit, which is basically the TweetNaCl kit but slightly easier to use. RSA is still common but think about what this thread would look like using RSA!

Thanks, this did verify, though it added a space to the hash as usual making it difficult to verify. I'd recommend saving your public key as that key  being an early evaluator is street cred for when the evaluation service is released.

Task 2 Correction:
The text as copied and pasted from the first link provided is actually:
CONTAINERIZATION
CONTAINER
ZR 0 to 1
CONTENT IDENTIFIER: Zenoribbon of Rainbow Road
CONTAINER IDENTIFIER: d9533c95c6a0d03e634b124f90c08c58800d3fb368b7f392ac698c66f140a6f7adf84ab27fa4f36 064f9817f17a1e578ee0d25e5c3fdb2c593a1e3f035c02b60
Hash of Containerization Text Above: SHA-512 Base64: a2041a22eec1a991d91fb71c40f6e88549ca64008f6df59834ad7b32e486221fb3f6db7f53738d6 9bd5d340a12b93cb96debcb819b6034d735acfd2d40d06a7c
Hash Signature and Transaction Identifier: Ed25519 TweetNaCl:
0nP5UpmI3+m9Uk1qf8fMQK3drWwS7p4+sLSZu7iepnFv1rHUJElJqDjQtYJLfWM/jW1e/LwdLn69g1bdLvuyCQ==

I copied and pasted from the wrong source! So, in any case, the signature would match in your evaluations. This is part of the reason why I'm doing this... to see just how hard it is to do the claims and evaluate manually. Not that easy to do correctly at least when your new at evaluating apparently. But we'll design tools to make it easier for a manual verification before we design the automated tool.

Task 2 of 4 Detailed Instructions:

1. Examine the page at
https://boards.4channel.org/vip/thread/99136#p99161 which has been cc'd to the zenoribbon.freeforums.net claimchain ledger.
It will have this text:
CONTAINERIZATION
CONTAINER
ZR 0 to 1
CONTENT IDENTIFIER: Zenoribbon of Rainbow Road
CONTAINER IDENTIFIER: d9533c95c6a0d03e634b124f90c08c58800d3fb368b7f392ac698c66f140a6f7adf84ab27fa4f36 064f9817f17a1e578ee0d25e5c3fdb2c593a1e3f035c02b60
Hash of Containerization SHA-512: a2041a22eec1a991d91fb71c40f6e88549ca64008f6df59834ad7b32e486221fb3f6db7f53738d6 9bd5d340a12b93cb96debcb819b6034d735acfd2d40d06a7c
Hash Signature: JO+1T3LpvwQRAJ3F0wgx2+5774fO0MewdreycjDLFGAPbJlLI5+9uW4LRFwUKTtQ0YEnP2v/iBC/tqtxK6iVAg==

This is a claim that Zenoribbon is being placed in a container which can be transacted over the Public Settlement Network (PSN), which can only be honored if done by the rightful owner. So, Check to see if there are any other earlier tranfers of Zenoribbon using a basic internet search. If not, the transaction is potentially valid.

2. Verify that the "Hash of Containerization" matches the text beginning "CONTAINERIZATION" and ending "...b60"
Unlike the previous hashes in task 1, this hash is in Base64 encoding and so the TweetNaCl hash won't match. However, the more common version will work.
A good SHA-512 Base64 hash tool can be found here:
https://emn178.github.io/online-tools/sha512.html
In the input box, the hash from above beginning "CONTAINERIZATION" and ending "...b60"
Remove any spaces in the hash because copying and pasting from a browser sometimes adds spaces that ruin the hash.
The output should match the hash as claimed beginning "a204..." for the containerization to be valid. If valid, then you can go to the next step.

3. Verify that the hash signature matches the owner of "Zenoribbon of Rainbow Road" which is indicated by this public key according to your previous evaluation:
Claimant Sharing Key: hqXdZnrTvicitWv4V/LH/9qA3nUMcl5PIbbdgclZ9cY=
A good signature kit can be found at: https://tweetnacl.js.org/#/sign
Click on the verify tab.
Enter the sharing Key as the signature public key.
Enter the Hash signature from above "JO+... Ag==" in the signature line.
Once again, delete any spaces added by your browser.
Enter the "Hash of Containerization" hash as the message. In this case that is the above hash beginning "a204" ending "...a7c"
Click Verify. Hopefully the statement verifies correctly!

4. If everything is valid and there are no conflicting claims found by an internet search, then you can honor the statement using the same signature signing process used in step 1:
Create the evaluation statement as:

Evaluation:
Honor to: 0nP5UpmI3+m9Uk1qf8fMQK3drWwS7p4+sLSZu7iepnFv1rHUJElJqDjQtYJLfWM/jW1e/LwdLn69g1bdLvuyCQ==
Hash of Evaluation Statement: (hash of honor statement above goes here)
Signature: (signature of the hash in the previous line above)
Public Key: (insert your public key here)

a. Hash the text starting with "Evaluation" and ending "...CQ==" using a hash tool such as the linked page above.
b. Sign the hash such as by using https://tweetnacl.js.org/#/sign
You should still have your public and private key from the previous task. If you don't have that key, generate a new one with the "random" button and save both the private and public keys it for future use.
Paste your private key to the private key field.
In the message field, put the line generated from hashing your evaluation statement, which may be this:
8e549d1b367600979314c83a788bf1215223bf6ac8b1d81fe19862e141151928c5e0a20e1a01dfc dc57e7723672825648cd22a8c9adddb7283d80ff951eb3e46
Then click sign.
Paste the resulting signature in place of "(signature of the hash in the previous line above)" in your evaluation statement.
c. Paste your public key in place of "(insert your public key here)" in your evaluation statement.

5. Post your evaluation statement to this thread. Done! As always, don't be afraid to loosely interpret these instructions and do things according to your personal preferences.

Hi, you are in as the last evaluator needed for the time being. I'll PM you if there are any tasks for you.

We have enough evaluators for the time being. Thanks!

The Web of Trust is expected to be established on Zeronet (ZNET), which is basically a layer over Tor where everyone is encouraged to run anonymous services which could include a Zenoribbon claimchain ledger. Unlike .onion service, a Zeronet Service Cog is intended to be extremely easy to set up for any participant. Each participant is expected to build their own web of trust by ranking who they trust most to least. The overlap of agreement between that person and each other person they interact with on the network is where consensus begins to build. From that point, users are expected to assign a level of honor to the various groups within their network of most trusted people. The group with the highest honor is then delegated as the consensus leader for that participant. The protocols of that group will be accepted as the protocols used. So for Zenoribbon, the minimum time delay between transactions would be an example of the requirements by that group to get a transaction validated.

The Web of Trust is merely a formality. Crypto enthusiasts know that Bitcoin Core is the group setting the Bitcoin protocol. However, who knows their public key? Everyone should have a copy of their public key. We don't have that because we generally don't have a formalized and automated Web of Trust application. Such an application would enable much better security for everyone.

Good, that verified nicely, though you swapped signature lines such that the last signature actually corresponds with the second to last hash. The reason why that doesn't need to be corrected is that a digital signature itself is considered bound to whatever statement is verified by it. It is the duty of the signor on the Public Settlement Network (PSN) to check all hash codes to make sure they match the text lest they accidentally sign away their soul. So the moral of the story is to sign a hash carefully on the Public Settlement Network!

Task 2 Note:
A good SHA-512 Base64 hash tool that is savable as offline as an extra security step is here:
https://emn178.github.io/online-tools/sha512.html

The first step would be to cop & paste the text beginning "CONTAINERIZATION" and ending "...35c02b60". The TweetNaCl uses a rare encoding base for their hashes, so this is using Base64 as an easier way to achieve consensus.

Task 2 of 4

Zenoribbon has now been "containerized" so it can be traded on the Public Settlement Network (PSN):
https://boards.4channel.org/vip/thread/99136#p99161
and CC'd to zenoribbon.freeforums.net Claimchain ledger.

The verification task is to ensure that the container identifier matches to the first person to claim it, that the hash accurately matches with the containerization text, and that the same public key that signed the homestead claim is the same public key to sign the containerization transaction. A simple internet search and check of the zenoribbon.freeforums.net transaction ledger will help in deciding if that is the next valid transaction after the homestead claim.

So, a statement of your choosing is then signed to verify that all the above is accurate and honored, or of not honored if the transaction is done with problems. I'll provide detailed instructions in a next post, but it will take a bit of time so this is hopefully enough to get started.

Yes, that worked with the same data. Thanks for the time you took to correct this. When I copied & pasted the hash as you listed from the forum message, a space was added in when I pasted the hash data like this:
"KlRVcq ia1vSUQ=="

I didn't notice the space and wouldn't expect such an odd bug in the forum or browser I'm using. But I do now feel good about the TweetNaCl encryption page. They use a rare encoding method for their hashes, which I might not be widely accepted. But of course their public keys are also encoded by the same method. Its something we'll have to consider, but its a good app and good code.

Payment will be sent to you within a day of this message. Task two will be posted shortly.

Task 2 of 4 Notice:

Since there were some minor issues with day 1, I'm waiting until tomorrow to post task two of four. Sorry for the delay. As a side note, tasks are generally expected to be completed within 30 hours of being posted, but of course sooner is always appreciated.

Zippy

https://ibb.co/4JZHSvpUnfortunately verification failed. Maybe you accidentally added spaces? Please retry again with your info to make sure its not a TweetNaCl issue.