lotus/chain/actors/builtin
LexLuthr 3f9b6837c9 feat: api: new verified registry methods to get all allocations and claims (#11631)
* new verireg methods

* update changelog and add itest

* update itest and cli

* update new method's support till v9

* remove gateway APIs

* fix cli internal var names
2024-03-22 07:00:28 +01:00
..
account [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
cron [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
datacap [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
evm [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
init [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
market feat: sealing: Support nv22 DDO features in the sealing pipeline (#11226) 2024-03-22 07:00:28 +01:00
miner feat: sealing: Support nv22 DDO features in the sealing pipeline (#11226) 2024-03-22 07:00:28 +01:00
multisig [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
paych [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
power [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
reward [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
system [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
verifreg feat: api: new verified registry methods to get all allocations and claims (#11631) 2024-03-22 07:00:28 +01:00
builtin.go feat: chain: light-weight patch to fix calibrationnet (#11363) 2023-10-31 18:29:09 -04:00
builtin.go.template feat: chain: light-weight patch to fix calibrationnet (#11363) 2023-10-31 18:29:09 -04:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07:00
registry.go [WIP] feat: Add nv22 skeleton 2024-03-22 07:00:28 +01:00
registry.go.template NV18: Filecoin EVM runtime + Actor Events + EthAccount + EAM + f4 addressing (#9998) 2023-01-13 19:11:13 +00:00

Actors

This package contains shims for abstracting over different actor versions.

Design

Shims in this package follow a few common design principles.

Structure Agnostic

Shims interfaces defined in this package should (ideally) not change even if the structure of the underlying data changes. For example:

  • All shims store an internal "store" object. That way, state can be moved into a separate object without needing to add a store to the function signature.
  • All functions must return an error, even if unused for now.

Minimal

These interfaces should be expanded only as necessary to reduce maintenance burden.

Queries, not field assessors.

When possible, functions should query the state instead of simply acting as field assessors. These queries are more likely to remain stable across specs-actor upgrades than specific state fields.

Note: there is a trade-off here. Avoid implementing complicated query logic inside these shims, as it will need to be replicated in every shim.