r/gridcoin • • Feb 18 '22

Gridcoin Mining/Crunching Guide and FAQ 2022

138 Upvotes

If you are new to Gridcoin, you may be wondering how you can use your computer's spare processing power to earn some GRC. Whether you are new to the cryptocurrency in general or an experienced crypto miner, this guide will provide you with the information you need to get started.

You do not need to mine/crunch Gridcoin to use it or even to get your hands on your first few GRC. Thanks to the generosity of our community, you can get free GRC from several faucets. You can also get staking rewards just for holding GRC in your wallet. You can, of course, also just buy GRC outright through exchanges as well. Please see our general guide/FAQ for more information about these options.

What is mining? Crunching?

Mining is a term used among Proof-of-Work currencies such as Bitcoin, Litecoin, and Monero. In mining, you spend your computational power trying to guess the answer to a mathematical puzzle and in doing so, you provide the security for the network. When you guess correctly, you are given some currency in exchange for your work. This is a very energy intensive process, and has no use outside of securing the network. As of 2022, Bitcoin has the same energy footprint as the entire country of Argentina, for example.

Because Gridcoin is a proof-of-stake system, no mining is required. It uses less than .01% of the energy used by traditional proof-of-work coins and uses people staking coins on the network to secure it (this is how you earn staking rewards).

As part of it's financial model and protocol, Gridcoin issues new coins to "crunchers" - people who volunteer their computing power towards various scientific research projects in the BOINC network and Folding@home. These projects tackle some of humanity's most pressing problems. Which projects are incentivized with GRC is determined by votes in network-wide polls. You pick which projects you want to crunch. You could cure a disease, help map asteroids, or make more accurate climate models, it's all up to you!

With traditional cryptocurrencies, miners spend their computational power calculating math puzzles and get rewarded. In Gridcoin, crunchers spend their computational power on scientific research and get rewarded. You spend computational power to get coins either way, but with Gridcoin, you also contribute to the progress of science.

What kind of computer do I need to crunch?

You can crunch on every OS (Windows, Mac, Linux, etc). The newest and faster your computer, the more GRC per day you can earn, and GPUs (fancy graphics cards) can earn more than CPUs. But any computer will work. Even a Raspberry Pi can crunch!

You can crunch on as many devices as you want.

How do I get started crunching? (Solo Crunching w/ MRC)

Check out this easy video guide to get started. In short, you must:

  • Download BOINC and attach to project(s) you want to crunch, making sure you enable GDPR/project stats export for those projects which require it. See the list of approved projects to check if your project does. You can crunch as many projects as you want, all projects must be signed up using the same e-mail address. Using an account manager like BAM can help simplify signing up for multiple projects or assigning different project/work preferences to different machines. When creating accounts through BAM, all accounts will be created with the same e-mail.

  • Download the Gridcoin wallet from gridcoin.us and run the solo crunching wizard which will make a beacon for you and direct you to change the username at one of your BOINC projects (one is all you need to change) to verify you really own that account. This will take <1GRC which you can get for free from our discord server, by using a faucet, or by by using an exchange. If you have this GRC but receive an error that there are "insufficient" GRC to make a beacon, the GRC you received is probably new and you must wait a half hour or so for it to complete a cooldown before those coins can be used. Your beacon will take up to 48 hours to verify, after which point you should start accumulating rewards. Your rewards will continue to increase for around a week as your RAC (recent average) ramps up.

  • You can crunch on as many device(s) as you want, only one should run the Gridcoin wallet. Just make sure all device(s) crunching are connected to BOINC project(s) using the same e-mail address. The machine with the Gridcoin wallet must have BOINC attached to all projects you crunch, but if you don't want that machine to actually crunch, you can set each project to "no new tasks" in BOINC manager's advanced view.

  • As accumulated rewards build up (shown in wallet), you can claim them by staking a block or using the MRC ("manual reward claim") feature to have somebody else stake the block and claim the rewards for you on demand. The fee for this decreases over time, so the longer between MRC claims the cheaper. As you obtain more GRC, your "average time to stake" will decrease so eventually you will just stake automatically without any fees and there will be no need to use MRC. On average, without about $50 USD of Gridcoin in your wallet, you would automatically stake once a month if your wallet is online 24/7. Staking can only happen automatically if you wallet is left open and you are connected to the internet. Staking is based on averages, so sometimes you will go through dry spells and sometimes you will stake more often than "expected".

  • Note: If you want to crunch Folding@home, you must download BOINC and connect to at least one BOINC project as you need to obtain a "CPID" to put into your Folding@home username. Follow the "solo crunching" guide here as usual, then come back to this note to finish the Folding@home setup. Note that when prompted in the solo crunching wizard, you must change your username at a BOINC project to verify your beacon. In order to be assigned a CPID and verify the beacon you must earn a negligible amount of credit at a BOINC project by completing one work unit. This will take up to several hours depending on the project. Remember as noted in the solo crunching tutorial that some projects require enabling a setting to export your stats (GDPR). After that, there is no need to crunch BOINC, you can set BOINC projects to "no new tasks" in advanced view on BOINC manager. To get credit for your folding@home work: change your Folding@home username to username_GRC_CPID with username being whatever you want it to be, and CPID being the CPID the wallet solo crunching wizard shows. Note GRC must be ALL CAPS. You are encouraged to setup a passkey for your folding@home account (as you get more rewards) but it is not required.

  • We also encourage you to join the Gridcoin team on each project you are attached to, but it is not required.

Which projects should I crunch? How do I maximize my earnings?

You can pick projects which you find interesting or valuable, pick projects which will get you the most reward, or do some combination of both. Not all BOINC projects will earn you rewards from crunching, only those on the approved projects list/whitelist will. You can sign up for one, two, or all of them! I would suggest at least two, so that if your main project runs out of work temporarily, your computer will still have one to work on.

You can get a rough estimate of what you might earn with your CPU/GPU combination using Quickmag. Note that Quickmag is unable to list all projects due to some projects not exporting the correct kind of stats. If you have been crunching for more than a week, you can also use FindTheMag to get suggestions based on your machine's actual performance.

Generally speaking, medical research projects tend to pay less than math or physics projects, because more people want to crunch them and therefore there is more competition. In the same way, if you are crunching with a CPU only, projects which support GPUs will be reward less because GPUs are much more efficient at some kinds of problems than CPUs.

Will I actually make money crunching?

You will definitely earn GRC. How much money you make crunching depends on your costs (hardware, electricity, and pool fees if any) and GRCs current value (or if you hold onto it, the value you sell it at). Unlike with "mining" proof-of-work coins, where profit is the only thing you can earn as a result, when you crunch for GRC you are also supporting worthy scientific research, so we like to say that it's never truly a loss! There are people who crunch GRC at a profit, doing so means keeping track of what the most profitable projects are and adjusting your crunching accordingly.

Is crunching bad for my computer? Will it overheat?

The short answer for desktop computers is no. Crunching will not harm your computer, computers after all are designed to compute! While crunching does utilize your CPU/GPU heavily, the reality is that every other component in your computer will likely fail first (your hard drive, OS, etc) or become obsolete before your CPU dies. Many computers crunch for a decade plus with no issues, at which point they make most sense to replace from an energy perspective alone.

However, if your machine has a pre-existing problem with heating (like if it's full of dust or running inside a cabinet), crunching can exacerbate this problem or make its symptoms more readily visible. Modern CPUs are designed to throttle and turn off if the heat becomes too high, but for longevity it is best to stop them from getting to this level in the first place. You should be removing dust from your computer's fans every 6-12 months depending on your environment. Making sure your computer is not on the floor or carpet will also help greatly with dust accumulation. Here's a video documenting the basics of dust removal, be sure to do it outside and wear a dust mask or other respiratory protection to keep yourself from inhaling all the dust.

Generally speaking, a CPU under high load shouldn't be higher than the mid 80s in Celsius. You can monitor your CPU temps with a tool like Open Hardware Monitor. If you are cleaning out your case regularly and your computer seems to be running fine, you don't need to keep an eye on temps. I don't monitor mine, for example. If you research what "safe" temps are online, you will see widely differing opinions. This is partially from people who do not know what they are talking about, but also because CPUs can have wide temperature ranges in their official documentation.

Laptops, on the other hand, are often built with insufficient heat exhaustion and can quickly overheat at full load. Heat will also shorten your battery life significantly. Setting BOINC to only use 50% of your CPU power and not to use your GPU will keep heat manageable. Be sure to regularly clean dust out of your vents just like with a desktop PC, you can use a pen to hold the fans in place while blowing the dust out. With laptops, remember that warm is fine, hot is bad.

While BOINC does have an Android app, it is widely considered a quick way to kill your phone. It has no good way to manage heat, phones are not designed to be run at 100% all the time, and can quickly lead to swollen and dangerous batteries. I do not suggest crunching with Android.

Will crunching slow down my computer?

You can configure BOINC to only run while your computer is idle, which means it won't slow anything down while you're using it.

If you are feeling brave, you can also set it to only use a certain % of memory or cores to leave it running while the computer is in use if you want. BOINC runs at the lowest priority, so it won't slow down tasks using your CPU, but if you run low on memory then it may impact performance while you're using the machine.

What is Magnitude (MAG)? RAC? How does CPU power turn into GRC?

The path from CPU power to GRC is a bit complicated to wrap your head around at first, and luckily, you don't actually need to understand any of it to crunch and receive GRC rewards. Broadly speaking, your rewards are based on a running average of the work you have contributed to all projects, so starting from zero, it will take around a week to start getting awarded the maximum amount of GRC your hardware can provide.

But since you asked, here's how it works.

  • A total amount of "magnitude" (MAG) is allocated to all projects. Each project gets the same amount of magnitude. These aren't the actual numbers, but for simplicity's sake we'll assume there is 100 MAG and 10 projects so each project has 10MAG allocated to their crunchers. For every 1 MAG, .25 GRC are minted.

  • Each project assigns you credits for your work, and a rolling average of your credits is created called RAC. The RAC of each cruncher is published by the projects.

  • The Gridcoin Protocol downloads this RAC data using a system of federated oracles (scrapers). Gridcoin has one of the few, functional federated oracle systems in the blockchain world because 👏 our 👏 developers 👏 are 👏 awesome.

  • From this RAC number, your MAG is calculated. Your MAG is proportional to your amount of the total RAC from other Gridcoin crunchers on the project. So on project X if there is 100 MAG to give out, and you had 10% of the RAC, you would receive 10% of the MAG or 10 MAG.

  • Your MAG is added from each project to get your total mag, and you receive this many GRC divided by four. So 1 mag means you get .25 GRC.

  • Note that projects do not do anything aside from publish stats. The GRC is minted and distributed by the protocol all without the projects having to do anything.

  • This process happens once daily, so your GRC per day will fluctuate based on your RAC/MAG calculations each day.

Here's some example of how this works out.

  • There are 100 MAG total and five projects, so each have 20 MAG to distribute.

  • On project 1, you are the only Gridcoin cruncher, so you get all the mag, so your running total is 20 MAG.

  • On project 2, you had did half the crunching and therefore had half the RAC, so you get 10 MAG for a new running total of 30 MAG.

  • You didn't crunch the other projects at all, so your total is 30 MAG, which means you are minted 7.5GRC (30/4)

I've been crunching forever, can I get retroactive rewards?

Gridcoin does not issue any retroactive rewards, only rewards for contemporary crunching.

What about cross-mining? Is GRC the only coin I can earn this way?

If you are crunching Folding@home, you can earn /r/curecoin at the same time. If you are crunching World Community Grid, you can also earn Obyte for your work at the same time. Once you sign up with Obyte, you will continue to accumulate it even if your Obyte wallet is not open. Obyte is no longer rewarding WCG work.

Can I use an account manager like BAM for crunching?

If you are doing pool crunching, no, because the pools themselves are account managers. If you are solo mining though, absolutely, and they may simplify your BOINC project account sign-up/management process.

Am I required to be on the Gridcoin team in BOINC?

We used to require this but no longer do. You are encouraged to join the Gridcoin team though, it helps us bring new people into the project and show the impact Gridcoin can make.

How come I'm not seeing any pending rewards?

It will take a few days of crunching to start seeing rewards. After that:

  • If you are a pool cruncher and see no rewards, your BOINC client is probably not crunching under the pools account. In BOINC, go to the advanced view and go to Projects. Each project should be attached to the Pool's account, if it's not, restart the pool setup guide to get everything setup correctly.

  • If you are solo cruncher, you probably have not enabled GDPR export. Some projects require that you login and consent to your stats being exported (so that Gridcoin can see them), a list of projects that require this and how to do it is available on the whitelist page. It's also possible that your project has been temporarily greylisted, see the researcher tab in your wallet to check.

Does my wallet need to stay open for me to receive research rewards?

Pool crunchers: No

Solo crunchers: Your "pending rewards" will continue to accumulate if your wallet is closed, but you will not be able to claim them until you stake a block which requires leaving your wallet open to do. MRC (having somebody else stake a block for you for a small fee) does not require your wallet to remain open after making the request. Leaving your wallet open does help provide security to the network and increases your chance of staking, so it's best to leave it open as much as you can.

How much energy does crunching take? How much does electricity cost?

Most of your PC's energy is consumed just by virtue of it being on. There is a difference between "on" and "full blast", but it's less than you'd expect. A standard desktop PC takes around 40-60W of power and would cost around $5/month to run in the US if you kept it running 24/7, or about the same amount as a 20" box fan. If we assume your computer would be on half the time and now you're leaving it on all the time for crunching, that's a $2.50 difference. A GPU might add 2-3 dollars to that. If you live in a cold climate, the heat generated by your computer can help offset your heating costs and in some situations running your computer becomes free thanks to the law of the conservation of energy. Physics is pretty cool.

Does crunching BOINC with Gridcoin rewards use more energy/CPU than crunching BOINC alone?

No. The only additional thing required to get Gridcoin rewards is the Gridcoin wallet (if you are solo crunching), which is no more CPU or energy intensive than an e-mail client.

Why isn't my favorite project on the whitelist?

In order to be on the list of approved projects, a project must meet certain criteria. They must have a large, constant volume of work (so every cruncher has an opportunity to participate), they must reward that work fairly (no cruncher should be able to game the system), and the project must agree to be incentivized by Gridcoin. Plus, the project must be approved by a community poll on the Gridcoin blockchain. Gridcoin has approached every major BOINC project, so if your project is not listed, there is probably a good reason for it.

Why is my favorite project on the greylist?

Projects get greylisted for a number of reasons, most commonly that they run out of work or have too much server downtime. The Gridcoin twitter is a good lower-volume place to hear the latest about this, or right here on reddit!

I have another question or I'm stuck, or confused where can I get help?

No problem, crunching can be confusing to do at first! Our discord server is probably the easiest and fastest way to get help, just jump on the #help channel and say hello. Everybody answering your questions will be a volunteer, taking time out of their day to help you, and they're happy to! Please check the Gridcoin website and do your best to answer the question before asking it, letting people know you have tried to solve it yourself but got stuck will increase the chance that somebody will volunteer to help and helps prevent volunteer burnout.

Can I use Gridcoin w/ NiceHash?

Nicehash doesn't natively support Gridcoin, but a third-party service does enable you to earn GRC by using NiceHash. Note that if you do this, you will not be computing for science projects, you will essentially just be selling hashpower like you normally do with NiceHash, but getting paid in GRC.


r/gridcoin • • Mar 16 '18

A tour of the Gridcoin wallet

86 Upvotes

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.

Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.

This is my first post like this, so please forgive me if this appears a little scatter-brained.

This will not cover the mining setup process for pool or solo miners.

When you launch the wallet software for the first time you should be greeted with this screen.

  • If you're a pool miner or investor, press cancel.

  • If you're a solo miner, enter your email you used to sign up for projects and press OK.

  • If you're not sure or haven't decided yet, press cancel. We can come back to this later.


OVERVIEW TAB

After that prompt, you should be left sitting on the main overview tab with several fields on it.

From top to bottom:

  • Available: All coins available to be sent or staked (I'll cover this term later).

  • Stake: All coins that are currently staking.

  • Unconfirmed: All coins that have been received and have not yet received 110 confirmations.

  • Total: All coins in your wallet. (The sum of the above fields)

  • Blocks: How many blocks your client has in it's chain. Your wallet just started syncing with the network so this number will be low.

  • Difficulty: How difficult it is for someone to stake the next block.

  • Net Weight: An estimate for how many coins are staking on the entire network.

  • Coin Weight: How many of your coins that are currently staking.

  • Magnitude: A quantifier for how much work you put in mining. For solo miners only. For pool miners, this value will always be 0.

  • Project: Displays the projects you're working on, one at a time. For solo miners only. For pool miners, this will always say "INVESTOR".

  • CPID: Cross Project Identifier. Used to keep track of users across projects. For solo miners only. For pool miners, this will always say "INVESTOR".

  • Status: Displays various status messages.

  • Current Poll: Displays the latest poll.

  • Client Messages: Displays various client messages.


SEND TAB

Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:

  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.

  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.

  • Message: Enter a message here if you want it attached to your transaction.

  • Amount: How many coins you want to send.

  • Add Attachment: Leave this alone, it is broken.

  • Track Coins: This doesn't do anything.


RECEIVE TAB

Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.

  • New: Generate a new address.

If you click on an address, the rest of the options should be clickable.

  • Copy: Copy the selected address to your clipboard.

  • Show QR Code: Show a scan-able QR code for the selected address.

  • Sign Message: Cryptographically sign a message using the selected address.


TRANSACTIONS TAB

The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.


ADDRESS BOOK TAB

The Address Book is where all the addresses you've labeled (that aren't yours) will show up.

  • Verify Message: Verifies a message was signed by the selected address.

The rest of the functions are similar to the functions on the Receive tab.


VOTING TAB

Onto the Voting tab. There wont be any polls because we aren't in sync yet.

  • Reload Polls: Pretty self-explanatory, I've never had to use this.

  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.

  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)

Here's what the Voting tab will look like once you're in sync


CONTEXT BAR

Now onto the context bar menus on the top.

Under File you have:

  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.

  • Export: You can export your Transactions tab or Address Book in CSV format.

  • Sign message: Does the same thing as on the Receive tab.

  • Verify message: Does the same thing as on the Address Book tab.

  • Exit: Close the wallet.

Under Settings you have:

  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)

  • Change Passphrase: Allows you to change your encryption password.

  • Options: Opens the options menu. (We'll come back to this)

Under Community you have:

Under Advanced you have:

  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)

  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.

  • FAQ: Don't touch this, It is broken.

  • Foundation: Don't touch this, It is broken.

  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.

  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.

Under Help you have:

  • Debug window: Opens the debug window. (We'll come back to this)

  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.

  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.


OPTIONS

Now back to the options menu under Settings > Options.

Here we have the options menu main tab:

  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.

  • Reserve: You can reserve an amount so that it will always be available for spending.

  • Start Gridcoin on system login: Pretty self-explanatory

  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.

On the Network tab:

  • Map port using UPnP: Attempts to connect to nodes through UPnP.

  • Connect through SOCKS proxy: Allows you to connect through a proxy.

The window tab is pretty self-explanatory.

The Display tab is also pretty self-explanatory, with the exception of:

  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".


ENCRYPTING YOUR WALLET

Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.

Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.

Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.


GETTING IN SYNC AND ICONS

Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.

This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.

The lock

The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.

The connection bars tell you how many connections to the network you have.

The check tells you if you're in sync.


WHAT IS STAKING?

Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.

Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.

Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.

In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.

Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.


UTXOS AND COIN CONTROL

At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.

First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.

Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?

Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.

All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.

How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.

Now pay attention to the fields on the top:

  • Quantity: The total amount of UTXOs we have selected.

  • Amount: The total amount of coins we have selected.

  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)

  • After Fee: Amount - Fees.

  • Bytes: How large the transaction is in bytes.

  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.

  • Low Output: If your transaction is less than 0.01 coins (I think).

  • Change: What you will get back in change.

  • custom change address: You can set the address you get your change back at, by default it will generate a new address.

So let's fill out our transaction so we end up with 1 UTXO at the end.

In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.

Notice how we get no change back.

Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".

Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.

(Ignore the first one, that was me fragmenting my wallet)

Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.

Now why would you want to use coin control?

2 Situations:

  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.

  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.

  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.

Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.


FORKING

A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.

How do I know if I'm on a fork?

Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.

You can confirm this by comparing your blockhash with someone elses, like a block explorer.

Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.

Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.

This will spit out a crazy string of characters, this is the "blockhash" of that block.

Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.

Now compare your hash with the one gridcoinstats gives you. Does it match?

If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as gridcoin.network or neuralminer.io.

If it doesn't match, then you need to try to get off that fork.

How do I get off a fork?

  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.

  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.

  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.

  4. Use Advanced > Download Blocks.

  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.


CONFIGURATION FILE

Your configuration file depends on your operation system:

  • On Windows: %appdata%\GridcoinResearch\

  • On Linux: ~/.GridcoinResearch/

  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/

And it should look like this.

If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".

Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.

A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.


RUNNING A LISTENING NODE

A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.

Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.

If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".


QUICK LINKS

Gridcoin.us Official Website

Gridcoin.science Unofficial Website

Gridcoinstats.eu Block Explorer

NeuralMiner.io Block Explorer

Gridcoinstats.eu Faucet

Gridcoin.ch Faucet

Gridcoin Wiki

Gridcoin Github

GRCPool

Arikado Pool


And that's all I have for now!

I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!


r/gridcoin • • Feb 25 '18

An Update from the Dev Team

82 Upvotes

First, let me introduce myself. I am Barton26, the newly appointed "Gridcoin Testing Coordinator". My job on the dev team is to oversee testing of new releases and monitor situations like the one we are currently in.

Recently users have raised many valid questions about the current state of development and when the exchanges will be reopened. I am writing this quick update for those who have not been following the latest information on Slack or GitHub.

Here is a list of "breaking issues" that were identified in the original forking period that lead to the closing of the exchanges:

  1. Crashes due to tally

  2. Forking due to PoR checks

  3. RPC slowdowns

  4. Unable to get past 1163544

  5. Inability to sync from 0 without getting stuck

Here are the most recent updates from the development team regarding these issues:

  1. Fixed in hotfix.

  2. Believed to be either entirely or mostly fixed. Still being actively tested.

  3. Fixed in hotfix.

  4. Fixed in hotfix.

  5. Under active testing.

As you can see, we have made significant progress towards a production-ready release version. Our current testing priorities are Proof of Research Check forking (believed to be fixed, but we want to be sure) and syncing from 0 without getting stuck. Syncing from 0 is slow to test due to the length of time it takes to sync over 1.1 million blocks on production and nearly 500k blocks on testnet.

Please bear with us as we finish testing and hopefully verifying that this hotfix is ready to be released. We will make the announcement to open exchanges when we feel that the hotfix is stable and ready to be deployed to production.

Thank you for your patience in this difficult time. I apologize for the lack of communication and I will personally strive to communicate on other platforms to keep as many of our users up to date as possible. Please know that the development team is working as hard as they can to get this hotfix released as soon as possible. If you have any questions feel free to comment below.

-Barton26 (Gridcoin Testing Coordinator)


r/gridcoin • • Jan 22 '18

A guide to project selection and earnings estimation for Gridcoin

82 Upvotes

Corresponding Steemit article can be found here.

So over the past few months, we've definitely seen a measurable increase in people signing up to the Gridcoin network, and r/gridcoin recently hit 4000 subscribers, so I thought I'd do a writeup on how I go about choosing projects for my hardware and also how to estimate earnings for particular hardware. I’m also going to add the disclaimer that this may not be the best way to do these things, it’s just how I do it and seems fairly effective from my own application. If anyone has any suggestions/improvements, feel free to leave a comment.

Introduction

Firstly, to get a solid overview, I'll point to Dutch's "Hardware and Project Selection" three part miniseries over on Steemit. Part one gives a comparison between GPUs and CPUs so you can get a better idea of how they work. Part two goes into depth with GPUs, and part three explores CPUs.

So now that we’re past that, let’s get to it. When choosing a project, you’ll initially want to have mainly two things on your mind. These are:

  • How scientifically relevant do I want my contributions to be?

  • How much of a reward (in terms of GRC) am I looking for?

This is because (generally) the more scientifically relevant a project’s work is, the more popular it is, the less GRC you will earn for your computational contribution. For example, a graphics card like the NVIDIA GTX 1060 running SETI@home will earn significantly less GRC than a GTX 1060 running Collatz Conjecture. This can be partially attributed to the fact that SETI has four times as many Gridcoin members as Collatz Conjecture, so the magnitude allocated to SETI has to split across significantly more people. Thus we can see that there is a negative correlation between “scientific usefulness” and earnings potential. What I’m going to do next is order all the projects from least users to most users, and allocate each project a broad category starting with projects with only CPU work units.

  • ODLK1 (aka Latin Squares) – Mathematics

  • Sourcefinder (has been out of work units for some time) – Astronomy

  • SRBase – Mathematics

  • YAFU - Mathematics

  • TN-Grid - Biology

  • VGTU Project – Civil Engineering

  • DrugDiscovery@home - Biology

  • Numberfields@home - Mathematics

  • NFS@home - Mathematics

  • Yoyo@home - Multiple applications (mainly mathematics)

  • theSkyNet POGS - Astronomy

  • Universe@home - Astronomy

  • Citizen Science Grid - Multiple applications

  • Cosmology@home - Astronomy

  • World Community Grid - Multiple applications (lots of real world applications)

  • LHC@home – Physics

  • Asteroids@home - Astrophysics

  • Rosetta@home - Biology

Now the reason I’ve done separated the CPU-only projects from GPU projects is because, if you care the slightest bit about earnings, you’ll want to put your CPU on CPU-only projects. GPUs have significantly more brute horsepower than CPUs, which means one GPU could output the equivalent RAC of 100 CPUs. What this means for you is that if you run your CPU on a GPU project, you might get as little as one-tenth as much (or even less) GRC than if you were running a CPU-only project.

Sidenote: If you're crunching with an ARM device, such as an Android device or Raspberry Pi, you'll want to be careful about which CPU project you crunch. Not all CPU projects support ARM processors. A good way to find out if your ARM device is supported is to check grcpool's website here and use their list to check compatibility with your device. You can also cross reference this with the BOINC website's project list as well, found here.

Now here’s the projects with GPU work units ordered from least users to most users.

  • Amicable Numbers – Mathematics

  • Collatz Conjecture - Mathematics

  • Moo Wrapper - Cryptography

  • Enigma@home - Cryptography

  • PrimeGrid - Mathematics

  • GPUGrid (NVIDIA GPUs only) – Biology

  • Einstein@home - Astrophysics

  • Milkyway@home (1/8th ratio FP64 or better GPU strongly recommended) - Astronomy

  • SETI@home - Astrophysics

So, there’s obviously a reason why I’ve ordered them from most users to least users. This is because, as I mentioned previously, generally, the less users a project has the more earnings it will produce. Now you’ll notice that it’s mostly mathematics on the upper half for both lists, and (subjectively) more useful stuff on the bottom half, like astronomy and physics. The mathematical projects tend to have less real world benefits than something like Rosetta or Einstein, but they still have some value, and hence they tend to give the best earnings. So that’s all well and good, but how can you really tell which project is better than another? Well we gotta do some maths first.

Earnings estimation

So I’ll go through the process I use to get a rough idea of how much recent average credit (henceforth “RAC”) a particular set up is going to get me, and hence GRC earnings. It’s not very difficult, just tedious, with lots of flicking between tabs. So you start off with what hardware you’ve got that you wanna compare earnings between projects for. The example I’m going to use is a GTX 1080, you can substitute any GPU or CPU for this example, but generally more recent and popular GPU/CPUs are gunna be easier to work with.

First I just wanna mention that this is all very rough and isn’t going to provide you with a pinpoint accurate measure of your max RAC, merely an approximation. Now with that out of the way, we start by looking at how much RAC corresponds to one unit of magnitude for a given project. The three projects I’m going to compare are Collatz Conjecture, GPUGrid and SETI. Pretty much you just pick a random user’s RAC and divide by their magnitude to get RAC/Mag, so I’ll put this into a table below:

ProjectRandom User's RACRandom User's MagRAC/Mag
Collatz7,997,35596.48~82,891
GPUGrid4,595,053212.14~21,660
SETI1,266,852775.74~1,633

I hope this also gives people an appreciation that one project’s RAC is definitely not equal to another project’s RAC for Gridcoin purposes.

Once we have this information, we now head to each project’s website and try to find their “top computers” (or hosts) link. Most of the projects use a very similar template, so most of the time it isn’t difficult to find. For example for Collatz, you just need to scroll down to “Statistics”, click on that and then click on “Top computers” under “Statistics for Collatz Conjecture”. You’ll want to do this for every project you’re comparing. Continuing to use Collatz as our primary example, we’ll want to look through the list for hosts with GTX 1080’s. Looks like we’ve got two hosts with multiple 1080’s in them that seem to follow a trend. Take a look at the image below.

https://i.imgur.com/N46EAGO.png

The second and seventh ranked hosts have multiple 1080’s, and if we do some quick math, it looks like each 1080 is outputting roughly 6 million RAC for these hosts. So we can add that to our table. Repeat the same process for the other projects. I’m going to put the results in another table below.

ProjectRAC/MagOne 1080's RACMag per 1080
Collatz82,891~6,000,000~72.38
GPUGrid21,660~700,000~32.32
SETI1,633~40,000~24.49

You can see I’m making very rough generalisations with the RAC per GTX 1080, because there’s not much point to being too precise with these sorts of calculations as there’s a billion other factors that can influence what your max RAC is. These include:

  • Amount of time spent crunching

  • Any overclocking applied on the GPUs

  • CPU bottlenecking (i.e. not enough CPU resources available for GPU tasks)

  • Other GPU limitations such as thermals, power and voltage

  • What GPU driver version you’re using

  • The list goes on…

So what conclusions can we draw from this data? Collatz is clearly the superior choice for pure earnings, but (subjectively) its research may not be as useful as GPUGrid’s or SETI’s. Which project you choose will depend on those two factors I mentioned earlier in the article.

So I’ll close up this article with a couple of notes that might be useful for you.

Some notes

Hotbit over on Steemit published an article about the mathematics behind the RAC calculation and how you can estimate how much of your max RAC you’ll have at various points in time. Here’s a link to the article in full, but the numbers that are most interesting to me are:

  • ~10 % of your max RAC after 24 hours (extrapolated from graph, not explicitly stated in article)

  • 50 % of your max RAC after 7 days

  • 75 % of your max RAC after 14 days

  • 88 % of your max RAC after 21 days

  • 94 % of your max RAC after 28 days

  • 97 % of your max RAC after 35 days

So you can see it really takes a while for your RAC (and therefore earnings) to build up. So don’t be concerned if you’re only making a few GRC a day after crunching for a couple of days. As you can see, it takes roughly a month before you get close to your max RAC.

If you're looking for a bit more of an in-depth series on GPU crunching, I'd recommend Vortac's series of articles regarding his experiences with GPUs and various projects. Links to parts: one, two, three, four, five, six, seven and eight.

Speaking of GPUs, I’ve compiled a spreadsheet that has the theoretical floating point operations per second (FLOPS) for various GPUs for single precision and double precision compute. This is important for a few scenarios. Milkyway@home is a big example, which I briefly noted in the project list beforehand, in that Milkyway uses double precision compute for its GPU work units. This is why you’ll find GTX Titans and 280X’s topping the “top computers” list for Milkyway, as they have relatively high double precision compute. For example, an R9 280X has more FP64 (double precision) compute than a GTX 1080 Ti! So this is why I mentioned that generally GPUs with 1/8 ratio FP64 or better are suited for Milkyway, and anything else is a waste. You’ll also find double precision compute on one of Primegrid’s prime number searches. All of the other projects mainly rely on single precision, so you can pick between any of them for most GPUs. Here’s a link to the spreadsheet with columns sorted by FP64 and FP32 (single precision) performance.

My personal picks for projects at the moment are:

  • For CPU:

  • ODLK1 currently, as it's just been whitelisted so there's very few users to compete with.

  • Before ODLK1, it was VGTU, but you could pick any of the CPU projects that are in the lower half of users and you'd probably be fine.

  • For GPU:

  • For my double precision wielding R9 280X's I'm running Milkyway.

  • For my single precision GTX 1080 Ti I'm running Enigma as a sort of middleground between earnings and 'usefulness'.

