Post History

How to link an existing Odysee web wallet to the local `lbrynet` daemon for automated video publishing?

I'm building an automated content pipeline that publishes daily video briefings from a headless Arch Linux server. The pipeline already works for other platforms (Bluesky, Mastodon, PieFed, Telegram) and I want to add Odysee as a primary video host.

I have an Odysee account with an existing channel that has ~0.25 LBC in the web wallet. What I need is to publish videos programmatically from the command line, using that same account and channel — no browser uploads, no GUI.

**What I've tried:**

1. Installed `lbrynet-bin` (v0.113.0) from the AUR on the server
2. Set up a systemd user service so the daemon starts on boot and stays running
3. Started the daemon — `lbrynet start` works, daemon runs on `localhost:5279`

**Current state of the local daemon:**

```
lbrynet wallet balance
→ 0.0 LBC

lbrynet channel list
→ empty (no channels, no certificates)
```

The problem is that the daemon creates a **brand-new wallet** on first launch, not connected to my Odysee web account. The ~0.25 LBC and the channel certificate live in the Odysee web wallet, not in the local daemon's data directory.

**Specific questions:**

1. **Wallet linking** — Is there a way to import my existing Odysee web wallet into the local `lbrynet` daemon so I get the LBC balance and channel certificates locally? I've seen references to BIP-39 seed phrases in the Odysee settings. Would `lbrynet account add --seed` work for this, or would that create a *second* wallet alongside the empty local one?

2. **Publish command** — Assuming I solve the wallet issue, is this the right way to publish a video? I'm guessing:
   ```
   lbrynet publish \
     --name daily-briefing-2026-07-06 \
     --file_path /path/to/video.mp4 \
     --title "Daily Briefing | July 6, 2026" \
     --description "Today's analysis" \
     --channel_name @MyChannel \
     --bid 0.0001 \
     --tags "news" "analysis" \
     --languages en \
     --blocking
   ```
   Are there any gotchas with `--name` uniqueness? If the same `--name` is reused, does it update the existing claim or fail?

3. **Daemon management for cron** — Should `lbrynet` run continuously as a background daemon, or is it safe to `start`/`stop` it for each publish run (which would waste time on blockchain header sync)? What's a reasonable systemd user service for this use case?

4. **LBC economics** — At 0.01 LBC minimum bid per upload, my ~0.25 LBC covers about 25 uploads. Is the 0.01 LBC a *deposit* (returned if the claim is abandoned) or a *fee* (consumed)? And is there any per-byte bandwidth cost on the LBRY network for video hosting?

**Environment:**
- Arch Linux (CachyOS), headless server
- `lbrynet` v0.113.0 from AUR (`lbrynet-bin`)
- Publishing is triggered by a cron job running a Python pipeline
- Videos are ~12-14 minutes, ~12-15 MB MP4s (H.264, 1280x720, AAC audio)

I've looked through the Odysee publishing docs and the `lbrynet --help` output but the gap between "upload from browser" and "automated CLI" is not well documented. Anyone who's bridged this gap, I'd appreciate the cleanest approach you've found.