Monolithic Token Standard

User-friendly options trading tools are at the forefront of Optio's vision for empowering users to customize strategies for their market outlooks. Complex trading strategies for speculation and hedging will be precompiled into easy to buy structured products via an intuitive user interface.

The Optio team is working on several important initiatives that will play a role in later versions of the deployment empowering both the traders community and the StarkNet ecosystem:

  • Optio token standard

  • Fully on-chain matching engine

  • Tooling

Optio Token Standard

Optio token allows to consolidate the logic in one contract and build the entire Optio ecosystem around one single address which holds the global tokens state. It also allows batching to operate within the frame of the same contract — and all of this can be accomplished at a reduced gas cost.


A single smart contract that can govern an infinite number of tokens and token types.


Within Optio there are tokens which, although they represent the same underlying asset, need to have differentiating data tied to them. This additional metadata implicitly makes these tokens non-fungible, but in real life for us this data is going to be applied only to a subset of the token attributes (like maturity, strike, etc.) rather than an individual token.

First and foremost, it allows building better UX for Optio. It allows to batch different sequences of operations in a single transaction, like batchTransfer, batchMint, batchCreate, etc. Which will reduce gas consumption in a big way and hence transaction costs for Optio which will in turn allow Optio to reduce fees for end users.

Rights are inherently fungible, while Obligations possess far less traits of fungibility.

Another major feature — Optio token standard supports both fungible and non-fungible tokens — because of its ability to support multiple states on the same address and contract. In practical terms, this means you can send a collateral using fungibles to Optio contract and simultaneously transfer some rights and obligations as NFTs.

Why not using just ERC20?

Tokens standards like ERC-20 and ERC-721 require a separate contract to be deployed for each token type or collection. This limits certain functionality by separating and isolating each token contract into its own address. ERC20 have no mechanism on conditional reverting.

Why not ERC721?

No batch transfers, each NFT would require a dedicated transaction. Another issue is the incompatibility between ERC-20 and ERC-721 tokens. Since many DApps make use of both tokens, it becomes very complex because their contracts are created very differently.

Last updated