Ownership is only the beginning

Most NFTs can prove which address owns an asset. A composable game asset needs more.

Dungeon Saga is building toward rules that can also verify:

• which fragments compose a Hero;
• whether those fragments belong to the player starting the forge;
• which contract state transition created the Hero;
• whether its composition proof remains valid after a transfer; and
• how the original fragments can be released safely in a future UNFORGE.

A Hero should not be a row that a project database can rewrite. It should carry history.

Act I

FORGE — an on-chain birth, not a backend exchange

The player begins by signing with their own wallet. The UTXO contract then validates fragment quantity, type, and ownership. Only an eligible set can enter the protocol state from which a new Hero is forged.

• The player does not hand custody of the assets to the project.
• The backend cannot skip the rules and simply issue a Hero.
• Every fragment must pass the same verifiable constraints.
• An invalid combination cannot masquerade as a valid forge.

SIGNVERIFYFORGE

This is not a backend distribution. It is a birth Bitcoin rules can verify.

Act II

BIND — a verifiable lineage

When a Hero is forged, it forms a verifiable relationship with the fragments that made it. The result records not only that the Hero exists, but why it was allowed to exist.

Act III

TRANSFER — ownership can travel without losing provenance

A forged Hero can move into a player's wallet and circulate freely. Its owner may change, but the relationship to its original fragments does not disappear and does not need to be reconstructed by our backend after every transfer.

A future act

UNFORGE — groundwork for a reversible asset lifecycle

This architecture also lays the foundation for a later UNFORGE release. A future implementation is intended to let the current Hero holder prove ownership, destroy the corresponding Hero, and release its bound original fragments without project custody.

UNFORGE is not part of the around-August-15 FORGE launch commitment. It will ship in a later release.

Fragments → Hero → transfer → future Hero destruction → fragment release

Why the additional time?

A Bitcoin UTXO state transition must become a correctly signed, independently verifiable transaction with a safe failure path. Our remaining work includes:

1. complete constraint tests for multi-fragment forging;
2. boundary validation for Hero-to-fragment bindings;
3. state-continuity tests after Hero transfers;
4. signature and transaction compatibility across supported wallets;
5. refund and asset-recovery paths for failure, timeout, or interruption; and
6. lifecycle stress tests spanning FORGE and the groundwork for future UNFORGE.

For player assets, success on the happy path is not enough. Failure must be safe too.

What this protocol could mean

Based on the public material available to us and to the best of our knowledge, we have not found a mature, complete, publicly reproducible Bitcoin precedent that combines multi-asset composition, Hero mint binding, free transfer, future non-custodial reversal, timeout refunds, and asset self-recovery in one UTXO asset lifecycle.

This is not a claim that no related experiment exists. It is why we are taking the time to test the protocol as infrastructure for Dungeon Saga rather than treating it as a one-off exchange flow.