Evaluators Wanted

[nelson4lov]

~

Hopefully if you put in that public sharing key, then the provided signature above, then the hashed message, and click verify it will say "verified"? This would count as another paid task specifically for you. I need to be sure the TweetNaCl kit is working correctly because this is 3 for 3 signature verification fails.

Public Key: SNEw1GN/FuTzcN3LJJLXt8erw7zkhnl4MQJ5GESNz98=

Hash of the above evaluation statement: OgKBFR13cfSEMKG4dhU2p0q4MIOW1Oi6NAKbV3LtnrB5HR2MCoUSjsDy9xDMzw6YyR71cTfRzKlRVcq ia1vSUQ==
Signature (of hash): 27f2On2g7buUR02aL5+RA/CY7KqEWSwn4WJozuFgVDxS8pyF/7MdLhBxrGiidkxS62U8GgmGQ16uaWPfr9lPDw==


I've now updated my submission. I tried it myself and it shows that it is verified. Let me know if it works as expected.

[1714825428]

1714825428

[1714825428]

1714825428

[1714825428]

1714825428

[1714825428]

1714825428

[1714825428]

1714825428

[1714825428]

1714825428

[SiNeReiNZzz]

EVALUATION TASK 1 OF 4
~

~

The hash came out correctly for me, but the signature failed verification. So, for the message you'd want to put in the hash line (the line with OgK....Q==), then you'd want to put in your private key and click sign. Hopefully you can get a new signature on the hash?

Okay, I'll be home in about two hours. It's a little awkward on my cell phone to do this...

As soon as I'm home, I'll make the right verification for you.

Sorry

[SiNeReiNZzz]

EVALUATION TASK 1 OF 4
~

~

The hash came out correctly for me, but the signature failed verification. So, for the message you'd want to put in the hash line (the line with OgK....Q==), then you'd want to put in your private key and click sign. Hopefully you can get a new signature on the hash?

Hmm... Interesting that I was not alone on the wrong track...

I hope I have now completed the task (I have added some screenshots for you to review):



Public Key: f74kSSFLWcz8qahPw2c6wEaaGBhacFgaP8zaADyk8BU=

Claim Identifier: 26HCsa7MldWXjplJMd6Js++bitjDw+ILhkQ1rn9/2R+6DVmh/EX43vEYIrYzppabv8DKy5OSglHwPYq4GbPIwg==
Full Property Name: Zenoribbon of Rainbow Road
Abbreviations: ZR, Zenoribbon
I searched the internet for a few minutes and was unable to find any earlier homestead claim to any similar works as named or abbreviated "Zenoribbon", though ZR is too generic of a term to search and so ignored.
I honor this homestead claim as an original creation.
Hash of the above evaluation statement: OgKBFR13cfSEMKG4dhU2p0q4MIOW1Oi6NAKbV3LtnrB5HR2MCoUSjsDy9xDMzw6YyR71cTfRzKlRVcq ia1vSUQ==
Signature (of hash): veIMN7zTpkx3TJDh56NIiYeH+tDLscaTdmIVJ95khAHHW6z/aHkdbfGY1Z7C9cHO2tcbuED7s5nVLn87ge1FDQ==

[Zippy]

~
1E4z9grbyhYQdd7acZwdpecBJBchxed3TS
~

I’m sorry I read your first message incorrectly.
U1b3FSErIxUI7jdg9H79KUJpYYYAvZSvXodbaGSrie8
8qHo2pfAVD3CIcjI4nV4mebBPhwtjYCJmCFLz4zARJVz2jeR//9g+/YrxKUNZk16fIeg7K8Mme036uwYZ9dBDw==

Unfortunately that validation failed. You signed your bitcoin address beginning 1E4 with the public key beginning U1b and the resulting signature is the text beginning 8qH? I'm hoping there are no bugs in the TweetNaCl demo kit.

Ok I just tried it again

1E4z9grbyhYQdd7acZwdpecBJBchxed3TS

3oatsD6vkg748Yh74fw4hBMfGysM+8TU4I5vYelYZQAp6NgC9W9xOp3jLjMi2u21n1Dxc7guBzNajMK9Su8FKw==

