Pages:
Author

Topic: [SC2] just another Proof-of-Storage coin - page 2. (Read 3638 times)

sr. member
Activity: 470
Merit: 350
That's a great concept.

Are you looking someone to fund it?

Sure, all help is welcome! Guess that I should add non-PoW coins donation addresses, or is that too radical?
hero member
Activity: 658
Merit: 1003
Sound Great! Im in, keep working!  Shocked
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
Sounds great, wonder how demanding would it be on the upload side, though.
hero member
Activity: 742
Merit: 500
I'm dying.
That's a great concept.

Are you looking someone to fund it?
sr. member
Activity: 470
Merit: 350
Hey there everyone!

A little background first

My wife is environmental engineer and she hates ASIC miners, I born in the Southamerican Andes and my city is suffering climate change, so anything that is not energy efficient is out of discussion for us. Yet we are not green-tards, we just try to improve our consumption habits. This is a mess! I know!

So, in short, Proof-of-Work is not for us, period. Let's try to build something that is energy efficient.

Proof-of-Storage

There are plenty of gigabytes not used in millions of computers connected to the internet, some of them use BitTorrent, but what about private files? Lets think on system that can compress, split, crypt and distribute several copies of my private data over the Internet, securely. A system where uploads and downloads are always free and where nodes providing storage service get rewarded with SC2 coins.

I spend yesterday afternoon and evening designing the idea, sorry if this is too drafty but guess is time to release the idea since my background on cryptocurrencies is yet too short:


  • file storage, uploads and downloads are always free!
  • 2^21 SC2 "pre-mined" to pay initial seed nodes infrastructure
  • the network makes sure that each file has at least 10 copies of each chunk
  • proof of storage:
     
    • get rewarded to proof storage of files
    • node stores each successful confirmation in the  blockchain
    • 8 confirmations needed each 32 min to consider the chunk is really stored there
  • the confirmation:
     
    • confirmations older than 8 min will be rejected by nodes
    • created by the node that stores a copy of the chunk
    • the node randomly picks 32 positions within the chunk, they are concatenated along with the microtimestamp and hashed with SHA256, which is then used as confirmation key
    • confirmation database:
         
      • chunk id
      • confirmation id: UUID
      • confirmation key
      • microtimestamp
       
  • the blockchain
     
    • a new block is generated every 2 minutes
    • a block contains
         
      • all found confirmations from last 8 min
      • all transactions from last 8 min
       
    • nodes find to each other by broadcast
  • the transaction
     
    • address to send coins from
    • receiving addresses and what amount should each receive
  • the SC2 address
     
    • 'SC' prefix
    • long-random-key
    • 'SC' suffix
  • the node
     
    • stores a full copy of the blockschain
  • the storage node
     
    • just like any other node
    • stores copies of random chunks
  • the wallet
     
    • has a RSA-8192 pair: public-key and a private key
    • the public key is used as the AES key
    • stores the the list of chunks that compose the file tree
  • the chunk
     
    • each chunk is a part of a file
    • compressed with xz
    • crypted with the private wallet key
    • named after its SHA-256 hash: [sha256].xz
    • no need duplicate storage of identical chunks
    • max chunk size starts at 1MB and varies by the total file size, the rules might change overtime as internet connection speeds improve worldwide
  • the file descriptor
     
    • split in chunks
    • named after UUID: [uuid].file
    • JSON format
    • contains:
         
      • filename
      • filesize
      • list of chunks that belong to the original file
       
  • the file tree
     
    • is just another file
    • contains the file tree (directory structure)

And that is it, willing to get your feedback!
Pages:
Jump to: