Documentation

CLKT saves WordPress posts and media to Arweave using a self-managed wallet. The plugin is available from the WordPress.org plugin directory, and the public source repository is available on GitHub.

Installation

  1. Install CLKT from the WordPress.org plugin directory, or download the plugin ZIP from WordPress.org.
  2. In WordPress admin, go to Plugins > Add New and search for CLKT, or upload the ZIP manually.
  3. Activate CLKT, then open Settings > CLKT.

Wallet Setup

  1. Install the Wander browser extension.
  2. Create or import an Arweave wallet and fund it with enough AR for storage fees.
  3. Open Settings > CLKT and connect the wallet.

First Upload

  1. Open a published post in the WordPress editor.
  2. Review the CLKT panel and estimated upload cost.
  3. Click Save Forever to send the current version to Arweave.
  4. After upload, CLKT stores the Arweave transaction ID and shows the version in the post timeline.

Atomic Assets and CLKT Records

A CLKT Record is not a second upload. It is the CLKT-specific profile inside an atomic asset-compatible Arweave object.

The atomic asset layer gives CLKT a permaweb-native envelope for durable data, tags, ownership, discoverability, and licensing. CLKT aligns this layer with the published Tradeable Atomic Asset spec: one permanent identifier containing data, labels, and an agreement. The CLKT Record layer gives the saved item product meaning: where it came from, who collected it, how it can be restored, and how it relates to other saved or remixed objects.

  • Standard tags: Content-Type, Type, Title, Description, and optional Topic tags for permaweb discoverability.
  • CLKT tags: App-Name, CLKT record version, source URL, source domain, collector, collection ID, and restore manifest references.
  • Tradeable mode: SmartWeave contract tags and UDL license tags are the path for owner, license, and market behavior when CLKT records become collectable or tradeable assets.
  • Metadata: compact display fields such as title, description, author, topics, and source URL.
  • Payload: the full CLKT Record JSON, including attribution, hashes, restore manifest, media list, version history, and remix references.
{
  "schema": "clkt-record-v1",
  "type": "wordpress-post",
  "source": {
    "url": "https://example.com/post",
    "publisher": "Example Site",
    "author": "Jane"
  },
  "collector": {
    "wallet": "arweave-wallet-address"
  },
  "proof": {
    "contentHash": "...",
    "packageHash": "...",
    "restoreManifestTx": "..."
  },
  "relationships": {
    "previousVersion": "...",
    "derivedFrom": []
  }
}

This keeps CLKT interoperable with the permaweb while giving the product room for open collecting, attribution, remixing, wallet-based collections, and trust signals.

Auto-Upload

Global auto-upload can be enabled from Settings > CLKT. Individual posts can inherit the global setting or override it. When a published post changes, CLKT compares the content hash and uploads a new version only when needed.

Bulk Upload

Use the Bulk Upload tab in Settings > CLKT to select multiple posts, preview estimated costs, and upload content in batches.

Encryption

CLKT can encrypt content before upload using a global or per-post password. Passwords are not recoverable by CLKT, so keep a secure copy before uploading encrypted content.

External Services

CLKT connects to Arweave, CoinGecko, Goldsky GraphQL, and AO Testnet during normal operation. Details are documented in the plugin readme and in the site Privacy Policy.

API for developers

CLKT includes a REST API (clkt/v1) so you can save content to the permanent web headlessly — from a script, CI, or an agent — without opening wp-admin. The plugin never holds a key: signing happens in your own wallet, and the API only prepares, records, and verifies.

The flow is GET /wp-json/clkt/v1/prepare/<id> → sign & dispatch with your own wallet → POST /wp-json/clkt/v1/save/<id>. All routes require a WordPress application password. Endpoints include health, prepare, save, status, records, auto-save-queue, and admin settings.

Full reference and a working Node dispatcher: CLKT API docs on GitHub.

Support