0
Make Alby Hub (with LDK) work with Coldcard Q signing to enable Alby Hub users to use its wallet for Ocean's Bolt12-payouts
H
hodlshopper
Aug 26, 2025

Regarding LDKs long Bolt12 offering strings

Could we make it optional to have blinded paths when using LDK? For example, make the user decide if we would like to have a shorter string, without blinded paths

The problem I'm currently facing is that when I try to sign the message with my Coldcard Q which has a limit on how long the mesage can be, 240 characters. This tells me that the BOLT12-string Alby Hub produces is much longer (more than 240 characters) than the BOLT12-string that Core Lightning produces which makes me not able to use Alby Hub.

Is it possible to get Alby Hub to produce a shorter string so users with a Coldcard Q can sign the message, thus be able to receive Ocean payouts.

Core Lightning Bolt12-string:
"lno1pg7y7s69g98zq5rp09hh2arnypnx7u3qvf3nzutdds682enyvekkcer5dccrswfnx4nhx6rhwp6xu6rhdeunxetjddcrsvnyvdjpvggzc3m2qq87346z6uu4yw3kxk6qt6dvg2mm06vysage7tuh3fe3uers"

Alby Hub Bolt12-string:
"lno1pg7y7s69g98zq5rp09hh2arnypnx7u3qvf3nzutdds682enyvekkcer5dccrswfnx4nhx6rhwp6xu6rhdeunxetjddcrsvnyvdjpp6qr3209v5fwexx69dtcjasl0tu09q96lx9qj2prvrxklufcrd0g3xls9nngzj0vjn64gdmn0qe8h8f7yn3ga9u89mrhw4ym73tjm6zyxk2jqgp95n04qq28xnea6mxem8hs60ef7k0xqls7e3rgr6udsphm3yfu9zsqxw0ryg5wr3nkval9cqsm9l363y86vu7ksfafmj0lgl0lmwjppd0rzgt0q5u2jm7hvzr7w3yl3z629ycfzc4q9t8l6txsz5glk7kv3dyqk846vrpc68ktmkmf50h4884jpgm0f8p3qqk8z20pgtns0r3c63xwn7ngx3dn04v3t5q06thk70mgpfhg6c38qe634j0qr2rh4d0cdz5dl5tzzqeuagfktk504rg4a23ltqw96cfeluuxw48s86zwpxmcplx6dh2kqv"

The BOLT12 offer string is longer because it includes paths . These are blinded paths used for recipient privacy. LDK (the integrated node in Alby Hub) uses these by default.

Comments
No-one has commented on this post yet.