# Radius > Unlocking the Institutional Digital Economy Radius provides economic infrastructure for rollups to capture MEV revenue while safeguarding users from harmful practices. Radius builds economic infrastructure enabling rollups to generate revenue through MEV capture while protecting users. The platform connects rollups with searchers to identify profitable opportunities like arbitrage and liquidations. With Secure Block Building technology, Radius ensures user transactions remain protected from harmful practices through encryption and cryptographic verification. By transforming MEV into sustainable revenue, Radius helps rollups solve high L1 data costs and transaction fee limitations, creating a foundation for long-term growth in the Ethereum ecosystem. - Type: Project - Sector: Infrastructure - Status: Active - Founded: 2025-01-01 - Profile: https://thegrid.id/profiles/radius ## Products - [Lighthouse](https://thegrid.id/profiles/radius): Lighthouse functions as a decentralized network connecting rollups with searchers to capture MEV opportunities. The system processes MEV bundles from searchers who identify profitable trading strategies across rollups. Lighthouse implements a competitive bidding mechanism for bundle inclusion, enabling rollups to collect fees from executing winning bundles. The network supports multiple MEV strategies including arbitrage, liquidations, and cross-rollup opportunities. By creating revenue beyond transaction fees, Lighthouse provides rollups with a sustainable economic foundation. (Shared Sequencer, Live, Main Product) - [Secure Block Building (SBB)](https://thegrid.id/profiles/radius): Secure Block Building implements cryptographic primitives that protect users from harmful MEV practices during block production. The system encrypts transactions directly in the user's browser with sub-second processing time. SBB utilizes Practical Verifiable Delay Encryption and Single Key Delay Encryption technologies to maintain rollup composability while preventing transaction reordering. The architecture includes slashing mechanisms enforced through native rollup security or shared security protocols. This configuration enables rollups to capture MEV revenue without exposing users to frontrunning or sandwiching attacks. (Developer Tooling, Live) - [Alpha Engine](https://thegrid.id/profiles/radius): Alpha Engine implements a unified growth platform for rollups combining revenue generation, security, and network connectivity solutions. The system integrates Radius, Symbiotic, and Avail technologies to create sustainable economics. Alpha Engine generates revenue through MEV capture, utilizes shared security infrastructure to reduce costs, and facilitates cross-rollup interoperability. The architecture supports multiple rollups simultaneously, creating an interconnected ecosystem with enhanced liquidity flow. By addressing fundamental economic challenges, Alpha Engine provides rollups with essential tools for long-term sustainability and growth. (Shared Sequencer, In Development) ## Links - [Main](https://www.theradius.xyz) - [Documentation](https://docs.theradius.xyz) - [Blog](https://www.theradius.xyz/blog) - [Media Kit/branding](https://www.dropbox.com/scl/fi/ngk2kw7bdy6dnwzxeai8u/Radius-Brand-Assets.zip?rlkey=4nca98aa0ws1zze4bcg7efyiv&st=onknjz0e&dl=1) - [GitHub](https://github.com/radiusxyz) - [Twitter / X](https://x.com/radius_xyz) - [Paragraph](https://paragraph.com/@radius) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP