Thanks, Let me then repeat and please confirm or extend my list:
Situations where a user could not be able to access uploaded files,
- when enough blobbers fail in the EC ratio
- when user forgets the private key of the wallet
- when user forgets to renew the subscription fees before expiry date
Do you have any more to add?
I have still questions to the points above:
- the EC ratio failure: here I refer you back to our chat in 0Box-Data Availability questions about losing and recovering data
This EC ratio failure should be totally prevented by your protocol in a way that your network constantly monitors and automatically replaces failed blobbers whenever EC-ratio-failures occur.
It should not even come to this situation,
the network should automatically replace failed EC ratios to prevent data losses, because it is not your customer’s fault when blobbers in the EC fail !.
I don’t understand what is difficult with this, every other storage network does that, centralized or not. Please prioritize this soon in your features roadmap @saswata
Can you always recover your data and your wallet when you still know your private key from any other computer of mobile phone?
failure to renew allocations, can you explain in more detail: What happens to my uploaded files in your network when I forget to renew in time?
Isn’t there any kind of extension period?
Are the files lost forever on the second the expiry date kicks in?
What happens to the uploaded files in the network?
Any way to recover them even when you missed the timely allocation?
Please here again introduce some automatic mechnism to take off work from the user. To prevent such cases where users forget timely allocation.
For example let users stake/pay in advance for their desired period of time,
or, make your protocol take away a sufficient amount of ZCN tokens automatically from user’s wallet (when there is sufficient amount available) , from those users who forget to manually renew
Please think of something