<p>As mentioned in the comments, I can certainly see the benefit of using the immutable recording function of the blockchain to identify and record parameters, in this case MAC (media access control) addresses, which are unique to each device.</p>

<p>Here a few challenges which will need to be overcome:</p>

<ul>
<li>having a device's MAC details would be fantastic for tracking ownership, for example, in the case of stolen goods. However, anyone with even IT basic knowledge knows it's trivial to <a href="http://www.wikihow.com/Change-a-Computer&#39;s-Mac-Address-in-Windows" rel="nofollow">change a MAC address</a>; so whilst the blockchain is immutable the data (ie MAC) addresses is not</li>
<li>privacy concerns also arise. Without going in to too much detail, it's problematic to say the least to be sharing one's identifying information on a public ledger if one had less malicious intentions (eg identification of MAC address for a stolen iPad, which could then be used to match up with <a href="https://en.wikipedia.org/wiki/Phishing#Social_responses" rel="nofollow">social phishing</a> (social engineering) with Apple Tech Support to match an owner's name with the stolen device)</li>
<li>The MAC address (or similar identifying number) should be encrypted, ideally. Homomorphic encryption allows for manipulation of data without decrypting it, and will be of great use for secure cloud based access. That being said, we're still a long way off meaningful use cases of <a href="http://en.wikipedia.org/wiki/Homomorphic_encryption" rel="nofollow">homomorphic encryption</a> in conjunction with blockchain ledgers</li>
</ul>

CC BY-SA 3.0
2014-10-20T06:49:54.453Z
2014-10-20T06:49:54.453Z
Wizard Of Ozzie
<p>I've been reading about several alternate uses for the underlying technology behind Bitcoin:</p>

<ul>
<li><a href="http://www.proofofexistence.com/" rel="nofollow">Proof of Existence</a> (digital notary)</li>
<li><a href="http://en.wikipedia.org/wiki/Namecoin" rel="nofollow">Namecoin</a> (for DNS as well as identity and messaging)</li>
</ul>

<p>I was wondering if there is any project or team working on a system for registering devices that are marketed broadly (like cellphones) with decentralized set of identity servers. Once it is registered with one server it cannot be registered with any other server, and if it is identified someone else they can look up which server and which identity manages the device. Also, if the valid user transfers the identity of the device to a new server, then everyone can be certain of the new host.</p>

CC BY-SA 3.0
2014-10-20T02:24:43.890Z
I'm not sure I understand your use case. I think you're asking for a mechanism that can map, f.e. a phone's MAC address to, "Mike's awesome identity server." That's something you could do with Namecoin, but I'm not sure why you'd want to.
Nick ODell
CC BY-SA 3.0
2014-10-20T04:36:59.680Z
You may want to if your device is stolen!
Wizard Of Ozzie
CC BY-SA 3.0
2014-10-20T05:34:07.260Z
@wizard, exactly! I'm building an identity service for a type of commercially available device that lets new owners register their device (binding it to their identity), with a centralized service the task of preventing someone else from registering the same device is simple, but what if we allow other entries to set up their own services, the ideas of a decentralized identity service sounded very much like the blockchain to me but I wanted to know if this is already being done (or if I fundimentally don't understand the blockchain (also a possibility))
Jason Sperske
CC BY-SA 3.0
2014-10-20T05:37:36.333Z
I'm in the preliminary stages of a similar project. I'll add contact details to my profile if you want to get in touch as there's way to do this using new homonorphic encryption
Wizard Of Ozzie
<proof-of-existence>
Is anyone using the blockchain (or other core Bitcome technology) for device registration?
Jason Sperske
# Is anyone using the blockchain (or other core Bitcome technology) for device registration?

(Asked by: username_0 on 2014-10-20)

I've been reading about several alternate uses for the underlying technology behind Bitcoin:

* [Proof of Existence](http://www.proofofexistence.com/) (digital notary)
* [Namecoin](http://en.wikipedia.org/wiki/Namecoin) (for DNS as well as identity and messaging)

I was wondering if there is any project or team working on a system for registering devices that are marketed broadly (like cellphones) with decentralized set of identity servers. Once it is registered with one server it cannot be registered with any other server, and if it is identified someone else they can look up which server and which identity manages the device. Also, if the valid user transfers the identity of the device to a new server, then everyone can be certain of the new host.

**Tags:** proof-of-existence

> **Comments:**
> **username_1**: I'm not sure I understand your use case. I think you're asking for a mechanism that can map, f.e. a phone's MAC address to, "Mike's awesome identity server." That's something you could do with Namecoin, but I'm not sure why you'd want to.  
> **username_2**: You may want to if your device is stolen!  
> **username_0**: @wizard, exactly! I'm building an identity service for a type of commercially available device that lets new owners register their device (binding it to their identity), with a centralized service the task of preventing someone else from registering the same device is simple, but what if we allow other entries to set up their own services, the ideas of a decentralized identity service sounded very much like the blockchain to me but I wanted to know if this is already being done (or if I fundimentally don't understand the blockchain (also a possibility))  
> **username_2**: I'm in the preliminary stages of a similar project. I'll add contact details to my profile if you want to get in touch as there's way to do this using new homonorphic encryption  

---

## 1 answers

### Answer by username_2 on 2014-10-20. Score: 2

As mentioned in the comments, I can certainly see the benefit of using the immutable recording function of the blockchain to identify and record parameters, in this case MAC (media access control) addresses, which are unique to each device.

Here a few challenges which will need to be overcome:

* having a device's MAC details would be fantastic for tracking ownership, for example, in the case of stolen goods. However, anyone with even IT basic knowledge knows it's trivial to [change a MAC address](http://www.wikihow.com/Change-a-Computer's-Mac-Address-in-Windows); so whilst the blockchain is immutable the data (ie MAC) addresses is not
* privacy concerns also arise. Without going in to too much detail, it's problematic to say the least to be sharing one's identifying information on a public ledger if one had less malicious intentions (eg identification of MAC address for a stolen iPad, which could then be used to match up with [social phishing](https://en.wikipedia.org/wiki/Phishing#Social_responses) (social engineering) with Apple Tech Support to match an owner's name with the stolen device)
* The MAC address (or similar identifying number) should be encrypted, ideally. Homomorphic encryption allows for manipulation of data without decrypting it, and will be of great use for secure cloud based access. That being said, we're still a long way off meaningful use cases of [homomorphic encryption](http://en.wikipedia.org/wiki/Homomorphic_encryption) in conjunction with blockchain ledgers


---

