FAQ

General​

What are harvesters, farmers, full nodes, and timelords?​

You can read about each of them and the architecture in the Architecture Overview page. The Consensus Intro page is the most current documentation, however.

What is a proof of space?​

A proof of space is a proof that a farmer has allocated a portion of their storage in a way that is very difficult to create in real-time but efficient to pre-compute and store on a hard drive. The Chia Proof of Space Construction document goes deeply into the math and implementation considerations to mitigate Hellman's Time - Memory tradeoff problem. A plot is a large set of proofs of space. A harvester can harvest multiple plots on the same machine. A farmer can then control multiple harvesters across many machines to manage the whole "farm".

Farming uses substantially less electricity than Proof of Work for the same unit of security. You can learn more at chiapower.org.

What is a VDF/proof of time?​

A VDF, also known as a proof of time, is a sequential operation that takes a prescribed amount of time to compute (and which cannot be accelerated by parallelism) and which produces an accompanying proof whose result may be quickly verified. This must be done in a group, for which Chia uses ideal class groups. You can learn about them in our class group document. Timelords usually run three VDFs at a time for the three internal blockchains of the Chia blockchain. They run as vdf_client processes.

What is a genesis challenge?​

A genesis challenge is the first VDF challenge on a network that uses the Proof of Space and Time consensus. For more info about the genesis challenge for Chia's mainnet, see the consensus section of this website.

What is XCH, TXCH, and mojos?​

XCH is the currency symbol for Chia. TXCH is the currency symbol currently being used for testnet chias. TXCH has no value and is only used for testing purposes. Chias and testnet chias can be divided up to 12 decimal places (trillionths). The smallest unit of chia, a trillionth of a chia, is called a mojo, as a tribute to Mojo Nation, a decentralized file storage platform created in the early 2000s by Zooko Wilcox, Bram Cohen, and others.

Chia vs XCH vs mojo vs chia​

• Chia - uppercase Chia depending on context, this can refer to Chia Network the company, the Chia software (Chia client), or the Chia blockchain.
• XCH - refers to the Chia token, XCH.
• mojo - a trillionth of an XCH.
• chia - lowercase chia refers to the Chia token, XCH. Similarly, mojos are lowercase.

You can select either General Chia News or Developers News or both to receive emails about those topics.

How do I contact Chia with more questions?​

You can email us at [email protected] or join us on Discord.

Please note that for support with Chia, we do not offer 1:1 direct support. All support is provided via our discord #support channel.

Will the average person be able to use Chia as a payment instrument?​

Our hope is that, over time, Chia will be supported by point of sale systems and consumer payment apps all over the world. For example, if you pay for a coffee at Tully’s in England with your GrabPay app from Thailand, it should “just work” without you needing to know it was paid in Chia.

Or, for example, if services like Venmo or Cash App aren’t available where you live, using Chia will be far less of a hassle than executing a slow and expensive wire transfer. Using legacy banking to send and convert cash across borders is cumbersome, slow and expensive, and while alternative money transfer services might be faster, they’re not cheap: Western Union can charge upwards of 10% in transfer fees.

The technology is completely open source and accessible, and anyone can build a new wallet without our permission or assistance. However, we intend to help wallet, exchange, and merchant processing partners with support and integration services, joint marketing and lending for liquidity.

Why are you named Chia?​

We’re green money! Our founder Bram Cohen started the company knowing he wanted to reduce the energy dependence of blockchains through a “green” option. The concept of farming seemed to be the best metaphor for filling unused disk space and monitoring it for winning sprouts. This led us to look for a grain that had the properties we wanted to embody with our new Network. The team wanted a name that would be short and impactful. Everyone was amused that it was also a grain associated with a whimsical meme. Chia Network was born.

Is the value of Chia going to be as volatile as other cryptocurrencies?​

We believe that Chia coins will be less volatile than other cryptocurrencies due to the planned nature of our planned public company status which will allow financial institutions to hedge and leverage coins and equity. Initially, we expect Chia Network to largely be valued based upon the valuation of the chia that the Company will hold on its balance sheet. Movements in the price of chia on digital exchanges are likely to be mirrored by price movements in the price of our stock on a stock exchange. There will be more ways to get exposure to the success of chia than traditional blockchain projects. This will also allow the usual options and derivatives to our stock to be used as something like a synthetic derivative for the price of chia coins. Additionally, our ability to use the Chia Strategic Reserve may reduce some volatility of chia in the market.

Why does Chia run competitions?​

We believe that more eyes on our code will only make it better. For example, the results of our VDF Competition produced a VDF implementation whose runtime was 80% faster than our original implementation.

Where has Chia advanced the state of the art in applied cryptography?​

Chia has created three new core inventions and advanced the interest in, and adoption of, a fourth. Firstly, Chia created the first intended for production BLS Signatures library. Second, Chia is the first production use of Verifiable Delay Functions, or VDFs. Third, Chia created Proof of Space and Time for Nakamoto consensus.

Finally, Chia is the first production use of class groups of unknown order which has spawned significant new research into their applicability to cryptography.

Does Chia use Bitcoin's code?​

No. Chia is written entirely from scratch with a custom form of Lisp called Chialisp.

Chia also advanced applied cryptography as described above.

Isn't Bitcoin good enough?​

When Bitcoin was developed, it was not foreseen that specialized hardware could vastly outperform the computers that everyone owns. What was intended to be a decentralized network is now controlled by a small number of miners with access to chip fabrication plants and wholesale electricity purchasing (or worse). The miners who currently control the Bitcoin Network feel they have a competitive advantage as is and oppose changing the protocol even when it’s clear that it should be changed. Chia has had ten years to study the new digital money ecosystem and believes we can make cryptocurrency more decentralized, more secure, and easier to use.

What is Chia's inflation?​

After the Chia pre-farm, Chia offers farming rewards of 64 chia every 10 minutes. Over the first 12 years the farming rewards will be halved at the end of each 3rd year. From year 13 to infinity, the rewards will remain constant at 4 chia every 10 minutes leading to ever decreasing inflation rates. Chia’s inflation falls through the 0.50% rate 22 years after mainnet launch. More information can be found in our halving schedule

Where is the Chia source code?​

The Chia Blockchain comes together from a few different repositories:

RepositoryContents
chia-blockchainConsensus code, networking, and reference Chialisp implementations.
chia-blockchain-guiAn Electron/React graphical user interface to the plotter, node, and wallets.
clvmChialisp Virtual Machine in Python
clvm-rsChialisp Virtual Machine in Rust for security and performance.
chiaposCreating plots and verifying Proofs of Space.
chiavdfProofs of time/VDFs and Timelords.
bls-signaturesIETF standard BLS-12-381 signature scheme.
clvm_toolsTools for Chialisp and CLVM.
Chia Network OrganizationContains all of the public Chia repos released by Chia Network

When did Chia launch mainnet?​

Chia launched mainnet on March 19, 2021. You can follow along with code updates across our many repositories outlined here

What is the Chia Strategic Reserve?​

Chia has a novel business model to both, lower volatility of the coin and increase adoption. By loaning Chia and managing the interest rates of those loans as well as other tools like buying our stock with chia coins, we hope to lower the quarter to quarter volatility of the coin. To drive adoption, we intend to loan Chia to Global 5000 companies who will use it to pay their international vendors quickly, less expensively, and more securely. We also intend to use the strategic reserve to aid development and adoption. We plan to do things like invest in promising startups in the Chia ecosystem, potentially increase farming rewards during limited periods of time to spur additional farming, and fund corporations paying 105% of the value of their international payables in Chia instead of fiat currency.

Chia Network Inc created 21 million chia at mainnet launch. This is known as the Strategic Reserve. For details on the Company’s plans for the Strategic Reserve, see page 20 of the Business Whitepaper.

Did Chia have an ICO?​

No. Chia did not have and is not planning an ICO. Instead, our goal is to take the company’s equity public on an American stock exchange. This way, shareholders can share risk and return with management with transparency and disclosure while we use well understood corporate controls to make binding statements about how Chia Network intends to use the Strategic Reserve. The chia coin (XCH) is meant to be a useful payment instrument and not an investment opportunity. Chia intends to complete a fully compliant SEC registered equity IPO and will come to market as market-timing is amenable.

Why do I want to farm Chia?​

You can farm Chia on the unused storage of your laptop, desktop, or corporate network and, in return, you have the chance to receive rewards in chia for helping secure the blockchain. Our software allows you to allocate a certain amount of unused disk space to create plots. Since the only resource intensive step is the initial plotting, once you download the Chia node software, your drives will be plotted in the background. Once plotting is complete, your computer will begin farming on your behalf and the software does all the work and tracks your rewards for you. Ongoing farming uses very little network bandwidth and almost no resources other than storage. By making the farming process available to anyone with unused disk space, we are moving towards our goal of a truly decentralized blockchain that will also serve as a cross subsidy to the storage and cloud industry. Visit our Farming Basics doc to get started.

What is the Chia Network Strategy?​

It is our belief that the blockchain industry is still led by developers. We intend to be the superior chain for deploying new applications and services as well as being the only serious and secure choice for applications like sovereign backed stable coins. The Chia Network business will be the first for profit company that manages a pre-farm and we intend to be the first publicly tradable “near ETF” cryptocurrency. We believe that - as Redhat and MySQL AB were necessary to drive corporate adoption of linux and mysql - we will be the source for support and training as sovereigns, financial institutions, and corporations look to use cryptocurrency in daily commerce. Finally, we believe that we will be able to leverage the storage ecosystem to drive adoption at corporations and end users as hard drive manufacturers and storage server sellers are likely to bundle space farming into their offerings.

Our Business Whitepaper is the definitive document on our strategy and approach.

Details can be found on the Consensus page of our docs site.

What is the difference between mining and farming?​

Mining requires expensive single use hardware that consumes exorbitant amounts of electricity. We are mitigating this problem through a fair, eco-friendly, and better blockchain that uses farming to leverage existing empty hard disk space distributed on nodes around the globe. Farming remains decentralized because anyone that has installed our software and has plots can win the next block. Mining requires expensive custom single use hardware and access to electricity at wholesale or better prices which only purpose built corporations can afford to mine. Farming is more decentralized because it relies on empty hard disk space and anyone with a mobile phone, laptop, or corporate network tends to have extra space not currently being used. Unlike mining, once you’re done farming your storage you can repurpose it to, for example, store your family photos.

For more information we have this blog article, or you can refer to our Farming and Plotting docs.

Documentation can be found at Chialisp.com.

Why is Chia better?​

Chia has a new innovative Nakamoto consensus algorithm, Proof of Space and Time, that removes the energy demands of Proof of Work from the system. Compared to other cryptocurrencies, Chia has significantly better security due to its more decentralized blockchain by Nakamoto Coefficient. Chialisp is Chia’s new smart transaction programming language that is powerful, easy to audit, and secure and will unlock the security, transparency, and ease of use that cryptocurrencies promise. Chia is also adopting more modern cryptographic tools to enable richer smart transaction capabilities. Chia is taking a new and superior approach to funding, building, and supporting a blockchain via an eventually public, for-profit, open source development company that holds a pre-farm. Chia will use its Strategic Reserve to ease the volatility of the coin to mitigate bubbles and crashes and to drive adoption of chia.

What is Proof of Space and Time?​

Chia developed a new innovative Nakamoto consensus algorithm, Proof of Space and Time, that eliminates the energy demands of Proof of Work while maintaining and in some cases enhancing security.

Proof of Space is a cryptographic technique where provers show that they allocate unused hard drive space for storage space. In order to be used as a consensus method, Proof of Space must be tied to Proof of Time. PoT ensures that block times have consistency in the time between them and increases the overall security of the blockchain.

What is Chialisp?​

