Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

View Austin-Williams's full-sized avatar

Austin Williams Austin-Williams

  • The Internet
View GitHub Profile
Verifying that "austinwilliams.id" is my Blockstack ID. https://onename.com/austinwilliams
@Austin-Williams
Austin-Williams / obsetup.sh
Created July 22, 2016 23:24 — forked from mariodian/obsetup.sh
OpenBazaar Server installation script for Ubuntu
#!/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
I am @onewayfunction on Twitter.
@Austin-Williams
Austin-Williams / Possible_Approach_to_OB_Reviews
Last active August 29, 2015 14:23
A possible approach to storing reviews for completed OB transactions.
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