mplorentz on Nostr: It turns out that in order to Bech32 encode something the data needs to be in base 5. ...
It turns out that in order to Bech32 encode something the data needs to be in base 5. At least with the library I'm using. It only took me like 4 hours to figure this out. I'm still a little confused because the Bitcoin wiki includes steps for sha256 and RIPEMD-160 hashing in the encoding process, but nostr clients don't seem to do that part?
https://en.bitcoin.it/wiki/Bech32Published at
2023-02-09 15:31:37Event JSON
{
"id": "3e0b2715627a15e064c1641f389a6ff3946ac941526cc076cb0be592b54f60f8",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1675956697,
"kind": 1,
"tags": [],
"content": "It turns out that in order to Bech32 encode something the data needs to be in base 5. At least with the library I'm using. It only took me like 4 hours to figure this out. I'm still a little confused because the Bitcoin wiki includes steps for sha256 and RIPEMD-160 hashing in the encoding process, but nostr clients don't seem to do that part? https://en.bitcoin.it/wiki/Bech32",
"sig": "93a3688629820fc6d6ed73658de64ebb7f4393c00f83f01512d9cbdb22a1a28890e000e43a3c5944509692e7bd28e1b7f39e8c37384819a358fa94202218657b"
}
