lotus/chain/actors/builtin
2024-01-17 16:23:12 -08:00
..
account feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
cron feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
datacap feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
evm feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
init feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
market chore: chain/actors: Use type proxies instead of versioned GST imports 2023-08-29 15:28:16 +02:00
miner fix: fill in power-base & replaced-day-reward in state getter 2024-01-17 16:23:12 -08:00
multisig feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
paych Fix/texts (#11298) 2023-10-27 11:32:42 -07:00
power feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
reward feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
system feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02:00
verifreg chore: chain/actors: Use type proxies instead of versioned GST imports 2023-08-29 15:28:16 +02: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 feat: introduce local nv21 skeleton 2023-08-16 20:01:48 +02: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.