00:01:21 <moneromooo> No. One's enough.
00:02:37 <magnum90> Looking for 11 outputs of size 0.00    this is very strange
00:02:41 <magnum90> why size 0.00
00:02:59 <moneromooo> rct (amount unknown)
00:03:06 <magnum90> ah
00:04:04 <magnum90> from the begining are always 7 outputs
00:04:12 <magnum90> why there no 6 or 8 or 9
00:04:14 <magnum90> why 7
00:04:46 <magnum90> maybe some tx version need to change
00:10:56 <magnum90> moneromooo why always 7 outputs and not other number
00:11:59 <moneromooo> Where are 7 outputs ?
00:12:06 <moneromooo> I mean, where are you seeing that ?
00:12:40 <magnum90> Error: not enough outputs for specified ring size = 11:output amount = 0.00, found outputs to use = 7Please use sweep_unmixable
00:12:57 <magnum90> when transfer command is used
00:13:00 <moneromooo> Ah, did you run output_histogram @0 ?
00:13:08 <magnum90> on daemon
00:13:31 <moneromooo> If that's a question, then yes.
00:13:48 <magnum90> 372  0.00
00:14:05 <moneromooo> Hmm. Dunno then,
00:14:42 <magnum90> with what number 7 can be linked
00:14:54 <magnum90> because i have allways 7 outputs
00:15:17 <moneromooo> It's an old ring size IIRC.
00:16:54 <magnum90> yes but block 1 has version 12 so somewhere is hardcoded a function connected to v7
00:17:32 <moneromooo> Unlikely since we're on v12, but you never know.
00:19:08 <magnum90> for example on protocol handler is last_block_v1 hardcoded
00:19:24 <moneromooo> Ah, yes. Good point.
00:21:42 <magnum90> i greped all hardfork block numbers but nothing about v7
00:22:44 <moneromooo> You get to add prints to see where the 7 comes from. Likely a dameon RPC (get_output_histogram seems likely).
00:25:02 <magnum90> what is the equvalent on command line because rpc daemon is more complicated
00:26:31 <moneromooo> utils/python-rpc/console 18081
00:26:40 <moneromooo> daemon.get_output_histogram([0])
00:26:51 <moneromooo> Parameters might be a bit different, check the python file.
00:30:21 <magnum90> rpc.py", line 29, in <module>    import requestsImportError: No module named requests
00:30:28 <magnum90> not working
00:32:41 <magnum90> on cryptonote_core is other hardcoded version
00:32:42 <magnum90> https://paste.laravel.io/1f2d4ad0-524a-4c2f-8a60-2752a5da1795
00:32:56 <magnum90> maybe that one is creating all
00:36:16 <moneromooo> Unrelated.
00:39:21 <magnum90> this one is on wallet.cpp https://paste.laravel.io/efd3834f-0da2-43cd-930d-50d1c30e56bf
00:44:49 <magnum90> from hardcoded greps is not possible to understand why choose 7 outputs and 8,9,10,3,4,5
00:51:00 <magnum90> any idea where to search
00:58:40 <magnum90> moneromooo always this "output amount = 0.00, found outputs to use = 7"
05:45:30 <magnum90> hello
06:35:08 <locustlord> hey how do I use the monero client *without* downloading the entire blockchain
06:41:43 <UkoeHB_> locustlord: remote node
06:56:32 <locustlord> btw is the xmr.to node down?
07:43:03 <endor00[m]> Got a connection error on Monerujo on first attempt, but now it shows up
13:25:49 <Jackman2> why is #monero-markets full of gross neets
13:26:42 <Jackman2> ?
13:29:42 <azy> ?
13:29:55 <azy> who upset u bb
13:30:32 <Jackman2> neets
13:30:45 <Jackman2> I've more respect for grass
13:30:49 <Jackman2> than for neets
13:30:57 <Jackman2> seriously
13:32:28 <azy> im a neet
13:33:24 <Jackman2> ignored
13:33:39 <azy> what a loss for me
15:30:00 <xmrmatterbridge> <rbrunner7> Hah, learned something today, what a "neet" is. Now on the the interesting question why it's a problem if there are many of those in a particular place ...
15:52:33 <Mochi101> Isn't Neet a brand name for a hair removal cream?
15:58:53 <azy> thats veet
16:04:44 <asymptotically> mixed up nair and veet. protip: don't put either of them on your balls
16:14:26 <Jackman2> hi ghost43
18:14:50 <Aexis> so, who would like to help me stay awake all night?
18:15:39 * jwinterm pinches Aexis 
18:16:02 <Aexis> yes, it's not as if I could not do that myself....
18:16:13 <Aexis> but thnaks anyway.
18:16:26 <Aexis> trouble is, it DOES brind bad memories
18:16:35 <Aexis> but nothing YOU should know...
18:19:21 <jwinterm> 2spooky4me
18:28:09 <Aexis> nah, just...how do you call something that is so painful as not to be able to quantify it?
18:32:49 <azy> hurty
18:34:26 <Aexis> It's just that when you've kept inside some painful situations ofr over telve years, if they "come out", they become unbearable
21:35:22 <smrcascao_> @MalMen,
21:44:31 <Jackman1> I like monero
22:56:48 <magnum90> why this hardcoded 33.4  here   "pre_fork_num_out_ratio = 33.4/100.0f"
22:57:46 <moneromooo> It was a hack to protect against key reuse, which you don't have to deal with.
22:58:05 <moneromooo> You can remove this code altogether if you want.
22:59:38 <magnum90> i edit this to 1 SEGREGATION_FORK_VICINITY  and transfer is working
23:02:51 <magnum90> why this SEGREGATION_FORK_HEIGHT was version 7 block number before and now is 99999999
23:03:12 <moneromooo> You can ignore/remove that code.
23:04:19 <magnum90> i removed and transfer work now but what is the reason to change from version 7block number to 9999999
23:09:50 <magnum90> is better to change this defines to 1 or to remove?
23:11:12 <moneromooo> I don't remember how this works exactly, but if I were you I'd just remove.
23:17:05 <magnum90> if we have dandelion and other stuff for protection this "RECENT_OUTPUT_DAYS/RECENT_OUTPUT_RATIO" maybe is useless
23:26:36 <magnum90> monero code create fake outputs right?
23:26:42 <magnum90> so why this "RECENT_OUTPUT_DAYS/RECENT_OUTPUT_RATIO"
23:59:48 <magnum90> moneromooo what is this FIRST_REFRESH_GRANULARITY