Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Key management API returns 404 on fee recipient

See original GitHub issue


When calling GET on eth/v1/validator/$__pubkey/feerecipient for a $__pubkey that has no individual recipient set, I get a 404 with message Fee recipient not found

As per it should return the value of --validators-proposer-default-fee-recipient instead

Likewise, a POST gets me Validator public key not found when attempting to set fee recipient.

The keys were imported with the key manager API, they are not “read-only” file system keys

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:10 (6 by maintainers)

github_iconTop GitHub Comments

rolfyonecommented, Aug 22, 2022

I’ve got a similar thing happening with a minor caveat, and I think the ‘caveat’ is the point in time you’re checking…

  • start VC with keymanager, have validator-proposer-default-fee-recipeint
  • add a key to VC, it comes back ‘accepted’
  • request fee recipient: responds 404
  • wait until epoch transition
  • request fee recipient: responds with default fee recipient.

I’m planning on a tiny tweak that should let this work more cleanly, should be up in a few hours barring unexpected issues, but I figured I’d update here so that the scope of the problem is clearer… The first epoch transition after adding a key updates data currently and after that the functions currently released will work. There’s a definite period where they’ll report 404 because they (gas limit, fee recipient) can’t find the key, so they think the key isn’t ours. I’m planning on linking this more closely so that a better decision can be made about which keys we own.

rolfyonecommented, Aug 23, 2022

Fantastic! thanks for the retest, I appreciate it

Read more comments on GitHub >

github_iconTop Results From Across the Web

Is it correct to return 404 when a REST resource is not found?
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410...
Read more >
API Errors & Responses - Braze
The REST API Key you are using does not have sufficient permissions, check the API key permissions in the Braze Developer Console. 404...
Read more >
Recipients API - Honeycomb Documentation
API Keys with the “Manage Recipients” permissions can modify recipients used by ALL environments for a given team. Fields on a Recipient. A...
Read more >
Content Management API | Contentful
If a content type is not activated yet, the API will return a 404 response. An editor interface is created automatically on the...
Read more >
API Overview - SparkPost Developers
Documentation for sending via SMTP or HTTP with the SparkPost API. ... Create and manage your API Keys in the app (EU). We...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found