This motion proposes the following schema:
Name: dsnp.update Model Type: Parquet Payload Location: IPFS
Parquet schema:&nbsp;
<a href="https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Update.md">https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Update.md</a>
Frequency discussion:&nbsp;
<a href="https://github.com/frequency-chain/frequency/issues/2125">https://github.com/frequency-chain/frequency/issues/2125</a>
TL;DR: Fields containing a content has are changing from BYTE_ARRAY to STRING. While this is compatible at a raw binary level, it is semantic change that developers should be aware of. Note that there is no "legacy" data on mainnet at this time, so the original schema will never be used.

This motion proposes the following schema:

Name: dsnp.update  
Model Type: Parquet  
Payload Location: IPFS

Parquet schema: 

[https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Update.md](https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Update.md)

Frequency discussion: 

[https://github.com/frequency-chain/frequency/issues/2125](https://github.com/frequency-chain/frequency/issues/2125)

TL;DR: Fields containing a content has are changing from BYTE\_ARRAY to STRING. While this is compatible at a raw binary level, it is semantic change that developers should be aware of. Note that there is no "legacy" data on mainnet at this time, so the original schema will never be used.

- **Problem Statement:** 
  - Updating fields from BYTE_ARRAY to STRING in the Parquet schema for dsnp.update model on IPFS.
  - Intended Audience: Developers working with LibertyDSNP and Frequency.

- **Significance:** 
  - Transitioning fields in the schema is crucial for maintaining data integrity and ensuring developers are informed about the semantic change.

- **Proposed Solution:** 
  - Change fields containing content hash from BYTE_ARRAY to STRING in the dsnp.update Parquet schema on IPFS.

- **Expected Outcomes:** 
  - Enhanced data compatibility and developer awareness without affecting existing data on the mainnet.

#48 Schema proposal: dsnp.update (update for DSNP 1.3)

No Active Proposals