Is it right sample ?
Hexadecimal 64 symbols 0-9 and a-f
085e58b702532045fa67a8eb8a0c3e7880067afbf49a3a156f862ed34a98df68
Does it include checksum ?
No Prefix ? How stranger recognise that it is Safecoin address ?
Is it right sample ?
Hexadecimal 64 symbols 0-9 and a-f
085e58b702532045fa67a8eb8a0c3e7880067afbf49a3a156f862ed34a98df68
Does it include checksum ?
No Prefix ? How stranger recognise that it is Safecoin address ?
You can use base 58 etc. but users may not wish to see these at all and send to a persons name (i.e. via the DNS/Petname etc.)
No checksum, it is a public key in this case.
They are all on the SAFE network
One could use the cid proposal of @bochaco here - adding a short checksum +make it a cid - then depending on the circumstances one can use base58 encoding, base32 or hex to represent the address - all have the same meaning (bytes + checksum) but it can be shorter/less ambiguous
(in the end a safecoin address is no more than a xor URL anyway… So if both would share the same standard that would make sense imo )
Edit:
Oh sorry didn’t read carefully enough - you yourself suggested that anyway even cooler - yes - no reason to not integrate safecoin into the dns system if it’s like a xor URL anyway! Nice! (especially that you included a pet name system explicitly ; )