Cashu question: What’s the difference between the “legacy” format (cashuA…) and the “new” version (cashuB…) in nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch? I noticed it when trying to claim tokens with nostr:npub1cashuq3y9av98ljm2y75z8cek39d8ux6jk3g6vafkl5j0uj4m5ks378fhq, which only accepts the legacy one.
#AskNostr #DeezNuts 🌰🐿️
The legacy format v3 encodes the JSON with base64_urlsafe with the prefix cashuA.
The v4 format uses smaller JSON keys and adds CBOR (converts the JSON to binary) then encodes as base64_urlsafe with the prefix cashuB.
This results in smaller sized tokens.
The prefix was my suggestion to make the difference both human and machine readable, iirc.
For more info:
nostr:nprofile1qqsvwct7qgjz7kznled4z02pruvmgjkn7rdftg5dxw5m06f87f2a6tgpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdufyudzh can upgrade cashu-ts and it will accept the new cashuB format as well :)
