00:59:02 <donbas> hello
00:59:31 <donbas> how to connect to daemon behind router with only open port 698
01:02:50 <moneromooo> Tell your router to send 698 to the host running monerod, presumably on 18080 (or 18081 if you want RPC).
01:03:11 <moneromooo> You won't be able to connect to more than one server though.
01:03:58 <donbas> if i dont have access tou router nothing can be done?
01:19:05 <xmrpow> @moneromoo: Are there some issues with open public nodes? xmr.to , hashvault.pro  etc nodes seem to be down... Is this still our sibling guy?
01:19:26 <moneromooo> ew, not sibling
01:19:37 <moneromooo> I don't run any of those.
01:21:08 <xmrpow> Yea, I know. Maybe they didnt apply the ban list. What do you mean by ew? ;)
01:22:06 <moneromooo> Hmm, that's the kind of thing you'd say if you step in shit.
01:22:28 <moneromooo> Or anything else really gross.
01:22:47 <moneromooo> Anyway. Might be DoSed for all I know. You'd have to ask those people to check logs.
01:24:14 <xmrpow> Ok, I thought ew is one of these fancy abbreviations :-D
01:25:30 <donbas> @moneromooo  daemon to daemon not wallet to daemon
01:27:06 <xmrpow> Hmm... Strange that all these nodes have been pulled down... opennode and moneroworld is down as well.
01:58:24 <selsta> xmrpow: https://github.com/monero-project/monero-gui/issues/3140#issuecomment-706440354
01:58:29 <selsta> try the nodes from this comment
02:12:05 <nioc> xmrpow:  https://monero.fail/?page=1
02:12:24 <nioc> lists public nodes
02:12:40 <nioc> xmrto onion is up
02:13:23 <nioc> moneroworld is up but the their other one, uwillrunanodesoon is down and has been for a while
02:15:21 <selsta> xmr.to node seems affected by the +2 bug
02:15:41 <selsta> node.supportxmr.com:18081 should be fine, also the others I posted in this link
02:19:36 <nioc> selsta: funny that monero.fail lists xmrto as being up and properly synced
02:20:02 <nioc> last page
02:20:06 <selsta> yea, it is synced
02:20:19 <selsta> but the target height is wrong which monero.fail does not check
02:20:33 <nioc> ok, thx
02:20:47 <xmrpow> selsta: I had the sibling problem the day before yesterday and then added the banlist. Today my node failed again....
02:21:13 <selsta> the attacker can add new IPs
02:21:26 <selsta> ban list is temporary measure
02:21:39 <xmrpow> I ryl looking forward to the new point release :)
02:21:53 <selsta> try to update the ban list, if you still have issues post the output of sync_info
02:22:04 <selsta> so that we can find the attackers IP address
02:22:26 <selsta> we will tag the release today hopefully
02:23:54 <xmrpow> ok, then im just going to wait.
02:25:43 <selsta> updating the ban list should not take long and will most likely resolve your issue
02:25:54 <selsta> what value did you set for out_peers?
02:26:29 <xmrpow> I set out_peers to 500
02:27:09 <xmrpow> Where can the list be found again?
02:29:03 <selsta> if you set out_peers to 500 it will increase the chance of getting connected to an attacker by 40x
02:29:21 <selsta> keeping it at default 12 is recommended
02:29:55 <selsta> should be enough to solve your issue most likely, but still here is the latest version: https://gui.xmr.pm/files/block.txt
02:30:13 <xmrpow> Isnt it better supporting more connections in general?
02:31:03 <xmrpow> Thanks
02:31:04 <selsta> I don’t know.
02:31:32 <selsta> Afaik low out peers is better for decentralization, bitcoin core hardcodes it to 8
02:31:39 <sethsimmons> <xmrpow "Isnt it better supporting more c"> Out connections just cost the network more over the long term in theory.
02:32:00 <sethsimmons> <selsta "Afaik low out peers is better fo"> Yeah, that’s a great example.
02:32:24 <selsta> having many in_peers means your node is helping the network, having many out_peers is not as beneficial
02:32:36 <sethsimmons> Yup 🙂
02:32:55 <xmrpow> selsta: Oops, then I meant it the other way round. Thanks selsta! ;)
02:33:11 <xmrpow> Then it makes sense :)
02:33:38 <selsta> I always find it difficult to wrap my head around in / out peers
02:33:45 <xmrpow> Me too :)
02:34:32 <xmrpow> Then I am going to set my in_peers to 500 ;)
02:35:27 <selsta> in_peers is unlimited by default
02:35:31 <selsta> so no need to :)
02:36:36 <xmrpow> ok
02:39:06 <xmrpow> selsta: Are you sure that it is set to unlimited by default. My in_peer number is basically not growing.
02:39:10 <xmrpow> ?
02:39:48 <selsta> something between 20-80 in peer should be normal
02:40:03 <xmrpow> I do have 3
02:40:15 <selsta> did you recently restart your node?
02:40:21 <xmrpow> yep...
02:40:25 <xmrpow> Maybe it takes some time
02:40:27 <selsta> will take a while until peers get connected again
03:54:15 <gingeropolous> technically, uwillrunanodesoon is up, its just so overloaded that it doesn't respond within the timeout
03:54:54 <gingeropolous> i think its a bandwidth issue because system resources look fine. even though i thought i was payin for 1 gbps unmetered
03:55:02 <gingeropolous> it mighta been 100 unmetered
12:18:48 <Mochi102> Has anybody ever done tests to see what the limits for txs per time period that the monero-wallet-cli can do?
12:20:32 <Mochi102> er... I mean the rpc
12:30:39 <moneromooo> vtnerd had some numbers in the asm patch PR IIRC.
12:34:10 <Mochi102> asm patch?
12:34:33 <moneromooo> The patch that added an assembler implementation of crypto ops to the wallet.
12:35:03 <Mochi102> ah ok
12:35:06 <Mochi102> thanks
12:39:02 <Mochi102> You're referring to this here? https://github.com/monero-project/monero/pull/6337
12:43:36 <moneromooo> Yes.
12:49:02 <Mochi102> Thanks moneromooo, I'd never have found that without you.
12:52:06 <mrtrousers> Hello
12:52:23 <mrtrousers> Im settint a monero node and now want to connect to it with monero-cli, is not working..
12:52:37 <mrtrousers> I get Error: wallet failed to connect to daemon
12:52:49 <mrtrousers> What are the default ports..?
12:53:14 <Lyza> 18080 is p2p 18081 is RPC and 18089 is restricted RPC
12:53:38 <mrtrousers> Is monero-cli RPC ?
12:53:50 <Lyza> yes it uses RPC to talk to the daemon
12:53:59 <Lyza> or restricted RPC if it's remote
12:54:12 <Lyza> since full RPC lets you do stuff you don't want randos doing on your node
12:54:26 <moneromooo> There's no default restricted RPC port, to be precise.
12:54:38 <mrtrousers> Would that be the command: ./monero-wallet-cli --daemon-address loopback:18081 --trusted-daemon
12:54:39 <Lyza> my bad, Ig I 18089 is just often used
12:54:39 <moneromooo> monero-wallet-cli uses daemon RPC.
12:55:07 <moneromooo> If loopback ends up correcly looked up, it's right, but it's also the default.
12:55:41 <moneromooo> Are you sure your daemon is running, and is done syncing ?
12:56:02 <mrtrousers> The daemon is ./monerod right?
12:56:07 <moneromooo> Yes.
12:56:18 <mrtrousers> I can turn on the wallet see balance, etc.. I cant mine though..
12:57:12 <mrtrousers> The daemon is running not sure if its done syncing..
12:57:48 <moneromooo> "status" in monerod
12:58:04 <Lyza> you can run 'monerod status' to see but do unsynced nodes refuse connections?
12:58:17 <mrtrousers> Thats what monerod says:  Sync data returned a new top block candidate: 2244517 -> 2246925 [Your node is 2408 blocks (3.3 days) behind]
12:58:22 <moneromooo> They don't, but it might time out.
12:58:37 <Lyza> tru
12:58:44 <moneromooo> And *some* RPC are rejected when not synced.
12:58:51 <moneromooo> So wait till it's done.
12:58:53 <Lyza> right not being synced def would prevent mining
12:59:19 <mrtrousers> So am i not synced yet?
12:59:41 <mrtrousers> Also the your node blocks behind number is going up instead of down..
13:00:12 <mrtrousers> Like the number of blocks behinde is increasing instead of decreasing over time..
13:00:51 <mrtrousers> Status returns: Height: 2244517/2246926 (99.9%)
13:01:23 <moneromooo> Ah, it might be stuck. Restart monerod with --log-level 1.
13:01:41 <moneromooo> That'll give you more info on why it's not progressing.
13:01:56 <mrtrousers> Its unprogressing like going backwards..
13:02:13 <Lyza> well it's not losing blocks from what I see it's just that new ones are made every ~2 minutes
13:02:15 <moneromooo> Looks like the same to me.
13:03:08 <mrtrousers> Orphaned block..
13:03:58 <mrtrousers> Ah ok, is the new ones that make my lag increase then?
13:04:24 <mrtrousers> But if new ones are created faster than my syncing I might never be fully synced then, right?
13:04:32 <Lyza> yeah. you should run it would log-level=1 and we can get more info
13:04:52 <Lyza> or '--log-level 1' rather
13:05:13 <mrtrousers> Yes i have..
13:05:54 <mrtrousers> E Block recognized as orphaned and rejected, id = <450919b06788d3d0043885d6b063409033a4cac06886be377b223c3752fceef4>, height 2244518, parent in alt 0, parent in main 0 (parent <19e0db157746e8a02869c96aa922e8ea501414731be699081f6db05936983569>, current top <cb6abc4af9da93eafc70e75673382a9dabbb21e47b6a59cf577b92bb0cfe13db>, chain height 2244517
13:06:19 <mrtrousers> Did my blockchain become corrupted? I read something about popping blocks?
13:06:54 <moneromooo> Looks likely. Gimme a min.
13:07:31 <moneromooo> That looks like a correct block. There should be an error before that, can you check ?
13:07:37 <mrtrousers> Ok, now its working.. Before it was looping and periodically giving the orphan block error.. But now seems unstuck and moving forward..
13:07:42 <mrtrousers> Yes, ok.
13:07:59 <moneromooo> That's odd... Can you paste the entire log to paste.debian.net or similar ?
13:08:37 <moneromooo> Oh, the prev top is not right in that message. That's why.
13:08:52 <moneromooo> You likely were on a local fork, which took a bit to resolve.
13:09:04 <moneromooo> The log might shed more light.
13:09:42 <mrtrousers> So some of the peers I was connected to where feeding me the wrong blockchain?
13:09:48 <moneromooo> Maybe.
13:09:57 <Lyza> >3 days seems pretty far behind for an organic fork situation. I do wonder if it's our old friend the attacker
13:10:13 <raecarruth> sounds suspect as hell to me
13:10:23 <raecarruth> i'd redo the whole chain
13:10:47 <Lyza> nahh if you get synced and matching other well known nodes you good
13:11:00 <mrtrousers> I get this in red too: E Setting timer on a shut down object
13:11:10 <moneromooo> That's fine.
13:12:11 <moneromooo> I think it's fine, just a rare known problem, you seem to have "skipped" a block in download. I've seen that reported before, but it's very rare.
13:12:24 <mrtrousers> So when you are fully synced you are no blocks behind anymore?
13:12:44 <moneromooo> So you could not add the new block because you were missing the one just before it. A little hole. It resolved once you fetched that missing block.
13:12:57 <mrtrousers> And thats why i cant connect with ./monero-cli to ./monerod yet?
13:13:05 <moneromooo> Right. Then you'l constantly catch up every 2 minutes on average as new blocks are created.
13:13:20 <moneromooo> Probably. I'll try to make the wallet feedback better.
13:13:53 <mrtrousers> Ok thanks Lyza moneromooo
13:15:10 <mrtrousers> I spent a few hours trying to work it out, and seeing the blocks behind number increase was doing my head in..
13:15:26 <moneromooo> Did you restart monerod in that time ?
13:15:52 <mrtrousers> Yes i've closed it ctrs+c and restarted ./monerod a few times
13:16:11 <moneromooo> Then maybe something else is odd since this should have reset the download queue.
13:16:37 <moneromooo> Or maybe you were only connected to asshole nodes and they did not give you the data.
13:17:08 <mrtrousers> Still checking and the blocks behind is still increasing..
13:17:36 <moneromooo> Can you paste the output of "sync_info" to some paste site ?
13:17:52 <mrtrousers> I was 2427 and then 2434
13:18:32 <mrtrousers> Im a bit concerned about the ips being out there..
13:19:06 <mrtrousers> I checked, it seems mine is not showing..
13:22:39 <mrtrousers> Im having trouble copy pasting the terminal output.. When i scroll down it unselects..
13:24:34 <moneromooo> Exit monerod maybe.
13:26:20 <mrtrousers> Ok..
13:29:47 <Lyza> there's also the log file in your bitmonero folder
13:30:14 <Lyza> nm commands like 'sync_info' don't print to the log I think
13:31:05 <Lyza> but you can pull up monerod again when it's already running like, 'monerod sync_info' in the command prompt, it'll print the info then exit. then maybe full screen the term
13:32:52 <mrtrousers> Thats what was happening lastly: https://pastebin.com/ZeZ9ARw6
13:33:55 <mrtrousers> And thats what was happening previously when it seemed to error more: https://pastebin.com/hX7dy4Es
13:35:26 <mrtrousers> Dunno, part of me thinks if i just let it run ./monerod it will eventually sync but the other thinks that it might never sync meanwhile wasting resources..
13:36:36 <mrtrousers> Like now i restarted ./monerod, im getting the pattern from pastebin 2 , with orphaned blocks and the recurrent error red wording..
13:37:14 <mrtrousers> Mmm , also let me say i pruned the blockchain in case that has something to do with it..
13:37:39 <moneromooo> You have a lot of known malicious peers there.
13:37:43 <moneromooo> Pruning's fine.
13:37:58 <collectivev> What kind of person steals from their own community?
13:37:58 <collectivev> https://www.reddit.com/r/Monero/comments/6d5yt5/what_fluffypony_just_did_is_not_ok/
13:38:01 <moneromooo> Download this: https://gui.xmr.pm/files/block.txt
13:38:18 <moneromooo> Then run monerod with an extra: --ban-list block.txt
13:39:19 <mrtrousers> Malicious peers?
13:39:35 <Lyza> https://www.reddit.com/r/Monero/comments/k3hoew/psa_if_you_run_a_public_remote_node_please/
13:42:37 <mrtrousers> Was that targeted or they are just ther in the monero network connecting to whoever happens to turn up? I doubt it was targeted nobody knew i was startint to run a monero node, and I had no monero ports open so there was no tell..
13:43:50 <moneromooo> There's a known dishonest asshole that's been barking at us for years. He's now trying to degrade network operation by running lots of nodes that behave badly.
13:44:00 <moneromooo> Unlikely it's just for you.
13:45:47 <lorian29> hello
13:46:41 <moneromooo> hi
13:46:58 <mrtrousers> Ok, I got those malicous nodes banned.. Blocks behind is still increasing though, at a far bigger rate than a block per 2 min..
13:47:55 <moneromooo> Then I need to see the level 1 log from the start of your run. You pasted part of the log only.
13:49:29 <moneromooo> At least the first verification error.
13:50:26 <mrtrousers> https://pastebin.com/raw/eLVYZXTE
13:52:42 <mrtrousers> Probably that ban list is not comprehensive as they may be updating their ips to bypass it right?
13:53:06 <Lyza> the ban list is actively maintained but it's always possible there could be some that aren't on there, sure
13:53:53 <selsta> to me this seems like a corrupted blockchain
13:56:02 <mrtrousers> How do I fix that? Cant believe i got to redownload the whole blockchain..Also how come it became corrupted?
13:56:45 <selsta> but wait for mooo to look at the logs
13:59:09 <jess> out of interest, do you know who it is that's trying to poison the network with bad nodes
14:00:07 <mrtrousers> Yea I was wondering too, an ex developer?
14:00:12 <Ymgve> what's that three year old reddit link referring to?
14:01:18 <mrtrousers> I read Fluffypony did a pump and dump..
14:01:28 <fluffypony> lol
14:01:39 <jess> is your nick fluffypony due to mlp or something
14:01:50 <jess> rainbow dash best pony btw
14:02:05 <fluffypony> jess: unfortunately not related to MLP, but I get that a lot :)
14:02:17 <jess> ^^
14:04:45 <fluffypony> re: who is trying to poison the network, it's a former developer of a piece of mining software
14:05:18 <fluffypony> he tried to contribute to Monero itself, and even raised funds from the CCS, but then when delivery time came he had all sorts of strings attached via a weird license
14:05:35 <fluffypony> which goes against merge request rules for Monero
14:05:57 <sech1> Was it before 2017? I'm not familiar with that part of the story
14:06:12 <fluffypony> so he got all butthurt and left to start a Monero fork, and instead of just quietly working on things he's spent the last few years attacking Monero
14:06:21 <fluffypony> and then getting angry when nobody listens
14:06:51 <fluffypony> sech1: 2018 I think
14:07:01 <Lyza> that's interesting I didn't know about the ccs/licensing stuff either
14:07:07 <lorian29> how u know that is he or anyone else
14:07:18 <Lyza> he told everyone it was him
14:07:33 <Lyza> made a dumb website and everything
14:07:39 <fluffypony> lorian29: he's open about it
14:08:26 <lorian29> what is his gain
14:08:29 <sech1> What was that CCS? Some wallet scan speedups?
14:09:18 <Lyza> <lorian29> I think it's more personal but he did fork the Monero code to create a competing currency so, there's that. seems like a dead project though.
14:09:24 <moneromooo> He's probably paid for it. No one would waste so much of their life just for something so dumb.
14:09:28 <fluffypony> sech1: yes
14:09:48 <sech1> Ah, that one I remember
14:09:56 <sech1> I didn't know it was funded, lol
14:09:57 <fluffypony> it was basically just the ASM speedups that vtnerd eventually did
14:11:48 <jess> fluffypony: is this the fireice guy or whatever
14:11:53 <fluffypony> yup
14:12:01 <jess> same dude spamming you on freenode?
14:12:36 <moneromooo> Yes.
14:13:12 <jess> he's quite dedicated
14:13:13 <lorian29> so he start a fork alone and after quit and because of that is doing all this
14:13:24 <moneromooo> He was also apparently stalking a monero contributor's brother on the phone :D
14:14:05 <moneromooo> Damn. I shouldn't laugh about it, it's not nice.
14:14:32 <lorian29> wow psycho
14:15:12 <Lyza> he's pretty clearly unwell imo
14:15:50 <moneromooo> Yeah, either that or paid.
14:16:07 <Lyza> If I were going to pay somebody to attack Monero I feel like I could do better lol
14:16:17 <Lyza> find somebody better I mean
14:16:32 <moneromooo> For the tech side, sure.
14:16:33 <Lyza> maybe he'd do it for cheaper since he's motivated heh
14:16:46 <Lyza> I mean also personality wise he mostly makes himself look bad I feel like
14:17:20 <moneromooo> I wonder what I've done. Full rebuild, and ccache ain't speeding things up...
14:17:22 <fluffypony> moneromooo: yeah I agree, could entirely be externally motivated / paid
14:17:34 <fluffypony> his aim isn't to break Monero technically
14:17:47 <fluffypony> it's to cast doubt, to call individuals into question, and to fracture the community
14:17:56 <jess> i've got a bit of experience with trolls and i think the best advice i could give is pretend he doesn't exist
14:18:10 <fluffypony> jess: we do
14:18:22 <fluffypony> occasionally we have to acknowledge his existence when people ask questions, like now
14:18:26 <jess> yeah
14:18:28 <jess> fair enough
14:18:57 <moneromooo> He's good at starting from a grain of truth to make up a mountain of lies though.
14:19:10 <moneromooo> Could get a job a JTRIG.
14:19:14 <moneromooo> at
14:19:18 <moneromooo> If not already there ^_^
14:19:25 <fluffypony> lol
14:20:05 <jcpham> hi
14:20:10 <fluffypony> jcpham: ltns
14:20:22 <jcpham> huh
14:20:29 * jcpham is dumb
14:20:45 <fluffypony> long time no see :-P
14:20:53 <jcpham> i'm a real boy!
14:21:04 <jcpham> play with my strings
14:21:11 <fluffypony> lol
14:21:19 <jcpham> we hang out in secret channels
14:21:41 <jcpham> usermask were set invite only 10 years ago sorry
14:22:15 <jcpham> if I told you the channel name they'd kill me
14:22:51 <jcpham> i was able to sync the latetst monero blockchain as of friday that was neat
14:24:03 <jcpham> hello Hail_Spacecake
14:24:40 <jcpham> fluffypony our passports just expired :\
14:43:06 <nos411> <Lyza> "seems like a dead project though."  RYO's still kicking, not that I always agree with the tact used to engage with others.
14:43:36 <Lyza> I guess I should have said dying not literally dead
14:49:58 <donkeydonkey[m]> is the wallet polling the monero daemon for new transactions or does it make some soft or bidirectional connection where the daemon can push updates to the wallet?
14:50:13 <moneromooo> The former.
14:50:38 <donkeydonkey[m]> thx
14:50:42 <moneromooo> If you use 0mq, it might do the latter too.
14:50:54 <moneromooo> Not sure it was done already, but it was planned.
14:51:00 <donkeydonkey[m]> whats 0mq
14:51:13 <moneromooo> An RPC layer.
14:51:47 <donkeydonkey[m]> ohh wow looking at it now.
14:51:53 <moneromooo> The wallet doesn't use it, so you;d have yto have your own wallet code.
14:52:04 <moneromooo> Like mymonero. Which uses it.
14:52:08 <donkeydonkey[m]> thats why im asking
14:52:30 <donkeydonkey[m]> the daemon supports it?
14:53:36 <moneromooo> Yes.
14:53:42 <moneromooo> Well, 0mq. Pub/sub, not sure.
14:56:02 <selsta> https://github.com/monero-project/monero/blob/master/docs/ZMQ.md
15:00:48 <donkeydonkey[m]> thanks selsta
15:08:11 <sethsimmons> Over 25,000 transactions in the last 24h, blowing past our previous ATH:
15:08:12 <sethsimmons> https://localmonero.co/blocks/stats/transaction-stats
15:14:54 <sech1> This is a bit too steep rise in transactions. Is someone playing with the network?
15:17:43 <sethsimmons> Potentially, hard to know TBH.
15:17:44 <sethsimmons> Could try to do fee fingerprinting or timing analysis to try and see if there is a clear batch.
15:19:59 <sethsimmons> We also are well past our previous yearly ATH in USD and climbing vs BTC so could be speculators rushing onto/off exchanges
15:20:14 <sech1> We're past 2-year ATH
15:21:01 <sech1> It was $140+ in July 2018 last time
15:21:21 <sethsimmons> Even better 🙂
15:21:35 <sethsimmons> So could be speculators + the steady organic growth we’ve seen lately.
15:21:49 <sethsimmons> But again, Monero makes it hard to determine 😅
15:36:53 <midipoet> are we being attacked again?
15:37:18 <sethsimmons> Via transaction spam? Or what do you mean?
15:38:58 <sethsimmons> https://pooldata.xmrlab.com/
15:40:57 <sethsimmons> Nothing way out of the ordinary that I can see, midipoet
15:41:24 <sethsimmons> Mostly just a steady, busy day in the mempool
15:41:36 <sech1> I can at least say 2 of those past 24h transactions are mine :)
15:42:37 <sethsimmons> :D
15:43:02 <hyc> but why would you ever say such a thing
15:43:49 <moneromooo> When just one is yours.
15:44:37 <sech1> btw moneromooo they both ended up in mempool instantly this time
15:44:45 <sech1> using 0.17.1.5 + ban list
15:45:49 <moneromooo> Of a miner ?
15:45:59 <sech1> I checked at xmrchain.net
15:46:43 <sethsimmons> My previous notes on a flooding attack, if helpful to anyone else worried about the TX count rise:
15:46:44 <sethsimmons> https://paste.debian.net/1175945/
15:47:20 <sech1> I wonder when we'll see dynamic block size kicking in for the first time. Has it ever activated before?
15:47:30 <moneromooo> Yes.
15:47:35 <moneromooo> Spectacularly!
15:47:48 <sech1> that fork bug?
15:47:55 <moneromooo> Thought to be activated by the bytecoin team.
15:47:58 <moneromooo> Yes.
15:47:58 <sech1> that left hard-coded block hash in the source?
15:48:23 <sech1> well, I mean first time for real. It'll be interesting to watch
15:48:37 <moneromooo> Well, it also went up normally later on.
15:48:52 <moneromooo> It never went up a *lot* though.
15:49:31 <sethsimmons> Getting pretty close TBH: https://localmonero.co/blocks/stats/block-medians
15:49:39 <sethsimmons> Lots of blocks hitting the median last 24h
15:49:56 <sethsimmons> But the overall median blocksize is still <100kb
15:50:13 <sethsimmons> So would be costly to miners to raise median limit
15:54:02 <dEBRUYNE> sech1: August 2017 iirc
15:56:08 <vtnerd> the situation fluffypony described earlier was actually slighty worse - I only repeat for those that dont know some of the story
15:56:30 <vtnerd> the PR with licensing issues was for concurrency speedups in the wallet, not ASM
15:56:56 <vtnerd> the ASM speedups came later as a separate library for self-promotion. all of the comments from the original source were stripped, including original authors name
15:57:15 <vtnerd> the ASM was converted from AT&T syntax to Intel syntax to further obscure the original source of the code
15:58:25 <sech1> I remember all of that, he created a lot of buzz around that time and ended up starting ryo and integrating all that code there
15:58:33 <hyc> so, aside from just grousing over the license, he was plagiarising the contribution?
15:58:38 <sech1> I didn't know it was community funded, which makes it 100000 times worse
15:59:04 <vtnerd> the changes made by him were primarily already done in my working branch that was public, but Im not sure if that was used as a reference
15:59:23 <vtnerd> it took a while because I had to change some of the crypto code to make it work with dynamic libs and constant time
16:00:15 <vtnerd> hyc yes, basically. the license was public domain so it was legal? but certainly unethical
16:00:44 <Mochi102> vtnerd, did you ever bombard the wallet-rpc with tx requests to see when it would be saturated? (assuming you had all the outputs you ever needed)
16:01:08 <Inge-> sech1: actually, he joined SUMO, but later (According to him) found out that there was a hidden premine or something, and the community split into SUMO and Ryo
16:01:24 <sech1> so much drama
16:01:50 <Mochi102> Inge-, not eveRYOne wants to hear about that coin. :P
16:02:29 <Inge-> But hey, maybe someone got tired of the AHP's and moved on to try a spam attack instead
16:03:13 <vtnerd> Mochi102 : I tested from daemon->wallet-cli not wallet-rpc->3rd party or were you asking about the former?
16:05:04 <vtnerd> I've done various tests to determine limits of serialization code, but it was a bunch of direct timings. I have not tested to see full lmdb->wallet-cli timings
16:06:20 <moneromooo> The PR has timings, like 17 minutes for 2 million blocks or so. That's something like 16 million outputs IIRC, very roughly.
16:06:24 <vtnerd> my numbers on a 3900x were indicating that the crypto code may not be the bottleneck on bigger cache cpus. I didn't fully look into though
16:07:38 <vtnerd> this was a 3900x, with a 970pro (but encrypted) and fast ram recommended for mining, so it was on the edge of what an "average" person would have
16:07:43 <Mochi102> I was just wondering if it could handle 15-20 txs per second. Third party to wallet-rpc
16:08:51 <vtnerd> what rpc call? one to retrieve received xmr, or ?
16:08:58 <Mochi102> Spend
16:09:14 <vtnerd> oh right that could have lots of results
16:09:14 <moneromooo> Oh, sending ? No way.
16:09:41 <moneromooo> 1 tx/sec sounds more like it. It could be sped up if needed though.
16:09:50 <vtnerd> oh wait I thought this was to retrieve "possible-spends" that was to send 15-20 txes a second?
16:10:17 <vtnerd> *that was to send->, but this was for sending
16:10:36 <Mochi102> yes spending xmr (transfer)
16:11:09 <moneromooo> Spending's fairly inefficient. It constructs at least two txes to send one, for example.
16:11:24 <vtnerd> yeah no clue on that, moo's guess is probably close
16:11:29 <moneromooo> There are misc serialized daemon RPC calls to get data.
16:11:45 <Mochi102> I see
16:12:33 <vtnerd> yeah it probably hits the daemon-rpc to get the mapping for dummy outputs every time, which is a pretty response
16:12:40 <vtnerd> *pretty big
16:13:51 <gingeropolous> id love a monero resources reporter, some data that shows what functions are using the most resources. i wonder if i could get it just by parsing a very verbose logfile
16:14:12 <moneromooo> You can use perf and cachegrind.
16:14:24 <gingeropolous> sorry, thats ancillary. oh cool. ill check em out
16:14:37 <moneromooo> "perf top -a" is very useful.
16:19:13 <gingeropolous> cause with ~150 wallets connected a node gets a bit sloggy
16:21:30 <moneromooo> Dont connect 150 wallets :D
16:21:47 <hyc> there's no limits for number of rpc connections
16:21:59 <hyc> that's why I run monerod with ulimit -n
16:22:20 <moneromooo> If you must offer public RPC, setup pay-for-rpc.
16:22:40 <selsta> https://github.com/monero-project/monero/issues/6262
16:22:42 <moneromooo> And see some asshole offer free rpc service so they can spy.
16:22:43 <selsta> could this be related?
16:51:21 <sethsimmons> https://reddit.com/r/Monero/comments/k8k94i/cli_v01716_oxygen_orion_has_been_tagged_you_may/
16:51:42 <selsta> sethsimmons: gui is also tagged
16:51:58 <sethsimmons> Ah I’ll update for that then
16:51:59 <sethsimmons> Thanks
16:52:29 <sethsimmons> But no deterministic builds yet, correct?
16:53:44 <selsta> CLI or GUI?
17:02:34 <gingeropolous> huh. 30% at fe_mul
17:03:02 <sethsimmons> GUI has no deterministic builds right?
17:03:22 <gingeropolous> they do exist now, dunno if the ones for 17.6 are ready
17:03:29 <tobtoht> only on linux binaries, xiphon made a thread about it recently
17:03:46 <selsta> The Linux GUI is reproducible, but we don’t have a repository for it like gitian.sigs.
17:04:35 <tobtoht> sethsimmons: https://old.reddit.com/r/Monero/comments/k5mp0a/
17:10:58 <hyc> is it still using gitian build system?
17:11:23 <selsta> GUI does not use gitian.
17:11:41 <selsta> it is mostly a dockerfile
17:12:12 <sethsimmons> tobtoht: Do you or someone else want to post asking for sigs of that? I don’t know enough detail to really do it TBH
17:13:49 <selsta> maybe better to keep GUI reproducible builds to IRC for now
17:18:37 <selsta> Lyza: the peer id issue should be solved in v0.17.1.6
17:20:30 <Lyza> fantastic
18:40:32 <sech1> 26.6k transactions in the last 24h, it keeps growing...
19:19:28 <mrtrousers> Hello.. I was here before.. moneromooo
19:19:38 <mrtrousers> I still have trouble syncing..
19:19:50 <sethsimmons> What trouble?
19:19:54 <mrtrousers> Some people suggested the blockchain might be corrupted.. Are we certain about it?
19:20:15 <mrtrousers> sethsimmons my syncing instead of getting closer smaller, increases..
19:20:52 <mrtrousers> So im 2628 blocks behind and next i'm 2630 blocks behind..
19:21:08 <sethsimmons> What version are you running? What is the output of ‘status’ from your daemon?
19:21:11 <nioc> did you delete the chain and sync again?
19:21:38 <mrtrousers> No.. What folder is the chain in?
19:22:00 <nioc> sorry what OS?
19:22:16 <mrtrousers> sethsimmons Height: 2244517/2244517 (100.0%)
19:22:24 <mrtrousers> Thats strange..
19:22:31 <mrtrousers> +nioc im in ubuntu 20.04
19:23:05 <nioc> sethsimmons: do you know where the chain is in linux?
19:23:13 <selsta> ~/.bitmonero/lmdb
19:23:28 <nioc> 2247151 is current height
19:23:29 <sethsimmons> Don’t need to delete I don’t think
19:23:38 <sethsimmons> You seem to be affected by the malicious peers
19:23:49 <selsta> sethsimmons: moo looked at it previously, it is a non obvious issue
19:23:51 <sethsimmons> What version are you running?
19:23:58 <sethsimmons> Oh nvm then
19:24:01 <sethsimmons> Seems like he’s eclipsed
19:24:15 <selsta> "sync_info" output would be interesting
19:24:20 <mrtrousers> nvm ? When i use status in monero-cli it says i'm synced..
19:24:27 <selsta> it is not synced
19:24:36 <sethsimmons> You’re not, you’re behind the network in reality
19:24:45 <selsta> can you run ./monerod, then in a second terminal enter ./monerod sync_info
19:24:48 <selsta> and then post the output
19:24:49 <sethsimmons> Please provide the output of `sync_info` from your daemon
19:24:52 <mrtrousers> So why is status saying i'm synced?
19:24:57 <mrtrousers> OK +selsta
19:24:58 <sethsimmons> I’ll let selsta handle this :)
19:25:14 <selsta> because your daemon does not know the real height so it thinks it is synced
19:25:18 <retarder> Can I trust MyMonero app?
19:26:33 <mrtrousers> Thats the output of sync_info: https://pastebin.com/raw/kevL7a0Z
19:27:02 <azy> link it retarder
19:27:21 <azy> https://mymonero.com/ " We do not currently have an Android application. Please DO NOT download a MyMonero application from the Google Play store. Any MyMonero Android application is fake, and you will risk losing all your funds!"
19:27:32 <retarder> https://github.com/mymonero/mymonero-app-js
19:27:59 <selsta> I would try to sync from scatch
19:28:05 <mrtrousers> So what should I do..? Also what is nvm ?
19:28:30 <mrtrousers> Ok.. Where is the blockchain.. What folder files do i delete?
19:28:41 <selsta> rm ~/.bitmonero/lmdb/data.mdb
19:29:17 <mrtrousers> Could i just delete the whole folder?
19:29:18 <moneromooo> mrtrousers: yes, the failure to find output 1 of whatever amount it was means the db is borked.
19:29:18 <Quotes> Feel bork inc.® https://www.youtube.com/watch?v=muLAN-kP5pE
19:29:37 <selsta> mrtrousers: yes
19:29:58 <moneromooo> monero-wallet-cli tells you whether the wallet is synced with the daemon.
19:30:04 <mrtrousers> Will it be faster to download the blockchain raw?
19:30:21 <moneromooo> Download yes, process it probably not.
19:30:37 <mrtrousers> Mmm, i dont understand..
19:30:37 <Quotes> But it's easy! https://www.youtube.com/watch?v=RXJKdh1KZ0w
19:30:49 <moneromooo> You want to use a SSD if you can, and bump the number of out peers to, say, 40, from the defualt. It'll speed it up.
19:31:13 <mrtrousers> moneromooo should i just restart ./monerod then ? How do i bump up to 40?
19:31:20 <mrtrousers> Im using an SSD
19:31:34 <moneromooo> "out_peers 40" in the monerod console
19:32:17 <mrtrousers> ./monerod --out_peers 40 ?
19:32:28 <moneromooo> Maybe. Check --help.
19:35:17 <mrtrousers> Well, it's starting from 0, cant believe it i spent  all last night doing that.. I will try one more time..
19:35:48 <mrtrousers> I have used the --ban-list command too..
19:35:53 <moneromooo> Hmm. Did you delete it already ?
19:36:05 <mrtrousers> moneromooo what means borked? Was that cause by the malicious nodes..?
19:36:07 <moneromooo> It's odd if you got it yesterday and it's borked already...
19:36:10 <moneromooo> No.
19:36:15 <mrtrousers> Yes i deleted it.. moneromoo
19:36:15 <moneromooo> borked means broken.
19:36:15 <Quotes> Feel bork inc.® https://www.youtube.com/watch?v=muLAN-kP5pE
19:36:19 <mrtrousers> bork
19:36:22 <mrtrousers> borked
19:36:33 <selsta> ./monerod --out-peers 40 --ban-list /path/to/block.txt
19:36:40 <selsta> would be the correct command ^
19:37:05 <mrtrousers> Ok, cools, thats what I did.. Will rebooting or restarting the computer while im downloading the blockchain and syncing break it?
19:37:43 <moneromooo> If you end up with hte same problem, try: output_histogram @55704670000 0
19:37:48 <moneromooo> It should output 2.
19:37:52 <selsta> you wrote --out_peers that’s why I wrote it again
19:38:13 <moneromooo> It should not, but if you use windows, it might.
19:38:28 <moneromooo> Best to exit monerod before shutting down your machine, just in case.
19:38:33 <selsta> force shutdown during sync can corrupt it
19:38:36 <Mochi102> With Windows you're able to potentially break anything.
19:38:39 <mrtrousers> ah ok +selsta i wrote it right in the console, thanks.
19:38:51 <mrtrousers> Im in ubuntu
19:41:34 <mrtrousers> Could it be related to pruning the blockchain before being fully synced? moneromoo +selsta
19:41:51 <selsta> how did you prune it?
19:42:08 <mrtrousers> ./monero-blockchain-prune
19:43:05 <mrtrousers> moneromooo so would the command ./monerod output_histogram @55704670000 0
19:43:12 <moneromooo> In theory, it should not... But it might be buggy.
19:43:29 <mrtrousers> have fixed the issue? Should i just restore the old blockchain and try it..?
19:43:42 <moneromooo> If you want to prune, restart monerod now with --prnue-blockchain. It's *much* faster if you prune from the start (or near start).
19:43:50 <moneromooo> No, it's a query only.
19:43:59 <mrtrousers> ok..
19:45:38 <mrtrousers> Is that command right: ./monerod --out-peers 40 --ban-list block.txt --prune-blockchain  ?
19:45:59 <mrtrousers> Can't tell from the output if its pruning or not..
19:47:09 <moneromooo> Yes, it's fine.
19:48:36 <mrtrousers> So pruning doesnt prune 1/3 of the blockchain, it prunes a 1/3 of each block.. right?
19:50:00 <mrtrousers> Lulz, i'm reading about pruning now.. anyways, thanks a lot for helping me with that issue, lulz
19:52:12 <moneromooo> Pruning dumps signatures, which take... maybe 2/3 of a tx on average, *very* roughly. And it dumps that for 7/8ths of the chain,
19:52:34 <moneromooo> All in all, it dumps about 2/3rds of the whole historical chain.
19:52:48 <moneromooo> ie, 100 GB -> 30 GB.
19:59:20 <mrtrousers> Ok thanks for helping with the technical..
19:59:56 <mrtrousers> Is monero the coin with more presence at defcon?
20:10:45 <mrtrousers> I saw there is a monero village and stuff..
20:13:35 <xmrmatterbridge> <agentpatience> lol wtf is a monero village
20:14:08 <sethsimmons> Yes there is a large Monero village at each DEFCON for the past few years
20:14:36 <sethsimmons> <xmrmatterbridge "<agentpatience> lol wtf is a mon"> Villages are the name for mini conferences at DEFCON each year with their own talks etc
21:44:44 <Inge-> 0.17.1.6 now? xmrchain is a little trigger happy - binaries not yet on getmonero.org?
21:45:19 <selsta> it is tagged, website release will be out tomorrow
21:45:19 <sethsimmons> Deterministic build verification is happening now so some early adopters are likely building from the tag and deploying.
21:45:26 <Inge-> cool
21:45:35 <Inge-> tl;dr or release notes out somewhere?
21:46:16 * sethsimmons sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/yUpEopLZtmhBvJHKMIksPlRn/message.txt >
21:46:24 <sethsimmons> From https://reddit.com/r/Monero/comments/k8k94i/cli_v01716_oxygen_orion_has_been_tagged_you_may/
21:46:50 <sethsimmons> Many more fixes of course but those are the high level changes
21:46:59 <sethsimmons> Lots of mitigations for the ongoing network attack.
21:47:36 <selsta> also drop peers that decrease their target height and drop peers that don’t reply to queries
21:48:18 <sethsimmons> Nice 😀
21:48:46 <selsta> and also drop peers that are idle for too long
22:22:13 <lorian29> hello
22:26:53 <while> hi
23:01:50 <donkeydonkey[m]> nice work y'all!
23:27:23 <kinghat[m]> so there was ways to automate it 😁
23:35:35 <lorian29> as i told u before this serialize_rctsig_base cant serialize block version > 3  but i cant replace with this one serialize_rctsig_prunable
23:49:01 <locustlord> when I left my node to sync
23:49:10 <locustlord> it had a segmentation fault 67% through
23:49:19 <locustlord> no other error, just "segmentation fault"
23:49:45 <locustlord> is there a way I can alert myself if this happens?
23:50:01 <locustlord> because I do not want this happening in production
23:50:40 <moneromooo> Oh, that's very bad. Unless it's lmdb, which likes to SIGSEGV on bad data.
23:50:51 <moneromooo> Try running in gdb.
23:50:58 <moneromooo> Then, if it crashes again: bt
23:53:10 <locustlord> how do I run it in gdb?
23:53:33 <locustlord> "sudo gdb monerod --stagenet --data-dir /mypathhere" ?
23:54:09 <locustlord> I turned it back on already and it hasn't crashed yet
23:54:33 <locustlord> I'm somewhat aware that a segmentation fault is a programmer thing, not a user thing.
23:54:41 <locustlord> so I'm happy to test it
23:55:10 <locustlord> hmm gdb command not found
23:55:50 <locustlord> I have apt installing gdb
23:56:40 <locustlord> I don't normally use gdb but in this case there's good reason to do it
23:56:45 <moneromooo> You don't need sudo .
23:56:49 <moneromooo> THen:
23:56:49 <selsta> try `gdb --args --stagenet --data-dir /mypathhere`
23:56:52 <moneromooo> gdb monerod
23:56:54 <moneromooo> run --stagenet --data-dir /mypathhere
23:57:01 <moneromooo> Or what selsta said, yes.
23:57:02 <selsta> ah wait, my comment was wrong :)
23:57:06 <selsta> monerod is missing
23:57:15 <selsta> `gdb --args monerod --stagenet --data-dir /mypathhere`
23:57:54 <locustlord> I do need sudo though because my directory needs root
23:58:35 <locustlord> the thing is I can't reproduce this bug
23:59:01 <locustlord> running that just brings me to the gdb prompt
23:59:07 <selsta> run
23:59:22 <locustlord> ah ok cool
23:59:30 <locustlord> it's doing its thing now
23:59:39 <selsta> if it crashes again enter "bt"
23:59:50 <locustlord> ok
23:59:57 <locustlord> it happened some time yesterday