Bitcoin Forum

Bitcoin => Project Development => Topic started by: willoms on June 30, 2014, 04:24:49 PM



Title: Using blockchain to save and verify software licensing
Post by: willoms on June 30, 2014, 04:24:49 PM
Hi guys,

I'm totally new to the bitcoin. And I'm very interested in the blockchain application. Just had this idea and want to check with the community to see if it makes senses at all. Thanks a lot in advance.

I'm thinking to use blockchain to replace the software license, such as serial number. So when end user bought a software, the service can generate a message signed by user's public key and put this data into blockchain with some trivial fee. Then when user starts the software, the software goes to the service and service can download the message, then user can use his own private key to decrypt the message. If it succeeds, the software is unlocked.

Does this make sense?  
 


Title: Re: Using blockchain to save and verify software licensing
Post by: TotalPanda on July 29, 2014, 05:34:37 PM
http://www.bootstrappedbook.com/wp-content/uploads/2014/04/1-billion-dollars.png


Title: Re: Using blockchain to save and verify software licensing
Post by: gweedo on July 30, 2014, 01:10:09 AM
I think this needs to be proof of concept, because you aren't giving a lot of technical details to go off. Also what if I use your software for a 10000000 years but in 10 years you are out of business, now I can't unlock the message cause it sounds like some centralization is involved.

Try to make it decentralized that would be awesome!


Title: Re: Using blockchain to save and verify software licensing
Post by: semobo on July 30, 2014, 01:14:19 AM
Your idea would work, but wouldn't stop piracy. All someone would have to do is drain the bitcoin wallet and create a new one. Then distribute the private key so anyone can use the software.


Title: Re: Using blockchain to save and verify software licensing
Post by: gweedo on July 30, 2014, 01:16:20 AM
Your idea would work, but wouldn't stop piracy. All someone would have to do is drain the bitcoin wallet and create a new one. Then distribute the private key so anyone can use the software.

He would probably put a cap, at 5 or per payment. So once the key has been verified 5 times by the server it can't be used again.


Title: Re: Using blockchain to save and verify software licensing
Post by: Kprawn on July 30, 2014, 06:19:51 AM
Well the entry would be in the blockchain, and the record would be kept on a stable source. So the idea is great. The implementation might be a bit tricky.  ;D

Good luck, and give us more detailed feedback, when you finished please.


Title: Re: Using blockchain to save and verify software licensing
Post by: Relnarien on July 30, 2014, 08:14:00 AM
I think this needs to be proof of concept, because you aren't giving a lot of technical details to go off.

The OP is just asking if using the digital signature of Bitcoin addresses is a feasible method of verifying software licenses.


Also what if I use your software for a 10000000 years but in 10 years you are out of business, now I can't unlock the message cause it sounds like some centralization is involved.

Try to make it decentralized that would be awesome!

Most commercial software are designed to be supported for only up to 5-10 years. If you are using software that is over 10 years old, then you are using outdated software that has not been patched for any possible exploits. It may still work, but it is pretty much guaranteed that faster and more efficient variants of that software had been written within that span of time.

Centralization is obviously involved -- in fact, it is required. The point is to make sure that the end-user paid for the license to use the software. Why would a business need to decentralize that? What point is there in decentralizing it?


Your idea would work, but wouldn't stop piracy. All someone would have to do is drain the bitcoin wallet and create a new one. Then distribute the private key so anyone can use the software.

If I were using the OP's method, then I would add an "Invalidate this license" feature to the software. That way, if a private key was being shared around to pirate the software, then the software vendor (or anyone) could simply use that same key to invalidate the license key of every copy of the software using it. If the software required the user to connect online every 15 minutes or so, then the license key can still be invalidated post-verification.