I used to think a decentralized database meant every node kept a full copy of the data, the same way most blockchains work.
Imagine a bank that refuses to store the actual transaction papers. Instead it only keeps a sealed envelope containing a cryptographic fingerprint of those papers, and a group of managers must all sign that fingerprint before it becomes official. Anyone can later prove the papers haven’t been changed without ever opening the envelope.
That’s essentially how SXT Chain handles data. Validators never store the raw tables. They create a cryptographic commitment for each table and threshold-sign it through BFT consensus. The commitment becomes the root of trust.
The actual data still has to live somewhere usually with archive nodes or indexers. If those disappear, you can still prove the commitment is valid, but you can no longer run the query.
So is this a tamperproof database, or just a tamperproof fingerprint of a database?
@SpaceandTime #sxt $SXT
Imagine a bank that refuses to store the actual transaction papers. Instead it only keeps a sealed envelope containing a cryptographic fingerprint of those papers, and a group of managers must all sign that fingerprint before it becomes official. Anyone can later prove the papers haven’t been changed without ever opening the envelope.
That’s essentially how SXT Chain handles data. Validators never store the raw tables. They create a cryptographic commitment for each table and threshold-sign it through BFT consensus. The commitment becomes the root of trust.
The actual data still has to live somewhere usually with archive nodes or indexers. If those disappear, you can still prove the commitment is valid, but you can no longer run the query.
So is this a tamperproof database, or just a tamperproof fingerprint of a database?
@SpaceandTime #sxt $SXT