Alright well I think that about wraps it up, I’ll be posting this to Steemit shortly under my friendlier alias ‘@Cautilus’ to see if I can spread the word around better, good luck with your crunching!


r/gridcoin • • Mar 16 '21

Release Gridcoin 5.3.0.0-mandatory EMERGENCY release

81 Upvotes

[5.3.0.0] 2021-03-16, mandatory

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.3.0.0

EMERGENCY MANDATORY

First, I would like to apologize for having to issue an emergency mandatory release. The newbie bug was ALMOST squashed by the combination of 5.2.0.0+ and the hard fork and following superblock. Unfortunately almost is not good enough. There were 130 people affected by the newbie bug, and after the post hard fork superblock, the pending rewards matched properly for 127 out of the 130 original mismatches. The other three didn't, and further, different nodes showed different things for those three. Most nodes showed a perfect match but some showed a mismatch on one or two of the three involved. Many thanks to @div72 for a keen eye in helping me spot the one line in code that was causing the problem.

Given different nodes don't match, this is a consensus issue and requires a mandatory to fix. Note that this version, when installed and first run will automatically rebuild the accrual snapshots (in the accrual folder) to straighten everything out. This may take a couple of additional seconds on startup, but should be transparent.

There are no other changes in this mandatory. Not installing this mandatory risks your node forking if it has a different accrual than the rest of the network for those three newbie CPID's if they stake, so it is best to upgrade to this version ASAP.

We have run audits on a number of nodes with a hotfix version of this mandatory that we tested on mainnet last night and all now match. This should be the end of the newbie bug problem and things should be quieter on the release front for a while!

Onward!

Thanks!

[5.3.0.0] 2021-03-16, mandatory

Fixed

  • consensus, accrual: Fix accrual post hard-fork at 2197000 #2053 (@jamescowens, @div72, @cyrossignol)


r/gridcoin • • Sep 04 '20

Gridcoin 5.0.0.0-Mandatory "Fern" Release

80 Upvotes

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0

Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.

Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.

We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.

Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.

Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.

The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.

There are so many goodies here it is hard to summarize them all.

I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.

The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

  • Network magnitude unit pinned to a static value of 0.25

  • Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)

  • New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement

Removed

  • 500 GRC research reward limit for a CPID's first stake

  • 6-month expiration for unclaimed rewards

  • 10-block spacing requirement between research reward claims

  • Rolling 5-day payment-per-day limit

  • Legacy tolerances for floating-point error and time drift

  • The need to include a valid copy of a CPID's magnitude in a claim

  • 10-block emission adjustment interval for the magnitude unit

Beacons

Added

  • One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project

  • Verification codes of pending beacons expire after 3 days

  • Self-service beacon removal

Changed

  • Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC

  • Rain addresses derived from beacon keys instead of a default wallet address

  • Beacon expiration determined as of the current block instead of the previous block

Removed

  • The ability for developers to remove beacons

  • The ability to sign research reward claims with non-current but unexpired beacons

Unaltered

As a reminder:

  • Beacons expire after 6 months pass (180 days)

  • Beacons can be renewed after 5 months pass (150 days)

  • Renewed beacons must be signed with the same key as the original beacon

Superblocks

Added

  • Magnitudes less than 1 include two fractional places

  • Magnitudes greater than or equal to 1 but less than 10 include one fractional place

Changed

  • A valid superblock must match a scraper convergence

Removed

  • Superblock popularity election mechanics

Voting

Added

  • Yes/no/abstain and single-choice response types (no user-facing support yet)

Changed

  • To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.

  • Burn fee for creating polls scaled by the number of UTXOs claimed

    • 50 GRC for a poll contract

    • 0.001 GRC per claimed UTXO

  • Burn fee for casting votes scaled by the number of UTXOs claimed

    • 0.01 GRC for a vote contract

    • 0.01 GRC to claim magnitude

    • 0.01 GRC per claimed address

    • 0.001 GRC per claimed UTXO

  • Maximum length of a poll title: 80 characters

  • Maximum length of a poll question: 100 characters

  • Maximum length of a poll discussion website URL: 100 characters

  • Maximum number of poll choices: 20

  • Maximum length of a poll choice label: 100 characters

Removed

  • Magnitude, CPID count, and participant count poll weight types

  • The ability for developers to remove polls and votes

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

  • Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)

  • Implement project level rain for rainbymagnitude #1580 (@jamescowens)

  • Upgrade utilities (Update checker and snapshot downloader/application) #1576 (@iFoggz)

  • Provide fees collected in the block by the miner #1601 (@iFoggz)

  • Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)

  • Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)

  • Implement zapwallettxes #1605 (@jamescowens)

  • Implements a global event filter to suppress help question mark #1609 (@jamescowens)

  • Add next target difficulty to RPC output #1615 (@cyrossignol)

  • Add caching for block hashes to CBlock #1624 (@cyrossignol)

  • Make toolbars and tray icon red for testnet #1637 (@jamescowens)

  • Add an rpc call convergencereport #1643 (@jamescowens)

  • Implement newline filter on config file read in #1645 (@jamescowens)

  • Implement beacon status icon/button #1646 (@jamescowens)

  • Add gridcointestnet.png #1649 (@caraka)

  • Add precision to support magnitudes less than 1 #1651 (@cyrossignol)

  • Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)

  • Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)

  • Add options checkbox to disable transaction notifications #1666 (@jamescowens)

  • Add support for self-service beacon deletion #1695 (@cyrossignol)

  • Add support for type-specific contract fee amounts #1698 (@cyrossignol)

  • Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)

  • Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)

  • Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)

  • Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)

  • neuralnet: Add integrity checking to researcher accrual snapshot registry #1727 (@jamescowens)

  • Add workaround for scrypt assembly on macOS #1740 (@cyrossignol)

  • gui: Build onboarding/beacon wizard #1739 (@cyrossignol)

  • doc: Add CONTRIBUTING.md from bitcoin #1723 (@div72)

  • rpc: Implement inspectaccrualsnapshot and parseaccrualsnapshotfile #1744 (@jamescowens)

  • scraper: Add disk based state backing for verified beacon list in scraper #1751 (@jamescowens)

  • Add ability to recover beacon in block version 11+ #1768 (@cyrossignol)

  • refactor: Add transaction context to contract handlers #1777 (@cyrossignol)

  • gui: Add context for when BOINC is attached to a pool #1775 (@cyrossignol)

  • doc: Clarify what to do if PR in multiple categories (for CONTRIBUTING.md) #1798 (@RoboticMind)

  • qt: Add option to choose not to start the wallet minimized #1804 (@jamescowens)

  • superblock: Add check for OutOfSyncByAge to SuperblockValidator::Validate #1806 (@jamescowens)

  • contract: Standardize contract validation and add block context #1808 (@cyrossignol)

  • add seed.gridcoin.pl to default config #1812 (@wilkart)

  • gui: Implement sidestake send display #1813 (@jamescowens)

  • gui: Add pool/investor pages to researcher wizard #1819 (@cyrossignol)

  • ci: Port lint scripts from Bitcoin #1823 (@div72)

  • doc: Create basic readme in contrib #1826 (@RoboticMind)

  • gui: Implement TransactionRecord::Message #1829 (@jamescowens)

  • rpc: Add private_key_available to beaconstatus #1833 (@a123b)

  • gui: Validate email address in researcher wizard #1840 (@a123b)

  • rpc: Add "getrawwallettransaction" RPC function #1842 (@cyrossignol)

  • consensus: Set block version 11 threshold height for mainnet #1862 (@cyrossignol)

Changed

  • Upgrade LevelDB from v1.17 to v1.20 #1562 (@cyrossignol)

  • Re-enable scrypt optimizations #1450 (@denravonska)

  • Derive CScript from prevector type (optimization) #1554 (@cyrossignol)

  • Disable quorum for grandfathered blocks to speed up sync #1568 (@cyrossignol)

  • Refactor hashBoinc for binary claim contexts #1558 (@cyrossignol)

  • integrated_scraper_2 branch tracking PR #1559 (@jamescowens)

  • Upgrade depends - OpenSSL to 1.1.1d #1581 (@jamescowens)

  • Ubuntu 19.10 fixes #1590 (@denravonska)

  • Force a re-parse of legacy claims in generated blocks #1592 (@cyrossignol)

  • Improve the "versionreport" RPC output #1595 (@cyrossignol)

  • Overhaul the core tally and accrual system #1583 (@cyrossignol)

  • Overhaul the superblock quorum system #1597 (@cyrossignol)

  • Add more data to the "superblocks" RPC output #1599 (@cyrossignol)

  • Update Windows Build doc #1606 (@barton2526)

  • Change the order of calls in gridcoinresearchd.cpp to optimize rpc shunt path #1610 (@jamescowens)

  • Change staking tooltip to display frequency #1611 (@jamescowens)

  • Enhancements to ETTS #1442 (@jamescowens)

  • Standardize money values as integers #1614 (@cyrossignol)

  • Clean up and optimize legacy coin age code #1616 (@cyrossignol)

  • Some scraper cleanups #1620 (@jamescowens)

  • Reorganize accrual code and fix 6-month cutoff #1630 (@cyrossignol)

  • Update Copyright years #1633 (@barton2526)

  • Change team whitelist delimiter to <> for CPID detection #1634 (@cyrossignol)

  • Change team whitelist separator to <> to accomodate more team names #1632 (@jamescowens)

  • Change Curl download speed type to support older environments #1640 (@cyrossignol)

  • Optimize logo SVGs used for tray icons #1638 (@cyrossignol)

  • Tweak consolidateunspent rpc function #1644 (@jamescowens)

  • ETTS and staking icon enhancements #1650 (@jamescowens)

  • Implement new transaction fees for block version 11 #1652 (@jamescowens)

  • Optimize in-memory storage of superblock data #1653 (@cyrossignol)

  • Miscellaneous superblock API improvements and housekeeping #1654 (@cyrossignol)

  • Update openssl to 1.1.1f compatibility #1660 (@jamescowens)

  • Optimize bdb to avoid synchronous flush of database #1659 (@jamescowens)

  • Add support for CPID input to "lifetime" RPC function #1668 (@cyrossignol)

  • Overhaul the contract handling system #1669 (@cyrossignol)

  • Make the autostart mainnet/testnet aware #1671 (@jamescowens)

  • Remove slashes from User Agent in peers tab #1674 (@div72)

  • Refactor contracts for polymorphic binary payloads #1676 (@cyrossignol)

  • Overhaul the beacon system #1678 (@cyrossignol)

  • Replace boost::optional<T&> with non-owning pointers #1680 (@cyrossignol)

  • Optimize proof-of-stake validation #1681 (@cyrossignol)

  • Updated Slack link #1683 (@NeuralMiner)

  • Update build-unix.md #1686 (@Quezacoatl1)

  • Replace deprecated QT methods #1693 (@Pythonix)

  • Made protocol.h more similar to bitcoin #1688 (@Pythonix)

  • Touch up some details for block version 11 #1697 (@cyrossignol)

  • More tweaks for block version 11 #1700 (@cyrossignol)

  • Finish the conversion to the BCLog class based logger #1699 (@jamescowens)

  • Move claim version transitional code in miner for proper signature #1712 (@cyrossignol)

  • doc: Update threads in coding.txt #1730 (@div72)

  • qt: Include QPainterPath in trafficgraphwidget.cpp #1733 (@div72)

  • doc: Update doc/build-unix.md #1731 (@div72)

  • gui: Show peers tab on connections icon click #1734 (@div72)

  • refactor: Change return type of IsMine to isminetype && move wallet files to wallet directory #1722 (@div72)

  • build: Updates boost to 1.73.0 for depends #1673 (@jamescowens)

  • doc: Update Unit Test Readme #1743 (@RoboticMind)

  • wallet: Change Assert To Error Message In kernel.cpp #1748 (@RoboticMind)

  • scraper: Shorten display representation of verification codes #1754 (@cyrossignol)

  • log: Change ".B." to Clear Message #1758 (@RoboticMind)

  • util: Fix braindamage in GetDefaultDataDir() #1737 (@jamescowens)

  • scraper: Improve scraper processing of beacon verifications #1760 (@jamescowens)

  • scraper: Add instrumentation to convergencereport #1763 (@jamescowens)

  • rpc: Improve rpc stress test script #1767 (@tunisiano187)

  • Generalize enum serialization #1770 (@cyrossignol)

  • scraper: Improve handling of ETags in http class and tweak verified beacon logic #1776 (@jamescowens)

  • scraper: Improve ProcessNetworkWideFromProjectStats and other tweaks #1778 (@jamescowens)

  • researcher: Automate beacon advertisement for renewals only #1781 (@cyrossignol)

  • gui: Tweak behavior of beacon page in researcher wizard #1784 (@cyrossignol)

  • Prepare for block version 11 hard-fork on testnet #1787 (@cyrossignol)

  • scraper: Modify UpdateVerifiedBeaconsFromConsensus #1791 (@jamescowens)

  • gui: Optimize OverviewPage::updateTransactions() #1794 (@jamescowens)

  • ci: Adopt ci changes from Bitcoin #1795 (@div72)

  • consensus: switch snapshot accrual calculation to integer arithmetic #1799 (@cyrossignol)

  • voting: Overhaul the voting system #1809 (@cyrossignol)

  • contract: Optimize contract replay after chain reorganization #1815 (@cyrossignol)

  • contract: Reimplement transaction messages as contracts #1816 (@cyrossignol)

  • staking: Sign claim contracts with coinstake transaction #1817 (@cyrossignol)

  • gui: Change research wizard text #1820 (@div72)

  • net: Update protocol version and clean up net messaging #1824 (@cyrossignol)

  • rpc, wallet: Corrections to GetAmounts #1825 (@jamescowens)

  • gui: Tweak some minor researcher wizard details #1830 (@cyrossignol)

  • gui: Change GetEstimatedStakingFrequency text #1836 (@jamescowens)

  • scraper: Scraper global statistics cache optimization #1837 (@jamescowens)

  • doc: Update Vulnerability Response Process #1843 (@RoboticMind)

  • scraper: Optimization of manifest and parts sharing between ConvergedScraperStatsCache, mapManifest, and mapParts #1851 (@jamescowens)

  • consensus: Update Checkpoints #1855 (@barton2526)

  • docs: Update docs to build off master #1856 (@barton2526)

  • gui: Fix and improve GUI combo box styles #1858 (@cyrossignol)

  • build: Tweak Gridcoin installer for Fern release #1863 (@jamescowens)

