# \#nitro **URL:** https://research.arbitrum.io/tag/nitro/1.md [Latest](https://research.arbitrum.io/latest.md) · [Categories](https://research.arbitrum.io/categories.md) · [Tags](https://research.arbitrum.io/tags.md) --- ## [RIP-7614: Expose call stack to contracts](https://research.arbitrum.io/t/rip-7614-expose-call-stack-to-contracts/9575)
**Author:** [@canercidam](https://research.arbitrum.io/u/canercidam)\ **Replies:** 1\ **Last updated:** [February 17, 2024, 12:38am UTC](https://research.arbitrum.io/t/rip-7614-expose-call-stack-to-contracts/9575 "2024-02-17T00:38:18Z")
Hi everyone! We would like to present you our new Rollup Improvement Proposal RIP-7614, which suggests implementing a call stack that contains opcodes, addresses and function selectors, and exposing through a precompile… --- ## [WASM oracle in Nitro](https://research.arbitrum.io/t/wasm-oracle-in-nitro/55)
**Author:** [@Jonas](https://research.arbitrum.io/u/Jonas)\ **Replies:** 6\ **Last updated:** [May 29, 2022, 9:54pm UTC](https://research.arbitrum.io/t/wasm-oracle-in-nitro/55 "2022-05-29T21:54:15Z")
Motivation Solidity is a great language for articulating contracts over on-chain events. Especially for smart contracts about real-world systems however, there’s a need to perform computations which cannot be efficientl… --- ## [L1 calldata data pricing / Sequencer reimbursement, "Fee Pool" Model](https://research.arbitrum.io/t/l1-calldata-data-pricing-sequencer-reimbursement-fee-pool-model/107)
**Author:** [@DZack23](https://research.arbitrum.io/u/DZack23)\ **Replies:** 5\ **Last updated:** [June 27, 2022, 4:08pm UTC](https://research.arbitrum.io/t/l1-calldata-data-pricing-sequencer-reimbursement-fee-pool-model/107 "2022-06-27T16:08:37Z")
(h/t to @yahgwai, @EdFelten, et al) Background The transaction fee an Arbitrum user pays is derived from two components; the “L2 fee” and the “L1 fee,” each with its own pricing mechanism. The L2 fee pays for L2 gas; i… --- ## [Thoughts on Arbitrum's Proposal to Score Connections by PoW](https://research.arbitrum.io/t/thoughts-on-arbitrums-proposal-to-score-connections-by-pow/8121)
**Author:** [@zkstonks](https://research.arbitrum.io/u/zkstonks)\ **Replies:** 1\ **Last updated:** [March 1, 2023, 9:21pm UTC](https://research.arbitrum.io/t/thoughts-on-arbitrums-proposal-to-score-connections-by-pow/8121 "2023-03-01T21:21:07Z")
Offchain Labs is developing a proof-of-work mechanism to disincentivize massive sybil attacks by MEV searchers on the Arbitrum sequencer. In this post, I describe issues with the proposed mechanism and suggest alternativ… --- ## [Security In Depth, Client Diversity](https://research.arbitrum.io/t/security-in-depth-client-diversity/7896)
**Author:** [@shotaro](https://research.arbitrum.io/u/shotaro)\ **Replies:** 1\ **Last updated:** [February 15, 2023, 10:30pm UTC](https://research.arbitrum.io/t/security-in-depth-client-diversity/7896 "2023-02-15T22:30:51Z")
So nitro is based on geth. Will future roadmaps include execution client modularity, or is the fraud proof mechanism too deeply entangled with the execution client? What happens in the remote chance that there’s a bug … --- ## [Measurement on Nitro's Proof Size](https://research.arbitrum.io/t/measurement-on-nitros-proof-size/61)
**Author:** [@LEAFERx](https://research.arbitrum.io/u/LEAFERx)\ **Replies:** 1\ **Last updated:** [May 11, 2022, 4:23pm UTC](https://research.arbitrum.io/t/measurement-on-nitros-proof-size/61 "2022-05-11T16:23:12Z")
Hi there, after seeing your Nitro one step prover, I am very curious about the proof size on the WASM. In Arbitrum One I believe you claimed the proof size is around 200 bytes, maximum 500 bytes. Do you have any measurem… --- ## [Support for BLS signatures in Nitro](https://research.arbitrum.io/t/support-for-bls-signatures-in-nitro/12)
**Author:** [@edfelten](https://research.arbitrum.io/u/edfelten)\ **Replies:** 4\ **Last updated:** [August 30, 2022, 2:50pm UTC](https://research.arbitrum.io/t/support-for-bls-signatures-in-nitro/12 "2022-08-30T14:50:10Z")
We’re considering whether or when Arbitrum should support BLS signatures, on the BLS 12-381 curve, on transactions. The main advantage is that this allows the sequencer to aggregate signatures so that an entire batch of…