3.6 KiB
| simd | title | authors | category | type | status | created | |
|---|---|---|---|---|---|---|---|
| 0047 | Syscall to get the last hardfork |
|
Standard | Core | Draft | 2023-04-15 |
Summary
Create a new syscall which can be used to get the last hard fork slot.
fn sol_get_last_hardfork_slot() -> Slot
Motivation
In Solana, when the cluster cannot reach consensus, it is currently restarted
using ledger-tool with a hard fork on a slot. All participating nodes need to
restart their validator specifying the hard fork slot. Once all nodes
participating in the restart effort on the hard fork exceed 80% of the total
stakes, the restart is successful, and the cluster continues from the hard fork
slot. So hard fork is a tool to intentionally fork off the nodes not
participating in the restart effort.
Dapp developers may find it useful to know that a hard fork has recently occurred. This information can help them prevent arbitrage and liquidation caused by outdated oracle price account states. However, the cluster's restart process takes several hours; in that time, the world can change, causing asset prices to fluctuate. As the cluster updates the state of all accounts, malicious actors could take advantage of the delay by conducting trades using outdated prices, anticipating that they will soon catch up to the actual prices of real-world assets. Knowing that hard fork has been done recently, dapps can manage these cases more appropriately.
Alternatives Considered
No alternate considerations; we need to have the value of last hard fork slot while executing the dapp to correctly treat this case. We cannot have an account because then it should be updated just after the restart is successful, which will add complexity. The best way is to create a new syscall to get this information during execution of transaction, which will help us get last hardfork slot without any interface changes for the instruction.
Detailed Design
Creation of a new syscall
The implementation of this syscall is pretty straitforward. In solana client all the hardforks for a cluster are stored in the bank structure. The last hard fork slot can be retrieved and then stored in invoke context, so that the executing dapp can access it.
For other clients, we have to get the last hard fork slot information and make it accessible to the runtime of the dapp.
Overview of changes for solana client
The hardfork data is available in the Bank. The structure HardForks contains
a vector with all the previous hard forks. The vector is also sorted when we
register a slot. So the last element of the vector is usually the last slot at
which hard fork was done. We can get the last hard fork slot from the bank and
pass it to invoke context structure. We can register new syscall in the file
definitions.rs where other syscalls are defined.
define_syscall!(fn sol_get_last_hardfork_slot() -> Slot);
We can then return the data of last hardfork slot passed to the invoke context in this functions implementation.
Impact
Dapps will start using this new syscall to correctly address the security concerns during network restart. This will increase the reliability of solana cluster as whole and make dapps more confident to handle edge cases during such extreme events.
As the method is syscall the dapp developers do not need to pass any new accounts or sysvars to the instruction to use this feature.
Security Consideration
None
Backwards Compatibility
The dapps using the new syscall could not be used on solana version which does not implement this feature. Existing dapps which do not use this feature are not impacted at all.