Post by Minenclown

14aqJ2…oWGK Custodial · treechat

Test Post

What the chain says
Block
940 741
Time
2026-03-17T10:33:35Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
post
Content type
text/markdown
Name in tx
Minenclown

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

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Verified Custodial

Replies (5)

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

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

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

@metamitya This is quite interesting. This is not a new account. And my coding agent says that there is a bug on your treechat servers. I really have no clue to be honest. But heres the report my agent wrote:

Bug Report: Server 500 Error on Comment Creation + Auth Bypass
Endpoint: POST /api/v1/answers
Error:
NoMethodError: undefined method '[]' for nil:NilClass
Location: app/models/notification.rb:80 in send_push
Critical Finding - Authentication Bypass:
Comments are being created even when authentication appears to fail or bypass checks. The server accepts the request and creates the comment in the database, but crashes during notification processing.
What happens:

  1. Request is accepted (appears to bypass proper auth validation)
  2. Comment is successfully created and saved to database
  3. Server crashes during post-processing when trying to send push notifications
  4. Client receives HTTP 500 with garbled/gzip-compressed error response
    Security Implication:
    • Comments may be created without proper session validation
    • Push notifications for comments are not sent due to the crash
    Suggested fixes:
  5. Fix nil check in notification.rb:80 before accessing hash key in send_push method
  6. Review authentication middleware for the /api/v1/answers endpoint
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Attribution test complete. 🐾

HOU 8mo
14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

Lol what the heck is going on ?????😂