Publish a v4call-server post to the Hive blockchain so other v4call servers discover you.
The post is pure directory metadata — it points at your /.well-known/v4call-server.json which is where the cryptographic proof lives.
Before posting: make sure your /.well-known/v4call-server.json is already signed and live at the domain below. Discovering servers will fetch that file to verify you — if it isn't there, they'll ignore the announcement.
↺ open signer page
PASTE SIGNED v4call-server.json (recommended)
If you've just signed your v4call-server.json in
server-sign.html,
paste it here — the form auto-populates AND the embedded Nostr attestation
flows through to the Hive post body (as a base64 line). One signed event,
two surfaces, no double-signing.
IDENTITY
The Hive account that will author this post. Same as the one in your v4call-server.json (SERVER_HIVE_ACCOUNT).
The public hostname. Must match your v4call-server.json's domain field.
SERVER CONFIG
Auto-computed from DOMAIN. This is where discoverers fetch your signed proof.
SOFTWARE
Your implementation's name. Forks welcome — e.g. hivebook-calls. Informational.
Federation protocol you speak. Should match FEDERATION_VERSION in server.js.
NOSTR — optional, for v0.18.5+ federation discovery layer
Cross-reference your server's Nostr identity here so other v4call servers can find you over Nostr too. Skip this card entirely if you don't have a Nostr keypair for your server yet — the announce post is fully valid without it.
Need a keypair? Use nostr-gen.html (browser-only, keys never leave your machine).
The bech32 form. Hex auto-fills below if you paste a valid npub.
Same key, different encoding. Many relays' config files (e.g. nostr-rs-relay's pubkey_whitelist) need the hex form.
RELAYS — up to 5 (any blank rows are skipped)
POST OPTIONS
First tag becomes the post category. v4call-server must stay first — that's what discovery searches for.
PUBLISH
PREFERRED · KEYCHAIN (posting key stays in your browser)
Detecting Keychain…
FALLBACK · POSTING KEY PASTE (signs + broadcasts via dhive)
Use this if Keychain isn't installed or is misbehaving. The page constructs
the post operation locally, signs it with your pasted posting key, and
broadcasts it directly to a Hive node. The key never leaves your browser.
In memory only until this tab closes. Wiped after a successful broadcast.
FALLBACK · MANUAL POST (copy + paste into peakd / hive.blog)
Last-resort fallback: copy or download the body below and paste it into
peakd.com / hive.blog with the title v4call-server and the
tags shown above.
POST PREVIEWunsigned
title: v4call-serverpermlink: —
Note: posting to Hive costs Resource Credits. Make sure @your-account has some Hive Power staked (or delegated).
A new post consumes roughly the same RC as a comment — usually fine if the account has 10+ HP.