What is Project Rain?
'Project Rain' is the practice of distributing crypto assets to BOINC users based on their verified BOINC computation; it was initially devised within the Gridcoin network and has been expanded to multiple cryptocurrencies and all BOINC teams through this BOINC project.
Through this BOINC project, you will be able to match a user's BOINC CPID to their multiple crypto asset addresses/accounts to which you can distribute your asset against.
Think of Project Rain as a new share-dropping vector that doesn't require end-users handling wallet private keys nor providing proof of IRL identity.
What is exciting about project rain is that there are currently over 500,000 active BOINC users and 4 million total registered BOINC users to whom you could potentially distribute your choice of asset.
What are the recent updates?
- The repo has been uplifted to use the latest BOINC server code; this was required because the BOINC devs migrated the web server to using the Bootstrap library.
- Optimized implementation (easier to fire up with less steps).
TODO
- Add additional cryptocurrencies (please request the cryptos you want integrated).
- Improve how cryptocurrencies are displayed within the profile (if subtle enough, perhaps we could get these changes integrated into the core BOINC repo..)
- Investigate & document the distribution of docker containers as work units.
- Investigate how to make BOINC Database data persistent across container resets (given that if the container is reset it loses all data).
- Your suggestions!
What cryptocurrencies are currently supported?
Gridcoin, Steem, Bitshares, Peerplays, Storj, NEM, IBM Bluemix Blockchain, ColoredCoins, Antshares, Lisk, Decent, Synereo, LBRY, Wings, BoardRoom, Ethereum, Ethereum Classic, Expanse, Golem, NXT, Ardor, Hyperledger Sawtooth Lake (Intel), Hyperledger Fabric (IBM), Waves, Peershares, Omnilayer, CounterParty, Hyperledger (MISC), Stratis, Metaverse, Cosmos, Stratis, Zcash & Heat Ledger.
Is there a mandatory team requirement?
There is no mandatory team requirement for joining the website, all BOINC teams/users are welcome to join!
Assets may however be distributed by rain makers to specific teams since they have full freedom of choice to do so & there's no site interference on the matter.
Who decides upon asset distribution details?
The 'rain maker' planning on 'raining' an asset is fully responsible for picking the projects and/or teams to target as well as the desired 'rain weight' for each project. The 'Project-Rain' BOINC project admin has no input on who/what gets 'rained' upon.
Are supported cryptocurrencies endorsed by 'Project Rain'?
Project Rain has provided the ability for users to match their BOINC CPID to multiple cryptocurrency addresses/accounts, but this does not constitute financial advice nor endorsement of supported cryptocurrencies.
Several of the supported cryptocurrencies are yet to be released, are in development or are planning ICO phases - be very careful & don't invest money you can't afford to lose (cryptocurrencies are incredibly volatile). Seriously consider consulting with financial advisors before making financial decisions.
Are 'rained' assets endorsed by 'Project Rain'?
Assets distributed via the ‘project rain’ share-dropping vector are not by default officially endorsed by this website unless otherwise stated.
Are fees charged for this service?
The Project Rain website does not charge fees. You'll likely have to pay a large fee to distribute your asset on your cryptocurrency platform of choice to handle the scale of the Project Rain distribution (thousands of receipients). Please do consider donating to help cover server costs.
Can I contribute to the development of project-rain?
Yes, you certainly can! https://github.com/grctest/project-rain-site
I would really appreciate help finishing the 'rain tutorial' page: https://github.com/grctest/project-rain-site/blob/master/source/rain-tutorial.html.erb (I need specific info for how to create the equivalent of a 'sendmany' transaction to potentially tens of thousands of BOINC users on your crypto network platform).
I would also appreciate input on address validation for the planned supported cryptocurrencies, some which do not have completed documentation I have provided 254 field length despite likely requiring far less (or perhaps may require larger fields):