2023-07-05 13:50:11 +00:00
|
|
|
# nimbus-eth1
|
2024-02-29 21:10:24 +00:00
|
|
|
# Copyright (c) 2023-2024 Status Research & Development GmbH
|
2023-07-05 13:50:11 +00:00
|
|
|
# Licensed under either of
|
|
|
|
|
# * Apache License, version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or
|
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0)
|
|
|
|
|
# * MIT license ([LICENSE-MIT](LICENSE-MIT) or
|
|
|
|
|
# http://opensource.org/licenses/MIT)
|
|
|
|
|
# at your option. This file may not be copied, modified, or distributed
|
|
|
|
|
# except according to those terms.
|
|
|
|
|
|
|
|
|
|
## Aristo DB -- Standard interface
|
|
|
|
|
## ===============================
|
|
|
|
|
##
|
|
|
|
|
{.push raises: [].}
|
|
|
|
|
|
2023-09-26 09:21:13 +00:00
|
|
|
import
|
2024-10-09 07:44:15 +00:00
|
|
|
aristo/[aristo_api, aristo_constants]
|
2023-09-26 09:21:13 +00:00
|
|
|
export
|
2024-10-09 07:44:15 +00:00
|
|
|
aristo_api, aristo_constants
|
2023-09-26 09:21:13 +00:00
|
|
|
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
import
|
2024-02-29 21:10:24 +00:00
|
|
|
aristo/aristo_init
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
export
|
2024-02-29 21:10:24 +00:00
|
|
|
MemBackendRef,
|
|
|
|
|
VoidBackendRef,
|
2024-07-03 15:50:27 +00:00
|
|
|
finish,
|
2024-02-29 21:10:24 +00:00
|
|
|
init
|
Core db and aristo updates for destructor and tx logic (#1894)
* Disable `TransactionID` related functions from `state_db.nim`
why:
Functions `getCommittedStorage()` and `updateOriginalRoot()` from
the `state_db` module are nowhere used. The emulation of a legacy
`TransactionID` type functionality is administratively expensive to
provide by `Aristo` (the legacy DB version is only partially
implemented, anyway).
As there is no other place where `TransactionID`s are used, they will
not be provided by the `Aristo` variant of the `CoreDb`. For the
legacy DB API, nothing will change.
* Fix copyright headers in source code
* Get rid of compiler warning
* Update Aristo code, remove unused `merge()` variant, export `hashify()`
why:
Adapt to upcoming `CoreDb` wrapper
* Remove synced tx feature from `Aristo`
why:
+ This feature allowed to synchronise transaction methods like begin,
commit, and rollback for a group of descriptors.
+ The feature is over engineered and not needed for `CoreDb`, neither
is it complete (some convergence features missing.)
* Add debugging helpers to `Kvt`
also:
Update database iterator, add count variable yield argument similar
to `Aristo`.
* Provide optional destructors for `CoreDb` API
why;
For the upcoming Aristo wrapper, this allows to control when certain
smart destruction and update can take place. The auto destructor works
fine in general when the storage/cache strategy is known and acceptable
when creating descriptors.
* Add update option for `CoreDb` API function `hash()`
why;
The hash function is typically used to get the state root of the MPT.
Due to lazy hashing, this might be not available on the `Aristo` DB.
So the `update` function asks for re-hashing the gurrent state changes
if needed.
* Update API tracking log mode: `info` => `debug
* Use shared `Kvt` descriptor in new Ledger API
why:
No need to create a new descriptor all the time
2023-11-16 19:35:03 +00:00
|
|
|
|
2023-10-27 21:36:51 +00:00
|
|
|
import
|
2024-02-29 21:10:24 +00:00
|
|
|
aristo/aristo_nearby
|
2023-10-27 21:36:51 +00:00
|
|
|
export
|
2024-02-29 21:10:24 +00:00
|
|
|
leftPairs, # iterators
|
2024-06-27 09:01:26 +00:00
|
|
|
rightPairs,
|
|
|
|
|
rightPairsAccount,
|
|
|
|
|
rightPairsStorage
|
2023-10-27 21:36:51 +00:00
|
|
|
|
2024-02-29 21:10:24 +00:00
|
|
|
import
|
|
|
|
|
aristo/aristo_desc/[desc_identifiers, desc_structural]
|
2023-08-07 17:45:23 +00:00
|
|
|
export
|
2023-08-10 20:01:28 +00:00
|
|
|
AristoAccount,
|
2023-09-18 20:20:28 +00:00
|
|
|
desc_identifiers,
|
2023-08-10 20:01:28 +00:00
|
|
|
`==`
|
2023-07-05 13:50:11 +00:00
|
|
|
|
2023-08-07 17:45:23 +00:00
|
|
|
import
|
|
|
|
|
aristo/aristo_desc
|
2023-07-05 13:50:11 +00:00
|
|
|
export
|
|
|
|
|
AristoDbRef,
|
|
|
|
|
AristoError,
|
2023-09-18 20:20:28 +00:00
|
|
|
AristoTxRef,
|
2023-08-07 17:45:23 +00:00
|
|
|
isValid
|
2023-07-05 13:50:11 +00:00
|
|
|
|
|
|
|
|
# End
|
