The 1M-token headroom (ported from t4t homelab gateway) makes maxPayment
so large that JobEscrow's concurrency cap fires on a fresh provider
with ~70 xBZZ stake — postJob reverts with InsufficientStakeForJob.
50k tokens still covers chat-template overhead with room to spare, and
brings per-job exposure down ~20x so ~20 concurrent jobs fit comfortably.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two bugs that together blackholed every reverse-PSS message from the
provider when the api ran more than one replica:
1) `pssKeys = generatePssKeypair()` ran per-container, so each replica
had a different ECIES identity. Provider encrypts its reply to ONE
of those keys, only that replica can decrypt — so two replicas =
~50% of chats hang forever.
2) `resolveSelfOverlay` swallowed errors and returned 0x00…00 when
Bee wasn't ready yet at boot. That zeroed overlay landed in the
gateway context AND in the job_notify envelope sent to the provider
— provider then sent PSS replies into the void.
Fix: load PSS key from PSS_KEY_PATH (shared volume across replicas);
retry getNodeAddresses up to 5 minutes and throw if still zero.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previous formula computed maxPayment from the estimated input length
plus offering.maxContextTokens — but the on-chain offering for some
provider models has maxContextTokens=0, so output cost was 0 and the
posted maxPayment only covered the (under-estimated) input side. The
provider's claimJob then reverted with PaymentTooHigh, leaving the
gateway hung waiting for a PSS job_deliver that never came.
Match the t4t/container homelab gateway: assume both prompt and
completion can be (max_tokens + 1M-token headroom), budget at the full
split rate, let the JobEscrow contract refund the unused portion. The
provider's actual claim is always smaller, so PaymentTooHigh can't fire.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
swagger({ path: '/' }) renders the UI at root but doesn't register the
/json spec route, so the embedded UI loads then 404s on its own spec.
Keep the plugin defaults and bounce / → /swagger instead.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Was only building + pushing; swarm kept running the previous image
until someone ran service update --force. Mirror the frontend workflow:
ssh in and `docker stack deploy --resolve-image always` so every main
push rolls out.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Was at /swagger by default. Apex 404 was confusing — there's no other
content on the api host, so make the API docs the default landing.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