KejYAvVvcTqd4y4zItrttZ9Q8XO4LgczWozCvUrvBS

Let me know if that one works

Please label everything so I know what is what. Three parts for a signature validation would be the public key, the message (which is generally a hash for any signature which in this case is your bitcoin address), and the signature itself.

[Moonpie28]

~
1E4z9grbyhYQdd7acZwdpecBJBchxed3TS
~

I’m sorry I read your first message incorrectly.
U1b3FSErIxUI7jdg9H79KUJpYYYAvZSvXodbaGSrie8
8qHo2pfAVD3CIcjI4nV4mebBPhwtjYCJmCFLz4zARJVz2jeR//9g+/YrxKUNZk16fIeg7K8Mme036uwYZ9dBDw==

Unfortunately that validation failed. You signed your bitcoin address beginning 1E4 with the public key beginning U1b and the resulting signature is the text beginning 8qH? I'm hoping there are no bugs in the TweetNaCl demo kit.

Ok I just tried it again

1E4z9grbyhYQdd7acZwdpecBJBchxed3TS

3oatsD6vkg748Yh74fw4hBMfGysM+8TU4I5vYelYZQAp6NgC9W9xOp3jLjMi2u21n1Dxc7guBzNajMK9Su8FKw==

KejYAvVvcTqd4y4zItrttZ9Q8XO4LgczWozCvUrvBS

Let me know if that one works

Please label everything so I know what is what. Three parts for a signature validation would be the public key, the message (which is generally a hash for any signature which in this case is your bitcoin address), and the signature itself.

Public Key: CqC/13SxJt9qd/sBl+0TxOqNsPQT9M27VArBuKoPK/Q=
Secret key: zZmo6GX6vWLgft2zUF/pF/aXyI0Xbz819pG0iHDzy80KoL/XdLEm32p3+wGX7RPE6o2w9BP0zbtUCsG4qg8r9A==
Signature: Xdpm7CO23SYCgG4b27ZmPYr/xPCM/iLzKerH7uOuLxR1Dd3QSbOFvx1gJZoge87CkvO4uhpuZTVsEI+2zHjVCg==

[Zippy]

~
EVALUATION TASK 1 OF 4
~

Good, your signature properly verified on my end! I was worried that the TweetNaCL demo was bugged as it has already been patched once a few months ago due to a possible bug, though my worries have not completely gone away. I suppose I should have included a tutorial on how to use that signature page. I'll send the remaining $10 USD as BTC due within one day because you've already done enough work to earn it.

A participant named feathertone is going to code our own version of that signature kit and already did one for PGP as a savable offline webpage. feathertone's security kit is easier to use but is still considered a work in progress.

[Zippy]

~
1E4z9grbyhYQdd7acZwdpecBJBchxed3TS
~
Public Key: CqC/13SxJt9qd/sBl+0TxOqNsPQT9M27VArBuKoPK/Q=
Secret key: zZmo6GX6vWLgft2zUF/pF/aXyI0Xbz819pG0iHDzy80KoL/XdLEm32p3+wGX7RPE6o2w9BP0zbtUCsG4qg8r9A==
Signature: Xdpm7CO23SYCgG4b27ZmPYr/xPCM/iLzKerH7uOuLxR1Dd3QSbOFvx1gJZoge87CkvO4uhpuZTVsEI+2zHjVCg==

Good, that verified. I'll relay the $5 USD as BTC within one day and your in as at least a backup evaluator. I'll PM you with any tasks to follow.

[Moonpie28]

~
1E4z9grbyhYQdd7acZwdpecBJBchxed3TS
~
Public Key: CqC/13SxJt9qd/sBl+0TxOqNsPQT9M27VArBuKoPK/Q=
Secret key: zZmo6GX6vWLgft2zUF/pF/aXyI0Xbz819pG0iHDzy80KoL/XdLEm32p3+wGX7RPE6o2w9BP0zbtUCsG4qg8r9A==
Signature: Xdpm7CO23SYCgG4b27ZmPYr/xPCM/iLzKerH7uOuLxR1Dd3QSbOFvx1gJZoge87CkvO4uhpuZTVsEI+2zHjVCg==