Chia has a newly developed, innovative blockchain programming language called Chialisp.com, which is powerful, easy to audit, and secure. Chialisp is a superior on-chain smart transaction development environment that will unlock the security, transparency, and ease of use that cryptocurrencies promise.

How does Proof of Space and Proof of Time work?​

Proof of space can be thought of as a way to prove that you are keeping some storage unused on your hard-disk drive. Users of the Chia blockchain will “seed” unused space on their hard-disk drive by installing software which stores a collection of cryptographic numbers on the disk into “plots.” These users are called “farmers.” When the blockchain broadcasts a challenge for the next block, farmers can scan their plots to see if they have the hash that is closest to the challenge. A farmer’s probability of winning a block is the percentage of the total space that a farmer has compared to the entire network.

Proof of time requires a small period of time to pass between blocks. Proof of time is implemented by a Verifiable Delay Function that takes a certain amount of time to compute, but is very fast to verify. The key idea of a VDF is that they require sequential computation, and since having many parallel machines does not yield any benefit, electricity waste is minimized. There will likely be relatively few VDF servers (“Timelords”), as the fastest one will always finish first and it takes only one fast and fair Timelord on the network to complete a block and move the chain forward.

You should first read through the Chia Introduction and docs FAQ, check out the wealth of information on our docs site and join us on discord in the #support or #general channels. We have also created a good summary of the basics of creating plots for Chia.

What is Chia?​

Chia was incorporated in August of 2017 to develop an improved blockchain and smart transaction platform. We are building the Chia Network to improve the global financial and payments systems. Chia is the first enterprise-grade digital money. Chia is using the first new Nakamoto consensus algorithm since Bitcoin. Called Proof of Space and Time, it was created by Bram Cohen, the best network protocol engineer alive and the inventor of BitTorrent. Chialisp is Chia’s new smart transaction programming language that is powerful, easy to audit, and secure. Reference smart transactions currently available are: atomic swaps, authorized payees, recoverable wallets, multisig wallets, and rate-limited wallets.

What is the official Chia Network DID used for NFTs?​

From time to time, Chia Network may release NFTs for a variety of reasons, such as our inaugural Chia Friends collection. Any NFTs minted by Chia Network will use our official DID: did:chia:19qf3g9876t0rkq7tfdkc28cxfy424yzanea29rkzylq89kped9hq3q7wd2. Always check the provenance of an NFT purportedly to be official from us by looking for this DID as the minter. Fortunately, the majority of 3rd party platforms are designed to automatically show the Chia Network name and/or logo with these NFTs, but it never hurts to double check!

What makes Chia different from proof of work blockchains?

One core difference is the consensus algorithm called proof of space and proof of time. Basically as after the farmer creates a proof of space and a block, other computers called timelords add proofs of time to the block, which is a cryptographic proof that says that a certain amount of time (like 30 seconds) has passed. So instead of the whole world mining at the same time, only a few computers are "mining" for each proof of space that won. Since these are all cryptographic proofs, they cannot be forged or broken, making the consensus extremely secure.

In Chia, the only electricity required is the electricity to create the plots, and to run the hard drives, which is on the order of 10 watts to power, plus CPU power required to run a full node (which is very light). In comparison Blockchains like Bitcoin and Ethereum rely on huge farms of GPUs ( 300W each GPU), or ASICs (hundreds or thousands of watts per machine) to secure the blockchain. You can think of proof of work, as millions of computers "making" lottery tickets by using electricity, but each ticket can only be used once. Chia will use vastly less electricity as each plot will last over 5 years, and the only electricity required is the initial setup (plotting) and 10W for farming a drive.

xch1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqm6ks6e8mvy

txch1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqm6ksh7qddh

Chia addresses are puzzle hashes encoded into the "xch" prefix address format using the bech32m encoding scheme.

A traditional bech32m puzzle hash for a burn address is all zeros ending in "dead": 0x000000000000000000000000000000000000000000000000000000000000dead

Converting this to an address, you end up with the burn address for mainnet: xch1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqm6ks6e8mvy

The testnet burn address is different: txch1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqm6ksh7qddh

You can use a puzzle hash converter to verify these burn addresses for yourself.

A burn address is an address whose private key (24 words) is unobtainable. There's no feasible way to determine the key for the above burn addresses. This means anything sent to a burn address is inaccessible forever, aka "burned."

Thank you to r/chia member juraj for this information.

How does the transactions_generator work?​

Some important changes went into the transactions_generator code with the 2.1.0 hard fork. These changes are detailed in the Block Format page.

Plotting​

What is k?​

"k" is the space parameter that controls the size of plots. It is an integer for the following equation: plot_size_bytes = C1 * 2^k(k + C2) where C1 is constant 1 and C2 is constant 2. In practice this means that final size is roughly ((2 * k) + 1) * (2 ** (k - 1)) * 0.78005 though that constant is estimated. You can examine the Space Required section of the Chia Proof of Space Construction document for the calculation of how much space is required for a given k.

note

Prior to Chia 2.0, the estimated space constant factor of 0.762 slightly incorrect. This led to a netspace calculation that was lower than the actual netspace. To correct this, we have updated the constant factor to 0.78005.

How big are plot sizes (k)?​

You can see some example plot sizes, times to plot, and working space needed based on various k's in these k size tables. Current working space needed for the default plotting options of a k=32 is 239 GiB and the final file is approximately 101.4 GiB. There is small natural variation in temp space needed and the final file size of each plot. Note that 239 GiB is 256.6 GB.

What k-size should you plot?​

The minimum plot size is k=32. There is only one reason why you might want to plot larger than k=32: to maximize the total utilization of a given drive or space. A couple of k=33 plots with a majority of k=32 plots can reduce the amount of leftover unused space on a drive.

The reason k=32 was chosen as the minimum plot size was to prevent a short-range replotting attack, which is detailed in our consensus doc. The gist of the attack is that if someone can create a plot in less than ~30 seconds, they could create a new plot that passes the filter for each signage point, and then delete the new plot immediately afterward. This would effectively emulate storing 512 plots, thus turning Chia into PoW.

• Note that this attack does not create a winning plot; it only creates a plot that passes the filter.

This attack won't be economically feasible for some time, if ever. Two potential mitigation techniques are to lower the plot filter (thus reducing the benefit of the attack), or to increase the minimum plot size (thus making the attack more difficult to perform).

k=32 is expected to be the minimum plot size until at least 2026. If and when that size is increased, you will be given ample notice to replot before the change is made effective.

We think you will want to use used Data Center grade NVMe SSD drives to create your plots. Regular consumer NVMe SSD generally has too low of a TBW rating. One of our community members keeps this handy SSD Endurance page up to date so you can compare various SSDs. You should never use your root/OS SSD to plot as it can lead to drive failure and loss of booting. You can plot directly to hard drives and get good results, especially if you plot in parallel to different drives. You can use non-root SSD over Thunderbolt 3 and migrate your plots off to whatever storage you want to keep them on long term. You could even load them on a Raspberry Pi 4 with outdated USB 2.0 drives attached and they will harvest and farm just fine. PC World offers this great background on current storage technologies but this graph gives you a quick view of why we recommend NVMe SSD:

Can I plot more than one plot at a time?​

Yes, using either the GUI or CLI. Over the short run you have a bit more control of plotting using the CLI. You can read the Installation page to learn more. You may have better results if you stagger the start time of parallel plotting processes depending on your hardware setup.

Can I make plots on one machine and move it to another machine?​

Yes. The Moving Plots page gives you the details. You may also want to consider running a remote harvester. You can also use the same private key set to plot on more than one machine at a time but be aware of the uPnP issues.

What is the secondary temp directory -2, and how should I set it?​

-2 is in use during phase 3 and 4. It is the file being built into the resulting .plot file. As it is done compressing tables during phase 3, it will move them into the .plot.2.tmp file (-2), and phase 4 will scan through the entire .plot.2.tmp (-2) file, and write table headers for easy access by the harvester. When phase 4 is done, if -2 = -d, it will simply rename the .plot.2.tmp to .plot. If -2 != -d, it will copy the file into place, then rename, and finally remove the -2 file. The amount of writing is about 110% of the resulting .plot file size. It is a setup dependent option - is your setup faster at moving the compressed tables into the .plot.2.tmp file, and then scan through the entire file, and write table headers during phase 4 - and then copy to -d (-2 = -t) - or is it faster to send the compressed tables directly into the -d (-2 = -d) directory, and then in phase 4, scan through the entire file, and write table headers inside -d (-2 = -d) thereby skipping the final copy into place. The -2 directory can be set in the Advanced Options for Step 3 in the GUI.

My plotting attempt got "Caught plotting error: Not enough memory..."?​

If you see something like Caught plotting error: Not enough memory for sort in memory. Need to sort X.XXGiB then you need to either select more memory buffer or more buckets. More buckets require less memory but will create more temp files and more sporadic disk writing. You will almost always want to use 128 buckets and you should try increasing the RAM max usage/-b to 4608MiB.

My plotting attempt ended with "RuntimeError: bad allocation"?​

This is a RAM problem with your machine. It can be how your swap file is configured. It is often your overclock, or XMP settings and even can be a faulty RAM stick. Chia plotting is better than memtest at surfacing broken or mis-configured RAM.

Can I resume plotting if my computer or drive reboots or enters power save mode while plotting? ?​

Unfortunately, resuming a plot is not supported. We suggest that you disable power saving mode - especially for external drives - and try to limit other possible causes of interruptions. Plotting a k=32 could take multiple hours, depending on your hardware, so these interruptions can be painful. They are also a part of why we don't recommend plotting plots larger than k=32 as each increment in k generally doubles the time to complete a single plot.

Do I have to be connected to the internet or synced to plot?​

No. Plotting can be done entirely offline and needs nothing from the blockchain to complete. The only time you have to be online and synced is when you're farming so that you receive new challenges for the next blocks and transactions to include in a transaction block if you're lucky enough to win one of them and get the transaction fees. Note that one farmer winning is independent of other farmers winning at the same time. All farmers can "win" at nearly the same time. That is why sometimes there are 10 blocks in one minute, and sometimes there is only 1 block per minute, etc.

Is there any advantage in plotting larger k sizes?​

No. As long as you plot at least k=32, those plots will be eligible to win on mainnet. In a decade or more, k=32 may become too small, but that's speculative. Usually the only reason to plot larger than k=32 is to optimize using all of the space on a given drive. For example, it may make sense to have two k=33's and the rest k=32 so that you only leave 10 GB free on a given drive.

Yes.

How do I know if my plots are OK?​

Run chia plots check -n 30 to try 30 sample challenges for each plot. Each of your plots should return a number around 30, which means it found around 100% of the attempted proofs of space. If you're still worried try -n 100 as more random attempts will give you a more valid assessment that the plots is fine. It really is ok if your plot is within 80%-120%. If some of your plots are missing for some reason you may need to add the directory they are in to your config.yaml file. That can be done in the GUI with the MANAGE PLOT DIRECTORIES button or on the command line with chia plots add -d [directory].

Can I use USB 3.0 cable connected to SSD/NVME running the Temp files?​

On Windows, it has not worked well since the communication speed is not fast enough, sometimes the usb turns off, then the plot is not valid. It's possible to run 1 plot, but limiting when trying to process multiple plots. Most are installing PCIe adapters to SSC/NVME and that solves the issue. The mac has very fast communication to do the first plot, many others are saying that they can do 2 plots but process time increases dramatically. Technology is constantly changing so continue to do research and ask in the chat rooms.

Full Node​

What is this UPnP Error?​

UPnP is an optional setting that allows users to open a port in their router and therefore allow other nodes to connect to them. This is not required, since your node can still make outgoing connections without UPnP.

For some routers, UPnP is enabled automatically, but for others, you might have to go into your router settings and enable UPnP manually. Sometimes restarting the router is also necessary.

Another option is port forwarding, where you tell your router/NAT to forward requests on port 8444 or 58444 for testnet to your machine.