Removed

  • Remove old research age checks (rebase #1365) #1572 (@cyrossignol)

  • Remove PrimaryCPID check from diagnostics dialog #1586 (@cyrossignol)

  • Remove missed label for PrimaryCPID from diagnostics #1588 (@cyrossignol)

  • Remove legacy quorum messaging system (@neural network) #1589 (@cyrossignol)

  • Remove old remnants of legacy smart contract experiments #1594 (@cyrossignol)

  • Remove block nonce for version 11 #1622 (@cyrossignol)

  • Delete obsolete contrib/Installer and Upgrader directories #1623 (@jamescowens)

  • Remove redundant LoadAdminMessages() calls #1625 (@cyrossignol)

  • Remove some legacy informational RPC commands #1658 (@cyrossignol)

  • Remove informational magnitude field from binary claims #1661 (@cyrossignol)

  • Remove fDebug3,4, and net and convert to BCLog::LogFlags #1663 (@jamescowens)

  • Remove qt5.7.1 depends support build System #1665 (@iFoggz)

  • Remove unused jQuery library #1679 (@cyrossignol)

  • Remove unused NetworkTimer() function and global state #1701 (@cyrossignol)

  • Refactor claim context objects into contracts #1704 (@cyrossignol)

  • Clean old assets up #1718 (@div72)

  • Remove legacy "rain" RPC (not by-project rain) #1742 (@cyrossignol)

  • Temporarily disable voting system on testnet #1769 (@cyrossignol)

  • gui: Remove legacy GUI transaction description for contracts #1772 (@cyrossignol)

  • gui: Remove transaction fee setting #1780 (@cyrossignol)

  • trivial: Cleanup unused legacy functions #1793 (@cyrossignol)

  • mining, rpc: Remove kernel-diff-best and kernel-diff-sum #1796 (@jamescowens)

  • refactor: Remove libs subdirectory #1802 (@div72)

  • scraper: cleanup unused/unnecessary functions #1803 (@jamescowens)

  • gui: Remove useless "Detach databases at shutdown" #1810 (@jamescowens)

  • test: Remove testnet condition for standard transactions #1814 (@cyrossignol)

  • consensus: Remove transitional testnet code #1854 (@cyrossignol)

Fixed

  • Fix "Owed" amount in output of "magnitude" RPC method #1569 (@cyrossignol)

  • Add support for paths with special characters on Windows #1571 (@cyrossignol)

  • Fix lingering peers.dat temp files and clean up remaining paths #1582 (@cyrossignol)

  • Fix incorrect beacon length warning in GUI transaction list #1585 (@cyrossignol)

  • Fix default config file line endings on Windows #1587 (@cyrossignol)

  • Reenable Travis builds for MacOS #1591 (@jamescowens)

  • Correct peer detail info background color #1593 (@jamescowens)

  • Fix exception in debug3 mode #1598 (@cyrossignol)

  • Fix deadlock in "getmininginfo" RPC function #1596 (@cyrossignol)

  • Fix accuracy of statistics in "network" RPC output #1602 (@cyrossignol)

  • Fix heights for quorum vote weight calculations #1604 (@cyrossignol)

  • Fix deadlock in log archiver when rename fails #1607 (@cyrossignol)

  • Fix a spurious segmentation fault during client load on Windows with fast CPUs #1608 (@jamescowens)

  • Fix lock order debugging and potential deadlocks #1612 (@jamescowens)

  • Add dependencies #1613 (@Scalextrix)

  • Fix std namespace pollution #1617 (@denravonska)

  • Add missing condition for newbie accrual computer #1618 (@cyrossignol)

  • Track first reward blocks in research accounts #1619 (@cyrossignol)

  • Fix lingering beacon warning after advertisement #1627 (@cyrossignol)

  • Fix accrual calculation for new, zero-magnitude CPIDs #1636 (@cyrossignol)

  • Fix diagnostics, add ETTS test, fix tooltipcolor, add missing lock, and add email=investor check #1647 (@jamescowens)

  • Fix help message of two RPC methods #1656 (@div72)

  • Fix legacy accrual for newbie with non-zero past reward #1667 (@cyrossignol)

  • Fix GUI autostart on Windows for paths with wide characters #1670 (@cyrossignol)

  • Qualify boost bind placeholders with their full namespace #1672 (@Ponce)

  • Fix suffix when copying txids #1677 (@div72)

  • Unnecessary if-statement removed #1685 (@Pythonix)

  • Fix consolidatemsunspent Help Message #1687 (@Pythonix)

  • Fix gettransaction help message #1691 (@Pythonix)

  • Fix GetNewMint To Look for Stakes #1692 (@RoboticMind)

  • Suppress deprecated copy warnings for Qt with GCC 9+ #1702 (@cyrossignol)

  • Fix exclusion error on stats processing and misplaced ENDLOCK logging entry #1710 (@jamescowens)

  • Removed unnecessary comparison #1708 (@Pythonix)

  • Fixed typo #1707 (@Pythonix)

  • Fix out-of-bounds exception for peers tab version slashes #1713 (@cyrossignol)

  • Fix transition for v1 superblocks when reorganizing #1714 (@cyrossignol)

  • Touch up transition to version 2 transactions #1715 (@cyrossignol)

  • Avoid mutating transactions in ConnectBlock() #1716 (@cyrossignol)

  • Skip beacon advertisement when already pending #1726 (@cyrossignol)

  • Fix Windows cross-compilation in newer environments #1728 (@cyrossignol)

  • Fix out-of-bounds access in IsMineInner() #1736 (@cyrossignol)

  • Fix a couple of block version 11 issues #1738 (@cyrossignol)

  • Fix null pointer dereference in GUI researcher model #1741 (@cyrossignol)

  • accrual: Reset research accounts when rebuilding accrual snapshots #1745 (@cyrossignol)

  • scraper: Correct update for verified beacons #1747 (@jamescowens)

  • accrual: Refactor tally initialization for snapshot rebuild #1749 (@cyrossignol)

  • rpc: Fix "cpid" field in "beaconconvergence" RPC output #1750 (@cyrossignol)

  • accrual: Fix snapshot accrual superblock state transitions #1752 (@cyrossignol)

  • scraper: Correct stale verified beacon logic #1753 (@jamescowens)

  • rpc: Correct possible divide by zero in getblockstats #1755 (@jamescowens)

  • gui: Fix issues with researcher wizard flow #1756 (@cyrossignol)

  • wallet: Stop Error When Starting From Zero #1759 (@RoboticMind)

  • Don't count empty email as explicit investor #1761 (@cyrossignol)

  • accrual: Fix snapshot accrual superblock state transitions #1764 (@cyrossignol)

  • rpc: Cleanup Help Message and Fix Typo #1771 (@RoboticMind)

  • scraper: Fix scraper etag header case sensitivity #1773 (@cyrossignol)

  • consensus: Use explicit time to check if superblock needed #1774 (@cyrossignol)

  • gui: Fix scroll area dark theme styles #1785 (@cyrossignol)

  • rpc, gui: Fix three divide by zero possibilities #1789 (@jamescowens)

  • rpc: Fix balance pre-check in "rainbymagnitude" RPC #1792 (@cyrossignol)

  • accrual: Fix outdated comment and correct grammar #1800 (@RoboticMind)

  • gui: Fix stuck cursor on labels #1801 (@div72)

  • beacon: Fix research wizard beacon renewal status #1805 (@cyrossignol)

  • gui: Fix translations for port numbers #1818 (@cyrossignol)

  • util: Create parent directory #1821 (@div72)

  • mining: Fix coinstake/claim signature order #1828 (@cyrossignol)

  • voting: Remove double increment in loop #1831 (@cyrossignol)

  • neuralnet, scraper: Fix compilation with gcc5 and older libcurl #1832 (@a123b)

  • wallet: Fix smallest coin selection for contracts #1841 (@cyrossignol)

  • gui: Fix display of polls with no votes yet #1844 (@cyrossignol)

  • gui: add indentation to diagnostic status bar labels #1849 (@jamescowens)

  • voting, gui: Fix formatting and alignment of vote shares and percent #1850 (@jamescowens)

  • wallet, rpc: Fix for self-transactions in listtransactions #1852 (@jamescowens)

  • accrual: Clear any accrual snapshots when syncing from pre-v11 #1853 (@cyrossignol)

  • accrual: Fix reset of accrual directory if starting sync below research age height #1857 (@jamescowens)

  • gui: Fix researcher wizard layout on macOS with native theme #1860 (@cyrossignol)


r/gridcoin • • Dec 27 '21

Happy Holidays - 50000 GRC rain

78 Upvotes

Happy Holidays everyone. Spreading some good cheer with a 50k GRC rainbymagnitude to the network. Enjoy! :)


r/gridcoin • • Aug 02 '21

Release Gridcoin 5.3.2.0-leisure "Ingrid"

75 Upvotes

[5.3.2.0] 2021-08-01, leisure, "Ingrid"

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.3.2.0

This leisure release represents the completion of the "Ingrid" milestone. It has turned out to be a very substantial release, quite a bit larger in scope than originally envisioned. The biggest thing that folks will notice right away is the re-skinning of the application to conform to the approved GUI assets that were done for the GUI bounty. While a complete rewrite of a loosely coupled GUI has not been completed, this is a great stop-gap until that is done.

Some highlights:

  1. Implementation of the GUI assets in https://github.com/gridcoin-community/Gridcoin-Research/issues/847 as native Qt. This major re-skinning is meant to tide us over until the implementation of the GUI as bountied in https://github.com/gridcoin-community/Gridcoin-Research/issues/1401.

  2. Many fixes and refinements to the GUI's underlying style and scaling. The wallet has a consistent look and feel across all platforms and most screen resolutions. There may be some remaining fine-tuning to dialog box sizes and we will attend to that in the next release after feedback from users in production.

  3. Overhauling of the poll/voting GUI. More work needs to be done in this area still, but the improvements in here should make voting a much better experience.

  4. Port of Bitcoin's ArgsManager which allows for much better processing of program arguments on the command line and the config files, and provides the plumbing for read-write core wallet settings into a new gridcoinsettings.json file while the wallet is running. Note that settings stored in gridcoinsettings.json always override the read-only gridcoinresearch.conf. (See 7.)

  5. Implementation of the consolidate unspent wizard for graphically assisted selection of UTXOs to consolidate and automated construction of the consolidation transaction. (Prior to this to do UTXO consolidation required the use of the consolidateunspent RPC command in the debug console.)

  6. Refresh of rainbymagnitude to require a minimum of 1000 GRC to do a network rain, and also prevent dust distribution via rain. No payment to an individual as part of a rain of less than 0.01 GRC is allowed. The ability to send custom rain messages has also been removed. The ability to do a trial run of the rain transaction before the send to understand what is going to happen has been implemented.

  7. The implementation of new options that allow in wallet GUI control of staking and stakesplitting without having to shut the wallet down first. In wallet GUI control and configuration of sidestaking is envisioned for the next release.

  8. Refresh of the snapshot download functionality to ensure broader compatibility and more reliable operation across all platforms, and implementation of the "reset blockchain data" option to easily wipe the blockchain from the GUI or the command line and start syncing from zero without having to manually go and delete the files.

  9. Refresh of the diagnostics to provide better information and eliminate bugs within the diagnostics themselves in corner cases.

  10. Many other fixes and refinements.

Some known remaining issues (both predating this release):

  1. Snapshot download functionality still will not work correctly on some 32-bit Linux platforms due to the distributions not properly compiling the libzip package with 64 bit file offsets enabled. We are probably going to end up distributing a version of libzip in the main source code compile tree, just like LevelDB, ensure it is statically linked into the executable, and ensure it is properly compiled with large offset support to fix this issue across all platforms. Note that the platforms that seem to be most affected by this are ARM 32-bit SBCs. The reason this is an issue at all is that the snapshot file is now greater than 2 GB. Windows 32 bit platforms work correctly and are not affected by this issue.

  2. If coin control is used to manually select UTXOs for a send, and a message is provided, the fees calculated do not include the cost of the message (0.1 GRC), so if the amount post fees to send + the calculated fees equals the selected UTXO size, the transaction will fail. This normally will not be a problem if automatic input selection is used, or you can simply reduce the amount to send by another 0.1 GRC and it will succeed.

Detailed notes on the new gridcoinsettings.json file and the listsettings and changesettings RPC commands:

With the implementation of the Bitcoin ArgsManager in Gridcoin comes the new gridcoinsettings.json file. This file contains settings changed by the node while running and settings stored in this file override the read-only settings in the gridcoinresearch.conf file.

Two new RPC commands have been implemented to enable listing and change of settings while the wallet is running:

listsettings takes no arguments and provides a JSON output of all settings currently active in the wallet. For each setting it shows whether that setting is changeable dynamically while the wallet is running without requiring a restart.

If a setting does not require a restart of the wallet (i.e. changeable_without_restart is true), then the setting(s) can be dynamically modified by...

changesettings setting1=value1 setting2=value2 etc.

No dashes are required for the settings (think about them like entries in the config file).

Note that settings modified this way will make entries in the gridcoinsettings.json file and they will override any corresponding settings in the gridcoinresearch.conf file.

The GUI control of staking and stakesplitting makes use of the same services internally.

Enjoy!

[5.3.2.0] 2021-08-01, leisure, "Ingrid"

Added

  • util, rpc. gui: Changes for snapshotdownload and add feature sync from zero #2093 (@iFoggz)

  • gui: Implement GUI version of consolidateunspent (coin control part) #2111 (@jamescowens)

  • gui: Implement consolidateunspent wizard #2125 (@jamescowens)

  • qt: Add antialiasing to traffic graph widget #2150 (@barton2526)

  • util: Port of ArgsManager and a significant subset of src/util #2146 (@jamescowens)

  • doc: add issue templates for bug reports and feature requests #2147 (@Pythonix)

  • gui, rpc: Implement dynamic stakesplitting control, settings changes via rpc, and dynamic changes to sidestaking via rpc #2164 (@jamescowens)

  • rpc: Implement getblocksbatch #2205 (@jamescowens)

  • voting, rpc, gui: Implement demand loading of historical poll by poll id and AVW calculation #2210 (@jamescowens)

  • gui: Show GUI error dialog if command line parsing fails #2218 (@jamescowens)

  • gui: Implement close confirmation. #2216 (@denravonska)

  • build: Use -fstack-reuse=none #2232 (@barton2526)

Changed

  • doc: Update build doc #2078 (@iFoggz)

  • gui: Normalize button and input control appearance #2096 (@cyrossignol)

  • consensus: Implement GetMinimumRequiredConnectionsForStaking #2097 (@jamescowens)

  • refactor: move CTransaction to primitives #2006 (@div72)

  • consensus, refactor, test: Merkle #2094 (@div72)

  • gui: Update diagnostics #2095 (@jamescowens)

  • gui: Refresh UI styles and sidebar/statusbar design #2102 (@cyrossignol)

  • gui: Set standard base Qt style on Windows and macOS #2114 (@cyrossignol)

  • build, refactor: bump to C++17 #2113 (@div72)

  • util, rpc, gui: Implement GetMaxInputsForConsolidationTxn() #2119 (@jamescowens)

  • gui: Refresh overview page design #2117 (@cyrossignol)

  • depends: change boost mirror #2122 (@div72)

  • refactor: small cleanup #2123 (@div72)

  • build: Update depends Qt recipe to version 5.12.10 #2129 (@cyrossignol)

  • build: Bump Codespell to 2.0.0 #2135 (@barton2526)

  • gui: Refresh "send coins" page design #2126 (@cyrossignol)

  • gui: Optimize locks to improve responsiveness #2137 (@cyrossignol)

  • gui: Refresh "receive payment" page design #2138 (@cyrossignol)

  • gui: Add empty placeholder to recent transactions list #2140 (@cyrossignol)

  • gui: Refresh transaction history page design #2143 (@cyrossignol)

  • gui: Refresh address book page design #2145 (@cyrossignol)

  • doc: Update http to https where possible #2148 (@barton2526)

  • depends: Update dependencies #2153 (@barton2526)

  • depends: Bump python to 3.6 #2159 (@barton2526)

  • test: Update cppcheck linter to c++17 #2157 (@barton2526)

  • test: Drop Travis specific workarounds, Mention commit id in error, Fix typos, Update spellcheck ignore words #2158 (@barton2526)

  • gui: Overhaul the voting UI #2151 (@cyrossignol)

  • wallet: simplify nTimeSmart calculation #2144 (@div72)

  • gui: Refresh checkbox and radio button styles #2170 (@cyrossignol)

  • build: Bump libevent to 2.1.11 #2172 (@barton2526)

  • build: Update native_mac_alias, Remove big sur patch file in qt recipe #2173 (@barton2526)

  • docs: Misc Grammar #2176 (@barton2526)

  • build: miniupnpc 2.2.2 #2179 (@barton2526)

  • rpc: Refresh rainbymagnitude #2163 (@jamescowens)

  • util: optimize HexStr #2185 (@div72)

  • refactor: misc style changes #2177 (@div72)

  • rpc: consolidatemsunspent changes. #2136 (@iFoggz)

  • refactor: Replace "GlobalStatus" state management #2183 (@cyrossignol)

  • rpc, util: Remove use of ArgsManager::NETWORK_ONLY for now #2190 (@jamescowens)

  • doc: Replace hidden service with onion service, Capitalize "Tor" #2193 (@barton2526)

  • gui: Update Qt Linguist localization files #2192 (@cyrossignol)

  • script: Shell script cleanups #2195 (@barton2526)

  • build: set minimum required Boost to 1.58.0 #2194 (@barton2526)

  • build, util: Prevent execution for Windows versions less than Windows 7 #2203 (@jamescowens)

  • build: Tweak NSIS Windows installer #2204 (@jamescowens)

  • build: Add bison in depends #2206 (@iFoggz)

  • build: macOS toolchain bump #2207 (@div72)

  • doc: Update build-unix.md #2212 (@springfielddatarecovery)

  • build: Bump minimum python version to 3.6, Remove python2 references #2219 (@barton2526)

  • depends: Change openSSL source path to Github #2237 (@barton2526)

  • doc: Fix typo in bug report template #2243 (@jamescowens)

  • ci: fold depends output #2244 (@div72)

