Skip to content

Is there a planned payment mechanism for storing cxo? #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vidya88 opened this issue Sep 19, 2019 · 4 comments
Open

Is there a planned payment mechanism for storing cxo? #7

vidya88 opened this issue Sep 19, 2019 · 4 comments

Comments

@vidya88
Copy link

vidya88 commented Sep 19, 2019

@steadyclackin commented on Jan 27, 2018

I could see such a mechanism powering basically a global network file store. I.e. something really really useful. It could come with replication controls so that the owner can choose the desired replication (paying whatever the rate is for the amount of data that results). Pay more to have more guarantee that the data won't be lost, etc. In this manner skycoin could not only be asset-backed by bandwidth capacity but also asset-backed by storage capacity.

@vidya88
Copy link
Author

vidya88 commented Sep 19, 2019

@steadyclackin commented on Jan 27, 2018

I think such a system would incentize content hosting on the network, since hosts would be compensated both for storing and serving it (the latter being true only if i understand the bandwidth compensation system correctly, not 100% sure tho).

@vidya88
Copy link
Author

vidya88 commented Sep 19, 2019

@vidya88
Copy link
Author

vidya88 commented Sep 19, 2019

@steadyclackin commented on Jan 29, 2018

neat. is there any more info besides a marketing release? :)

@vidya88
Copy link
Author

vidya88 commented Sep 19, 2019

@logrusorgru commented on Jan 29, 2018

No, there is not. I can't help. The SPARCO is separate project. Sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant