gyblos docs
Sellers

Seller beta guide

Install the Gyblos seller node, check that it serves and register it with your invitation.

You were invited to the Gyblos seller beta. This guide takes you from the files in your invitation to a seller listed in discovery. It takes about 15 minutes, most of it downloading.

Beta on devnet

The beta runs on Solana devnet. Your node gives a small model away for free, within daily limits. No real money moves.

What you need

  • Your invitation, with three things:
    • install.sh, the install script;
    • a relay token, which lets your node reach Gyblos relays;
    • an invite code that starts with gyb_, used once to register.
  • A machine that stays on. Linux (x86-64 or ARM64) or macOS. A small VPS works.
  • Docker with Compose v2.17 or later. On macOS, Docker Desktop. On Linux, Docker Engine with the compose plugin, and an account in the docker group.
  • At least 4 GB of memory. The seller needs 1.5 GB free to start, and the model runs next to it.
  • A few GB of disk for the images and the model.
  • An outbound internet connection. No port is opened: your node connects out to the relays.

Keep the relay token and the invite code private. Do not paste them in chats, issues or screenshots.

Install

Run the script

In the folder where you saved install.sh:

sh install.sh

It asks for the relay token. The token is not shown as you type or paste it.

Wait for it to finish

The script works in ~/gyblos-seller:

  1. writes compose.yaml, gyblos.toml (your offer) and seller.env (your relay token, readable only by you);
  2. downloads the seller image, Ollama and the qwen3:0.6b model;
  3. creates your seller keys;
  4. runs gyblos doctor, which checks everything before starting;
  5. starts the seller.

When it ends with The seller is running, you are done. Doctor also prints your seller identity:

Seller identity (public; `gyblos seller register` enrolls it in discovery):
  nodeId  4d789a89…
  owner   7is91kWV…

Both values are public. Save them: Gyblos may ask for them.

If it stops with an error

Read the line marked FAIL, or the one that starts with gyblos install:: it says what is wrong and what to do. Fix it and run sh install.sh again. Rerunning is safe: it keeps your files and keys and continues where it stopped.

Check that it serves

Every command below runs from the install folder:

cd ~/gyblos-seller
docker compose exec seller gyblos seller status

Look at the Result: line:

ResultMeaning
RUNNINGThe seller is up and serving.
STARTINGStill starting. Wait a minute and check again.
FAILINGThe last start failed. The next line names the step, the error code and what to do.
STOPPEDThe container is up but the seller is not running. Run docker compose up -d --force-recreate seller.
NOT_CONFIRMEDStatus could not confirm the service. Check docker compose ps.

If the command itself says the service is not running or is restarting, the seller stopped after a failure: read docker compose logs seller, fix the cause and start it with docker compose up -d.

Register with your invite

Registration lets your seller appear in Gyblos discovery, where buyers find it. Use your invite code once:

cd ~/gyblos-seller
docker compose exec seller gyblos seller register

Paste the code when asked. It is shown on screen as you paste it, so do this where no one can see your screen. Registered: this seller may now publish. means it worked. If you run it again with the same code, it answers Already registered.

The code is tied to your seller's keys. If you delete them (docker compose down -v), the same code no longer works.

On-chain step

Discovery also checks that your node is recorded on Solana devnet. We are finishing that step. If register answers DISCOVERY_IDENTITY_NOT_REGISTERED, your node is not recorded yet: send the nodeId and owner from the install to the Gyblos team and keep your code. It is not used up, but it can still expire; if it does, ask for a new one.

Publish your offer

New installs start unlisted. Once registered, open ~/gyblos-seller/gyblos.toml and change:

[discovery]
publish = true

Apply the change:

cd ~/gyblos-seller
docker compose up -d --force-recreate seller

After a minute, check that discovery lists you:

docker compose exec seller gyblos seller status --online

It should say listed in the index.

What your node offers

The default offer in gyblos.toml gives qwen3:0.6b away for free:

  • up to 200,000 tokens per day in total;
  • up to 5,000 tokens per day for each buyer.

The counts reset when the seller restarts. You can lower these limits in the [[offers]] section. Apply edits with docker compose up -d --force-recreate seller.

Prompts are processed on your machine, so your node can read them. Do not store or share what buyers send. Discovery publishes your nodeId, your owner, your model and a zero price.

Everyday commands

From ~/gyblos-seller:

WhatCommand
Statusdocker compose exec seller gyblos seller status
Follow the logdocker compose logs -f seller
Stopdocker compose stop seller
Startdocker compose up -d
Apply an edited gyblos.tomldocker compose up -d --force-recreate seller
Update to the latest betadocker compose pull && docker compose up -d

Stopping withdraws your offer from discovery within two minutes.

Your keys live in a Docker volume

docker compose down -v deletes your seller keys, and with them your identity. Use docker compose down (without -v) to remove the containers and keep the keys.

Troubleshooting

You seeWhat to do
Docker is not installed or Docker Compose v2 is missingInstall Docker with the compose plugin (v2.17 or later) and run the script again.
Docker is not runningStart Docker Desktop, or the Docker service on Linux, and run the script again.
Docker Compose … is too oldUpdate Docker or the compose plugin to v2.17 or later.
The relay token is empty… or must have 32 to 512 charactersCopy the relay token again from your invitation, with nothing before or after it.
FAILING with SELLER_RELAY_OFFLINENo relay answered. Check that the machine can reach the internet. If the token may be wrong, run rm ~/gyblos-seller/seller.env, then sh install.sh again from the folder where you saved it, to enter the token; never print seller.env on a shared screen.
Ollama did not startRun cd ~/gyblos-seller && docker compose logs ollama. It is often a lack of memory or disk.
The seller fails after Ollama restarted by itselfRun docker compose restart seller.
DISCOVERY_INVITE_INVALIDThe code is wrong, already used or expired. Ask Gyblos for a new one.
DISCOVERY_RATE_LIMITED or DISCOVERY_UNAVAILABLEDiscovery is busy. Try again in a few minutes.

If you are stuck, send the Gyblos team the output of docker compose exec seller gyblos seller status. It never contains your relay token or your keys.

Gyblos Docs

Guides for running a Gyblos node.

On this page

What you needInstallRun the scriptWait for it to finishIf it stops with an errorCheck that it servesRegister with your invitePublish your offerWhat your node offersEveryday commandsTroubleshooting