lotus/chain/actors/builtin
2023-11-15 13:06:51 +01:00
..
account fix circleci and fiximports 2023-11-15 13:06:51 +01:00
cron fix circleci and fiximports 2023-11-15 13:06:51 +01:00
datacap fix circleci and fiximports 2023-11-15 13:06:51 +01:00
evm fix circleci and fiximports 2023-11-15 13:06:51 +01:00
init fix circleci and fiximports 2023-11-15 13:06:51 +01:00
market fix circleci and fiximports 2023-11-15 13:06:51 +01:00
miner fix circleci and fiximports 2023-11-15 13:06:51 +01:00
multisig fix circleci and fiximports 2023-11-15 13:06:51 +01:00
paych fix circleci and fiximports 2023-11-15 13:06:51 +01:00
power fix circleci and fiximports 2023-11-15 13:06:51 +01:00
reward fix circleci and fiximports 2023-11-15 13:06:51 +01:00
system fix circleci and fiximports 2023-11-15 13:06:51 +01:00
verifreg fix circleci and fiximports 2023-11-15 13:06:51 +01:00
builtin.go fix circleci and fiximports 2023-11-15 13:06:51 +01:00
builtin.go.template feat: chain: light-weight patch to fix calibrationnet () 2023-10-31 18:29:09 -04:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07:00
registry.go fix circleci and fiximports 2023-11-15 13:06:51 +01:00
registry.go.template NV18: Filecoin EVM runtime + Actor Events + EthAccount + EAM + f4 addressing () 2023-01-13 19:11:13 +00: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.