lotus/chain/actors/builtin
2023-03-02 16:38:05 -05:00
..
account Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
cron Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
datacap Update go-state-types 2022-12-14 19:33:47 -05:00
evm fix: eth: return the correct nonce from EthGetTransactionCount 2023-02-17 10:51:42 -08:00
init Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
market Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
miner Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
multisig Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
paych Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
power Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
reward Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
system Drop actor keys from chain/actors/manifest.go 2022-12-13 18:02:34 -05:00
verifreg feat: update renew-sectors with FIP-0045 logic 2023-03-02 16:38:05 -05:00
builtin.go make jen 2023-01-26 16:26:39 +01:00
builtin.go.template make jen 2023-01-26 16:26:39 +01:00
README.md [WIP] Network upgrade support 2020-09-11 20:16:29 -07:00
registry.go NV18: Filecoin EVM runtime + Actor Events + EthAccount + EAM + f4 addressing (#9998) 2023-01-13 19:11:13 +00:00
registry.go.template NV18: Filecoin EVM runtime + Actor Events + EthAccount + EAM + f4 addressing (#9998) 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.