You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
We talk about the "runtime" in the contracts engine RFC, but it's not in a module or a struct of its own. It's some set of Bank methods acting on a subset of Bank state. Without that separation, it'll be difficult to ask others to scrutinize that mission-critical code.
Proposed solution:
Split the bank. execute_and_commit_transactions() everything it calls to a new runtime.rs module.
execute_and_commit_transactions(), as previously proposed, might be too much for runtime.rs. Instead, only execute_transaction() looks useful on its own. A client could use it to test their transactions and then assume ACID when submitting those same transactions to a Solana cluster.
garious
added a commit
to garious/solana
that referenced
this issue
Nov 24, 2018
Problem:
We talk about the "runtime" in the contracts engine RFC, but it's not in a module or a struct of its own. It's some set of Bank methods acting on a subset of Bank state. Without that separation, it'll be difficult to ask others to scrutinize that mission-critical code.
Proposed solution:
Split the bank.
execute_and_commit_transactions()
everything it calls to a new runtime.rs module.Depends on #1529
The text was updated successfully, but these errors were encountered: