lotus/chain/actors/builtin
Steven Allen ca9448bc11 rename actors v1 -> actors v2
The actual actors version is v2, not v1. Using Version1 internally was really confusing.
2020-09-28 13:13:18 -07:00
..
account rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
init rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
market rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
miner rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
multisig rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
paych rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
power rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
reward rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
verifreg rename actors v1 -> actors v2 2020-09-28 13:13:18 -07:00
builtin.go rename actors v1 -> actors v2 2020-09-28 13:13:18 -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.