Good, that verified. I'll relay the $5 USD as BTC within one day and your in as at least a backup evaluator. I'll PM you with any tasks to follow.

Sounds good

[SiNeReiNZzz]

Nice to read that it all worked out.

Yes, if there are any bugs on the own website, it can cause you sleepless nights!
But I doubt it was because of TweetNaCl.js.
I don't know what I did wrong the first time, but I admit it took me a few minutes to understand what to do. With your second instruction, I knew immediately what i have to do.
Maybe your writing style was a little confusing, or I just had a bad day.

I'm would be very happy, to be allowed at your disposal for further tasks.

[Zippy]

~

Hopefully if you put in that public sharing key, then the provided signature above, then the hashed message, and click verify it will say "verified"? This would count as another paid task specifically for you. I need to be sure the TweetNaCl kit is working correctly because this is 3 for 3 signature verification fails.

Public Key: SNEw1GN/FuTzcN3LJJLXt8erw7zkhnl4MQJ5GESNz98=

Hash of the above evaluation statement: OgKBFR13cfSEMKG4dhU2p0q4MIOW1Oi6NAKbV3LtnrB5HR2MCoUSjsDy9xDMzw6YyR71cTfRzKlRVcq ia1vSUQ==
Signature (of hash): 27f2On2g7buUR02aL5+RA/CY7KqEWSwn4WJozuFgVDxS8pyF/7MdLhBxrGiidkxS62U8GgmGQ16uaWPfr9lPDw==


I've now updated my submission. I tried it myself and it shows that it is verified. Let me know if it works as expected.

Unfortunately verification failed. Maybe you accidentally added spaces? Please retry again with your info to make sure its not a TweetNaCl issue.

[Zippy]

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

[nelson4lov]

~
Unfortunately verification failed. Maybe you accidentally added spaces? Please retry again with your info to make sure its not a TweetNaCl issue.

I hope it works this time.

Link to paste bin: https://pastebin.com/MaUicFhs

PS: I used pastebin due to some inconsistency with the hash of the message.

Screenshot:

[SiNeReiNZzz]

~

~

You have probably already signed messages with your BTCTC address. This is almost the same here!

You just have to imagine:
Public key = your BTCTC address
Secret key = Private key of your BTCTC addressInstruction:

Go to the site: https://tweetnacl.js.org/#/sign

1. > Click on 'Random' and write down the Secret key and the public key (remember the Secret key is like your private key at BTCTC, and your future key for further tasks, so that you do not have to create a new one each time)

2. > Write in the 'Message' field (without spaces in front or back): OgKBFR13cfSEMKG4dhU2p0q4MIOW1Oi6NAKbV3LtnrB5HR2MCoUSjsDy9xDMzw6YyR71cTfRzKlRVcq ia1vSUQ==

