:tada:Welcome to the EEA Trusted Token central repo!:tada:
@see [Truffle Releases]https://github.com/trufflesuite/truffle/releases
@see [Truffle]https://github.com/trufflesuite/truffle
@see [Web3j]http://web3js.readthedocs.io/en/1.0/
@see [Ganache]https://github.com/trufflesuite/ganache-core
EEA is launching a trusted execution environment (TEE) testnet on top of a Blockchain network (Kaleido running the Pantheon client using tokenization features). The first use case is an EEA trusted reward token to incentivize EEA membership to participate more in EEA activities!
Diagrams and full TTF specifications for these tokens is below:
There are 3 tokens in the EEA Token ecosystem (EEA Reputation, EEA Reward, and EEA Penalty).
The tokens are used to incentivize participation of EEA member organizations and their employees in EEA SIGs and TWGs. Tokens are issued for participation in EEA activities such as working group calls, deliverables or F2F meetings. The more commitment that is required by a member organization to perform an activity, the higher the reward. If a member organization commits to something and does not deliver on the the commitment,tokens are taken away from the organization's balance.
The EEA Reward Token is used to incentivize participation of EEA member organizations and their employees in EEA SIGs and TWGs. Tokens are issued as "Grants" for participation in EEA activities such as working group calls, deliverables or F2F meetings. The EEA Reward Token Grant is a contract between the EEA SIG or TWG's chairman, the participating organization and it's contributing individuals and details the potential reward that can be earned by following through with the commitment that the grant represents. A contracted commitment to perform and contribute towards an activity by an organization will reflect the relative impact and detail the potential reward in the grant. The grant also has a potential negative reward if the commitment is not followed through. A grant has a vesting schedule that indicates when the tokens in the grant can be minted. Tokens in the grant remain as potential until a vesting occurs. The number of vests defined in the schedule determines the percentage of the tokens in the grant that can be transformed for each vesting event. In this case, there is only a single vest event.
The token grant vests at the end of the the sponsored SIG or TWG effort defined in the grant, where the token grant can mint three different kinds of tokens, Reward, Penalty and Reputation. The reputation token is a "Lifetime" score of reputation for an individual within the EEA. The Reward token has a 0 or positive value, is transferable and is applied towards the purchase of swag from an EEA swag pool or a specific sponsor bounty outlined in the grant. However, the Penalty token has a zero or negative balance, is non-transferable and burned after redeemed, which decreases the total Rewards balance. The Reputation token is non-transferable and not redeemable.
Initial issuance of a token grant is based on "potential" activity the member commits to. Full delivery of the commitment will allow the grant to vest at 100% into its positive value. Failure to deliver on a grant commitment will result in the negative value or Penalty tokens to be minted. The value of the grant, positive or negative, effects the overall Reward or Penalty tokens and individual's Reputation balances. The grant can also include a sponsor bounty, which is a donation from an interested party towards the completion of the commitment that can be obtained with redeemed Reward tokens.
Vesting of the grant issues or mints redeemable tokens, Reward or Penalty, to the organization and the Reputation tokens to the organization's contributors. The Grant contract is updated prior to vesting to reflect the actual reward or penalty and individuals contribution percentages.
Only EEA Reward tokens can be shared between member organizations and they can be redeemed for purchase of reward swag or bounty. A negative balance, captured by the EEA Penalty token, will negatively impact the individual and organization's reputation score as well as decrease the organization's reward token purchasing power. EEA Penalty tokens are not transferrable. The normal token accounting period is the anniversary cycle of a membership organization (1 year -- not one calendar year). An organization must redeem all of its Penalty tokens before it can redeem any Reward tokens.
Reputation Tokens are issued, upon vesting, to an organization's contributors establishing an individuals reputation. The token grant should be adjusted when commitments are met or before vesting indicating the split of reputation tokens by percentage to the contributors listed in the grant. The reputation split between contributors is finalized when the grant vests. Both Reward and Penalty tokens are matched 1-1 towards Reputation with the ability to improve or damage an individual's reputation. An individual's reputation cannot be negative so penalties will subtract 1-1 until exhausted or the account balance reaches 0. The reputation score of an organization is the sum of their contributors balances.
EEA Reputation tokens are a measure over time where tokens accumulate over the lifetime of an organization and represent the level of commitment of an organization to the EEA; it becomes a measure of an organization's EEA reputation. This also extends to the employees of the organization who earn the tokens in the first place; they will also keep those tokens as reputation tokens for the organization. The EEA Reputation tokens are lifetime tokens and are not transferable for any member that has earned them. EEA Reputation tokens are minted and burned, but are not redeemable.
For example, if an organization collects 10,000 tokens during its annual membership cycle, they can redeem the EEA Rewards tokens for say tickets to a future EEA Conference or other swag, or continue to accumulate. In addition, if the organization's lifetime membership EEA Reputation tokens total was 100,000 at the beginning of the membership cycle, it would be 110,000 at the end of the cycle in this example. In addition, 10,000 points would be split across the organization's employees who earned them.
As an example, the chair of a SIG sets up a EEA Grant for an organization that is committing to participate in the groups project deliverable. After defining the organizations commitment and setting Key Performance Indicators (KPI) to determine completion, the Grant Contract is defined as such:
Grant Potential:
Grant level set and contributions are updated prior to vest and reviewed by the chair, organization and participants.
Or let’s say Eugene was just a slacker and Debby still picked up the work, they could then adjust the grant with -10 to Eugene.
EEA Rewards token can be redeemed, by the organization, at the end of a membership cycle (1 year) after all of the organization's EEA Penalty tokens to purchase swag from the pool or the bounty defined in the grant. Items in the swag pool or bounty will have EEA Rewards token prices for the organization to select items to purchase from the redemption. Note, that the EEA swag pool can also have general bounty contributions from member organizations as well.
Only EEA Reward Tokens that have not been redeemed can be transferred to any member organization.
Initial token amount is 0. No tokens are initially distributed. Tokens are created or destroyed (burned) based on validated total contributions against initial grant commitments.
All initial grant values are set by the chair of the working group and any sponsor adding a bounty, then reviewed with the organization. Some of these values can be adjusted prior to vesting:
Any defined EAA activity that is deemed appropriate to earn tokens can create a token grant. The grant has initial settings for positive and negative vesting.
Initial Suggested List:
Committing to any of the above (Creation of EEA Reward Tokens) activities such as registering to participate in a SIG/TWG/SC and then not contributing/participating to that activity. EEA Reward Tokens are not burned but rather negative balances are created, via EEA Penalty Tokens for member organizations which have to be redeemed at the end of a membership cycle before any Reward tokens can be redeemed.
Reputation tokens are created based on the earned reward and penalty tokens. The reputation tokens for individuals and organizations are created and accounted for the following way:
| Question | Process | Answer |
|---|---|---|
| Who controls a token grant, when, how and where? | Sharing | Who: EEA SIG/TWG chair on behalf of the EEA; When: Any time; How: Setting and adjusting grant values; Where: No specific location required |
| Who issues a token grant, when, how and where? | Issuance | Who: EEA SIG/TWG chair on behalf of the EEA; When: Upon commitment of activity by EEA Member; How: EEA members completes or does not complete committed to activity; Where: SIGs/TWGs/Projects |
| Who vests a grant, when, how and where? | Vesting | Who: EEA Member; When: At Membership Anniversary (within a certain time frame e.g. 1 month) the token grant will vest; How: Vesting request to EEA Secretary; Where: On extension/close-out of EEA membership |
| Who redeems a token, when, how and where? | Redemption | Who: EEA Member; When: At Membership Anniversary (within a certain time frame e.g. 1 month) the token grant will vest; How: Redemption request to EEA Secretary; Where: On extension/close-out of EEA membership |
| Who liquidates a token, when, how and where? | Redemption | See Answer for Redemption process |
| What, if any, are the restrictions on token control, issuance, redemption, and liquidation? | All Processes | Token rules governing all processes and financial accounting are controlled by the EEA Steering Committee and follow the established Change Control process of the EEA. See the Token Model for control and restriction details |
| What are the Legal triggers to be considered? (money transfer regulation, securities trigger, gift card regulation, …)? | All Processes | Token design is such that the EEA token is not a security (Is not used to raise money, is not promoted as an investment, will be issued on existing platform, is not freely exchangeable, can only be used for one purpose, does not represent any interest in an entity) and cannot be traded except OTC through sharing and within the EEA ecosystem which is permissible through the EEA membership rules. The EEA is using its established banking relationships to fullfil all applicable banking and money transfer law requirements. |
| Are there token usage fees? | Redemption | There is a fee through an exchange rate to cover the EEA administrative costs of the token |
| If there are token usage fees, what is the fee schedule by value exchange? | Redemption | Fee schedule is still TBD but will be fixed |
| Where and how is the economic value capture taking place and who are the participants? | Token Economics | Where: EEA SIGs and TWGs and Projects; How: Recording of EEA Member participation and contributions; Who: EEA Members, EEA Chairs, EEA Secretary |
| Where, how and through whom is economic value entering and leaving? | Token Economics | Where: EEA Secretary; How: Redemption Requests from Members: Through Whom: EEA Member and EEA Secretary |
| Are tokens treated as a GAAP liability or as a private currency? | N/A | GAAP Liability on EEA Balance Sheet |
| How are tokens financially accounted for? | N/A | On-chain in the token contract and off-chain through a liability/credit on the EEA Balance sheet |
| Who is responsible for the financial accounting of tokens? | N/A | EEA Secretary |
| What are the currency controls both qualitative and quantitative such as liquidity/supply requirements, exchange rates? | Relevant for a private currency only | Fixed exchange rate to account for EEA accounting costs. Redemption rules ensure that tokens can only be redeemed at the rate that membership dues are received. |
| Who or what sets those controls? | Relevant for a private currency only | EEA Steering Committee |
| Who or what implements them? | Relevant for a private currency only | Token SIG + Testnet TWG |
EEA Reputation tokens are minted based on the earned EEA Reward tokens & EEA Penalty Tokens in a 1:1 relationship. The EEA Reputation tokens for individuals and organizations are created and accounted for the following way:
Looking to implement Role Based Access Control (RBAC) for the token system. Roles include:
Structure could follow something like this
Token Implementation Architecture with TEE
Add details here about initialization, deployment and migration.
The server side scripts requires at least NodeJS 8, but currently names version 10.16.3 Go to NodeJS and install the appropriate version for your system.
Yarn is required to be installed globally to minimize the risk of dependency issues. Go to Yarn and choose the right installer for your system.
Depending on your system the following components might be already available or have to be provided manually:
sudo apt-get install build-essential)Before running the provided scripts, you have to initialize your current terminal via source ./tools/initShell.sh for every terminal in use. This will add the current directory to the system PATH variables and must be repeated for time you start a new terminal window from project base directory.
For Windows, use ./tools/initShell.ps1.
Every command must be executed from within the projects base directory!
Open your terminal and change into your project base directory. From here, install all needed dependencies.
cd <project base directory>
source ./tools/initShell.sh
yarn installThis will install all required dependencies in the directory _nodemodules.
For Windows
Open up Powershell and change into your project base directory. From here, install all needed dependencies.
cd <project base directory>
.\tools\initShell.ps1
yarn installThe correct deployment order is already set in 2_deploy_contracts.js under migrations. However, the deployment order follows:
Deploy ERC1820Registry to contract address: 0x1820a4B7618BdE71Dce8cdc73aAB6C95905faD24
@see https://github.com/0xjac/ERC1820
Deploy EthereumDIDRegistry contact (ERC1056)
@see https://github.com/uport-project/ethr-did-registry
Deploy EthereumClaimsRegistry contract (ERC780)
@see https://github.com/uport-project/ethereum-claims-registry
Deploy EEAClaimsIssuer contract with address of EthereumClaimsRegistry as the EEA Admin
Deploy EEAOperator contract with addresses of (EthereumDIDRegistry, EthereumClaimsRegistry, EEAClaimsIssuer) as the EEA Admin
Deploy ReputationToken contract with address of EEAOperator as default operator. Can be deployed by any address.
Deploy PenaltyToken contract with address of EEAOperator as default operator. Can be deployed by any address.
Deploy RewardToken contract with addresses ([(EEAOperator)], EthereumDIDRegistry, EthereumClaimsRegistry, EEAClaimsIssuer). Can be deployed by any address.
We now have to register all token contracts in the EEAOperator contract.
function registerTokens(address _penaltyToken, address _rewardToken, address _reputationToken) This must be called by the EEA Admin.
EEA members must be registered on-chain as EEA members to receive tokens. To do this we use the EthereumClaimsRegistry (ERC780) contract to set the claim. The EthereumClaimsRegistry uses the mapping:
mapping(address => mapping(address => mapping(bytes32 => bytes32))) public registry;
The function call to set claims in EthereumClaimsRegistry is:
function setClaim(address subject, bytes32 key, bytes32 value)
Since bytes32 key and bytes32 value must be exactly the same and the issuer must be similar, it is best to hardcode the information we need to set the claim.
This is why we need EEAClaimsIssuer; it hard-codes bytes32 key and bytes32 value to:
keccak256(abi.encodePacked("membership")) and keccak256(abi.encodePacked("true")), respectively.
Note: these values are actually:
0xe4d89b09a6eb94125ee9c6123f55fbaef99eabb81fcefd76640abb9269a84805
and
6273151f959616268004b58dbb21e5c851b7b8d04498b4aabee12291d22fc034
It also standardizes the issuer of the claim as EEAClaimsIssuer is msg.sender and becomes the issuer. This means we can swap out EEA admin addresses, if required, but keep the same issuer address.
To set EEA membership claims call:
function setMembershipClaim(address organization)
as the owner of the contract, which should be the EEA admin
To revoke membership:
function revokeMembership(address organization)
The EEAClaimsIssuer can also set/remove any other claim through setClaim and removeClaim.
To complete our network, organizations (the EEA member) must set their employees as delegates of the organization. This allows employees, or delegates, to act on behalf of the organization, own their own address, and set their own reputation.
An organization must set the employees as delegates for delegates and organizations to receive tokens.
To do this we leverage EthereumDIDRegistry to set delegates for an organization.
The function to do this is:
function addDelegate(address identity, bytes32 delegateType, address delegate, uint validity)
This function MUST be called by the organization with:
identity set to the organization's own address
delegateType set to:
keccak256("employee"), or 0x863480501959a73cc3fea35fb3cf3402b6489ac34f0a59336a628ff703cd693e
NOTE: if delegateType is set to anything else, the delegate will not be considered registered within the smart contract ecosystem.
delegate set to the employee's address4.validity set to some number in seconds for how long the claim is valid for (e.g., 31536000 = 1 year).
Note: the validity can be set to large numbers to ensure the claim is valid for the forseeable future (e.g., 3153600000 = 100 years)
That is it, once all of these steps are complete, the EEA Admin can start issuing rewards and penalties.
As EEA Admin
For EEAOperator the callable functions are:
function batchMintRewards(address[] memory _organization, address[] memory _account, uint256[] memory _amount)
function batchMintPenalties(address[] memory _organization, address[] memory _account, uint256[] memory _amount)
function burnPenalties(address organization, uint256 amount, bytes memory operatorData)
function burnRewards(address organization, uint256 amount, bytes memory operatorData)
function burnAll(address organization)
For EEAClaimsIssuer the callable functions are:
function setMembershipClaim(address organization)
function revokeMembership(address organization)
function setClaim(address subject, bytes32 key, bytes32 value)
function removeClaim(address subject, bytes32 key)
As an Organization
For RewardToken the only callable functions are:
function send(address recipient, uint256 amount, bytes memory data)
function transfer(address recipient, uint256 amount)
function transferFrom(address holder, address recipient, uint256 amount)
function approve(address spender, uint256 value) external returns (bool)
Callable by any
For EEA Operator the only callable function is:
function balance(address account) external view returns (uint256, uint256, uint256)All EthereumClaimsRegistry functions are callable; this is a public contract.
All EthereumDIDRegistry functions are callable; this is a public contract.
All token ReadOnly functions are public functions.
To deploy the smart contracts, go into the projects root directory, and change into the truffle development console.
cd <project base directory>
source ./tools/initShell.sh
yarn run devNow you can compile, migrate and run tests.
# Compile contract
compile
# Migrate contract
migrate
# Test the contract
test
__The development console will automatically start its own TestRPC server for you!__
### Run the coverage test
To run the coverage tests, go into the projects root directory and run the coverage test.
```bash
cd <project base directory>
source ./initShell.sh
yarn run coverageThe coverage test will automatically start it's own TestRPC server for you!
To deploy the smart contracts onto Kaleido you need to specify the network.
Kaleido documentation @see https://docs.kaleido.io/
In truffle-config.js,a kaleido network is already specified, but you will need to enter credentials and URL in
a .env file.
To compile and migrate
go into the projects root directory, and change into the truffle development console.
cd <project base directory>
source ./tools/initShell.sh
yarn run consoleNow you can compile and migrate contract in Kaleido
# Compile contract
compile
# Migrate contract
migrateEEA trusted token off-chain execution is based on the EEA Off-Chain Trusted Compute Specification v1.0, the token Reward/Penalty business execution logic are actually running inside TEE (i.e. Microsoft Azure SGX VM).
Short answer is all about the Ethereum Scalability.
EEA Trusted Token Reward/Penalty business rules could be updated frequently, running all those frequently-updated execution logic via on-chain smart contracts would represent a cost. In some other use case, the smart contract could be complicated and thus be very costly.
Indeed, the on-chain (complicated or/and frequently-updated) execution logic could be securely off-loaded to the off-chain TEE (i.e. Intel SGX enclave), the execution logic can be smart contracts, or any application coded in almost any mainstream language like python, Java, JS, C++, etc...; the owner's private key (i.e. EEA/Organization admin's key which is used to sign the Blockchain transaction) could be transferred to the off-chain secure enclave within a high secure secret provision channel, and the Blockchain transaction (based on the execution logic results) could be sent directly from the TEE enclave based on owner's private key. Please note that this private key can never be inspected by anyone thanks to the protection of TEE.
With decentralized cloud computing backed by TEE, a smart contract on main-net can offload its compute-intensive workloads to off-chain networking without compromising user experience and security.
The current Token Implementation Architecture is based on Trusted Compute Framework (TCF).
iExec implemented two principle components of TEE: TEE listener and TEE execution logic, and deployed the SGX framework to Azure SGX VM.
TEE listener intercepts the token request data from the UI, parses, encrypts and send them to the remote TEE workers, the secret (i.e. owner's private key) is also managed and sent in a high-secure-channel to remote TEE enclave. TEE execution logic runs on remote TEE node and executes the token issuance/burn business logic and manage to send the transaction to Blockchain in a secure way.