Re: [Sipwitch-devel] Telephone number mapping via blockchain

[Rene Bartsch]

I also have an idea to solve the dynamic IP-address problem. If we put 
the callflow/number mapping directly in the blockchain we have a minimum 
update-frequency of 10 minutes at high costs.

So I suggest to only publish the public asymmetric wallet key per phone 
number in the blockchain and use a Kademlia-like Distributed-Hash-Table 
for phonenumber-mapping. That way we can exchange the RSA-public-key for 
encryption and authentication and use a hash of the public key as index 
and the array as value of a signed DHT. Sipwitch nodes can directly use 
their (dynamic) IP-Addresses in the SIP-URIs instead of being dependent 
on the Domain Name System. If an IP-address changes a Sipwitch node just 
updates the signed record in the DHT whithin milliseconds while the 
blockchain will only have a renew every 36,000 blocks or at transfer of 
the phone number to another wallet.

Mapping:

Phonenumber -> RSA public key -> hash(RSA public key) -> callflow/URI
|-------- blockchain --------|   |--------------- DHT ---------------|


What do you think?


--
Best regards,

Renne



Am 2014-07-29 14:47, schrieb Rene Bartsch:
> As a proof of concept I suggest to fork
> https://github.com/namecoin/namecoin, add a 12-digit E.164-compliant
> namespace and change the port number to run a Sipwitch-specific
> blockchain. Sipwitch can query the key/value store via the
> JSON-RPC-API of namecoind. For implementation details of
> namespaces/namecoind I suggest to contact "biolizard89", "domob",
> and/or "indolering" at the namecoin forum
> (https://forum.namecoin.info/).
>
>
>
> Am 2014-07-07 01:02, schrieb David Sugar:
> > I like this idea a lot.
> >
> > On Sunday, July 06, 2014 01:46:17 PM Rene Bartsch wrote:
> > > Hi,
> > >
> > > the Namecoin developers have tuned Bitcoin to allow namespaces
> > > (https://wiki.namecoin.info/index.php?title=Namespaces) for domains 
> > > in a
> > > blockchain.
> > > I want to suggest to use a blockchain for mapping telephone numbers 
> > > to
> > > SIP-URIs by integrating libcoin (http://libcoin.github.com/libcoin/)
> > > into Sipwitch. That way Sipwitch gets a signed P2P-key-value-storage. 
> > > As
> > > key I suggest a 12-digit E.164-compliant decimal number (which allows 
> > > to
> > > request a 3-digit international dial-prefix from ITU for
> > > PSTN-to-SIP-gateways) and as value I suggest a 3-dimensional array:
> > >
> > > Array dimensions:
> > > 1. Call sequence (absolute start time of Invite/Ring)
> > > 2. Call group
> > > 3. SIP-URI
> > >
> > > Example:
> > >
> > > {
> > >      "0": [
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060"
> > >      ],
> > >      "60": [
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060",
> > >          "sip:address@hidden<mydomain>:5060"
> > >      ],
> > >      "120": "sip:address@hidden<mydomain>:5060"
> > > }
> > >
> > >
> > > What do you think?