Integration Boost

Introduction

The Integration Boost Primitive is a demand-side stablecoin mechanism defined under Section A.2.2.8.2 of the Sky Atlas that incentivizes DeFi protocol partners to hold USDS within their smart contracts by paying them the equivalent of the Sky Savings Rate on their unrewarded USDS balances ^[1]. Unlike the Distribution Reward Primitive — which pays a fixed 0.2% annualized fee to integrators based on Reward Codes — the Integration Boost compensates partners at the full SSR rate (approximately 4% as of February 2026), making it a substantially larger financial incentive ^[2] ^[3].

The Laniakea framework defines Integration Boost as a "mechanism to apply SSR yield to naked USDS held in smart contracts without using sUSDS" ^[36]. This framing is significant: rather than treating the Integration Boost as a growth incentive or marketing expense, Laniakea's accounting framework classifies it as a cost of capital — the same category as the DSR and SSR ^[37]. In FY 2025, the combined Savings category (DSR + SSR + Integration Boost) totaled approximately $194 million out of $285 million in total expenses, representing roughly 68% of all protocol spending ^[37]. This classification reflects a core economic insight: paying the SSR to a protocol holding naked USDS is economically equivalent to running the savings rate itself. The Integration Boost is not a subsidy — it is the price Sky Protocol pays to make USDS competitive as a reserve asset.

The mechanism addresses a specific gap in Sky Protocol's incentive architecture: protocols that hold raw USDS in their smart contracts — rather than converting it to sUSDS — earn no yield by default ^[36]. This creates a disincentive for DeFi platforms to integrate USDS, since holding a non-yielding stablecoin represents an opportunity cost compared to alternatives like USDC or yield-bearing tokens. The Integration Boost eliminates this gap by providing SSR-equivalent payments directly to partner protocols, enabling USDS to earn yield in three specific contexts where sUSDS is impractical: protocols that need to hold raw USDS for liquidity or specific contract logic, integrations where wrapping and unwrapping sUSDS adds friction or gas costs, and smart contracts that cannot easily integrate ERC-4626 vaults ^[36].

As of February 2026, the Integration Boost program operates across Ethereum, Base, and Solana, with weekly payment distributions to qualifying partners funded through governance-approved budget allocations ^[6]. The expectation is that Integration Boost partners will pass these payments through to their end users, though partners are under no obligation to do so ^[10]. Together with the Distribution Reward Primitive, the Integration Boost forms one half of Sky Protocol's two-pronged demand-side stablecoin strategy — the Distribution Reward incentivizes integrator platforms at a modest fixed rate, while the Integration Boost provides substantial SSR-equivalent yield to protocol smart contracts holding raw USDS ^[26].

How Integration Boost Works

The Integration Boost system operates through a cycle of balance monitoring, time-weighted reward calculation, and weekly payment distribution. The mechanism connects Sky Protocol's treasury with partner DeFi protocols through an off-chain calculation system backed by on-chain data verification. At a high level, the process resembles a payroll cycle: the system continuously monitors how much USDS each partner holds throughout the week, computes an average, and issues a payment based on that average multiplied by the prevailing savings rate.

Integration Boost Partners

Integration Boost partners are DeFi protocols that allow users to deposit USDS balances within their smart contracts ^[1]. Sky Protocol makes payments to these partners equal to the Sky Savings Rate multiplied by the unrewarded USDS balances held in their protocol ^[1]. The term "unrewarded" is significant — it refers to USDS that is not already earning yield through sUSDS conversion, the Sky Token Rewards module, or Agent holdings ^[4] ^[36]. This distinction prevents double-counting: USDS that is already earning through one of these mechanisms is excluded from Integration Boost calculations.

Partners are part of the broader Integrator Program defined under A.2.2.8.1.2.1.1, sharing the same onboarding framework as Distribution Reward participants ^[11]. Current and onboarding integrators are recorded in the Sky Atlas and maintained by the operational governance function ^[11].

A critical design choice is that Integration Boost partners have no obligation to pass through any portion of Integration Boost payments to their users ^[10]. Nevertheless, the Atlas notes that the expectation is that most partners will pass through payments to remain competitive with other protocols offering yield on stablecoin deposits ^[10]. This voluntary pass-through model balances partner flexibility with market-driven incentive alignment — competitive pressure among DeFi protocols effectively enforces pass-through without requiring contractual mandates.

Balance Tracking and Reward Calculation

