MIN_CHANGE is a privacy leak, since it is an easily observable wallet behaviour. Any output almost equal, but minimally larger than MIN_CHANGE is highly likely the change output of a tx.

Also, MIN_CHANGE is quite high, considering the value of bitcoin.

An easy fix for the second issue would be to just lower the value, but maybe some randomization can be done to also fix the first issue?
}
/******************************************************************************
 OutputGroup
 ******************************************************************************/
void OutputGroup::Insert(const COutput& output, size_t ancestors, size_t descendants, bool positive_only) {
    /
    const CAmount coin_fee = output.input_bytes < 0 ? 0 : m_effective_feerate.GetFee(output.input_bytes);
    const CAmount ev = output.txout.nValue - coin_fee;
    /
    if (positive_only && ev <= 0) return;
    m_outputs.push_back(output);
    COutput& coin = m_outputs.back();
    coin.fee = coin_fee;
    fee += coin.fee;
    coin.long_term_fee = coin.input_bytes < 0 ? 0 : m_long_term_feerate.GetFee(coin.input_bytes);
    long_term_fee += coin.long_term_fee;
    coin.effective_value = ev;
    effective_value += coin.effective_value;
    m_from_me &= coin.from_me;
    m_value += coin.txout.nValue;
    m_depth = std::min(m_depth, coin.depth);
    /
    /
    /
    m_ancestors += ancestors;
    /
    /
    m_descendants = std::max(m_descendants, descendants);
}
bool OutputGroup::EligibleForSpending(const CoinEligibilityFilter& eligibility_filter) const