lotus/chain/actors/builtin
Steven Allen 03cd3760bb correctly pick the seal type based on the network version
Of course, we should really just run all of our tests post actors v2.
2021-01-21 15:21:20 -08:00
..
account update imports to v3 2021-01-21 15:21:19 -08:00
cron update imports to v3 2021-01-21 15:21:19 -08:00
init update imports to v3 2021-01-21 15:21:19 -08:00
market update imports to v3 2021-01-21 15:21:19 -08:00
miner correctly pick the seal type based on the network version 2021-01-21 15:21:20 -08:00
multisig update imports to v3 2021-01-21 15:21:19 -08:00
paych update imports to v3 2021-01-21 15:21:19 -08:00
power update imports to v3 2021-01-21 15:21:19 -08:00
reward update imports to v3 2021-01-21 15:21:19 -08:00
verifreg remove abstract map constructor/loader 2021-01-21 15:21:19 -08:00
builtin.go update actor "is" functions for v3 2021-01-21 15:21:19 -08: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.