Why should I not run more than one node on a home network and what's this about UPnP?​

First, running more than one node with the same private keys on your home network is wasting bandwidth by syncing two copies of the blockchain over your download link. You can get the same results by running one node and using multiple harvesters on multiple computers. Second, if you have uPnP enabled on both nodes and your home router supports uPnP (and most do) it will cause both of your nodes to not sync the blockchain. You need to disable uPnP on all or all but one node behind a uPnP enabled router. The CLI command chia configure --enable-upnp false will turn uPnP off on a node. It requires a restart of the node to take effect. If you disable UPnP on all but one of your nodes then your local router will forward inbound 8444 traffic to the one node and the rest will now be able to connect to the network but just will not accept inbound connections from the network.

Why does my node have no connections? How can I get more connections?​

Step 1. Make sure you are running the most recent version of the Chia software. Check out the Installation page.

Step 2. If your node has no connections, it could be one of many reasons. The most likely reason is that there are no users with space to have new connections, so you cannot connect to them. To solve this, you should try opening port 8444 on your router so other peers can connect to you. Follow the steps in the Node Syncing page.

Port 8444 is the port through which other Chia computers can communicate with your PC. When you set up port forwarding on port 8444, the Chia software on your computer can quickly talk to other PCs, link up, and start downloading and syncing with the Chia blockchain.

The network is undergoing rapid growth and expansion. Many of the newly arrived Chia peers (computers) do not open up port 8444. It makes it very hard for the network. So please port forward on port 8444!

Use this link to check if your router's port 8444 is closed: https://portchecker.co/

Step 3: You might need to disable UPnP in the config file (~/.chia/mainnet/config/config.yaml) or by using the cli command chia configure -upnp false. You might have multiple nodes running on the same machine, or in the same wifi network. Make sure to close all Chia applications on your computer. Also check your firewall or antivirus software, which might be blocking connections.

Step 4: Try deleting your peer DB which is located at ~/.chia/mainnet/db/peer_table_node.sqlite. Close then restart Chia.

Step 5: Edit ~/.chia/mainnet/config/config.yaml, search for weight_proof_timeout and increase it from 180 to 400. If that value is not there, you can add it under the full_node section.

It can take a few minutes to start receiving peers and several hours to completely sync.

I am seeing blocks and connections but my node says "Not Synced"​

This is usually a system clock issue, which is causing the display of "Not synced", even though you are. Your clock must be set to the exact time, and cannot be more than 5 minutes off. Check your phone and your computer and ensure the time is the same.

What is the new database?​

Chia began using version 2 of its blockchain database in 2022. Version 1 has since reached its end-of-life.

Version 2 of the database is still written in SQLite, but it has undergone a series of optimizations from version 1, such as storing hashes in binary, rather than human-readable hex format. It also is more compressed than version 1. These two factors combined have resulted in an approximately 45% reduction in the size of the database, as well as a slight improvement in its performance.

When you install a brand new full node, version 2 of the database will be created when you run chia init.

If you are upgrading from Chia 1.x to 2.1 or later (which is required due to the hard fork), you will no longer be able run with version 1 of the database. In this case, your options are to download a database checkpoint or to upgrade to version 2 manually, as described below.

If you still have a copy of version 1 of the database, you can upgrade it to version 2. This upgrade will not happen automatically. The command to perform the upgrade is chia db upgrade. This is documented in detail in our CLI reference. Be sure you have enough free space on the disk that contains your database file to write the new file.

The upgrade could take several hours. After it has completed, run chia start farmer -r to restart your farmer and switch to the new database.

Note that the new database will have the same peak as version 1 at the time you initiated the upgrade. Your node will still need to run a short sync to fetch the remaining blocks that had gotten added while the upgrade was being performed.

Because the upgrade from version 1 to 2 of the database is time-consuming, most users will likely only perform it on one of their systems and copy the new database file to their other systems afterward. If you choose this option, be sure to either copy the file before running chia start farmer -r, or stop Chia altogether if it is already using the new database. Once the database is swapped from v1 to v2, you also need to update your config.yaml to reflect the new v2 database change. Under the full_node: section set database_path: db/blockchain_v1_CHALLENGE.sqlite to database_path: db/blockchain_v2_CHALLENGE.sqlite

warning

If you copy your database file to another computer while Chia is currently using it, you'll risk corrupting it, which will necessitate a full sync from genesis.

Technical details​

If you're interested in learning more technical details of the new database, see the first Github Pull Request that introduced the changes:

And there were two follow-up Pull Requests with additional improvements, along with some benchmarks.

What is the difference between Wallet Mode and Farming Mode?​

When you load Chia's client GUI for the first time, you'll be asked to choose whether to run in Wallet Mode or Farming Mode. Here are the main features of each mode:

Wallet Mode:

• This mode runs a Chia wallet, but not a full node.
• The wallet will sync by connecting to external peers.
• You'll be able to send and receive Chia and/or CATs.
• Farming will be disabled.

Farming Mode:

• This mode runs a full node, so farming will be enabled.
• The wallet will also sync by connecting to external peers, unless specific conditions are met (see below).
• You'll be able to send and receive Chia and/or CATs, just as while running in Wallet Mode.

To switch between Wallet Mode and Farming Mode, click the gear icon on the upper-right side of your client. The settings menu will appear. Click the desired mode.

Note that in both modes, the light wallet protocol is always used. This protocol will sync your wallet by only downloading information from a subset of the blocks. The more transactions your wallet has had, the longer this process will require.

The following are situations when your wallet will NOT connect to external peers:

• connect_to_unknown_peers = false is set in config.yaml, under wallet:.
• Your wallet is connected to a trusted node (typically this is your local host) AND that node is fully synced.

For example, let's say you're running Chia for the first time and you have not modified connect_to_unknown_peers. Here is one potential workflow:

1. Start the GUI and select Wallet Mode.
4. After your full node has synced, your wallet will automatically connect to your full node in order to stay synced. It will terminate its connections with external peers.
5. Change to Wallet Mode. Your full node will continue to run in the background, and your wallet will remain connected to your full node in order to stay synced.
6. Stop and restart Chia. You will return to Wallet Mode, and your full node will no longer be running. Your Chia client is now in state 2.

Depending on how you are using your Chia client, we recommend the following:

• Casual users who are not farming or running a business such as a DEX can use Wallet Mode.
• Farmers need to run in Farming Mode.
• Anyone running a business, as well as anyone who frequently trades XCH or CATs, should do one of the following:
• Run in Farming Mode. Only transact when your node is fully synced.
• Set connect_to_unknown_peers = false. Run in either Wallet Mode or Farming Mode.

What are trusted peers and how do I add them?​

There are two types of peer nodes -- trusted/known and untrusted/unknown. By default, your local node is your only trusted node. It is possible to add other nodes to the trusted list, for example if you personally run more than one full node. One reason to add a trusted node is to speed up the sync time of your light wallet.

The light wallet protocol has two techniques to sync:

Typically, it is much faster to sync a wallet by connecting to a trusted node. Therefore, if you have access to a synced node that you trust, you may want to add that node to your trusted peers list. We recommend that you only add your own full nodes to this list.

Prerequisites​

1. Chia needs to be version 1.3.0 or later on all computers
2. Have a full node running on version 1.3.0 or later

Steps to add a trusted node (peer)​

