Eliminate temREDUNDANT_SEND_MAX (RIPD-590):

The rules for when a SendMax is redundant are complicated. It is easier to
always allow a SendMax and eliminate temREDUNDANT_SEND_MAX.
This commit is contained in:
Miguel Portilla
2014-11-24 10:11:59 -05:00
committed by Nik Bougalis
parent 93b7599b1c
commit c522ffa6db
3 changed files with 0 additions and 11 deletions

View File

@@ -132,15 +132,6 @@ public:
return temREDUNDANT;
}
else if (bMax && maxSourceAmount == saDstAmount &&
maxSourceAmount.getCurrency () == saDstAmount.getCurrency ())
{
// Consistent but redundant transaction.
m_journal.trace <<
"Malformed transaction: Redundant SendMax.";
return temREDUNDANT_SEND_MAX;
}
else if (bXRPDirect && bMax)
{
// Consistent but redundant transaction.

View File

@@ -79,7 +79,6 @@ enum TER // aka TransactionEngineResult
temINVALID,
temINVALID_FLAG,
temREDUNDANT,
temREDUNDANT_SEND_MAX,
temRIPPLE_EMPTY,
temDISABLED,

View File

@@ -116,7 +116,6 @@ bool transResultInfo (TER code, std::string& token, std::string& text)
{ temINVALID, "temINVALID", "The transaction is ill-formed." },
{ temINVALID_FLAG, "temINVALID_FLAG", "The transaction has an invalid flag." },
{ temREDUNDANT, "temREDUNDANT", "Sends same currency to self." },
{ temREDUNDANT_SEND_MAX, "temREDUNDANT_SEND_MAX", "Send max is redundant." },
{ temRIPPLE_EMPTY, "temRIPPLE_EMPTY", "PathSet with no paths." },
{ temUNCERTAIN, "temUNCERTAIN", "In process of determining result. Never returned." },
{ temUNKNOWN, "temUNKNOWN", "The transaction requires logic that is not implemented yet." },