3. > Click 'Sign' (after this point, you don't need the Secret key anymore for this task), then a Signature should appear (just like BTCTC)

4. > Write this Signature in the Evaluation Statement below at Signature (of hash) (marked purple) and then just insert your Public key (from step 1) (marked green):Public key:

Evaluation Statement:
Claim Identifier: 26HCsa7MldWXjplJMd6Js++bitjDw+ILhkQ1rn9/2R+6DVmh/EX43vEYIrYzppabv8DKy5OSglHwPYq4GbPIwg==
Full Property Name: Zenoribbon of Rainbow Road
Abbreviations: ZR, Zenoribbon
I searched the internet for a few minutes and was unable to find any earlier homestead claim to any similar works as named or abbreviated "Zenoribbon", though ZR is too generic of a term to search and so ignored.
I honor this homestead claim as an original creation.
Hash of the above evaluation statement: OgKBFR13cfSEMKG4dhU2p0q4MIOW1Oi6NAKbV3LtnrB5HR2MCoUSjsDy9xDMzw6YyR71cTfRzKlRVcq ia1vSUQ==
Signature (of hash):

[Zippy]

~
Unfortunately verification failed. Maybe you accidentally added spaces? Please retry again with your info to make sure its not a TweetNaCl issue.

I hope it works this time.

Link to paste bin: https://pastebin.com/MaUicFhs

PS: I used pastebin due to some inconsistency with the hash of the message.

Screenshot:

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.

[nelson4lov]

~
Unfortunately verification failed. Maybe you accidentally added spaces? Please retry again with your info to make sure its not a TweetNaCl issue.

I hope it works this time.

Link to paste bin: https://pastebin.com/MaUicFhs

PS: I used pastebin due to some inconsistency with the hash of the message.

Screenshot:

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.

Glad to hear. I noticed it. I don't know why - I pasted it multiple times and it still had the same issue so I opted for pastebin. waiting for the next task!

[Zippy]

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.

[Zippy]

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 copy & 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.

Edit: I don't have time to add details at the moment so feel free to take two days for this task as I'll post details in about 14 hours and will will send PMs to the evaluators with a link to the details.

The evaluation statement will be something like:
Evaluation:
Honor to: 0nP5UpmI3+m9Uk1qf8fMQK3drWwS7p4+sLSZu7iepnFv1rHUJElJqDjQtYJLfWM/jW1e/LwdLn69g1bdLvuyCQ==
Hash of Evaluation Statement:
(Hash of above starting with "evaluation:" and ending with "CQ==")
Signed:
(digital signature of the hash using your evaluator keys)

[SiNeReiNZzz]

~

~

I greet you most sincerely.Task 2 of 4:

Public Key: f74kSSFLWcz8qahPw2c6wEaaGBhacFgaP8zaADyk8BU=

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==Evaluation Statement:

Public Key: f74kSSFLWcz8qahPw2c6wEaaGBhacFgaP8zaADyk8BU=

Evaluation:
Honor to: 0nP5UpmI3+m9Uk1qf8fMQK3drWwS7p4+sLSZu7iepnFv1rHUJElJqDjQtYJLfWM/jW1e/LwdLn69g1bdLvuyCQ==
Hash of Evaluation Statement: jlSdGzZ2AJeTFMg6eIvxIVIjv2rIsdgf4Zhi4UEVGSjF4KIOGgHfzcV+dyNnKCVkjNIqjJrd23KD2A/5Ues+Rg==
Signature: ReECezZZVGIxvIZeCMNFWY42czX/RLeOANNrGNKENcPKEWsTtuljYmbVryh38AaW5/QWzFK72LU9YHuXyDMfAw==

And with SHA512 Hash of Evaluation Statement:

Hash of Evaluation Statement: 8e549d1b367600979314c83a788bf1215223bf6ac8b1d81fe19862e141151928c5e0a20e1a01dfc dc57e7723672825648cd22a8c9adddb7283d80ff951eb3e46
Signature: o8aYBduwhDPPss3IdVLeGqPreJQq7Vyoxwx+8zgMxi9WtgBMEkjp8oZmTAWYcBhjWc7tLYNu9djZlQSfHvEbBw==

[Aveatrex]

I am a Junior dev. Count me in if you still need people

3FBZQp5vVQtTtTdpVGCPBUKN2EtqyYkwi9

In case I have not told you already, you're in as backup #1. There was another backup number one, but they were needed already. The BTC signup pay has been sent.

If you need me just send me a pm and for some reason you aren't able to send me one, just quote me here I'll receive a notification via Telegram.

[amishmanish]

OP, You have a thing going on here. From what i understand, this is an idea of using a web of trust to verify transactions. Consensus to be arrived at by building and utilizing a web of trust. Its like an online version of a bunch of clerks maintaining the ledger in banks in old times.

I doubt its usage for settling transactions but the idea itself is worth exploring as it has potentially several applications in the times of Social media. I would follow this. I have a small but important request for you to kindly consider.

If its a "web of trust" we are looking at, please keep a condition that people who have used alt-accounts for spamming and have negative trust feedback should not be accepted. The condition for "minimum 8 posts" is pretty weak, especially considering that you have an ages old account at the forum. If this isn't a bought account, you must be aware of the mass manipulation and scamming this forum has gone through. If you are looking to start a web of trust, wouldn't it be prudent to have some sort of best practices??

Good Luck!