How Helixdesk works

When you open a ticket, Helixdesk shows a short message containing a timestamp and a random nonce, for example: Helixdesk support · 2026-01-01T10:00:00.000Z · 9f2a41c0.

Your wallet signs that message with your private key. Helixdesk then checks the ed25519 signature against your public address in your browser. If it matches, the ticket is tied to that wallet.

Signing a message is not a transaction. It costs no SOL and cannot move funds.

A Solana transaction ID is a base58 signature, usually 87 or 88 characters long. You can copy it from your wallet activity or from a block explorer.

In the ticket form, paste one or more signatures separated by spaces, commas, or new lines. You can also paste a full Solscan link of the form solscan.io/tx/<signature> and we extract the signature.

Each signature gets a status check and a link to open it on Solscan.

Every ticket includes the wallet address, its SOL balance, a summary of SPL token accounts with a non-zero balance, and its most recent transaction signatures.

For any transaction you paste, we also show whether it is processed, confirmed, finalized, failed, or not found by the RPC endpoint.

Enrichment is a snapshot taken when the ticket is created. It does not update on its own.

Helixdesk never asks for your seed phrase, private key, or keystore file. Agents will not ask for them either. If anyone asks, do not share them.

We only use your public wallet address and a signed message. Both are already visible to anyone on-chain, apart from the signature itself.

In this build, tickets and replies are stored in your own browser using localStorage.

Demo mode creates a simulated wallet address and a mock signature in your browser. No extension is needed.

Enrichment in demo mode is generated from realistic sample values, and Solscan links for simulated data will not resolve to real accounts.

The ticket you create is a real ticket in local state, so agents can reply and change its status.

The default RPC endpoint is a shared public endpoint that can rate limit requests. When a lookup fails or times out, Helixdesk still creates your ticket.

In that case the enrichment panel shows a notice that cached values are being used. Those values are illustrative and are not live chain data.

To use your own provider, set NEXT_PUBLIC_SOLANA_RPC_URL in the environment.

Open means the ticket has been created and no agent has started on it. In progress means an agent is working on it. Resolved means the agent considers the issue handled.

You can keep replying on a resolved ticket. An agent can move it back to open or in progress.

Agents sign in with a local demo account (agent@helixdesk.dev / helixdesk) or with the Continue as agent button. The session is stored in the browser.

This sign-in is a local demo and is not a server-side authentication system.