Mojo#7167 | 1h02 | ||
Link | John Galt#0295 | 1min18s | |
Block Hash | John Galt#0295 | solved all (1st) | 2min17s |
SHA256 | zert#1398 | 2min21s | |
# | Arksun#0694 | link+block | BANsplit |
# | Rodrigues#3798 | block | BANsplit |
# | Kron#0582 | SHA+block | BANsplit |
# | VirtuGrana#3892 | block | BANsplit |
# | eric#4970 | link | BANsplit |
Three seeds were hidden on the page, and a bonus puzzle on Twitter. Open the block details on creeper and look around to find 64 hexadecimal characters.
In reality, it wasn't supposed to be so easy, hence a bonus puzzle on Twitter containing a question as ban_ address:
ban_1otaa7c41ik3cf4k1jcgaf9najcm631k1ik3bshn4j46cb4o8nsz4twxespoThis address is "valid" but was generated from a particular public key (instead of a private key). Using nanoo.tools, you get the following public key:
57484154204241534520454E434F44455320412042414E5F414444524553533FRecognize the hexadecimal ASCII range (most bytes begin with 4 or 5), decoding from hexadecimal gives:
WHAT BASE ENCODES A BAN_ADDRESS?The alphabet used for ban_ address has 32 characters, the answer is Base32.
Note: The bonus puzzle was the one intended. So, what happened? The block I sent leaked the address in the "Link". Oh well.