I'm not sure we want to move forward this with this.

Ideally, withdraw_anchor_account should never change once its originally set in order to avoid confusion / mistakes. We only allow withdraw_anchor_account to be changed in the Anchor Platform because the field is set to the asset's configured distribution account when the transaction is created.

This is a bug, since withdraw_anchor_account should only be available once the business is ready to receive funds and the transaction is in pending_user_transfer_start. But because businesses already depend on that behavior, we can't change that until 3.0.

All this is to say that account_id should probably remain a required field for the synchronous success response. The Anchor Platform will never return this response type so we don't need to be concerned about providing the wrong account_id.

Actually, I misspoke when I said the Anchor Platform will never return the success response (it will).

So now I see the problem.. the Anchor Platform's implementation has a bug but we can't fix it without potentially breaking business's application logic. At the same time, allowing businesses to update withdraw_anchor_account means the wallet will get an incorrect account address in the synchronous response.

So I've come full circle now 😅 and think making account_id optional is really the only viable path forward. I think this makes sense from an API design perspective as well. We don't want to provide deposit instructions in the synchronous response, so we shouldn't do that in the withdraw response either.

@JakeUrban Thanks for catching that, I made the changes 👍