Version 2.1.0 of the Chia reference client is now available for download! This release features farming and user experience improvements, including updates to GPU plotting support, Credential Restricted CATs, and upgraded support for offers, WalletConnect, and DataLayer features.
Note: Version 2.1.0 includes additional changes originally intended for the 2.0.0 hard fork and is a required update.
Farming Improvements
GPU Plotting Support on Systems with 128GB of DRAM
Version 2.1.0 comes bundled with the latest version of BladeBit, which supports plotting with 128 GB of DRAM. This enables desktop PC users to leverage their existing systems as plotters rather than requiring an upgrade to workstations with higher RAM performance.
See our plotting guide for more information.
General User Experience Improvements
Offers
Expiring Offers
In version 2.1.0, users can create offers that expire automatically by a certain time. Expiring offers simplify user management of available offers by mitigating stale offers and stimulating a higher frequency of offer trading. Instead of tracking all open offers and canceling outdated versions, users can set an offer’s expiration time in advance. If an offer expires without being accepted, users will have the option to recreate the offer and set a new expiration period.
The wallet will now default to a seven day expiration period in the GUI during offer creation. Users may modify the default timing for all offers, or change/remove the timing for one specific offer. Offer takers reviewing an offer will be able to see the expiration time of the offer and will be notified with an error message when viewing or attempting to accept an expired offer. All digital assets currently supported by the Chia wallet are eligible for inclusion in an expiring offer.
Expiring offers are a backwards compatible update. Users operating on older versions of the Chia wallet will not be able to see the offer’s expiration timer, and expired offers will not be accepted.
For those new to Chia, we have created a beginner-friendly guide to learn how to use offers.
Developers can use the new options in the create_offer_for_ids RPC when adding support for expiring offers in their software.
Credential Restricted CATs
Successfully tokenizing real-world assets hinges on security and regulatory compliance. Our Credential Restricted (CR) Chia Asset Tokens primitive brings us one step closer. While these tokens will appear and operate as regular CATs, an additional requirement of holding a Chia Verifiable Credential must be met for the tokens to be sold, traded, or transferred. Receivers of CR CATs must possess an on-chain Verifiable Credential (VC) from a designated issuer to hold the token, ensuring only verified users can obtain a CR CAT.
Offer Trading for CR CATs
As part of adding support for CR CATs, we’ve added offer trading support to leverage Chia’s decentralized offer primitive to enable true peer-to-peer trading of these special CATs. VC holders are now eligible to both create and accept buy or sell offers for CR CATs – those who do not hold the required VC(s) will not be able to accept an offer for CR CATs.
WalletConnect
Wallet Key Selection During WalletConnect Pairing
We’ve streamlined the wallet connection process with the latest updates to our WalletConnect pairing application. During a wallet pairing, users can select specific wallet keys from a dropdown menu and connect their selection to the dApp regardless of which wallet is actively synced.
For more information on configuring and using WalletConnect with the Chia reference wallet, see our guide.
Addition of getPublicKey Command
Now, users can easily provide their master public key directly to a dApp with the new getPublicKey command. This command allows dApps to request access to the user’s master public key. Given the command authorizes the dApp to scan all derived wallet addresses, users should exercise caution when providing their master public key.
The complete list of WalletConnect commands can be found in our developer guide.
For Developers and Creators (RPC and CLI only):
Mint Credential Restricted CATs
With the introduction of CR CATs comes the ability to mint these security tokens using our CAT admin tool. When minting CR CATs, the DID of the VC issuer along with the expected proofs required in the VC will be specified to ensure only holders of VCs from that specific issuer can hold or trade CR CATs. Check out our tutorial for steps on how to mint CR CATs.
DataLayer
Chia’s DataLayer powers secure and auditable data sharing among multiple parties. Version 2.1.0 features various updates to the application aimed at improving its accessibility, security, and efficiency, which we’ve outlined below:
Wallet Selection with Fingerprint
Fingerprints can now be used to alternate a user’s active wallet while operating any DataLayer command. In previous versions, DataLayer commands were assumed to be for the current active wallet key. With this update, the active wallet will switch according to the specified fingerprint, allowing developers to interact with DataLayer singletons stored across various wallets on the same computer.
Our DataLayer CLI reference has been updated with all of the latest options.
Default Deletion of Local Data When Unsubscribing
All local files for a DataLayer singleton will be automatically deleted after a user unsubscribes from a specific DataLayer integration. Deleting unnecessary local data simplifies the management of local file storage and frees hard drive space.
DataLayer Plug-ins: Custom Header Configuration
To enhance the security of the DataLayer plug-in system, we’ve added a custom authorization header. In version 2.1.0, users will find a custom header option for config.yaml, specifying which API keys will be used for DataLayer plug-in communications.
Refresh of CLI and RPC Help Text and Output
We’re rolling out a standardized JSON output for DataLayer commands, allowing for a more user-friendly processing experience. CLI and RPC outputs are now available in a refreshed JSON format for the following commands:
- chia_data_create_data_store
- chia_data_get_owned_stores
- chia_data_get_root_history
- chia_data_get_keys
- chia_data_get_keys_values
General
Addition of get_public_key and get_public_keys daemon RPCs
We’ve enabled RPC access to users’ master public keys in this release. The updated get_public_key and get_public_keys RPCs can be used to retrieve key details, such as fingerprints, public keys, and labels. As a new RPC call, these commands only share key information without risk of sharing the seed phrase or private key data.
See our daemon RPC reference for more information.
WalletConnect
Addition of getPublicKey Command
Now, dApp developers can easily request users for their master public key with the new getPublicKey command. This command allows dApps to request access to the user’s master public key. Given the command authorizes the dApp to scan all derived wallet addresses, users should exercise caution when providing their master public key.
See our documentation for a complete list of available commands.
Removal of createNewCATWallet Command
Following the introduction of the CAT minting tool, we’re removing functionality for the createNewCATWallet Command from the Chia wallet backend. Moving forward, all CAT minting should occur through the new CAT minting tool. Users should use addCATToken as the updated command for adding a CAT wallet.
Other Fixes and Improvements
Read our release notes for details on other fixes and improvements included in this release.
