# MIP-23: Account-configurable Reserve Balance

**URL:** <https://forum.monad.xyz/t/mip-23-account-configurable-reserve-balance/598>\
**Category:** MIPs\
**Created:** [November 11, 2026, 1:40pm UTC](https://forum.monad.xyz/t/mip-23-account-configurable-reserve-balance/598 "2026-11-11T13:40:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![qedk](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.monad.xyz/qedk/32/146_2.png) [@qedk](https://forum.monad.xyz/u/qedk)\
**Post date:** [November 11, 2026, 1:40pm UTC](https://forum.monad.xyz/t/mip-23-account-configurable-reserve-balance/598/1 "2026-11-11T13:40:39Z")

</div>

We want to introduce account-configurable reserve balances by extending the reserve balance precompile at `0x1001`. Accounts can select any `uint256` amount, denominated in wei units. Accounts that do not configure a reserve will retain the existing global default of 10 MON.

Configuration changes will activate after the consensus-execution delay. Consensus accounts for scheduled reductions without treating scheduled increases as immediately available gas collateral. Existing emptying transaction eligibility and transaction-end reserve balance enforcement are otherwise preserved.

You can find the MIP here as a PR (link will be updated once merged):

> <https://github.com/monad-crypto/MIPs/pull/109>
>
> \- \[x\] adds a MIP to propose Account-configurable reserve balance
> 
> I've taken the… self-liberty to assign MIP-23 as the next assignable number.

---

<div class="post-metadata">

**Author:** ![Anzus\_GemWallet](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.monad.xyz/anzus_gemwallet/32/394_2.png) [@Anzus\_GemWallet](https://forum.monad.xyz/u/Anzus_GemWallet)\
**Post date:** [November 12, 2026, 2:35am UTC](https://forum.monad.xyz/t/mip-23-account-configurable-reserve-balance/598/2 "2026-11-12T02:35:48Z")

</div>

From the wallet support side, a reserve that can differ per account seems like something users will need explained when a send fails. Two plain questions:

- How would a wallet read an account’s current reserve, so it can show how much MON is actually sendable?
- Could a dapp ask a user to sign a reserve change? If so, it seems worth flagging clearly in the signing prompt, since a very high reserve could stop someone from sending their MON.

---

<div class="post-metadata">

**Author:** ![qedk](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.monad.xyz/qedk/32/146_2.png) [@qedk](https://forum.monad.xyz/u/qedk)\
**Post date:** [November 12, 2026, 12:50pm UTC](https://forum.monad.xyz/t/mip-23-account-configurable-reserve-balance/598/3 "2026-11-12T12:50:43Z")

</div>

> How would a wallet read an account’s current reserve, so it can show how much MON is actually sendable?

The wallet application would do an `eth_call` to the `0x1001` precompile using the `GET_RESERVE_BALANCE` selector with the wallet address as the parameter. Sendability would then depend on current balance, in-flight transactions (gas reserved in consensus) and specified reserve balance (i.e. `DEFAULT_RESERVE` or a set value).

> Could a dapp ask a user to sign a reserve change? If so, it seems worth flagging clearly in the signing prompt, since a very high reserve could stop someone from sending their MON.

Yes, since it’s essentially a normal transaction. Wallet applications would be expected to:

1. support setting a custom reserve balance, in which case the user would be made aware of what they are signing
2. not support setting a custom reserve balance, in which case the user would not be allowed to sign the transaction