Solana co-founder Anatoly Yakovenko has sparked a debate over what truly belongs to the Solana ecosystem, arguing that projects operating outside the blockchain’s main network should be treated as independent platforms. His comments followed a public disagreement with BULK, a decentralized trading platform preparing to expand across multiple blockchain networks.
The discussion began on October 29, 2026, after BULK founder kdot outlined plans to introduce multichain trading infrastructure that would allow users to access shared markets using funds from different blockchains.
While BULK believes its new approach will improve trading efficiency and accessibility, Yakovenko maintains that projects relying on separate execution networks should not be considered applications running directly on Solana.
The disagreement highlights a broader challenge facing blockchain developers: whether to prioritize a single high-performance network or build infrastructure that connects multiple ecosystems.
Solana Co-Founder Questions Projects Operating Outside Layer 1
In an October 29 post on X, Anatoly Yakovenko explained his position on applications that operate outside Solana’s layer-1 blockchain.
According to Yakovenko, projects using independent execution infrastructure function as separate networks, even if they maintain connections with Solana.
His comments followed BULK’s decision to develop a trading system capable of handling transactions and collateral across several blockchains.
Yakovenko has consistently supported the idea that Solana’s base layer should be capable of handling demanding applications without requiring separate scaling networks.
He believes developers should focus on improving the main blockchain rather than moving essential operations to independent systems.
However, this perspective differs from the approach taken by projects that prioritize specialized infrastructure for high-frequency trading or other demanding financial applications.
The discussion has raised questions about how blockchain ecosystems should define applications that use their technology but operate independently.
BULK Announces Plans for Multichain Trading Expansion
BULK is a decentralized trading platform focused on perpetual futures and high-performance trading infrastructure.
The project was initially associated closely with Solana, but its founders are now pursuing a broader multichain strategy.
BULK founder kdot explained that the platform requires its own execution environment to support the speed and reliability demanded by active traders.
The system includes a specialized order book, matching engine, and risk-management infrastructure.
These components are designed to process trading activity while continuously monitoring positions, collateral, and margin requirements.
According to kdot, the objective is to provide a trading experience that does not require customers to move all their assets onto one specific blockchain before accessing the platform.
Instead, BULK wants users to deposit collateral through different supported networks while trading through a shared market infrastructure.
This approach could make the platform more accessible to traders who already hold assets across multiple blockchain ecosystems.
However, the company has not announced a confirmed launch date for its additional blockchain integrations.
How BULK’s Multichain Trading System Would Work
BULK’s proposed architecture aims to combine collateral from different blockchain networks within a single trading environment.
At present, the platform says its collateral is held on Solana, while its internal ledger tracks user balances, open positions, and margin requirements.
The planned expansion would connect additional blockchain networks, including:
- Arc
- Tempo
- Arbitrum
- HyperEVM
Under this model, customers could deposit funds from a supported blockchain and use them as collateral for trading through BULK’s shared order book.
For example, a trader could deposit collateral through Solana, execute positions on BULK, and later withdraw available funds through HyperEVM.
Each supported network would continue to handle its own deposit confirmations and settlement requirements.
The trading platform would manage execution, account balances, and risk calculations through its specialized infrastructure.
BULK argues that this model could reduce unnecessary steps for users while allowing traders from different blockchain networks to access the same markets.
A shared liquidity system could also help avoid dividing traders into separate markets based on where their assets are stored.
Nevertheless, the effectiveness of the proposed system will depend on its technical implementation, security controls, and available liquidity.
Why BULK Wants Its Own Trading Infrastructure
High-frequency derivatives trading places significant demands on blockchain technology.
Trading platforms must process orders quickly while managing collateral, margin balances, and liquidation risks.
For perpetual futures exchanges, these requirements become particularly important because prices and trader positions can change rapidly.
BULK’s founders believe a specialized execution environment is necessary to deliver the performance they want.
Rather than relying entirely on Solana’s main blockchain for every part of the trading process, the project has developed infrastructure tailored to its specific trading requirements.
Kdot has argued that customers care primarily about execution quality, liquidity, and the ability to access markets conveniently.
From that perspective, requiring users to transfer funds through several blockchain networks before trading creates additional friction.
The company’s multichain strategy is intended to simplify that process while keeping trading activity within a common system.
However, operating separate infrastructure can also introduce additional technical dependencies and security considerations.
The disagreement with Yakovenko reflects these competing priorities between blockchain simplicity and specialized application performance.
Yakovenko Responds to BULK Founder Over Investment Ties
The public discussion became more personal when BULK founder kdot pointed out that Yakovenko was an investor in the project.
Kdot referenced Yakovenko’s position on BULK’s capitalization table, questioning why an investor would criticize the company’s technical direction.
Yakovenko acknowledged the distinction between supporting a founding team and agreeing with every decision that team makes.
He made clear that he did not want BULK to fail, even though he disagreed with its approach to blockchain infrastructure.
The Solana co-founder emphasized that his own priorities remained focused on products operating directly on Solana.
He also referenced projects such as Bullet and Backpack while explaining his position.
The exchange illustrated how investors and founders can hold different views about the technical direction of a cryptocurrency project.
Kdot subsequently acknowledged that founders must make decisions based on the needs of their products and customers.
Despite their disagreement, the discussion did not indicate that Yakovenko had withdrawn his investment or ended his support for BULK’s founding team.
Solana Layer-1 vs Multichain Infrastructure Debate
The disagreement between Yakovenko and BULK reflects a larger debate about blockchain scalability.
Solana is designed as a high-performance layer-1 blockchain capable of supporting decentralized applications directly on its main network.
Yakovenko has previously questioned the need for separate layer-2 scaling solutions when an optimized base blockchain can handle significant transaction activity.
In March 2025, he argued that additional scaling layers can introduce unnecessary complexity, including separate security assumptions and operational challenges.
Supporters of specialized infrastructure take a different view.
They argue that certain applications, particularly high-frequency trading platforms, may benefit from execution systems designed specifically for their requirements.
These systems can prioritize factors such as order-matching speed, continuous risk monitoring, and consistent trading performance.
The trade-off involves balancing performance improvements against the complexity of operating infrastructure outside the main blockchain.
For users, the practical differences may include transaction costs, security arrangements, liquidity access, and the steps required to move funds between systems.
Neither approach automatically guarantees better outcomes in every situation, as the appropriate architecture depends on the application’s requirements.
BULK Moves Beyond Its Original Solana-Focused Strategy
BULK’s latest plans represent a shift from how its founders described the project earlier in 2026.
During a January 22 interview on Solana’s Lightspeed podcast, kdot and co-founder Jun Bug discussed their goal of building a high-performance perpetual futures exchange associated with the Solana ecosystem.
The conversation included challenges related to network latency, reliability, and execution performance.
Since then, the project has moved toward describing itself as a specialized trading layer-1 network.
Its execution and risk-management infrastructure are intended to operate independently while connecting to other supported blockchain networks for collateral access.
This change reflects BULK’s ambition to serve traders across multiple ecosystems rather than relying exclusively on Solana-based customers.
The planned architecture could also allow the platform to reach users who enter cryptocurrency markets through wallets, financial technology applications, and other digital payment services.
However, the additional integrations remain proposed, and the company has not provided a deployment timetable.
Is BULK Truly Multichain or Just Adding Deposit Options?
Another question raised during the discussion was whether BULK’s proposed expansion represents full multichain trading or simply broader support for deposits and withdrawals.
A participant known as defido questioned how much of the platform’s trading activity would actually operate across different blockchain networks.
Kdot rejected the suggestion that the changes were limited to additional funding routes.
He explained that BULK’s shared clearing and margin system is central to its proposed architecture.
Under the model, traders would access common markets regardless of the blockchain used to deposit collateral.
This differs from operating separate exchanges on multiple networks, each with independent order books and liquidity.
Instead, BULK wants to maintain one trading environment that can accept funds from several blockchain ecosystems.
Whether this structure delivers the promised benefits will depend on the eventual implementation and how effectively it handles deposits, withdrawals, liquidations, and settlement across networks.
What Does the Debate Mean for the Solana Ecosystem?
The discussion comes as Solana continues to support a growing range of decentralized financial applications.
Projects such as Phantom, Jupiter, Kamino, and Pump.fun have become significant parts of the network’s broader application ecosystem.
Yakovenko has previously emphasized the importance of optimizing Solana for applications that generate substantial user activity.
His comments suggest a preference for keeping important application functions directly connected to the main blockchain.
For developers, however, the decision to build on a single network or use specialized infrastructure often depends on technical and commercial requirements.
Some projects may prioritize direct access to Solana’s existing users and liquidity.
Others may seek greater flexibility by building infrastructure that can connect several blockchain networks.
The BULK disagreement highlights how these decisions can create different interpretations of what it means to belong to a blockchain ecosystem.
It also raises questions about how independent execution networks should be categorized when they rely on existing blockchains for some services but not others.
What’s Next for BULK and Solana?
BULK intends to continue developing its multichain trading infrastructure and connect additional blockchain networks to its shared execution environment.
The project has not yet announced when support for Arc, Tempo, Arbitrum, or HyperEVM will become available.
Further technical details will be important for evaluating how the system manages collateral, network connections, risk controls, and liquidity.
Meanwhile, Yakovenko’s comments reinforce his position that applications operating outside Solana’s main blockchain should be treated as independent networks.
For the Solana ecosystem, the broader discussion is likely to remain relevant as developers explore different approaches to scalability and decentralized financial infrastructure.
The eventual performance of BULK’s trading system could provide a practical example of how specialized execution networks compare with applications operating directly on a high-performance layer-1 blockchain.
Conclusion
Solana co-founder Anatoly Yakovenko’s disagreement with BULK founder kdot has brought renewed attention to the distinction between applications running on a blockchain and platforms that maintain independent execution infrastructure.
Yakovenko believes projects operating outside Solana’s layer-1 network should be considered separate systems.
BULK, meanwhile, argues that its multichain strategy is necessary to improve trading performance, liquidity access, and customer convenience.
Although the two sides disagree on technical priorities, both are focused on developing blockchain infrastructure that can support demanding financial applications.
The bottom line: The debate between Solana and BULK highlights an ongoing question in decentralized finance: should trading platforms rely directly on established layer-1 networks, or build specialized systems that connect multiple blockchains? BULK’s planned expansion may offer further evidence as its infrastructure develops.

















































