Your transaction is executed before the call returns
Send once, get a signed receipt back in milliseconds, and build on the result without waiting for a block.
For teams shipping agents, checkouts and trading systems that cannot afford to poll, guess or show a spinner.
On most networks you send a transaction and wait. You poll, you show a spinner, you write retry logic, and you hope the thing you sent is still the thing that lands. Paxeer X does the work when you send. The transaction executes the instant it arrives, and the answer comes back in the same call: a signed receipt with the result, the events it emitted and the exact position it holds in the next block.
That receipt is a signed promise from the network. The block that follows contains exactly the receipted sequence, in order, and every validator checks that it does. Nothing you were told can be quietly reordered, cut in front of or dropped.
What that feels like in your product
The receipt in your hand
A receipt is not a hash to look up later. It is the result, signed, in your hand before you let go of the request.
Each receipt carries the outcome, the gas used, the logs and the sequence number, signed with a key anyone can verify offline. A reverted transaction is receipted too, with a plain reason, so your code learns about a problem in the same round trip rather than discovering it a block later. Nothing has to be polled, and nothing has to be guessed.
Read the world as it is, not as it was
Because execution happens at receipt, the network can answer questions about state that has not reached a block yet. Balances, nonces, logs, order books and contract calls all read at pending from the open block. Your app sees the effect of a transaction immediately, so a user never watches a number that is wrong for a second.
A receipted transaction lands at its sequence in the next block, and about a second later that block commits for good. The network holds two synced copies before it ever hands you the receipt, so a machine failing does not take your receipt with it. Finality covers the second moment.
Related
Build on the receipt
The developer docs show how to send, verify the signature and read pending state in every SDK.