pogo
pogo
PogoBarweave
Twitter user who solved the first two Arweave puzzles, each within two days of going up, and posted the Weave 1 answer under its launch tweet.
- Solves
- 2
- Prize recorded
- 2250 AR
- Channels
- twittertwitter.com/PogoB
Log
Replied to @ArweaveP twenty minutes after the claim: Solved! The solution was "5 7 10:01 18 90 Dead Sea Bd6 Apple 039".
x.com/PogoB/status/1131654631250178049ZorenX's write-up of Puzzle 01 names pogo as the solver: a row of mini riddles typed into the page in the exact format it wanted.
zorenx.medium.com/arweave-puzzle-series-puzzle-01-solved-59aa19a0ea2fZorenX's write-up of Puzzle 02 names pogo as the solver: numbered paper pieces answered with a square count, a chess position and a cryptarithm.
zorenx.medium.com/arweave-puzzle-series-puzzle-02-solved-71fd4c71bbcWho this is
For years, just a handle in someone else's write-up. ZorenX wrote up the whole Arweave series and names pogo as the solver of Puzzle 01 and Puzzle 02. That was the entire trail. Then the launch tweet of Puzzle #1 turned out to have a reply.
Solved! The solution was "5 7 10:01 18 90 Dead Sea Bd6 Apple 039". Thank you very much for this puzzle, hoping more will come!
PogoB posted it on May 23, 2019 at 20:14 UTC. The prize wallet had moved at 19:53. Who else would have the full answer twenty minutes after the claim? ZorenX's write-up came a year later. So the record no longer guesses about a handle.
And the speed is the fun part. Puzzle 01 got its first AR on May 22. The page hit the chain the next afternoon, and Tiamat tweeted it at 18:33. Eighty minutes later the prize was gone. Seven riddles, logos included, typed in the exact format the page wanted. Puzzle 02 went up a day later and lasted under twelve hours. Two puzzles, 2250 AR. Good week.
What the record says and what it doesn't
Three facts now: the reply, plus one per write-up. The Twitter account goes in as a profile and PogoB as an alias. The key stays pogo, the name ZorenX used. Is Pogo Bounce a real name? Nobody says, and the record doesn't either.
There's also a pogo writing puzzle write-ups on Medium around the same years. Tempting. But nothing on either account points at the other, so the record keeps them apart.
The record
solver: party("pogo", {
key: "pogo",
kind: PartyKind.Person,
aliases: ["PogoB"],
about: "Twitter user who solved the first two Arweave puzzles, each within two days of going up, …",
profiles: [profile("twitter", "https://twitter.com/PogoB")],
facts: [
fact("Replied to @ArweaveP twenty minutes after the claim: …", SOLVED, { date: "2019-05-23" }),
fact("ZorenX's write-up of Puzzle 01 names pogo as the solver: …", WRITEUP),
],
}),
weave/2 carries the same key and kind with its own fact, and the registry joins the two. The reply itself is archived in assets/sources/weave/ with a screenshot, since tweets have a habit of disappearing.