phelix: 100% with you,
the problem is that in alt-crypto 99% are speculators not developers...
mnc is the 1% the problem is that in alt-crypto 99% are speculators not developers...
Topic: [NMC] Brainstorm: File Signing (Read 1705 times)
phelix: 100% with you,
the problem is that in alt-crypto 99% are speculators not developers...
the problem is that in alt-crypto 99% are speculators not developers...
I don't understand what is the advantage over a simple signature. They were invented exactly for the purpose of source verification.
The point is: Where to store the pubkey.I like something like this be created, or if it exist, know hot to do it.
http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/
Yeah, that is interesting. http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/
I like something like this be created, or if it exist, know hot to do it.
http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/
http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/
I don't understand what is the advantage over a simple signature. They were invented exactly for the purpose of source verification.
A potential new use case for Namecoin: file verification.
Verifying the source of a file is critical in the cryptocurrency world. This would be a decentralized solution.
Publish
New Namecoin entry:
name: filename
value: hash of the file, signature, established entry the file is signed from
Verify
Check signature --> file is signed by the established entry holder
The signature could be from the Namecoin key holding the established entry or a key published in the value of the established name.
The established entry could be a .bit domain or an id / personal namespace entry or something completely new. I currently tend towards the domain.
Comments? Interest?
Verifying the source of a file is critical in the cryptocurrency world. This would be a decentralized solution.
Publish
New Namecoin entry:
name: filename
value: hash of the file, signature, established entry the file is signed from
Verify
Check signature --> file is signed by the established entry holder
The signature could be from the Namecoin key holding the established entry or a key published in the value of the established name.
The established entry could be a .bit domain or an id / personal namespace entry or something completely new. I currently tend towards the domain.
Comments? Interest?
Jump to: