Yeah, I think this is the best idea so far. That way as long as there is one person who is online they can act as a server to start with. As the community grows it will be more distributed.
If private/public key signing was used then we can guarantee who made the offer and who accepted the ofefer. For example an accepted offer can be timestamped so that whenever somebody.accepts an offer that has already been made the accepted offer is rejected.
Ideally the objective is for a critical mass of nodes are always online making sure the orderbook is always up-to-date.
Is there anything I can do to help out, morpheus?
There will be some issues in the details of making sure everyone has an up to date list of all offers, and keeping the data clean. I can think of a few now, but once I start implementing it, I'm sure more will come up.
I think there will be some issues keeping time on the network synchronized if we try to base everything on a timestamp. Plus, more than one person can accept an offer at the same time anyways. Though, I don't think it matters, since the one making the offer can choose which trade to fill in the end.
I don't remember your skill set Sultan. Can you program? Do you know Java? Do you know Clojure?