Roadmap Spotlight #5: New Smart Contract Features

As we continue to see development occurring on our blockchain, we are always on the lookout for feedback on how to improve our platform, either to make it easier for developers to develop on, or to add new functionalities to help improve the product offering by the teams developing on our chain.

In the last 6 months we’ve been listening to the developers and have been working on various new functionalities and features that should help improve the quality and functionality of the projects. Some of them came in the form of development tools which we reviewed last week.

In this article, we will review the new feature sets that are upcoming to help developers improve upon the existing features or add new functionalities.

Some of these features will also create new use cases for the MPC tokens

Improvements in the PBC as a Second Layer Functionality

One of our main value propositions is our cross-chain bridge (Hermes). This unique bridge and gas payment system allows other chains to be a usable asset in Partisia Blockchain. It is this bridge that allows other chains to call our MPC technology as a service and pay for it using their native coins. But at the moment the data that is transferred is through manual data attestation, and the transfer only occurs in one way (PBC -> EVM).

By implementing BYOC messages to be supportable, we will now implement a two way communication system. This allows for the smart contract writer to hook events that are happening in the EVM back to PBC. Through adding a MPC powered threshold key and tying our oracle servers to collateralize these data through MPC tokens, developers will now be able to create an automated bidirectional flow of data between the EVM and PBC. This opens up additional functionality, such as adding message information in NFTs and allowing them to be transferable cross chain, or sending and receiving of data during the actual bridging transfers.

Staking as an Insurance

Currently, once the funds inside a smart contract runs out, the contract gets deleted. We will be creating a new method to allow for SC owners to stake their MPC tokens as insurance to allow for these smart contracts to continue to live on even if the funds run out of the contract. This will allow for both a safety mechanism in the event funds do run out and also introduce another use for MPC tokens.

ZK Contract Lifetime Beyond 28 Days

Currently the data in a ZK contract lasts for 28 days. Going forward, we will introduce a way to allow for this data to be extendable to go past the 28 days through staking MPC tokens and re-funding the smart contract.

ZK Computation in Batches

This feature will allow for multiple ZK computations to be batchable so that you do not have to execute each and every computation one at a time.

Allow ZK Contracts to Control User Data

Currently the developers writing ZK smart contracts do not have flexible control of the Zero Knowledge data. Through this feature, we will allow for developers to have greater control of the type of data and the control of how the data will be used.

We hope that the above will both help improve the speed in which development can be done as well as allow for new features to be implementable by the developers.

As each of the items complete, we will make a separate announcement in our development channels.

Stay updated:

Website • Twitter • Discord • Telegram • LinkedIn • Facebook • Instagram • GitLab • Medium • YouTube