{
"01_vendor" : {
"01_listing" : {
"01_metadata" : {
"01_obcv" : "",
{ | |
"genesis": { | |
"merchant": { | |
"metadata": { | |
"obcv": "", | |
"category": "", | |
"subcategory": "", | |
"nonce": "", | |
"expiration_date": "" | |
}, |
Should a buyer be selecting the moderator? In my view, no.
There are two options in this question:
- Vendor selects the moderator
- Buyer selects the moderator
If the vendor is selecting the moderator, then the buyer will be scanning listings and factoring in the choice of moderator in a decision to place an order. This means that any orders have essentially accepted the choice of moderator attached to that listing.
swagger: '2.0' | |
info: | |
title: OpenBazaar API | |
description: Let's make trade free | |
version: "1.0.0" | |
# the domain of the service | |
host: localhost | |
# array of all schemes that your API supports | |
schemes: | |
- http |
{
"vendor_offer" : {
"listing" : {
"metadata" : {
"version" : "",
"expiry" : "",
"category" : "",
"category_sub" : "fixed price"
},
There is a significant bottleneck in the current workflow for OpenBazaar, which is the selection of a third party notary or arbiter. Irrespective whether the notary or arbiter is the same agent, both the merchant and the buyer are required to come to a consensus in selecting a third party key-holder in a 2-of-3 multisignature escrow address. The fundamental obstacle is the risk of possible collusion between one of the parties and the notary, and the subsequent distrust one party has for the other party's notary preference. Unless both parties have preselected the same notary that they both trust, somewhat coincidentally, then a transaction cannot take place. This may result in significant and frustrating delays that run counter to the values that OpenBazaar ho
Thus far the proposals for various market implementations within OpenBazaar have assumed that the third party in a transaction (signer #3 in a 2-of-3 multisignature escrow address) performs two roles: a notary, and an arbiter. The notary aspect of their service includes digitally signing contracts and transactions, the latter in the event of a dispute between the buyer seller. The arbitration aspect of their role is to decide who the winning side is in a dispute between the buyer and seller. However, this overlapping notary-arbiter model is prone to several weakenesses:
- There is a conflict of interest between the arbiter and disputing parties
- There is a practical burden on a single agent to perform all of these tasks simultaneously for potentially dozens/hundreds of transactions
{ | |
langName: "English", | |
langCode: "en", | |
/* Use capitalized keys for widely reused text that must be capitalized */ | |
Next: "Next", | |
IAgree: "I Agree", | |
Back: "Back", | |
EnterMessage: "Enter message...", | |
Skip: "Skip", | |
Done: "Done", |
I hereby claim:
- I am drwasho on github.
- I am drwasho (https://keybase.io/drwasho) on keybase.
- I have a public key whose fingerprint is 0614 43F9 9FC1 4F63 5DB8 2E7B 5818 FAC9 E224 0372
To claim this, I am signing this object: