feat: add miner deposit #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…roject#1368) * chore: upgrade actor bundler to use the latest blockstore We were importing both a v0.1.0 and a v0.2.0 blockstore from the FVM, now we only import the latter. This also upgrades to the latest clap version (FWIW). * chore: upgrade bitfield to use the latest blockstore Apparently, just the bundler wasn't enough.
This makes compilation _much_ faster.
…ject#1291) feat: propegate return data when contract creation fails And clear the return data otherwise.
* replace simple_qa_power with extensible flags * use u32 for SectorOnChainInfoFlags
* chore: update the fvm This doesn't add support for synthetic porep, but splits: filecoin-project#1335 Into two PRs. * finish update * I guess patches aren't enough * fix evm tests We now need to explicitly specify the sha3/ripemd features when testing (it was removed from shared). * fix clippy * switch back to helix master branch so that helix can pass CI again * use released helix crates
* finish update * I guess patches aren't enough * fix evm tests We now need to explicitly specify the sha3/ripemd features when testing (it was removed from shared). * feat: adds support for Synthetic PoRep feat: updates to use latest fvm releases * style: rust fmt * fix: add proper seal proof variant count * fix: apply review feedback * style: rust fmt --------- Co-authored-by: Steven Allen <[email protected]>
…ilecoin-project#1413) alloc expiration_groups after declared_expirations is set
…n-project#1412) * dispatch: make it possible to specify the param/return codec And specify it for two EVM methods that need to pass "reachable" CIDs: 1. The `bytecode` return value. 2. The `invoke_contract_delegate` parameters. * dispatch: auto detect "raw" dispatch Instead of forcing the user to specify `[raw]`, just auto detect it based on the method parameters. * dispatch: test changes * address feedback
avoid recompute quantize_up
* init * avoid recompute current_deadline * treat empty bitfield as all * rm useless quote * add verify * combine option1 & option2 * fix * fix * nit * mod error * nit * fmt * fix ci * fix bug * add test * add more test * partial fix for review * adjust test * use .context_code * fix for test * disallow empty partitions * refactor deadline_available_for_move * fix for clippy * minor opt * only verify_windowed_post once * mod error msg * 1. verify_window_post batch by batch 2. move partitions intact, the `expirations_epochs` and `early_terminated` may have a gap of 24H * fix ci * mod check for epoch * partial review fix * adjust test * refactor with Partition::adjust_for_move * share the language with FIP * deadline_available_for_move => ensure_deadline_available_for_move * add some doc comment * more renaming * more renaming * rename + merge master * mod wording * fix test * renaming in test * apply alex's idea of not re-quantizing at all. * 1. forbid moving when there're early terminations 2. remove `adjust_for_move` * rm anyhow::Ok * minor optimization by observing that partition `faulty_power` should be zero when `faults` is empty * adjust find_sectors_by_expiration for not re-quantizing * add test * fix for review * add a comment about not re-quantizing when moving expirations_epochs * minor optimization * avoid scanning the same range twice * 1. review fix 2. add check for `max_partitions_per_deadline` * fix comment * use with_context_code
…oin-project#1417) The actor has been deleted so the assertions should reflect that. By removing the state from the mock runtime, this change will also let us catch any other testing bugs (and let's us assert that the actor was actually deleted).
…coin-project#1422) * return error data from multisig actor * multisig should return error data back to the user * fix test
…t#1421) use read only send for verifreg balance
…s in the proving deadline cron job (filecoin-project#1427) * cache precommit state * fix clippy
filecoin-project#1432) check all ExpectAggregateVerifySeals fields
…1433) test to handle fault verification errors
* optimise_cron_green_tests * use reward spec quantisation * fix clippy * address review * add test for cron vesting optimisation * test for quantisation * fix clippy * address nit
…ecoin-project#1438) * copy blockstore locally from fvm_ipld_blockstore * put dep in correct section * remove actor blockstore package
* add testcase for dispute after move partition * also dispute the original deadline * refactor ActorHarness::move_partitions * refactor integration test * more review fix
* merge memory and tracking blockstores * change name to memory blockstore
…ilecoin-project#1423) * rename some tests and comments to no longer reference slashed_epoch which will never be observable * port cron tick tests for deal termination * move deal termination tests * modify generate and publish deal to return proposal inline * fix bug when settling payments between between publish and activation * deal termination edge cases * pr review
…ilecoin-project#1441) * hide deals that are asynchronously termianted in get_deal_activation * add test for EX_DEAL_EXPIRED behaviour
* squashed commit to merge built-in Actor events to master
… optional (filecoin-project#1511) * Make Prove{CommitSectors, ReplicaUpdates}3Params aggregate proof type optional. * Enforce no agg proof type when not used
…ilecoin-project#1514) Rename integration test files to match the method names being tested.
Without this it naively serialises using the underlying Rust BigInt representation: [sign,[data,data,...]]
* Move MAX_SECTOR_NUMBER from fvm_shared to runtime/policy * Move Spacetime from fvm_shared to the reward actor * Remove SectorQuality type alias * Move TOTAL_FILECOIN into the market policy * Move network constants into runtime::builtin::network
…ject#1519) * Move reward logic from fvm_shared to the shared runtime * move back import
Unfortunately, I had to duplicate a little bit of code in the market actor, but I think it's better to do that than to put this mostly miner specific logic in, e.g., the runtime.
…ject#1520) * Add market state invariants and fix a mistake in tests. * Fix clippy issues Co-authored-by: Rod Vagg <[email protected]> --------- Co-authored-by: Steven Allen <[email protected]> Co-authored-by: Rod Vagg <[email protected]>
…r checks (filecoin-project#1506) fix: cron_tick to use implicit executions to avoid sender checks when running in fvm the sender is checked for non-implicit executions, which matters when running these in fvm-workbench
…ct#1522) Some of the lints were... kind of 🙄, but it's easier to appease the animated paperclip than to argue with it.
…ntions (filecoin-project#1524) * Update SetMultimap to use Map2 internally and match conventions. * review * feat: remove clone by borrowing --------- Co-authored-by: Steven Allen <[email protected]>
…posit_should_fail_without_construct
…power::ext::miner
tediou5
merged commit 3517745
into
ipfs-force-community:feat/add_miner_deposit_v3
10 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fip: FIP-0077
fip update: FIP-0077 update
discussions: discussions