Manka Expands Solana Transaction Landing Through Blockspace by Everstake

TL;DR

• Manka, a Solana infrastructure provider for transaction execution and real-time network data, has integrated with Blockspace by Everstake to expand transaction landing access for its users. 
• Through an adapter integration, Manka routes transactions through the Blockspace validator network and the leader slots of its validators.
• The integration gives Manka access to low-latency Solana network data and transaction routing infrastructure operated by Everstake.

What Does Manka Build?

Manka builds Solana infrastructure for transaction execution and real-time network data. Its stack includes:

• transaction landing,
• SWQoS connectivity,
• direct validator routing,
• ShredStream,
• bundles,
• transaction batches.

Manka helps the trading, dApp and infra provider teams connect closer to the Solana network and reduce the time between signal and execution.

The Manka Tx Landing product sends signed transactions to the leader validator over stake-weighted connections. Applications keep their own signing flow, and Manka provides the submission path over HTTP or gRPC.

What Does the Manka and Blockspace Partnership Include?

The partnership connects Manka’s transaction landing service to Everstake Blockspace through an adapter integration. Manka users gain an additional landing path that reaches Solana leaders through the Blockspace validator network.

Through the integration, Blockspace provides Manka with:

• low-latency Solana network data from Everstake’s validator infrastructure,
• transaction routing to the TPU of validators in the Blockspace network,
• access to the leader slots of Blockspace-network validators.

The Blockspace Relayer/TPU adapter delivers transactions directly to the leader’s TPU within a ~126ms priority window per leader. Manka users keep their existing Manka integration, routing through Blockspace.

What Are Leader Slots on Solana?

The leader schedule assigns slots to validators in proportion to their stake, and each leader produces blocks for 4 consecutive slots.

Solana has no global mempool, so transactions are sent directly to the TPU (Transaction Processing Unit) of the current or upcoming leader. A landing service that connects directly to more leaders can deliver transactions into more of the leader schedule without intermediate hops.

Through Blockspace, Manka reaches the leader slots of validators in the Blockspace network. When one of those validators is the leader, Manka users’ transactions can enter its TPU through the Blockspace adapter.

What Is Transaction Landing?

Transaction landing is the process of delivering a signed transaction to the current leader and getting it included in a block. A Solana transaction can be dropped before execution at 4 points:

• at the validator’s TPU entry, when unstaked traffic is deprioritized behind stake-weighted traffic,
• at the banking stage, when the fee-based scheduler selects other transactions,
• at signing time, when the chain state used to build the transaction is already outdated,
• at expiry, when the transaction’s recent blockhash ages out before inclusion.

Landing services shorten the path to the leader through:

• stake-weighted connections (SWQoS),
• direct routing to the leader validator,
• regional endpoints close to the sender’s infrastructure.

SWQoS reserves 80% of a leader’s TPU connection capacity for staked senders, allocated in proportion to their stake. To count as staked, a sender needs about 1/50,000 of total active stake. 

A returned signature confirms that a service accepted the transaction for delivery. The transaction lands only when a leader includes it in a block, which the sender verifies by checking the signature’s on-chain status.

What Is Everstake Blockspace?

Blockspace is Everstake’s Solana MEV infrastructure for the inbound path — the route a transaction travels before a validator includes it in a block. It addresses the points where transactions are commonly dropped, acting as a two-sided market between validators (supply) and teams that need their transactions to land (demand).

Each Blockspace product offers its own access model, billing, and performance profile. Blockspace includes 4 products:

• ShredStream: raw Solana shreds delivered before slot confirmation.
• Direct Shreds: a dedicated, IP-isolated shred feed.
• SWQoS: stake-weighted priority routing into the validator’s TPU, scoped to whitelisted public keys, with no 15,000 SOL minimum for the customer.
• Relayer/TPU: a pre-leader transaction stream pushed to a gRPC endpoint the customer operates, plus a TPU adapter that delivers winning bundles to the leader within a ~126ms priority window on a pay-on-performance basis.

ShredStream and SWQoS are live in 7 regions:

• Frankfurt,
• Amsterdam,
• New York,
• Tokyo,
• London,
• Dublin,
• Singapore.

Relayer/TPU is live in Frankfurt and New York. Coverage of the Relayer/TPU stream grows as more validators opt in through Blockspace Searcher Connection.

Where Can Teams Start With Blockspace and Manka?

Teams can start with Blockspace in the Blockspace dashboard and with Manka in the Manka dashboard. 

Blockspace Relayer/TPU access is application-based through [email protected] 

FAQ

What does the Manka and Everstake Blockspace partnership do?

The partnership expands transaction landing access for Manka users through Everstake Blockspace. Manka routes transactions through the Blockspace validator network, where the TPU adapter delivers them to the leader within a ~126ms priority window.

Which Blockspace product does Manka integrate with?

Manka integrates with Blockspace through the Relayer/TPU adapter. 

What is a leader slot on Solana?

A leader slot is the window in which one validator is scheduled to produce a Solana block. Blockspace gives Manka access to the leader slots of Blockspace-network validators.

How do teams get access to Blockspace Relayer/TPU?

Blockspace Relayer/TPU access is application-reviewed: