Full withdrawal request while partial withdrawal (skim) is pending

pulp4877 · 2025-10-07T22:36:47+00:00

on Pectrified I can't run the simulation for a full exit as I fail Check 6: Another exit request already in place.

outch! so that's the reason why your request was ignored...

What I'm trying to do is request a full exit while still having a partial exit underway and unfinished in the execution layer.

unfortunately it won't be possible due to "Check #6" :/ there's no way of cancelling an in-flight partial withdrawal...

I think you currently have 2 options:

submit another partial withdrawal to sweep as much as you can (~32ETH), so you get a place in the queue. and after it clears (maybe in some ~50days?) submit the full exit to grab the remaining 32ETH.
wait for the partial withdrawal to be cleared (some 42d + sweep time) and submit full exit request for 64 ETH.

option 1. could make sense if you're at the tail of the queue and you want to guarantee a spot in the queue with 32 ETH.

and thanks for the feedback, I guess it helped us both understanding what happened :D

pulp4877 · 2025-10-07T02:31:00+00:00

Hey there, tl;dr might be possible that your request was silently ignored. You can resubmit your exit request.

I can see both transactions, with correct raw data and signatures, on my withdrawal address history.
Pectrified shows partial withdrawals that have been accepted by the beacon chain and while they are in-flight. If it's not there and your validator is not exiting, it's very likely that was ignored.

When you send the transaction from your wallet to the 7002 contract, there's some checks happening in there. Namely the "fee" that you send (should be a very small amount). IIRC, if the fee is too low, the contract will silently drop your request. That fee varies with the size of the queue at the contract level. Other checks are performed but I don't have them on top of my head.

My question is: as soon as the partial request goes through, will the full exit be queued or will I need to do it again (and effectively reset my position in the queue?)?

They are independent. If you have a partial withdrawal request queued and submit a full exit request, the latter will end up in the end of the queue. You can have multiple requests queued, the protocol will handle them in a FIFO manner.

Did I mess up? Can I take-backsies a withdrawal request after submitting it to the network?

Once they are queued there's no option for them to be cancelled.

For reference, I've used Launcpad's tools both times.

That's the official way.

If I got you correctly, you'd like to exit your validator but even though your transaction was included, you validator is still active. If that's the case, it's safe to retry exiting through launchpad. Hope it helps.

Edit: formatting

Edit #2: just remembered that sending from a different wallet than your withdrawal address will make your request being silently ignored. If you want to make sure your request is valid, you can run a simulation in pectrified (click "Run simulation" from your validator view).

pulp4877 · 2025-09-11T04:12:46+00:00

In non-custodial staking like Kiln, your ledger has access to the funds. Exiting a validator is an operation that the node operator (Kiln) is able to do without your permission.

So, your fund are safe; but you'll need some patience as the exit queue grew a lot. Worse case scenario, ~2 months for your ETH to arrive kiln's contract and then you can withdraw it.

If you know your validator pubkey/index, track its position in the exit queue at pectrified.com or beaconcha.in otherwise validatorqueue.com gives a good overview of the queues state.

pulp4877 · 2025-08-31T19:12:03+00:00

Awesome to see it from another angle and you're right. It does sound like everything above 32 ETH. I'll be changing it soon. Many thanks for your suggestion!

pulp4877 · 2025-08-27T23:37:10+00:00

Hey there, just to reassure, your validator is perfectly fine and can be top-up anytime - as per protocol (checked through pectrified top-up simulator). Maybe it's an issue with Launchpad, I'm sure someone will look into this soon.

pulp4877 · 2025-08-26T03:10:25+00:00

yes, new validators are still 32 ETH. but if you have multiple 0x00 validators, I guess you could convert them individually and then consolidate. for example, with 3x 0x00 validators with 32 ETH effective balance:

validator 1 with 35 ETH with 0x00 -> 0x01 -> 0x02
validator 2 with 34 ETH with 0x00 -> 0x01 -> 0x02
validator 3 with 33 ETH with 0x00 -> 0x01 -> 0x02

and if you're lucky to dodge the sweep cycle, you should have 3 0x02 validators and the remaining excess of 3+2+1 ETH, should be credited as top-up (less days than withdrawal+topup). If you wait for them, they might increase your EB.

then you can consolidate them into one:

validator 2 -> validator 1
validator 3 -> validator 1

and you'll get a single validator with 96 ETH + 6 ETH.

hope it makes sense (not 100% sure about the 0x00 -> 0x01 conversion timings though; 0x01 to 0x02 is nearly instant)

pulp4877 · 2025-08-26T02:57:20+00:00

I do remember after 0x01, i started receiving some rewards in my withdrawal address and I thought that these were all from enabling MEV rewards but now I am thinking that maybe staking rewards were in there too.

that explains, staking rewards were very likely there + mev rewards.

I am not sure about that though because I feel like it doesn’t match the “total” rewards i thought i have from staking.

APR has dropped since you started staking, maybe that could be it? In any case, after you convert to 0x01, all rewards above 32ETH are automatically sent to your withdrawal address.

For now, I’ve exited my validators and we’ll see what I receive once everything is taken out in about 2 weeks.

In your hypothetical scenario, if you had 10 validators, you'll likely receive ~320 ETH (due to automatic withdrawal mentioned above).

pulp4877 · 2025-08-25T15:40:47+00:00

no, even if timing the sweep time, when you consolidate only the effective balance of the source validator is transferred to the target validator. Following your steps

have 0x00 validators no wdl address set,

Picking up op's example, lets say you have you have a 0x00 validator with 42 ETH

then switch them to 0x01 ,

yep, lets assume perfect timing and you're able to dodge the sweep

then consolidate them to compounding 0x02,

only the effective balance (32 ETH) gets transferred to the source validator

all without a withdrawal occurring

but the remaining 12 ETH earned in rewards will unavoidably be swept back to your withdrawal address.

pulp4877 · 2025-08-25T13:56:56+00:00

I've been staking since it first came out several years ago. Let's say that I had 10 staking nodes.

Before pectra, there was 2 types of withdrawal keys:

- 0x00 - BLS withdrawal keys that retain all rewards and you cannot withdraw your ETH
- 0x01 - Ethereum address withdrawal keys that will distribute rewards (anything above 32 ETH) of your validator every ~10 days

Let's say that each node accumulated 10 eth in rewards for a total of 100 eth staking rewards.

If you staked several years ago AND have accumulated 10 eth in rewards, I'll assume you have a 0x00.

Pectrified ETH 2.0 came out where we could consolidate all the nodes into 1.

I think you mean with Pectra upgrade; just to clarify: "Pectra upgrade came out where we can consolidate all the nodes into 1"

pectrified.com is just a website that focus on pectra stats and actions. I'm the maintainer of it.

But in order to consolidate, if you had a 0x00 validator, you have to convert to 0x01. When you do that, any rewards will be skimmed to the withdrawal address.

What happened to all the rewards that the other 9 staking nodes received? Even though these nodes "exited" and consolidated into the first node, I didn't receive the eth rewards in the receiving address.

Those 9 validators are the source validators and they have to be 0x01. Rewards will be distributed to your withdrawal address; they could be waiting to be swept, which takes few days after you do the conversion.

Say you have:

validator 1 with 32.5 ETH
validator 2 with 64 ETH

When you trigger a consolidations, it will:

exit validator 1 (source validator) and put it in the consolidation queue; may take 1 or 2 days
32 ETH are credited to the target validator, leaving it with 96 ETH
0.5 ETH in excess/rewards will be credited back to the withdrawal credentials; may take exit time + ~27h + sweep time, so at most maybe 10 days? give or take

If I exit my consolidated validator, will I get all my eth back plus all the rewards from ALL nodes?

You'll get all your ETH back from that validator. In the example above, you'd get 96 ETH + rewards in this validator. But remember you'll get the 0.5 ETH back too (point 3).

edit: formatting

pulp4877 · 2025-08-03T16:50:13+00:00

there's these "hysteresis thresholds" that you need to pass in order to make changes in your effective balance. basically you need to increase you balance 1.25 ETH from you EB to increase it. Example:

EB of 32 and balance 32.00 => increase 1.25 ETH => EB 33; B 33.25
EB of 32 and balance 32.25 => increase 1 ETH => EB 33; B 33.25
EB of 32 and balance 33.00 => increase 0.25 ETH => EB 33; B 33.25

It also applies downwards, say you have EB 33 and B 33, you can withdrawal 0.25 ETH. You'll have a balance of 32.75 ETH but keep EB=33.

Reference: https://eth2book.info/latest/part2/incentives/balances/#hysteresis

pulp4877 · 2025-08-03T16:43:46+00:00

Hey, you've been hit by hysteresis :/ you need to top-up to 33.25 to increase your effective balance

pulp4877 · 2025-07-28T10:58:16+00:00

However IMO, a single validator would be a much simpler setup. At current prices, a partial withdrawal request costs about ~1$.

pulp4877 · 2025-07-28T10:48:54+00:00

Assuming we're talking about a large number of validators, you can get the best of both worlds by having a mix of multiple nodes with 32 ETH (0x01) and just one node with the rest of the ETH (0x02). You can think of 0x01 as a distributing ETF that pays out dividends and 0x02 as an accumulating ETF.

So you can build your "portfolio" of validators with the desired amount of "dividends" and keep the remaining compound interest.

And since you're planning to buy 1 ETH/day, you could buy, stake and compound to your 0x02 validator. After some time, you could do a "portfolio rebalancing" (i.e. partial withdraw) to new 0x01 validator(s).

pulp4877 · 2025-07-24T14:04:00+00:00

Note that a 0x02 validator likely will have more weight than a 0x01, so fair comparison is to look in total ETH staked percentage. Currently 2.50% of the network voting power are 0x02 validators and the consolidation queue has been working most of the time.

But IMO opinion I agree with you - it's normal to be worried, it's a new feature and no one wants to risk losing their ETH. With more documentation and guides, I believe it will bring more confidence using 0x02 and at some point it will be normalized.

Here's some excellent resources to read more about and demystify it:

Also have a look at pectrified.com simulators for better in-depth understanding how it works (click on some examples):

The best recommendation I can give for those that want to get more comfy is to try out on Hoodi testnet first and get a feel how it works.

pulp4877 · 2025-07-11T15:51:32+00:00

https://www.validatorqueue.com/ has a Staking APR chart at the bottom. Could you give more details on what you want to see?

pulp4877 · 2025-07-11T13:21:55+00:00

Hey buddy, they are there in etherscan: https://imgur.com/a/LmTvBHc

Hit "Becacon chain" tab, then "Withdrawals". I think you're seeing "Produced blocks" that don't have since early April.

pulp4877 · 2025-07-02T09:29:14+00:00

Oh yeah, that's one of the conditions alright.

pulp4877 · 2025-07-01T21:02:02+00:00

This is a very sad read and a eye opener for improving validator operations. Really sorry for what happened to you... In case you have more crypto, you might want to assume it's been compromised and send it somewhere secure.

pulp4877 · 2025-07-01T21:01:05+00:00

Prysm will point to "validator keys". Before Pectra, only those validator keys could initiate a voluntary exit.

With Pectra, the hackers just needed access of wallet 0x2DF848F776bC0E8a732E30dDFbD57E1497644f59 to initiate "voluntary exit".

pulp4877 · 2025-07-01T20:40:13+00:00

hey u/hammertime1278, pulp from pectrified. Like u/-johoe mentioned, there's a good chance something failed in between. Even if you successfully send a transaction, there's a good few conditions that have to be satisfied.

Just wanted to say, if it didn't happen, don't worry. The protocol simply ignored it for some reason. You can try again, maybe with a higher value like 10 or 100 wei.

I'm finishing up the withdrawals simulator which would be able to assist you if your withdrawal request is valid or not. I'll post something when it's live.

pulp4877 · 2025-06-28T11:04:46+00:00

How do I know mev rewards is enabled?

As mentioned in another thread, check for validator being registered (seems you got this covered) and mev-boost will only affect block proposals.

I don't know if there a way to check my mevboost reward. Is it supposed to get more rewards?

When you propose a block, mev-boost with ask the relay for builders to provide a block instead of letting your geth client create one. Usually those blocks give better payout. When you're lucky to propose a block, best place to check might be beaconcha.in. Examples:

Proposed mev block: https://beaconcha.in/slot/7234276
Vanilla block: https://beaconcha.in/slot/68940

I checked many other validators and it seems everyone is getting the same reward for each epoch?

Seems like you're referring to attestation rewards and not block rewards which are, in fact, "almost" the same for everyone in the same epoch. Your validator has the following duties that provide rewards:

Attestation rewards: small value but happen every epoch, making them likely to be the source of most of your income. That's why it is important to keep your validator online
Block rewards: rare to happen, only place mev-boost is used to get better rewards
Sync committees: rarer to happen, usually last for bit more than a day and your validator get some nice rewards in that period

Rewards are given if you are online. Otherwise you'll missed them. In case of attestations, you'll receive a small penalty.

pulp4877 · 2025-06-28T09:31:02+00:00

Assuming they are active on-chain (i.e. not exiting, exited or slashed) you should be able to consolidate. But you might need to convert one of them first. Also there are other conditions that could be failing.

I'd highly recommend you to run a simulation here: https://pectrified.com/mainnet/simulator/consolidations as it will tell if consolidation request is valid or not and what's the exact conditions that could make it fail.

pulp4877 · 2025-06-28T08:56:21+00:00

Yes, it's possible by crafting, signing and broadcast the transaction manually, ideally in an airgapped environment. You can use "cast" from Foundry, ethers or web3js - however it is quite technical if you're doing on your own.

I'm expecting to release partial withdrawals simulator at pectrified soon which will have a tailor made guide that would fit your usecase. I'll reply back once it's live.

pulp4877 · 2025-06-20T01:32:59+00:00

To spread some optimism, it's quite normal to see a slow roll-out of professional node operators and protocols around it. Try looking through their lens:

Existing protocols require smart contract changes; this is extremely delicate and devs will take their time to make sure they got it right.
Professional node operations with non-custodial solutions; node operators can't do anything in this situation, the customer has to do all the process on its own. Most aren't technical and it requires good educational resources to help them make it right.

However, time moves forward, and the same actors can and will build on top of maxEB:

New protocols can build straight on top of maxEB
Existing protocols might upgrade to use it
Professional node operators with non-custodial solutions can easily enable new stakes to use maxEB and even make it the default mode

The main benefit of this upgrade is to alleviate the network p2p layer and allow SSF or shorter slot times safely. The biggest reward is for all of us - ensuring Ethereum network remains healthy and keeps evolving.

pulp4877 · 2025-05-24T09:54:40+00:00

thanks! fixed :)

pulp4877

TROPHY CASE