builtin-actors
builtin-actors copied to clipboard
filecoin-project
The Filecoin built-in actors
Currently, we "skip" bad inputs, but we should really be rejecting messages that specify completely invalid inputs: - sector numbers that exceed the maximum. - impossible deadlines. - etc.
`expect_query_network_info` currently has magic numbers for reward and power levels. These should be moved to the `setup` function (with a harness) like it is in the original golang code.
The `success_with_multiple_miners_and_multiple_confirmed_sectors_and_assert_expected_power` test depends explicitly on the order of hashed miner ids. This is fragile and should be changed to accept any valid order of results.
## Context https://github.com/filecoin-project/specs-actors has the very useful feature of being able to generate standardised [test vectors](https://github.com/filecoin-project/test-vectors) from its integration tests. builtin-actors is missing this feature, which makes us have to...
To improve type safety of using `Cid` fields in `State` like [here](https://github.com/filecoin-project/builtin-actors/blob/v8.0.0/actors/market/src/state.rs#L29), we just merged a PR in the fork Alfonso's fork for Hierarchical Subnet Coordinator Actors: https://github.com/adlrocha/builtin-actors/pull/8 The PR...
The values we are using here do not necessarily refer to **networks**. Instead, they refer to well-known/named configurations, or presets.
Currently, we build actors with `strip = true`. Instead, we should compile with debug info, then split it into a separate "bundle".
The specs-actors project has a rich backlog of potential improvements to the built-in actors and supporting code. We should migrate a relevant set of those issues over to this project....
This automates the creation of GitHub releases and associated GitHub tags based on the changes to the version in the root Cargo.toml file. The automation uses the same principles as...
## Done Criteria There is a tutorial(s) for doing builtin-actor development and getting those changes into Lotus. Since this focuses on getting changes into Lotus, the docs probably belong in...
