lotus/chain/actors/builtin
2022-10-13 16:38:30 -04:00
..
account Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
cron Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
datacap review fixes 2022-10-07 00:25:08 -04:00
init Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
market use NoAllocationID instead of nil AllocationId 2022-10-12 13:54:04 -04:00
miner Fix miner state precommit info 2022-10-13 16:38:30 -04:00
multisig more fixes 2022-09-10 12:37:03 -04:00
paych Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
power Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
reward Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
system more fixes 2022-09-09 21:40:15 -04:00
verifreg revert change to verifreg util 2022-10-13 13:33:22 -04:00
builtin.go Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
builtin.go.template Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07:00
registry.go Add datacap actor to registry.go 2022-10-12 15:54:36 -04:00
registry.go.template Add datacap actor to registry.go 2022-10-12 15:54:36 -04: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.