Hi nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5...

Cheyenne Isa ₿

npub1ssdszl2flqs33qdz8t9aqq4lkp7qm8qdwgxy4xwyye55tzlsacusgvunvc

hex

346fc0f3861ec2235d3a14063e7f6c832acf52b4168392dd947a0ea7c5786242

nevent

nevent1qqsrgm7q7wrpas3rt5apgp370akgx2k0226pdqujmk285r48c4uxyssprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsggxcp04ylsggcsx3r4j7sq2lmqlqdnsxhyrz2n8zzv62930cwuwgtc8gn2

Kind-1 (TextNote)

2026-03-09T12:48:15Z

Hi nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 #safebox,

I'm writing to report an issue that I deliberately tested to assess the wallet's reliability. For over a week now, I've been seeing the 502 Bad Gateway error (nginx/1.24.0) on both Wi-Fi and 4G/5G. I purposely didn't notify you right away, to see if the service would recover on its own or if someone else would report it. Instead, it's still down.

This makes me think that:

· The server I'm on (or where the wallet is hosted) lacks auto-restart mechanisms or monitoring. · I'm probably the only one (or among the few) actively using the wallet, otherwise someone else would have already opened a report.

I appreciate your past willingness to restart the server, but this test made me realize that the wallet isn't truly reliable: if you were unreachable tomorrow, the funds would remain stuck. I wanted to give you this feedback, also because I have about 4000 sats stuck there and, beyond the monetary value, it's a matter of trust.

Do you have any plans to make the system more resilient (e.g., auto-restart, monitoring), or is this a project you only maintain "on call"?

原始 JSON

{
  "kind": 1,
  "id": "346fc0f3861ec2235d3a14063e7f6c832acf52b4168392dd947a0ea7c5786242",
  "pubkey": "841b017d49f8211881a23acbd002bfb07c0d9c0d720c4a99c42669458bf0ee39",
  "created_at": 1773060495,
  "tags": [
    [
      "t",
      "safebox"
    ],
    [
      "p",
      "06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c"
    ]
  ],
  "content": "Hi nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 #safebox,\n\nI'm writing to report an issue that I deliberately tested to assess the wallet's reliability. For over a week now, I've been seeing the 502 Bad Gateway error (nginx/1.24.0) on both Wi-Fi and 4G/5G. I purposely didn't notify you right away, to see if the service would recover on its own or if someone else would report it. Instead, it's still down.\n\nThis makes me think that:\n\n· The server I'm on (or where the wallet is hosted) lacks auto-restart mechanisms or monitoring.\n· I'm probably the only one (or among the few) actively using the wallet, otherwise someone else would have already opened a report.\n\nI appreciate your past willingness to restart the server, but this test made me realize that the wallet isn't truly reliable: if you were unreachable tomorrow, the funds would remain stuck. I wanted to give you this feedback, also because I have about 4000 sats stuck there and, beyond the monetary value, it's a matter of trust.\n\nDo you have any plans to make the system more resilient (e.g., auto-restart, monitoring), or is this a project you only maintain \"on call\"?",
  "sig": "cb223d19ae0d0221c505ea9401dba5df142bd486f5237c966c2b32634fe7bf49ad057aed67278e06f3f355e5d67348c97c3be301c245d199aaa19ad1948e4cb5"
}