lotus/chain/actors/builtin
Aayush Rajasekaran 5f1783c9a5 Address review
2021-11-19 15:11:13 -05:00
..
account Integrate v7 actors 2021-11-17 15:55:14 -05:00
cron Integrate v7 actors 2021-11-17 15:55:14 -05:00
init Integrate v7 actors 2021-11-17 15:55:14 -05:00
market Integrate v7 actors 2021-11-17 15:55:14 -05:00
miner Address review 2021-11-19 15:11:13 -05:00
multisig Integrate v7 actors 2021-11-17 15:55:14 -05:00
paych Integrate v7 actors 2021-11-17 15:55:14 -05:00
power Integrate v7 actors 2021-11-17 15:55:14 -05:00
reward Integrate v7 actors 2021-11-17 15:55:14 -05:00
system Integrate v7 actors 2021-11-17 15:55:14 -05:00
verifreg Integrate v7 actors 2021-11-17 15:55:14 -05:00
builtin.go Integrate v7 actors 2021-11-17 15:55:14 -05:00
builtin.go.template Merge master into feat/nv13 2021-05-27 12:28:20 +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.