The calculation engine continuously monitors on-chain transfer events for each partner's contract addresses ^[6]. Every time USDS moves into or out of a partner's smart contract, the system records the new balance and the timestamp at which the change occurred. At the end of each reporting week (Monday through Sunday), the system calculates a time-weighted average balance — multiplying each recorded balance by the number of seconds it persisted before the next change, summing those products, and dividing by the total seconds in the week ^[6]:

Time-Weighted Balance = Σ (Balance × Δt) / Seconds in Period

This approach captures the true average USDS held throughout the period rather than relying on a point-in-time snapshot, which could be gamed by temporarily increasing balances before measurement. The time-weighted balance is then multiplied by the SSR, pro-rated for the week, to determine the payment amount.

Balance data must be verifiable using on-chain data ^[12]. In the near term, the Core Council Risk Advisor (Block Analitica) calculates net deposit data and makes it available through API endpoints for Ethereum and Solana ^[12]. Data is submitted on a weekly basis, with payment the following Monday ^[13]. Failure to submit data on time results in delayed payment until the following week — there is no retroactive accelerated payment for late submissions ^[13].

The monitoring infrastructure operates on a 30-minute cron cycle across three independent pipelines: SSR rate monitoring (tracking rate changes on the sUSDS farm contract), EVM Transfer event collection for Ethereum and Base partners, and Solana Transfer event collection ^[6]. Event collection differs by blockchain architecture — on EVM chains, the system uses standard event indexing for efficient Transfer event retrieval, while on Solana, the system must retrieve all transaction signatures for monitored addresses and iterate them in reverse order, a less efficient process due to Solana's architectural differences ^[6].

Rate Change Handling

When the Sky Savings Rate changes during a reporting period (as determined by monitoring File events on the sUSDS farm contract), the calculation automatically splits at the block where the change occurred ^[6]. The old rate applies to the time-weighted balance accumulated before the change, and the new rate applies to the balance after. This ensures that neither the partner nor Sky Protocol is penalized or windfall-benefited by rate adjustments — each second of the reporting period is priced at the rate that was actually in effect.

Spark Treasury Component

The Spark Protocol receives a modified Integration Boost with distinct parameters ^[6]:

Payment Frequency — Monthly rather than weekly
Rate Calculation — Uses an annualized SSR formula: Annualized SSR = 365 × (e^(ln(1 + SSR) / 365) - 1)
Additional Rate — A fixed 0.6% annual rate was added on top of the annualized SSR, valid through end of 2025 ^[6]

As of February 2026, the 0.6% Spark premium has expired according to its original terms ^[6]. The Spark Treasury rate now equals the annualized SSR without the additional premium. This elevated rate had reflected Spark's position as Sky Protocol's largest Star and its critical role in deploying USDS across DeFi lending markets during the program's initial scaling phase.

Distribution Reward Interaction

Net USDS balances in a DeFi protocol receiving Integration Boost are also eligible for the Distribution Reward ^[15]. The tracking methodology used for Integration Boost balance reporting serves as a valid tracking methodology for Distribution Reward purposes as well ^[16]. However, the no-double-payment rule applies: Distribution Rewards may only be paid on balances where a Distribution Reward is not already being paid ^[17]. Prime Agents may choose whether to share Distribution Reward payments with Integration Boost partners ^[18].

Bonus Incentive Layer

Beyond the formula-driven SSR reward, partners may receive discretionary flat bonus amounts configured through governance ^[6]. These bonus incentives stack with the standard SSR-based calculation, allowing Sky Protocol to provide additional compensation to strategically important partners without modifying the base rate mechanism. A partner might receive the standard SSR reward on its time-weighted USDS balance plus a fixed weekly bonus — creating a two-tier incentive structure where the base reward scales automatically with TVL and rate changes while the bonus provides targeted flexibility for governance to adjust partner economics as competitive conditions shift.

Non-USDS Token Coverage

The Integration Boost is not limited to partners holding native USDS. When a partner's monitored smart contract holds a token other than USDS — such as a wrapped variant or a liquidity pool token — the system automatically converts the position to a USDS-equivalent value using historical price data before applying the reward calculation ^[6]. This extension enables the Integration Boost to reach liquidity pools, vaults, and other DeFi primitives where USDS is present in a transformed or paired form, broadening the program's reach beyond simple custody arrangements.

Operational Safeguards

