# Staking error EIP-1559?

**URL:** https://forum.thegraph.com/t/staking-error-eip-1559/2454
**Category:** Feedback
**Created:** [August 24, 2021, 6:48pm UTC](https://forum.thegraph.com/t/staking-error-eip-1559/2454 "2021-08-24T18:48:17Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![CryptoGuy](https://avatars.discourse-cdn.com/v4/letter/c/df788c/32.png) [@CryptoGuy](https://forum.thegraph.com/u/CryptoGuy)
#### Post date: [August 24, 2021, 6:48pm UTC](https://forum.thegraph.com/t/staking-error-eip-1559/2454/1 "2021-08-24T18:48:17Z")

</div>

Hello Graph community,

My metamask wallet is connected to the site. My ledger wallet is also tethered with the MetaMask and this is where I have the GRT token under the Etherium as and ERC20.

When I proceed to confirm the delegate, MetaMask returns and error:

transaction failure ! Error EIP-1559 not enabled on common

I have no idea what this means, and I am wondering if it has anything to do with the Ledger tethered to MetaMask.

Any help to resolve this would be much appreciated.

cheers,  
Pierre

---

<div class="post-metadata">

### Author: ![indexer\_payne](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/indexer_payne/32/44_2.png) [@indexer\_payne](https://forum.thegraph.com/u/indexer_payne)
#### Post date: [August 24, 2021, 7:14pm UTC](https://forum.thegraph.com/t/staking-error-eip-1559/2454/2 "2021-08-24T19:14:00Z")

</div>

Hey there 🙂

I don’t currently have a Ledger around to test this, but looks like they just recently merged [this PR](https://github.com/LedgerHQ/app-ethereum/pull/157) and you might have to:

- update Ledger Live
- update Ledger Firmware
- update Metamask

---

<div class="post-metadata">

### Author: ![CryptoGuy](https://avatars.discourse-cdn.com/v4/letter/c/df788c/32.png) [@CryptoGuy](https://forum.thegraph.com/u/CryptoGuy)
#### Post date: [August 24, 2021, 10:37pm UTC](https://forum.thegraph.com/t/staking-error-eip-1559/2454/3 "2021-08-24T22:37:11Z")

</div>

Thank you for the link. Looks to be a known issue with a migration path to solve in the next releases.
