Kadena Releases Updated Smart Contract Language for 'Hybrid Blockchains'

Veröffentlicht auf by Coindesk | Veröffentlicht auf

"Pact 3.0 generally makes available the features that makes hybrid blockchains a reality. We now have the smart contract language for hybrid blockchains."

That's Stuart Popejoy, the former blockchain team lead at investment banking giant J.P. Morgan and founder of a multi-million dollar enterprise blockchain startup called Kadena.

Today, Popejoy and the Kadena team released a new version of their native computer programming language, called Pact, designed to enable safe and simple smart contract development on the blockchain.

At present, Kadena has already built a private blockchain platform called ScalableBFT and will be launching in October of this year a public blockchain platform called Chainweb.

"A programmer is [now] able to write a very simple smart contract that is able to exchange data back and forth between the public and private parts of a hybrid blockchain application without ever leaving the comfort of the Pact smart contract," Popejoy told CoinDesk.

This means that developers can deploy smart contract environments on a Kadena blockchain that independently verifies transactions happening off-chain on other blockchain networks.

Some of the immediate implications of this tooling as outlined by Popejoy include "Proving that something happened on a public blockchain in a private blockchain, proving that something happened on a private blockchain in a public blockchain, [and] proving that something happened on some other blockchain."

Secondly, Pact 3.0 introduces a functionality called "Capabilities" that help ensure secure, rights-based computing on the blockchain.

Unlike most other smart contract languages such as Solidity on the ethereum blockchain, Pact is not a Turing-complete language and does not boast immutable decentralized applications.

"Smart contracts start off as this idea that you can move more business models onto a blockchain but the immediate problem there is that they need to be really safe and not just safe but they to be simpleWe think you need to have smart contracts that are simple, that a non-technical user can understand and even code."

x