-
Notifications
You must be signed in to change notification settings - Fork 19
Organisations page #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,17 +1,19 @@ | ||
| WALLETCONNECT_PROJECT_ID=<WALLETCONNECT_PROJECT_ID> | ||
| API_KEY=<PINATA_API_KEY> | ||
| API_SECRET=<PINATA_API_SECRET> | ||
| ALCHEMY_API_KEY=<ALCHEMY_API_KEY> | ||
| CONTRACT_ADDRESS=<CONTRACT_ADDRESS> | ||
| APPLICATION_ID=<APPLICATION_ID> | ||
| #API KEYS AND SECRETS | ||
|
|
||
| API_KEY= | ||
| API_SECRET= | ||
| ALCHEMY_API_KEY= | ||
|
|
||
| //CONTRACT ADDRESSES | ||
| #APPLICATION CONFIGURATION | ||
|
|
||
| APPLICATION_CHAIN_ID= | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems that Treee is currently made to work with a single blockchain. We should generalize it to be multi-chain, so that the user can choose on which blockchain he/she wants to register his/her trees. |
||
| WALLETCONNECT_PROJECT_ID= | ||
|
|
||
| TREE_NFT_CONTRACT_ADDRESS=<TREE_NFT_CONTRACT_ADDRESS> | ||
| ORGANISATION_FACTORY_CONTRACT_ADDRESS=<ORGANISATION_FACTORY_CONTRACT_ADDRESS> | ||
| CARE_TOKEN_CONTRACT_ADDRESS=<CARE_TOKEN_CONTRACT_ADDRESS> | ||
| VERIFIER_TOKEN_CONTRACT_ADDRESS=<VERIFIER_TOKEN_CONTRACT_ADDRESS> | ||
| LEGACY_TOKEN_CONTRACT_ADDRESS=<LEGACY_TOKEN_CONTRACT_ADDRESS> | ||
| PLANTER_TOKEN_CONTRACT_ADDRESS=<PLANTER_TOKEN_CONTRACT_ADDRESS> | ||
| #CONTRACT ADDRESSES | ||
|
|
||
| TREE_NFT_CONTRACT_ADDRESS= | ||
| ORGANISATION_FACTORY_CONTRACT_ADDRESS= | ||
| CARE_TOKEN_CONTRACT_ADDRESS= | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there just one care/verifier/legacy/planter token contract for everyone? If so, people could easily cheat to get more tokens. I thought each verifier would be able to mint its own set of tokens. For example, if I want to act as a verifier, I would launch my own planter token, which I can then mint and give to users who planted the trees that I have verified. |
||
| VERIFIER_TOKEN_CONTRACT_ADDRESS= | ||
| LEGACY_TOKEN_CONTRACT_ADDRESS= | ||
| PLANTER_TOKEN_CONTRACT_ADDRESS= | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not clear anymore that this is from Pinata.