nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygq...

npub1ak68qfcjj7k95c0jwleu69x72nr8adwv6g80pkwl9xlps6zmkqzqrxy8fx

hex

00000114b847a08e3b509576d39fad195c74d25d60ff1440dd87c9fd0c45a76a

nevent

nevent1qqsqqqqpzjuy0gyw8dgf2aknn7k3jhr56fwkplc5grwc0j0ap3z6w6sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswmdrsyuff0tz6v8e80u7dzn09f3n7khxdyrhsm80jn0scdpdmqpq572fws

Kind-1 (TextNote)

2026-08-27T14:35:53Z

nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprfmhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5hs592xhz I notice in 13.2.0 that the "receive to self custody" ecash feature will sometimes fail and then say token already spent and won't redeem ... but then the token value does appears in the ecash mint. Users may think they lost the token because of the red failure notifications. ✌️

Raw JSON

{
  "kind": 1,
  "id": "00000114b847a08e3b509576d39fad195c74d25d60ff1440dd87c9fd0c45a76a",
  "pubkey": "edb470271297ac5a61f277f3cd14de54c67eb5ccd20ef0d9df29be18685bb004",
  "created_at": 1787841353,
  "tags": [
    [
      "p",
      "34d2f5274f1958fcd2cb2463dabeaddf8a21f84ace4241da888023bf05cc8095",
      "wss://nostr.bitcoiner.social/"
    ],
    [
      "client",
      "Amethyst"
    ],
    [
      "nonce",
      "000A-O",
      "21"
    ]
  ],
  "content": "nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprfmhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5hs592xhz I notice in 13.2.0 that the \"receive to self custody\" ecash feature will sometimes fail and then say token already spent and won't redeem ... but then the token value does appears in the ecash mint. Users may think they lost the token because of the red failure notifications. ✌️",
  "sig": "9289a51e9e3017fbbe68c68fe9117a7a294a56c77cf4e605dc8d3a84afa39e79aa608b1b113867b6d0ce43f322ea84edffc7da99bbd5d428ed55c285fe8873ca"
}