[RFC] Smart Contracts Engine #420
Assignees
Milestone
Comments
|
@aeyakovenko, can this be closed? |
vkomenda
pushed a commit
to vkomenda/solana
that referenced
this issue
Aug 29, 2021
* Pack instructions and state more efficiently * SwapInfo and SwapInstruction are more memory-efficient, following the example from SPL Token * Remove unnecessary helper structs to make instructions clearer * Error -> SwapError * Update JS tests to reflect the change * Integrate review feedback
godmodegalactus
pushed a commit
to blockworks-foundation/solana
that referenced
this issue
Jan 5, 2024
Use cluster info functions for tpu (solana-labs#345) (solana-labs#347) Use git rev-parse for git sha Remove blacklisted tx from message_hash_to_transaction (Backport solana-labs#374) (solana-labs#376) Updates scripts for easy local setup. (solana-labs#383) Backports sim_bundle improvements (solana-labs#407) backports clone derivation 416 (solana-labs#417) Backport solana-labs#419: add upsert to AccountOverrides (solana-labs#420) backports solana-labs#430 v1.16: update jito-programs sha (solana-labs#431) [JIT-1661] Faster Autosnapshot (solana-labs#406) Fix Buildkite warnings (solana-labs#437) Backport solana-labs#446 to v1.16 (solana-labs#447) backport 428, runtime plugin (solana-labs#429) v1.16: Backport solana-labs#449 (solana-labs#450)
brooksprumo
pushed a commit
to brooksprumo/solana
that referenced
this issue
Apr 8, 2024
…sary. (solana-labs#420) * Find the bank hash of the heaviest fork, replay if necessary. * Make it more explicit how heaviest fork slot is selected. * Use process_single_slot instead of process_blockstore_from_root, the latter may re-insert banks already frozen. * Put BlockstoreProcessError into the error message. * Check that all existing blocks link to correct parent before replay. * Use the default number of threads instead. * Check whether block is full and other small fixes. * Fix root_bank and move comments to function level. * Remove the extra parent link check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RFC is here
Please comment!
@rob-solana I would love some feedback from you and @bhk. basically, we have a
callinterface that takes a bunch of PubKeys and for some proofs of ownership. This translates into memory regions that are loaded into the call. I think the proofs of ownership can be treated like a privset. But, any memory that is owned by the contract should be Writable, and in theory, all memory can be Readable. The call should then be able to make subsequent calls with the subset of the privset.I think we should mark the caller, as in the call was initiated by the owner of this public key, and the contract itself should be able to asynchronously schedule other calls either as itself, or as the current caller.
Example is here
Merged PRs (for doc only):
#489
#439
#428
#423
#419
#396
The text was updated successfully, but these errors were encountered: