In posting on this subject, I clearly state that I know absolutely nothing about this topic that is outside the public domain and have no intentions to infer otherwise.

I wouldn't even comment on the topic except to counter the arrogance of some who believe in absolute security of encryption systems. In my book, that is nothing but foolhearty.

History is filled with grand claims by the inventors of crypto systems and the subsequent easy cracking by cryptanalysts. There are two types of minds and they see crypto problems differently. If you want a crypto system tested... you never ask the designers because they can never see the forrest for the trees. Cryptanalysts are premiere anti-thinkers and can usually find pathways and processes the designers would have never dreamed of.

The definition of crypto-security is never to lock the data from others because that is unattainable when you transport it through accessible mediums. Its always defined to delay the potential cracking to a time longer than the information inside could be of any use.

You can always reduce the pool of capable crackers, but you can never prevent a determined effort with necessary resources. And before you lecture me on one-time pads... that too has been compromised.

Its also fair to say that a lot of that which is encrypted never is turned into plaintext by unauthorized parties.

Commercial code-cracking
===================
There are laws. Do what you want.
You can find plenty of crypanlysis challenges to work on without violating any laws.

Regarding the original question, there are probably very very few applications where your circuitry would be of great value in cracking codes. It may be quicker to get a Phd in Theoretical Mathmetics and Operations Research before attacking that problem. Until you understand the importance of fibonacci you're probably spinning your wheels.

aka j