GuideSystem3 min read
Ethereum, Tezos & Anchors
Use the same KEEL words across chains, while checking the storage, wallet, and release path on each.
Select an underlined word to see what it means.
In this guide
- Hold
- Small file pieces, called Slugs, live in storage containers called Ingots. Welds record how to join them.
- Die / Slab
- The collection records who owns each Slab. It can issue individually identified tokens or editions with multiple copies.
- Sleeve
- The token supplies its name, preview, and opening information. A compatible gallery can open the interactive work.
- Wallet review
- Review the network, your sending account, the receiving contract, the requested action, and the payment amount.
Each network has its own stored files, collections, and balances. Keep the network with every contract address.
The same file keeps one identity on every chain.
A MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry → identifies file bytes. A portable root is a combined fingerprint for a declared collection of resources. These content identities can stay the same when the exact files are copied to another chain.
The network, contract address, token record, and storage location still identify separate things. A copy of the files does not transfer ownership of the original SlabThe collectible token recorded in your wallet. It identifies an owned item and points to its work.For exampleYou collect Tidal Study #7. That token is your Slab; the artwork files have their own storage records.Full glossary entry →.
The words stay the same; the machinery differs.
Both networks use KEEL’s HoldKEEL's native onchain storage for the file bytes and the instructions for joining them back together.For exampleYour sketch and its shared drawing library are stored as separate objects in the Hold.Full glossary entry →, HarnessThe composition that runs the work: its selected resources, runtime context, and isolated environment.For exampleThe Harness connects your sketch to its drawing library and runs it inside the Cage.Full glossary entry →, and other system roles. Ethereum-style chains use EVM contracts. Tezos uses its native contract machine and token interface.
Storage formats, wallet operations, and publishing options differ by network. The Ethereum and Tezos guides explain each path using the same KEEL vocabulary.
| Shared | Network-specific |
|---|---|
| Content graph and integrity checks | Store, registry, and builder contracts |
| Creator intent and resource declarations | Transaction encoding and wallet transport |
| Verification concepts | Receipts, finality, and chain evidence |
| Presentation goals | Measured read limits and supported host integrations |
Read what an Anchor actually establishes.
An AnchorA record on another chain that points to one version of your work, so people can check a copy is kept there too.For exampleAn Anchor may document a checked copy; an attested route additionally depends on the named parties vouching for its observation.Full glossary entry → ties a stated revision to particular chain or carrier evidence. Some routes check chain proofs; attested routes rely on named parties vouching for an observation. Inspect which route and revision you have.
GripHow many chains are recorded as holding an Anchor. The count is meaningful alongside each record's evidence.For exampleTwo listed chains do not by themselves prove that every dependency is retrievable from both.Full glossary entry → counts chains recorded as holding an AnchorA record on another chain that points to one version of your work, so people can check a copy is kept there too.For exampleAn Anchor may document a checked copy; an attested route additionally depends on the named parties vouching for its observation.Full glossary entry →. The count needs the underlying evidence and available files to be useful. Anchoring by itself neither bridges a token nor proves every dependency is present.
Technical detail: portable roots and trust classes
Portable manifests commit address-neutral resource identities. Chain-specific anchor records bind those commitments to native records, proof inputs, or attestations. Trust classes include direct/native checks, proof-based verification, and named attestors. Cross-chain minting is a separate opt-in operation with its own route, recipient, authorization, and replay rules.
Ask OnKeel Studio what it supports.
OnKeel Studio publishes a short list of what it supports right now: networks, upload limits, and ways to publish. Tools read that list before they send your files or ask your wallet to sign.
If your Tezos route is blocked, the plan should explain that and retain your Tezos choice. Choosing Ethereum is a separate creator decision.
Technical example: read a configured Studio’s capabilities (Node.js)
import { fetchStudioCapabilities } from "@keel/sdk";
// Supply the URL of the Studio your application connects to.
async function inspectStudio(studioUrl) {
const studio = await fetchStudioCapabilities(studioUrl);
return studio.chains.map(({ network, status, reason }) => ({
network, status, reason,
}));
}
// This reads capabilities. It does not upload or publish a work.