Integrating your own StarkEx instance

You are the only Operator. You have full control of your StarkEx instance.

There are multiple Operators.

You manage the vaultId allocation as part of your application.

The vaultId value that you define for your transaction can be taken by someone else.

You are the only one sending transactions, so you don’t need to call get_first_unused_tx_id.

StarkEx processes transactions sequentially, based on the value of each transaction’s id, so the ids in your list of transactions must include all integers in the range of values.

For example, for a list of three transactions, the list of transaction id values cannot be 0,1,3, it must be 0,1,2. It can also be non-sequential, such as 0,2,1. If the list doesn’t include an integer, StarkEx stops processing when it reaches the missing id and waits for it to be submitted.

In order to get the next transaction id, you must query the StarkEx gateway by calling get_first_unused_tx_id, because other Playground users need to sync the next tx_id.

Be aware that StarkEx does not process two transactions with the same id and does not process a transaction if the transaction with the previous id has not been processed.