CMTAT roadmap

[rya-sge]

V3.3.0

• Add support of ERC-2612 Permit
• Add support of multicall
• 358
• Improve document management and create an adapted DocumentEngine

V3.4.0

• Add support of ERC-3643
• Add support of Chainlink ProofOfReserve: smartdata

V3.5.0

• Add support of semi fungible tokens (ERC-1400)

V3.6.0

• Add support of ERC-3009

To think about

• canTransfer/canTransferFrom don't check ERC-20 balance
• Optimize batch functions

Other projects

• Integration of ACE into CMTAT
• Vyper version of CMTAT
• Update Aztec version to the latest noir version + specification
• Stellar version of CMTAT
• RuleEngine, Rules, SnapshotEngine

[sideris]

Regarding ERC-3643 I would ask what is the logic behind this.

The Tokeny contracts that are referenced have a viral license that does not let you use them for commercial purpose without getting a license. It might have changed in v4.0. but that was the reason I migrated to CMTAT.

[rya-sge]

Hello @sideris,

Thanks a lot for your comment and interest!

We plan to implement a deployment version implementing the official ERC.

This will be our own implementation, so with the same license than for the rest of CMTAT codebase (MPL-2.0).

Also we will only implement the token interface (ERC-3643), not the related identity contracts.

Best!