Update README.md
This commit is contained in:
parent
9b7f2d3c92
commit
b8194fba45
40
README.md
40
README.md
@ -21,28 +21,31 @@ Community Inclusion Currency (CIC) technology seeks to give organizations and co
|
||||
|
||||
## CIC full system vision ##
|
||||
* Blockchain
|
||||
* Currently: We are on a public blockchain (Layer 2 side chain)
|
||||
* Currently: We are database first and uploading data to a public blockchain (Layer 2 side chain)
|
||||
* Goal: To ensure decentralization, censor proofing and fair gas prices we look for Humanitarian Blockchains like bloxberg.org.
|
||||
* Blockchain 1st vs database
|
||||
* A blockchain where gas prices can be kept to zero.
|
||||
* A Proof of Authority chain where nodes can be elected democratically.
|
||||
* A blockchain that enables easy and secure bridging to other chains.
|
||||
* Blockchain Contracts
|
||||
* [Sarafu](https://gitlab.com/cicnet/erc20-demurrage-token) - Network / Basic Income token - Mints tokens that include a demurrage.
|
||||
* [Demurrage token](https://gitlab.com/cicnet/erc20-demurrage-token) - Network / Basic Income token - Mints tokens that include a demurrage.
|
||||
* Bridge - in order to move between the side chains (Layer 2) and the Ethereum main net we need a bridge
|
||||
* Currently: We have no connections to Ethereum Mainnet
|
||||
* Goal: To have options to bridge to a variety of other tokens
|
||||
* Goal: To have options to bridge to a variety of other tokens - possibly Cosmos Protocol
|
||||
* Liquidty Pools - Enable connection of Sarafu and CICs to each other and outside networks
|
||||
* Currently not in use: Bancor Protocol v1 - [Blockchain Smart Contract](https://github.com/bancorprotocol/contracts)
|
||||
* Goal" A variety of options for connecting CICs and other tokens, such as [Static and Bonded Liquidity pools](https://www.grassrootseconomics.org/post/static-vs-bonded-liquidity-pools-for-cics)
|
||||
* Contract Deployment (Currency Creation service)
|
||||
* Currently: We currently deploy the Bancor Contract suite manually via Command line
|
||||
* Goal: A web based interface for organizations and communities to create their own tokens
|
||||
* Currently: We currently deploy all contracts via Command line
|
||||
* Goal: A web based interface for organizations and communities to create their own tokens and other contracts
|
||||
* CIC Token Creation system
|
||||
* Currently: Manual contract deployment (command line)
|
||||
* Currently: Manual contract deployment (command line) and paper based agreements with communities.
|
||||
* Goal: Registered organizations can submit an application to be an issuer, they must have:
|
||||
* an audited and legally binding backing commitment signed by local guarentors to back the total amount of a CIC .
|
||||
* The CIC issuers should also choose to add thier CIC to a liquidity pool with Sarafu or other CICs for connections
|
||||
* Longer term goal: DAOs
|
||||
* Cloud server - is where we host all of our systems, Platform, Dashboard, future blockchain node.
|
||||
* Currently: We are using AWS for instances and data storgage along with postgress databases - Transactions are done here first then synced with blockchain
|
||||
* Currently: We are using Digital Ocean for instances and data storgage along with postgress databases - Transactions are done here first then synced with blockchain
|
||||
* Goal: Migrating servers to Digital Ocean using Kubernetes.
|
||||
* Moving toward a web-based wallet and decentralized data storage with self-soverign data (certificate based)
|
||||
* Simulations
|
||||
@ -66,29 +69,22 @@ Community Inclusion Currency (CIC) technology seeks to give organizations and co
|
||||
* Wallet:
|
||||
* Currently: Users connect via USSD through AfricasTalking to connect with their wallet on the CIC Mgmt Platform, private keys are held by Grassroots Economics for these phones
|
||||
* Goal:
|
||||
* Telegram Chat bot
|
||||
* [WebApp](https://gitlab.com/grassrootseconomics/cic-docs/-/blob/master/spec/010_Web_Wallet.md)
|
||||
* Non custodial
|
||||
* Social account recovery
|
||||
* Cloud data storage (Swarm/IPFS) - opt in data, with an option for sharing and 3rd party validation
|
||||
* Market Place linkages
|
||||
* Auto-conversion – so you only have one (CIC) token (your community token) - all other tokens auto convert
|
||||
* CIC aware
|
||||
* you can change your home token to another
|
||||
* You can see the stats of any CIC you want to trade with or change to
|
||||
* You can see the effect of converting to other tokens
|
||||
* Fiat On-ramp / off-ramp - In order to enable users and donors to interact with CICs we need a way to move fiat on and off the blockchain
|
||||
* Currently: the float account is in no way linked to blockchain and handled manually (bank transfers)
|
||||
* Goal: To create API driven liquidity pools to fiat (eMoney)
|
||||
* Currently: any connection to national currency is handled manually (eMoney / bank transfers)
|
||||
* Goal: To connect to / create API driven liquidity pools to fiat (eMoney)
|
||||
* To make credit card another other payment on and offramps available and streamline our fiat to token processes.
|
||||
* Exchange Rates will be variable based on the CIC → KSH rate (depends on the liquidity pool maths)
|
||||
* Blockchain interaction (once bridged)
|
||||
* Anyone who can obtain or create any CIC token can send it to a liquidity pool if avalaible for conversion and bridging.
|
||||
* ID System -
|
||||
* Data /ID System -
|
||||
* Currently: Each user has a sim card and the Telecom provides KYC services - users are asked a pin number to access the account on USSD
|
||||
* Goal: Creating a more robust ID system for users with and without sim cards. Possibly adding brightID social ID - like technologies with confidence scoring or 3rd party biometrics
|
||||
* Non custodial data ownership on cloud where users can specify what data tehy want to make avalible
|
||||
* Goal: Creating a more robust ID system for users with and without sim cards. Possibly adding brightID social ID - like technologies with confidence scoring
|
||||
* Non custodial data ownership on cloud where users can specify what data they want to make avalible
|
||||
* Move toward a 'claims' based system where CIC are claims against redemption with endorsments and data and other claims can be created and endorsed - such as product offering, carbon offseting, SDG Impacts.
|
||||
* Rewards and Incentives
|
||||
* Currently: These incentive systems are a mixture of manual and CIC Mgmt Platform base, such as initial user air drop, referral bonuses and holding fees.
|
||||
* Currently: These incentive systems are manual, such as initial user air drop, referral bonuses and holding fees.
|
||||
* Currently: We are using a CIC by the name of Sarafu that is not backed by anything. Users get a Sarafu for free and groups will be able to create their own CICs backed by local goods and services and connect to eachother.
|
||||
* Goal: Any org developing a CIC can easily establish various rules and policies - these should be built into the token contracts.
|
||||
* Training Materials:
|
||||
|
Loading…
Reference in New Issue
Block a user