The monitoring and calculation infrastructure includes several safeguards that ensure payment accuracy and program flexibility ^[6]:

Disabled periods — Partners can be temporarily excluded from receiving rewards during specified date ranges, such as during contract migrations, security reviews, or dispute resolution. The system continues tracking their on-chain balances for record-keeping even when payments are paused, allowing seamless resumption when the exclusion period ends.
Automatic retry logic — Failed data collection jobs are automatically retried up to three times before requiring manual intervention, ensuring that transient blockchain node issues or network congestion do not result in missed balance snapshots.
Data retention policy — Raw blockchain transfer events are retained for two months after processing, providing a sufficient audit window for dispute resolution while keeping database overhead manageable. Calculated incentive records are retained indefinitely.

Role in Sky's Architecture

The Integration Boost occupies a distinctive position within Sky Protocol's broader economic architecture. Rather than functioning as a discretionary growth program, it is structurally embedded in the protocol's capital allocation framework — treated by the Laniakea design as economically equivalent to the savings rate itself.

Cost of Capital Classification

Laniakea's accounting framework categorizes all protocol expenses into four buckets: Operations (governance and team costs), Rewards (ecosystem participation incentives), Savings (yield paid to attract and retain USDS supply), and Staking (value distribution from buyback proceeds) ^[37]. The Integration Boost falls squarely into the Savings category alongside the DSR and SSR — classified as a cost of capital that scales with USDS supply and the savings rate spread, not with headcount or operational complexity ^[37].

This classification has practical implications for evaluating the program. When Sky Protocol spent approximately $194 million on Savings in FY 2025 — roughly 68% of its $285 million total expenses — the Integration Boost was part of that figure as a structural cost of maintaining USDS's competitiveness as a reserve asset, not a discretionary marketing budget that governance could easily eliminate ^[37]. By contrast, operational expenses (spells, vests, council buffers) totaled approximately $67 million and have been declining as legacy overhead winds down ^[37]. The distinction matters: cutting the Integration Boost would be equivalent to cutting the savings rate — it would reduce USDS's attractiveness to DeFi protocols and likely trigger capital outflows.

Institutional Ownership Under Launch 3

Within Sky's Star agent hierarchy, the Integration Boost is institutionally assigned to Launch 3, one of the five genesis Prime Agents ^[38]. The Synome — Laniakea's description of Sky's organizational DNA — identifies Launch 3 as the Prime focused on "distribution rewards, integration boosts" ^[38]. While other Stars can deploy the Integration Boost Primitive through the standard Instance Invocation process, Launch 3 bears primary institutional responsibility for the program's strategy and operational execution.

This assignment places Integration Boost alongside the Distribution Reward under a single Prime's mandate, enabling coordinated demand-side strategy. Spark, Keel, and Grove each operate Integration Boost instances for their respective partner ecosystems, but Launch 3's oversight role ensures consistent standards across all deployments.

Pioneer System Interaction

The Integration Boost intersects directly with the Pioneer Chain Primitive — Laniakea's mechanism for incentivizing USDS adoption on new blockchain networks ^[36]. Under the Pioneer System, Pioneer Stars earn SSR-equivalent rewards on "unrewarded USDS" bridged to their Pioneer Chains. Crucially, the definition of "unrewarded" excludes USDS that is already earning yield through three mechanisms: sUSDS conversion, Integration Boost payments, or Agent holdings ^[36].

This creates a structural interaction between the two primitives. When a Pioneer Star like Keel deploys Integration Boost on Solana, the USDS receiving Integration Boost payments becomes "rewarded" — reducing the pool of unrewarded USDS that feeds into Pioneer Reward calculations. In effect, Integration Boost and Pioneer Rewards are substitutes at the balance level: each dollar of USDS can earn through one mechanism or the other, but not both. Pioneer Stars therefore face a strategic choice when designing their chain's incentive mix — whether to pursue broad Pioneer Rewards on unrewarded USDS or targeted Integration Boost partnerships with specific DeFi protocols.

Position in the Capital Framework

A critical architectural distinction in Laniakea's design is that the Integration Boost is not a risk-capital position. The capital formula that governs Prime Agent balance sheets — calculating required reserves as the sum of position capital plus category cap penalties — does not apply to Integration Boost payments ^[42]. Primes' lending positions, credit facilities, and collateral exposures all require risk capital reserves proportional to their duration-matched and unmatched exposure under the SPTP framework. Integration Boost payments, by contrast, require only operational budget — they create no balance sheet risk for the protocol and are not subject to risk capital ingression curves that govern how new capital positions are recognized and scaled ^[43].

