00:28:04 <Thomas[m]1> I am writing an RPC client for monerod and I am having trouble with the binary requests. I've more or less reverse-engineered this portable binary encoding defined within epee but it still doesn't quite work. Specifically, I am trying to invoke `/get_o_indexes.bin` but regardless of which transaction ID I am sending to it, monerod always prints `transaction with hash
00:28:04 <Thomas[m]1> 0000000000000000000000000000000000000000000000000000000000000000 not found in db` to its log even though I am clearly **not** sending `0000000000000000000000000000000000000000000000000000000000000000` as the txid. Any pointers on what could be wrong here?
02:05:27 * Thomas[m]1  < https://matrix.org/_matrix/media/r0/download/matrix.org/zaJkiUpVSdQWaBgaRrhGPDLo/message.txt >
03:38:32 <h2017> hi
03:38:55 <h2017> how often does the progressbar at https://ccs.getmonero.org/proposals/cypherstack-sarang-triptych-research.html update?
03:39:04 <h2017> i donated and I think it's gone through now
03:39:36 <selsta> rehrar is working on it
03:39:46 <selsta> usually it shows up instantly / after 1 conf
03:39:59 <selsta> but something is broken currently :P
03:41:27 <h2017> i joke at work "progress bars mean progress".
03:42:16 <h2017> i should say i used to say that at work before the stupid-ass lockdown
05:37:31 <mj-xmr> gb
06:01:40 <mj-xmr> Sorry. Wrong window.
06:02:11 <syzdlpuhjtd> Word of guys running Monero community should be BELIEVED. Why would anyone that stole money and laughed at the losers that took the bait ever have a reason to lie to you? http://removeddit.com/r/Monero/comments/6d6okb/fluffypony_needs_to_give_up_his_commit_access_and/ (changed link to removeddit since /r/monero mod removed to try to cover it up - maybe fluffy himself?)
13:54:49 <askvjeqp> Will you HODL XMR or dump it for Tari when it comes out? Will others?
19:44:54 <gingeropolous> moneromooo, so does all this work enough to be implemented, say, in wownero? https://github.com/moneromooo-monero/bitmonero/commit/20873b6ade3d5418518dd67678b5831445bae130
19:55:34 <moneromooo> Hopefully well enough to add it to monero ^^_
19:55:41 <moneromooo> It's not quite the most recent version though IIRC.
19:55:53 <moneromooo> It's also on top of BP+.
20:04:20 <gingeropolous> <moneromooo> Hopefully well enough to add it to monero ^^_ <<< indeed! I just meant, its all there sans audits
20:05:46 <gingeropolous> re: most recent. hrm. but, is that regarding optimizations? or some fundamental cryptomaths that could break consensus
20:08:00 <gingeropolous> welp, wowario is keen to implement on wownero
20:08:36 <gingeropolous> regardless of multisig etc
20:09:23 <moneromooo> I don't remember tbh. I just remember I made some small changes after pushing.
20:09:34 <moneromooo> I'll push latest later.
20:13:41 <moneromooo> Pushed.
20:13:48 <moneromooo> WIP branch, etc etc.
20:14:00 <moneromooo> But all tests pass bar multisig.
20:38:36 <rehrar> hey devs, so don't know if you knew this, but xiphon and I (but mostly xiphon) have worked out a way to avoid the fuk spam. We have monero-guard. He's a bot that works as follows.
20:39:24 <rehrar> We put the room to voiced-only mode, and manually voice people. Monero Guard remembers who is voiced so if they dc and reconnect, they'll be auto voiced. It also remembers voices across rooms, so someone voiced in #monero would be voiced here too.
20:40:11 <rehrar> The trade-off is that some new joiners will need to be voiced before they can speak (obviously), and though the fuk spam will stop, there will be many of the 'monero-guard voiced this person' kind of thing, which can also be spammy. Just wanted to know if you guys were interested in that for this room.
20:40:34 <rehrar> One option is to try it out and if you hate it we go back to the other way. It's not all or nothing here.
20:40:56 <rehrar> Just if you're getting super sick of the fuk spam we've got a way to mitigate it, with some trade-offs.
20:41:23 <moneromooo> I'd go for it. I could be arsed making those changes to tippero so thanks -_-
20:41:40 <moneromooo> FWIW I've not seen any spam for a while now, it's always the same (or similar) messages.
20:42:07 <moneromooo> The thing I wanted to do is auto voice after a delay after connect (longer delay for rr.com, spectrum etc)
20:42:29 <moneromooo> The cunt might adapt, but then you can just revert to manual.
20:44:23 <rehrar> askvjeqp> Will you HODL XMR or dump it for Tari when it comes out? Will others?
20:44:27 <rehrar> this was just today
20:44:52 <rehrar> Seven hours ago.
20:45:04 <rehrar> And they're quite annoying for sure. :P
20:47:07 <rehrar> moneromooo: if you're down for it, all you need to do is op monero-guard (set him to autoop), set the room to voiced only, and then voice current people
20:47:16 <rehrar> if you give me temp powers I can do the voicing for you
20:47:44 <moneromooo> I'm not op here.
20:48:03 <rehrar> so it would seem
20:48:23 <rehrar> fluffypony luigi1111  luigi1111w binaryFate can you I get opd to make the changes? :)
21:25:23 <kinghat[m]> how do new comers get voiced? PMs?
21:33:01 <nioc> mooooooooo
21:56:25 <luigi1111w> kinghat[m] it happens automagically
21:57:13 <kinghat[m]> just remember the little ppl
22:01:14 <luigi1111w> it seems to have missed a bunch of people
22:03:05 <ndorf> get_info daemon RPC response includes two fields, credits and top_hash which are never set (always 0/empty). is it ok to remove them? ... would that need a major version bump?
22:05:12 <moneromooo> Did you try it with rcp payment enabled ?
22:07:33 <ndorf> nevermind. i had misread the code and thought it never set them for that call
22:45:05 <ndorf> would it be fair to say that block_size_{limit,median} fields of get_info response are deprecated in favor of block_weight_X, and the documentation should only mention the latter?
22:48:46 <moneromooo> IIRC, yes.
22:49:24 <ndorf> thanks.
22:50:17 <ndorf> they're always they same value, *size* seems to be dating back to before fork v5.
23:44:21 <lu4p[m]> Hey I'm trying to understand how RandomX works.
23:44:21 <lu4p[m]> I roughly know how the mining part works, but neither the spec nor design document (https://github.com/tevador/RandomX) touch on how all this work is actually validated by other peers.
23:44:22 <lu4p[m]> Can you give me some pointers?
23:46:09 <kinghat[m]> freenode_lu4p[m]: #monero-pow
23:46:54 <moneromooo> Same way it's mined: the validator calculates the hash in the same way from the supplied block data, then compares with the target, same as the miner did.
23:47:09 <moneromooo> There's no shortcut there.