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
bitcoin:federatedmarket [2011/08/05 17:47] – [Plan A] donpdonpbitcoin:federatedmarket [2024/01/31 04:08] (current) – external edit 127.0.0.1
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.  
 + 
 +Another service to take query requests for those who dont want to run a client that receives offer information. 
 + 
 +basic distinction: are the offer records(DNS) distributed or the search requests(gnutella)? far less traffic in distributing the offer records than distributing the search queries
  
-con: High latency for queries. 
  
 ===== Escrow Service (ES) ===== ===== Escrow Service (ES) =====
  
 +One party visits ES home page to define a deal. (Deal State: Defining) \\
 +The party provides: BTC amount description, USD amount description, Time limit. \\
 +ES provides: deal ID/url. (Deal State: Confirming)
  
-==== Plan ====+Party communicates deal ID/url to party B. (ok if this happens later on)
  
-Client A visits ES home page. \\ +Party A visits ES deal url. \\ 
-Client provides: BTC amount description, USD amount description, Time limit, indicates BTC will be provided \\ +Party confirms amounts by providing A's dwolla receiving address \\ 
-ES provides: deal ID, receiving BTC address+ES provides: ES's bitcoin receiving address
  
-Client A communicates deal ID/url to client B.+Party B visits ES deal url. \\ 
 +Party B confirms amounts by providing B's bitcoin receiving address. \\ 
 +ES provides: ES's dwolla receiving address.
  
-Client B visits ES deal url \\ +ES waits to receive BTC and USD. (Deal StateCollection)
-Client B provides: BTC amount description confirmation, USD amount description confirmation, receiving bitcoin address\\ +
-ES providesa dwolla address.+
  
-ES waits for BTC and waits for USD. \\ 
 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.
  
-==== Plan B ==== +(Deal State: Dispursement) 
- +ES skims transaction fee from BTC and/or USD. \\ 
-Client A or B creates deal, provides: BTC amount description, USD amount description, Time limit +ES sends remaining amount of BTC to client B and USD to client A.
-ES Provides: deal ID +
- +
-Creating client needs to communicate deal ID to other client. +
  
-==== Finally ==== +ES deal URL shows history of the deal.
-once both arrive,  +
-  * send BTC to client B and initiate dwolla transfer to client A. (skim transaction fee) +
-  * notify client A and client B of completed transaction+
  
bitcoin/federatedmarket.1312566461.txt.gz · Last modified: 2024/01/31 04:08 (external edit)