is there a simple way of distinguishing the amount of integrated address use vs subaddress use?

i'd like to display the % use of each on my monero stats website

If extra has an extra pubkeys field, it means at least one recipient used a subaddress. For integrated address vs standard, you can't really tell since a dummy one's added now.

how do i decode the extra? "extra - Usually called the "payment ID" but can be used to include any random 32 bytes."

i see small ones and long ones (xmrchain.net/tx/4ae2efacfbe892fddc6…ad16aee7856c538067774b2ffa19f0e7c12, xmrchain.net/tx/f706cd689b93048165b…e7f12c28b8db46b7399113dd25b3a2545bc)

parse_tx_extra (cryptonote_format_utils.h)

ty

There's probably an english explanation somewhere on monero.stackexchange.com.

there is, neat

"it means at least one recipient used a subaddress" - and that means that the transaction definitely paid a subaddress?

if i were to count all tx with no "TX_EXTRA_TAG_ADDITIONAL_PUBKEYS" byte as "not a subaddress transaction", that would be correct?

xmrchain.net/tx/4ae2efacfbe892fddc6…ad16aee7856c538067774b2ffa19f0e7c12 has nothing after the 01 + Tx public key

this one has 2 but only "0901ae7f50479094ab30" after it xmrchain.net/tx/f706cd689b93048165b…e7f12c28b8db46b7399113dd25b3a2545bc

this one has 4 like monero.stackexchange.com/questions/…a-tag-additional-pubkeys-from-extra describes: xmrchain.net/tx/aed9becf83c2f8f7fc5…507092ae983f3873793793e4fb81a0eaa3b

No, someone could add this tag without paying a subaddress.

can anyone think of a prettier solution than ifdef? monero-project/monero #6488#issuecomment-622505062

a print function / lambda that uses the correct cout?

A function that does it, so at least you have just one of them.

ok

It's odd it wouldn't work though, since printing messages works on Windows (or we'd have heard about it).

So why does it not work with those particular calls ?

And maybe the chars should be sent encoded as UTF-8, rather than code points.

will try utf8 first

but AFAIK windows console + utf8 is always a bit tricky

"ga" in vim shows encoding for any char.

ga looks quite useful

"ga" like in (g)aracter (a)ncoding, I guess?

moneromooo: you mean like this? paste.debian.net/hidden/f6b3de8b

I was thinking the hex codes, but I guess if it works like that, even better :)

seems to also work on mac, iDunk could you test on top of latest version of my PR?

and if it does not work, please try again stackoverflow.com/questions/4557586…tdcout-on-windows/45622802#45622802

why would somebody add the tag without paying a subaddress?

is there even a good way of seeing how often subaddresses are used vs not subaddresses?

To confuse your system.

so it's unlikely? then it seems like a nice way of seeing the adoption rate/use of subaddresses?

Yes, unlikely. But your question was "and that means that the transaction definitely paid a subaddress?"

i appreciate it

azy counting pub keys is not nearly enough to know how many tx have a sub address recipient, since most or all 2-output tx with a subaddress recipient will have 1 tx pub key, and even some >2 output tx

are there any must have PRs still open that have to get into v0.15.1.0?

6409 6418 (I've not reviewed the 0mq specific stuff though) 6431 6441 6451 6467 6468 6471 6472 6477 6478 6480 6481 6484 6485 6486

that.. was quick

:P

Sorry. I just failed the Turing test didn't I.

I had just sent dEBRUYNE that list :P

(phew, nice save)

:D

Any opinions on 6426 6427 ? It feels iffy (especially the latter), but no strong dislike.

Also if someone who uses docker can check 6428 6434 that would be nice.

6428 is a duplicate

I thought we closed it already..

6421: not sure about that one, it might make DoS easier. Any opinion ?

I commented on 6434

sarang: I assume 6329 is still WIP as it's still marked as such ?

moneromooo: can you close 6428 as a duplicate of 6420? I can’t do it

done.

6329 needs a unit test with a V1 proof

selsta: it doesn't work, but nothing's changed, really.

iDunk: okay, one more question, does the endl also have to be printed out with wcout?

It doesn't even print a single line, so inconclusive.

I meant with your patch

that you posted on Github

Yes, otherwise everything gets printed on a single line, IIRC.

With that SO patch, I lose colors if I set vbuff to 1000, colors still there with vbuff 0. And that's with and without u8.

Btw, that SO article seems to be for VS, not mingw.