Cryptoeconomic Release & Version Control - Privately coordinate git repositories and software releases.
Go to file
Jarrad Hope 3f272674b8
return path instead of gitDir, parseURL TODO
2019-02-25 14:05:36 +07:00
crvc-games@40177720c9 add crcv-games submodule 2019-02-14 17:24:06 +07:00
src return path instead of gitDir, parseURL TODO 2019-02-25 14:05:36 +07:00
.gitignore handle environment, ready for stdio communication 2019-02-25 13:52:22 +07:00
.gitmodules add crcv-games submodule 2019-02-14 17:24:06 +07:00
README.md update readme 2019-02-14 17:38:17 +07:00
crvc.nimble handle environment, ready for stdio communication 2019-02-25 13:52:22 +07:00

README.md

CRVC

Cryptoeconomic Release & Version Control

Summary

CRVC is a custom git-remote and a collection of cryptoeconomic games to allow anonymous actors to trustlessly coordinate git repositories and software releases.

The current idea is to treat git commit history and release binary hashes as Schelling Points. Git Objects are deployed on decentralized file storage (Swarm/IPFS) and are extended to provide hash of the content that is more robust than SHA1.

The work is a generalization of the discussion for providing a voluntary update mechanism to Status and encourage deterministic builds , which can be found here. Inspired by mango and pando.

Goals

  • Friends don't let friends run untrusted binaries.
  • Providing some assurance that:
    • the binaries and build environment were not tampered with
    • the same source code was used.
  • Checking for updates should be passive.
  • A user should be able to independently build and check artifacts against the respective hash of a binary.
  • Updating should be voluntary, trust is in the eye of the beholder.

Todo

  • Contract Games
  • Create a Git-Remote
  • Pretty much everything