lotus/chain/actors/builtin
2022-06-06 23:23:32 -04:00
..
account Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
cron Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
init Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
market Merge branch 'release/v1.15.3' into jen/mergev1153to16 2022-05-31 16:33:18 -04:00
miner Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
multisig Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
paych Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
power Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
reward Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
system Implement function to access state of system actor 2022-06-06 23:23:32 -04:00
verifreg Use new go-state-types accessors 2022-05-17 15:21:27 -04:00
builtin.go Address review 2022-05-17 15:52:59 -04:00
builtin.go.template Address review 2022-05-17 15:52:59 -04: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.