Article
If it’s not on the L1, it’s not on solana and it’s on its own L1, and that’s why I am a pita about supporting anything that’s not directly on the solana L1
X account: If it’s not on the L1, it’s not on solana and it’s on its own L1, and that’s why I am a pita about supporting anything that’s not directly on the solana L1
X account @toly stated that projects not directly located on Solana L1 belong to their own L1, and therefore he maintains a strict stance on supporting such projects.
Key points
If it’s not on the L1, it’s not on solana and it’s on its own L1, and that’s why I am a pita about supporting anything that’s not directly on the solana L1
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
SOL: This statement emphasizes a preference for projects deployed directly on Solana L1, which may affect ecosystem participants' expectations regarding the scope of support, but does not disclose actual funding, product, or governance measures.
Why it matters to readers
This is a direct statement by X account @toly, confirming the content expressed; however, it is a personal position on ecosystem architecture and support standards, and does not provide specific projects, policies, or business actions.
Focus:SOL. Observation period: medium term
Risks and unknowns
- @toly or Solana related teams announce specific support policies or implementation measures for non-native L1 projects
- Whether affected projects respond regarding deployment architecture or partnership arrangements
- SOL Conditions that could reverse the impact assessment: If specific supported or excluded projects, funding arrangements, or protocol-layer changes are subsequently announced, the assessment of its actual impact may change.
Related Developments
Loading event timeline…