1. You'll need your trusted node's ID. From your trusted node, run chia show -s. Copy the value of Node ID, which will appear near the beginning of the output. For example:
~$chia show -sNetwork: mainnet Port: 8444 Rpc Port: 8555Node ID: 0ThisisanexampleNodeID7ff9d60f1c3fa270c213c0ad0cb89c01274634a7c3cb9 1. Edit config.yaml. This file is located in ~/.chia/mainnet/config on Linux and MacOS, and C:\Users\<username>\.chia\mainnet\config on Windows. Search for the wallet: section. It should be near the end of the file. Edit the following values from within this section: • connect_to_unknown_peers - Default is true; change it to false • target_peer_count - Default is 3; change it to 1 (assuming you only have one trusted full node) • trusted_peers • Default is 0ThisisanexampleNodeID7ff9d60f1c3fa270c213c0ad0cb89c01274634a7c3cb9: Does_not_matter • Change to <Node ID>: Does_not_matter • Note 1: Replace <Node ID> with the actual Node ID you obtained above • Note 2: It doesn't matter what you enter on the right side of the colon. The argument will be ignored. Just make sure to enter something Optional (this setting ensures the node is automatically used while starting the client) • full_node_peer: the default host: is localhost. Change this to the IP address of the trusted full node (local IP if the node is on the same LAN and public IP if it is not). • Note 3: The IP address can be found by reviewing your full nodes network connection information (local IP) or by searching "What's my IP" in your favorite search engine. 1. Restart Chia on the computer you are connecting to the trusted node to pick up the changes. • Note 4: If you did not add the full node peer in the optional step you will need to run chia peer wallet -a <trusted_node_ip>:8444 to manually connect to the node peer. 1. To verify that the changes are working, run chia wallet show. The last line of the output should contain -Trusted: True How does light wallet syncing work?​ This response will give a non-technical overview of Chia's light wallet syncing process. For technical info, see our docs site, as well as the FlyClient White Paper, which details the process from which Chia's light client is based. First, a bit about addresses in Chia. A single Chia wallet can use up to four billion (2^32) addresses. Hopefully, you won't need more than that! Using multiple addresses can help provide anonymity. Rather than having to sign up for a new account each time you want to receive money, you can simply click "NEW ADDRESS" and presto -- a new address appears. Additionally, each time you receive change from sending money, a new address is automatically generated. Your wallet keeps track of each of the addresses that have been used. As long as your wallet is synced, it always knows how much money you have. One important thing to remember is that your wallet addresses will always be generated in the same order. When you generate a "new" address, you're actually calculating the next address in the sequence. Your wallet doesn't know what the next address will be until it's generated, but the sequence will always be the same. For example, if you generate 50 new addresses (and write them down), and then install Chia on a new computer and import the same wallet, the first 50 addresses you generate will exactly match those from your original computer. Next, we'll introduce a setting called initial_num_public_keys. This setting is part of config.yaml, located in ~/.chia/mainnet/config on Linux and MacOS, and C:\Users\<username>\.chia\mainnet\config on Windows. The default value of this setting is 100. The majority of users should not change it. You can think of initial_num_public_keys as the number of future addresses to examine. It's a window that expands with time (and never contracts). Here's how it works: The first time you run Chia's software, your wallet will attempt to sync. It does this by checking the first address in the sequence. If that address has ever received money, your wallet will account for that transaction history and examine the next address, and so on. It would take a very long time to examine all four billion addresses, so your wallet will stop looking at some point. This is where initial_num_public_keys comes in. By default, your wallet will stop after it has examined 100 straight addresses that have never received money. If it examines 50 empty addresses and then finds a transaction on the 51st address, the number left to examine is reset back to 100. Because the addresses always appear in the same sequence, it will be rare to have even a single address without any transaction history. But there is one exception: if you click "NEW ADDRESS" twice, then one address will remain unused. If you click "NEW ADDRESS" 101 times without receiving money at any of those addresses, then you'll have 100 consecutive unused addresses in the sequence. Let's say you receive money at the 101st address. When your wallet attempts to sync, it will stop looking after the 100th blank address. Transactions from subsequent addresses will remain undiscovered, and your balance will be incorrect. The default setting for initial_num_public_keys is quite conservative -- it should be rare for anyone to click "NEW ADDRESS" more than 100 times without actually using any of those addresses. That said, you might have a legitimate reason to do this, for example if you're running an exchange. In that case, feel free to set initial_num_public_keys to a higher number, stop your wallet, delete your wallet database, and start your wallet again to begin a fresh sync. Why not set initial_num_public_keys to a higher number by default? Because it would take longer for your wallet to sync. Why not set it lower? If the default setting were 2, most wallets would likely still show the correct balance and the sync time would be faster. However, we set the default to 100 to prioritize showing the correct balance over syncing as fast as possible. How does your wallet know it has the correct info for each address? It polls one or more of its peers. These peers can be either trusted or untrusted, as explained in the previous question. By default, your own node is the only one you trust. If your node is fully synced, then your wallet only needs to query your node to determine your transaction history for each address. If your node is not fully synced, then your wallet will query a number of peers about this info. If any of them lie, omit info, or disconnect in the middle of a query, your wallet will know because the responses won't all match. If you believe your balance is incorrect, changing initial_num_public_keys is unlikely to fix the problem. If at all possible, you should sync a full node, stop Chia, delete your wallet database, and start Chia again. This time, Chia will sync based on your own node alone. If this is not an option, then resyncing from untrustred nodes might fix the problem as well. Where is the Chia blockchain database located?​ The Chia database (db) is located in the db/ directory inside the .chia/mainnet/ directory. The .chia/ directory will be found in your user's home directory. You will find the testnet database in the same db/ directory if you are using testnet. • mainnet database filename: blockchain_v2_mainnet.sqlite • testnet database filename: blockchain_v2_testnet11.sqlite Windows Systems​ info To show hidden files on Windows file explorer click View \ Show \ Hidden items C:\Users\<YOURUSERNAME>└─ .chia/ └── mainnet/ └─ db/ macOS and Linux Systems​ info To show hidden files on Mac finder click "COMMAND"+"SHIFT"+"." (period), on linux GNOME explorer click the carrot (small down arrow in top right) then select Show Hidden Files /Users/<YOURUSERNAME>└─ .chia/ └── mainnet/ └─ db/ How do I use the Official Chia Blockchain snapshot torrent?​ 1. Download the torrent file from https://www.chia.net/downloads/#database-checkpoint 2. Use a torrent client to download the full db (I have used bittorrent and qbittorrent) 3. Unpack/reassemble the torrent file that was downloaded (on windows I used 7zip, Mac and linux have built in tools that work for this) 4. Move the db to the correct folder (~.chia\mainnet\db) and update the name to "blockchain_v2_mainnet.sqlite" (removing the date information in the name) 5. Verify the config file (~.chia\mainnet\config\config.yaml) has the correct value under the full_node section for database_path: db/blockchain_v2_CHALLENGE.sqlite (should only need to change the v1 to v2) 6. Launch chia and wait for a bit (the height to hash and peers files need to be built so this can take upwards of 30 minutes) How do I move the Chia blockchain database to another drive?​ The Chia blockchain database will continue to grow as new blocks are farmed creating the ever-growing need for additional space. In some cases this requires users to move their database to a different drive. warning We strongly urge using a fast ssd to store the blockchain database. Using a slow drive can create issues with maintaining sync with the network. 1. Stop all chia processes. 2. Locate the database file you want to move. • Blockchain db: ~/.chia/mainnet/db/blockchain_v2_CHALLENGE.sqlite • Wallet db: ~/.chia/mainnet/wallet/db/blockchain_wallet_v1_CHALLENGE_KEY.sqlite Note: CHALLENGE will either be mainnet or testnet based on your selected network. Note: KEY will be the fingerprint of your wallet. 3. Copy the database file(s) you want to move to their new location. 4. Update the applicable config.yaml parameters from the table below. • Config file: ~/.chia/mainnet/config/config.yaml DatabaseConfig.yaml ParameterDefaultNew Location Blockchainfull_node: database_path:db/blockchain_v1_CHALLENGE.sqlite<NEW_LOCATION_PATH>/db/blockchain_v1_CHALLENGE.sqlite Blockchain peer tablefull_node: peer_db_path:db/peer_table_node.sqlite<NEW_LOCATION_PATH>/db/peer_table_node.sqlite Walletwallet: database_path:wallet/db/blockchain_wallet_v1_CHALLENGE_KEY.sqlite<NEW_LOCATION_PATH>/wallet/db/blockchain_wallet_v1_CHALLENGE_KEY.sqlite Wallet peer tablewallet: wallet_peers_path:wallet/db/wallet_peers.sqlite<NEW_LOCATION_PATH>/wallet/db/wallet_peers.sqlite Note: This information has been adapted from the Spacefarmers guide. info Chia versions 2.1.0 and newer no longer support the version 1 (v1) blockchain database. Please refer to the upgrade instructions if your database is version 1. How do I upgrade my version 1 blockchain database to version 2?​ Chia versions 2.1.0 and newer no longer support the version 1 (v1) blockchain database. There are two method for updating the database to version 2, either using the upgrade cli command or downloading the official database snapshot torrent. CLI command:​ 1. Stop the chia client (this can be done while chia is running but stopping the client saves from any potential issues). 2. Run the command chia db upgrade (you do not need the input or output paths if these are still default). Upgrade command context. • This process will take some time and requires additional space as the v1 db is compacted into the v2 db which leaves the v1 db intact. • Remove any -wal or -shm files that are present in the directory (these are temporary files that should only be removed when all chia processes are stopped). 3. Verify the config file (~.chia\mainnet\config\config.yaml) has the correct value under the full_node section for database_path: db/blockchain_v2_CHALLENGE.sqlite (should only need to change the v1 to v2) 4. After the above completes start the chia client. 5. If all loads up properly (might take ~5-10 minutes to load) then you can safely delete the v1 db found here ~\.chia\mainnet\db\blockchain_v1_mainnet.sqlite. Official torrent:​ 1. Download the torrent file from the official database snapshot torrent. 2. Use a torrent client to download the full db. Bittorrent is recommended but any torrent client will work. 3. Unpack/reassemble the torrent file that was downloaded (on windows one can use 7zip, Mac and linux have built in tools that work for this). 4. Stop all chia processes if you have not already. 5. Move the db to the correct folder ~\.chia\mainnet\db\ and update the name to blockchain_v2_mainnet.sqlite (removing the date information in the name). • Remove any -wal or -shm files that are present in the directory (these are temporary files that should only be removed when all chia processes are stopped). 6. Verify the config file (~.chia\mainnet\config\config.yaml) has the correct value under the full_node section for database_path: db/blockchain_v2_CHALLENGE.sqlite (should only need to change the v1 to v2). 7. Launch chia and wait for a bit (the height to hash, sub-epoch, and peers files need to be built so this can take 5-10 minutes). How can I connect to the same full node peers whenever I start Chia?​ info This functionality was first made available in Chia version 2.2.0, in PR #17369. Special thanks to Felix Brucker for creating it! By default, when you start a Chia full node, it will attempt to connect to a random set of peers. This is normally fine, but there are some cases in which you might want to connect to the same peer(s) every time, such as if: • You are a pool operator who wants to establish consistent groups of nodes to support your pool • You are running a small, private testnet where all peers are known • You are connecting to a larger testnet which nonetheless has an insufficient number of nodes to locate your first peer immediately upon starting a full node Steps to connect to the same full node peers: 1. Edit your config file; the default location is ~/.chia/mainnet/config/config.yaml 2. In the full_node: section, you should see the following line: full_node_peers: [] • If you do not see this line, you can either add it manually, or rename your config file and run chia init to create a new copy, which will contain this line. 3. Remove the square brackets ([]) and add add new lines with - host and port. Be sure to indent port, even though it does not have a hyphen. For example, to add two mainnet peers, use the following syntax: full_node_peers: - host: <Peer 1 IP address> port: <port> - host: <Peer 2 IP address> port: <port> • Typically, <port> will be either 8444 (for mainnet) or 58444 (for most testnets). note These are not trusted peers (for more info, see the question on connecting to trusted peers). Instead, these are normal peers that you happen to want to connect to on an ongoing basis. If you lose your connection to one of these peers, your node will automatically attempt to reestablish the connection. Farming​ What is the difference between a Farmer and a Harvester?​ A harvester can be thought of as a node that is an extension of your farmer. The harvester checks the plots and reports the results to the farmer, the farmer then submits the results to the blockchain. If setting up harvesters it is important to review the proper way to farm on many machines How do I tell if I'm farming correctly?​ If you see plots in the Plots section of the Farm page in the GUI - your plots are being farmed. You will see challenges and proof attempts as they come through in the Last Attempted Proof section however you usually will not have a proof worth sending to the network due to the plot filter. You can additionally see the Total Size of Plots on the Farm view and it will tell you how much unique space is being farmed and statistically how long it should take - on average - to win a block. Also, your node needs to be synced for you to farm properly. In the GUI, check the Full Node page. On the cli, do chia show -s -c. Does it matter how fast my internet connection is?​ No. You have 30 seconds to respond to challenges. I have only 10 TB, will I ever win XCH?​ ChiaCalculator.com does a good job at running the numbers. First, the bad news. Statistically, it would take multiple years to win a reward with a 10-TB farm. ("So you're saying there's a chance...") Now, the good news. You can join a pool and collect regular rewards, no matter your farm's size! See the Pool Farming page for more info. What is the plot filter and why didn't my plot pass it?​ Farmers compute a plot filter based on the signage point, their plot id, and the sub-slot challenge - which are hashed together to create the plot filter bits. If the plot filter bits start with 9 zeroes, that plot passes the filter for that signage point, and can proceed. This disqualifies around 511/512 of all proofs of space on the network, for each signage point. There are 4608 * 2 or 9216 signage points per day so the average plot should pass the filter 18 times per 24 hours on average. Once a plot passes the plot filter it then competes for the best proof of space with every other plot that also passed that plot filter for that signage point. For reasons that aren't super simple to intuit, the only thing each plot is competing on is to have the best proof of space and thus the chances of getting a reward depend on total size of plots on the farm - even with the plot filter in place. As long as the plot passes the filter, and do not have any internal file errors, the plot will always be eligible to compete for the best proof of space. Moving the plot to another directory or server will not change its eligibility. Please note that the speed of your lookups when passing the plot filter should be below 5 and preferably below 2 seconds. When you actually win a reward, your drive will have to do more lookups than these, so it's important that the the lookups are happening fast. Why does my Chia farm say Missing signage points?​ This means that your harvester did not respond to one or more signage points in time to be eligible to win a reward. However, if you miss fewer than 100 signage points per day, it is not a serious issue. On average there are 9216 signage points per day, or one every 9.375 seconds. If your harvester misses 9 signage points per day, then your farm was operational 99.9% of the time. This would be considered normal, even for a farm with a stable internet connection. If you are consistently missing more than 1% of the signage points, or around 100 per day, then it is probably worth investigating the cause. Some reasons your harvester might miss more than 100 signage points per day: • Your harvester can't handle its required compute load -- typically this will happen if you are farming with compressed plots. However, even with uncompressed plots, if your harvester sometimes requires more than five seconds to perform its lookups, it may miss some signage points. See our plotting documentation for more info on how determine the maximum number of plots your harvesters can handle. • Lost connections to peers -- check your peer count by clicking the FULL NODE icon in the upper right corner of your farmer GUI. If you only have a few peers, your local network might have a UPNP issue. See our question on obtaining more peer connections. • Changed external IP address -- some ISPs will change the IP address of their customers frequently and without warning. This may be happening to your home network. Your ISP might be able to provide you with more info. Unfortunately, if this is happening, often the only recourse is to pay for a dedicated IP address. • Changed internal IP address -- your home network might also have changed the IP address of your harvester(s). Your router's settings might provide you with more info. • Temporary loss of internet -- you don't need a fast internet connection to run a Chia node. But you do need a stable one. If your local network loses internet connectivity for a few seconds, you might miss a signage point. • Bad wifi connection -- we recommend that you run your farmer with a wired internet connection. If you need to use wifi, try to keep your farmer as close to your router as possible. While wifi tends to be consistent enough to run a Chia farm, if your farmer is in a different room than your router, you might occasionally miss a signage point. Can I join a farming pool?​ Yes you can. Please check the Pool Farming page. This was our advice in 2020, long before the launch of mainnet. However, we no longer advise anyone to delete their winning plots. Some background: The consensus Chia originally used during the testnet phase contained the possibility of an attack where an attacker who could co-ordinate N deep from the tip of the chain could try to coerce a winning farmer to re-write a historical transaction block. However, before the launch of mainnet, the consensus was updated; this attack is no longer viable. See the link for more details. Do my plots "wear out" or "go bad"/"go stale" over time? Will I have to regularly re-plot?​ No, your plots are virtually unaffected by the passage of time, aside from hardware errors. Even in the presence of bit flips due to aging hardware, plots remain mostly effective. The only cases where you would need to re-plot are: 1. if you are using solo plots (not NFT plots) and wish to join a pool (please see note below) or 2. if hardware speeds advance to the point of a certain k value becoming obsolete (e.g., k=32 becomes too fast to plot and we ban them, forcing you to replace them with k≧33 plots). For case 1., you are free to have any mix of solo plots and pool plots if you do not want to re-plot. For case 2., k=32 is not expected to become outdated until sometime between 2026-2031. • Note on case 1: We have added a Pooling Protocol that replaces the hard-coded "Pool Public Key" of a plot, with a plotNFT's "Pool Contract Address" - more on this subject can be read here: https://docs.chia.net/pool-farming/#pooling-faq Is it possible to have a proof but not get a reward?​ It is unlikely, but it is possible. There are multiple reasons why this might be the case. The most common is that due to network delay, or drive speed delay (for example using a slow NAS), you missed the time for inclusion into the blockchain, which is 28 seconds. This time is from when the timelords create the signage points, to when the timelords infuse your block. Check to make sure that you are connected and synced to multiple peers, and that your quality lookup are fast (<2 seconds, definitely less than 5). Another reason might be that the signage point where you won did not get included into the blockchain. This can sometimes happen, since timelords may publish signage points that don't end up on chain. Wallet​ How do I use the Chia faucet?​ To use the chia faucet or testnet11 faucet you will need to identify your Master Public Key (also referred to as the Public Key). You can use either the GUI or CLI to identify the Master Public Key by following these steps: GUI​ warning Never share your private / secret keys or mnemonics with anyone. These give access to spend funds from your wallet. 1. In the top right corner select logout: 1. Using the desired keys menu, select details: 1. View and copy the Public Key to the field on the Faucet page: CLI​ warning NEVER share your private / secret keys or mnemonics with anyone. These give access to spend funds from your wallet. In order to view your keys from the cli, run chia keys show, optionally including the -f <fingerprint> flag to show only the info for the key you just generated: 1. From terminal (mac/linux) or powershell (windows) run chia keys show: chia keys show 1. View and copy the Master Public Key to the field on the faucet page: Showing all public keys derived from your master seed and private key:Label: Demo WalletFingerprint: 2281896037Master public key (m): 96ce91d974daa0990e6681ac2de3e3f49142f6b655a081817832265c143e658a6e60a5dec856f292f45fe2d04c7856f6**Farmer public key (m/12381/8444/0/0): a9e366b26f155491af9a903c0ed9717bfd09a71cbe283eeda825128fd7c6b9ac60e1608f9f008adcfbf66e233d5b4ce8Pool public key (m/12381/8444/1/0): 9566fa434f342dd5f9380a6bfc59dd7d1abd22869a425a8ca09cf27200eaa6aad5bc8fc00db90af832eb8028b0c6e3f0First wallet address: xch1kr3zf7dqw5q953ex6zt33lndj90q0zlh68404tsntnljthnwqs2qvjmwrg note For more security best practices please review the Securing Your Chia – How to Be a Hard Target blog article. How do I send or receive a transaction?​ The Wallets page in the GUI will display your receive address and provide an interface for you to spend your chia funds. You can also obtain a new wallet receive address any time you would like and those funds will all come to the same place as they are based on HD Keys. There is growing wallet functionality available on the command line. Try chia wallet -h. Wallet software also provides features related to CAT's, and trade offers. You can get a receive address on the cli with chia keys show. What is the Coin model?​ The coin (or UTXO) model is a Bitcoin-style transaction model which is also used in Chia. Your wallet keeps track of a set of coins, where each coin can be any amount of XCH. When spending a coin (making a transaction), you have to spend the entire amount, and split that coin into multiple outputs, called coin additions. One addition is to the recipient of the transaction, and the other one is to you, as change. The change usually goes to a new address, so you will not see it in your normal address on Chia explorer, but your wallet will keep track of it and include it in the balance. Each block in Chia is a list of removals (coins spent) and additions (coins created). There are no transactions in the blockchain, which is why you cannot lookup transactions in the block explorers. What are HD Keys?​ HD or Hierarchical Deterministic keys are a type of public key/private key scheme where one private key can have a nearly infinite number of different public keys (and therefor wallet receive addresses) that will all ultimately come back to and be spendable by a single private key. How many confirmations do I need to trust that a chia transaction is final?​ Small reorgs in Chia are possible, though rare. In order to be confident that your transaction won't be reorged, you should wait around six blocks, or two minutes, after the first confirmation. More details are available in our consensus documentation. Why is my wallet not synced? Why can I not connect to wallet from the GUI?​ Try the following options: 1. GUI may not be fully refreshed. Try the "force reload" option under View to force the GUI to refresh. 2. It's possible the wallet DB may be corrupted. Deleting the wallet DB will resolve this, but will also cause you to lose any Offer history and you will need to setup your CAT wallets again. To delete your wallet DB follow these steps: 1. Shut down Chia and all Chia processes, check the task manager to see if they are all shut down. Note that this will cancel running plots, so be careful. 2. Restart your computer (if there are still running processes and you can't get those processes to quit) 3. Delete the ~/.chia/mainnet/wallet/db folder 4. Restart Chia Why do I have a negative balance? Why is my pending transaction not confirming?​ Your pending transaction can take a few minutes if blocks are full. If it's not confirmed after a while, your pending transaction might be stuck. Try the following steps: 1. Shut down your wallet and node 2. Delete your wallet db files: located at ~/.chia/mainnet/wallet/db. This will require syncing up your wallet, but not your node. And then you can resubmit the transaction. 3. Make sure you have upgraded to the latest version 4. Start the application and wait for the wallet to sync up 5. After your wallet is fully synced to the same height as the Full Node, your Wallet Balance will be correct. Known problem: After your wallet is resynced, any previous outgoing transaction will appear as incoming transaction at the block height you made the outgoing transaction. Where can I buy Chia?​ Visit chia.net/buy-xch for instructions on buying Chia with USDS and offers using the Chia light wallet and Offers. There are also several exchanges that offer XCH. You can see a list of exchanges supporting XCH here. This list is for informational purposes only. It is up to the reader to do their own research on the best exchange for their needs. I was running the light wallet beta app and I upgraded to the latest beta and my offer history disappeared. How do I get that back?​ If you were running the light wallet beta app (v1.2.11 dev 265) and you've upgraded to the latest beta (v1.2.12+), you can get your offer history and your CAT wallets back by following these instructions: 1. Close the Chia app 2. Check the following directory: ~/.chia/mainnet/wallet/db if it's not empty, then be sure to delete all the .sqlite files that match the key (e.g., blockchain_wallet_v2_mainnet_1123456789.sqlite) 3. copy the file(s) from ~/.chia/standalone_wallet/wallet/db/blockchain_wallet_v1_mainnet_123456789.sqlite_new to ~/.chia/mainnet/wallet/db 4. rename the file ~/.chia/mainnet/wallet/db/blockchain_wallet_v1_mainnet_123456789.sqlite_new to blockchain_wallet_v2_mainnet_123456789.sqlite 5. launch the Chia app Why does the wallet tab tell me that it's synced, but when I look at the full node tab, it still shows that I'm syncing?​ This is because of the newly integrated light wallet client sync. The wallet will sync through the light wallet sync while the full node syncs up in the background. Once the full node is synced up, then the wallet will sync primarily through the local trusted full node. I lost my offer history, and I have open offers. How do I cancel those offers since I can't access the open offers through the wallet?​ If you've lost your offer history and want to cancel those offers but can't access them, then the only way to cancel the offer would be to send yourself a transaction with the CAT tokens that were part of the offer. Why don't new CAT tokens automatically show up in my wallet anymore?​ The wallet no longer automatically adds unknown CATs wallets for CATs that may have been airdropped to your wallet. This is to help ensure that syncing doesn't slow down with all the additional CATs that could suddenly show up. It is recommended that you use a tail database to look up and add. We understand that this will add some extra work to know which CATs to add wallets for and set them up manually. We do hope to improve upon this experience Soon™ How can I make a coin that may only be spent until a certain timestamp or block height?​ This capability is available by using the ASSERT_BEFORE_* conditions, originally added in CHIP-14. In order to prevent the possibility of bricking a coin, you are recommended to use these conditions only in a coin's solution and not in its puzzle. See our documentation for more info. Where is the executable file to start the reference wallet GUI located on Windows?​ If you only installed Chia for the current user, the exe will be installed to the following location (be sure to replace <user ID> with your actual user ID): C:\Users\<user ID>\AppData\Local\Programs\Chia\Chia.exe If you installed Chia for all users, then this is the location of the exe: C:\Program Files\Chia\Chia.exe What is the dust filter?​ In crypto parlance, "dust" refers to coins that have almost no value. In Chia, the smallest denomination is 1 mojo, or 1-trillionth of an XCH. Unsolicited coins of this value certainly count as dust, but even much larger coins, for example 1 million mojos, are still worth a fraction of a penny. Chia experienced its first "dust storm" in late 2021. The "duster" spammed the blockchain with millions of tiny coins, likely in an attempt to stress-test the network. Chia's blockchain is robust, so it continued without issue. However, many people ended up with thousands of dust coins in their wallets. This proved problematic. In version 1.2.x, wallets that had received tens of thousands of dust coins were unable to sync. The task of optimizing our wallet was a difficult one, but by version 1.3 we had made significant improvements, and these wallets could finally sync. However, sync times for dusted wallets were still measured in days, which was unacceptable. We continued making optimizations, and by version 1.5.1, a wallet with over 100,000 coins could sync within a few minutes. But we wanted to reduce those sync times even more. The dust filter is a new feature, added in version 1.6.0. It is activated whenever there are at least a certain number of unspent dust coins in the wallet. While activated, the filter ignores any coins considered "dust". Two new settings have been added to ~/.chia/mainnet/config/config.yaml in the wallet section: • spam_filter_after_n_txs: 200 • xch_spam_amount: 1000000 If you are upgrading an existing Chia installation, these settings won't be added automatically. In this case, you will need to either add them manually or delete config.yaml and run chia init to generate a new copy. The default settings essentially say, "If my wallet contains more than 200 coins, ignore all coins after the first 200 that are worth less than 1 million mojos." Note that the filter is not applied for CATs or NFTs. You can modify these default values to support different functionality. For example: • Disable the filter by setting xch_spam_amount to 0 (nothing is dust) • Enable the filter regardless of your wallet's status by setting spam_filter_after_n_txs to 0 • Consider coins to be "dust" only if they are smaller than 100 mojos by setting xch_spam_amount to 100 However, we believe the default settings will be sufficient for most users. Note that if the number of unspent coins in your wallet falls to 200 (by default) or lower, then the dust filter will be deactivated. This could happen if you spend or consolidate some of your coins. Why is my wallet's balance inconsistent?​ If you have more than two hundred unspent coins (by default) in your wallet, the dust filter will be activated. Depending on which mode your wallet is using, your balance could show slight differences each time you sync. This is because the coins will not necessarily show up in the same order while syncing. The maximum difference in your balance is spam_filter_after_n_txs * xch_spam_amount. However, the actual difference will rarely be more than a few thousand mojos. There are three potential scenarios: 1. Light wallet only (untrusted mode) -- Your wallet is syncing from multiple remote full nodes. Each time your wallet syncs, it will connect to a new set of nodes, so the coins might not show up in the same order. Different coins could be filtered, so your balance may be slightly different each time you sync. 2. Synced full node (trusted mode) on multiple computers -- If you load the same wallet on different full nodes, the databases will be slightly different due to network latency. Even though the coins themselves all exist, they might not show up in the same order, so different coins could be filtered. In this case, your balance might be slightly different between the two computers. 3. Synced full node (trusted mode) with one computer -- Your trusted database will be the same each time you sync, so the wallet balance will also be the same. Why does my wallet say Error Can't send more than xxxxxxxx mojos in a single transaction?​ This error can occur when attempting to send XCH, CATs, or NFTs. Unfortunately, the error is vague, so there is a bit of guesswork in determining the cause. In the future, we plan to make this error -- along with the recommended way to fix it -- more specific. Some of the potential causes include: 1. You don't have enough money in your wallet. Double check your wallet's Total Balance. 2. You have enough money, but one or more of your coins are locked. Chia uses the coin set model of accounting, where everything is a coin. If some of your coins are part of either a pending transaction or an Offer, they have been temporarily locked. In this case, your Spendable Balance is less than your Total Balance. In order to unlock these coins, cancel any pending offers and click Actions --> Delete Unconfirmed Transactions in your wallet's Summary panel. 3. The CLVM cost of your transaction is greater than the maximum cost allowed. In order to add a Chia transaction to the blockchain, a certain amount of processing power is required. This is the transaction's cost. When sending a single coin or NFT to another wallet, the cost is low. However, if you are attempting to send hundreds of coins or dozens of NFTs in a single transaction, the total cost could be prohibitively high, thus triggering the error. One way to fix this is to break your large transaction into multiple smaller ones -- try sending only the amount indicated in the error message. Another fix is to combine your coins by opening a command prompt or terminal window and running chia wallet coins combine. Is there an RPC to list wallet names?​ Unfortunately, no. However, to obtain the user-specified wallet names programmatically, you can use the chia keys label show CLI command. Another way to obtain this info is by connecting to the daemon over a websocket by using wscat: wscat -n --cert ~/.chia/mainnet/config/ssl/daemon/private_daemon.crt --key ~/.chia/mainnet/config/ssl/daemon/private_daemon.key -c wss://localhost:55400 From there, you can use the get_keys command, similar to the following example (the request_id can be any string): { "ack": false, "command": "get_keys", "data": {}, "destination": "daemon", "origin": "client", "request_id": "43dc226cef76963ddd56c7068972947f373918c24b0fdf5bfa767a1340271da6"} This command will return a payload with all of the pubkeys/fingerprints/labels -- private keys omitted. If you want the private keys included, pass "include_secrets":true in the data object. For example: { "ack": false, "command": "get_keys", "data": { "include_secrets": true }, "destination": "daemon", "origin": "client", "request_id": "43dc226cef76963ddd56c7068972947f373918c24b0fdf5bfa767a1340271da6"} How do I disable the dust filter?​ 1. Edit ~/.chia/mainnet/config/config.yaml 2. If xch_spam_amount doesn't exist, add it 3. Set the value for xch_spam_amount to 0 (nothing is dust) 4. Restart Chia Can I import a 12-word mnemonic seed phrase from another wallet?​ Starting in version 1.7.0, Chia's reference wallet will accept both 12- and 24-word mnemonics. This allows you to import a mnemonic from another wallet. Simply click IMPORT FROM 12 WORD MNEMONIC when importing your wallet. However, do keep in mind: • Chia's reference wallet only allows you to import a 12-word mnemonic. It does not allow you to create a new 12-word mnemonic. • Certain wallets use 12-word mnemonics that are not compatible with Chia's reference wallet. As far as we know, this only applies to the Pawket wallet, but there may be others as well. In the case of Pawket, you need to export a 24-word mnemonic from their app in order to use Chia's reference wallet. More info can be found on their FAQ page. How can I configure Chia to reuse the same receive address?​ By default, Chia will update your receive address for every new transaction. This is done for privacy reasons -- it is more difficult to associate multiple transactions with the same wallet if each transaction uses a different address. However, there are some downsides to using multiple addresses: • It can be more difficult to track the history of your own transactions. For example, block explorers cannot associate multiple addresses with the same wallet. (Note, however, that the reference wallet will show you a complete history.) • Some wallets only search a limited number of addresses for a given key, so they may not display your full balance. • Wallet performance can degrade after a large number of addresses have been used. This is because the wallet must search for transactions for each address in the derivation index. Starting in version 1.7.1, Chia's reference wallet will allow you to keep the same receive address with each transaction. If you change this setting, each of the above issues will be mitigated, at the expense of reduced privacy. To set up your wallet to reuse the same receive address: 1. Edit ~/.chia/mainnet/config/config.yaml 2. Search for reuse_public_key_for_change: If this parameter doesn't exist, you can add it manually. Under wallet: add the following two lines: reuse_public_key_for_change: '2999502625': false 1. 2999502625 is a dummy fingerprint that is added by default. You will need to obtain your wallet's fingerprint actual by running chia keys show. For example, $ chia keys showShowing all public keys derived from your master seed and private key:Label: Testnet1Fingerprint: 2104826454
1. Change the dummy fingerprint to your wallet's actual fingerprint, and update the value to true. For example,
reuse_public_key_for_change:  '2104826454': true
1. If you wish to specify the behavior for more than one fingerprint, you can add additional fingerprints to new lines. If a fingerprint is not listed, the default value of false will be used.
2. Restart Chia for the changes to take effect. Your wallet will now reuse the same receive address for every transaction.

