Crypto-Badge v2.0.0 Release Notes

Crypto-Badge smart contract

Issue badge to non CAN account + RAM service (#9 )

• Allow community/issuer can issue badge to non CAN account. After user has CAN account he/she can claim this badge under the verification from 3rd-party (crypto-badge)
• Allow contract owner can pay RAM for issuers/users as a service
• Rename all table name with following rules: version_tablename. With this update, Smart contract might support to read the table by version in the future.

System ENV (#14 )

Contract owner now can update system environment through action without updating smart contract's code

Unit-test (#16 )

Add unit-test using hydra framwork

Other Changes

(#10 ) Removed unused encrypted_data in certification table

Dependencies

This release depends on eosio.cdt v1.7.x and (optionally) on can v1.8.x. To compile the contracts in this release, first install eosio.cdt v1.7.0.

For the unit-test it depend on hydra V1.0.0-beta.2

Crypto Badge v1.0.2 Release Notes

CAN Foundation is pleased to announce the stable release version v1.0.2 of the crypto-badge. This smart contract allow user can create/issue badge in CAN Network.

Crypto-badge contract

This release allow users can do following actions:

• correct parameter name from encripted_data to encrypted_data
• remove encrypted_data in certification' state data

Crypto Badge v1.0.0 Release Notes

CAN Foundation is pleased to announce the stable release version v1.0.0 of the crypto-badge. This smart contract allow user can create/issue badge in CAN Network.

Crypto-badge contract

This release allow users can do following actions:

• allow community in governance design can become an issuer.
• issuer can create a badge.
• issuer can update a badge which was created by them.
• issuer can issue a badge to any users who has CAN account..
• users can claim the badge

Dependencies

This release depends on eosio.cdt v1.7.x and (optionally) on can v1.8.x. To compile the contracts in this release, first install eosio.cdt v1.7.0.