βοΈ What Is a Blockchain (and What It Means for Allfeat)
Introduction
To understand how Allfeat works β and especially how metadata behaves over time β you need to understand what a blockchain really is.
Many misunderstandings come from thinking that data on a blockchain is either:
- permanently frozen and can never change, or
- completely editable like a regular database.
The truth is: itβs neither.
Letβs clarify.
π¦ A Blockchain Is a History of Blocks
A blockchain is a continuously growing list of blocks, each containing:
- A batch of validated transactions
- A reference to the previous block (via a cryptographic hash)
- A timestamp and other metadata
Together, blocks form a linked, immutable chain β meaning:
- You can always read the full history
- You cannot modify blocks that are already finalized
- The state of the system is reconstructed by replaying all blocks in order
This applies to Allfeat too.
π§ What Gets Stored in Allfeat's Blocks?
In Allfeat, every action on metadata is a transaction:
- Submitting a new MIDDS
- Certifying a MIDDS
- Marking it as ready for review
- Proposing an edit
- Linking two MIDDS together
Each of these actions is written into a block.
The result is a verifiable timeline of who did what, when, and how.
π Can MIDDS Change Over Time?
Yes β but not by modifying the past.
Hereβs how it works:
β You cannot edit a block.
β But you can submit a new transaction that modifies the state.
That means:
- If you submitted a MIDDS and later realize you forgot a detail, you can propose an update
- If the update is accepted and validated, it becomes part of a new block
- The new state replaces the previous one β but the history is preserved forever
This is called append-only logic:
You donβt delete or overwrite, you add new instructions.
π‘οΈ What Does "Immutable" Really Mean?
"Immutable" does not mean βfrozen forever.β
It means that the history of actions cannot be altered.
In Allfeat, this brings real benefits:
- π΅οΈ Auditable: Anyone can track how a MIDDS was created, updated, or certified
- π§Ύ Traceable: Conflicts or fraud can be detected by comparing past actions
- π Dependable: Apps, organizations, and people can rely on a single public source of truth
Even when a MIDDS evolves, its historical path remains visible and provable.
π How MIDDS Evolve
Hereβs a simple example of how a MIDDS lifecycle might look on-chain:
- πΆ Block #421: A Musical Work is submitted
- β Block #426: The work is certified by Trusters
- βοΈ Block #490: A correction is submitted (wrong BPM)
- π Block #491: The correction is approved and the state is updated
At any point, someone can query:
- The current version of the MIDDS
- The full change history (who submitted what and when)
This gives Allfeat both durability and flexibility β a powerful combination that traditional metadata systems often lack.
β In Summary
- A blockchain is a permanent record of events, not a database you βeditβ
- Allfeat stores metadata changes as events across time
- A MIDDS can evolve β but always through new transactions, never by modifying the past
- This ensures a balance of immutability, transparency, and data evolution