From 2097f2958588a3e233676d0562a5d646f4d26a5e Mon Sep 17 00:00:00 2001 From: Will Ruddick Date: Wed, 26 Aug 2020 08:24:53 +0000 Subject: [PATCH] adding tags --- spec/017_CIC Deployment.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/spec/017_CIC Deployment.md b/spec/017_CIC Deployment.md index fad9333..3c0a50f 100644 --- a/spec/017_CIC Deployment.md +++ b/spec/017_CIC Deployment.md @@ -2,12 +2,30 @@ This document describes the components and steps involved to deploy a CIC token to the network. +## TAGS + +1. Bootstrap network +1. Deploy new CIC token (converter + smarttoken) +1. List tokens in network +1. Query registry for contract address +1. Query CIC tokenCIC Supply +1. Query the Converter Contract for connector weight, reserve supply and Conversion Fee +1. Add reserve to mint CIC +1. Burn CIC to withdraw reserve + +all: simplify code (use web3 arg builders rather than manual ones) +1. 1+2: connect to wallet using jsonrpc +1. 2: enable initial tx to deposit reserve and first mint +1. 2+3: connect with my metadata registry contract (deduplication of token symbols) + ## RATIONALE Although registering a new token on the Bancor contracts will emit events upon which CIC client code can act upon, the information available is limited to the token itself and the exchange only. Therefore, a way to specify additional metadata for the entity that should be associated with the token must be provided. + + ## OVERVIEW The system consists of two smart contracts and a metadata schema. The schema describes the actual metadata, and the contracts provide the announcement of the token metadata availability, and a mechanism to locate where the metadata can be retrieved from.