To verify that the same address is being reused:

1. Run chia wallet get_address -f <fingerprint>.
• Replace <fingerprint> with the fingerprint you would like to test
• This command will give you the latest address for that fingerprint
2. Run chia wallet send -f <fingerprint> -t <address> -a 0.000000000001 -m 0.000000000001 --override. Some notes:
• Replace <fingerprint> with fingerprint you used in step 1
• Replace <address> with the address you retrieved from step 1
• This command will send 1 mojo to your latest address, and attach a 1 mojo fee. Feel free to adjust these amounts accordingly. (You can also send money from the GUI.)
• The --override flag is needed because the amounts to send are considered unusual
3. After the transaction has completed, run chia wallet get_address -f <fingerprint>. You should receive the same address as you received in step 1. If you received a different address, reuse_public_key_for_change was not set to true for the specified fingerprint.

What is identical spend aggregation?​

Identical spend aggregation is a mempool feature that allows multiple different spend bundles to spend the same coin. It is being introduced in version 1.8.2.

There are two requirements for identical spend aggregation to be successful:

1. The puzzle of the coin being spent must not contain any AGG_SIG_ME or AGG_SIG_UNSAFE conditions
2. Each of the spend bundles that spend the coin must have identical solutions for spending that particular coin

In cases where both of these requirements are met, when a farmer creates a block, it will choose one of the identical spends from the mempool as the "winner", based on which transaction pays the highest fee-per-cost. The remaining copies of that spend will then be deduplicated against the winner (they will be aggregated into a single spend). Any announcements the coin makes will then be available for any other spend to assert within the same block.

