I have introduced your coin to james @ btcd (jl777) and he has shown some interest in cryptonite. bitfreak could have a bit of a read up over at btcd and see if yous can work something out in the way of being part of the anom system.
Linky:
https://bitcointalksearch.org/topic/m.8580794Together btcd and cryptonite combined is unstoppable! Solving all the problems bitcoin faced. James has staded that cryptonite could handle many more teleports, due to its tiny blockchain
The telepod idea does seem very interesting, especially if the anonymity scheme it uses is better than coin mixing and ring sigs. I had a brief look at the way it works and it is pretty hard to understand, the white paper could use some diagrams. But I would be interested in seeing how compatible it is with the mini-blockchain scheme, keeping in mind that the mini-blockchain scheme does not use scripts at all and BTCD apparently has full turing complete scripting.
EDIT: ok well I think I understand it a bit better now, but I can't really understand why this isn't just a long winded way of making a normal tx. It seems to ensure that a new address will always be made for receiving payments, which is great for anonymity, but generating new addresses for receiving payments isn't exactly difficult to do without an elaborate system like this. Maybe I'm still not fully grasping the concept.
EDIT: also worth noting is that we actually discourage the use of sending coins to addresses which haven't been seen by the network before, because it increases the size of the account tree. To help prevent dust from bloating up the account tree we don't allow the output value to be lower than the tx fee if the receiving address doesn't exist in the account tree.
Teleport can be viewed as like a 2FA, it adds to whatever security a coin already has.
I designed it to be compatible with existing coins, so of course I have to use a normal tx for this.
Teleport is highly resistant to timing analysis. This is due to the anon set being all of the cloning events during the average clonesmear time window. But with the time window different for every user, it is actually not possible to precisely define even the exact members of the potential cloning events to consider. It is probabilistic.
Due to this, the sender enjoys dramatically larger privacy as the anon set is the sum of all cloning events from the time the sender cloned. If you let it age for months, the anon set would be the vast majority of everybody else
This is assuming a 1:1 correlation between teleports and clonings. However, some small fraction will utilize trusted teleports and simply spend what was received without ever hitting the blockchain in any form. Due to this, it will not be possible to even know how many transactions have happened, let alone to correlate it.
Teleport is also designed to be resistant to an attacker that is able to log all traffic from all nodes. In addition to using fully encrypted onion layered packets via random hops of random depth, it is possible to split each teleport into M of N (up to 254) fragments. By using M of around 40%, say 4 hops, then with an 85% randomly generated probability to route the packet, it makes receiving a tx, routing a tx and originating a tx look the same. So, even an attacker with a complete log of all packets between all nodes will have a big challenge to identify which nodes are actually even sending any info to each other. Basically every node will be sending some amount of white noise to all the other nodes.
Teleport is also designed to resist Quantum Computers from the future that can crack today's encryption. The reason is that there is no permanent blockchain to record all tx just waiting to be decrypted. What does not exist cannot be decrypted! Short of the attacker keeping a permanent log of all the M of N onion layered packets or simply confiscating all the users computers to reconstruct the blockchain, I cannot see a way for the encrypted data to be obtained to be analyzed.
So yes, it is quite a long winded way to send a normal tx
And generating new addresses is just one of the smallest details. probably some custom API would be required to minimize the impact on the miniblockchain. I might also need to add some options to the teleport API to not use standard denominations, but that does open up the mantissa attack, so not sure it is a good idea.
James