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.

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

Update state machine to use a SectorSet AMT #2888

Closed
ZenGround0 opened this issue Jun 4, 2019 · 3 comments
Closed

Update state machine to use a SectorSet AMT #2888

ZenGround0 opened this issue Jun 4, 2019 · 3 comments

Comments

@ZenGround0
Copy link
Contributor

ZenGround0 commented Jun 4, 2019

Description

After the work begun in #2887 has provided go-filecoin with an AMT-based SectorSet we need to update the miner actor to track its sector storage in this datastructure.

This will make #3007 obsolete.

Acceptance criteria

Use SectorSet instead of golang map in miner actor storage

Risks + pitfalls

Where to begin

Look at how HAMT based storage works. The AMT should be designed similarly enough that hooking up vm blockstorage to the AMT should be straightforward.

@anorth anorth changed the title Update state machine to use a SectorSet Update state machine to use a SectorSet AMT Jul 24, 2019
@anorth
Copy link
Member

anorth commented Jul 24, 2019

This issue is blocked by implementation of the AMT IPLD structure.

A spec for this is happening here: ipld/specs#137

@anorth
Copy link
Member

anorth commented Aug 29, 2019

@whyrusleeping has the initial implementation of AMT here: https://github.com/filecoin-project/go-amt-ipld

cc @hannahhoward while you are investigating HAMT storage layer improvements #3223 #3078. My first glance at the AMT code looks like it has the interface we need to swap in our own storage layer.

@anorth
Copy link
Member

anorth commented Oct 30, 2019

Done (@acruikshank)

@anorth anorth closed this as completed Oct 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants