Same as Transaction, with MeshTxBuilder you have to register a stake address before delegate to stakepools. Here's the 2 APIs you need:

Since we need to provide the deserilized hash of pool id, we can use the following util to get it:

Delegation with MeshTxBuilder is exactly the same as first delegate, but without registering stake key, so only one API is needed:

Withdrawal with MeshTxBuilder comes with only one API, to specify the reward address and the amount to withdraw.

• rewardAddress (string) - the reward address to withdraw from
• lovelace (number) - the amount to withdraw in Lovelace

Deregister a stake address. The function accepts the following parameters:

• rewardAddress (string) - the bech32 reward address to deregister

Withdrawal from script is supported by MeshTxBuilder with this set of APIs:

Withdraw Zero

With that capability, it supports a Cardano technique - withdraw zero - which is a technique to trigger withdrawal script validation without actually withdrawing any value. This is a technique to help boost script ExUnits performance especially comes to validating multiple script inputs. In order to perform withdraw zero, 2 steps are involved:

• Register script stake key
• Withdraw Zero