Layer-2 and Layer-1 Transaction Identities
Keep rollup execution transactions separate from parent-chain settlement records, linking them without assuming one hash or timestamp represents both layers.
Overview
When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.
A rollup transaction and the parent-chain transaction carrying related settlement data belong to different networks and stages. A useful model connects them without erasing either identity.
Record both execution contexts
Store layer-2 chain ID, transaction hash and block separately from parent-chain batch or commitment references. Many rollup transactions can relate to one parent-chain publication. The parent transaction’s sender and fee payer may be an operator rather than the end user whose rollup transaction is being analysed.
Worked example: many transactions, one batch
A batch publication contains evidence related to hundreds of rollup transactions. Copying the parent transaction’s full fee and timestamp onto every child creates misleading totals and chronology. Retain the batch relationship, then use a declared fee or timing interpretation where the application needs one.
Expose stage-specific status
Distinguish execution inclusion, data publication and settlement confidence according to the rollup design. Test delayed publication and a missing parent reference. Do not call a parent-chain hash the user’s transaction hash. A cross-layer explorer link should identify which evidence stage the reader is opening.
A practical acceptance test
Link several rollup transactions to one parent-chain publication. Assert distinct transaction hashes, chain identities and timestamps. The parent fee must not be copied in full into every child’s total. If a fee allocation is supplied, test that allocated pieces reconcile to the declared parent amount and remain labelled as an allocation rather than direct receipt evidence.
Questions about the topic
Frequently asked questions
Is a rollup transaction hash its parent-chain hash?
No. They identify different transactions.
Can one parent transaction relate to many rollup transactions?
Yes. Batch publication can aggregate many child transactions.
Standards & technical documentation
