Ecosystem and growth strategy of Tetris DAO and the growth model

The RUBT growth model is a two-perimeter architecture and a partner flywheel: the regulated RUB perimeter provides a predictable on-ramp/off-ramp, while the primary exchange moves into DeFi swaps where the decisive factor becomes RUBT on-chain liquidity depth.

The logic is built on four mutually reinforcing pillars:

• Conversion scales via atomic DeFi swaps; the key metric is depth of RUBT on-chain pools versus major crypto assets.

• Base liquidity is created and retained through POL and the treasury so that pool growth is controlled rather than accidental.

• CeFi partners provide distribution and RUB flows; DeFi partners convert those flows into on-chain volume and real RUBT utility.

• Points and token incentives (TETRIS/veTETRIS, Rebate) function as a partner sales and marketing engine tied to measurable actions: liquidity, volume, and routing.

5.1 RUBT’s competitive “physics”: localized settlement in rubles + on-chain exchanges

RUBT addresses both bottlenecks: a RUB on-ramp/off-ramp aligned with regulation for the client, and reduced dependence on external centralized counterparties through atomic on-chain swaps.

Client advantages (DeFi + Execution Platform):

• Legal certainty of settlement: the Monetary Claim under RUBT is settleable only (i) in RUB, (ii) on an Execution Platform, and (iii) via a request to the Settlement Agent; settlement in another currency/outside Execution Platforms is not provided.

• Reduced counterparty risk in conversion: key exchange is moved into DeFi where a DEX swap is atomic—either it executes fully or it does not execute at all—eliminating the typical risk “the asset has been delivered while the return leg is uncertain.”

• Cost and scalability: RUBT as an ERC-20 asset is compatible with DeFi infrastructure and operates 24/7; total route cost is defined not by manual intermediaries but by on-chain pool depth and efficiency.

5.2 Liquidity depth is built as a controlled protocol asset: POL, partner pools, and the treasury

For liquidity to be predictable and reproducible, the base portion must be owned by the protocol (POL), while pool expansion should be guided by the treasury and partner funding programs rather than relying only on external LPs.

Practical design:

• Protocol-Owned Liquidity (POL): the DAO deploys and holds its own liquidity in key RUBT pairs on DEXs; fees and market activity reinforce the treasury and support stable swap quality.

• Partner liquidity pools: large integrators (CeFi and DeFi) have an economic reason to hold liquidity in RUBT pools via incentive mechanisms and Rebate.

5.3 Partner network scales volume: CeFi brings flow, DeFi turns it into routes and use cases

What scales is not “the token,” but the distribution and routing network: CeFi creates funnels and RUB flows; DeFi turns them into on-chain volume, liquidity, and RUBT utility.

CeFi partnerships as distribution and client acquisition:

• Banks and fintech integrators embed RUBT as an infrastructure conversion route for clients and/or proprietary operations, relying on predictable settlement via Execution Platforms and the Settlement Agent.

• Payment service providers (PSPs) and wallets turn RUBT into a mass conversion layer inside apps where “best route” is determined by RUBT liquidity depth.

• Centralized exchanges and OTC venues provide listings/pairs, large-volume infrastructure, and price visibility; strategically, the focus remains on shifting primary conversion into on-chain pools.

• Execution Platforms and operators of Digital Rights infrastructure provide the regulated perimeter (admission, register/accounting, KYC/AML, RUB settlements) and make RUBT institutionally reproducible.

DeFi partnerships as swap quality and on-chain utility:

• DEX/AMMs and routing aggregators provide base pools, execution, and “best price”; this is where liquidity depth is measured and built.

• Bridges into compatible networks expand RUBT availability while preserving the liquidity core and the same settlement principles for the Monetary Claim in rubles via partner infrastructure.

• Lending and derivatives protocols increase demand for RUBT as collateral, raising organic need for liquidity.

5.4 Points and token incentives as a way to reach critical mass

Incentives are “paying for outcomes” in partner sales: they reduce conversion cost, accelerate liquidity formation, and motivate partners to bring volume.

5.4.1 Points program as controlled marketing tied to actions

Points are awarded for actions that measurably improve RUBT’s market properties: on-chain swaps, adding liquidity, using partner routes, cross-chain operations, and use of the regulated RUB perimeter on Execution Platforms (where applicable under platform rules).

Points act as “marketing receipts”: they convert into TETRIS/veTETRIS after token generation and listing.

5.4.2 veTETRIS and Rebate as a mechanism for partners to compete for volume and liquidity

Holding veTETRIS gives partners the right to a Rebate on fees in RUBT on-chain pools (subject to protocol-level implementation), turning RUBT distribution into a measurable conversion business.

Rebate and partner terms are tied to volume and routing quality (proprietary and client operations), not to “passive holding,” keeping incentives in marketing/partner sales and avoiding any promise of yield on RUBT.

5.4.3 Client-flow attribution makes incentives targeted and auditable

The protocol must reliably link “partner → client flow” at the integration layer: through Managed Wallets and the Execution Platform perimeter, the protocol records the association of users/operations with a given partner.

This allows (i) counting partner volume from client operations, (ii) awarding Rebate and Points in a targeted way, and (iii) making partner terms comparable and governable through Governance.