**This is an old revision of the document!**
Table of Contents
Bid/Ask Federation
A distributed database(ala gnutella) of asks/bids
Queries are generated locally and communicated into the nework. matching asks/bids are sent to the query origin.
con: High latency for queries.
Escrow Service (ES)
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.
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.
The party provides: BTC amount description, USD amount description, Time limit.
ES provides: deal ID/url.
Party A communicates deal ID/url to party B. (ok if this happens later on)
Party A visits ES deal url.
Party A confirms amounts by providing A's dwolla receiving address
ES provides: ES's bitcoin receiving address
Party B visits ES deal url.
Party B confirms amounts by providing 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.