lotus/chain/actors/builtin
Steven Allen 87351fa35c move version to actors, from builtin
Otherwise, we're going to end up with an import cycle between the adt and this
version.
2020-09-25 12:49:39 -07:00
..
account Introduce v1 actors 2020-09-25 12:49:39 -07:00
init fixup v1 actors for new methods 2020-09-25 12:49:39 -07:00
market fixup v1 actors for new methods 2020-09-25 12:49:39 -07:00
miner correctly load new actors 2020-09-25 12:49:39 -07:00
multisig fixup v1 actors for new methods 2020-09-25 12:49:39 -07:00
paych fixup v1 actors for new methods 2020-09-25 12:49:39 -07:00
power correctly load new actors 2020-09-25 12:49:39 -07:00
reward fixup v1 actors for new methods 2020-09-25 12:49:39 -07:00
verifreg move version to actors, from builtin 2020-09-25 12:49:39 -07:00
builtin.go move version to actors, from builtin 2020-09-25 12:49:39 -07: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.