APEX (Asynchronous Program EXecution) design

[aeyakovenko]

Problem

Fork choice doesn't need to depend on executing of all of the state transitions, and this dependency currently slows down the network when demand spikes.

Summary of Changes

Design proposal that isolates vote program from all the other programs.

Fixes #

tag @carllin @buffalu @jstarry @t-nelson @jackcmay @pgarg66 @sakridge

[t-nelson]

can we wrap at ~80char to ease commenting?

[t-nelson]

seems like a really invasive way to get to "remove consensus messages from the transaction pipeline"?

EDIT: Which I should clearly state that I am generally in support of! Votes and program TXs have too different of constraints to try to balance in the same execution path

[aeyakovenko]

seems like a really invasive way to get to "remove consensus messages from the transaction pipeline"?

I think this is pretty low overhead. The failing txs that mix domains can be done at the tx processor. And the isolation program accounts are the only ones that can move domains and the only ones that keep track of that state.

[buffalu]

what reasons would someone need to move domains? it seems like just transferring SOL to vote accounts?

[aeyakovenko]

@t-nelson I think like NONCEs, this might need to be part of System.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale pull request has been automatically closed. Thank you for your contributions.

[ryoqun]

(seems this is superseded by solana-foundation/solana-improvement-documents#45)