Removed

  • wallet: remove dead hardcoded addnodes #2116 (@sweede-se)

  • rpc: Remove readconfig #2248 (@jamescowens)

  • rpc: Remove obsolete comparesnapshotaccrual RPC function #2100 (@jamescowens)

  • rpc: Remove memorypool RPC Command #2214 (@RoboticMind)

  • rpc: Remove deprecated RPC commands #2101 (@jamescowens)

  • Remove CCT from README, add Discord #2134 (@barton2526)

  • refactor: Remove obsolete pubsub method definitions #2191 (@barton2526)

  • refactor: Remove msMiningErrorsIncluded & msMiningErrorsExcluded #2215 (@RoboticMind)

  • qt: Remove obsolete topLevelWidget(), Remove obsolete QRegExpValidator #2198 (@barton2526)

  • net: Drop support of the insecure miniUPnPc versions #2178 (@barton2526)

  • log: remove deprecated db log category #2201 (@barton2526)

  • doc: Remove CCT from README and release process docs #2175 (@barton2526)

  • build: Remove travis references #2156 (@barton2526)

Fixed

  • gui: Fix macOS and designer font sizes #2098 (@cyrossignol)

  • gui: Have the TrafficGraphWidget respect the selected stylesheet. #2107 (@jamescowens)

  • gui: Fix macOS display inconsistencies #2106 (@cyrossignol)

  • gui: Fix RPC console auto-complete background color #2108 (@cyrossignol)

  • gui: Avoid reloading redundant stylesheets #2109 (@cyrossignol)

  • gui: Fix "no active beacon" status #2110 (@cyrossignol)

  • gui: Fix dark theme link text color visibility #2115 (@cyrossignol)

  • scraper, util, qt: Fix several deprecations and warnings #2131 (@jamescowens)

  • gui: Fix duplicate time in GUIUtil::dateTimeStr() #2139 (@cyrossignol)

  • gui: Fix debug console traffic graph legend colors #2142 (@cyrossignol)

  • gui: Fix nomenclature #2104 (@jamescowens)

  • doc: Fix Typos #2149 (@barton2526)

  • doc: Fix "master" branch build status badge in readme #2167 (@cyrossignol)

  • gui: Fix Inter font rendering on Windows with FreeType #2169 (@cyrossignol)

  • gui: Fix assert on non-existent data directory and GUI datadir chooser corner case issues #2174 (@jamescowens)

  • gui: Fix display artifact in poll loading indicator #2180 (@cyrossignol)

  • rpc, logging: Minor fixes for sidestake logging #2187 (@jamescowens)

  • gui: Fix fractional scaling for dialog sizes #2189 (@cyrossignol)

  • doc: Random fixes #2197 (@barton2526)

  • doc: getbalance should say GRC not "btc" #2199 (@barton2526)

  • net: Add missing verification of IPv6 address in CNetAddr::GetIn6AddrÂŚ #2200 (@barton2526)

  • doc: remove duplicate line from .gitignore #2202 (@Pythonix)

  • util: Tweak exception handling in MilliTimer class to eliminate compiler warnings #2233 (@jamescowens)

  • depends: patch missing include in qt #2234 (@div72)

  • wallet, rpc: Check each input for IsMine() in GetAddressGroupings #2242 (@jamescowens)

  • util, qt: Fix snapshot download #2246 (@jamescowens)

  • gui: Fix Column Widths in RPC Console. Elide long strings in their center. Indent user agent. #2241 (@barton2526)

  • qt: Fix crash during download snapshot on macOS #2250 (@jamescowens)

  • qt: Don't allow to open the debug window during splashscreen & verification state #2245 (@barton2526)

  • gui: Fix address book selected model record when editing #2253 (@cyrossignol)

  • researcher: Check wallet status before beacon renewal #2254 (@cyrossignol)

  • qt: Prevent pasting (no label) as label in consolidation transaction #2255 (@jamescowens)


r/gridcoin • • Jun 20 '21

Hello my fellow Gridcoiners. (Cross Post)

74 Upvotes

First off, I’ll introduce myself for those who do not know who I am; If you do know then you can skip this paragraph completely. My name is Paul aka iFoggz. I’ve been with Gridcoin development since around Mid 2017. Since than I’ve contributed to the development process, worked up the ranks and gained the trust of the community. I rather enjoy contributing when I can to a community that is passionate about Gridcoin. So keep on crunching and supporting the network.

Unfortunately, this post is not a hyped post of good news. Due to certain circumstances, I feel obligated to inform the community about my health issues since I maintain a few Gridcoin services and access. This post is to inform you of what I am going through as well as my future plans with regards to my health concerns. Also, this post will address any concerns with regards to the Gridcoin services and access I have in the event I worsen in health or became deceased.

In mid March I started to develop a bump where I had recently gotten rug burn of all things. Over time the bump simply grew which led me to believe I had an abscess. Due to COVID-19 restrictions appointments with doctors did not come fast in my small town. I was finally seen in early May in which the doctor then opted to perform a procedure at our local hospital to attempt to drain the apparent abscess on my right lateral knee. While the procedure was being performed it was determined that there was no drainage and the matter appeared to be firm. Along with that fact and the numbness to touch around the mass a biopsy was performed.

On May 19th I got a phone call from my doctor who had a diagnosis for my incredibly fast-growing mass. It turns out I would now be preparing for the biggest battle I’ve had to face in my life. I was diagnosed with Merkel cell carcinoma. For those who may not know about this cancer I’ll provide some details. Merkel cell carcinoma is a very aggressive, dangerous but treatable rare skin cancer that starts in the merkel cells of the skin. This cancer affects around 3 in a million Americans which is lottery odds in my opinion.

On June 1st I had a PET scan and the results of the scan showed I had a positive lymph node. I’m currently waiting on a biopsy date to be set to determine if the cancer is there or not. A positive PET scan does not necessarily mean it is cancerous.

On June 2nd I underwent a surgery to remove a 10-week-old mass which was about 1.5 inches in diameter. The surgeon managed to remove the whole mass as well as extra for margins and 3cm of extra skin around the tumour as per protocol for this cancer. I then had a negative pressure vacuum to help promote healing and keeping the wound healthy for a future skin graft. A skin graft could not be immediately done due to the amount of skin loss as well as flesh and muscle.

On June 5th I had a complication that was a huge eye opener for my family and me. I had a complication with the vac therapy as it managed to erode my already eroded artery in the open wound where the tumour was removed. If it were not for my 2 brave children (aged 5 and 8) to be able to get to the front door of the apartment complex to let paramedics in I would not be here today.

On June 9th I had a second surgery and irrigation to attempt to put a different kind of pump to promote healthy wound healing but with my bad luck the machine couldn’t get a good seal, so the surgeon left the wound bandaged.

On June 18th my wound had healed nicely and was granular to be able to accept a skin graft. Now I remain in hospital till Tuesday before I travel to have my first consult with the specialist the following day. This specialist at the BC Cancer agency will be biopsying my lymph node at a near future date. Also, now that my skin graft has been done I wait to find out when it will be safe for my rounds of radiation on the tumour site. Radiation is very effective against this cancer so the sooner I am able to start the better the outcome can be. As I know more I’ll happily share this with anyone who wishes to be updated.

Now that you’re aware of my diagnosis I’ll work into what would happen in the future if things do not improve for me.

Currently I maintain the following:

gridcoin.us domain

mail.gridcoin.us server (which hosts snapshot)

amazon cloudfront CDN (for snapshot CDN)

cloudfront (dns services)

Any project teams under “Gridcoin”

I am also a foundation key holder but that key will not need to be transferred to anyone as we have a 2-of-3 multi-signature address and the funds from the foundation will just be transferred to a new 2-of-3 address with a new 3rd key holder being introduced.

I do not believe this is a cancer battle I will lose. I have a strong aggressive team behind me and I am throwing everything I have at the cancer. However, if I was to start to deteriorate I would then start transferring these services over to trusted members of the community. In the event I suddenly pass away, a family member will have immediate access to contact information for Jim Owens to start the process of determining where and whom the services would be transferred to and during this time the services will be funded until this process is complete.

I have complete faith in Jim to do what is necessary to fairly distribute the services to one or more trusted members along with consensus of the matter. I’m aware there is always concern about 1 person having too much which is why the services will continue to be paid for until everything is transferred and figured out then standard compensation for the services can be paid out to my address which my family member will have access to. All accesses will not be available to my trusted family member unless I’ve passed on.

I know there will be some individuals who will be concerned about my dev payments from past work as to get those payments I will have to be contributing. I will do my best to honour that but if I’m actively in radiation treatment etc. I may not be able to fulfill that obligation and fully understand that I will not be qualified for a payment. I’m also aware that in the event that I am no longer alive that these payments would also stop and remain with the foundation minus the compensation for the services above.

Thank you for your time and keep crunching.


r/gridcoin • • Mar 01 '21

Gridcoin 5.2.0.0-mandatory "Hilda" release

71 Upvotes

[5.2.0.0] 2021-03-01, mandatory, "Hilda"

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.2.0.0

The core team is proud to present the Hilda milestone release, which is a mandatory upgrade.

The mandatory aspect of the upgrade here is the complete fix for the "newbie bug" that was not completely fixed in Gladys. This mandatory provides a permanent fix for the bug, and also will pay newbie's back accrual when they stake post-fix to the point of their original beacon confirmation superblock, as long as they have not already staked with their CPID. (For reference, the "newbie bug" is where newly confirmed beacons would have their accruals reset to zero at each superblock instead of continuing like they are supposed to.)

The transition height ("hard fork") is at 2197000, which will be approximately Sunday, March 14. All nodes MUST be upgraded by then or face disconnection from the network. There is a disconnection grace period of 2000 blocks higher than the hard fork, or 2199000. Any node not on 5.2.0.0 at that time will automatically be disconnected.

In addition to the mandatory inducing changes, this release contains LOTS of goodies that should improve the experience with the wallet. Some highlights:

  1. A Port of the data directory dialog box from Bitcoin Core for a brand new installation, allowing a different directory than the default to be specified. This will be memorized by the wallet as an alternative to providing a -datadir value on the command line. This should be especially useful for MacOS folks.

  2. Another goodie for the MacOS folks is the implementation of the AppNap manager ported from Bitcoin Core, which suspends AppNap when the wallet is staking to avoid lost stake opportunities.

  3. Significant optimizations were done to memory usage that reduce memory requirements by 30% or more. This should really help using the wallet on SBCs and also reduce hardware requirements on other platforms. It also results in another modest improvement in sync speed, although we are getting to the point of diminishing returns there. Mainnet can sync from zero in less than 2 hours on a fast machine.

  4. Several bottlenecks were removed in the GUI code that caused the wallet to bog down very badly if the wallet has a lot of transactions or a lot of UTXOs. This drastically improves the GUI experience, especially if resyncing an existing wallet from zero with the blockchain, or on a slower SBC.

  5. The GUI now remembers the size and position of the wallet window for both mainnet and testnet, and some font work was done to improve scaling on various displays. (The font and scaling work is still a work in progress, but it is much better than before.)

  6. A big bug was fixed in CreateTransaction that was causing insufficent fee transaction rejections and driving everyone crazy! This bug has actually been in there forever and is finally slayed!

  7. Related to #3, but also generally useful for folks interested in monitoring their staking efficiency are new measures in the getmininginfo RPC: staking_loop_efficiency measures the percent of elapsed time that is covered by an active staking loop, and staking_efficiency measures the overall staking efficiency, which takes into account staking_loop_efficiency and the UTXO's that are on cooldown.

  8. The beacon registry in the wallet, which holds in memory the beacons for the network, has received enhancements that solve some thorny problems related to contract lookback and beacon renewals, and does this with high performance by using leveldb for specialized storage of the beacon structures.

  9. Consolidateunspent has been enhanced. The function now allows the consolidation of ALL addresses to the specified address, and also allows the sweeping of associated change addresses.

  10. The wallet no longer depends on external IP resolvers, but instead uses the Bitcoin Core style of IP resolution. This also means the wallet will correctly update its IP if a notebook is put to sleep on one network and then awoken on another with a different IP. Before the wallet would have to be restarted to accept incoming connections. Note that UPNP can still be an issue though.

  11. Other bugfixes and enhancements too.

This was a pretty hefty release. We hope you enjoy it! :)

[5.2.0.0] 2021-03-01, mandatory, "Hilda"

Added

  • gui: Add RAC column to wizard summary page projects table #1951 (@cyrossignol)

  • rpc: clean up the superblocks function and add magnitude to getmininginfo #1966 (@jamescowens)

  • rpc: Add transaction size to RPC output #1971 (@cyrossignol)

  • voting: Add user-facing support for poll response types #1976 (@cyrossignol)

  • gui: Port Bitcoin Intro class (implement the ability to choose a data directory via the GUI) #1978 (@jamescowens)

  • gui: Port Bitcoin MacOS app nap manager #1991 (@jamescowens)

  • mining, rpc: Implement staking efficiency measure and improve SelectCoinsForStaking and CreateCoinStake #1992 (@jamescowens)

  • accrual, rpc: Implement auditsnapshotaccruals #2001 (@jamescowens)

  • docs: add doxygen support #2000 (@div72)

  • beacon: Specialized beacon storage in leveldb #2009 (@jamescowens)

  • rpc: Add a call to dump contracts in binary form #2011 (@div72)

  • rpc: Add boolean option to report active beacons only in beaconreport #2013 (@jamescowens)

  • consensus: Set Hilda mainnet hardfork height to 2197000 #2022 (@jamescowens)

Changed

  • refactor: [Memory optimization] Block index duplicate PoS state #1945 (@cyrossignol)

  • refactor: [Memory optimization] Block index superblock and contract flags #1950 (@cyrossignol)

  • refactor: [Memory optimization] Remove stake modifier checksums #1954 (@cyrossignol)

  • refactor: [Memory optimization] Block index allocation overhead #1957 (@cyrossignol)

  • refactor: [Memory optimization] Remove block index subsidy fields #1960 (@cyrossignol)

  • refactor: [Memory optimization] Separate chain trust from the block index #1961 (@cyrossignol)

  • refactor: [Memory optimization] Eliminate padding between block index fields #1962 (@cyrossignol)

  • beacon, gui: Add check for presence of beacon private key to updateBeacon() #1968 (@jamescowens)

  • util: Enhance ETTS calculation #1973 (@jamescowens)

  • refactor: Use new clamp in util.h #1975 (@jamescowens)

  • gui: Redo global status for overview #1983 (@jamescowens)

  • util: Improvements to MilliTimer class and use in the miner and init #1987 (@jamescowens)

  • rpc: Move rpc files to directory #1995 (@Pythonix)

  • rpc: Enhance consolidateunspent and fix fee calculation #1994 (@jamescowens)

  • contract: Double the lookback scope of contract replay #1998 (@jamescowens)

  • net: Don't rely on external IP resolvers #2002 (@Tetrix42)

  • beacon: Change beacon map to pointers #2008 (@jamescowens)

  • gui: Update bitcoin_sv.ts #2014 (@sweede-se)

  • util: Update snapshot URLs and add accrual directory #2019 (@jamescowens)

  • beacon: Tweak BeaconRegistry::Revert #2020 (@jamescowens)

  • rpc, qt: bump fees @2023 (@div72)

Removed

  • researcher: Remove automatic legacy beacon key import #1963 (@cyrossignol)

  • util: Revert "Close LevelDB after loading the block index" #1969 (@cyrossignol)

  • ci: Fix python symlink issue & remove travis #1990 (@div72)

  • ci: remove python workaround #2005 (@div72)

