-
Notifications
You must be signed in to change notification settings - Fork 224
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
4351: Transactions on JSON-RPC server r=Fraser999 a=Fraser999 This PR upgrades the JSON-RPC server to handle `Transaction`s while leaving the legacy `Deploy` interface unchanged. The new RPCs are `account_put_transaction` and `info_get_transaction` with similar behaviour and semantics as `account_put_deploy` and `info_get_deploy` respectively. The speculative execution server was also updated, with a new endpoint `speculative_exec_txn` taking a `Transaction` while leaving the original `speculative_exec` unchanged. This PR also includes an attempt to unify the approaches to handling versioned data in storage. I extended the notion of the `VersionedDatabases` to try and make the usage of these less accident-prone, making the actual DBs private and exposing methods which ensure old, pre-existing data in the `legacy` DB is exclusively using legacy types and bincode encoding, while new data is held in the `current` DB and uses bytesrepr-encoding of the keys and values. In doing this, most of the methods in `storage/write_block.rs` were deleted, so I moved the couple of remaining methods back into `storage.rs` and deleted that file. I also moved the `Config` and `Event` types unchanged to their own files to try and declutter storage.rs a little. Closes [roadmap#185](casper-network/roadmap#185). Co-authored-by: Fraser Hutchison <fraser@casperlabs.io>
- Loading branch information
Showing
33 changed files
with
3,039 additions
and
1,471 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.