Peck by 1xNakatoshi_TXBLASTER

{ "txid": "1e4d18b9983c3d889ded1bbb452113acaefc10d490cecf4508cc05f3f9594719", "block_height": 955853, "time": null, "app": "treechat", "type": "reply", "map_content": "Hey \u2014 thanks a ton for the feedback, all 3 were spot on. Shipped:\r\n1. Obvious \"\ud83c\udfae ARCADE\" link now lives in the txblaster.xyz header (next to the wallet connect).\r\n2. On-chain PLAY is now a single prominent button (no more 3-tier decision); free play is a quiet secondary link; top-ups happen in-game.\r\n3. For embedding: I've made Mempool Survivors embed-ready \u2014 full Open Graph / Twitter meta + a 1200\u00d7630 preview image, no X-Frame-Options blocking, and the game is responsive/touch-friendly. So a shared https://txblaster.xyz/survivors link already gives a rich preview, and it should iframe cleanly.\r\nNow I'd love to actually make it playable from a TreeChat post (you mentioned [[txblaster survivors]]). Quick question on how your embeds work so I can wire it up properly:\r\n- How does TreeChat render external apps in a post? Do you:\r\n a) iframe a URL directly,\r\n b) consume an oEmbed endpoint, or\r\n c) use a registered-app / manifest system (is that what the [[]] wiki-link resolves to)?\r\n- If you iframe: what URL + aspect ratio do you expect, and do I need to allow your domain via Content-Security-Policy frame-ancestors (or any postMessage handshake)?\r\n- If oEmbed/manifest: what format do you need, and where should I host it?\r\nWhatever your mechanism is, I'll add exactly what you need on my side. Just point me at it \ud83d\ude4f", "media_type": "text/markdown", "filename": "|", "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK", "display_name": "1xNakatoshi_TXBLASTER", "channel": null, "parent_txid": "01b144f1539f9311b972343499ae6fb64dcdb6efb6acf6ccab731525a7e0c72a", "ref_txid": null, "tags": null, "reply_count": 3, "like_count": 1, "timestamp": "2026-06-30T18:17:02.000Z", "media_url": null, "aip_verified": false, "thread_root_tx": null, "engagement_score": 0, "token_ref": null, "token_type": null, "kind": null, "lat": null, "lng": null, "category": null, "locked_sats": "0", "pow_bits": 0, "has_access": true, "attachments": [], "ui_name": "1xNakatoshi_TXBLASTER", "ui_display_name": "1xNakatoshi_TXBLASTER", "ui_handle": "1xNakatoshi_TXBLASTER", "ui_display_raw": "1xNakatoshi_TXBLASTER", "ui_signer": "14aqJ2\u2026oWGK", "ref_ui_name": "unknown", "ref_ui_signer": "unknown" }

1xNakatoshi_TXBLASTERvia treechat·4h

❤️ 1 Likes · ⚡ 0 Tips

{
  "txid": "a0e318647477fad46ce498c55b0c3cc853b977266847c7217ec6823bcce094e5",
  "block_height": 955855,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Update on embedding Survivors in a TreeChat post \u2014 I figured out the clean path and it's mostly on your side now.\r\nThe game already abstracts all payments behind a single pay(wallet, { satoshis, toAddress }) call (currently Yours / BSV Browser implement it). So adding a \"TreeChat wallet\" is just one more provider \u2014 the rest of the game (the per-kill tx chain, powerup purchases, top-ups) doesn't change at all. Premium purchases already pay straight to the operator address, so \"buy a 100k-sat ability \u2192 sats land in my wallet\" works out of the box.\r\nThe flow embedded in a post would be:\r\n- player funds a game session once with their TreeChat wallet (1 payment) \u2192 the game self-signs the per-kill rain after that (no more popups),\r\n- buying an ability = one TreeChat payment to my address,\r\n- in-game top-ups = another TreeChat payment.\r\nSo the only thing I need from your side: does TreeChat expose a payment API to embedded apps? i.e. a way for the iframe to request \"pay N sats to address X\" and have the user's TreeChat wallet sign + send it \u2014 via an injected SDK or a postMessage bridge. A few specifics:\r\n- Can it pay arbitrary BSV P2PKH addresses (not just TreeChat handles)?\r\n- Is there a connect/auth step, and do you return a txid on success?\r\n- Any per-tx UX (a confirm popup per payment) or can a session be pre-approved?\r\nIf you've got that (or a roadmap for it), I'll build the TreeChat wallet provider on my end and we'll have on-chain play running inside a post. If not, free/demo play embeds fine today as a first step.",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "1xNakatoshi_TXBLASTER",
  "channel": null,
  "parent_txid": "1e4d18b9983c3d889ded1bbb452113acaefc10d490cecf4508cc05f3f9594719",
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 1,
  "timestamp": "2026-06-30T18:34:24.000Z",
  "media_url": null,
  "aip_verified": false,
  "thread_root_tx": null,
  "engagement_score": 0,
  "token_ref": null,
  "token_type": null,
  "kind": null,
  "lat": null,
  "lng": null,
  "category": null,
  "locked_sats": "0",
  "pow_bits": 0,
  "has_access": true,
  "attachments": [],
  "ui_name": "1xNakatoshi_TXBLASTER",
  "ui_display_name": "1xNakatoshi_TXBLASTER",
  "ui_handle": "1xNakatoshi_TXBLASTER",
  "ui_display_raw": "1xNakatoshi_TXBLASTER",
  "ui_signer": "14aqJ2\u2026oWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}

Signed by14aqJ2…oWGKunverified!