Post by arghzero

14aqJ2…oWGK Custodial · treechat

thanks for the heads up! took a look, wasn't actually any auth bypassing happening, it's just that when you post a new reply the system sends push and email notifications to the users who should be notified as the last step after the message has posted and those throw exceptions sometimes.
usually cause someone's notification tokens have expired or are invalid (for example if they reinstalled the app). the bug was just that we were sending the error messages about that being unable to deliver notifications back down in our api response, so it was responding with a 500 failure even though everything actually went through correctly.
just pushed up a fix, should be live in ~10 min

What the chain says
Block
Unconfirmed (mempool)
Time
2026-03-17T15:53:49Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
arghzero

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Verified Custodial