3 ms·
Time for a cryptocurrency for F@H?
by nicwilson 9y ago
Time for a cryptocurrency for F@H?
- asfgionio 9y agoGridcoin is the biggest I'm aware of. Most people who mine it (that I've spoken to) think of it as a way of subsidizing their hardware and electricity, not as a get-rich-quick scheme. Since it lets you choose what project to work on, you can choose one that you approve of and that is well-suited to your hardware. I was considering buying some old servers to mine it. I'd have pretty much broken even back when it was $0.10/grc, but it would have taken me ages to make back my investment.
- tramGG 9y agoRelevant: https://golem.network/ https://golem.network/
- maaarghk 9y agoquick search reveals these: https://curecoin.net/ https://curecoin.net/ https://foldingcoin.net/ https://foldingcoin.net/ pretty cool idea! if you're going to do difficult maths for proof of work it might as well be useful I suppose?
- n-exploit 9y agoI was on the Curecoin team as of last year. It's a neat project, but they weren't able to manage a working relationship with Stanford. There is a unique opportunity here to use digital currencies to fund scientific research through the use of a reward mechanism and distributed ledgers. Our project is hoping to take a similar idea to scale (research/project-based "work) by utilizing open datasets posted on decentralized technology. We hope to build relationships with institutions, non-profits, and the public sector to track the economic and social value of campaigns similar to the Folding@Home and Seti@Home projects, but with a capacity to on-board projects as they appear. https://vitae.foundation https://vitae.foundation
- neuromantik8086 9y agoI suggest sending the leaders of aforementioned institutions/non-profits/public sector establishments a healthy dosage of LSD if you hope to persuade them to work with you.
- simias 9y agoThe problem of replacing the general purpose proof of work in cryptocurrencies (finding partial SHA256 collisions in the case of Bitcoin) with something more useful is that the attributes for a good PoW computation are hard to find in real world distributed problems. In particular you want something a problem with the following attributes: - must derive somehow from the block data you're trying to mine, otherwise you could reuse your work for an different block and make double-spend attacks trivial. It's very important that once a new block is mined everybody else must start from scratch for the next one, otherwise you could "premine" an arbitrary number of blocks and later append them at an arbitrary position in the block "tree", potentially rewriting history. - difficulty should easily be modifiable to account for the current "hashrate" otherwise your blockrate will go whack as the amount of computing power available changes. It also means that you should be able ahead of time to guess the difficulty of a problem and the average amount of processing power required to solve it. - easy to validate: the nodes of the network should be able to check that the proof of work is valid using a tiny fraction of the computing power necessary to actually produce the proof (finding hash collisions is hard, verifying them is comparatively trivial). - doesn't require access to a centralized resource. If you need to connect to some central repository to fetch the work set then not everybody is on equal footing. You have a single point of failure and some miners could have privileged access to the work data. It's very difficult to find real world problems that have all these attributes.
- nicwilson 9y agoIt wansn't a particularly serious suggestion, but thanks for the explanation.
- simias 9y agoOh I took it very seriously because it's something I've given quite a lot of thought. I'm not a huge believer in cryptocurrencies but I would be a lot more optimistic about them if they weren't wasting so much energy. Harnessing all that processing power to do something useful would be amazing. Unfortunately so far the most useful PoW people have manage to implement are things like "compute very large prime numbers" which I suppose is mildly more useful than finding SHA256 collisions but not by a very large margin.