Mummy finance
Mummy finance: Position State, Balance Reconciliation, and Exit Proof
Mummy finance trade records span wallet authorization, transaction submission, protocol state changes, and resulting balances, but not every action reaches every stage. Trace the transaction hash first, then match the relevant position or order state, applicable fees, and resulting balance before treating an entry or exit as complete.
updated
Entry paths create different records
A market request, a limit order, and a trigger order leave different evidence. A market request seeks execution after submission, while a conditional order can remain open until the market reaches its condition and execution occurs.
An approval changes a token allowance. It does not create exposure, set an entry price, or prove that collateral reached a position. A deposit or exchange-balance credit can make funds available, but the position record must still show size, direction, collateral, and entry price.
Product version also changes the trail. V1 routes open, close, and collateral edits through a request followed by keeper execution. V2 uses stablecoin collateral and an internal exchange balance, so wallet transfers alone cannot describe every state change.
Identify the action type before interpreting its receipt. A successful approval can precede a failed trade, and an accepted conditional order can remain unfilled without creating a position.
The normal path from signature to open position
The normal path begins with the correct wallet account, network, collateral source, and enough native currency for network costs. A missing prerequisite can stop the request before any trading state changes.
Confirming in the wallet signs the call; after submission, the transaction has a hash. The receipt then shows whether the network included the call successfully. Its sender, destination, status, block, and token movements identify what happened on-chain, but they do not replace the protocol position record.
V1 open, close, and collateral edit requests use a second transaction that a keeper submits after the user’s request. The first successful receipt is therefore an intermediate state for those actions, not final proof that the requested position change executed.
Execution should produce a matching position entry in the intended product version, with the expected direction, size, collateral, and entry price. If those fields do not appear, check the request hash and any later execution record before signing another state-changing transaction.
State records across the stack
State records divide into wallet authorization, chain receipts, protocol positions, open orders, and balances. Each record answers a different question, and reconciliation fails when one substitutes for another.
Wallet authorization and chain receipt
Wallet authorization proves that the selected account signed a call. A successful receipt proves that the chain processed that call without reverting. Neither fact identifies the economic outcome unless the call, emitted activity, and resulting protocol state match the intended action.
Protocol position and order state
Protocol state separates live exposure from instructions that may act later. Read the position and order panels independently.
Position record
The position record carries the live size, collateral, direction, entry information, accrued costs, and liquidation data that the product shows. An increase, reduction, or collateral edit should change the relevant fields rather than merely add a wallet notification.
Order record
The order record shows an instruction that remains pending, executes, or reaches canceled status. Its presence does not prove a fill. After execution, the order state and affected position must agree on the quantity that changed.
Balances form the last layer. A wallet balance may move because of network gas, collateral transfer, settlement, or redemption. V2 also keeps an exchange USD balance, which can hold proceeds without an immediate wallet token transfer.
A reconciliation checklist before the next action
Reconciliation compares records for the same account, network, product version, and requested action. Use this checklist before adding collateral, placing another order, or withdrawing proceeds.
- Confirm that the connected account and network match the transaction record.
- Match the transaction hash and receipt status to the intended call.
- Find the expected live state: a position, changed size, canceled order, or credited balance.
- Compare the starting balance with collateral, realized profit or loss, and displayed fees.
- Record any remaining position size and open orders before taking the next action.
A mismatch narrows the investigation. A confirmed request without the expected V1 change points to the keeper stage; a changed position with an old interface view points to data retrieval; a correct close with an unexpected net amount points to fees or settlement location.
How can you prove that a close is complete?
A full close is complete when the position record shows no targeted exposure, the final transaction succeeded, no unwanted orders remain, and the correct balance contains the net proceeds. A partial close cannot satisfy that test because it intentionally leaves live size and collateral behind.
Settlement location depends on the version and position path. V1 settles long profits in the asset being longed and short profits in the stablecoin that opened the position. V2 credits profit to the exchange USD balance, where it can support another position or be redeemed for USDC.
Open orders require a separate check. In V1, manually closing a position does not automatically cancel its associated trigger orders. A zero position with a live trigger order is therefore not a clean terminal state for someone who does not want that instruction available later.
Partial exits leave a live remainder
A partial exit changes the position rather than ending it. The remaining size, collateral, accrued fees, liquidation data, and related orders still matter after the reduction. Compare the requested close quantity with the executed reduction, then reconcile the realized amount separately from the value and risk that remain in the position.
Fees that change the final balance
Fee reconciliation separates the preview amount from the final credit. Position charges, funding, borrowing, network costs, and any swap needed by the selected path can affect different records at different times.
Position fees follow the executed size rather than the wallet’s total balance. Increasing or decreasing a position can create a charge even when the transaction does not fully open or close the exposure.
V2 funding uses an asset-specific index that changes as the long and short imbalance changes. Positive funding makes longs pay shorts, while negative funding reverses that direction. The applicable index difference and size being reduced belong in the close reconciliation.
V2 borrowing cost depends on position size, the configured per-asset rate, and the time held. Since the rate is a protocol parameter, use the value applied to the position rather than carrying an earlier preview into the final calculation.
Network costs sit outside trading profit and loss. V1 also presents an execution fee for the keeper transaction. A wallet can therefore spend native currency even when the collateral and settlement amounts reconcile exactly inside the protocol.
Delayed execution and bounded recovery
Classify a delayed or conflicting state before submitting another request. Determine whether the chain lacks confirmation, the protocol awaits a later execution step, or the interface has not loaded confirmed state.
Confirmed chain, stale interface
A stale interface can hide a confirmed change when its RPC connection is slow or unavailable. Check the same account and network, compare the transaction receipt with the position state, and refresh the data path. Changing an RPC endpoint changes access to chain data, not the position itself.
Failed request or unexecuted order
A reverted call does not apply its requested state change, although the wallet may still spend network cost. A successful V1 request without keeper execution remains incomplete. A trigger order can also remain open if the marked price does not satisfy its condition long enough or no keeper executes it, and the trigger price does not guarantee the execution price.
Recovery stops at the last verified state. Do not infer a fill from a wallet prompt, submit a duplicate solely because the interface looks old, or treat an order as canceled because the position changed. The existing hash, nonce, receipt, position, and order records define where recovery should resume.
A clean terminal state
A terminal record has no unintended exposure, no unwanted live orders, and no unexplained balance difference. Keep the entry, adjustment, and exit hashes together so the final net movement can be reconstructed without relying on interface history alone.
In V2, a profitable full close removes the position and credits profit to the exchange USD balance. Redeeming that balance for USDC is a separate transaction with its own receipt and resulting wallet balance.
Your questions, answered
Is a token approval proof that a Mummy finance position opened?
No. A token approval changes how much a contract may spend from the wallet; it does not create a position. The transaction record must identify the later trading call, and the resulting protocol state must show the expected size, direction, collateral, and entry data before the position is actually open in the protocol. The approval receipt alone cannot supply those fields.
Does changing an RPC endpoint alter an existing position?
No. An RPC endpoint is a route for reading chain data and submitting transactions; changing it does not rewrite contract state. If one endpoint lags, another may display the confirmed position sooner. The receipt and contract-backed position state should remain consistent for the same account, network, and block height. An endpoint change cannot reverse a completed trade.
Can a V1 trigger order remain after a manual close?
Yes. A manual V1 close can leave its associated trigger orders open, so a zero position does not prove that every instruction disappeared. Inspect the order list after the close, match each order to the old position, and cancel any instruction that should not remain available for a later position. The close and cancellation produce separate records.
Where does profit from a V2 close appear?
V2 credits profit from a close to the exchange USD balance rather than directly sending that profit to the wallet. That balance can support another position or be redeemed for USDC. The close record and credited balance confirm settlement; a later redemption receipt confirms the wallet transfer. These are distinct state changes.
Will a trigger order always execute at its trigger price?
No. A V1 trigger order is a market order, and the trigger price sets the condition for execution rather than guaranteeing the final price. The marked price may fail to satisfy the condition long enough, or no keeper may execute the order. Reconcile the order status and position change instead of treating a chart touch as proof of a fill.
Are token transfers alone enough to reconcile a trade?
No. Token transfers show asset movements, but they do not by themselves distinguish collateral, settlement, redemption, or every fee. Match the transfers with the called action, successful receipt, position change, and version-specific balance. Network costs may also appear only in the native-currency balance, outside the token movements used for collateral and proceeds.
Do accrued V2 funding and borrowing fees change the final balance?
Yes. V2 funding and borrowing fees accrue through different mechanisms and can change the net amount realized at a reduction or close. Funding follows the asset’s funding-index movement and position side, while borrowing reflects position size, the configured per-asset rate, and time held. Use the values applied to the executed change, not an older preview.
Must a partial close remove the position row?
No. A partial close should leave the remaining position visible, with reduced size and updated collateral, fee, and liquidation information. Completion proof for that action is the requested reduction, the realized settlement, and the continuing position state. A missing row would suggest either a full close or a display problem, not a successful partial exit by itself.