The Frictionless smart contracts are an audited suite of smart contracts available under the permissive MIT license which enable compliant digital securities transfer, payment and settlement on EVM-compatible blockchains, such as Avalance C-Chain, Ethereum or Polygon.
The Frictionless smart contracts extend the T-REX specification ERC-3643 with specific features to operate private placements under MiFID II regulation.
The Frictionless protocol is essentially a decentralised system of privacy-protecting proofs and permissioned tokens that can only be transferred under tight controls in accordance with the regulatory rules of the underlying funds and securities which are tokenized.
The Frictionless protocol extends the ERC-3643 specification with specific features to operate private placements under MiFID II regulation. The are six main pillars of the Frictionless protocol as illustrated in the diagram below.
Identity Management - based on OnChainId all participants in the Frictionless protocol are permissioned with specific roles, defining the actions and token classes they can interact with.
Compliance - based on the ERC-3643 specification, upgradable modules for compliance enable the compliant transfer of token classes in the protocol.
Frictionless Tokens - based on the ERC-3643 specification, these are the tokens circulated in the protocol to represent securities, assets, cash contributions, cash distributions and settlements.
Treasury Management - provides the smart contract functions to mint, transfer and burn token classes in the protocol.
Proof-of-Reserve - provides independent attestations over the currencies underpinning FrictionlessFundDepositTokens.
Transfer Agency - provides the controlled transfer of tokens between participants under strict compliance. This also includes the facility to swap tokens, such as stablecoins with FrictionlessFundDepositTokens or FX swaps of FrictionlessFundDepositTokens of various denominations.
The Smart Contract Docs cover these topics in depth with visual explanations of how each contract functions along with its NATSPEC documentation.