A HogEx record is not a single customer transfer
Litecoin’s extension-block design describes an integrating transaction that carries peg-outs onto the canonical chain. The current Litecoin MWEB implementation explicitly treats the first HogEx output differently: it contains the extension balance and header commitment, while the remaining outputs are peg-outs. The first or largest displayed output is therefore not a safe shortcut for identifying your payment.
This matters when a wallet supplies a public-side reference after a movement out of MWEB. A transaction page can show values belonging to the integration structure and other outputs. Use the wallet’s own mapping to the intended recipient and output; the presence of an impressive transaction total does not establish the amount paid to an exchange.
A fictional output list: which entry is the intended payment?
| Illustrative entry | Meaning in this example | Can it describe your payment? |
|---|---|---|
| Output 0: extension balance | Special integrating output, not a peg-out | No: do not treat it as your personal amount |
| Output 1: 3 LTC to recipient A | One fictional transparent peg-out | Only if the actual instruction and wallet record identify A |
| Output 2: 7 LTC to recipient B | Another fictional transparent peg-out | Not because it shares the same transaction |
| Displayed transaction aggregate | A broader transaction-level figure | No: it does not select a customer recipient |
Review only the record relevant to your own payment
- Did the wallet identify a specific recipient output?
- Keep the wallet-provided public reference, output context and intended amount together. A kernel-related reference, an integration record and the resulting recipient output have different roles. If the wallet does not make the relationship clear, ask it to explain the existing operation rather than selecting a plausible-looking entry yourself.
- Does the actual instruction allow the proposed funding method?
- A public peg-out output is not a universal assurance that every receiving service supports direct funding that way. Check the current payment instruction and clarify compatibility before authorizing a new transfer. This page does not assert that KOT.CASH accepts any particular MWEB-origin workflow.
- Are you checking inclusion or spendability?
- A visible output and the ability to spend it later are different questions. The extension-block design discusses locking peg-out outputs before children can spend them. This article gives no fixed maturity or confirmation promise; use the current wallet and recipient requirements for the actual operation.
Explain an existing deposit without sending a second one
- State the intended public-side payment
Provide the appropriate public transaction reference, identified recipient output, amount and the exchange instruction it was meant to satisfy. Do not label a transaction aggregate or the special extension output as your deposited balance. Keep raw private wallet material out of the enquiry.
- Resolve the Litecoin-side result first
If the output or acceptance remains unclear, describe that uncertainty precisely. Do not repeat the peg-out or send another LTC payment to test whether the first was recognized. Once the actual funding state is established, trace the SOL payout separately with its receiving record.
The purpose is matching your instruction, not tracing other users
Several outputs sharing a public transaction do not establish common ownership. This worksheet uses no private-transfer inference and makes no anonymity guarantee. Its purpose is narrower: help the sender read a record their own wallet supplied and avoid assigning another entry or a system-level amount to their exchange payment.
Litecoin peg-out evidence questions
- Is the first HogEx output a normal peg-out payment?
- The cited current implementation treats it as the extension balance and header commitment, not a peg-out.
- Can I use the whole transaction total as my deposit amount?
- No. Identify the intended recipient output using your own wallet’s record and the funding instruction.
- Does a peg-out output guarantee every service accepts that funding method?
- No. Check the actual recipient’s current instruction and supported workflow.
- Does sharing a HogEx transaction prove the outputs have one owner?
- No. This page makes no ownership-linking inference and concerns only your own supplied payment record.
Litecoin design and implementation sources
- Litecoin extension-block design: integrating outputs and peg-outs
- Current Litecoin implementation: HogEx output classification
Reviewed: