Proper MaidManager account entry creation

Yes, seems I have misread the RFC and un-authorised put is removed, i.e. option 2 is no go then.

I think in this sprint all we do is allow all `Put`s so where we will check safecoin balance in safecoin sprint at the moment this returns true.

I think you are perhaps misreading the RFC, the unauthorised_put is shown only as a failure of the design of requiring ID packets and replacing with public_key identifiers removes that failure.

So far, there are two options to make such allowance setup more realistic:
1, burning safecoin : client needs to burn a safecoin, i.e. PUT a safecoin type SD to network, updating it's owners to NONE(or network?). This can also be used for later on TOP-UP the allowance by burning. Two things are currently missing to achieve this method:
a, convert rate from safecoin to space
b, a fetch of SD from MaidManger to SDM to verify the ownership

2, According to rfc https://github.com/maidsafe/rfcs/blob/master/active/0001-Use-public-key-for-id-on-all-messages.md, client needs to use un-authorized put first before can put anything to the network. I am just wondering can that un-authorized put be used to pass some other info as well to MaidManager to setup the allownace. However, this methods still require something later on to top-up allowance.