Open
Conversation
Summary by OctaneNew Contracts
Updated ContractsNo contracts were updated. 🔗 Commit Hash: 940dcfe |
Overview
🔗 Commit Hash: 940dcfe |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CCA token is a placeholder to be used in the CCA Uniswap ICO. It is soul-bound in that only approved addresses can send tokens. The CCA token contract is intended to be the exchange contract for when the actual token is released. It is expected that the rate is 1:1.
The admin needs to eventually set the actual token address on the contract, directly transfer the asset to the CCA contract (at least the total supply of the CCA token), and unpause the contract. Users can exchange the CCA tokens for the actual token by calling
exchange(address to)orexchange(address from, address to)when available.The zap is integrated to allow users to exchange using the existing UI on cap.app. Users can approve/permit the zap's token manager to spend the CCA token. The zap cannot send CCA tokens elsewhere, so the CCA tokens must be exchanged in the same transaction.
The contract is upgradeable and uses the same access controls as other cap contracts.