Financial services are nearly done client side and testing should begin Wednesday or Friday at the latest. One of the major changes is that the system is not fully decentralized. While the code for decentralization already exists, there is are major hurdles with regards to the following :-
1) Legal ramifications of offering decentralized services such as banking, financing and brokering.
2) Liability in the event of defaults or fly-by-night setups.
3) Arbitration of client-bank disputes
Initially I had intended to leave all this in the hands of users, but i have been warned that in some jurisdictions, I may be in trouble if things go south. So I am trying to work out ways to change the system such that i cannot be held responsible for the actions of others.
Each Service node was meant to service customers who sign up and maintain a local database which would periodically sync with third tier permanent nodes, to ensure there are un-altered copies of records. Then if a service owner made a run with the funds, there would be a record... but then how to totally prevent such a situation? I thought perhaps to have each node use 2/3 Multisig addresses for services, with the third key being stored on the third tier, much work involved and not sure if feasible. (If it works would be the best solution) and finally i thought of centralized solution, but then this makes me liable... i'm not interested in liability or centralization. So pending current work, i'll update this portion.
The crowdfund has been a failure. So tokens will be sold OTC. I will try get a write up of all the new functions introducing and explaining how services will function.
As i am a bit tired of this section, i will begin work on decentralized exchange and a centralized exchange interface.
