cybercongress/chaingear

The consensus computer driven database framework

The consensus computer driven database framework

Current state: 0.1 Euler Chaingear's release for EVM with paper.

_{Built by cyber•Congress and contributors}

Try EVM's Chaingear rigth now!

• Mainnet
• Kovan
• Rinkeby

Chaingear Dapp (Mainnet, Kovan, Rinkeby) accessible directly from IPFS: QmQmQKkPFqLS4iNiicvAqx6aJtRpYookK8iEZjojcfEqib

Note: Best option to use CYB web3 browser with .chaingear dapp, all contracts code verified with Etherscan.

Whitepaper

Chaingear - The consensus computer driven database framework

Principles of Chaingear

Chaingear is a set of smart contracts which operating in consensus computer with following principles:

0. Databases creates by user createDatabase call for Chaingear witch mints database-linked NFT token for user and deploys database with support of CRUD+TF operations. Token controls adminship of database.
1. Admin initializes database with given table/tables data schema.
2. Database admin may set user permissions for entry creation and fee for adding.
3. Each entry in database linked to NFT token (primary key) which grants a set of rights for token-entry operation as UPDATE/DELETE and TRANSFER/FUND.
4. Chaingear for given platform acts as Consensus Computer Driven Database as a Service
5. Application specific business logic should be available to operate on top of database/databases.

Chaingear on EVM, 0.1 Euler PoC

Chaingear

• Chaingear is database of database which allow deploy new databases from there and creates an associated token for adminship.
• Chaingear allow deploys different types of databases with defined functionality with connects with databases builders.
• Database Builder is a fabric of databases of given type.
• Databases may have their unique code base as an extension to the basic database.
• Database-token may be transferred, sold/traded alongside with their right adminship.
• Chaingear have fees for database creation.
• Chaingear have benefitiaries which may claim collected fees proportional to their shares.

Database

• A database is a smart contract which defines NFT tokens linked to entries. User creates database with given name and token symbol for entries.
• After deploy database admin initializes database with data schema table/tables and this allows them or/and other users to create a systematic collection of data, where rights to operations with entry defined by entry-token ownership.
• Entries data lives in Schema contract.
• Each entry may be publicly funded, an entry-token owner may claim collected funds.
• Database admin may set policy for entry creation: {OnlyAdmin, Whitelist, AllUsers} and fee for the entry-token creation and next claim fees.
• Also admin may set multiple database's beneficiaries which may claim collected fees proportional to their shares.

