builtin

README

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.

Documentation

Index

• Constants
• Variables
• func ActorNameByCode(c cid.Cid) string
• func IsAccountActor(c cid.Cid) bool
• func IsBuiltinActor(c cid.Cid) bool
• func IsMultisigActor(c cid.Cid) bool
• func IsPaymentChannelActor(c cid.Cid) bool
• func IsStorageMinerActor(c cid.Cid) bool
• func Load(store adt.Store, act *types.Actor) (cbor.Marshaler, error)
• func QAPowerForWeight(size abi.SectorSize, duration abi.ChainEpoch, ...) abi.StoragePower
• func RegisterActorState(code cid.Cid, loader ActorStateLoader)
• type ActorStateLoader
• type FilterEstimate
  • func FromV0FilterEstimate(v0 smoothing0.FilterEstimate) FilterEstimate
  • func FromV2FilterEstimate(v2 smoothing2.FilterEstimate) FilterEstimate
  • func FromV3FilterEstimate(v3 smoothing3.FilterEstimate) FilterEstimate
  • func FromV4FilterEstimate(v4 smoothing4.FilterEstimate) FilterEstimate
• type PoStProof
• type SectorInfo

Constants

const (
	EpochDurationSeconds = builtin0.EpochDurationSeconds
	EpochsInDay          = builtin0.EpochsInDay
	SecondsInDay         = builtin0.SecondsInDay
)

const (
	MethodSend        = builtin4.MethodSend
	MethodConstructor = builtin4.MethodConstructor
)

Variables

var ActorStateLoaders = make(map[cid.Cid]ActorStateLoader)

var BurntFundsActorAddr = builtin0.BurntFundsActorAddr

var CronActorAddr = builtin0.CronActorAddr

var (
	ExpectedLeadersPerEpoch = builtin0.ExpectedLeadersPerEpoch
)

var ReserveAddress = makeAddress("t090")

var RootVerifierAddress = makeAddress("t080")

var SaftAddress = makeAddress("t0122")

var SystemActorAddr = builtin0.SystemActorAddr

Functions

func ActorNameByCode

func ActorNameByCode(c cid.Cid) string

func IsAccountActor

func IsAccountActor(c cid.Cid) bool

func IsBuiltinActor

func IsBuiltinActor(c cid.Cid) bool

func IsMultisigActor

func IsMultisigActor(c cid.Cid) bool

func IsPaymentChannelActor

func IsPaymentChannelActor(c cid.Cid) bool

func IsStorageMinerActor

func IsStorageMinerActor(c cid.Cid) bool

func Load

func Load(store adt.Store, act *types.Actor) (cbor.Marshaler, error)

func QAPowerForWeight

func QAPowerForWeight(size abi.SectorSize, duration abi.ChainEpoch, dealWeight, verifiedWeight abi.DealWeight) abi.StoragePower

Doesn't change between actors v0, v2, and v3.

func RegisterActorState

func RegisterActorState(code cid.Cid, loader ActorStateLoader)

Types

type ActorStateLoader

type ActorStateLoader func(store adt.Store, root cid.Cid) (cbor.Marshaler, error)

type FilterEstimate

type FilterEstimate = smoothing0.FilterEstimate

func FromV0FilterEstimate

func FromV0FilterEstimate(v0 smoothing0.FilterEstimate) FilterEstimate

func FromV2FilterEstimate

func FromV2FilterEstimate(v2 smoothing2.FilterEstimate) FilterEstimate

func FromV3FilterEstimate

func FromV3FilterEstimate(v3 smoothing3.FilterEstimate) FilterEstimate

func FromV4FilterEstimate

func FromV4FilterEstimate(v4 smoothing4.FilterEstimate) FilterEstimate

type PoStProof

type PoStProof = proof0.PoStProof

type SectorInfo

type SectorInfo = proof0.SectorInfo

These are all just type aliases across actor versions 0, 2, & 3. In the future, that might change and we might need to do something fancier.