This repository contains Toucan Protocol's smart contracts and corresponding deployment artifacts.
During normal development, the code here may be slightly ahead or behind of the active contracts onchain. In order to view the latest state onchain, we recommend viewing the implementation contract's source code on the respective block explorer (e.g. Polygonscan). These can be found easily via our web app which provides this full list of the active contracts.
Toucan builds infrastructure to accelerate global climate action. Since our launch in 2021, we've led in real-world asset (RWA) tokenization, bringing $100 million in carbon credits onchain and enabling $4 billion in transactional volume. Our focus is on integrating high-integrity carbon removal throughout the crypto ecosystem, making climate action more transparent, accessible, and efficient.
Our website is https://toucan.earth.
To find out the technical details of Toucan Protocol, please see https://docs.toucan.earth.
In addition to what's published in this repository, we have many other technical components which we intend to publish as part of a planned initiative to incrementally Open Source the protocol, including the following:
- Test suite for the smart contracts
- Protocol deployment / maintenance scripts (hardhat tasks etc.)
- Source code for the protocol's subgraphs
We are currently working on preparing these in a form suitable for publication. This is quite a big task, so it will happen gradually.
git clone https://github.com/ToucanProtocol/contracts
cd contracts
yarn
yarn compile- Smart contracts are written in Solidity
- Hardhat development environment and various plugins
ethers.js- TheGraph for indexing of blockchain data
- Since some of the smart contracts are upgradable via the UUPS proxy system provided by Open Zeppelin, changes of already deployed contracts are realized on-chain by an upgrade process, which is subject to scheduling and governance processes.
Please see the CONTRIBUTING file.
The files in this repository are currently unlicensed (i.e. proprietary), but will be released under a Free / Open Source license as per above.
We have used the reuse tool
to aim for compliance with the REUSE
standard, using SPDX identifiers where
appropriate.