lotus/chain/actors/builtin
2021-04-27 10:30:33 +02:00
..
account v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
cron v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
init v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
market Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
miner v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
multisig Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
paych v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
power v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
reward v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
verifreg v4 specs-actors integration, nv12 migration 2021-04-27 02:02:44 -04:00
builtin.go Merge tag 'v1.8.0' into release/v1.9.0 2021-04-27 10:30:33 +02:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07: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.