This means Integration Boost costs flow through the Monthly Settlement Cycle as recurring protocol expenses, paid from operational flows before any loss absorption mechanisms are invoked. The loss absorption waterfall — progressing from Backstop Capital through SKY token inflation, Genesis Capital haircuts, and ultimately USDS peg adjustment — exists to absorb credit losses on the asset side of the protocol's balance sheet ^[44]. Integration Boost spending never reaches this waterfall because it is settled as an operational cost within the normal settlement process, not as a realized loss on a risk position ^[45]. The expanded seven-step waterfall in Laniakea's Guardian framework adds SKY Token Inflation, Genesis Capital Backstop, and USDS Peg Adjustment as nuclear options beyond the initial backstop layers — none of which interact with Integration Boost's cost-of-capital flows ^[45].

The practical implication is that scaling the Integration Boost program does not increase the protocol's capital requirements or reduce its loss-absorbing capacity. When governance approves additional Integration Boost funding, it is authorizing an increase in recurring operating expenditure — not taking on additional financial risk that requires corresponding capital reserves. This contrasts sharply with Primes' lending activities, where each new credit position must be supported by proportional risk capital recognized through the ingression process ^[43].

Transition to Operational GovOps

Both the Atlas and Laniakea describe a near-term to long-term transition in how the Integration Boost is administered ^[21]. Currently, the Core Council Risk Advisor (Block Analitica) calculates balances, and Support Facilitators execute payments from dedicated wallets ^[14] ^[19]. In the long-term design, Operational GovOps assumes both calculation and payment responsibility, disbursing from its Buffer and receiving reimbursement through the Monthly Settlement Cycle ^[21]. This transition reduces Sky Core's direct operational involvement and aligns with Laniakea's broader vision of delegating execution to specialized Operational Executor Agents.

Historical Context

The Integration Boost Primitive addresses a challenge that became apparent during the transition from MakerDAO to Sky Protocol. In the MakerDAO era, DAI held within DeFi protocols earned no yield unless the protocol specifically converted it to sDAI through the DAI Savings Rate mechanism. Many DeFi protocols — particularly lending markets, decentralized exchanges, and liquidity pools — held substantial DAI balances in raw form within their smart contracts, either because they lacked ERC-4626 integration capabilities or because the gas costs and complexity of continuous sDAI conversion outweighed the yield benefits ^[5].

This structural inefficiency meant that a significant portion of circulating DAI was "unrewarded" — generating no yield for holders while simultaneously not contributing to the protocol's peg stability through the savings rate mechanism. When the September 2024 rebrand introduced the Sky Primitives framework, the Integration Boost was formalized as a dedicated solution to this problem: rather than requiring every DeFi protocol to implement sUSDS vault integration, Sky Protocol would directly compensate protocols for the yield gap on their raw USDS holdings ^[1] ^[26].

The program became operationally active in late 2024, coinciding with Sky Protocol's cross-chain expansion to Solana ^[23]. The Solana deployment provided a natural test case for the Integration Boost, since Solana-native DeFi protocols had no prior relationship with USDS and required strong financial incentives to justify integration engineering work. The initial Solana incentive program — allocating up to 500,000 USDS weekly across Kamino, Drift, Save Finance, and Jito — demonstrated the Integration Boost's role as a market-entry tool, not just a yield-gap mechanism ^[23].

The Integration Boost's governance profile grew rapidly through early 2025. Between January and March 2025, five separate executive votes allocated over 11.5 million USDS to the program, establishing it as one of Sky Protocol's most active budget categories ^[7] ^[8] ^[39] ^[9] ^[20]. The AEP-8 proposal in February 2025 — which sought to redirect Integration Boost spending entirely toward cross-chain adoption use cases, pulling funds away from Ethereum-native partners — triggered the first significant governance debate about the program's strategic focus ^[29]. The proposal was ultimately rejected, confirming that governance views the Integration Boost as a multi-chain program rather than exclusively a cross-chain growth tool ^[29].

The program's most significant partner disruption occurred in December 2025, when Aave governance voted with 99.5% approval to remove USDS as collateral across all Aave instances, raising its reserve factor to 25% and removing it from e-Mode ^[40]. The stated rationale was that USDS generated negligible revenue for Aave while introducing asymmetric risks from the USDS issuance model ^[40]. This unwinding of the Sky Aave Force partnership — once the flagship Ethereum Integration Boost relationship — illustrated the limits of incentive-based partnerships when the underlying risk-reward calculus shifts for the partner protocol.

Operational Framework

The Integration Boost Primitive follows the same three-phase operational lifecycle as other Sky Primitives: Global Activation, Instance Invocation, and Ongoing Management. Each phase is defined in detail within the Sky Atlas and reflects the broader agent-based architecture that governs all Prime operations.

Global Activation

A Prime Agent intending to deploy the Integration Boost Primitive must first globally activate it through the Powerhouse interface, setting the Primitive Hub Document's Global Activation Status to "Activated" ^[30]. Unlike some primitives, the Integration Boost has no time-based or document-update triggers for activation — it requires explicit agent action ^[31]. Activation is subject to constraints defined in the general primitive lifecycle rules at A.2.2.1.2.4 ^[32]. Notably, Grove's Integration Boost Primitive status is currently listed as "Inactive," meaning Grove cannot onboard new Integration Boost partners without a separate activation governance action ^[30].

Instance Invocation

After Global Activation, adding a new Integration Boost partner follows a six-step sequential process: Initial Opportunity Identification and Planning, Operational GovOps Review, Artifact Update Draft, Operational Facilitator Review, Off-Chain Vote, and Artifact Update ^[33]. Each step must complete before the next begins, ensuring that new partner onboarding receives appropriate operational and governance scrutiny. During the planning phase, the Prime Agent estimates the Distribution Reward earnings the partnership would generate versus the cost of funding SSR payouts — effectively building a business case for the integration ^[33].

Ongoing Management

Active Integration Boost instances are managed through three protocols ^[34]:

Routine Protocol — The standard cycle of balance calculation by Operational GovOps, payment distribution, and Sky Core reimbursement through the Settlement Cycle
Non-Routine Protocol — Handles parameter changes, partner disputes, and other operational adjustments outside the normal cycle
Emergency Protocol — Defines procedures for urgent situations including partner misconduct, security incidents, or governance-mandated immediate parameter changes

The cadence for Integration Boost distribution is configurable, with three options: weekly, biweekly, or monthly ^[35]. Most partners currently operate on a weekly cycle, with the notable exception of Spark Treasury's monthly payments ^[6]. An Agent Artifact may run multiple simultaneous Integration Boost instances — one for each partner or market — without requiring a Multi-Instance Coordinator Document, since instances operate independently of each other ^[34].

Treasury Management and Funding

The Integration Boost program is funded through governance-approved USDS allocations transferred to dedicated wallets. This funding process has been one of the most active recurring governance actions in Sky Protocol's executive vote calendar, reflecting the program's position as a structural cost of capital rather than a one-time expenditure.

Funding Wallets

In the near term, Support Facilitators directly pay Integration Boost recipients from dedicated wallets ^[19]. The wallet balance on Ethereum mainnet may be topped up to 3 million USDS, though total balances across all blockchains may exceed that amount ^[19]. The wallet addresses are:

Chain	Address	Type
Ethereum	`0xD6891d1DFFDA6B0B1aF3524018a1eE2E608785F7`	Primary
Solana	`7Gf8AqAtmYkkVhQbbJr18RxVUuoGjA8ZEw3Af4NauyaY`	Primary
Solana	`BKT2JR5wRWsXQBxrht1LbbbKtgUkz3sJdaBY8UzgRJPL`	Hot Wallet

All funding transfers are subject to Executive Vote approval, with the standard 16-hour Governance Security Module delay between approval and execution ^[19].

Governance Funding History

Multiple executive votes have allocated USDS to the Integration Boost program since early 2025:

Date	Amount	Executive Vote Description
January 23, 2025	2.5M USDS	Integration Boost Funding ^[7]
February 6, 2025	3M USDS	Integration Boost Funding ^[8]
February 21, 2025	—	Integration Boost Funding (included in broader vote) ^[20]
March 6, 2025	3M USDS	Integration Boost Funding ^[39]
March 20, 2025	3M USDS	Integration Boost Top-Up ^[9]

