Secure Operations and Gas

Secure operations are supported via our gcEVM extension, which is implemented through a set of precompiled contracts.

To bring a new private datum into the gvEVM the function's signature should include an argument of type Inputtext. Then, inside the function, it is necessary to call ValidateCiphertext, which returns a Garbledtext if verification succeeds and an error otherwise. Then, the contract is free to save private data temporarily in Memory, by calling Offboard on the relevant Garbledtext.This returns a private datum of type Ciphertext that awaits other commands, namely, the Ciphertext type cannot serve as an operand to secure operations, rather it should be Onboarded again and turn into a Garbledtext first; alternatively, the Ciphertext may be stored permanently by simply assigning it to a state variable of the contract.

List of Operations and Their Required Gas

Each operation within the network requires a specific amount of gas. It's important to note that the following gas allocations are intended to be proportional and serve as initial estimates. The final determination of gas requirements will be made at a later stage, taking into account various factors such as network performance, usage patterns, and protocol optimizations.

List of operations supported on Garbledtextand their required gas prices

Operation

Bool

gtUint8

gtUint16

gtUint32

gtUint64

Other Special Function and Their Required Gas

A more detailed explanation on the functionality of these functions can be found in the following link.

PreviousSecure Data Types NextLibrary

Last updated 5 months ago