🏦 American Bank ~ Trust is built on paper. Paper burns.
A bank where the manager guards the ledger like a hawk — alarms for every number change.
But the real flow of value? Barely watched.
The books are perfect, the vault is “secure”…
and something is very, very exploitable.
The team decided we should “support beginners” (read: save them from basic RE).
So we sprinkled some extra clues into the README.
See? You can solve it now! We believe in you! 😭😂
Is this a manual challenge or a program challenge ?
Flag format isn’t clear I have the key instruction, but no `.so`
Should we be looking for a `Flag{...}` or submit instruction data or base64-encoded VersionedTransaction ?
@solctf
Obscurix - A Trail of Bytes, a Key in Disguise
An innocuous Rust file was found drifting through a famous repo — a file that looks ordinary at first glance, yet feels wrong the longer you stare.
Lines don’t match. Comments don’t comment. Symbols look just slightly out of place. It’s as if someone took a real Rust module and twisted it until it resembled a cipher wearing a compiler’s skin.
Why disguise a message this way?
We @solctf are looking for contributors to submit CTF challenge ideas.
Any idea that gets selected will receive $50–$100.
Just describe your concept clearly and win! 👇👇