The SpaceBudz wormhole contract. Moving from CIP-0025 to CIP-0068.
Policy Id: 4523c5e21d409b81c95b45b0aea275b8ea1406e6cafea5583b9f8a5f
This contract is immutable and autonomous.
It has no admin keys and cannot be upgraded.
No one controls its execution after deployment.
Use is entirely voluntary and at your own risk.
No guarantees are made regarding its functionality, security, or future behavior.
Born in the early days of 2021, this project began as a foundational experiment to push the boundaries of what was possible on Cardano. In 2023, a migration using the Wormhole contract was undertaken. It was a strategic move that accompanied an art overhaul. The need for this transition arose when it was discovered that some graphic elements in the initial SpaceBudz collection were not entirely original, prompting a decision to ensure all artwork was authentic.
This software is provided "as-is" under the original MIT License.
SpaceBudz NFTs are designed as digital collectibles. They should not be relied upon for authentication, identity, or security-critical logic in smart contracts.
In particular, smart contracts should not depend on SpaceBudz metadata for authorization or validation purposes.
Additionally, CIP-0068 is a living standard and its metadata schema may evolve over time. Future revisions or extensions to the standard may introduce changes that are not compatible with assumptions made by external contracts.
SpaceBudz should therefore be treated purely as collectible assets rather than protocol-level primitives.
- Deno >= 1.28.1
import { Contract } from "https://deno.land/x/wormhole@1.0.4/mod.ts";npm install @spacebudz/wormhole
import { Lucid, Blockfrost } from "https://deno.land/x/lucid@0.10.9/mod.ts";
import { Contract } from "https://deno.land/x/wormhole@1.0.4/mod.ts";
const lucid = await Lucid.new(new Blockfrost(...));
lucid.selectWalletFromSeed(
"<seed_phrase>",
);
const contract = new Contract(lucid);
// Logging the SpaceBudz policy id
console.log(contract.mintPolicyId);
// Migrate SpaceBud #10
console.log(await contract.migrate([10]));deno task build:contract
See requirements.
deno task build
Outputs a dist folder.
Lucid needs to be imported separately and is a peer dependency (version @0.10.9).
migrate(ids: number[]): Promise<TxHash>deployScripts(): Promise<TxHash>burn(id: number): Promise<TxHash> move(id: number): Promise<TxHash> updateIp(url: string): Promise<Transaction> updateRoyalty(royaltyRecipients: RoyaltyRecipient[]): Promise<Transaction> getRoyalty(): Promise<RoyaltyRecipient[]>getMetadata(id: number): Promise<Json>hasMigrated(id: number): Promise<boolean>getDeployedScripts(): Promise<{ mint: UTxO }> In order to migrate a SpaceBud of the old collection, three outputs need to be created:
- Lock address holding the old SpaceBud
- Reference address holding the
reference NFTwith the metadata in the datum - Wallet address receives the
user NFTthat represent the new SpaceBud
The reference NFT and user NFT are minted during the transaction and need to follow the CIP-0068 (222) sub standard.
To validate metadata and correctness of the minted SpaceBud a merkle tree is used that contains 10,000 entries. Each entry is a sha2_256 hash of:
metadata hash + asset name of reference NFT + asset name of user NFT + asset name of single asset sent to Lock address
Only a small merkle tree proof needs to be brought on-chain to make sure a SpaceBud is minted correctly
To keep integrity for the twins 1903 and 6413 (with quantity 2) some extra steps are required.
Important is that there exists only ever one reference NFT. In order to achieve this the reference NFTs including their respective metadata are preminted and locked in the script UTxO.
Whenever you migrate a twin you mint a mock reference NFT (with label 1), that doesn't really have any functionality, but it allows to keep the existing contract logic as it is.
No unnecessary complexity and risk needs to be introduced into the contract.