MoneyRange() allows zero?

[dougEfish]

In MoneyRange():

Code:

inline bool MoneyRange(const CAmount& nValue) { return (nValue >= 0 && nValue <= MAX_MONEY); }

Zero is valid.

I can see how fees can be zero, but is it possible for CAmount in a transaction (e.g. p2wh address1 --> address2) be zero?

[1714780402]

1714780402

[1714780402]

1714780402

[dougEfish]

in tx_check.cpp

Code:

// Check for negative or overflow output values (see CVE-2010-5139)
CAmount nValueOut = 0;
for (const auto& txout : tx.vout)
{
     if (txout.nValue < 0)
          return state.Invalid(TxValidationResult::TX_CONSENSUS, "bad-txns-vout-negative");
     if (txout.nValue > MAX_MONEY)
          return state.Invalid(TxValidationResult::TX_CONSENSUS, "bad-txns-vout-toolarge");
     nValueOut += txout.nValue;
     if (!MoneyRange(nValueOut))
          return state.Invalid(TxValidationResult::TX_CONSENSUS, "bad-txns-txouttotal-toolarge");
}

It looks like you can

[ABCbits]

I can see how fees can be zero, but is it possible for CAmount in a transaction (e.g. p2wh address1 --> address2) be zero?

It's definitely possible if address2 actually refer to OP_RETURN output.

[pooya87]

It's definitely possible if address2 actually refer to OP_RETURN output.

It is standard if the address2 is OP_RETURN output but it is still perfectly valid for it to be anything else.

is it possible for CAmount in a transaction be zero?

Basically the only thing that the consensus rules care about is that the sum of outputs is not bigger than sump of inputs. In simple terms: you don't spend more than you can.