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:26] donpdonpbitcoin:federatedmarket [2024/01/31 04:08] (current) – external edit 127.0.0.1
Line 1: Line 1:
-== bid/ask database ==+===== 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.
  
-local generation of queries into the db for interesting bid/asks.+Clients can subscribe to a telehash channel and receive new offer information. Some 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.
  
 +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. 
  
-== escrow service == 
  
-client A provides BTC. clint B provides USD.+===== Escrow Service (ES) =====
  
-escrow service(ES) has bitcoin daemon and dwolla app registration.+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)
  
-client tells ES it is willing to use ES for a transaction with client B, finishing in a given amount of time, and provides a dwolla address. (half-open state)+Party communicates deal ID/url to party B. (ok if this happens later on)
  
-ES provides a transaction ID and a bitcoin address to client A.+Party A visits ES deal url. \\ 
 +Party A confirms amounts by providing A's dwolla receiving address \\ 
 +ES provides: ES'bitcoin receiving address
  
-client provides transaction ID (received from client A) and a bitcoin address. ES provides dwolla address.+Party visits ES deal url. \\ 
 +Party B confirms amounts by providing B'bitcoin receiving address. \\ 
 +ES provides: ES'dwolla receiving address.
  
-ES waits for BTC and waits for USD. +ES waits to receive BTC and USD. (Deal State: Collection)
  
-once both arrive,  +Client A sends BTC through bitcoin client. \\ 
-  * send BTC to client B and initiate dwolla transfer to client A(skim transaction fee) +Client sends USD through dwolla.
-  * notify client A and client B of completed transaction+
  
 +(Deal State: Dispursement)
 +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.
  
bitcoin/federatedmarket.txt · Last modified: 2024/01/31 04:08 by 127.0.0.1