User Tools

Site Tools


bitcoin:federatedmarket

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
bitcoin:federatedmarket [2011/08/05 18:57] donpdonpbitcoin:federatedmarket [2011/08/08 17:16] donpdonp
Line 1: Line 1:
 ===== Bid/Ask Federation ===== ===== Bid/Ask Federation =====
  
-A distributed database(ala gnutella) of asks/bids+A distributed database of asks/bids. An ask or bid offer is created, signed, and communicated into a telehash network.
  
-Queries are generated locally and communicated into the neworkmatching asks/bids are sent to the query origin.+Clients can subscribe to a telehash channel and receive new offer informationSome service perhaps to catch them up on old information
  
-con: High latency for queries.+Another service to take query requests for those who dont want to run a client that receives offer information.
  
-===== Escrow Service (ES=====+basic distinction: are the offer records(DNSdistributed or the search requests(gnutella)? far less traffic in distributing the offer records than distributing the search queries. 
  
-==== plan A ==== 
-Client A visits ES home page. \\ 
-Client A provides: BTC amount description, USD amount description, Time limit, A's dwolla receiving address. \\ 
-ES provides: deal ID/url, ES's bitcoin receiving address. 
  
-Client A communicates deal ID/url to client B. +===== Escrow Service (ES) =====
- +
-Client B visits ES deal url. \\ +
-Client B provides: BTC amount description confirmation, USD amount description confirmation, B's bitcoin receiving address. \\ +
-ES provides: ES's dwolla receiving address. +
- +
-ES waits to receive BTC and USD. +
- +
-Client A sends BTC through bitcoin client. \\ +
-Client B sends USD through dwolla. +
- +
-ES skims a transaction fee from BTC and/or USD. \\ +
-ES sends remaining amount of BTC to client B and USD to client A. +
- +
-ES deal URL shows history of the deal.+
  
-==== Plan B ==== +One party visits ES home page to define a deal. (Deal State: Defining) \\
-One party visits ES home page to define a deal. \\+
 The party provides: BTC amount description, USD amount description, Time limit. \\ The party provides: BTC amount description, USD amount description, Time limit. \\
-ES provides: deal ID/url.+ES provides: deal ID/url. (Deal State: Confirming)
  
 Party A communicates deal ID/url to party B. (ok if this happens later on) Party A communicates deal ID/url to party B. (ok if this happens later on)
Line 45: Line 26:
 ES provides: ES's dwolla receiving address. ES provides: ES's dwolla receiving address.
  
-ES waits to receive BTC and USD.+ES waits to receive BTC and USD. (Deal State: Collection)
  
 Client A sends BTC through bitcoin client. \\ Client A sends BTC through bitcoin client. \\
 Client B sends USD through dwolla. Client B sends USD through dwolla.
  
 +(Deal State: Dispursement)
 ES skims a transaction fee from BTC and/or USD. \\ ES skims a transaction fee from BTC and/or USD. \\
 ES sends remaining amount of BTC to client B and USD to client A. ES sends remaining amount of BTC to client B and USD to client A.
bitcoin/federatedmarket.txt · Last modified: 2024/01/31 04:08 by 127.0.0.1