Fixed

  • gui: fix mandatory/leisure detection of upgrade check #1959 (@Pythonix)

  • voting: Fix title in "gettransaction" RPC for legacy poll contracts @1970 (@cyrossignol)

  • gui: Fix missing menu items on macOS #1972 (@scribblemaniac)

  • rpc: Fix answer offset in "votedetails" #1974 (@cyrossignol)

  • voting: Implement missing try-catch in VotingVoteDialog::vote #1980 (@jamescowens)

  • scraper: Add check for minimum housekeeping complete in scraper #1977 (@jamescowens)

  • voting: Fix nonsense vote weights for legacy polls #1988 (@cyrossignol)

  • voting: Fix incorrect field returned in ResolveMoneySupplyForPoll() #1989 (@cyrossignol)

  • consensus, accrual: Fix newbie accrual #2004 (@jamescowens)

  • log: grammar correction #2016 (@nathanielcwm)

  • wallet: Correct nMinFee fee calculation in CreateTransaction #2021 (@jamescowens)

  • rpc, miner: Correct GetLastStake #2026 (@jamescowens)

  • wallet: Fix bug in CreateTransaction causing insufficient fees #2029 (@jamescowens)


r/gridcoin • • Nov 29 '17

Gridcoin just passed 6 cents!

Post image
71 Upvotes

r/gridcoin • • Dec 27 '17

Get into Gridcoin for only $35! (using a Raspberry Pi)

70 Upvotes

Hello everyone, I am somewhat biased in my love for this coin but I thought I would put out a very simple guide on how YOU can get started "mining" Gridcoin for only $35! The title may be slightly misleading, but bare-bones this setup will only cost you $35. If you are missing a couple components or would like to add on optional components your total may be slightly higher.

Introduction

In case you are completely new to the coin here is a little background: Gridcoin is an open source cryptocurrency (Ticker: GRC) which securely rewards volunteer computing performed upon the BOINC platform in a decentralized manner on top of proof of stake. BOINC is a Berkeley open-source volunteer computing grid which combines the processing power of all individual users for the purposes of scientific research. It's free, production ready and many projects already harness volunteered computing power to attempt to cure cancer/AIDS/Ebola/malaria, map the Milky Way galaxy, crack Enigma machine codes, etc.

Basically, we mine for the greater good of science. We aren't just solving random hashes, or decrypting random strings like other cryptocurrency. All of our mining helps further science due to our association with BOINC. I believe this to be an amazing venture and a rare one in the crazy world of crypto. If you'd like to learn more feel free to visit both Gridcoin websites: here and here. Be sure to download the wallet on your computer of choosing as you will need a way for the pool to send you your Gridcoin :).

Components

Lets get started with a list of things you'll need, it's rather small (hence the $35), but it will require some setup:

  • A Raspberry Pi 3 Model B - you can find these online or in computer stores near you. Don't pay more than $35 for them. They are designed to be sold for exactly what they cost to produce. They're basically little baby computers that run a linux based operating system.

  • A spare micro-usb cord and charger. If you don't have one you can purchase them just about anywhere for around $5. Do make sure that it is a 5V 2A charger, or it may not supply enough power to your Pi

  • A spare micro SD card (4GB or larger). You probably have one of these laying around from when you first bought expandable smartphones, and until now, forgot it existed. If you don't, these can be had at your local computer store (or online) fairly cheap. Don't pay over $10 for one.

  • A borrowed keyboard and HDMI cable. After we finish this guide you will no longer need to use either of these two objects, so feel free to borrow them from some other computer or electronic device in your home.

  • (Optional) A case and heatsinks. The raspi 3 has been known to run a little hot. This is due to the Pi 3 already computing at max performance (hence why standard overclocking is not a feature on this model). While these options are completely optional I would recommend getting at least heatsinks for your Pi. They should run you around $3. Try to find them locally so you won't have to pay more for shipping the heatsinks than they are actually worth. A case is good if you don't want your Pi out in the open around children, animals, or your own fingers potential shorting something. Again, recommended, but not necessary. If you do make the plunge for a case, try to make sure to find one that will have room for the heatsinks or has good airflow through the case otherwise it can actually heat up the Pi more.

Now that we have all of our goodies together let's get started on the next steps.

Hardware Setup

Grab your microSD card and plug it into your computer (you may need to use a regular SD card adapter). Your computer should recognize it as an external storage device, but ignore that for now. It's time to download the official CLI operating system for your Raspberry Pi! Head on over to the downloads section on the Raspberry Pi's official website here to download the OS. Be sure to select "RASPBIAN STRETCH LITE". This is the most minimal version of the operating system possible (we want to have as many free resources for our Pi to crunch as possible). This version only contains a linux command line, so you may want to refresh yourself on some simple commands first. Once you've downloaded the OS image from the web you will need to flash it onto your microSD card. Windows does not come stock with any flashing software, so if you don't already have some you will need to download one. I recommend Etcher. This tool is extremely straightforward and guides you through the process of flashing your microSD card. Simply pick the image you just downloaded, select your SD card, and press flash! That's it! It may take a couple minutes, but once you are done with the flashing, we're ready to use our Pi! Finally, plug your microSD card into your Pi, plug in both your keyboard and HDMI cable and then attach the power. Your Pi should boot-up shortly on the screen you are using.

Setting up the Raspberry Pi

Ready for some Linux? Well, you don't have a choice. When your Pi initially boots up it will ask your for a username and password. The username is "pi" and the password is "raspberry" (I recommend changing the password, but we'll cover this shortly). Login and continue to the command line. Here you can choose to setup ssh onto your Pi if you never want to worry about connecting an HDMI/keyboard to it again. I won't include that in this guide as there a numerous excellent guides out there already on how to setup ssh onto your Pi(s). First things first, though. Let's make sure everything is up to date. You just installed a fresh OS so most likely everything is, but you never know. Type:

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade  

This will take a moment, but most likely it will come back telling you everything is up-to-date (better safe than sorry). Next up let's configure this Pi to eek out every bit of processing power we can. Type:

sudo raspi-config

This will bring you to the Raspberry Pi Software Configuration Tool. Here you can choose to configure your timezone, keyboard, and password. Remember to reboot after changing all of those. While this step is not required, it's suggested for security and ease of use if you ever want to contact your Pi later. Now onto the important settings. These include expanding the filesystem and memory splits. First, go to the advanced tab and select the Expand Filesystem option. Doing so will ensure your Pi has access to all of the memory on your microSD card. I'm not sure this helps performance in terms of BOINCing, but it's good to give your Pi free range on your microSD card. The next step is purely optimization. Since we are using the Command Line Interface (CLI) version of raspbian you have no need for memory allocated to your GPU. That memory would be better allocated to your CPUs where you will be doing the BOINCing. Open the advanced tab once again and select Memory Split. Change the entry from 64 to 16. This is the minimum you can allocate to your Pi's GPU and the rest will be assigned to the CPU.

Awesome, we now have a pretty well optimized Pi and we're ready to start BOINCing. Be sure to reboot (sudo reboot) to make sure all of your settings have been confirmed.

Setting up a pool account

For those of you not new to Gridcoin feel free to gloss over this section. However, for new users you will need to setup an account on the Gridcoin pool in order to start mining. The only Gridcoin pool currently in existance is https://grcpool.com/. This pool is pretty great, they have no fees and charge the network minimum on GRC withdrawals. Withdrawals are dispersed on a daily basis once your balance hits 1 GRC. Simply click the signup button on the upper right of the navigation bar on the website to start. Once you've signed up (takes about 30 seconds), you're good to go! Be sure to add your wallet's public address to your payout address so you can get paid! We'll need to return to our pool account later, so keep this page open on your laptop or whatever else you are using to help you with this setup.

Setting up BOINC and begin mining

Here we are! It's time for your little Pi to start crunching! First, let's install BOINC. You'll laugh at how simple it is. Type: sudo apt-get install boinc Let it download and extract the files and BOINC will start automatically. As an added bonus BOINC automatically runs on startup. So if you plan to move your Pi somewhere and just plug it into the wall, you'll be BOINCing on startup! Next, we need to sync with the pool. This will display your Pi as a device on the pool and allow you to select a project and start crunching for GRC. Type:

sudo boinccmd --join_acct_mgr https://www.grcpool.com/ "username" "password"

Boom, we're now synced with the pool. That was easy. Remember when I told you to keep your grcpool.com profile open on your laptop? Well, lets head back there. Refresh the page and click on the "Hosts" section. You should see your Raspberry Pi there now! Awesome. Click on your Raspberry Pi and you'll be presented with the Host Details/Project screen. There are only a handful of projects that support ARM optimization (the type of processor your Pi runs), so we'll choose one of those. Pick either Asteroids@Home, Collatz Conjecture, Einstein@Home, Enigma@Home, or Universe@Home. Feel free to read up on what each project is about, who sponsors the project, and what exactly your little Pi is doing! Choose which project you'd like to support, click add, save project settings, and you're ready to go. Now to head back over to your Pi. Sync it up with grcpool again and you'll start receiving work! Simply type:

sudo boinccmd --join_acct_mgr https://www.grcpool.com/ "username" "password"

Now, wait about 30 seconds to a minute and type:

boinccmd --get_simple_gui_info

Your tasks should now show up and your Pi will be crunching happily :). Finally, to make sure you are completely synced up with the pool, once again type:

sudo boinccmd --join_acct_mgr https://www.grcpool.com/ "username" "password"

Reload the pool website and make sure that the error stating your Pi is not synced properly is gone. If it remains, wait another 60 seconds and try syncing again. BOINC can be a little finicky, so don't get discouraged if it doesn't sync on the first try!

FAQ

Q: How many GRC should I expect per day/week with my Raspberry Pi?
A: Depending on which project you choose and whether you decided to run your Pi at 100% at full maturity (about 1 month) you'll receive somewhere between 0.3 - 0.4 GRC per day and about 2.5 GRC weekly! Not bad for a little fella!

Q: Will this fry my Pi?
A: Most likely it will not. Pi's are pretty amazing when it comes to withstanding heat and computing power. That being said, I can't guarantee your Pi will suffer no injuries and take no liability for any damage to your Pi.

Q: What if I don't want to run my Pi at 100% CPU load?
A: Totally possible, albeit slightly more complicated. You'll need to create a BOINC global_prefs_override.xml file and manually add your settings in there. For a list of all settings check out this wiki page. Checkout cpu_usage_limit and max_cpus. Those are the ones you'll want to edit. Once you've saved your changes type: "boinccmd --read_global_prefs_override" and they should take effect.

Q: But what about overclocking?
A: Well, the Raspberry Pi 3 does not support native overclocking since the cores are already running at almost maximum output. I do not recommend overclocking your Pi 3, but if you really want to you will need to do it manually. There are more than enough guides out on the web to help you with that, but be careful!

Conclusion

Well, there you have it. Your little Raspberry Pi should be happily crunching and helping solve scientific problems worldwide. How awesome is that? If you have any questions not covered in the FAQ feel free to drop a comment below. I'll be happy to respond.

Donations are never expected, but always appreciated. If you liked this guide feel free to send me some GRC here: S8AubU5WJrBwqtZ5LVGJ5VY5HgSWzsBATc


r/gridcoin • • Jan 13 '22

Gridcoin as a Universal BOINC Credit

67 Upvotes

Hi everyone! After almost four year of research, I am happy to present the final product! I've provided a short description of the results below for those who don't have the time or inclination to read the paper, which you can find here.

Basically, this paper designs a reward mechanism for BOINC computations from scratch. The goals of the reward mechanism are the same as the ones described by David Anderson in his paper giving an overview of BOINC, which I've reproduced below for your convenience:

  • be device neutral: similar jobs (in particular the instances of a replicated job) should get about the same credit regardless of the host and computing resource on which they are processed;

  • be project neutral: a given device should get about the same credit per time regardless of which project it computes for;

  • resist credit cheating: i.e. efforts to get credit for jobs without actually processing them.

The way that I've done this is by making an equivalence between the WUs of different applications. Interestingly, this method is actually a generalization of the way that Proof-of-Work cryptocurrencies allocate their rewards. The summary of this method is that crunchers will be rewarded proportionally to their contributions as much as possible, and where they aren't rewarded proportionally, it's because their hardware is stronger/weaker on the applications that they are crunching.

Also, there is an anti-cheating mechanism described in Section 5, which overall reduces the amount of energy consumption/increases WU throughput of the network.

In Section 6 is a market system where crunchers can virtually trade their hardware with each other, which addresses the tradeoff between the applications that crunchers like the most, and the applications which would reward them the most.

I also take a look at ways that the computations can be made carbon-neutral, which I think is important given the impact that fossil fuel consumption and carbon emissions have on the environment.

If you notice any substantive mistakes in the paper, I'd be happy to update it and give you credit in the acknowledgments (I just found one typo myself, ironically in the word "acknowledgments" all the way at the end, hahaha). Also, implementations of some of the ideas in this paper will require work of various forms, including academic-level research, and I would be happy to collaborate with anyone who is interested. There are a number of open problems that people can also work on by themselves/in their own groups, if they wish.

Also, in case they are reading this, I also wanted to thank parejan, nexusprime, and hotbit for their useful work and comments back in the Steemit days - if you want your names included, please contact me (although keep in mind I would want your full names, since I intend to submit this for publication in a peer-reviewed journal).

I would like to give my thanks again to Jim and Cy for all of their development of the coin in these past few years. I'm not sure I would have continued down this path if it wasn't for their hard work providing a foundation and setting a good example.


r/gridcoin • • Apr 04 '21

Gridcoin 5.3.1.0 leisure release

67 Upvotes

[5.3.1.0] 2021-04-04, leisure

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.3.1.0

This leisure release is part of the "Ingrid" milestone and contains a number of important fixes. It is highly recommended to upgrade as soon as practicable.

