What is SECP and how it drives cross-chain development on Cardano

New cryptographic primitives are coming to Cardano to enable secure, cross-chain DApp development

Cryptography plays an integral role in the blockchain space, ensuring trust and security between network participants.

DApp developers can use cryptographic primitives as the building blocks to create secure transactions containing sensitive data, develop custom encryption and decryption algorithms, and validate such by using digital signatures.

In recent decades, Elliptic Curve Cryptography (ECC) has become the de facto primitive for developing cryptographic protocols and secure applications. ECC provides the same level of security as other mechanisms while using shorter keys and signatures.

What is SECP?

SECP, or SECP256k1 in particular, is the name of the elliptic curve. Many blockchains (including Bitcoin, Ethereum, and Binance Coin) use this curve to implement public key cryptography, which uses a key pair (public and private keys) to validate transaction signatures.

Examples of SECP include the Elliptic Curve Digital Signature Algorithm (ECDSA) and Schnorr signatures. These allow users to verify the integrity of specific signed hashed data. ECDSA and Schnorr signature algorithms work with the SECP256k1 curve in many blockchains.

Cryptography on Cardano

Cardano uses the Edwards-curve Digital Signature Algorithm (EdDSA) with elliptic curve25519 as its native signature algorithm.

This means that Plutus DApp developers who want to work with other blockchains and need to validate ECDSA and Schnorr signatures would have to spend time, effort, and funds to implement such SECP elliptic curves in Plutus. Additionally, this considerably increases potential security risks. Since ECDSA and Schnorr aren’t native to Cardano, such operations would be more expensive and time-consuming unless provided as built-in functions.

Adding new built-in functions to Plutus

To enable building cross-chain applications efficiently, Input Output Global (IOG) is adding new built-in functions to support ECDSA and Schnorr signatures along with Cardano’s native signature.

These built-in functions will become native to Cardano, and since they will be implemented and audited by experts, they will provide the highest level of security. This will allow any Plutus DApp developer to widen the choice of multi-signature or threshold signature design to use. In particular, Schnorr-based designs are well understood and widely used by the DApp community.

CIP-49 provides a more in-depth oversight of the motivation and specification for the new implementation of built-in functions. These changes affect the Plutus interpreter, so implementation will require a hard fork combinator event. To find out more about this requirement, read CIP implementation specifics.

How will new cryptographic primitives work?

Figure 1. How SECP cryptographic primitives will work on Cardano

After the new cryptographic primitives implementation, Plutus will be able to easily verify transactions from other blockchains using ECDSA and Schnorr standards. For example, Plutus will be able to natively verify signatures generated in EVM sidechains, which will improve the developer experience in terms of process simplicity, cost, and advanced security.

Community feedback indicated how the addition of new cryptographic primitives would improve the process of secure and efficient cross-chain DApp development on Cardano. Learning from the Vasil upgrade, IOG teams have done a lot of work refining the release process and are utilizing this for the SECP release. The community is already helping to test this new functionality, which will initially be deployed on the Cardano devnet. From that point, the functionality will undergo continuous testing on preview and pre-production environments. Once the community is comfortable that test benchmarks have been achieved and critical indicators have been met, IOG will propose a date of mainnet deployment via a hard fork combinator event.

To stay abreast of developments, please join IOG’s developer Discord channels.

I’d like to thank Inigo Querejeta Azurmendi, Nigel Hemsley, and Mark Irwin for their input and support in preparing this blog post.