Developers are building the infrastructure for Universal High Income. EL2 is the composable protocol layer on Solana that delivers it, and the GRASS SDK is how you integrate. $INCOME is the core asset and deflationary vehicle. Build with your own token or use $INCOME directly. If you use your own token, the infrastructure is symbiotic: a portion of all activity flows back to buyback and burn $INCOME. If you use $INCOME as your ecosystem token, the benefits are even greater: more burns, more buybacks, and no separate staking requirement to access the infrastructure.
EL2 is a new infrastructure for how projects deliver value and rewards to their ecosystem. A composable economic system on Solana with deployed smart contracts, reward pipelines, and an automated revenue flywheel. Everything you need to implement real earning infrastructure into your application already exists on-chain.
When you build on EL2, your application implements:
That is the starting point. Use your own token or use $INCOME directly. If you bring your own token, a portion of all activity flows back to buyback and burn $INCOME, while your token gets distributed to the $INCOME staker base. If you use $INCOME as your ecosystem token, the impact is even stronger: more direct burns, more buybacks, and full native access to the infrastructure without separate staking requirements.
$INCOME is the native asset of the economic layer. Builders can use their own token or $INCOME as the ecosystem token for their application. If they use their own token, the relationship is symbiotic: a portion of all activity is used to buyback and burn $INCOME, and they can distribute their token to $INCOME holders for network-wide reach. If they use $INCOME directly as their ecosystem token, the deflationary impact is far greater: more burns, more buybacks, and no separate staking requirement to access the infrastructure. Either way, the more applications that integrate, the more $INCOME is bought back and permanently destroyed.
EL2 is a layered protocol stack built on Solana's Anchor framework. The base layer handles staking and revenue. The identity layer manages accounts and tiers. The application layer provides vaults and governance. All layers are composable via cross-program invocation (CPI).
The foundation. Handles $INCOME staking (tiered APY, time-locks, PDA custody), revenue distribution (atomic 60/25/15 split with Synthetix-style accumulator), and ecosystem reward distribution for partner tokens. This layer is deployed and live on devnet.
On-chain identity for every participant. Tracks tier level, burn contribution, badges, account level, participation score, and full activity history. Other programs read this layer to gate access and weight actions.
Structured earning vaults with tier-gated access, configurable strategies, and reward accumulators. $INCOME-weighted governance where vote power scales with stake and tier. This is where third-party builders integrate.
Off-chain automation that collects ecosystem revenue, swaps it to $INCOME via Jupiter, and deposits it into the revenue distribution contract. This is the engine that keeps the economy self-sustaining.
Every layer reads from the layer below it. Your application sits on top and inherits the full economic stack. You do not need to build staking, revenue sharing, or tier logic. You just use it.
This is the mechanism that makes building on EL2 different from building on any other token ecosystem. Every application that generates revenue and routes it into EL2 makes the entire system stronger.
Every application on EL2 contributes to the deflationary flywheel. A percentage of all fees, revenues, and ecosystem volume generated by your application is used to buy back $INCOME from the open market and permanently destroy it. This is not optional. It is enforced at the protocol level through the revenue share contract. 25% of every revenue deposit is burned atomically in the same transaction. The result: the more successful your application becomes, the more $INCOME supply is destroyed, and the more valuable the remaining tokens become for every participant in the network.
When you build on EL2, your app is not an island. It is part of a compounding economic network. Revenue from your application benefits every staker in the ecosystem, and every other application brings more users and more value to yours. You are building inside an economy where growth directly reduces supply. This is the network effect that single-token projects cannot achieve: aligned economic incentives at the protocol level, enforced by smart contracts, with permanent deflationary consequences.
Builders have two paths. Use your own token alongside $INCOME in a symbiotic dual-token model, or use $INCOME directly as your ecosystem token. If you bring your own token, it powers your product while $INCOME powers the economic layer underneath. A portion of activity flows back to buyback and burn $INCOME, and you distribute your token to the $INCOME community for network-wide reach. If you use $INCOME directly, the benefits are far greater: more burns, more buybacks, deeper integration with the full protocol, and no separate staking requirement to access the infrastructure.
Path A partners onboard through the Partner Registry: they stake $INCOME (locked) to activate their project’s INCOME Node and unlock EL2 SDK access. That locked position earns from the same reward pools as all stakers, with a proportional share matching the commitment, plus exclusive USDi distributions. Smart contracts verify the partner stake before allowing interactions.
Building your own staking, reward distribution, tier system, vault infrastructure, and governance contracts from scratch takes months of development and millions in audit costs. EL2 provides all of this as deployed, tested, composable infrastructure. Your token gets the distribution reach of the entire $INCOME staker base. $INCOME gets the economic activity from your platform's fees and volume, feeding the buyback-and-burn flywheel. Both tokens benefit. Both communities grow. The more products that integrate, the stronger every participant's position becomes.
If you do not need your own token, you can use $INCOME as the native ecosystem token for your application. This is the simplest and most powerful integration path. Path B builders do not need separate locked staking to access the EL2 SDK; your users can still run INCOME Nodes by staking 10M+ $INCOME, earning from the same reward streams as all stakers with a larger proportional share, plus exclusive USDi distributions. Your users interact with $INCOME directly. All staking, rewards, tier-gating, vault mechanics, and governance run natively through the protocol with no additional token integration required.
The benefits of using $INCOME directly are significant:
If you have an existing token or need a separate brand asset, use the symbiotic dual-token model (Path A). Your token powers your product, $INCOME powers the economic layer, and both benefit; expect Partner Registry registration and locked $INCOME staking to activate your partner node and satisfy on-chain verification. If you want the simplest integration, deepest deflationary impact, and full native access to EL2 infrastructure without that partner stake, use $INCOME directly (Path B)—and encourage committed holders to consider INCOME Nodes at 10M+ to lock supply and earn a larger proportional share plus exclusive USDi. Both paths feed the flywheel. Both paths strengthen the network. Path B simply burns more $INCOME.
EL2 provides multiple reward pathways for developers to integrate. Choose the pipeline that fits your application. Whether you use your own token or $INCOME directly, every pipeline feeds the buyback-and-burn flywheel:
Deposit any amount of $INCOME into the distribution contract. It splits atomically: 60% to all stakers proportionally (O(1) complexity, scales to millions of holders), 25% burned, 15% to treasury. Your users earn passively just by staking. One function call.
If using your own token, distribute it to $INCOME stakers proportionally. The ecosystem reward contract reads staked positions and distributes with configurable cooldowns and burn mechanics. If using $INCOME directly, this pipeline is not needed as rewards flow natively through the protocol.
Create structured earning vaults gated by tier level. Deposit tokens, earn rewards over time. Configurable lock periods, capacity limits, and fee structures. Your strategy, powered by EL2 tier infrastructure.
Read a user's Economic Account to check tier level, badges, burn history, and account level. Gate premium features, whitelist spots, or enhanced rewards based on their position in the EL2 economy.
All pipelines work together. A builder can create a vault (C) that requires a minimum tier (D), distributes a partner token (B), and routes a portion of vault fees into the revenue share (A). The SDK handles the complexity.
The GRASS SDK: typed client libraries for every environment. 13 smart contracts, 60+ methods, generated from on chain IDLs with full instruction builders, account deserialization, PDA derivation, and helper methods. The developer toolkit for Universal High Income. Install, connect, build.
SDK packages are being finalized alongside mainnet deployment. The IDLs for all programs are generated and available. Early access for builders integrating before mainnet is available. Reach out via @IncomeSolana2 on X.
EL2 is built for teams implementing real economic infrastructure. The examples below show the dual-token approach (your token + $INCOME). If you use $INCOME directly as your ecosystem token, the integration is even simpler: skip the partner reward calls and every transaction runs natively through the protocol with maximum deflationary impact.
Your neobank can use its own token for loyalty, access, and payments, or use $INCOME directly. EL2 provides the economic infrastructure underneath: staking mechanics, tier systems, reward math, and vault custody. If using your own token, a portion of subscription revenue and platform activity is routed into the $INCOME flywheel where 25% is permanently bought back and burned. You also distribute your token to $INCOME holders for network-wide reach. If using $INCOME directly, all revenue, fees, and activity flows natively through the protocol with even greater deflationary impact.
Your community can use its own token for identity, governance, and rewards, or use $INCOME directly. EL2 provides the economic backbone: tier infrastructure, reward distribution, deflationary mechanics. If using your own token, distribute it to $INCOME holders for instant network reach. A portion of community revenue (merch, events, fees) flows into the flywheel. If using $INCOME directly, all community activity runs natively through the protocol. Both paths benefit: $INCOME gains economic activity and burns.
Your protocol can use its own governance token for strategy decisions, or use $INCOME directly. EL2 provides vault infrastructure, tier-gated access, and reward mechanics. Create structured vaults using EL2 custody and lock systems. Gate access by $INCOME tier: your best strategies go to the most aligned participants. If using your own token, fund vault rewards with it and route a portion of trading fees into the $INCOME flywheel. If using $INCOME directly, all vault activity, trading fees, and rewards run natively with maximum deflationary impact.
$INCOME is the native asset of the EL2 network. Builders can use their own token or $INCOME directly as their ecosystem token. If using their own token, a portion of all activity is used to buyback and burn $INCOME, and they distribute their token to $INCOME holders for network-wide reach. If using $INCOME directly, the deflationary impact is far greater: more burns, more buybacks, and full native access to the infrastructure without separate staking. Either path creates a continuous and sustainable flywheel:
More apps built on EL2 = more revenue flowing through the flywheel
More revenue = more $INCOME bought back from the market
More buybacks = more $INCOME permanently burned
More burns = less supply = every remaining token is worth more
Your token gets distributed to the entire $INCOME staker network
As a builder, you are not replacing your token with $INCOME. You are running them in symbiosis. Your success accelerates the flywheel. The flywheel accelerates the value of your $INCOME holdings. Your token gains the distribution of the entire network. This is the compounding network effect that makes EL2 fundamentally different from building on any other token ecosystem.
For builders that need real-time ecosystem data, EL2 provides REST APIs (live at incomesolana.com/api/), WebSocket feeds for browser-based real-time events, and gRPC streams for high-throughput backend integrations. Supply data, transaction history, pool state, burn metrics, and holder analytics are all available through the SDK or directly via HTTP.
EL2 is designed for builders who want real infrastructure for delivering value and rewards to their holders. Applications can use their own token alongside $INCOME (symbiotic model) or use $INCOME directly as their ecosystem token. Either way, $INCOME powers the economic engine and a percentage of all activity triggers buyback-and-burn. Using $INCOME directly maximizes the deflationary impact.
Every application on EL2 is economically connected to the network. Whether you use your own token or $INCOME directly, a portion of all fees, revenues, and ecosystem volume feeds the buyback-and-burn flywheel. If using your own token, you also distribute it to the $INCOME staker base for network-wide reach. If using $INCOME directly, the deflationary pressure is maximized with no additional integration. Every application that integrates contributes to the permanent reduction of $INCOME supply. Growth is deflationary by design.
Six programs compiled. IDLs generated. Data APIs live. SDK packages in development. EL2 is the infrastructure for how projects deliver value and rewards to their holders. Build with your own token or use $INCOME directly. Every application that integrates feeds the deflationary flywheel.
Early builder access is open. Build on EL2 with your own token or use $INCOME directly. Reach out for integration support, partnership structures, and priority SDK access.