Bitcoin Forum
December 08, 2016, 08:09:24 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Infrastructure Idea: A global, distributed, encrypted database  (Read 5159 times)
ripper234
Legendary
*
Offline Offline

Activity: 1260


Ron Gross


View Profile WWW
January 02, 2012, 02:27:05 PM
 #1

http://www.reddit.com/r/bitcoinideas/comments/nzl6g/a_distributed_persistent_encrypted_database/

Please do not pm me, use ron@bitcoin.org.il instead
Mastercoin Executive Director
Co-founder of the Israeli Bitcoin Association
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481184564
Hero Member
*
Offline Offline

Posts: 1481184564

View Profile Personal Message (Offline)

Ignore
1481184564
Reply with quote  #2

1481184564
Report to moderator
1481184564
Hero Member
*
Offline Offline

Posts: 1481184564

View Profile Personal Message (Offline)

Ignore
1481184564
Reply with quote  #2

1481184564
Report to moderator
1481184564
Hero Member
*
Offline Offline

Posts: 1481184564

View Profile Personal Message (Offline)

Ignore
1481184564
Reply with quote  #2

1481184564
Report to moderator
kangasbros
Hero Member
*****
Offline Offline

Activity: 811



View Profile
January 02, 2012, 03:05:51 PM
 #2

No need to be encrypted IMO - the user can use client-side encryption if he wants.

One application similar to this would be a global content delivery network, in which everyone who has some kind of server running and internet connection can participate. To earn bitcoins with your server/computer, you would just install a client. A central service would control the clients, and sell them to whoever wants to buy some capacity.

ripper234
Legendary
*
Offline Offline

Activity: 1260


Ron Gross


View Profile WWW
January 02, 2012, 03:08:47 PM
 #3

No need to be encrypted IMO - the user can use client-side encryption if he wants.

One application similar to this would be a global content delivery network, in which everyone who has some kind of server running and internet connection can participate. To earn bitcoins with your server/computer, you would just install a client. A central service would control the clients, and sell them to whoever wants to buy some capacity.

I mean that the client libraries should use encryption - you're correct that there are use cases where you might want not to encrypt the data.
I think it should be specified and be a part of the protocol - I'd like data written by a Java client to be readable by a python or javascript one.

Please do not pm me, use ron@bitcoin.org.il instead
Mastercoin Executive Director
Co-founder of the Israeli Bitcoin Association
kangasbros
Hero Member
*****
Offline Offline

Activity: 811



View Profile
January 02, 2012, 03:45:09 PM
 #4

I mean that the client libraries should use encryption - you're correct that there are use cases where you might want not to encrypt the data.
I think it should be specified and be a part of the protocol - I'd like data written by a Java client to be readable by a python or javascript one.

One has to think about applications - a content delivery network is mostly used for transmissing big files for very large audiences all over the world. So lot of bandwidth is required, and encryption is not required. Storage isn't needed that much, however bandwidth is.

However, for backup usage, where I wan't to store some files in cloud, i need mostly storage.

Perhaps both applications (and everything between) could be addressed by the same service. If you need the content delivery function without enryption, you can use the plain service. For backup purposes, client library with encryption could be built, similar to tarspan (http://www.tarsnap.com/).

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!