r35157/com_r35157_nenjim-hubd-impl_ref
SHA256
0
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Investigate and expose closeFeeUsd in JupiterPerpsPosition #23

New Issue
Open
opened 2026-06-30 06:50:27 +02:00 by minimons · 0 comments
minimons commented 2026-06-30 06:50:27 +02:00
Owner
Copy Link
Copy Source

Description

The Jupiter Perps API should expose the closing fee for an open position.

According to the Jupiter Perps liquidation documentation, the closing fee is one of the required input values for calculating the liquidation price. Unlike the opening fee, the closing fee represents the cost of closing the current position and therefore affects the liquidation threshold.

Goal

Identify where the closing fee is stored or how it is calculated, and expose it through JupiterPerpsPosition.

Required changes

  • Determine whether closeFeeUsd is:

    • stored directly in the Position account,
    • stored in another account,
    • or must be calculated.

  • If the value can be obtained reliably, expose it as:

    • ΩUSDCAmountΩ closeFeeUsd

  • Decode or calculate the value as appropriate.

Validation

Verify the decoded/calculated value against the Jupiter web UI for one or more open positions.

Notes

The closing fee is expected to represent the cost of closing the current position and is one of the required inputs for calculating the liquidation price.

This value is intended to be used by a future implementation of liquidationPrice in JupiterPerpsPosition.

### Description The Jupiter Perps API should expose the closing fee for an open position. According to the Jupiter Perps liquidation documentation, the closing fee is one of the required input values for calculating the liquidation price. Unlike the opening fee, the closing fee represents the cost of closing the current position and therefore affects the liquidation threshold. ### Goal Identify where the closing fee is stored or how it is calculated, and expose it through `JupiterPerpsPosition`. ### Required changes * Determine whether `closeFeeUsd` is: * stored directly in the Position account, * stored in another account, * or must be calculated. * If the value can be obtained reliably, expose it as: * `ΩUSDCAmountΩ closeFeeUsd` * Decode or calculate the value as appropriate. ### Validation Verify the decoded/calculated value against the Jupiter web UI for one or more open positions. ### Notes The closing fee is expected to represent the cost of closing the current position and is one of the required inputs for calculating the liquidation price. This value is intended to be used by a future implementation of `liquidationPrice` in `JupiterPerpsPosition`.
minimons added the enhancement label 2026-06-30 06:50:27 +02:00
minimons self-assigned this 2026-06-30 06:50:27 +02:00
minimons added this to the AssetAZ project 2026-06-30 06:50:27 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project AssetAZ
Assignees
Clear assignees
builder (CICD User) minimons (Morten Green Hermansen)
No Assignees minimons
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: r35157/com_r35157_nenjim-hubd-impl_ref#23
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?