[tahoe-lafs-trac-stream] [tahoe-lafs] #1408: accounting using bitcoins

[tahoe-lafs]

#1408: accounting using bitcoins
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  somebody
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  undecided
     Priority:  major    |    Version:  1.8.2
    Component:  code     |   Keywords:  bitcoin accounting performance
   Resolution:           |  leases security
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 > Open questions:
 >
 >  * who/what decides the rate at which bitcoins are used to pay for
 storage? (Perhaps each storage server can advertise its own rate, and that
 is one input to a more sophisticated server selection algorithm? But that
 sounds conplicated for an initial implementation.)

 Perhaps we can reimplement
 [https://secure.wikimedia.org/wikipedia/en/wiki/Mnet_%28peer-to-
 peer_network%29 this idea from MojoNation]:
 > In early versions of !MojoNation, users were required to set prices for
 any services their node provided. Most users had no idea how to choose
 prices, so the Mojo layer was rewritten to use a second-price rolling
 auction. Each node maintained a queue of incoming requests that had not
 yet been processed, sorted by a bid field contained in each request.
 Requests were serviced in order, from highest to lowest bids. This shifted
 the burden of pricing decisions from servers to clients: each user could
 set a price he was willing to pay for services, and his node would offer
 that bid in outgoing requests. This scheme was intended to create a simple
 feedback loop: if the system is responding slowly, increase your bid and
 if the system is responding quickly, decrease it.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1408#comment:3>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage