# priority_state_v1 · FT4 Rell API · Chromia Docs (concept)

> Return value of priority_check_v1 query.
It is used to represent how to prioritize a transaction: if multiple transactions
are in queue, the one with the h

Source: https://docs.chromia.com/pages/ft4-rell/-f-t4-library/lib.ft4.core.prioritization/priority_state_v1/

STRUCT

# priority\_state\_v1

Return value of `priority_check_v1` query.
It is used to represent how to prioritize a transaction: if multiple transactions
are in queue, the one with the highest priority value will be executed first.

```signature
struct priority_state_v1 {
 account_id: byte_array?;
 account_points: integer;
 tx_cost_points: integer;
 priority: decimal;
}
```

`account_id: byte_array?;`
:   ID of account which wants to push the transaction forward.
    A transaction can be multi-party, it's up to the dapp to decide who's the
    "main actor" of the transaction.

`account_points: integer;`
:   Number of points currently associated with the account.
    If this is lower than `tx_cost_point`, the transaction will be rejected.

`tx_cost_points: integer;`
:   Number of points which this transaction costs.
    If this is higher than `account_points`, the transaction will be rejected.

    If many transactions from this account are in queue, the costs are summed up to see if
    the account would be able to complete them all.

`priority: decimal;`
:   priority, higher is better

[Source](https://gitlab.com/chromaway/ft4-lib/-/blob/development/rell/src/lib/ft4/core/prioritization/module.rell#lines-9)

[View this page on docs.chromia.com](https://docs.chromia.com/pages/ft4-rell/-f-t4%20-library/lib.ft4.core.prioritization/priority_state_v1/index.html)Generated API reference, mirrored from the live docs