openoms
openoms
Blink is accessible now on * Obtainium (https://obtainium.imranr.dev/) -add the release with: https://github.com/GaloyMoney/blink-mobile and use prereleases if want to test * Zap Store (https://zap.store/download/)
> Why are there only prereleases here on github? That is not the case, all releases are here: https://github.com/GaloyMoney/blink-mobile/releases
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
> have you tried a restart, we fixed a big in this area see: [#10378](https://github.com/lightningnetwork/lnd/pull/10378) yes, the node has been restarted multiple times with no change in this issue >...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
Update: `bos peers` started working after running the commands above, but the `lncli getchaninfo` results still look the same. `bos fees` does error still: ``` err: - 503 - GetFeeReportError...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
Fixed only by closing two channels. Looking at the `getchaninfo` output for the remaining errored chanels `node1_policy` or `node2_policy` is still null: Channel | Own Node Position | Own Policy...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
Could `chantools dropchannelgraph` be used here at all (given the postgres database)? Adding some analyses made with Claude Opus 4.5 in case it is useful: ## Root Cause Analysis There...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
@ellemouton thank you for looking into this: Got the logs, there are some SQL errors which could be possible related: ``` 2025-11-28 21:21:10.514 [INF] GRDB: Pruned unconnected node 034efff7008339c9080e71a6bda4bf81799b7274a8b1545a39fc9c80141fb399c8 from...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
> can you share you complete log via DM (on slack for example) ? shared in Slack DM @ziggie1984 One more thing to note maybe that the postgres database instance...
[bug]: [ERR] NANN: Unable to retrieve chan status for Channel -s since update to v0.20.0 on postgres
Can confirm that funds are not at risk. I have cooperatively closed all the problematic channels with missing chanpolicy on either side. Now the fee setting functions are back.
The CLN words are BIP39 compatible (unlike LND which has the aezeed format), but CLN uses a special derivation path which is not supported by other wallets out of the...