RIF Rollup | Glossary
Here is a list of terms used throughout the documentation and their meaning.
| Terms | Meaning |
| L1 | The base layer blockchain, such as Rootstock (RSK), which provides foundational network and security for transactions and smart contracts. |
| Rollup | A secondary layer (L2) built on top of L1 that processes transactions off-chain for scalability and efficiency, often utilizing technologies like zkSync to bundle transactions into a single proof. |
| Owner | A user who has control over assets on the layer-2 blockchain (L2). |
| Operator | The entity responsible for managing the Rollup's operations, including processing transactions and submitting proofs to the L1 blockchain. |
| Eventually | Describes an event or action that will occur within a finite amount of time. |
| Assets in Rollup | Assets that are held in a layer-2 smart contract, controlled by their respective owners. |
| Rollup Key | A private key used by the owner to control assets deposited in the Rollup. |
| Rollup Block | Refers to a batch of multiple user transactions processed off-chain, for which a single proof of validity is submitted to the L1 blockchain. |
| Rescue Signature | A signature generated by signing the owner's message with their private key, used in Rollup internal transactions. |
| Fee Token | A token that has a liquid market volume and is listed for paying transaction fees in the Rollup. |
| ZKP (Zero-knowledge proof) | A method by which one party can prove to another party that they know a value x, without conveying any information apart from the fact that they know the value x. |
| Transaction | Actions submitted by users directly to the Rollup operator, involving the transfer or management of assets. |
| Priority Operation | Actions that users can submit directly to the zkSync smart contract, usually to ensure their transaction is processed with a certain priority. |
| Rollup Operation | A part of the rollup block that represents either a Transaction or a Priority operation. |
| Onchain Operation | Actions that the operator can include in the rollup block's public data (pubdata), which are recorded on the L1 blockchain. |
| Node Implementation | A model describing the operational structure or behavior of a transaction within the Rollup network. |
| Circuit Implementation | A model describing the operation and its witness within the context of zk-SNARKs or similar cryptographic processes. |
| Chunk | The dimension or unit of an operation within the Rollup, with each chunk having its own portion of public data allocated through witnesses. |
| Significant Bytes | The number of meaningful bytes within all bytes occupied by an operation, including the operation number. |
| Hash | The outcome of the SHA-256 function when applied to an operation's pubdata, used for operation identification. |
| zk-SNARKs | A form of zero-knowledge proof technology that allows for privacy-preserving transaction verification without revealing any specific details of the transactions themselves. |
| on-chain Data Availability | RThe process whereby, after off-chain transaction processing, a cryptographic proof (zkRollup) summarizing all transaction data is committed to the Rootstock blockchain. This includes a cryptographic hash representing state changes without detailing the transactions themselves, ensuring data availability and verifiability. |