Menu
The Chia Plot
  • Blog
  • How-To
  • About
  • Contact
  • Security
  • Discord
The Chia Plot

People are losing Chia farming rewards – make sure you aren’t one of them

Posted on August 20, 2021August 20, 2021 by Chris Dupres

If you spend any time in the Chia focused communities, like Reddit or the discord servers managed by the Chia Pools, you will see a re-occurring problem come up that people have while Chia farming for on chain pools. People on the new on-chain pools are farming blocks but not receiving their 0.25xch.

It looks like there are a couple things going on here, so we are going to talk about each of them but they all boil down to one thing: the farmer reward address and the config.yaml file. In a nutshell, no matter what keys or wallet you are using when you farm a block your client will include the xch_target_address value from your config.yaml file in that block and the 0.25xch farming reward portion will go there. The pool will claim the 1.75xch pool reward and sort that out if you are farming with a pool, but you could lose out on a big part of your reward if you have the xch_target_address set wrong even with a pool. The whole thing is at risk if solo farming.

Go check it out right now, its worth it. On Windows it is kept at C:\Users\%USERNAME%\.chia\mainnet\config\config.yaml and on Linux it is at /home/<username>/.chia/mainnet/config/config.yaml. You will probably find two xch_target_address values in your file, one near the ssl settings towards the top and one in each NFT settings for your on chain pooling information. The top one is where your 0.25xch will go, the bottom ones is where your client will register your reward address with your pool and your pool rewards will go by default.

So what is happening to people? Are they being hacked? Maybe, but probably not. It looks like are two main things going on: the first is that users who have or have had multiple keys on their system are farming to their second key with the farming rewards set to the first. This is actually a preferred security architecture, farming to a wallet not accessible to your farming machine. It is nice to know its setup like that. That’s what happened to this reddit user here, and I have seen a lot of users find their missing XCH in another wallet they control.

The second situation might not be such a pleasant outcome. The OG pools, like Hpool (EDIT: it has been brought to my attention that Hpool’s client uses a different mechanism to capture rewards and is likely not changing xch_target_address) and Core-Pool, work by using a custom client to change your reward address to one they control. Foxypool doesn’t do this and the farmer keeps the 0.25xch reward, but the other custom pools do pool the entire 2xch reward. Because of this while you have their software installed they redirect all block rewards to their wallets and then split them up amongst their farmers. So people are finding that even after they have left their OG pool and joined an on-chain pool that they still lose their farmer reward portion when they farm a block.

I spoke a little bit about this to the developer of Core Pool, and he said they have absolutely seen this problem. That they go to great lengths to prevent it from happening but that it still can. He says they have had a “Leave Pool” option in their software that puts everything back to normal using a config_bak.yaml file they create during original installation but that there are situations where a farmer doesn’t activate that functionality by losing power or turning windows off without closing the software it won’t properly revert the address. The other situation that can be shocking to people is if they are farming both Core-Pool and NFT plots to an on-chain pool the Core-Pool client will capture the farmer reward portion for Core-Pool regardless of which plot wins the block. But they are dealing with this too, they are sending the 0.25xch back to their farmers and their newest software version will automatically handle that portion. They have also been returning rewards to people who contact them and they really do seem to be trying to sort this out for their users.

So this is a real problem but it doesn’t largely seem malicious. The Core-Pool team seems on top of it at least, my understanding is that Hpool is also supporting users with integrity when it comes to this issue but I have not spoken to them. But it easily could be malicious and this is why you need to pay attention to your computer and network security while farming Chia.

Because of the nature of how permissive the Chia client is with both its certificates and its config files there is a LOT of opportunity for malicious software, let’s say a random Chia Fork among many, to make changes to the Chia config file. It will have the permissions to do so during installation, or when run. There is literally nothing stopping a Fork or someone like Mad Max from doing this other than integrity. This is why I think its so critical for projects like Nucle and that a proper Chia client be developed. As long as the reward address is pulled from a config file that anyone can edit it will be at risk. Either from accidental issues by honest actors, or deliberately by malicious developers.

Related

5 thoughts on “People are losing Chia farming rewards – make sure you aren’t one of them”

  1. aitorserra says:
    August 24, 2021 at 5:44 am

    Hello! I checked my xch_target_address and found that isn’t my wallet address, but I’m getting pool payments anyway. Do I have anything to worry about that? Thank you.

    Reply
    1. Chris Dupres says:
      August 24, 2021 at 5:54 am

      Your wallet can have multiple addresses. So it can be ok that way too!

      Reply
  2. X400 says:
    August 31, 2021 at 7:15 am

    Just checking if I’m understanding this correctly, if I’m farming with a pool, and I farm a block, I get 0.25xch of that 2xch

    But if I wasn’t in a pool, and straight solo farming I’d get 2xch?

    I was a bit confused reading some other posts saying we have to claim 1.75xch or else it goes to the pool

    Reply
    1. Chris Dupres says:
      August 31, 2021 at 7:18 am

      If you are farming nft plots solo 0.25xch will go to your wallet and 1.75xch will go to your NFT, which you will have to claim and then they will transfer to your reward wallet.
      If you are in a pool the pool handles the 1.75xch claim process and distributes that to everyone, but you still get the 0.25xch.

      Reply
      1. X400 says:
        August 31, 2021 at 11:21 am

        Great thanks for clearing that up!

        Reply

