Search content
Sort by
Showing 20 of 25 results by mi1994
Okay, I have a theory.
Suppose the puzzle creator generated an aztec code with the password which is 19x19 pixels.
Take a copy of the original code and rotate it 180 degrees.
Now cut out a triangle from the lower right of the new rotated image (defined by top right, bottom right and bottom left corners). Paste this over the original image.
Now, the pixels along the line defined by top right and bottom left would have been swapped. But it looks like the pixels in this image are mirrored. So that's 9 pixels that were left untouched (if you don't count the very center pixel). That would mean exactly 181 pixels were 'lost' in this process.
19+18+17+16+...2+1 - 9 = 181
Now suppose you wanted to encode the 'missing' lower right corner in the pixels of the newly created 'invalid' aztec image. You would need 181 pixels to encode on/off, right?
Suppose you went through this process and discovered that the now invalid aztec code you created (original + pasted part) only had 179 pixels set (just because that's the way the encoding went for the top left part). What would you do? Well, just add 2 pixels to the lower right corner since that's the section that's going to be restored anyway. (That would explain why there are 2 extra pixels in the bottom mirror part.)
So, in short, I believe the goal of this first step is to restore the original aztec code. There are 181 pixels that need to be restored in the lower right corner and I believe that information is given in the 181 pixels of this image.
The only part that is troubling is that you only need on/off information for those 181 pixels so the 3x3 grid and triangles are still a mystery. This theory might be totally wrong but it would explain the 181 count and 'mirrored' aztec image.
http://i.imgur.com/z68P9Um.png
(181 pixels to reconstruct = # of pixels in mirrored invalid aztec)
The way you have split it it is still invalid as the top right orientation marker is missing, and the first 5 codewords are still readable giving ".e: " (ignore the quotes) which doesn't work, and doesn't resemble the start of anything meaningful.Suppose the puzzle creator generated an aztec code with the password which is 19x19 pixels.
Take a copy of the original code and rotate it 180 degrees.
Now cut out a triangle from the lower right of the new rotated image (defined by top right, bottom right and bottom left corners). Paste this over the original image.
Now, the pixels along the line defined by top right and bottom left would have been swapped. But it looks like the pixels in this image are mirrored. So that's 9 pixels that were left untouched (if you don't count the very center pixel). That would mean exactly 181 pixels were 'lost' in this process.
19+18+17+16+...2+1 - 9 = 181
Now suppose you wanted to encode the 'missing' lower right corner in the pixels of the newly created 'invalid' aztec image. You would need 181 pixels to encode on/off, right?
Suppose you went through this process and discovered that the now invalid aztec code you created (original + pasted part) only had 179 pixels set (just because that's the way the encoding went for the top left part). What would you do? Well, just add 2 pixels to the lower right corner since that's the section that's going to be restored anyway. (That would explain why there are 2 extra pixels in the bottom mirror part.)
So, in short, I believe the goal of this first step is to restore the original aztec code. There are 181 pixels that need to be restored in the lower right corner and I believe that information is given in the 181 pixels of this image.
The only part that is troubling is that you only need on/off information for those 181 pixels so the 3x3 grid and triangles are still a mystery. This theory might be totally wrong but it would explain the 181 count and 'mirrored' aztec image.
http://i.imgur.com/z68P9Um.png
(181 pixels to reconstruct = # of pixels in mirrored invalid aztec)
Stuck and unsure which direction to go at this point and what parts of the available information are relevant for this stage (no luck with any of the approaches so far):
- use content of the qr codes?
- anagrams?
- use the markings?
- use the pipes?
- decode the aztec as something else? (since no proper orientation markers, and apparent improbable symmetry suggesting it might not be an aztec code)
- select appropriate pixels from the aztec using markings or pipes, and decode entire code? (the aztec core does not contain proper orientation markers though)
- select appropriate pixels from the aztec using markings or pipes, and decode part of the code? (the aztec core mode message indicates 2 layers and 7 data codewords, so presumably the keypad code is <= 7 characters)
Any opinions or hints to narrow it down?
- use content of the qr codes?
- anagrams?
- use the markings?
- use the pipes?
- decode the aztec as something else? (since no proper orientation markers, and apparent improbable symmetry suggesting it might not be an aztec code)
- select appropriate pixels from the aztec using markings or pipes, and decode entire code? (the aztec core does not contain proper orientation markers though)
- select appropriate pixels from the aztec using markings or pipes, and decode part of the code? (the aztec core mode message indicates 2 layers and 7 data codewords, so presumably the keypad code is <= 7 characters)
Any opinions or hints to narrow it down?
A phone pad?
1=0
2= ABC
3= DEF
4=GHI
5= JKL
6= MNO
7 = PQRS
8 = TUV
9= WXYZ
Triangle orientation could determine if it's A, B, or C. So, 2a would be A, 2b would be B, and 2c would be C?
Was just looking at my phone and thought of this. Not sure how it would apply to the squares that have four letters.
Looking at frequencies of other languages it looks closer to Italian, at least at the high end, which isn't impossible given the Rome connection.
The first step of the enigma might still be pretty simple, we're just being fed so much information and we don't know what to focus on.
I agree, it also doesn't help that we have no idea what format the code takes, for every guess you need to try capital letters, numbers in place of letters etc.I doubt that every group of symbols is a separate word though, it could be a long string of symbols with one representing a space. Also, the map says 'the journey inwards begins here' , it could be they are meant to be read in a spiral towards the center.
Edit: 1b is interesting, it is the most frequent symbol however the first occurrence of it is at the end of the 6th row.
Edit: 1b is interesting, it is the most frequent symbol however the first occurrence of it is at the end of the 6th row.
Diagonal? north east to south west and rotated 180 (Early and no coffee yet)
Yeah,was a bit too quick to write that, whatever way you split it evenly is going to give two very similar sections.Just seems weird that on such a large image there are only 2 differences in the pattern and they are very close together.
Tried manually decoding it as an Aztec anyway, but didn't get a working code, although i could have made a mistake.
I don't think it's a valid Aztec code because it's missing orientation marks. However the pattern is quite interesting as if you split it horizontally the two halves are almost identical, and i find it hard to believe that that is a complete coincidence.
Re: [ANN – NEW COIN 2014] [NOBLE] = NobleCoin = Ticker: [NOBL]
What's up with this? https://www.virustotal.com/en/file/40003137e227fac83f55b06f478645853605a533b00141a7bd0cb24b64f9488a/analysis/
Why does it give a virus. Did you dev include this one?
Why does it give a virus. Did you dev include this one?
I'm curious about this. Is this a false-positive shown by lots of QTs, or is it unique in this case?
I don't know if it is a false-positive. I hope so mate.
Re: [ANN – NEW COIN 2014] [NOBLE] = NobleCoin = Ticker: [NOBL]
This coin looks like it could be good, just as long as the devs stay active and release all the features they have planned. I did have a minor issue with compiling on Linux, which the devs may want to fix. You need to add the obj directory to /src . But apart from that all seems to be running smoothly.
What exactly looks good about it??? it is NO different from any other scrypt clone?
Re: [ANN – NEW COIN 2014] [NOBLE] = NobleCoin = Ticker: [NOBL]
This coin looks like it could be good, just as long as the devs stay active and release all the features they have planned. I did have a minor issue with compiling on Linux, which the devs may want to fix. You need to add the obj directory to /src . But apart from that all seems to be running smoothly.
Re: [ ANN - NEW COIN PRE LAUNCH ] "NYANCOIN" Here Comes The Cat ! **LAUNCHED**
Even Linux solo miners didn't probably, I couldn't get the thing to work, libraries issue.
In general, it's a clusterf***, and with that other NyanCoin it's gonna be a complete disaster. Yeah.
Same, wouldn't compile on Linux. Don't know wtf the devs did, every other coin compiles no problem.In general, it's a clusterf***, and with that other NyanCoin it's gonna be a complete disaster. Yeah.
I'm using amazon ec2 spot inscances. About 45 of them (c1.xlarge/c3.xlarge/c1.medium).
And a script that push every minute the wallet of the mining spot instance to a regular instance.
I wich I had the same ratio mmc/hmp as you !
Maybe the luck does not want to deal with me, I don't know.
I think that bitcoind only shows mature balance, so open those wallets with qt client. Or get the address from those wallet files and search for it on http://www.chainbrowser.com/memorycoin/ .And a script that push every minute the wallet of the mining spot instance to a regular instance.
I wich I had the same ratio mmc/hmp as you !
Maybe the luck does not want to deal with me, I don't know.