Chaingear UI (web3 DApp for EVM's Chaingear)

1. Web3/Metamask/Truffle/IPFS based
2. Full Chaingear control interface
3. Full custom Database control interface
4. Schema smart-contract code generation on client
5. Database ABI saves in IPFS

Contracts Overview

Configuring and deploying

General Chaingear/Database pipeline

web3 Application

General

Database

Database Deploy and Schema designer

Join Us On Telegram

If you're interested in using or developing Chaingear, come join us on Telegram

Gitcoin Tasks

Built With

• OpenZeppelin
• Truffle
• Web3.js
• IPFS

Prerequisites:

• Node.js
• Truffle
• Parity

Authors

Originally created by cyber•Congress

License

Cyber License

chaingear's Issues

Add icons for BitAssets

List of systems to rename

The problem with renames is that current names are indexed by Elasticsearch. Thus to rename we need to full reindexing. It is better to do it in batch and when (a) will be exhausted list of system to rename and (b) we will be ready to switch to identifications by chain ids.

List of system to rename:

• Nxt => NXT
• MaidSafeCoin => SAFE Network
• Storjcoin X => Storj
• BitShares Play => DacPlay
• Mastercoin (Omni) => Omni

Please post proposals in comments. I will update this list

Pre-draft BAT

Regeps for systems in Satoshi•Fund

Starbase

Final fraft Starbase

https://cyber.fund/EMC

UX may be better. Today's user story. I want to check EMC data fast. Right now I have to:

1. type cyber.fund URL
2. click search form
3. wait for EMC to appear (slow)
4. click EMC name or hit Enter

What I want:

1. type cyber.fund/EMC URL

---

Implementation will require:

1. ensure that URL handling is case sensitive
2. assume all root uppercase paths are coin names
3. generate redirects / proxy pages for every supported coin name
4. generate search form / redirect for unsupported coin name (coin not found)
5. generate search form / redirect for missing page (page not found, log referrer)

Switch to TOML

Chaingear docs

SONM

Links for Stellar

Links at Stellar page https://cyber.fund/system/Stellar are not displayed

Fix currencies names

For example:

• maidsafecoin, not SAFE Network
• bitcoin, not Bitcoin
• ether, not Ethereum
  etc.

Finish Aeternity Crowdsale

Crowdsale has been finished. Results should be fixed as well as the first price.

Bancor

Quality report calculation

Setup link checker

QA. Another story from today. Went to check what BTCD is and landed on spammed domain through cyber.fund links (#99).

The site was down for more than a year, so it could help if there was link autocheck for every PR / commit + every few days will ensure data quality of our dataset. Also should check for squatted domains.

Also, could be a good marketing point like "data quality feedback loop", which is tied to Cybernetics.

Mysterium

• final draft of publication ready
• ICO Stats filled in

Clear garbage systems

Autoupdated assets don't star system

Chaingear Init

Fix incorrect Cap due to wrong supply

• Synereo
• Factom
• Ripple
• Stellar
• Neucoin
• Augur
• BitShares Music
  Проверить:
• GetGemz
• Storj
• Moonstone
• Spells of Genesis
  Show stopper - this issue

Blockchain IDs for rated systems

Непонятно как они оказались в Радаре (внизу)

Tezos

Change address/path for generated API

Should be: /API/v0/systems.json

Chaingear landing

Add data label

This tracker needs a data label to help people not familiar with coding find some tasks to do.

We can then build an automatic queue for such issues.

AdChain

Update rating

Cofound.it

• pre-draft @trummax
• final draft @a-kov

Move aliases.CurrencyName to a token.token_name

As is: aliases.CurrencyName
Should be: token.token_name

aliases.CurrencyName after migration can be killed

Civic

Rename Objects and Arrays

Rename Oblects:

name = system
blockchain_id = genesis_id
short_description = headline
CoinMarketCap = coinmarketcap
blockTime = block_time
reward = block_reward
halfingCycle = halfing_cycle
total = total_tokens
premine = premine_tokens
difficultyCycle = difficulty_cycle
txsConfirm = txs_confirm
mintConfirm = mint_confirm

Move between Arrays and rename Objects:

symbol = token.token_symbol
metrics.rating = ratings.rating_cyber
metrics.consensus = consensus.consensus_name
metrics.algo = consensus.hashing
metrics.status = descriptions.state
metrics.type = descriptions.tags
metrics.hashtag = descriptions.hashtag
metrics.announce = events.announcement
metrics.genesis = events.genesis

Add Objects:

token.token_name
descriptions.system_type
consensus.consensus_type
links.type

Change Object to Array:

dependencies = [dependencies]

Rename Array:

metrics = specs

BAT

crowdsale times

1. utc
2. hour-wise "time left", at last day

Fix incorrect Storj cap calculation

Real cap 10x bigger

OmiseGo

How to add tokenless protocols?

Open Assets as a case

BitBTC icon

One chain - one folder

Bancor draft

Clean up API and source data

• Kill source field

Reconsile Coinmarketcap names

List of names that don't match

Fix first price and date

• First Blood
• Iconomi
• Zcash

Fix rating for ✪✪ systems

In cyberep/2 file there is 28 systems with rating ✪✪. Though chaingear has 23.
Reconciliation needed.

Pre-draft Bancor

• Collect info per topic & links

add missing icons

.svg for system icons support ~ this week

Sync users with dev

Merge dublicates

There are some data that need to be merged manually from other.toml to sources.toml

Status