This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Verifying that "austinwilliams.id" is my Blockstack ID. https://onename.com/austinwilliams |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Run: "chmod u+x obsetup.sh" before running the script | |
user=$(whoami) | |
dir=$(pwd) | |
if [ $user = 'root' ]; then | |
echo "Please run this script as a regular user." | |
exit; | |
fi |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I am @onewayfunction on Twitter. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The approach of storing hashes of reviews in the btc BC and having Sellers (and possibly notaries) held accountable for hosting the reviews (and verifying that they are doing so honestly) has at least two difficulties. | |
The first is, 'how do we find all the review hashes for reviews of a given seller in the btc BC'? | |
The second is, How do we verify that the reviews are legitimate (came from the buyer listed in a completed OB Ricardian contract)? I hope to address both of these problems below. | |
The following approach to storing reviews is intended to (a) make it easy to find (hashes of) legitimate OB reviews in the btc BC and (b) impossible to inject (hashes of) false OB reviews directly into the BTC blockchain. A malicious seller could still create a bunch of notary/buyer sybils, create false trades, and leave reviews for himself that way. That's a separate problem. | |
The approach below requires each seller to have a dedicated btc address, SELLER_REVIEW_ADDRESS, that will be used for the review process. This |