Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement FIP 0065 #11921

Closed
3 of 9 tasks
ZenGround0 opened this issue Apr 23, 2024 · 1 comment · Fixed by #11976
Closed
3 of 9 tasks

Implement FIP 0065 #11921

ZenGround0 opened this issue Apr 23, 2024 · 1 comment · Fixed by #11976
Assignees
@ZenGround0
Labels
kind/feature Kind: Feature
Milestone
Network v23

Comments

@ZenGround0
Copy link
Contributor

Checklist

  • This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
  • I have a specific, actionable, and well motivated feature request to propose.

Lotus component

  • lotus daemon - chain sync
  • lotus fvm/fevm - Lotus FVM and FEVM interactions
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt/WinningPoSt)
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

FIP 0065 ignoring f05's contribution to locked FIL is accepted.

Describe the solution you'd like

Implement the FIP

Describe alternatives you've considered

No response

Additional context

No response
@ZenGround0 ZenGround0 added the kind/feature Kind: Feature label Apr 23, 2024
@ZenGround0 ZenGround0 self-assigned this Apr 23, 2024
@rjan90 rjan90 added this to the Network v23 milestone Apr 25, 2024
@ZenGround0 ZenGround0 mentioned this issue May 8, 2024
Merged
8 tasks
@rjan90
Copy link
Contributor

rjan90 commented May 8, 2024 •
edited

Is my understanding correct that to test this e2e in a devnet, it would basically be:

  • Spin up a devnet. Check circulating suppy. Spend some larger amount to lock in the built-in market actor. Confirm that the circulating supply is the same before the network upgrade to nv23. Confirm after the network upgrade to nv23, that this amount is subtracted?

Are there any other edge-cases/testing we would want to cover?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ZenGround0 ZenGround0

Labels
kind/feature Kind: Feature
Projects
None yet
Milestone
Network v23
Development

Successfully merging a pull request may close this issue.

feat:state:Ignore market balance after nv23 filecoin-project/lotus
2 participants
@ZenGround0 @rjan90