The total documented funding through March 2025 alone exceeds 11.5 million USDS ^[7] ^[8] ^[39] ^[9]. The recurring nature of these allocations — appearing in nearly every monthly executive vote cycle — reflects the program's classification as a cost of capital that scales with USDS supply and the SSR spread. As of February 2026, Integration Boost top-ups continue to appear as a recurring line item in the governance calendar, with recent atlas edits adding new Integration Boost instances to the Skybase Artifact ^[9].

Long-Term Process

In the long-term design, Operational GovOps calculates the Integration Boost for each cadence occurrence, pays the recipient from its Buffer, and Sky Core subsequently reimburses the Operational Agent Buffer as part of the Monthly Settlement Cycle ^[21]. This architecture minimizes Sky Core's direct role in payment execution and emphasizes the Operational Executor Agent's primary role in implementing Sky Primitives ^[21].

Payment Error Resolution

If previous Integration Boost calculations are discovered to have been erroneous, the Sky Atlas specifies a clear resolution process: underpayments are resolved retroactively, while overpayments require the Prime Agent associated with the integrator to reimburse Sky, using future Integration Boost payments to recover the difference ^[22].

Partner Ecosystem

The Integration Boost program supports partners across multiple blockchains, with different Stars managing their respective chain ecosystems. The partner landscape has evolved significantly since the program's launch, with some partnerships deepening while others have been unwound.

Solana Partners

Sky Protocol's Solana expansion, launched in late 2024 through the SkyLink bridge infrastructure, was accompanied by significant Integration Boost allocations to bootstrap USDS liquidity on the chain ^[23]. As of early 2025, Solana-focused incentives included:

Kamino Finance — 200,000 USDS weekly for USDC/USDS liquidity pools plus 100,000 USDS weekly for stablecoin suppliers ^[23]
Drift Protocol — 100,000 USDS weekly ^[23]
Save Finance — 400,000 USDS monthly ^[23]
Jito — 5,000 USDS weekly for USDS/SOL pairs ^[23]

The total Solana weekly incentive budget reached approximately 500,000 USDS ^[23]. A notable structural detail is the Grove Partner on Solana: this is an artificial partner monitored through an Ethereum bridge contract, whose final reward equals the total Grove Integration Boost budget minus the sum of all other active Solana partner rewards — effectively a residual sweep mechanism that captures unallocated incentive budget ^[6].

Partners can be excluded from rewards during specified intervals through a disabledPeriods configuration ^[6]. For standard EVM partners, disabled periods result in zero rewards. For Solana, disabled partner rewards are not subtracted from the Grove Partner calculation, preventing penalization of the residual partner for excluded participants ^[6].

Ethereum and Base Partners

On Ethereum, the most significant Integration Boost relationship was with Aave through the Sky Aave Force initiative, launched on September 18, 2024 ^[24]. This partnership included a 3.33 million SPK monthly airdrop for sUSDS supplies on Aave V3, a 100 million debt ceiling for USDS in the Aave Lido Market, and a revenue-sharing arrangement where Aave and Spark split all revenue from sUSDS/USDS markets equally ^[24].

However, in December 2025, Aave governance voted with 99.5% approval to remove USDS as collateral across all Aave instances, citing negligible revenue generation and asymmetric risk from the USDS issuance model ^[40]. This decision effectively unwound the Ethereum-side Integration Boost relationship with Aave. Sky founder Rune Christensen attributed the dispute to misunderstandings and pointed to future improvements — including the Data Hub, Grove, and Sentinel Network — as a path to re-engagement ^[40].

Base deployments extend the Integration Boost to Layer 2 partners such as Euler, accessing USDS through SkyLink bridge infrastructure ^[6].

Relationship to Keel

Keel, Sky Protocol's Solana-focused Star, plays a strategic role in the Integration Boost ecosystem. As the Prime Agent responsible for Solana-based USDS distribution, Keel's operational activities intersect with Integration Boost payments flowing to Solana DeFi protocols ^[25]. The $2.5 billion USDS authorization granted to Keel supports the broader liquidity infrastructure that Integration Boost partners rely on for their Solana deployments ^[25]. In December 2025, Keel launched Season 1 of the Tokenization Regatta — a $500 million RWA initiative on Solana — further expanding the ecosystem of protocols that may benefit from Integration Boost incentives ^[25].

Comparison: Integration Boost vs Distribution Reward

The Integration Boost and Distribution Reward are both demand-side stablecoin primitives within the Sky Primitives framework, but they serve distinct purposes and operate with different economic models. Under Laniakea's agent architecture, both are classified as Rewards Primitives available to Prime Agents, and both fall under Launch 3's institutional mandate ^[38].

