1.6.0 is now available for download. This release is largely focused on providing a new primitive called DataLayer for developers. We also have added a new feature enabling dust filtering when syncing a wallet.
Key features of DataLayer include:
Key Value Store
- Tabular data can be stored as key/value pairs
- Keys and values of each row are stored as binary and can be any data type, including for example JSON
- The hash of the table (“root”) is stored in a singleton on chain
Data Propagation
- Datalayer data can be hosted by most/any HTTP server, including cloud providers like AWS, Azure, GCP
- Support for multiple URL mirrors of the data. Mirror URLs are announced on-chain to enable automatic discovery
- Includes a basic HTTP server with Chia
- Anyone can participate in ensuring the durability of blockchain data by hosting a mirror
Proof Of Inclusion
- The Chia DataLayer singleton can be spent by its owner in a way that cryptographically proves the inclusion of a particular row (or multiple rows), specified by the hash of the data in that row
Two-Party Commit
- Using DataLayer offer files and proofs of inclusion, two people can coordinate a simultaneous (“atomic”) update of their respective data
For end users:
Dust filtering
This is a new feature for end users that enables a wallet sync to ignore dust when calculating wallet balances. This benefits dusted wallets by further improving wallet sync speed through trusted or untrusted sync. After the first 200 transactions, the wallet will ignore coins below the dust size of 1 million mojos. Both the dust size threshold and the number of transactions are configurable in config.yaml. When dust is filtered the coin values do not show up in any transaction list and will also result in balances being calculated without the value of the dust being filtered. See our FAQ for more details.
Added
- DataLayer
- GUI Settings section for
DataLayer
Enable DataLayer
toggleEnable File Propagation Server
toggle
- XCH Dust Filter
- GUI Settings
Auto-Login
toggle (GUI only)
Modified
- Delayed pool config update until after sync
- Minor change to handling sync height to avoid race condition with blockchain DB
- Ignore
FileNotFoundError
when checking SSL file permissions if the file doesn’t exist
Fixed
- Fixed missing wallet
state_changed
events for GUI - Fixed several bugs related to wallet sync status
- Fixed GUI issue for CAT offers where the CAT Tail would not show in the tooltip for
Unknown CAT
s (Chia-Network/chia-blockchain-gui#950)
Known Issues
- The CLI command
chia configure --enable-data-server
, and theconfig.yaml
parameter atdata_layer.run_server
have no effect, and will be removed in the future - DataLayer offers cannot be accepted (
take_offer
) if the offer has inclusions for the exact same key/value data for both maker and taker inclusions.