Which mempool feature does identical spend aggregation introduce?​

In Chia versions prior to 1.8.2, two key features were not supported by the mempool:

1. The ability of a transaction to spend the output of another mempool item (i.e. inter-transaction ephemeral spends)
2. The ability to assert an announcement made by another mempool item (i.e. inter-transaction announcements)

These features both would necessitate the creation of dependency graphs, which a farmer would need to solve (and ideally optimize) when creating a block.

Regarding feature 1, the only ephemeral spends that are currently supported must come from the same spend bundle. Inter-transaction ephemeral spends are not yet supported as of version 1.8.2.

Chia version 1.8.2 introduces identical spend aggregation, which addresses some of the use cases of Feature 2. Spends that make use of this feature are still restricted by the lack of AGG_SIG_* conditions, which means that anyone who needs to assert an announcement from an aggregated spend could also have spent the coin. However, this version brings Chia one step closer to offering full support for inter-transaction announcements.

Why do I see INVALID_FEE_TOO_CLOSE_TO_ZERO in my log file?​

This error message occurs when you submit a transaction that does not include a high enough fee, for example when the network is quite busy. Try submitting the transaction again with a higher fee (100 million mojos will generally suffice for standard transactions). For more details, see our mempool documentation.

Offers​

What are Chia Offers?​

Chia Offers enable a decentralized, peer-to-peer trading of assets on the Chia blockchain. For more information, see our:

After creating an offer file, why does my spendable balance differ more than the amount specific in the offer?​

When you create an offer, coins are reserved to ensure that when the offer has been accepted and written on to the blockchain, the transaction can be completed. Chia's wallet will reserve the largest coin to fulfill an offer, and when that coin is reserved, it will lower the spendable balance by the total coin amount.

I plan on making many offers and I want to ensure that my coins aren't locked up?​

To create smaller coins, send money to your own wallet in smaller denominations. For more info, see our reference doc.

When canceling an offer, when should I check the "cancel on blockchain" checkbox?​

You should use this option if the offer file has left your computer. If you don't use this option, someone who sees your offer could still accept it. See our reference doc for more info.

If I cancel my offer on the blockchain, will other people be able to fulfill it?​

No, canceling on the blockchain ensures that your offer can no longer be fulfilled.

I'm accepting an offer, but it shows a Unknown CAT, what should I do?​

You should always check the ID of the asset(s) being offered before accepting any offers. First make sure you have a CAT wallet set up for the assets that you are trading for and are getting that information from a reputable source. Second, when you view the offer in the wallet, ensure the amounts and the CATs match up to what you are expecting. For more info, see our GUI tutorial.

Where can I share my offers?​

Once you've created the offer, you'll need to find someone who will take the other side of it. You can share your offers through the following methods:

• Send your offer file directly to another user
• Offerbin - an open marketplace for Chia Offers
• Offerpool.io - an open-sourced, decentralized offers database built on top of OrbitDB and IPFS
• dexie.space - a decentralized exchange for Chia offers supporting Chia tokens (CATs) and NFTs

Why don't I see the offers option in my wallet?​

You are probably running the wallet that comes installed with the full node. Be sure to download the standalone lightwallet here (and be sure not to install on the same machine as your full node). We will be integrating the new capabilities of the standalone light wallet into the full node so you can farm and use all the new features of the wallet Soon™.

How do I know if I'm getting the right exchange value for an offer?​

Prices in cryptocurrencies fluctuate all the time. You can review any of the existing DEXes like Hashgreen or Offerbin to see what trading pairs are trading for in the open market. Alternatively you can find a reputable website that will give you the currency valuation for more popular and well known currencies like USDS.

Will my Offers sync across different Chia wallets on different machines?​

No, Offers are created and stored locally on each machine. Any accepted offers will only be seen by other computers through the transaction history list.

Can my coin be spent on another computer with a wallet that uses the same keys, even if I am running two wallets on two different computers and I have an open Offer on one computer?​

Yes, the coin can be spent from another computer. Coins are reserved locally on the computer where the offer was created. If that coin is spent from another computer, then the offer will be canceled. In general, it is recommended that you don't use two machines to access the same wallet that offers are being made from.

Why do I see Error 6 when attempting to accept an Offer?​

Version 1.7.0 of the reference wallet uses a slightly different Offer format than previous versions. If your version of the reference wallet is older than 1.7.0, and the offer was created on version 1.7.0 or later, you will see Error 6.

To fix this, download and install the latest version of the reference wallet and accept the same offer. You should no longer see the error.

NFTs​

What are NFTs?​

