Transactions and status¶
The Transactions page is the history of everything this wallet has signed, with a live status for each entry.
The status lifecycle¶
Each transaction moves through three stages:
| Status | Meaning |
|---|---|
| Pending | Signed and broadcast, not yet in a block. |
| Confirmed | Included in a block and has a receipt. The block could still, in principle, be reorganised. |
| BFT-Finalized | The block is at or below g4_status.finalized_height and is still canonical. This is irreversible under the chain's BFT finality. |
Wait for BFT-Finalized before treating a payment as settled
"Confirmed" means a block included the transaction; "BFT-Finalized" means the network's validators have
finalised that block. For anything that matters, wait for BFT-Finalized. Applications can check the same
thing with g4_status — see Finality for applications.
How history is built¶
The PQWERAI Core node has no address index, so the wallet builds your history itself with an incremental, reorg-safe block scan: it walks new blocks as they arrive and re-checks the recent chain so that a reorg is reflected correctly rather than showing a stale result.
Alongside the scan, the wallet keeps a local journal of every transaction it has signed. This journal is what lets the wallet show a transaction as Pending immediately, independently of the scan.
Rebroadcast after a crash¶
If the wallet or PC crashes after a transaction was signed but before the network accepted it, the wallet rebroadcasts the signed transaction from its journal when it starts again. You do not need to re-sign or resend by hand.
Reading an entry¶
Each row shows the direction, the counterparty address, the amount, the fee actually paid, the block, and the current status. Selecting an entry shows its hash and details. Because amounts are stored as exact integers, the values shown are exact.
Sources at 7a33c77104: apps/pqwerai-wallet-windows/README.md
Found a problem? Report a documentation issue · Build testnet-rc1+7a33c77104