b46258d0bf
- Event keys are now t1, t2, t3, t4 for topics; and d for data. - ref-fvm no longer stores events in the blockstore for us. It just returns events to the client, who is now responsible for handling them as it wishes / according to its configuration. - Add a flag to VMOpts to have the events AMT be written in the blockstore. - Add a flag to the ChainStore to advertise to the rest of the system if the ChainStore is storing events. - Enable that flag if the EthRPC is enabled (can also add an explicit configuration flag if wanted). |
||
|---|---|---|
| .. | ||
| pack.sh | ||
| README.md | ||
| v8.tar.zst | ||
| v9.tar.zst | ||
| v10.tar.zst | ||
Bundles
This directory includes the actors bundles for each release. Each actor bundle is a zstd compressed tarfile containing one bundle per network type. These tarfiles are subsequently embedded in the lotus binary.
Updating
To update, run the ./pack.sh script. For example, the following will pack the builtin actors release dev/20220602 into the v8 tarfile.
./pack.sh v8 dev/20220602
This will:
- Download the actors bundles and pack them into the appropriate tarfile (
$VERSION.tar.zst). - Run
make bundle-genin the top-level directory to regenerate the bundle metadata file for all network versions (all*.tar.zstfiles in this directory).
Overriding
To build a bundle, but specify a different release/tag for a specific network, append $network=$alternative_release on the command line. For example:
./pack.sh v8 dev/20220602 mainnet=v8.0.0 calibrationnet=v8.0.0-rc.1