License

To get the license in the test blockchain, please contact [email protected].

Sending license

This function is only for Alliance, you can see the detail from getting a license.

Mint your own token

Once you get the license from any Alliance member, you can mint your own token.

./gcoin-cli mint {amount} {color_id}

Check the license

In GCoin, each wallet can get more than one licenses. To see which licenses you have, try the command:

./gcoin-cli getlicenseinfo

The command will list all the licenses in your wallet, and tell you each license belong to which address.

Moreover, we add the license info feature into GCoin1.1, the license info should be claimed and appended in the end of the sending license transaction. Once the sending license transaction is on the blockchain, the receiver get the license and the license info won't be changed anymore.

To check the detail of each license, use the command:

./gcoin-cli getassetinfo {color_id}

Member only token

There are only few rules in license info is implemented now. The most important one is the member_control field. If it is setting to true, this color token is a member only token.The token can send/receive only within the members. Only the license owner can activate the member by sending some token to that user (address). For example, id:123 token is a member control token，and address A keep the license，and we also have other two addresses: B, C.

transaction 1. A --> B (10 id:123 token)

valid, A is the license owner, and the transaction is for activate B as a id:123 token's member.

transaction 2. B --> C (10 id:123 token)

invalid, because id:123 token is member only token, and C is not a member.

transaction 3. A --> C (12 id:123 token)

valid, A is the license owner, and the transaction is for activate C as a id:123 token's member.

transaction 4. B --> C (10 id:123 token)

valid, id:123 is member only token , and B,C are already the member of id:123 token.