Staked connections with Manablast lite-RPCs

The current Manablast solution is built on the ability to add transactions to a block based on validators that have a stake, rather than those with public connections.

Manablast maintains its own staked connections by reallocating the stake delegated on the platform to partner validators. In turn, these partner validators increase the virtual stake in their node settings for Manablast lite-RPCs nodes.

Thus, when sending a transaction into a block via Manablast Lite-RPC, it enters the network on behalf of a validator-rpc with a large virtual stake. Because partner validators overwrite the virtual stake of our RPC node - making it appear as if it's a staking validator participating in consensus

• If the current leader is one of the partner validators, it’s simple—they just include the transaction in the block.

• If the current leader is any other validator (not a partner), the partner validator forwards the transaction to others, backing it with their own stake. However, since Manablast also delegates its stake to partner validators once the transaction enters their network, this redirection is reinforced by a larger stake—including both the validator’s own stake and the stake delegated from Manablast. As a result, this almost ensures successful transaction inclusion.

Manablast also runs its own validators that receive stake from the platform and directly participate in consensus as part of the partner validator network. For the system to function, the only necessary and sufficient condition is to have at least 1 staked validator in the partner network - which could even be just Manablast's own internal validator