
Layer-2 Rollup Data: Network Identity, Fees and Settlement
Read rollup activity in its own network context while retaining the relationships to settlement, data availability and cross-network movements.
Read the guideIndexbase journal / ideas for builders
Keep account, object, output and settlement context clear across different blockchains.
Follow the article feed18 articles / page 1 of 2

Read rollup activity in its own network context while retaining the relationships to settlement, data availability and cross-network movements.
Read the guide
Build a Solana wallet view that respects account and token-program structure instead of forcing every observation into an EVM-shaped record.
Read the guide
Understand how a UTXO-based wallet view differs from an account balance and why change and address coverage need explicit policies.
Read the guide
Build a shared data contract while preserving the differences between EVM, Solana, Move-based systems and UTXO networks.
Read the guide
Use Solana signature history with explicit address scope, commitment and pagination, and avoid treating one address lookup as complete wallet economics.
Read the guide
Distinguish Solana wallet ownership from token-account balances, and keep mint identity, authority and account lifecycle in portfolio data.
Read the guide
Interpret Solana pre- and post-token balances with account indexes, mint identity and missing-side handling, without inventing a zero-valued historical account.
Read the guide
Use inner-instruction evidence to understand composed Solana execution, while preserving top-level instruction context and decoder coverage.
Read the guide
Choose processed, confirmed or finalized Solana observations according to workflow requirements, and keep commitment separate from freshness and transaction success.
Read the guide
Understand Bitcoin change-output inference, avoid treating every output as an external payment, and preserve uncertainty in wallet transaction reports.
Read the guide
Use Bitcoin outpoints to identify spendable outputs, resolve input references correctly, and avoid treating a transaction ID as a unique holding.
Read the guide
Calculate Bitcoin fees from resolved input values and outputs, preserve exact satoshi arithmetic, and distinguish total fee from fee rate.
Read the guideThe editorial approach
Each guide starts with a concrete developer question and separates technical observations from the interpretation an application adds. Worked examples use illustrative values; references point to standards and technical documentation.
Published by Indexbase. Explore related guides as your requirements develop, from a first data question to a more deliberate integration workflow.