Leave a Reply Cancel reply

Advertisement

Recent Posts

  • Crypto is burning down – Chia seems fine
  • Chia CAT upgrade fiasco part 2 – Was I wrong?
  • WTF just happened?? CAT1 to CAT2 “upgrade”
  • The era of the Chia NFT is upon us
  • Chia Blockchain 1.4.0 released – NFTs and DIDs oh my
  • Discussion
  • Facts About Farmers
  • How-To
  • Information
  • News
  • pools
  • Security
  • Trademark
  • Trading
  • Uncategorized

Dark Mode Switch

©2021 The Chia Plot - Donate XCH / MRMT / SBX @ xch1p4440d6zwu9ryta2vx073lq2ge3s29d37kskz6t34jp085e8srjqnk0gcr
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
Cookie SettingsAccept All
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-advertisement1 yearThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
JSESSIONIDsessionUsed by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
na_id1 year 1 monthThis cookie is set by Addthis.com to enable sharing of links on social media platforms like Facebook and Twitter
na_rn1 monthThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_sc_e1 monthThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_sr1 monthThis cookie is set by Addthis.com. This cookie is used for sharing of links on social media platforms.
na_srp1 minuteThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_tc1 year 1 monthThis cookie is set by the provider Addthis. This cookie is used for social media sharing tracking service.
ouid1 year 1 monthThe cookie is set by Addthis which enables the content of the website to be shared across different networking and social sharing websites.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
d3 monthsThis cookie tracks anonymous information on how visitors use the website.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThis cookie is set by Google and stored under the name dounleclick.com. This cookie is used to track how many times users see a particular advert which helps in measuring the success of the campaign and calculate the revenue generated by the campaign. These cookies can only be read from the domain that it is set on so it will not track any data while browsing through another sites.
_ga2 yearsThis cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
_gat_gtag_UA_199099757_11 minuteThis cookie is set by Google and is used to distinguish users.
_gid1 dayThis cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
CONSENT16 years 4 months 5 daysThese cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
advanced_ads_browser_width1 monthThis cookie is set by Advanced ads plugin.This cookie is used to measure and store the user browser width for adverts.
anj3 monthsNo description available.
CMID1 yearThe cookie is set by CasaleMedia. The cookie is used to collect information about the usage behavior for targeted advertising.
CMPRO3 monthsThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMPS3 monthsThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMRUM31 yearThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMST1 dayThe cookie is set by CasaleMedia. The cookie is used to collect information about the usage behavior for targeted advertising.
DSID1 hourThis cookie is setup by doubleclick.net. This cookie is used by Google to make advertising more engaging to users and are stored under doubleclick.net. It contains an encrypted unique ID.
i1 yearThe purpose of the cookie is not known yet.
IDE1 year 24 daysUsed by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
KADUSERCOOKIE3 monthsThe cookie is set by pubmatic.com for identifying the visitors' website or device from which they visit PubMatic's partners' website.
KTPCACOOKIE1 dayThis cookie is set by pubmatic.com for the purpose of checking if third-party cookies are enabled on the user's website.
mc1 year 1 monthThis cookie is associated with Quantserve to track anonymously how a user interact with the website.
test_cookie15 minutesThis cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
uid1 year 1 monthThis cookie is used to measure the number and behavior of the visitors to the website anonymously. The data includes the number of visits, average duration of the visit on the website, pages visited, etc. for the purpose of better understanding user preferences for targeted advertisments.
uuid3 monthsTo optimize ad relevance by collecting visitor data from multiple websites such as what pages have been loaded.
uuid23 monthsThis cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements.
VISITOR_INFO1_LIVE5 months 27 daysThis cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
YSCsessionThis cookies is set by Youtube and is used to track the views of embedded videos.
yt-remote-connected-devicesneverThese cookies are set via embedded youtube-videos.
yt-remote-device-idneverThese cookies are set via embedded youtube-videos.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
__gpi1 year 24 daysNo description
adImpCountpastNo description
C3UID5 yearsNo description available.
C3UID-9245 yearsNo description
fc5 months 27 daysNo description available.
pfpastNo description
pxs5 months 27 daysNo description available.
SAVE & ACCEPT
Powered by CookieYes Logo