Feature	Integration Boost	Distribution Reward
Atlas Section	A.2.2.8.2	A.2.2.8.1
Rate	SSR (≈4% as of Feb 2026)	0.2% annualized (standard); +0.3% boosted rate available from Jan 2026
Target	DeFi protocol smart contracts	Integrator platforms (frontends)
Payment Frequency	Weekly (monthly for Spark)	Monthly
Purpose	Compensate for unrewarded USDS	Reward distribution activity
Pass-Through	Expected but not required	Paid to integrator directly
Balance Tracking	On-chain Transfer events	Reward Code system
Administrator	Core Council Risk Advisor	Viridian Advisors
Laniakea Classification	Cost of capital (Savings)	Growth expense (Rewards)

The fundamental distinction is economic: the Integration Boost replaces the yield that USDS would earn if it were converted to sUSDS, while the Distribution Reward provides a separate, additive fee for facilitating USDS access ^[1] ^[3]. A partner protocol can receive both simultaneously — the Integration Boost on its unrewarded USDS balances and the Distribution Reward on the same balances through its Reward Code — creating a layered incentive structure where protocol-level yield (Integration Boost) stacks with distribution-level fees (Distribution Reward) ^[15].

Laniakea's accounting framework reinforces this distinction: Integration Boost sits in the Savings category (cost of capital), while Distribution Rewards sit in the Rewards category (growth expense) ^[37]. This means the Integration Boost scales mechanically with USDS supply and the SSR spread — as supply grows or the rate increases, so does Integration Boost spending — whereas Distribution Rewards are a fixed-rate program unaffected by savings rate changes.

Current State

As of February 2026, the Integration Boost Primitive operates across three blockchains — Ethereum, Base, and Solana — with weekly payment distributions to active partners ^[6]. The Sky Savings Rate stands at approximately 4% as of February 2026 ^[3]. The Spark Treasury 0.6% premium, which was valid through end of 2025, has expired; Spark now receives the standard annualized SSR rate on a monthly cadence ^[6].

The partner landscape has shifted notably. The Aave partnership — once the flagship Ethereum Integration Boost relationship — was unwound in December 2025 following Aave governance's decision to remove USDS as collateral ^[40]. Conversely, the Solana ecosystem has matured through Keel's expanded mandate and the continued operation of Kamino, Drift, Save Finance, and other Integration Boost recipients ^[25]. The Sky Frontier Foundation projected USDS supply reaching $20.6–21 billion in 2026 with $611.5 million in gross protocol revenue, figures that imply continued scaling of Integration Boost spending as a cost-of-capital line item ^[41].

The operational infrastructure has matured since the program's initial deployment. Balance monitoring runs on 30-minute cron cycles across three independent pipelines, with automatic retry logic for failed jobs ^[6]. The Block Analitica API provides the primary data verification layer ^[12], and the Sky ecosystem dashboard at info.sky.money provides real-time supply and backing data ^[28]. The Sky Fusion dashboard at fusion.sky.money provides public visibility into Integration Boost spending alongside other protocol operational expenses ^[27].

The program's continued evolution will depend on governance decisions about budget allocation, strategic focus across chains, and the long-term transition toward the Operational GovOps-managed settlement process ^[21]. The February 2026 atlas edit cycle included new Integration Boost instances being added to the Skybase Artifact, indicating ongoing program expansion ^[9].

Distribution Rewards — Companion demand-side primitive paying integrators 0.2% on qualifying balances
Sky Primitives — The modular framework containing both Integration Boost and Distribution Reward
USDS — The stablecoin whose adoption Integration Boost incentivizes
sUSDS — The yield-bearing token that makes Integration Boost unnecessary when used
Sky Savings Rate — The rate used to calculate Integration Boost payments
Sky Token Rewards — Complementary user-side reward mechanism
Spark — Largest Integration Boost recipient via the Spark Treasury component
Keel — Solana-focused Star supporting Integration Boost partner infrastructure
SkyLink — Cross-chain infrastructure enabling multi-chain Integration Boost
Sky Stars — Prime Agents that deploy the Integration Boost Primitive
Pioneer Chain Primitive — Pioneer System whose "unrewarded USDS" definition interacts with Integration Boost
Grove — Star operating the Solana residual partner and PSM liquidity operations
Laniakea — The forward-looking protocol design that classifies Integration Boost as cost of capital