Non-Fungible Tokens have become extremely popular in the last few years. This site gives a beginner-friendly explanation of what NFTs are.

Chia NFTs make use of a unique feature: Offers. You may already have used Offers to trade XCH and CATs, but to summarize, they enable the trustless, peer-to-peer exchange of assets on Chia's ecosystem, with no involvement from central parties or intermediaries. And now you can use them to buy and sell NFTs, as well. Simply click the Offers button in your Electron wallet, then click "Create an Offer" and "NFT Offer". We'll have a more detailed guide that includes all of the options soon.

How can I make an NFT offer using the CLI?​

The CLI commands for NFT offers are almost the same as those for CAT offers. The main difference is that you have to include the NFT singleton's value after the NFT ID (typically this is :1). For example, to make an offer, you can run:

chia wallet make_offer -o 1:0.1 -r nft1g5gzj3hl9gdyrq83zveepf8wmeet8mxl8zutfyahs0wfkg9mcs9qepc4w5:1 -p test.offer -m 0.001

The result is:

Creating Offer--------------OFFERING:  - 0.1 XCH (100000000000 mojos)REQUESTING:  - 1 nft1g5gzj3hl9gdyrq83zveepf8wmeet8mxl8zutfyahs0wfkg9mcs9qepc4w5 (1 mojos)Offers for NFTs will have royalties automatically added.  Are you sure you would like to continue? (y/n): yConfirm (y/n): yCreated offer with ID 55314ee65db39c173de05873138440c48525eac39fd4a622fd766b3bb4ab02ffUse chia wallet get_offers --id 55314ee65db39c173de05873138440c48525eac39fd4a622fd766b3bb4ab02ff -f 2118200991 to view status

To view your new offer, run the get_offers command that was output upon the offer's creation. Using the above example:

chia wallet get_offers --id 55314ee65db39c173de05873138440c48525eac39fd4a622fd766b3bb4ab02ff -f 2118200991

The result is:

Record with id: 55314ee65db39c173de05873138440c48525eac39fd4a622fd766b3bb4ab02ff---------------Created at: 2022-07-12 11:27:17Confirmed at: 0Accepted at: N/AStatus: PENDING_ACCEPT---------------

How can I take an NFT offer using the CLI?​

Continuing with the previous example, we can run the take_offer command from the wallet that owns the NFT:

chia wallet take_offer test.offerSummary:  OFFERED:    - XCH (Wallet ID: 1): 0.1 (100000000000 mojos)  REQUESTED:    - 45102946ff2a1a4180f1133390a4eede72b3ecdf38b8b493b783dc9b20bbc40a: 0.001 (1 mojo)Included Fees: 0.001Would you like to take this offer? (y/n): yAccepted offer with ID 11abdc8b7bb241303d2f0c909860785e0e09a842fb6178bdf6527c99e37f3d35Use chia wallet get_offers --id 11abdc8b7bb241303d2f0c909860785e0e09a842fb6178bdf6527c99e37f3d35 -f 757927417 to view its status

Use the suggested command to view the offer's status:

chia wallet get_offers --id 11abdc8b7bb241303d2f0c909860785e0e09a842fb6178bdf6527c99e37f3d35 -f 757927417Record with id: 11abdc8b7bb241303d2f0c909860785e0e09a842fb6178bdf6527c99e37f3d35---------------Created at: 2022-07-12 11:41:50Confirmed at: 1241919Accepted at: 2022-07-12 11:41:50Status: CONFIRMED

Can I send an NFT to an XCH address?​

Yes. Just as with XCH and CATs, you can send NFTs to an XCH address. If the recipient doesn't have an NFT wallet, one will be created automatically.

How do I sell my NFTs?​

As with buying NFTs, you can also sell them using Offers. Simply create an Offer in your Electron wallet, then send it wherever you want, including to our community galleries and marketplaces such as MintGarden, Dexie, and SpaceScan. If an Offer file is modified, then that copy is no longer valid. This means that you can share your Offers with confidence -- the only thing a "thief" can do with your Offer is accept it.

Is there any limitation to which assets I can offer?​

As of version 1.6.1, you can use the Offer Builder to construct an offer of any asset(s) for any other asset(s). This includes offering XCH, CATs, and NFTs on both sides of the offer.

What is the difference between a transfer and a sale?​

A sale involves using an offer, which in turn requires an NFT to be exchanged for one or more assets. Any time you want to buy or sell an NFT, you will create or accept an Offer. Royalties are built into the NFT, so they will automatically be accounted for when the offer is created/accepted.

A transfer is where you move an NFT from one address to another. No money is exchanged, and there are no royalties. The two main use cases for transferring an NFT are

• Moving an NFT to another wallet that you own

Do I need a new wallet address in order to receive NFTs?​

No. You can send and receive NFTs from the same address you have used in the past. One caveat is that if you send an NFT to an address that is currently running on a pre-1.4 wallet, your wallet won't recognize the NFT. However, the NFT will be safely kept inside your wallet, and it will become accessible after you upgrade to version 1.4 or greater.

How do I mint an NFT?​

If you are comfortable using a command line interface (CLI), then you can follow our dev guide to mint an NFT. If you prefer a browser-based minting tool, options include MintGarden and Omakasea ChiaNFT. Other community-developed marketplaces are listed on ChiaLinks.com.

Can I mint an NFT with a URL that includes a comma?​

Yes, but you need to use an RPC. If you use the CLI command, the comma will be interpreted as a delimiter -- two separate URLs will be created. However, even though URLs that include commas are generally not recommended, they should work with the RPC command. You don't even need to escape the comma or use extra quotes. But, as with all things NFT-related, you should test this functionality on the testnet before attempting it on mainnet.

What does it mean to self-custody an NFT?​

On other blockchains, NFTs are typically custodied in a marketplace. This is akin to having an account with a company. The marketplace has a reputational motivation to keep your NFT safe and secure, but your NFT is still in their hands.

Self custody means that you have control over your own assets. The same mantra of "Not your keys, not your coins" also applies to NFTs. When you self-custody your Chia NFTs, it means that they are controlled by your keys, and therefore they are your assets.

Where does my NFT live?​

There are two components of a Chia NFT: on-chain and off-chain.

On-Chain: An NFT is a special type of coin called a "singleton". It contains three lists of URIs, which link to:

1. The NFT's data. This is typically an image file.
2. The NFT's metadata. This is typically a JSON file containing information about the NFT.
3. The NFT's license. This is typically a text file the spells out what rights the NFT's owner has.

The URI lists can only be prepended to; existing URIs cannot be modified or deleted.

For security purposes, each NFT contains a hash of the data represented by each of the corresponding URIs. The hashes can never be modified after minting.

Off-Chain: The actual NFT image lives in at least one location online. It can be stored under any number of URI protocols, including (but not limited to) http, https, ftp and ipfs.

Because Chia NFTs use a list of URIs (as opposed to a single one), the image can be stored in multiple locations. This is important for preserving an NFT's permanence because a single link could break.

For high-end NFTs, you may even want to store the image offline. Why would you do this? Let's say each of the online links is broken. As long as you (or anyone else) has a copy of the image, you can upload it and add a new link to the NFT. As long as the image's hash matches the hash that's built into the NFT, the new image is guaranteed to be identical to the original, and therefore valid. It is for these reasons that we believe NFTs on Chia will have stronger permanence than on any other blockchain.

The same rules apply for the metadata and license information. They can exist in multiple locations, but their hashes may not be modified after the initial minting. This prevents future owners from modifying this information, even though they can add new links.

The metadata URI can provide a wide variety of information about the NFT, including its title, properties (eg - year created, attributes, colors used, etc), rankings (eg - power: 25 out of 100, etc), collection name, as well as series number (eg - 1 of 100). The NFT's minter is free to include whatever information they want at the time of minting. The NFT1 spec allows different metadata formats to be developed. At the time of this writing, almost all NFTs use CHIP-7, which allows marketplaces to parse the metadata more easily.

The license URI can provide any relevant information concerning the NFT's license, such as who owns the Intellectual Property.

You can add new URIs to the data, metadata and license URI lists of any NFT you own. The new URIs will always be prepended to the list (added to the front of the list).

Is there a limit to the total data size of the metadata?​

No. (Well, you can't have infinite data, but Chia doesn't enforce any limits.)

Chia doesn't enforce a limit. However, because the links are contained within the NFT, as you add links, the size of the NFT also grows. If you were to add thousands of links, the NFT would eventually grow so large, it wouldn't fit inside a block and would no longer be spendable. If you only wanted to add a few dozen links, you would not run into this limitation.

On Chia's blockchain, everything is a coin. This includes XCH, CATs, and NFTs. Whenever any coin is spent, the original puzzle is revealed. Therefore, with NFTs, every link is posted on every spend.

You cannot modify or remove any existing URIs, or their corresponding hashes. This was a design decision to keep NFTs from being arbitrarily modified after their minting.

Does an NFT transaction take longer than an XCH (or CAT) transaction?​

In Chia, all transactions within a single block are processed simultaneously. As long as your NFT makes it into a block, it will take the same amount of time as any other transaction to process. The only caveat is that NFTs have a higher CLVM cost than XCH transactions. Therefore, if the mempool is full, a higher fee will be required in order for an NFT to be included in a block. However, if the mempool is not full, then this caveat does not apply.

How much is the fee for minting/selling an NFT?​

If the mempool is not full, then no fee is needed. If the mempool is full, then in order for your transaction to be included into the next block, you'll need to add a fee of at least 5 mojos per cost. The recommended minimum fee in this scenario is:

• Minting an NFT with a DID: 615 million mojos
• Transferring/selling an NFT: 335 million mojos

For other scenarios, see our NFT developer documentation.

What happens if exactly the same nft mint command is executed twice?​

Then two separate NFTs will be created. They will have different IDs, but everything else will be identical.

How do royalties work?​

An NFT's royalty percentage and receive address may optionally be included in an NFT upon its minting. After the NFT has been minted, the royalty may never be modified. If an NFT includes a royalty, then every time the NFT is sold, the appropriate percentage of the sale will be paid to the royalty's receive address (typically the address of the original artist). The amount paid both to the new owner, as well as the royalty address, will be clearly displayed within the Offer.

On other blockchains, royalties are paid at the discretion of the marketplace on which the NFT is custodied. On Chia, however, the royalties are built directly into the NFT. While under-the-table transfers could still circumvent royalties, they would also introduce counterparty risk for both the buyer and seller. In order to transfer a Chia NFT in a trustless manner, royalties must be paid.

Are there any royalties when exchanging an NFT for another NFT?​

No -- there would be no fair way to assess royalties for NFT-for-NFT offers, so these are treated as swaps with no royalties being calculated.

How are royalties calculated in offers that involve multiple assets?​

This depends on what assets are included in the offer. A few rules to keep in mind:

1. If more than one NFT is being traded, the royalties will be divided by the number of NFTs. For example:
• If 4 NFTs are being traded for 1 XCH, then each NFT will have an assumed price of 0.25 XCH
• If the royalty for each NFT is 10%, then each NFT will receive a 0.025 XCH royalty, for a total royalty of 0.1
• If the royalties are 10%, 8%, 5%, and 3%, then the NFTs will receive 0.025 XCH, 0.02 XCH, 0.0125 XCH, and 0.0075 XCH, for a total royalty of 0.65 XCH
2. If the NFTs are being traded for more than one fungible asset, then the royalties will be calculated for each asset individually
• For example, if 1 NFT is being traded for both 1 XCH and 1000 SBX and it carries a 10% royalty, then the royalties shall be 0.1 XCH and 100 SBX for this sale
3. If multiple NFTs are being traded for multiple fungible assets, then rules 1. and 2. will both be applied
4. When NFTs are traded for other NFTs, no royalties are exchanged

Can I use more than one royalty address?​

