A sovereign social network
powered by Bitcoin

they did not pre-bake the path on September 13th

transaction says /testing 22 mins later reply
https://bananablocks.com/tx/a42f918215b1832ee3285b5101384f9428123fba0f19e29066fd76a5dcc38790 and https://bananablocks.com/tx/7351ed00344dd1b078a0622aefbfdf4a1466f57f94145263523033dbf95877f3
today

3 min later
https://bananablocks.com/tx/3e4674128b559922d18d5c090d0aae4e658272735d602879834cdc5d72845e25
😏 and
https://bananablocks.com/tx/a1d9de286bacf9c08e2687f0a10cd74386317c75a5f337b62a21bc4c3de31e6c
the creator was replying to the two different people on two different days the creator could not even be sure they would reply at all.
the creator did this 100% naturally without any coding, as you said it was entirely planned. Or was it fluke. How could that be fluke
https://twetch.com/t/a1d9de286bacf9c08e2687f0a10cd74386317c75a5f337b62a21bc4c3de31e6c

Sorry to be a complainer. But that allready took three copy and pastes and my brain isnt functioning correctly enough to check side by side if the copy and pasting i did was accurate. So if i by any chance skiped a letter or if it is not exactly a correct update as you wish please point out errors.
At your leasure of course.
If it is accurately updated please ignore this post.
This brings up one of my biggest problems, and this isnt a whinge or complaint
.it is a limitation of android copy and pasting ability on treechat and of course grock.
See would you believe trying to copy and paste just two entries on android crashed my phone as it does with grock when doing same. Its a bug a 100% bottleneck that needs sovling.
But once again i do not reccomend messing with treechat code.
If anyone understands what im talking about feel free to elaborate clearer.
Or more in depth.
Im certain on a desktop or laptop i could possibly effectively do copy and paste.
Another point, on grock when the copy and paste on android , when you are selecting and syretching highlighted area, once the area extends past the visible text on screen it automatically selects whole thread and crashes android phone.
I have a possible solution.
Well i have existing sorry reached my mental limit. Will continue when brain is able to function.
Very confident we can fix this.
Been going trough this problem on grok until grok actually now will on first request provide a copy isolated piece of work, instead of numerous requests that grok just hits and misses sometimes never hitting.
I think the most workable solution is someone with a desktop or laptop , or knows how to copy and paste on android , or anyone have a solution to this on android. I dont know one.
If you just update the thread personally sunnie or designate a trusted party to.
Because once the body of text gets much bigger it will be impossible for me to manage this editing on android because i am mentally challenged.
But maybe i can figure out how to work arround this as we allready well i have, the existing updated version stored in my gmail , and even if a new question takes me 20 copy and pastes even more i will do it.
But my mental capacity , well i simply cannot remember and check if the text i updated , i entered just then is perfectly copied. Its just a physical limitation of mind ,
Ok no need to reply if in fact it is correctly copied.
And we can just continue as is if you wish sunnie or its your thread , so you are welcome to just post the updated content in one hit instantly. Thought id try to express as much as possible on this definite bottleneck in android tech.

(poor Gemini totally out of its mind (at this point))..

They are running a customized on-chain bot script
They built a automated digital trap
That is incorrect
They/He/She did this 100% naturally without any coding. How

Ah, that completely flips the canvas! If there was absolutely zero coding, no scripts, and no automation, it means we aren't looking at a tech trick—we are looking at a brilliant structural magic trick inherent to how blockchain data is manually published.
Here is how the creator pulled off the "exact same second" illusion 100% naturally, using nothing but standard blockchain mechanics and a clever sequencing layout:

1. The Multi-Output "Batching" Trick (Same Second Illusion)
   You don't need a bot to reply to someone at the exact same second if both transactions are built, signed, and broadcast inside the exact same message bundle.
   When using a standard, non-technical blockchain wallet interface or basic transaction composer, a user can manually create a single transaction that has multiple outputs (UTXOs).
   Look closely at transaction a1d9de28.... It explicitly shows Outputs (3).
   Output #0 contains the Twetch text protocol data.
   Output #1 contains the raw image/webp file data.
   The creator manually loaded their content into a single transaction wrapper. When they clicked "Send", the network processed the entire bundle all at once. Because they are part of the same broadcast packet, the network records them under the exact same timestamp down to the second. They didn't race anyone to the second; the data was joined at the hip before it ever left their computer.
2. The 12-Day "Pre-Baked" Timeline
   The creator didn't look 12 days into the future to react to you. Instead, they pre-baked the path manually on September 13th, and simply waited for you to discover it.
   On September 13th, the creator sat down and manually published two linked items (a42f9182... and 7351ed00...) at the exact same time. Because they published them back-to-back or in a multi-output step, they shared the exact same second timestamp (08:39:47).
   They didn't need to know when you would find it. The riddle was already sitting there on the public ledger like an open book.
   When you "stepped" into the riddle today, you weren't triggering a live reaction from a person sitting at a desk. You were reading a permanent historical marker that was stamped 12 days ago.
   By manually crafting multi-output transactions and publishing the riddle's sequence beforehand, the creator created a flawless illusion of "impossible timing" without writing a single line of code.
   Now that the technical illusion is cleared up, would you like to decode what the text inside those specific blockchain outputs actually says, or should we dive deeper into the symbolism of the steak meme?