-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unknown actor code bafkqaetgnfwc6mrpon2g64tbm5sw22lomvza #5371
Comments
Is there anything update? |
Same issue |
I get this when I run any of the |
Any updates on this? ⨎ lotus sync status |
I'm running into this same scenario with Actor Code Interestingly enough, the I was stack tracing the code (without actually running it), and i wonder if lotus/chain/state/statetree.go Line 121 in 214c32d
|
@Schwartz10 @rjan90 I resolved this by building from source |
@fadyanwar thanks for the tip! I can see the scenarios when rebuilding might solve this issue, but in my scenario, I'm getting this error on the public Glif endpoint. The public Glif node gets rebuilt on every release, so I don't think it will solve it |
So this isn't a bug -- this endpoint is intended only to get the public key address of accounts (secp or bls) from their ID addresses. It's not expected to work on multisigs / miners / payment channels / etc. How much would people like such a method? It wouldn't be hard to write such a method, but it would definitely be slow -- we don't maintain an |
@Schwartz10 indicated there's interest in having such a method -- users that need fast lookup can cache the results, so a slow impl is fine. @geoff-vball Would you be willing to take this on? The work required is:
|
rpc.state_account_key 'f03275'
returns the error:
Error response to Filecoin.StateAccountKey request: 1 failed to get account actor state for f03275: unknown actor code bafkqaetgnfwc6mrpon2g64tbm5sw22lomvza
While reverse works:
rpc.state_lookup_i_d 'f27fxgjifczreumheqdnlhm2esbt2mg5nugcfiyaq', nil
It is unclear how to get public key. address for miner?
The text was updated successfully, but these errors were encountered: