Gridcoin Community Hangout #021 - 07th Jan 2017 @ 9PM GMT (RSVP & Suggest topics!)
Gridcoin Community Hangout #021
A massive shout out to the BeyondBitcoin community & @officialfuzzy for providing the Gridcoin community a room in their mumble server for free.
Another massive thanks to @peppernrino for editing the hangout recordings! Follow him on Steem! :D
What is Gridcoin?
Gridcoin securely rewards BOINC computation on top of Proof of Stake. Reward allocation is distributed, not centralized unlike other distributed computing related cryptocurrencies.
Where can I listen to past hangouts?
 |  |  |  |
|---|
Past episode details
020 RSVP & Topic suggestion thread
Why are we holding these hangouts?
- A mumble conference call can provide significant advantages over communicating via forums and IRC.
- To create opportunities to inform the public of new Gridcoin, BOINC and related services & their development progress.
- To bridge relations between the cryptocurrency & BOINC communities.
How long will the hangout last?
If there are not many topics suggested then hangouts won't last longer than an hour, on the other hand if there are many topic suggested then the hangout may last 2-3 hours!
When the Gridcoin Community Hangouts start really picking up traction we can become more strict with allocated speaking time if need be (so you're not waiting hours to talk).
Want to suggest a topic to discuss?
Reply with your suggestions in this Steem post & order of discussion will be from highest to lowest voted suggestions.
Can we discuss anything?
It's advisable to stay generally on topic, attendees are distributed around the world so they may not (likely won't) share the same views regarding controversial topics not related to Gridcoin/BOINC/Cryptocurrency.
That said, this 'on topic' guideline fizzles away once official recording has ended & the hangout becomes a more relaxed environment.
Proposed time for Gridcoin Hangout #018:
9PM GMT 07th Jan 2017.
Compare 9PM GMT to your time zone!.
How to join the Gridcoin hangout
Step 1: Download Mumble. [Windows Client, Android Client]
Step 2:
Step 3: Configure Mumble & join the server!
Label: BeyondBitcoin - Gridcoin
Address: mumble.beyondbitcoinshow.com
Port: 64738
Username: Enter your username
Password: w0rldCh@NG3rsUN!t3
Step 4: Join the Gridcoin channel!
Step 5: Configure your audio wizard & setup Push-To-Talk. Join 10-15 mins before the hangout starts to test your audio configuration.
I hope you decide to attend the hangout - everyone is welcome to join, especially those who suggest topics of discussion in this thread.
Best regards,
CM.
team challenges in January:
review past ones: MOO WRAPPER, ENIGMA
upcoming ones: https://steemit.com/gridcoin/@erkan/help-team-gridcoin-in-the-january-2017-challenges
a new faucet is available
https://steemit.com/gridcoinstats/@sc-steemit/gridcoinstats-faucet-backed-with-rewards-from-a-stable-community
invitations accepted by BOINC admins to speak in mumble:
TN-Grid
(yoyo)
exact dates/times have to be still arranged
Foundation expense poll for sponsored funding of Gridcoinstats Faucet
I think this is a bad idea. Faucets are to be user-funded. Way too easy to abuse... and it's been suggested before. I think using foundation funds to get new users off the ground is an idea fraught with perils no one seems to be thinking about. I know your heart is in the right place, but we have to admit hard facts sometimes. Look at what's transpired with irpg... people can't help but take advantage of things like this, and it's sad, but real.
If people want to donate to a faucet for noobs to sip from, that's fine.
But, having a pre-determined limitless supply is just asking for trouble.
I think the gridcoinstats faucet is less vulnerable to abuse than irc bots.
I support the idea of funding the faucet, on a small scale.
main dev Rob has started a roadmap (2017-2019), please review/contribute:
https://steemit.com/gridcoin/@erkan/gridcoin-roadmap-2017-2019
BOINC Project whitelist guidelines/checklist - requesting peer review and suggestions:
https://cryptocointalk.com/topic/51660-requesting-peer-review-boinc-project-whitelist-guidelineschecklist/
GRC getting missed out of Techcrunch's recent article: https://techcrunch.com/2016/12/27/how-blockchain-can-create-the-worlds-biggest-supercomputer/
Recent reduction of RAM requirements and where I want to take the data structure inside the wallet: https://github.com/gridcoin/Gridcoin-Research/pull/160#issuecomment-270059244
In my utopia we would have the block chain stored in the wallet as an SQLite database. Instead of keeping the entire, growing blob in RAM we would query the DB as needed.
polls in January:
4 whitelist polls:
removal: BURP, CPDN ?
add: TN-Grid, Drug Discovery ?
13 casual polls
https://steemit.com/gridcoin/@erkan/gridcoin-polls-january-2017
There has been recent discussion regarding the team requirement in the announcement thread:
https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1208
https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1209
https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1210
https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1211
https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1212
I think we've to understand in the whole discussion:
Rob is against removing team requirement, and he'd be currently the only one to actually implement it.
Besides his preference, he also listed probs of that being implemented already. As long as we don't get more devs (and I hope Rob would accept then the pull request also) the situation won't change.
New devs need time to understand; the implementation of the change probably will bring unexpected probs, which also costs time to fix; ... <- I don't expect the feature to come that soon
Personally, I am also for the team requirement to stay.
Thus far, Rob has responded to the topic once in the last few months - continuing to discuss the topic rather than shutting it down based on an initial post is healthier for the community.
Just because it isn't something that's possible in the immediate future doesn't mean it should be dismissed entirely.