You all can also do analog of brainwalletx.github.io for SixEleven, like I did for SIGT and VTC in my previous posts.
There can working Armory, electrum, signing and verify messages (even armory hex) and converters.
I see this coin like bitcoin, using uncompressed private keys and addresses, and no any problems with import it in qt wallet.
Thanks for your hint! I did not knew about the great service of
TwoDns, yet.
Correct me if I am wrong but as far as I understand setting up a personal DNS and DDNS for a 611 [coin] domain is as simple as that using TwoDns:
1. register a 611 domain object, like
d/ExampleDomain2. register at
www.twodns.de and enable the (dns) name service for your registerred 611 domain object, like in our example: ExampleDomain.611.to
3. update your 611 domain object to use their DNS (Nameservers "tab", one per line), like in our example: {"ns":["ns1.register-it.net","ns2.register-it.net"]}
4. configure your DDNS (and all other dns related settings) of your 611 domain object on their website
5. update your DDNS entry with your router automatically using their DDNS update API.
Yeap, but before adding domain name, DDNS service software must be sure that this user is indeed the owner of the domain.
So then need signing and verify messages by private key from SixEleven address, which is associated with this name in blockchain SIL.
IMHO, that's all need for prevent of using your domain name paperwallet.611.to as example,
for the another user who can connect or resolving your DNS name through their NS servers.
So analog of Ethereum Metamask here can be useful for easy signing any messages and verify their signatures.
Also, would have been better if the domain was added and any message can been signed then and only then,
when {"ns": ["ns1.register-it.net", "ns2.register-it.net"]} is already installed for this domain!
DDNS-service can check this in the blockchain.
It need if DDNS service have
PUBLIC DNS,
and if in this cas any domain will be added there without any verifications,
resolving from this service can have more priority then updating records in your blockchain.
I don't know about their ns-servers, if it is public DNS it must be on their site.
You can contact their support.
Also, maybe, you can see
NS-SERVERS in whois data for any domain.
For example, I have 2 domain names:
global.
611.to (d/global of 611 coin)
and dyndns.
dd-dns.de (twodns.de name dyndns in zone dd-dns.de)
with IP from 2ch.hk site there.So I can see
NS-servers for this domain zones in whois:
global.611.to http://whois.domaintools.com/global.611.toWhois Record for 611.to
611 c.ns.buddyns.com
611 i.ns.buddyns.comdyndns.dd-dns.de http://whois.domaintools.com/dyndns.dd-dns.deDomain: dd-dns.de
Nserver: h2-045.net.crns.de
Nserver: ns2.crns.de
Native 611 [coin] DDNS implementation is planned to work simpler than that without the need to register and/or use external service(s):
- 611 users only need to add a secure and saltet password hash (key) to their 611 domain object.
- By using the 611 domain name (i.e. athome.611.to) and password for authentication it should be possible to update the DDNS entry with a secure 611 service URL, like with any other DDNS service.
IMHO, in this case you need to use with SIL-wallet a built-in DNS server or daemon
and specify in "Manage Names" his local IP-address:port (54 for example if 53 port is busy).
Because there can be dinamic IP, but in blockchain name updating operations need wait a confirmations.
This server can update IP for domain name after verifying signed message.
Also, IP and ports of this DNS server can be updated through DHT, or Peer Exchange,
in really decentralized netrowk, like Tox.
There is public key is unique identificator and it finded through DHT
even in the local network.Great. 3 confirmations take about 15 minutes.
It's good, but if the site will be have many peoples, 15 minutes waiting is not good.
For example, BITMEX stock exchange website. What will be there if traders will wait 15 minutes?..
Thanks for your hint!
I will deal with the matter and let you know about the results soon
Good. Easy signing and verify messages and API to working with is on the sites
will be great function for working with this coin. IMHO.
Also, as I see you have 611.to is in domain zone .to and it is Tongo centralized DNS.
For the sake of users privacy
611 (SixEleven) [coin] is publishing the blockchain domain name entries using the Tongo subdomain
611.to.
Wikipedia (dot)to quote:
.to is one of the few ccTLDs that (officially) do not maintain a (public) WHOIS database providing registrant information.
It is possible to contact domain registrants via tonic.to by typing the domain in the domain search field under "New Domain Name".[2]
...
Publishing data using the
611 (SixEleven) [coin] domain name system makes this information available
for every Internet connected device, because
611.to is an official, anonymous second level domain.
It's one of the way for connecting to the names, and it looks like a vulnerability,
if admins of the main NS servers for example will decided to delete your zone
or some domains, seized it or do resolving to any sinkhole-servers.
In this case your system not decentralized, like namecoin, but maybe you can add it to ZeroNet.
Actually that's the usage problem of Namecoin and most other crypto currencies:
You can use it only modifying or changing certain settings which are non-standard and/or using non-standard software.
I don't see any problem here,
because even now I can add
OpenNIC PUBLIC DNS server 52.174.55.168
to my router settings,
and easy open this link
http://nf.bit/viewtopic.php?f=11&t=2656&sid=526bdb072632632a00598bfbefa0ca65So if domain coins will be using
PUBLIC DNS,
like OpenNIC public DNS, Comodo Public DNS, Google Public DNS, OpenDNS Public DNS or your Tongo NS-servers,
it will be really decentralized.
ALSO DNS notes can be updated through DHT or PEER EXCHANGE
in REAL decentralized DNS network!
If distributed database of Domain Name System will be diversified by nodes
with the ability to manage domain names using private and public keys.
