kami considers itself as peer

[zemse]

This can be solved by implementing public key / address in url that is shared. A peer address can be like this:

kami://c8e1f3b9a0cdfcef9ffd2343b943989a22517b26@192.168.0.143:15985

Using such url, a kami can identify that a particular peer of it's peer is the kami itself.

Also, kami needs to check finally if the signature matches the main address

[zemse]

Doing this will also fix MIM attack scope highlighted in #27. I think having address instead of public key should be fine, since address can be derived easily by hashing the public key.