KTAPEOUT

KTAPEOUT 0.5.0 · Kaspa Testnet-10

Verifiable applications on Kaspa.

Every application gets a name on Kaspa and a content-addressed release. Before anything opens, the Shell checks both against live Testnet-10 nodes. Looking around needs no wallet.

Open an application Start building
How an application opens The Shell checks the name, the release and every file, then opens the application only if all three pass. NAME RELEASE FILES CHECK 2 TN10 NODES · SHA-256 PER FILE
Signed off before it opens

01 · Try it now

Open a live application

All applications →

DAG Knight

A walletless action game inspired by the Kaspa BlockDAG. Play directly in your browser.

GameNo wallet
Open DAG Knight

KasNote

Private notes you own: encrypted on your device before they are stored on Kaspa Testnet-10.

ProductivityWallet to write
Open KasNote

KTAPEOUT Registry

The naming registry itself: look up namespaces, releases and application identities.

ProtocolNo wallet
Open the Registry

02 · How it works

From an idea to an address anyone can check

  1. Step 1

    Compose

    Describe your application with Profiles: declared state, inputs and transitions. The toolchain turns them into a deterministic artifact.

    About Profiles →

  2. Step 2

    Publish

    Package the release so every file is content-addressed, then bind your registered name on Kaspa to that exact release.

    Build a package →

  3. Step 3

    Open and verify

    When someone opens the name, the Shell confirms the binding on two Testnet-10 nodes and checks every file before the app runs.

    See the network →

03 · For developers

Scaffold a project in two commands

The Rust CLI creates a starter project and checks its declarations locally. Nothing is signed or broadcast until you decide to publish.

FROM THE REPOSITORY ROOT
cargo run --locked -p ktapeout-cli -- init \
  --template StateMachine --network testnet-10 --output ./my-app
cargo run --locked -p ktapeout-cli -- dev workflow \
  ./my-app/workflow.json

04 · Interaction

Explore first. Sign when it matters.

Walletless by default

People can browse, resolve and use public application state without connecting anything.

Wallet when needed

Signing and settlement appear only where an application needs the user's authority, and the wallet shows every transaction for approval.

05 · Resources

Go deeper