Introduction

Screenshot of the wallet

Our aim is to allow municipalities to issue self-mintable utility tokens for basic goods.

The municipalities (service providers) would issue tokens as a part of an UBI or similar scheme and the clients would be free to use (burn) them in exchange of city services.

Note that the municipality doesn't need to own any infrastructure, the system as designed now is operational now and can be deployed to the ETH swarm given enough ether.

Considering the process of development of ECR20 tokens is so straightforward the idea is to develop tokens for each specific purpose, and give each token specific properties that best fit it's role - transport, electricity, internet access... in it's particular geographical location (transfer limits, any fees, option to trade or not - should be chosen in communication with regional actors).

For example:

1. some tokens may be tradeable - either directly through the ETH network, or through a specialized wallet held by the service provider which has the capability to run contracts as a wallet owner
2. most tokens will have the mintable property for the service provider - the idea here is the capability to attach a "PoW" to the minting process, ie "cleaning snow in the winter gives you X transport and Y internet access tokens"
3. used tokens will generally be burned or sank

To make this scheme useful to the general public - in public spaces such as trams, public keys can be put into Mifare cards backed by a safe & centralized cryptographic (session-key based) scheme based on the DesFire EV2 chip that has been developed in-house - those cards can be read by any NFC-capable device with appropriate cryptographic keys.

The system can be integrated with conventional banking interfaces and wallets as necessary using the FIAT bridge (jSecModule) which has also been developed in-house.

The beauty of the concept is that it's useful and usable now for a closed pilot with a limited group of "friendly users" and expanded as production experience and user base growth demands.

Develop an open source database of smart contract templates for the community tokens

Developing a token is dead-easy given a good template (often it's just a matter of parametrization), but there's a lack of good finished templates for mintable tokens which will be the main use case. The plan is to provide open source finished templates from real use cases to end clients to reduce the technical barrier to entry for prospective providers.

Instructions

First, check out our demo token on the Ropsten test network

As a developer

1. install the geth node
2. use the provided script in scripts/run_geth.sh to run the node on the Ropsten test network
3. install & run the Wallet

As a service provider

1. build the Wallet into static content and deploy it somewhere - you can use ETH Swarm, GH pages, S3, ... any place which allows you to host static files

As a client

1. install the Metamask chrome extension & follow instructions to set it up, then
   1. connect it to Ropsten test network (top of the Metamask screen)
   2. add the ECR20 token via "Add Token" option under "Tokens" tab in Metamask - the contract address of the token is 0x39dbb38e6d448ffd228534b21b9bf80e37d8fb3a
2. open the Wallet, it should be running on http://localhost:3000, but since at this point source code is shared with the meteor-dapp-wallet you can simply go to https://wallet.ethereum.org/ - your wallet should already be loaded and running via Metamask

Future development / per-provider customizations

1. customize the contract to the specific first use case
2. setup simple scripts to deploy the wallet to the Swarm
3. tweak the Wallet to allow a more streamlined user experience:
   1. list the community tokens first by default and any ETH balances later
   2. adjust the design elements to the provider's brand
   3. implement any particular extra business logic the provider might need
4. develop an open source database of smart contract templates for the tokens
5. telegram support group & discourse