-
errorreporteri am doing "transfer 4.. 0.2 4.. 0.1" which, after a second responds with "Error: transaction was not constructed"
-
errorreporterthe log file in addition has "cryptonote_tx_utils.cpp:242 Destinations have to have exactly one output to support encrypted payment ids" right before that
-
errorreporterand a DEBUG saying "Encrypting payment id <37cc69754b0c871d>" right before that in turn. however, i did not enter any payment id
-
errorreporterdoes it consider the last amount i provide a payment id?
-
errorreporter(this is with a trezor, in case that's relevant)
-
errorreporteralso, it happens only after "account switch 1". on "account switch 0" the issue doesn't arise
-
moneromoooTransactions to standard addresses automatically get assigned a random short payment id if none is specified.
-
moneromoooI'll try to repro here.
-
louipcsweet
-
moneromoooSeems to work for me, but without a trezor.
-
errorreportermaybe it's something about the outputs used
-
errorreporteryou did an account switch?
-
moneromoooYes
-
moneromoooPayment ID stuff ought not depend on outputs used.
-
errorreporterhere it's using one input. might be relevant
-
errorreporterso there's one input of .45 that's used for both outputs
-
errorreporterlet me see if things change using a different index explicitly
-
errorreporterit doesn't
-
moneromoooYou're running a recent monero version I assume ?
-
errorreportermonero-x86_64-linux-gnu-v0.17.1.9
-
errorreporterwhen changing at least the first recipient to a 8.. address, it works
-
errorreporterWORKS: transfer 8.. 0.02 4.. 0.01
-
errorreporterWORKS: transfer 4.. 0.02 8.. 0.01
-
errorreporterWORKS: transfer 8.. 0.02 8.. 0.01
-
errorreporterDOESNT: transfer 4.. 0.02 4.. 0.01
-
errorreporterjust before payment id, log says the following, indicating that things might be treated somehow differently depending on the type of address: cryptonote_tx_utils.cpp:76 destinations include 2 standard addresses and 0 subaddresses
-
moneromoooThey do. Subaddresses don't get the default payment id.