have a different error message for an empty bond #89

New Issue

zramsay · 2026-01-14T19:29:08Z

zramsay commented

2026-01-14 19:29:08 +00:00

e.g., if sending tokens but with insufficient funds, the error (as expected) shows "Insufficient Funds". the exact same error presents itself if the account has plenty of token, but the bond has run out. My service provider stopped working for this reason and it wasn't immediately clear why until i remember than an amount is associated with the bond, and refilled it with the laconic bond refill command

e.g., if sending tokens but with insufficient funds, the error (as expected) shows "Insufficient Funds". the exact same error presents itself if the account has plenty of token, but the bond has run out. My service provider stopped working for this reason and it wasn't immediately clear why until i remember than an amount is associated with the bond, and refilled it with the `laconic bond refill` command

prathamesh commented

2026-01-15 03:47:03 +00:00

@zramsay
In what process did you see this "Insufficient Funds" error? Was it in the webapp-deployer logs?

@zramsay In what process did you see this "Insufficient Funds" error? Was it in the webapp-deployer logs?

zramsay commented

2026-01-15 11:49:10 +00:00

yes exactly

zramsay commented

2026-01-15 11:51:24 +00:00

this account https://git.vdb.to/cerc-io/testnet-ops/src/branch/main/service-provider-setup/templates/laconic.yml.j2#L5 has tokens and I filled a bond when originally setting the name authority. i guess every registry record publish drains some of the bond (would also be good to output that info after a tx, or something

this account https://git.vdb.to/cerc-io/testnet-ops/src/branch/main/service-provider-setup/templates/laconic.yml.j2#L5 has tokens and I filled a bond when originally setting the name authority. i guess every `registry record publish` drains some of the bond (would also be good to output that info after a tx, or something

zramsay commented

2026-01-15 11:54:51 +00:00

correction, the error was not in the deployer logs but rather in the logs for an individual deployment (viewable either via deploy.laconic.com or the webapp-ui, eg. https://webapp-deployer-ui.pwa.laconic.audubon.app

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconic-registry-cli#89