What do we see in video #3 from @weapymon? He’s “selecting” skin, hair, eyes, etc… What do selectors, taproot and kaine’s messages tell us about the unsolved puzzle.
From the quotes surfaced over the years, the relevant Kaine statements were roughly:
1. Taproot Is Important For NoM
“Also exciting times for Bitcoin, Taproot unlocked a very promising use case that will prove to be the foundation for new possibilities in NoM.”
This is the big one. Notice he didn’t say Taproot helps Bitcoin. He said Taproot unlocks a foundation for NoM. That implies he saw Taproot as enabling something NoM-specific.
2. Code Instead Of JPEGs
Someone interpreted the future as: put programs in OP_RETURN and run them on NoM.
Kaine replied:
“That was the old way.”
Source: Telegram: View @zenonnetwork
Then:
“I think you can imagine what you can do if you store and transfer code instead of jpegs.”
Source: Telegram: View @zenonnetwork
This is the quote that keeps bothering you, because he’s explicitly contrasting:
- JPEG — passive data
- Code — active behavior
3. CPU PoW vs ASIC PoW
Kaine:
“The key is to balance both types of PoW.”
Then:
“CPU PoW is important for txs. ASIC PoW can be merge-mined.”
Then later:
“Replace SHA-3 with RandomX for Plasma. And ASIC friendly PoW can be obtained from merge-mining.”
This isn’t directly about Taproot, but it shows he was thinking in layers:
CPU work → transactions
ASIC work → security
NoM → orchestration
4. CivKit Could Be Implemented In Syrius
It’s another clue that Syrius was being viewed as more than a wallet — something closer to:
client + identity + marketplace + messaging + contracts
What Makes The Taproot Quote Interesting
The phrase that stands out is still:
“That was the old way.”
Because if someone says store code in OP_RETURN and the response is that’s the old way, then the implication is: there is a newer, better mechanism.
And after Taproot, the obvious candidates are:
- commitments
- selectors
- revealed paths
- script branches
- activation conditions
- proofs
which is exactly why the puzzle reconstruction is interesting.
The Strongest Version Of The Theory
Not:
- “The Taproot puzzle is Zenon code.”
- “The puzzle decodes to Syrius.”
But:
The puzzle may be demonstrating the kind of object Kaine was talking about: a verifiable selector/activation artifact where Bitcoin commits to behavior rather than merely storing data.
That’s the point where the reconstructed machine and Kaine’s comments start overlapping in a meaningful way. The overlap isn’t the bytes themselves — it’s the architecture:
Taproot → selector
selector → active path
active path → activation
activation → external verifier
And that’s very different from the old model he explicitly dismissed:
OP_RETURN → store data → read data
The theory is:
The Taproot puzzle is not a message and not a JPEG-style artifact. It is a compact code-like object: a selector machine that demonstrates how a Bitcoin Taproot commitment can point to, activate, or verify logic elsewhere.
Kaine’s hint was: don’t store JPEGs; store and transfer code. And when someone suggested OP_RETURN, he said: that was the old way.
So the “new way” would be:
Bitcoin Taproot transaction
→ commits to code / rule / pointer / selector
→ one path becomes active
→ external verifier extracts the active path
→ NoM/Syrius/Sentinels use that proof to activate or interpret something
The puzzle fits that shape because it behaves like a machine:
A, B, C, E fields
→ E selects G3
→ G3 produces kernel output 0x6b
→ G4 becomes the shared bridge/control cell
→ System B independently points back to G4
The important part is G4 = 10 41 14. Both systems converge on it, so G4 may be the “pointer/control word,” not a decoded sentence.
So the hypothesis becomes:
The Taproot artifact may be an early demonstration of code-on-Bitcoin: not executable code inside Bitcoin, but a Bitcoin-anchored selector/pointer machine whose state can be verified externally.
In NoM terms:
Bitcoin = commitment / activation layer
Sentinels = proof / artifact serving layer
Syrius = client / verifier
NoM = execution / coordination environment
This would make the puzzle less like:
“Find the hidden text.”
and more like:
“Recognize the mechanism: Bitcoin can carry verifiable code pointers, not just images or data.”
That is exactly what Kaine seemed to be alluding to.