This motion proposes the following schema:
Name: dsnp.tombstone Model Type: Parquet Payload Location: IPFS 
Parquet schema:&nbsp;
<a href="https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Tombstone.md">https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Tombstone.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.tombstone  
Model Type: Parquet  
Payload Location: IPFS  
  

Parquet schema: 

[https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Tombstone.md](https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Tombstone.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.

With a proven track record of supporting 68 networks in the Polkadot/Kusama ecosystems, OnFinality aims to provide a basic RPC API service for all 38 Polkadot parachains. The proposal seeks to address the divide between well-funded parachains and struggling newcomers by ensuring universal access to reliable, performant, and SLA-supported RPC API endpoints. OnFinality suggests an immediate solution until a long-term infrastructure bounty is established, emphasizing the importance of supporting all parachains to foster network growth and developer adoption.

Organize and execute the Hackathon in Shangai,China.

- **Problem Statement:** Developers need to be aware of a schema change in the dsnp.tombstone model from BYTE_ARRAY to STRING.
- **Significance:** Ensuring developers are informed about this semantic change is crucial for maintaining data integrity and compatibility.
- **Proposed Solution:** Update the schema of the dsnp.tombstone model from BYTE_ARRAY to STRING.
- **Expected Outcomes:** Improved data handling and compatibility for developers working with the dsnp.tombstone model.

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

No Active Proposals