lotus/chain/actors/builtin
2022-11-22 10:32:26 -08:00
..
account Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
cron Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
datacap Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
evm feat: actors: add the evm to the builtin actors shims (#9672) 2022-11-17 06:55:40 -08:00
init Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
market Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
miner Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
multisig Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
paych Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
power Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
reward Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
system Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
verifreg Merge branch 'master' into feat/nv18 2022-11-22 10:08:54 -08:00
builtin.go fix eth_feeHistory: add missing param. 2022-11-09 19:47:06 +02:00
builtin.go.template Fix discrepancies, run fiximports 2022-09-09 21:40:15 -04:00
embryo.go embryo: simplify code 2022-11-11 05:20:27 +02:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07:00
registry.go make gen 2022-11-09 07:36:09 +02:00
registry.go.template Invoker: Use MethodMeta from go-state-types 2022-10-19 15:53:26 -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.