Some highlights:

  1. The beacon renewal chain walker fix (#2054) corrects a potential stall on restart if the accrual directory is rebuilt.

  2. Beacons are not supposed to be auto-renewed during the scraper active period to prevent problems with magnitude for renewed beacons on the following superblock. We actually saw this, where a researcher lost magnitude on the following superblock (only) due to a renewal that occurred while the scrapers were active, and traced it to an incorrect guard on the renewal. #2090 and #2092 fix this problem.

  3. Checkpoint based spam protection has been reimplemented (#2084) and we are now verifying hardened checkpoints on startup to catch some forked wallets better.

  4. Several GUI improvements, including better researcher status while out-of-sync to prevent confusion (#2068), and an update to translations.

  5. Memory optimization for the beacon db to "passivate" unneeded beacon elements from memory.

  6. Implementation of a new getburnreport RPC function.

The next release should have the requested "sync-from-zero" menu option to complement the "snapshot download" option already present.

Enjoy!

[5.3.1.0] 2021-04-04, leisure

Added

  • doc: Invite users to donate to Gridcoin Foundation #1997 (@smoe)

  • rpc: Add "getburnreport" RPC function #2049 (@cyrossignol)

  • gui: Add stats export reminder to beacon wizard auth page #2050 (@cyrossignol)

  • doc: Add undocumented "-showorphans" GUI option to help text #2058 (@cyrossignol)

  • beacon: Cull beacon db memory (passivation) #2069 (@jamescowens)

  • gui: Avoid refreshing GUI researcher status while out-of-sync #2068 (@cyrossignol)

  • consensus: Reimplement checkpoint-based spam protection #2084 (@cyrossignol)

  • consensus: Verify hardened checkpoints on start up #2087 (@cyrossignol)

Changed

  • test: autogenerate data headers #2030 (@div72)

  • doc: Change copyright years to 2021 #2042 (@caraka)

  • gui: Clarify overview page "stake" field #2056 (@cyrossignol)

  • doc: Update Copyright headers #2059 (@barton2526)

  • gui: Update Qt Linguist localization files #2063 (@cyrossignol)

  • build: update dependencies #2064 (@barton2526)

  • net: Reduce default connection limit back to 125 #2066 (@cyrossignol)

  • build: openssl patch #2074 (@barton2526)

  • translation: Translate /src/qt/locale/bitcoin_en.ts in pt_PT #2083 (@DjMVeiga)

  • log: Adjust logging #2076 (@jamescowens)

  • gui: Change scraper tab to Inconsolata monospace font #2085 (@jamescowens)

  • researcher: Change beacon deferment fix to reference nActiveBeforeSB #2092 (@jamescowens)

Removed

  • net: Clean up mandatory protocol version transition #2080 (@cyrossignol)

  • refactor: Remove LessVerbose() function #2089 (@cyrossignol)

Fixed

  • build: Fix depends cross-compilation for macOS #2038 (@cyrossignol)

  • build: Deal with Qt depends .qmake.stash file #2048 (@cyrossignol)

  • beacon: Fix a subtle error in renewal chain walker #2054 (@jamescowens)

  • researcher: Fix "malformed CPID" status for some pool projects #2052 (@cyrossignol)

  • lint: Misc Typos #2060 (@barton2526)

  • lint: remove identified duplicate includes #2061 (@barton2526)

  • gui: Fix splash screen block height progress #2057 (@cyrossignol)

  • gui: Fix garbage placeholders in some tx notification localizations #2070 (@cyrossignol)

  • build: Patch libzip to fix mingw compile regression for mingw 9.2+ #2082 (@jamescowens)

  • gui: Fix shutdown response for failed core init #2088 (@cyrossignol)

  • researcher: Fix deferment of beacon renewal in superblock window #2090 (@cyrossignol)

  • gui: Fix typo in beacon status refresh #2091 (@div72)


r/gridcoin • • Jan 11 '18

A Prime Number Could Be the Answer to Bitcoin’s Power Problem / Gridcoin Up Sixfold Since October

Thumbnail
bloomberg.com
67 Upvotes

r/gridcoin • • Apr 19 '21

Gridcoin gets listed on a new exchange

Thumbnail twitter.com
66 Upvotes

r/gridcoin • • Jan 09 '18

$0.20

65 Upvotes

New ATH :)

The higher it goes, the more idle processing power gets thrown at real-world problems. Not many other coins can say that!


r/gridcoin • • Aug 01 '22

Gridcoin 5.4.0.0-mandatory "Kermit's Mom"

64 Upvotes

[5.4.0.0] 2022-08-01, mandatory, "Kermit's Mom"

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.4.0.0

The Gridcoin core developers are proud to release 5.4.0.0 which represents the Kermit's Mom milestone. This is a mandatory release and includes the long- awaited implementation of Manual Reward Claims (MRC) and significant improvments to poll and project structures among many other enhancements and fixes.

Highlights

Manual Reward Claims (MRC)

The importance of this release to the community cannot be overstated. One of the most significant challenges to new "crunchers" joining the Gridcoin community is the payment of the 2nd layer crunching rewards to the crunchers for work they are doing for network approved BOINC projects. The implementation of constant block rewards (CBR) a number of years back improved the participation of wallets in the staking process dramatically, raising the average difficulty on the network from about 3 to greater than 18 today, representing more than 180000000 GRC continuously online and staking. This has drastically improved security of Gridcoin, making it much more resistant to 51% attacks, but has had the downside of increasing the effective minimum GRC required to solo crunch to 5000 GRC or more. Without MRC, which is in this release, solo crunchers are required to stake to get paid their rewards.

Most people regard having enough GRC to stake on average once a month is the practical minimum for solo crunching, so 5000 GRC is effectively the minimum bar for entry for solo crunching. Needless to say this is a giant challenge for many newcomers and greatly harms the growth of the network. The pools help with the problem by providing a way to earn GRC and eventually collect enough to solo crunch, but they have a drawback in that the project research when pool crunching is done in the name of the pool, not the cruncher. MRC sweeps that giant hurdle away. With MRC you can solo crunch with only about 1 GRC to start. You simply need enough to send a beacon advertisement (which is the new solo cruncher's way of letting the network know that they want to get rewarded for crunching). MRC will now allow a solo cruncher with an active beacon to request payment at intervals as small as 14 days from the last time they were paid. There is no minimum payment threshold, only the minimum time threshold. This request for payment is a "manual reward claim" request, which is where the name MRC came from originally. Note that what is going on under the hood is that the requester is sending out a "MRC" request contract that is attached to a transaction in the Gridcoin blockchain, which is picked up by the next staker, and causes the staker to stake the reward for the requester as a delegate. Essentially MRC is a form of delegated staking. Note that for this privilege the requester will pay a portion of their reward as a fee to the staker and the foundation. The total fee starts at 40% of the rewards at 14 days and then declines as 14/(number of days) as the interval between payments is increased. The foundation gets 80% of the fees and the staker 20%. These ratios were set and approved by official poll (id 651a3d7cbb797ee06bd8c2b17c415223d77bb296434866ddf437a42b6d1e9d89, https://github.com/gridcoin-community/Gridcoin-Tasks/issues/250).

To give a specific example, a new cruncher registers their beacon and starts crunching. They have a pretty good computer and their magnitude has been building to the point where at 14 days they have about 35 GRC pending as rewards. At 14 days after the activation of their beacon, the MRC payment button on the main screen will allow them to request payment of their rewards. If they press the button at 14 days, then the requester will get 35 * (1 - 0.40) or 21 GRC. The foundation will get 0.80 * 0.40 * 35 or 11.2 GRC and the staker will get 0.20 * 0.40 * 35 = 2.8 GRC. If the cruncher waits until 28 days to request the reward, lets assume his or her magnitude is constant, so the rewards have doubled, so now the requester has 70 GRC pending. If they press the button at 28 days, then the requester will get 70 * (1 - 0.20) or 56 GRC. The foundation will get 0.80 * 0.20 * 70 or 11.2 GRC and the staker will get 0.20 * 0.20 * 70 or 2.8 GRC. Notice that the effective fee to the foundation and the staker at 28 days is the same as at 14 days. This is by design. The foundation and staker fees decline as a percentage from the point of view of the requester's total rewards as the time between payment requests increase beyond 14 days, but from the point of view of the foundation and staker, the fees essentially are computed at the 14 day point and remain capped as absolute numbers.

The MRC request button will appear on the wallet main screen for crunchers with active beacons and will allow MRC requests once the block v12 functionality block height is reached. This is the post Kermit's Mom release hardfork point, and it will be at block 2671700, which will occur on or about August 31, 2022.

Some resources to review for MRC and related concepts:

Polls

Kermit's Mom has significantly improved both the rigor and functionality of the polling system. Poll categories were included in the GUI rewrite a while back, but those categories were GUI only and were not enforced by protocol at the blockchain level. At the Kermit's Mom hardfork block (2671700), polls will now use the poll payload v3 contract and associated protocol code, which will enforce and validate poll categories and the validation rules associated with them. Minimum poll duration and minimum vote weight percent of active vote weight, along with poll type requirements are now encoded and/or enforced by protocol. The GUI will display a "validated" tag for polls that have met validation requirements for their given poll type. Polls that fail validation requirements by the end of the poll will show "invalid". Polls with invalid combinations of poll type, duration, and poll weight type cannot be created and will also be validated by all nodes and rejected if an invalid combination is received.

Polls also support the inclusion of additional fields, and the PROJECT poll type now requires the additional fields of project_name and project_url in the poll. This is in anticipation of driving automated whitelisting functionality in a future release.

For more information, please see:

Projects

Kermit's Mom has implmented the inclusion of a GPPR controls required flag in the project structure. After the Kermit's Mom hardfork point (2671700), all project entries for the whitelist will require the GDPR protection flag to be set to either true or false to indicate whether the project requires the user to give permission for project statistics for that user to be exported. This is used to drive a new column in the projects tab table in the researcher (cruncher) wizard, and indicate a possible situation where a cruncher may not have granted the necessary permission.

For more information, please see:

libsecp256k1 port from Bitcoin Core

This one is not visible on the outside to anyone, but is a major improvement to Gridcoin's plumbing. @div72 did a fabulous job porting over Bitcoin Core's libsecp256k1 to Gridcoin. This replaces OpenSSL for all elliptic curve cryptography on the blockchain itself with Bitcoin's more efficient (and more secure) version. OpenSSL is now only used by the CURL library for https communication with external websites in the scraper project download. This will remain as CURL is well encapsulated and well maintained.

There were many other improvements and fixes that are in the Kermit's Mom release. Please refer to the change log below for details. This release was a group effort. Thanks to everybody who submitted a PR merged into the release. A special thanks to @barton2526 for doing many backports/fixes to the build system, Qt version bumps, and other utility backports. Thanks to @Pythonix for submitting backports and fixes to the network code. And thanks to @iFoggz for submitting enhancements to the scanforunspent rpc. A special thanks to m3prx for submitting the winning icon for MRC submission used in the GUI.

A teaser of the major feature to look forward to for the next milestone, LaVerne: HD wallet support! This is another long sought piece of functionality that will allow folks to store one keyphrase to regenerate all keys if necessary and provide the foundation for proper hardware based wallet functionality.

Jim Owens

[5.4.0.0] 2022-08-01, mandatory, "Kermit's Mom"

Added

  • test: Add TrimString(...) tests #2447 (@barton2526)

  • test: Add dead code detection #2449 (@barton2526)

  • test: Add explicit references to related CVE's in comments #2467 (@barton2526)

  • test: Add testing of ParseInt/ParseUInt edge cases with leading +/-/0:s #2470 (@barton2526)

  • consensus, contract, mining, researcher, rpc, staking, gui: Implementation of MRC - baseline functionality #2425 (@jamescowens)

  • consensus: MRC mandatory implementation code #2471 (@jamescowens)

  • test: Add upstream sync_tests.cpp #2481 (@barton2526)

  • net: Countermeasures against eclipse attacks #2454 (@Pythonix)

  • lint: add script to check for https violations #2491 (@div72)

  • util: Add flatpath BOINC data directory path resolution for Linux #2499 (@jamescowens)

  • gui: Add beaconExpired() to researchermodel #2498 (@jamescowens)

  • consensus: Add missing block nVersion check for v12 blocks in AcceptBlock #2502 (@jamescowens)

  • gui, util: Add AccrualChangedFromStakeOrMRC core signal #2503 (@jamescowens)

  • util: Change default -dbcache to 100 MB and also implement -txindexdbcache #2507 (@jamescowens)

  • rpc, util, consensus: Implement exception handling framework for MRC and fix ValidateMRC to deal with testnet consensus issue #2508 (@jamescowens)

  • gui: Initial implementation of GUI MRC submission form #2513 (@jamescowens)

  • build: Port over Bitcoin's translation docs #2439 (@jamescowens)

  • [2/3] build: integrate libsecp256k1 #2492 (@div72)

  • gui: New MRC request icon #2526 (@jamescowens)

  • mandatory, voting: Implement poll type validation in protocol #2522 (@jamescowens)

  • gui, voting: Implement poll additional fields gui components #2525 (@jamescowens)

  • gui, researcher: Add GDPR protection display #2527 (@jamescowens)

  • consensus, rpc: Kermit's mom hardfork (2671700) #2551 (@jamescowens)

Changed

  • net: Hard Coded Seed Node Cleanup #2427 (@barton2526)

  • script: Add More Generated Files to Gitignore #2435 (@RoboticMind)

  • gui: Update copyright year to 2022 for Gridcoin About dialog box #2443 (@jamescowens)

  • rpc: Change type field in ListTransactions to lower case #2441 (@jamescowens)

  • refactor: Replace memset calls with array initialization #2452 (@barton2526)

  • refactor: Changed some parameters from pass by value to pass by reference #2455 (@Pythonix)

  • ci, cd: improve caching #2461 (@div72)

  • contrib: port recent macdeployqtplus changes #2465 (@div72)

  • test: Test for expected return values when calling functions returning a success code #2464 (@barton2526)

  • build: Improve error message when pkg-config is not installed #2460 (@barton2526)

  • test: Bump shellcheck, mypy versions #2463 (@barton2526)

  • build: Update depends packages (expat, fontconfig, freetype, libXau, libxcb, xcb_proto, xproto) #2466 (@barton2526)

  • lint: run mypy over contrib/devtools #2475 (@barton2526)

  • build, lint: Remove x-prefix's from comparisons, Fix some shell script issues the linter complains about, Re-enable boost include checks #2478 (@barton2526)

  • test: Avoid copies of CTransaction #2479 (@barton2526)

  • ci: change windows CI to Focal, modify wrap_wine to use wine64 for 64bit binaries #2484 (@barton2526)

  • build: Qt 5.15.2 #2486 (@barton2526)

  • net: No longer send local address in addrMe #2459 (@Pythonix)

  • voting, gui, rpc: Enhance PollResult and AVW calculation to improve pool handling #2489 (@jamescowens)

  • [1/3] refactor: port some misc changes from upstream #2485 (@div72)

  • build: Try posix-specific CXX first for mingw32 host, Fix Windows cross-compiling with Qt 5.15 #2494 (@barton2526)

  • Improve upon scanforunspent rpc #2468 (@iFoggz)

  • rpc: Change tail_fee and head_fee to display in GRC rather than Halfords in createmrcrequest #2501 (@jamescowens)

  • scripted-diff: change http to https in copyright text #2504 (@div72)

  • qt, refactor: Use enum type as switch argument in *TableModel #2496 (@barton2526)

  • build, qt: bump Qt5 version to 5.15.3 #2510 (@barton2526)

  • utils: run commands using utf-8 string on Windows #2514 (@barton2526)

  • prevector: enforce is_trivially_copyable_v #2516 (@div72)

  • crypto: Unroll the ChaCha20 inner loop for performance #2515 (@div72)

  • gui: Modify VerifyTCPPort to use the status of CheckOutboundConnectionCount #2506 (@jamescowens)

  • gui: Fix transaction history table column size behavior #2520 (@jamescowens)

  • log: Use consistent wording in random.cpp log #2538 (@div72)

  • lint: Use newer versions of our lint packages, remove yq #2541 (@barton2526)

  • [1/2] validation: move CBlock validation methods to validation.cpp #2539 (@div72)

  • gui: Implement proportional column resizing for Addressbook with memory #2543 (@jamescowens)

  • build: remove redundant warning flags #2546 (@barton2526)

  • qt: Prefix makefile variables with QT_ #2547 (@barton2526)

  • build: remove build stubs for external leveldb #2550 (@barton2526)

  • build, refactor: Improve package version usage #2549 (@barton2526)

  • build: minor boost tidyups #2548 (@barton2526)

Removed

  • rpc, util: Remove caching from BlockFinder #2490 (@jamescowens)

  • test: remove obsolete check sig test #2552 (@div72)

Fixed

  • build: fix unoptimized libraries in depends #2428 (@barton2526)

  • build: don't use deprecated brew package names #2429 (@barton2526)

  • qt: fix shutdown on MacOS #2440 (@div72)

  • net: Do not add random inbound peers to addrman #2451 (@barton2526)

  • util: skip trying to set the locale on NetBSD #2448 (@barton2526)

  • build: change bundle id #2462 (@div72)

  • net: Do not propagate obviously poor addresses onto the network #2453 (@Pythonix)

  • ci: Fix CI build title to reflect that we are building for bionic, not xenial #2469 (@barton2526)

  • lint: Fix misc typos #2472 (@barton2526)

  • util: Fix crash when parsing command line with -noincludeconf=0, Properly handle -noincludeconf on command line #2473 (@barton2526)

  • build: Fix several minor linter errors #2476 (@jamescowens)

  • tests: Don't access out of bounds array index: array[sizeof(array)] #2480 (@barton2526)

  • script: Fix and Minify Icon SVG #2488 (@RoboticMind)

  • gui: Add missing null pointer check for m_beacon #2500 (@jamescowens)

  • util: Fix BN_zero macro in key.cpp for OpenSSL 3.0 #2497 (@jamescowens)

  • rpc, contract: Adjust ValidateMRC, CreateMRC, and createmrcrequest to correct provided fee handling #2505 (@jamescowens)

  • consensus: Move DoS into contract validators to allow variability of DoS based on context and further fixes to ValidateMRC #2512 (@jamescowens)

  • lockedpool: When possible, use madvise to avoid including sensitive information in core dumps #2509 (@barton2526)

  • refactor: Fix some minor linter complaints #2517 (@jamescowens)

  • miner: Miner Logger bug fix #2518 (@iFoggz)

  • key: properly parse short DER private keys #2519 (@div72)

  • researcher: Fix ReadClientStateXml() crash on wrong BOINC directory permissions #2524 (@jamescowens)

  • init: fix daemon forking #2521 (@div72)

  • scraper: Change open mode from append to truncate for auth file #2528 (@jamescowens)

  • gui: New mrc contract icon try #2 #2529 (@jamescowens)

  • gui: Remove white outlines on MRC icon #2530 (@a123b)

  • voting: Change m_additional_fields serialization #2531 (@jamescowens)

  • build, qt: Fix QMAKE_CXXFLAGS expression for mingw32 host #2537 (@div72)

  • logging: fix logging empty thread name #2535 (@div72)

  • trivial: fix comment in account header guard #2542 (@div72)

  • build: Restrict check for CRC32C intrinsic to aarch64 #2544 (@barton2526)

  • build: force CRCCheck in Windows installer #2545 (@barton2526)


r/gridcoin • • Apr 13 '22

My Gridcoin mining Rig ^_^

Post image
64 Upvotes

r/gridcoin • • Jan 21 '18

Observations from a newcomer

64 Upvotes

I just started mining Gridcoin and wanted to share some observations as a newcomer to the project. I want to preface these observations by saying I think Gridcoin is a very interesting project, and it feels much better to be doing real scientific work than just burning cycles crunching hashes. I used to be very active in BOINC back in the day, so this project is right up my alley. So take the following as it's meant, as constructive criticism :)

I recognize many of these issues are due to the somewhat crusty nature of BOINC and how Gridcoin has to layer on top of it. Also know that I'm a developer myself, so I recognize the following suggestions are non-negligible amount of work. Just my thoughts for potentially future improvements :)

Issue #1: The newbie's first 10 minutes is overwhelming and confusing

This is what I was confronted with trying to figure out Gridcoin:

  • Decide if I should solo or pool mine, or just "invest". The Gridcoin page pushes users to solo mine because of the comparison chart (checkmarks next to items like "keep 100% of profit", "earn 1.5% APR", "help decentralize the network", etc.) But it isn't until page three and many installation directions that the I realize a non-negligible amount of GRC is needed to "stake"

    • The page lays out a long list of hypothetical staking scenarios, although I'm not really familiar with how staking works in general so this is all quite confusing. After reading the hypotheticals and consulting Reddit, I realize you need 2000+ GRC to realistically stake, and I should pool instead. Still not quite sure how staking works.

  • So I backs up and start working on directions to join a pool

  • I install BOINC and Gridcoin. Easy enough

  • I'm running headless linux, so perhaps this is easier on other platforms. But after installing, I have to sync to the pool, login and assign a project, resync client, edit a password file and host whitelist, fight Boinc Manager for a while until I realize I also need to edit an XML file to allow remote connections, edit some more settings through the manager, resync and then I think everything is setup.

  • Repeat for other hosts

  • Still not entirely sure if everything is configured correctly, as the pool stats don't update very often re: RAC/Magnitude. Check back in a few hours to see if I messed anything up

Takeaway: the on-boarding experience is anything but smooth. I appreciate the grcpool videos, they were very helpful. But this is a lot of effort for someone wanting to dip toes in the water. I imagine many people take one look at the installation instructions and go back to one-click mining on other projects

Suggestion: Ideally, the newbie is directed towards the pool. They register, download a docker image, populate their user/pass and everything else is setup for them. This can all be automated reasonably easy in an image. They can read about staking/solo mining later and reconfigure if desired

Issue #2: Mining profit is opaque and difficult to estimate

I'll preface this by saying, yes, all work is good work since it helps science. But if I only cared about science, I'd just run BOINC directly (and collect all my stats). Since people are mining via Gridcoin we can assume they also want some kind of ROI on the electricity they are spending on science... even if minimal.

So with that assumption, mining profits are determined by magnitude, calculated by RAC, over the course of weeks. Furthermore, RAC is determined by project size/competition. It is close to impossible to estimate mining rewards.

  • Documentation says to choose a project with low team members and/or low team RAC... but it's not clear which (I suspect low team RAC because that's the actual output)

  • Docs say to choose appropriate project based on GPU/CPU. The project whitelist shows these criteria, but project stats don't. So you end up flipping back/forth between the two tabs trying to cross reference.

    • Suggestion: put hardware criteria on project stats page, allow filtering. Better yet, automatically assign newbies to the most profitable projects (e.g. least active) given their hardware criteria. The user can re-assign if desired based on project preference

  • Project stats give top RAC hardware options per project, but as far as I can tell you can't get the full list.

    • Suggestion allow the user to search/browse through full list to find their hardware

  • Somewhere I read that I should find similar hardware in the stats, then look up a user with similar to estimate GRC/day. This is difficult/confusing, is the user's RAC total or daily?

  • Magnitude takes ~month from what I've read to fully accumulate. Miners like to min/max their setup... waiting a month between optimizations is a non-starter (e.g. which project is best for my hardware).

    • Suggestion perhaps some kind of very simple calculator that can use hardware stats from the project to estimate GRC? Or perhaps some kind of benchmark mode that allows the user to sample all the projects to find best fit?

Semi-issue #3: Boinc software is, frankly poor

This isn't a criticism of Gridcoin, it's just the fact that BOINC is awfully crusty. It really shows as a project started in early 2000's by academics :)

I think Gridcoin would really benefit from building some Gridcoin-specific BOINC clients. I know this is a lot of work, but it would really help paper over the irritations of BOINC while also making the BOINC-Gridcoin integration a lot smoother.

Anyhow, just my thoughts, I'm sure others will disagree. I'll happily be crunching Gridcoin for a while, as I feel better doing this than hashing useless work. I'm just hoping we can make the experience smoother so more users can contribute to Boinc :)


r/gridcoin • • Dec 12 '17

Business Insider mentions Gridcoin as better alternative to Bitcoin - 12 DEC 2017

Thumbnail
businessinsider.com.au
64 Upvotes

r/gridcoin • • Jan 31 '18

Gridcoin meets his girlfriend's dad[Comic]

Post image
61 Upvotes

r/gridcoin • • Oct 19 '18

Release Gridcoin Mandatory Update 4.0.0.0 Released - CBR!

60 Upvotes

.

Well folks the day has finally come. Gridcoin's newest mandatory, 4.0.0.0, CBR is here.

Betsy is ready for showtime!

 

4.0.0.0 is a mandatory update for all users. This means you must update your wallet before the hard fork date or you will be left behind. The hard fork is set at block 1,420,000. This is approximately 20 days from now. We expect the hard fork to occur on either November 7th or 8th. Please update before then!

 

The biggest change in 4.0 is, of course our new block version, v10. This brings CBR (constant block rewards) to Gridcoin. Instead of earning 1.5% APR from Proof of Stake, every block will instead be worth a static 10 GRC. This change follows network consensus through three seperate polls with the aim to increase network difficulty, and by extension, increase the strength and security of the Gridcoin blockchain.

 

If you wish to see resources about how to optimize your staking for CBR, please see this excellent post by core developer @jamescowens.

 

Download the update from GitHub here.

 

Linux PPAs are now updated!

The Windows MSI can be downloaded here. Checksum.


Full changelog for the 4.0 release:

 

Added

Linux nodes can now stake superblocks using forwarded contracts,
#1060 (@tomasbrod).

Changed

Replace interest with constant block reward #1160 (@tomasbrod).
Fork is set to trigger at block 1420000.
Raise coinstake output count limit to 8 #1261 (@tomasbrod).
Port of Bitcoin hash implementation #1208 (@jamescowens).
Minor canges for the build documentation #1091 (@Lenni).
Allow sendmany to be used without an account specified #1158 (@Foggyx420).

Fixed

Fix cpids and validcpids not returning the correct data #1233
(@Foggyx420).
Fix listsinceblock not showing mined blocks to change addresses,
#501 (@Foggyx420).
Fix crash when raining using a locked wallet #1236 (@Foggyx420).
Fix invalid stake reward/fee calculation (@jamescowens).
Fix divide by zero bug in getblockstats RPC #1292 (@Foggyx420).
Bypass historical bad blocks on testnet #1252 (@Quezacoatl1).
Fix MacOS memorybarrier warnings #1193 (@ghost).

Removed

Remove neuralhash from the getpeerinfo and node stats #1123 (@Foggyx420).
Remove obsolete NN code #1121 (@Foggyx420).
Remove (lower) Mint Limiter #1212 (@tomasbrod).

 

Thank you to all our of dedicated developers for all the hard work and long nights that have gone into making this release a reality. Thank you also to all of the dedicated folks on testnet who have been so helpful in finding and helping solve critical issues before we released this massive overhaul. We couldn't have done this without your help.


r/gridcoin • • Nov 19 '22

Folding@Home Adapter Whitelisting

59 Upvotes

The Gridcoin community has long sought a way to be able to include other distributed computing domains in our rewards structure. (See https://github.com/gridcoin-community/Gridcoin-Research/issues/782 and https://github.com/gridcoin-community/Gridcoin-Tasks/issues/70.) Long ago there was an attempt to try and expose Folding@Home directly as a BOINC project, and it failed. Years later, all of the work done on the scraper (Denise milestone) and later the rest of the recode of the Gridcoin rewards framework (Fern+) prepared the network infrastructure in theory to support other computing domains, with Folding@Home the top of the list. There are limits to what the current wallet protocol can support at the current time though. After thinking through these limits and discussing the most efficient way to "hook in" Folding @Home, the core developers concluded the best approach would be to create an adapter that would act as a bridge between Folding@Home and the Gridcoin network. Cycy contemplated doing a heavier weight adapter that would act much like a BOINC project, requiring account registration just like a regular BOINC project, and then monitoring Folding@Home tasks and transforming that into BOINC project like statistics for the Gridcoin network to process. Cycy even created an informal (survey) poll to gauge interest in the community on this. (See the output of getpollresults 9af4b51f00841ab82f444c218c47b80d0c590098e6d0237fa02489652055cb83 in the wallet console, https://www.reddit.com/r/gridcoin/comments/jvephz/opinion_poll_should_gridcoin_reward_foldinghome/, and https://www.gridcoinstats.eu/poll/9af4b51f00841ab82f444c218c47b80d0c590098e6d0237fa02489652055cb83.) The results of that poll indicated very strong support by the community to create an adapter for Folding@Home. Unfortunately before Cycy could do the adapter, his priorities changed and he is no longer active. Fortunately Div72 has picked up the baton and done it! The adapter that Div72 has written is much thinner than what Cycy envisioned, extremely simple, and elegant and will work very well for the community. It has been in testing on Testnet for several weeks and is extremely stable. I will get into how it works later in this write-up, but first I want to discuss the whitelisting requirements that we apply to new projects. Although Folding@Home is different in many ways from a native BOINC project, we should discuss the requirements as applied to Folding@Home and do a whitelisting poll for Folding@Home.

The basic requirements for whitelisting are spelled out here: https://gridcoin.us/wiki/whitelist-process.html.

First let's discuss the basic whitelist requirements

Criteria For Being Considered

Project Work Availability Score (WAS) is green

  • Means that the seven day median new credit / the 40 day median credit is greater than 0.1

  • Checks that there isn’t a low amount of credit recently given out compared to its past.

Number of Zero Credit Days (ZCD) is less than or equal to 7 out of the last 20 days

  • Means that there can’t be more than 7 days out of the last 20 that the project didn’t give out credits

For both WAS and ZCD, while it is difficult to compute these statistics exactly in the manner of a BOINC project for Folding@Home, it is evident looking at the statistics available for the Folding@Home network at large that they have an enormous number of tasks available and consistently supply work to all of their active users. Folding@Home currently accommodates (or has accommodated) other cryptocurrencies/tokens like FoldingCoin and CureCoin with capacity to spare for thousands of other users. My position is that they more than meet these two requirements in practice.

The project has a clear description of the what it does and the project work is as described

Folding@Home's documentation is very good. (See https://foldingathome.org/?lng=en.) Arguably, it is better than most, if not all BOINC projects.

The project allows new user registration

This is self-evident. We also have a very simple approach to linking the Folding@Home user to the CPID, which I will detail below.

Project complies with the BOINC terms of service

All crunchers that comply with the terms of service of both BOINC and the project have equal access to work units

Folding@Home's Rules & Policies are very comprehensive and comparable to or better than the equivalent in BOINC in these two areas. See https://foldingathome.org/support/faq/rules-policies/?lng=en. This includes validation of work units.

My position is that effectively Folding@Home already meets the basic whitelisting requirements above.

Admin Contact

The project admin should reached out to and if they agree to wanting to be whitelisted, should say this somewhere public such as on a project forum, social media, etc. This should also say when they would like to be whitelisted. If it’s anytime, they should say that. If they want to wait x months, say for ramping up their servers, they should say that as well.

If they are not interested, please do not pester the project admin. Some admins aren’t interested and that’s ok. There are plenty of reasons such as server capacity concerns that are completely valid for why they wouldn’t want to be whitelisted

Cycy himself reached out to Folding@Home to discuss Gridcoin rewarding Folding@Home contemporaneously with the informal poll mentioned above (https://www.reddit.com/r/gridcoin/comments/jvephz/opinion_poll_should_gridcoin_reward_foldinghome/). Folding@Home raised no objection. They do not endorse any cryptocurrency (consistent with BOINC's position too), but they are happy to have more computing contributions.

This definitely meets the admin contact and approval requirement for whitelisting.

So... Folding@Home meets whitelisting requirements. Let's discuss how the adapter actually works.

Adapter Operation

The adapter is really super simple in operation. You set up the Folding@Home client on your computer following the instructions on the Folding@Home site and you set the username to the form <username>_GRC_<CPID> where the username is any username you choose and the CPID is your CPID registered with your Gridcoin beacon. You should also set up a Folding@Home passkey for your <username>_GRC_<CPID> username combination, as you get bonus credit for verifying ownership of your account on the Folding@Home side. The passkey is not required to get Gridcoin magnitude for Folding@Home contributions.

  • The adapter monitors the Folding@Home network for WU's completed by the CPID specified in the usernames and treats the points just like BOINC credits.

  • The adapter than constructs a RAC (Recent Average Credit) value for each CPID using the same 7 day half-life calculation that a normal BOINC project uses to convert changes in Total Credit to RAC.

  • The adapter then publishes the user statistics in the exact same way that a normal BOINC project does once per day for the scrapers to pull and process.

  • The scrapers then achieve a convergence on Folding@Home statistics in the same way as normal BOINC projects and include the generated statistics in the superblock each day.

In this way Folding@Home contributions are effectively treated as a BOINC project, and assigned a magnitude just like any other BOINC project based on participant's relative contributions.

The limitation of the adapter compared to a normal BOINC project is that you cannot create or register a CPID using the Folding@Home client or adapter. You must first set up another whitelisted BOINC project and go through the beacon verification process first to get a CPID that is linked to a registered (validated) beacon, then you can use that CPID in the Folding@Home client. This is a small limitation in my opinion, and greatly simplifies the operation of the adapter.

Centralization Concerns

The adapter is a centralization concern, but no more than the same issues we face with the project servers themselves. Since Folding@Home is treated as just one of many peer projects, the same comments about mitigation through the way we award magnitude with multiple peer projects apply here. Div72, the core developer that wrote the adapter, has graciously hosted the adapter in a secure VPS and in my opinion can be trusted to ensure its correct operation. He will be compensated for this hosting from Foundation funds just like scraper operators and other key community members operating basic infrastructure required for Gridcoin. (See the compensation channel on Discord for examples.)

Whitelisting Poll

An official Project Listing poll has been created for the community to vote on whitelisting Folding@Home through the adapter. (See https://www.gridcoinstats.eu/poll/1ab2a405a167f17869bae637bd6cba371d4ac37f09d3a9f9e7853f6de601a96b or preferably the poll in the native wallet as the metrics are more accurate.) The Gridcoin team is really excited to see this opportunity come to fruition and encourages the approval of Folding@Home whitelisting by the community. The Active Vote Weight percentage required for whitelisting a project is very high: 40%. To meet this requirement, everyone needs to vote. If you do not want to take a position, vote abstain. Your vote will still count for poll validation.

Jim Owens Lead Core Developer


r/gridcoin • • Jul 27 '21

Last year I published my draft template for a gridcoin / boinc flyer. Recently I found that design on a sticker at my university's bathroom wall :)

Post image
59 Upvotes