Offchain Labs builds scaling solutions for Ethereum. Its main product, Arbitrum, enables faster and cheaper Ethereum transactions by using rollup technology that bundles many transactions off-chain and posts them to Ethereum Layer 1. This Layer 2 approach reduces network congestion and transaction costs for users. Compared with other blockchain tools, Arbitrum focuses on Layer 2 rollups to improve throughput and lower fees, serving developers, businesses, and individual users who run Ethereum-based applications. The company earns revenue from transaction fees on Arbitrum and may offer premium or enterprise services. Overall, its goal is to make Ethereum more accessible and usable by increasing speed and reducing costs for decentralized applications and users.
Work here?Claim your company
Industries
Company Size
51-200
Company Stage
Series B
Total Funding
$143.7M
Headquarters
Princeton, New Jersey
Founded
2018
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Total Funding
$143.7M
Above
Industry Average
Funded Over
3 Rounds
Industry standards
Arbitrum showcased at Token2049 as Layer 2 solution for programmable economy. 2026-10-16 12:52:11 Key takeaways. * Offchain Labs showcased Arbitrum platform at Token2049 as key programmable economy player. * Arbitrum is Layer 2 scaling solution enhancing Ethereum transaction throughput and reducing fees. * Offchain Labs emphasizes Layer 2 solutions as central to blockchain ecosystem transformation. Offchain Labs showcased the Arbitrum platform at the Token2049 conference as a key player in the evolving programmable economy. The company shared insights via the official Arbitrum Twitter account, positioning Layer 2 solutions as central to this transformation. Arbitrum is a Layer 2 scaling solution for Ethereum designed to enhance transaction throughput and reduce fees, with Offchain Labs serving as the development team behind the platform. Arbitrum platform overview. Arbitrum is a Layer 2 scaling solution for Ethereum, designed to enhance transaction throughput and reduce fees. Offchain Labs, the team behind Arbitrum, develops technologies that facilitate greater programmability and efficiency in the blockchain ecosystem. The platform's focus on Layer 2 technology positions it within the broader conversation around scalability solutions for decentralized applications. Faq. What did Offchain Labs showcase at Token2049? Offchain Labs showcased the Arbitrum platform at the Token2049 conference, positioning it as a key player in the evolving programmable economy. The company shared insights via the official Arbitrum Twitter account, emphasizing Layer 2 solutions as central to blockchain transformation. What is Arbitrum and who develops it? Arbitrum is a Layer 2 scaling solution for Ethereum designed to enhance transaction throughput and reduce fees. Offchain Labs is the team behind Arbitrum, developing technologies that facilitate greater programmability and efficiency in the blockchain ecosystem. Disclaimer: The information on this page may come from third-party sources and is for reference only. It does not represent the views or opinions of Gate and does not constitute any financial, investment, or legal advice. Virtual asset trading involves high risk. Please do not rely solely on the information on this page when making decisions. For details, see the Disclaimer.
Ethereum client Prysm patches Glamsterdam test ahead of 200M gas limit increase. Release v7.2.1 shipped about 16.5 hours before Sepolia's fork, after v7.2.0 left validators defaulting to a 60 million gas limit. Published 1 hour ago · Updated 9 minutes ago AI Summary Prysm's patch ensures Sepolia validators automatically adopt 200 M gas limit, avoiding manual configuration and reflecting upcoming capacity upgrades. Ethereum client Prysm shipped a patch for Glamsterdam's Sepolia test on October 5, raising validators' default gas limit to 200 million from the fork. The release it replaced would have left those validators at 60 million unless operators changed the setting themselves. The gas limit caps how much computation each Ethereum block can hold. The 200 million setting is Sepolia's scheduled default in this client, part of the capacity increase developers are testing before any mainnet decision. The patch also changes how validators configure external block builders. Under EIP-7732, Glamsterdam moves that builder role into the protocol. v7.2.1 only changes how Prysm reads the settings. Offchain Labs, which maintains Prysm, published v7.2.1 on GitHub on Oct. 5 at 21:18 UTC. Glamsterdam was scheduled to activate on the Sepolia testnet at 13:53:36 UTC on Oct. 6, according to the release notes. Prysm is consensus-layer software, which validators run to propose and attest to blocks. What Prysm v7.2.1 changes. The release notes say v7.2.1 focuses on configuring Gloas builders in the validator client. Gloas is the consensus-layer half of Glamsterdam; Amsterdam is the execution-layer half. The release adds Sepolia's gas limit schedule, so validators default to 200 million gas from the fork at epoch 353,024. The notes say this requires no action from operators. Operators who want a different limit can set gas_limit in their proposer settings, use the keymanager API, or pass the -suggested-gas-limit flag. Under v7.2.1, that flag also applies after the fork, where it overrides the schedule. The validator client now logs a warning when the flag is set on a network with Gloas scheduled and when its value exceeds the highest scheduled limit. Why v7.2.0 defaulted to 60 million gas. Prysm's previous release, v7.2.0, scheduled the Sepolia fork and was published on Sept. 28. Its notes state that Sepolia's Gloas configuration, published upstream on Sept. 24, added an EIP-8261 schedule raising the network gas limit to 200 million at the fork. That schedule landed after v7.2.0 was cut and was not included in it. As a result, validators on v7.2.0 defaulted to 60 million gas in their Gloas proposer preferences. The v7.2.0 notes told Sepolia validators who wanted to propose at 200 million to set the value explicitly in a version 2 proposer settings file or through the keymanager API. They also stated that -suggested-gas-limit would have no effect after the fork and that a follow-up release would include the schedule. Builder settings change before updating. Under Glamsterdam's enshrined proposer-builder separation (ePBS), specialized builders compete to supply a block's transactions, and the protocol itself handles the exchange between builder and validator. Until now, that exchange has relied on outside software such as MEV-Boost relays. v7.2.1 changes the format of two builder fields in proposer settings files. auth_data and builder_pubkeys, renamed from pubkeys, now take 0x-hex values instead of base64, matching the keymanager API. The release notes tell operators testing Gloas builders to update so their builder authentication is read correctly and to review their builder settings before updating. The release also adds validator client flags that configure builders for all validators from the command line. These are -builder-urls, -builder-min-bid, -builder-boost-factor and -builder-max-execution-payment. Default builder auth_data is now derived from the builder URL's hostname, and URLs without a hostname are rejected. On the beacon node, a new -builder-bid-timeout flag sets how long to wait for builder bids. The default wait doubles to 600 milliseconds from 300 milliseconds. Partial data columns now on by default. v7.2.1 also turns on partial data columns by default. This feature lets nodes share blob data at the level of individual cells rather than whole columns. Blob data is the temporary data that layer-2 networks post to Ethereum, which nodes distribute through a system called PeerDAS. Under the change, nodes send and receive the cells they hold instead of complete columns. Operators can revert to full-column sharing with -disable-partial-data-columns. The older -partial-data-columns flag is deprecated and has no effect. The release also lists fixes for producing the first Gloas block and for replaying historical states when certain stored records are missing. What Glamsterdam brings to Sepolia. The Ethereum Foundation scheduled Glamsterdam's Sepolia activation for epoch 353,024, slot 11,296,768, as The Crypto Times reported on Sept. 29. The upgrade includes EIP-7732, which brings proposer-builder separation into the protocol, and EIP-7928, which adds block-level access lists. The v7.2.0 notes required Sepolia operators to update before the fork and to run an execution client that supports Amsterdam on Sepolia. Hoodi and mainnet dates not yet set. According to the v7.2.0 release notes, Gloas is not yet scheduled for the Hoodi testnet or for the mainnet. Operators on those networks are told to update on their regular schedule. The 200 million gas schedule in v7.2.1 applies to Sepolia only. No gas limit for the mainnet under Glamsterdam has been announced. Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.
Arbitrum volume surges following Stylus implementation. Computational gains from Stylus. Offchain Labs released the Stylus mainnet for Arbitrum One and Arbitrum Nova in August 2026. This update adds a WebAssembly-based proving environment to the existing Nitro stack. Users deploy programs written in Rust, C, or C++ alongside Solidity contracts. The dual-VM design allows these multi-language contracts to interact with the Ethereum Virtual Machine. You already know that Solidity limitations restrict high-compute applications. The dual-VM architecture allows Stylus contracts written in Rust to call existing Solidity dApps, which ensures that developers maintain full interoperability with the Ethereum Virtual Machine while they execute computationally intensive logic at near-native speeds. Developers use the Rust SDK to manage storage and handle types. The compiler translates WASM bytecode into optimized machine instructions. This process removes the interpretation overhead found in traditional EVM execution. WASM provides a stable foundation for bringing diverse development communities into the blockchain space. Because WASM can be compiled to native machine code, it delivers performance that approaches non-virtualized applications. The execution speed exceeds Solidity by an order of magnitude. This efficiency helps developers build cryptography libraries or machine learning applications. Because the system relies on a single-party sequencer, the network still presents an operational centralization risk. Revenue from the Expansion Program. Robinhood Chain went live on the Arbitrum mainnet on 1 July 2026. It operates through the Arbitrum Expansion Program. This program requires external chains to return 10% of net protocol revenue to the Arbitrum ecosystem. In July, licensing fees from the Expansion Program reached $360,000, an amount that accounted for 35% of the Arbitrum DAO monthly income. Robinhood Chain processed more than 200 million transactions during its public testnet phase. The chain's daily DEX trading volume exceeded $1.5 billion in early September. Robinhood Chain uses the Orbit framework. Under the Expansion Program, 8% of revenue goes to the Arbitrum DAO treasury and 2% goes to the Arbitrum Developer Guild. The chain follows the issuance of tokenized stocks and ETFs on Arbitrum One from June 2025. The ecosystem generated $206 million in GDP during the first half of 2026. The Arbitrum DAO accrued $6.19 million in income during the first half of 2026 from transaction fees, Timeboost, Expansion Program fees, and treasury income. The collective gross margin on protocol revenue exceeded 97% in the first half of the year. Standard Chartered estimated that Arbitrum could receive $5 million in Expansion Program fees during September. Token supply and market pressure. The implementation of Stylus and the Expansion Program establishes Arbitrum as a broad infrastructure provider. Arbitrum faces a 92.65 million ARB token unlock. This batch of tokens carries a value of $18.2 million at a price of $0.197. The total circulating supply of ARB remains at 66.8% of the total supply. While the title notes a $2.8 billion daily volume, Arbitrum DEX volume fell 68% between January and September 2026. This decline happened while the market capacity for the network remained high. ARB futures trading volume hit $2.15 billion in a 24-hour period. Open interest in these futures reached $308 million. The cumulative ecosystem income since launch reached $1.7 billion, and the Arbitrum Foundation holds ARB in its treasury. The final token vest arrives in March 2027. The market cap for ARB exceeded $1.3 billion in early September, while 9.23 billion ARB tokens were unlocked or held in the treasury as of 17 August 2026. The price of ARB approached $0.197 on September 6; this marked a 127% gain since August 30. Does the demand from Robinhood Chain offset the 92.65 million token unlock?
Arbitrum releases Nitro v3.11.4 node update. September 23, 2026 2 Mins Read Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure Tl;dr. * Offchain Labs has released Arbitrum Nitro v3.11.4. * The maintenance release includes RPC fixes and state-execution performance adjustments. * It is a node-software update, not a major protocol redesign. The update applies to the software stack used across Arbitrum One and Nova and focuses on reliability rather than introducing a headline protocol feature. Nitro v3.11.4 targets routine node improvements. According to the release notes, the update includes RPC bug fixes and changes aimed at state-execution performance. Those are the kinds of improvements that matter most to infrastructure providers, indexers and validators running production systems even if they are largely invisible to end users. A cleaner RPC layer can reduce operational friction for applications and services that depend on stable node responses, while execution improvements can help keep nodes efficient as chain activity grows. Arbitrum no longer operates like an experimental rollup where every software release needs to introduce a major new feature. The release should not be described as a large protocol overhaul or as introducing unverified WASM speedups. The official change set is narrower. For operators, however, routine releases are part of keeping the network healthy, and v3.11.4 is now the latest stable maintenance point in that process. Editorial Process for bitcoinist is centered on delivering thoroughly researched, accurate, and unbiased content. Cryptocurrencey uphold strict sourcing standards, and each page undergoes diligent review by its team of top technology experts and seasoned editors. This process ensures the integrity, relevance, and value of its content for its readers. September 22, 2026 September 21, 2026 September 20, 2026 September 18, 2026
Arbitrum ZK settlement plan could cut withdrawals from days to hours. August 22, 2026 Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure Offchain Labs is advancing work to integrate zero-knowledge proofs into Arbitrum's BoLD settlement protocol, a move designed to reduce withdrawal times from seven days to a few hours while preserving optimistic fraud proofs. The system would use ZK fast confirmations alongside Arbitrum's existing dispute architecture. That means the plan is not to remove fraud proofs entirely, but to add a faster proving layer that can improve user experience. The upgrade is not live on mainnet yet. A DAO vote is still required before deployment. So this is a roadmap and governance story, not a completed network change. Tl;dr. * Offchain Labs is working to integrate ZK proofs into Arbitrum's BoLD protocol. * The goal is to reduce withdrawal times from seven days to a few hours. * Fraud proofs are not being removed, and mainnet deployment still requires DAO approval. Why withdrawal times matter. Optimistic rollups have a user-experience problem. Their security model typically includes a challenge window, which can make withdrawals to Ethereum slow. Users may wait days unless they use liquidity providers or third-party bridging services. That delay is one of the biggest friction points for rollups. Reducing withdrawal times to a few hours would make Arbitrum feel faster and more competitive, especially for users moving assets between L2 and Ethereum mainnet. ZK proofs offer one path to that improvement. Multi-Proving gives Arbitrum more flexibility. The proposed model is important because it does not simply replace one proving system with another. By combining ZK fast confirmations with optimistic fraud proofs, Arbitrum can potentially preserve parts of its existing security model while adding a faster settlement path. That is the appeal of multi-proving. Different proof systems can support different trade-offs. ZK proofs can speed up verification, while optimistic mechanisms can remain part of the dispute framework. This hybrid approach may become more common as rollups mature. BoLD is the settlement layer to watch. BoLD is Arbitrum's dispute and settlement framework. Integrating ZK proofs into BoLD would affect how the network confirms and settles state back to Ethereum. That makes the work important for Arbitrum's long-term architecture, not just a surface-level user feature. If the integration works, it could improve withdrawal speed without abandoning the system's optimistic roots. That would be a significant technical step. But it needs governance approval and careful implementation. Not live yet. The main caution is timing. The upgrade should not be described as already active on Arbitrum mainnet. Development progress is not the same as deployment. A DAO vote is still needed, and implementation details may change before launch. Crypto markets often price roadmap items early. That can create confusion when users expect immediate changes. For now, withdrawals should not be assumed to have already moved from days to hours. The plan is promising, but not finished. What comes next. The DAO process is the next milestone. If Arbitrum governance supports the deployment, attention will shift to rollout timing, security review, and real-world performance. Users will want to see whether withdrawals become reliably faster without adding new risks. For Arbitrum, the upgrade could strengthen its position in the L2 market. Faster settlement would make the network more competitive against other rollups and alternative chains, while the multi-proving model could give developers more confidence in the long-term design. The broader message is clear: Arbitrum is not standing still. It is trying to make optimistic rollups feel faster without throwing away their security model.
Find jobs on Simplify and start your career today
Industries
Company Size
51-200
Company Stage
Series B
Total Funding
$143.7M
Headquarters
Princeton, New Jersey
Founded
2018
Find jobs on Simplify and start your career today