Extending the bitcoin protocol has been done numerous times by the bitcoin community to achieve its current tech stack. The QTUM project extended bitcoin to include the use of an abstract account layer to make compatibility with the Ethereum Virtual Machine possible. Antara is Komodo's bitcoin protocol enhancement that enables objects of any type to become blockchain elements. Antara also enables Turing complete logic to be part of network consensus providing a broad scope for solutions.
Komodo lead dev jl777 was able to collaborate with libscott (Scott Sattler) to include a Ripple technology called “Crypto Conditions” into komodod. Similarly to how QTUM extended bitcoin with new OP_CODEs, the komodo protocol has an additional OP_CHECK_CRYPTOCONDITION op code. Op codes are part of the consensus, not only a smart contract synchronous short computation task. Parts of this technology make up the Interledger Payment Method specification draft currently at the w3c.
Crypto Conditions is an open standard data format submission put before the IETF (Internet Engineering Task Force) who govern some of the Internet standards. This data format is agnostic to the implementation - it can be implemented in any language. It can also be implemented in any cryptographic signing scheme.
In this video, Ethereum co-founder, Web3 Consortium president & Polkadot chief engineer Dr Gavin Wood briefly explains where smart contracts limitations are met. Go to 34mins.
Further to the conceptual understanding of consensus vs smart contracts, Consensus is the network rules, transactions occur and block producers are rewarded for ordering the transactions. Smart contracts involve a vendor and a user to a service, plus the additional effort of the consensus layer to order the execution of the smart contracts. This 3rd party in the vendor-user relationship needs to be paid for their service, and this is where gas fees becomes a problem for the economics for developers.
Consensus of a module is not limited by compute, where smart contracts generate higher gas costs for each computation invoked. In saying this, smart contracts from different vendors on a single chain offer synchronous execution whereas consensus between smart chain chain consensus is asynchronous, and take longer to communicate transaction states.
The humble programmatic object can now be signed and packaged as a UTXO data structure and used in the komodo protocol for network consensus amongst peers. This is what the Antara modules are - blockchain objects.
Objects have a state and this is maintained on the blockchain. The immutable parts (functions) are compiled into machine code and run on every peer, much like a smart contract. The mutable parts are stored on the blockchain in the OP_RETURN data portion. Bitcoin op_return data has a 40 byte limit, not enough for this sentence. Komodo op_return has a 10000 byte limit, enough to write signed crytographic object states.
Antara offers developers two methods to customize their consensus rules if not using the modules that ship with Komodo. The first is to modify the source of existing modules and include with Komodo. The other is to load custom modules as a library at runtime. All modules can interact with each other once loaded, like any other programming environment. A tutorial on how the Cryptocurrency Heirs consensus is built in the developer documentation along with the Heir API description.
The first generation of Antara modules included:
These first generation components were developed in 2018 and refined in 2019 to take advantage of the multichain architecture of Komodo.