An NFT can include a maximum of one royalty address. However, because the royalty address can be any XCH address, the address can correspond to a smart coin that splits all royalties between multiple recipient addresses. See CHIP-8 for one potential implementation of split royalties.

Are royalties paid upon transferring an NFT?​

No. Transfers are conducted without any royalties being paid.

What is the Chia Friends project?​

Chia Friends was an airdrop of 10,000 NFTs. While Chia Network Inc gave these NFTs to 10,000 lucky recipients for free, they currently can be bought or sold just like any other NFT. All sales include a 3% royalty, which goes to the Marmot Recovery Foundation (here's their wallet address). For more information, see the Chia Friends website.

Is Chia Friends the same as the Holiday 21 token?​

No, these are two completely different projects.

Chia Friends was an airdrop of 10,000 NFTs. While Chia Network Inc gave these NFTs to 10,000 lucky recipients for free, they currently can be bought or sold just like any other NFT. All sales include a 3% royalty, which goes to the Marmot Recovery Foundation (here's their wallet address). For more information, see the Chia Friends website.

The Holiday 21 tokens were an airdrop of CATs for farmers who farmed a block in 2021. These tokens are redeemable for a Holiday NFT until November 10th, 2023. For more information please refer to our blog article about the Holiday NFTs.

Can I donate directly to the Marmot Recovery Foundation?​

You sure can! The Marmot Recovery Foundation website lists a variety of ways to donate to the cause of saving the Vancouver Island marmot from extinction.

Why do I have a Profile in my wallet?​

The Profile in your wallet is a Decentralized Identifier (DID). These can be used for tracking an NFT's provenance (history). Each NFT can be assigned to one DID. Though not strictly required, most NFTs will use DIDs for their added provenance. You can create a new DID by clicking the Settings button (the gear icon) in the lower left corner of Chia's Electron wallet.

Do I need to have a Profile to own/trade an NFT?​

No. NFTs can be left unassigned to a Profile.

How do I use the CLI for creating and using DIDs and NFTs?​

Our dev guide will walk you through creating DID and NFT wallets, minting an NFT, adding links and transferring your NFT, all using the CLI. In addition to the dev guide, we have a complete reference with all CLI commands for using DIDs and NFTs.

What RPC functionality is available for DIDs and NFTs?​

We also have a dev guide geared at using RPCs. For more details about each of our individual RPCs, see our reference for DIDs and NFTs.

What limitations, if any, are there for NFTs on Chia's blockchain?​

Chia's bulk minting tool allows you to mint 25 NFTs per block. If you attempt to mint more than this, you run the risk of your spend bundle sitting in the mempool for a long time. Additionally, if you don't use the bulk minting tool (or a similar tool), you can only mint one NFT per block.

Are there any security concerns I should consider?​

Unfortunately, fraud and outright theft are common in this space. If you take a few basic precautions, you'll have a much better chance of keeping your NFTs safe:

• Never give away your wallet's seed phrase. If anyone asks for it, they are attempting to scam you.
• When viewing an offer for an NFT, always check its provenance. The links to do this are located below the image when viewing it in an offer. An NFT's provenance is a complete record of its ownership history. This helps to verify that the NFT is authentic.
• Avoid directly sending someone money in exchange for an NFT. Use offers whenever possible. Occasionally, legitimate projects may require you to send them a token in exchange for an NFT, but the most secure way to buy and sell NFTs is with offers.

What recovery options are available if my NFT gets stolen?​

If your NFT is stolen, then unfortunately there's not much you can do, other than offer to buy it back from the thief or the current owner. This is why you should be extra diligent in avoiding theft in the first place, beginning with following the above tips.

What is the stance on NSFW NFTs being created?​

Chia Network Inc has no ability to censor content on the Chia blockchain. However, the metadata schema that most NFTs use includes a "sensitive_content" object, with a default value of false. This flag will indicate to wallets and marketplaces whether the NFT contains any sensitive content, which they can then use in deciding whether to display the NFT.

Starting in version 1.6.1, you can send and receive notifications to a specified puzzle hash. This will eventually enable us to support sending an offer to an NFT's owner without having to go through an exchange.

This functionality is disabled by default. It includes two settings in the wallet: section of ~/.chia/mainnet/config/config.yaml:

• accept_notifications - a boolean to specify whether you want to allow notifications to be received. If this setting is missing, it will automatically be set to false. Set to true to receive notifications
• required_notification_amount - the amount (in mojos) you require to be sent with a notification in order to receive it. If this setting is not specified, the default of 10000000 (10 million) will be used

In order to enable notifications, you can either add these settings manually, or rename config.yaml and run chia init. A new copy of config.yaml will be created which contains the new settings.

Finally, you need to restart Chia for these settings to be picked up.

Note that for version 1.6.1, messages are sent and received via an RPC only. This is a primitive that will be added to the GUI in a future release. For more information on sending and receiving messages, see our RPC documentation.

How can I use the CLI to send an Offer notification to the owner of an NFT?​

This process is documented under Example 2 of the send_notification RPC doc.

How can I sign and verify a message with an NFT?​

From the CLI, you can use the chia wallet nft sign_message command. See our CLI documentation for more details.

From the GUI, you can sign and verify messages from the ADVANCED tab in the Settings section. Note that as of February 2023, this has not been included in an official build yet. It is only available in the main branch of the chia-blockchain-gui repository. Eventually this will be added to an official build, but for now you can use it at your own risk.

1. Click Settings, click on the ADVANCED tab, and click CREATE SIGNATURE:

1. Click NFT, enter the message you want to sign, and click SIGN:

1. The message details will appear. Copy these details to the clipboard or save them to a file:

1. To verify a signature, click VERIFY SIGNATURE from the ADVANCED tab and enter the signature's details:

1. If the signature is valid for the details you entered, you will receive a Valid message:

Support/Miscellaneous​

What are the minimum officially supported OS versions?​

• MacOS 10.14 Mojave
• Windows 10
• Ubuntu 18.04 (20.04 highly recommended)
• Raspberry Pi OS 64 or Ubuntu 20.04 for Pi/ARM64 (Not recommended for plotting or timelord)

Can I run this on a Raspberry Pi 3 or 4?​

Raspberry Pi 4 is supported, but Pi 3 is not. Here are the instructions. This project requires a 64-bit OS. One can install and run harvesters, farmers, and full nodes on the Pi. Plotting on a Pi is feasible now with Chacha8 instead of AES, but the Pi isn't quick. Modern desktops and laptops plot in the 0.07 - 0.10 GiB/minute range and the Pi 4 plots at 0.025 GiB/minute. Pi is also not a candidate for Timelords or VDF clients...

How do I upgrade and keep my keys and plots?​

If you use the GUI, it will migrate from release to release for you. For both the GUI and the command line, your keys are stored on OS specific keychains. If running services from the command line only, chia init will migrate your config.yaml and dbs - if appropriate - to the new version. Keys and plots made before Beta 8 are deprecated and useless.

Where is the executable file to start Chia's reference wallet on Windows?​

Windows users can run C:\Users\<user ID>\AppData\Local\Programs\Chia\Chia.exe (be sure to replace <user ID> with the actual ID) to start the reference wallet GUI. This will also start a full node if that features has been enabled.

I installed Chia with the packaged installer. How do I run CLI commands?​

For power users, it is possible to install Chia from source. In this case, you will run Chia from a virtual environment on the command line.

After installing with the packaged installer, you can run Chia from the command line by invoking the executable file. The easiest way to set this up is by running the alias command. The exact command needed depends on your OS:

Chia setup

(Be sure to use powershell and update <username> to match the name of the user that installed Chia.)

If installed just for your user:

Set-Alias -Name chia "C:\Users\<USERNAME>\AppData\Local\Programs\Chia\resources\app.asar.unpacked\daemon\chia.exe"

If installed for all users:

Set-Alias -Name chia "C:\Program Files\Chia\resources\app.asar.unpacked\daemon\chia.exe"

To test your setup, run chia version. You should be shown the correct version. For example:

chia version1.6.1

Where are the config and log files stored?​

Linux & macOS

Chia config: ~/.chia/mainnet/config/config.yamlChia logs: ~/.chia/mainnet/log/

Windows

Chia config: C:\Users\%USERNAME%\.chia\mainnet\config\config.yamlChia logs: C:\Users\%USERNAME%\.chia\mainnet\log\

CLI

You can use the CLI command chia configure --set-log-level INFO to set your log level to the useful INFO setting. Be sure to restart Chia after making settings changes. Config File

In config.yaml you can set the level of detail for your logs.

Look for this section in config.yaml. It’s useful to change the logger setting log_level from WARNING to INFO to get the detail needed to troubleshoot.

logging:&id001log_filename: log/debug.loglog_level: INFOlog_stdout:false

How do I quickly search the log file for errors?​

You can run grep (Linux, macOS) or Select-String (Windows) to search through your logs for relevant information.

Linux & macOS

cat ~/.chia/mainnet/log/debug.log | grep -i 'error'

Windows

Get-Content -Path "~\.chia\mainnet\log\debug.log" | Select-String -Pattern "error"

Harvester log lookup examples​

The time it takes to do a proof challenge should be below 30 seconds. If you see higher times, something is wrong with your setup.

Here are some example commands you can use to examine debug.log for problems.

Linux & macOS

tail ~/.chia/mainnet/log/debug.log | grep eligible

Windows

Select-String -Path "~\.chia\mainnet\log\debug*" -Pattern "eligible"Select-String -Path "~\.chia\mainnet\log\debug*" -Pattern "Found [^0] proof"Select-String -Path "~\.chia\mainnet\log\debug*" -Pattern "Farmed unfinished_block"Get-Content -Path "~\.chia\mainnet\log\debug.log" -Wait | Select-String -Pattern "found"

What is the difference between chia and Chia (chia capitalization)?​

Chia - depending on context, this can refer to Chia Network the company, the Chia software (Chia client), or the Chia blockchain chia - lowercase chia refers to the Chia token, XCH. Similarly, mojos are lowercase.

How can I use PFX certificates for .NET development on Windows?​

By default, Chia will install .crt certificates in ~/.chia/mainnet/config/ssl. If you are a .NET developer who is developing an application that connects to a full node, it is much easier to do this with .pfx certificates. This is because the TLS layer on Windows requires that the private key be written to disk (in a particular way). The PEM-based certificate loading doesn't do that, only PFX-loading does.

We plan to add .pfx certificates by default in a future version of Chia. However, for now there is an easy workaround -- export the certificates to .pfx and immediately reimport them. The command to do this in c# is:

cert = new X509Certificate2(cert.Export(X509ContentType.Pfx))

info

This issue only affects developers of Windows .NET applications. It does not affect Chia users on Windows, nor does it affect users or developers on other Operating Systems.

What are the plans for the project and what are its tokenomics?​

This is the Repository FAQ which focuses on how to use the software. We have released our Business Whitepaper that goes into details of both the tokenomics, the pre-farm, and our go to market strategy. Additionally you can review the Project FAQ.

How can I contribute?​

You should check out CONTRIBUTING.md in the repository but the quick answer is to please base your pull requests off the dev branch. The dev branch will only accept rebase merges or squash merges. You can help translate the application as well. Translating the GUI is especially useful and pretty easy to do with our Crowdin Chia-Blockchain-GUI tool.

What microphone is Gene using?​

Gene uses an Electro-Voice RE20.

Isn't the current international monetary system good enough?​

No. Around the world, governments and banks cause problematic interactions that make banks difficult to trust, especially in volatile regions like Hong Kong, Venezuela Argentina or Lebanon. International payments, when they are available and work, are slow, expensive and insecure. International SWIFT wires often take 1-5 days. Correspondent banks often charge up to 3% and since the changes to banking since 9/11 and 2008, many countries have limited correspondent banks. International wire fraud losses are very large, and we have a better solution to mitigate these problems.