chore(fees): add initial fees & migration testing (FIP-0100)#12942
chore(fees): add initial fees & migration testing (FIP-0100)#12942rvagg merged 2 commits intorvagg/calibnet-cs-adjustfrom
Conversation
69ad783 to
28e6193
Compare
09aa600 to
5fb2d67
Compare
5fb2d67 to
71f9107
Compare
28e6193 to
33c6ba5
Compare
71f9107 to
7d4c10f
Compare
33c6ba5 to
17ef76e
Compare
7d4c10f to
0901fd1
Compare
17ef76e to
9d65e33
Compare
6380873 to
77baaa1
Compare
|
Calling this ready for review. Still depends on the calibnet (etc.) CS fix @ #12938 but this is exercising the fees.
Limitations:
|
7333de9 to
4d4b1e5
Compare
|
Awesome work @rvagg !
Which (if any) of these do you think we should get in before calling this done? I'm assuming "nv24 sectors being extended in nv25 and attracting a fee" would be the most valuable addition given that is a top concern area for existing SPs. |
3ebed51 to
2315284
Compare
|
@Stebalien or @ZenGround0 : will you be able to look at this today (2025-03-13) so @rvagg can incorporate feedback and get this merged by end of the week? |
|
Test fix in #12950. |
Stebalien
left a comment
There was a problem hiding this comment.
Some nits but this seems reasonable. It would also be nice if we could run the invariants checks in the test, just to make sure they're sane.
|
(all those review items addressed in latest commit btw) |
FIP-0100 fees migration test. Still some more to add here and I'm stacking up PRs a little. This one is on top of #12938 which sets up circulating supply.
This PR uses UnmanagedMiner and has some changes I'd like to get merged regardless of FIP-0100's status. Currently we're testing onboarding different kinds of sectors while in nv24, then hitting the upgrade and snapping into CC sectors and checking fees. Also need to add new sectors post-nv25 and probably an extension or two. I also still haven't figured out how to test actual fee deduction in a reliable way, and it would also be good to do that with the BR cap too if I can figure out how to manage that as well.