FAQ

The Create wizard walks you through economy (stake and owner fee), name and review. The registration price is read live from the chain — it grows with every neuronet created and settles in about a day, so the review always shows the current figure. On managed hosting the platform treasury pays the registration and the initial stake; you work on a subscription. Tasks are added after creation, on the Tasks tab.

No. Idle time never deletes a neuronet or its tasks — it only changes the status and stops emission. Deletion happens on your command alone: dissolving the neuronet or removing a task. Tasks have no expiry at all.

Active — useful work is flowing. Warning — idle for over 50 400 blocks (≈7 days): everything still runs and rewards accrue. Frozen — idle for over 216 000 blocks (≈30 days): the gateway stops accepting requests and emission is withheld — it does not burn, it accrues and is paid once the neuronet is back. Freezing does not lift by itself: the way out is an owner-submitted settlement batch directly to the chain, or dissolving. Best not to let it get there.

Activity means executed requests to your tasks, and nothing else. The idle clock resets when the gateway settles those requests with the chain. Adding a task, staking or editing settings do not count: with no requests, the clock keeps running.

The record is removed from the network immediately, any earned-but-unpaid emission is paid to the owner as part of the same action, and the stake comes back through a queue: 50 400 blocks (≈7 days) after the command.

The declared compute cost of one request — a reserve for future useful-work weighting. Today rewards inside a task are split by credited requests and miner reputation; CU is a common multiplier for all miners of the task and does not change the shares.

Weight splits the MINER share of the neuronet’s emission between tasks — what is left after the owner fee and the stakers’ share: a task’s share equals its weight divided by the sum of all weights. The split bar on the Tasks tab shows the result.

Today P0 and P1 are active — transport encryption. P1 is not fully owner-blind yet: the gateway encrypts on your behalf and sees the plaintext itself, and sampled prompts may be revealed to verifier miners during checks. P2–P4 are locked in the selector and will open once the pipeline genuinely enforces them — promising earlier would be dishonest.

Yes. A key carries an allowlist — up to 32 entries, IPs or CIDR subnets; an empty list means no restriction. The list is edited without changing the secret, and key rotation inherits it. The gateway enforces the check and answers 403 ip_not_allowed for a foreign address; the client address is used only at the moment of the check and is never stored.

Yes: pick a task when issuing — the key will then work with that task only (another task answers 401). A key without a task works with every task of the neuronet. Each key also has a daily request budget; when it runs out the gateway answers 429 quota_exceeded and the budget returns at midnight UTC. Revoking a key reaches the gateway within a minute.

A ready-made frontend on top of a neuronet task: chat for LLMs, image or video generation. It opens by link; a visitor needs neither a wallet nor a key — requests go through the platform server with the Space’s own key and its own daily limit.

Public — listed in the Spaces catalog and open to search engines. Link-only — opens for anyone with the direct link, but is never listed and is closed to indexing (the link itself is unguessable). Private — owner preview only: the page is not served to visitors.

A Space visitor — no: the prompt is stored on the server and mixed into the request there, it never reaches the browser. But it is not a defence against an arbitrary API client: one that sends its own system message or a ready-made envelope replaces the owner’s prompt. For chat it is the assistant’s persona; for images and video, a permanent style prefix.

The per-neuronet limit is set by the platform: 3 by default, 10 on this testnet; a plan can set its own. At the limit, creation returns a space-limit error; deleting an unused Space frees a slot.

Two ways. Quick: create a Space for the task and send a request from its page — the same production route your visitors use. Programmatic: issue an API key on the API keys tab and call the endpoint from the Endpoint tab with that key.

A storefront badge: platform administration assigns it, and together with the weight it defines the order in the Featured sort. It does not affect execution, parameters or verification of the model.

A weights packaging format: the same artifact runs on Metal, CUDA and CPU. In the filter it is an additional value on top of precision, not a replacement — a Q4_K_M entry is found under both Int4 and GGUF.

The catalog and the task wizard have filters: hardware class (consumer or datacenter, by required VRAM), model family, parameter size and quantization. Each model card shows the minimum VRAM.