Help.

You are on Operator 0.6.18 or older. The bundled node in that build cannot decode blocks on the current testnet format. Reset won't help.

Download 0.6.19 or newer from testnet.asentum.com/downloads and install over the top. The auto-updater should also prompt on next launch.

The mac build is currently unsigned — Gatekeeper blocks it on first launch. Two ways past it:

Recommended: Right-click Asentum Operator.app in /Applications, choose Open, then click Open in the confirmation dialog. Only needed the first time.

Terminal fallback: xattr -cr "/Applications/Asentum Operator.app", then double-click normally.

A signed + notarized build is in the pipeline.

The .exe is unsigned. Click More info, then Run anyway. Same as any unsigned Windows installer.

Known issue in older builds — Start Over wipes the local wallet+key but the bond stays on-chain, which orphans the validator. Import your key backup (Settings → Import wallet key) if you have it. If not, contact us with your wallet address; we can look up the tx history.

Check three things:

• Your app is pointed at the current testnet — chain id 1337, RPC https://testnet.asentum.com.
• You haven't typed the address in mixed case. Wallet lookups are case-insensitive but explorers sometimes normalise differently.
• Testnet was last reset on 2026-07-02. Balances from before that date do not carry forward. If you received a distribution, it was re-sent post-reset.

Add a custom network:

• Network name: Asentum Testnet
• RPC URL: https://testnet.asentum.com
• Chain ID: 1337
• Currency symbol: ASE
• Block explorer: https://explorer.asentum.com

The bond is on-chain but the validator key on your machine was the only way to sign for it. Without a backup, that specific validator slot is unrecoverable. This is one of the things we're working to consolidate — future builds bind wallet + validator identity to a single key.

On any Ubuntu/Debian VPS with a public IP and Node 22 available:

curl -fsSL https://testnet.asentum.com/install/validator | bash

The installer sets up systemd, generates a validator key, fetches the chain snapshot, funds a small bond via the faucet, and starts producing. Total time about 5 minutes.

Two possibilities:

• Fixed 2026-07-08: before that date, external validators' signatures were being buffered but not included in the on-chain LastCommit cert, so reward math skipped them. Fully resolved now — no user-side action needed.
• Rewards are stake-weighted. At a 51,000 ASE bond you earn roughly 0.002 ASE per block signed. That's ~130 ASE per day of continuous participation, not thousands. Higher stake earns proportionally more.

Non-interactive runs (Docker, remote SSH pipe) block on the seed-backup prompt. Latest installer times out after 30s automatically. If you're still on the old version, either paste into your own SSH session (interactive TTY) or re-fetch the installer: curl -fsSL https://testnet.asentum.com/install/validator.

Yes. NAT'd validators use pull-mode: the node polls the baked relays for proposals, signs locally, POSTs the precommit back. Pull-mode is on by default in the installer. The rewards path treats pull-mode and direct-mode signatures identically.

One drip per IP per hour with a 500 ASE default cap. Bonded validators can request up to 51,000 ASE per drip (needed for the bond+gas floor). Rate limits reset on a rolling window per IP.

Nonce desync on the faucet wallet, usually right after a chain reset or a mass validator restart. Report the timestamp and your address; we bounce the faucet primary and the drip retries within a minute. Fixed in most cases automatically by the retry-on-drip logic in the installer.

Use the Vault Explorer in the IDE at ide.asentum.com/vault — pick a Worker (asentum-default is the free hosted one), paste the secret, set the ACL to the contract that's allowed to trigger decryption. That's it.

The plaintext is encrypted with X25519 + ML-KEM-768 hybrid to the Worker's public key. Ciphertext lives on-chain. Only the Worker with the matching private key can decrypt, and only on authorized on-chain requests.

The whitelist currently covers resend, openai, slack, telegram, github, and httpbin. Free during testnet. To reach a different domain, deploy your own Worker daemon and update the policy hash — instructions in the Workers docs.

Every reset ships a specific architectural change that requires fresh genesis — usually a change to block format, a new genesis-baked contract, or a chain-id migration. We announce ~24h ahead in Telegram. Last reset: 2026-07-02 (LastCommit cert + genesis-baked Vault/WorkerRegistry).

Live status at explorer.asentum.com — if the head isn't advancing there, it isn't for you either. Our on-call sees the same page. If the explorer looks healthy but your node doesn't, it's a client-side problem — open a ticket with your node logs.