lotus/chain/actors/builtin
zenground0 d6aa17e21f Snap Deals Integration
- FSM handles the actual cc upgrade process including error states
- PoSting (winning and window) works over upgraded and upgrading sectors
- Integration test and changes to itest framework to reduce flakes
- Update CLI to handle new upgrade
- Update dependencies
2022-01-14 17:14:32 -05:00
..
account Integrate v7 actors 2022-01-14 17:14:32 -05:00
cron Integrate v7 actors 2022-01-14 17:14:32 -05:00
init Integrate v7 actors 2022-01-14 17:14:32 -05:00
market Integrate v7 actors 2022-01-14 17:14:32 -05:00
miner Snap Deals Integration 2022-01-14 17:14:32 -05:00
multisig Integrate v7 actors 2022-01-14 17:14:32 -05:00
paych Integrate v7 actors 2022-01-14 17:14:32 -05:00
power Integrate v7 actors 2022-01-14 17:14:32 -05:00
reward Integrate v7 actors 2022-01-14 17:14:32 -05:00
system Integrate v7 actors 2022-01-14 17:14:32 -05:00
verifreg Integrate v7 actors 2022-01-14 17:14:32 -05:00
builtin.go Snap Deals Integration 2022-01-14 17:14:32 -05:00
builtin.go.template Snap Deals Integration 2022-01-14 17:14:32 -05: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.