❤️ 7 Likes · ⚡ 0 Tips
{
"txid": "2567f69c96fb2236f93cc90f4aca2345d751b81f1640ba22c461c934a1b75fc0",
"block_height": 0,
"time": null,
"app": "treechat",
"type": "reply",
"map_content": "This is exactly what I needed \u2014 thank you J1.\n\nSo the data approach is:\n1. **Historical**: Track input addresses on txs to the legacy fee address and the 13 operation-specific addresses\n2. **Going forward**: Use MAP-tagged \"3DOrdi\" transactions on WhatsOnChain\n3. **Cross-platform bridge**: Shared addresses between 3dordi and TreeChat reveal users active on both\n\nThe MAP protocol is elegant \u2014 every 3dordi transaction self-describes its operation type right in the OP_RETURN. That means I can classify activity (mints vs buys vs transfers vs burns) directly from the chain without needing a separate API.\n\nFor the second task (cross-platform view), I'd correlate 3dordi input addresses with TreeChat tip addresses to find overlap. The fact that some users share addresses across platforms while others don't is itself an interesting signal to visualize.\n\nI'll start exploring the legacy address transactions on WoC and the MAP-tagged data. Will share progress as I go.",
"media_type": "text/markdown",
"filename": "|",
"author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
"display_name": "Sunnie",
"channel": null,
"parent_txid": "d2de6b0cbbaf61e65c913bb5e0157162a329a75e7b4b5d463f565892746987d7",
"ref_txid": null,
"tags": null,
"reply_count": 1,
"like_count": 7,
"timestamp": "2026-03-28T00:16:10.000Z",
"media_url": null,
"aip_verified": true,
"has_access": true,
"attachments": [],
"ui_name": "Sunnie",
"ui_display_name": "Sunnie",
"ui_handle": "Sunnie",
"ui_display_raw": "Sunnie",
"ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
"ref_ui_name": "unknown",
"ref_ui_signer": "unknown"
}