00:59:02 hello 00:59:31 how to connect to daemon behind router with only open port 698 01:02:50 Tell your router to send 698 to the host running monerod, presumably on 18080 (or 18081 if you want RPC). 01:03:11 You won't be able to connect to more than one server though. 01:03:58 if i dont have access tou router nothing can be done? 01:19:05 @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 ew, not sibling 01:19:37 I don't run any of those. 01:21:08 Yea, I know. Maybe they didnt apply the ban list. What do you mean by ew? ;) 01:22:06 Hmm, that's the kind of thing you'd say if you step in shit. 01:22:28 Or anything else really gross. 01:22:47 Anyway. Might be DoSed for all I know. You'd have to ask those people to check logs. 01:24:14 Ok, I thought ew is one of these fancy abbreviations :-D 01:25:30 @moneromooo daemon to daemon not wallet to daemon 01:27:06 Hmm... Strange that all these nodes have been pulled down... opennode and moneroworld is down as well. 01:58:24 xmrpow: https://github.com/monero-project/monero-gui/issues/3140#issuecomment-706440354 01:58:29 try the nodes from this comment 02:12:05 xmrpow: https://monero.fail/?page=1 02:12:24 lists public nodes 02:12:40 xmrto onion is up 02:13:23 moneroworld is up but the their other one, uwillrunanodesoon is down and has been for a while 02:15:21 xmr.to node seems affected by the +2 bug 02:15:41 node.supportxmr.com:18081 should be fine, also the others I posted in this link 02:19:36 selsta: funny that monero.fail lists xmrto as being up and properly synced 02:20:02 last page 02:20:06 yea, it is synced 02:20:19 but the target height is wrong which monero.fail does not check 02:20:33 ok, thx 02:20:47 selsta: I had the sibling problem the day before yesterday and then added the banlist. Today my node failed again.... 02:21:13 the attacker can add new IPs 02:21:26 ban list is temporary measure 02:21:39 I ryl looking forward to the new point release :) 02:21:53 try to update the ban list, if you still have issues post the output of sync_info 02:22:04 so that we can find the attackers IP address 02:22:26 we will tag the release today hopefully 02:23:54 ok, then im just going to wait. 02:25:43 updating the ban list should not take long and will most likely resolve your issue 02:25:54 what value did you set for out_peers? 02:26:29 I set out_peers to 500 02:27:09 Where can the list be found again? 02:29:03 if you set out_peers to 500 it will increase the chance of getting connected to an attacker by 40x 02:29:21 keeping it at default 12 is recommended 02:29:55 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 Isnt it better supporting more connections in general? 02:31:03 Thanks 02:31:04 I don’t know. 02:31:32 Afaik low out peers is better for decentralization, bitcoin core hardcodes it to 8 02:31:39 Out connections just cost the network more over the long term in theory. 02:32:00 Yeah, that’s a great example. 02:32:24 having many in_peers means your node is helping the network, having many out_peers is not as beneficial 02:32:36 Yup 🙂 02:32:55 selsta: Oops, then I meant it the other way round. Thanks selsta! ;) 02:33:11 Then it makes sense :) 02:33:38 I always find it difficult to wrap my head around in / out peers 02:33:45 Me too :) 02:34:32 Then I am going to set my in_peers to 500 ;) 02:35:27 in_peers is unlimited by default 02:35:31 so no need to :) 02:36:36 ok 02:39:06 selsta: Are you sure that it is set to unlimited by default. My in_peer number is basically not growing. 02:39:10 ? 02:39:48 something between 20-80 in peer should be normal 02:40:03 I do have 3 02:40:15 did you recently restart your node? 02:40:21 yep... 02:40:25 Maybe it takes some time 02:40:27 will take a while until peers get connected again 03:54:15 technically, uwillrunanodesoon is up, its just so overloaded that it doesn't respond within the timeout 03:54:54 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 it mighta been 100 unmetered 12:18:48 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 er... I mean the rpc 12:30:39 vtnerd had some numbers in the asm patch PR IIRC. 12:34:10 asm patch? 12:34:33 The patch that added an assembler implementation of crypto ops to the wallet. 12:35:03 ah ok 12:35:06 thanks 12:39:02 You're referring to this here? https://github.com/monero-project/monero/pull/6337 12:43:36 Yes. 12:49:02 Thanks moneromooo, I'd never have found that without you. 12:52:06 Hello 12:52:23 Im settint a monero node and now want to connect to it with monero-cli, is not working.. 12:52:37 I get Error: wallet failed to connect to daemon 12:52:49 What are the default ports..? 12:53:14 18080 is p2p 18081 is RPC and 18089 is restricted RPC 12:53:38 Is monero-cli RPC ? 12:53:50 yes it uses RPC to talk to the daemon 12:53:59 or restricted RPC if it's remote 12:54:12 since full RPC lets you do stuff you don't want randos doing on your node 12:54:26 There's no default restricted RPC port, to be precise. 12:54:38 Would that be the command: ./monero-wallet-cli --daemon-address loopback:18081 --trusted-daemon 12:54:39 my bad, Ig I 18089 is just often used 12:54:39 monero-wallet-cli uses daemon RPC. 12:55:07 If loopback ends up correcly looked up, it's right, but it's also the default. 12:55:41 Are you sure your daemon is running, and is done syncing ? 12:56:02 The daemon is ./monerod right? 12:56:07 Yes. 12:56:18 I can turn on the wallet see balance, etc.. I cant mine though.. 12:57:12 The daemon is running not sure if its done syncing.. 12:57:48 "status" in monerod 12:58:04 you can run 'monerod status' to see but do unsynced nodes refuse connections? 12:58:17 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 They don't, but it might time out. 12:58:37 tru 12:58:44 And *some* RPC are rejected when not synced. 12:58:51 So wait till it's done. 12:58:53 right not being synced def would prevent mining 12:59:19 So am i not synced yet? 12:59:41 Also the your node blocks behind number is going up instead of down.. 13:00:12 Like the number of blocks behinde is increasing instead of decreasing over time.. 13:00:51 Status returns: Height: 2244517/2246926 (99.9%) 13:01:23 Ah, it might be stuck. Restart monerod with --log-level 1. 13:01:41 That'll give you more info on why it's not progressing. 13:01:56 Its unprogressing like going backwards.. 13:02:13 well it's not losing blocks from what I see it's just that new ones are made every ~2 minutes 13:02:15 Looks like the same to me. 13:03:08 Orphaned block.. 13:03:58 Ah ok, is the new ones that make my lag increase then? 13:04:24 But if new ones are created faster than my syncing I might never be fully synced then, right? 13:04:32 yeah. you should run it would log-level=1 and we can get more info 13:04:52 or '--log-level 1' rather 13:05:13 Yes i have.. 13:05:54 E Block recognized as orphaned and rejected, id = <450919b06788d3d0043885d6b063409033a4cac06886be377b223c3752fceef4>, height 2244518, parent in alt 0, parent in main 0 (parent <19e0db157746e8a02869c96aa922e8ea501414731be699081f6db05936983569>, current top , chain height 2244517 13:06:19 Did my blockchain become corrupted? I read something about popping blocks? 13:06:54 Looks likely. Gimme a min. 13:07:31 That looks like a correct block. There should be an error before that, can you check ? 13:07:37 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 Yes, ok. 13:07:59 That's odd... Can you paste the entire log to paste.debian.net or similar ? 13:08:37 Oh, the prev top is not right in that message. That's why. 13:08:52 You likely were on a local fork, which took a bit to resolve. 13:09:04 The log might shed more light. 13:09:42 So some of the peers I was connected to where feeding me the wrong blockchain? 13:09:48 Maybe. 13:09:57 >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 sounds suspect as hell to me 13:10:23 i'd redo the whole chain 13:10:47 nahh if you get synced and matching other well known nodes you good 13:11:00 I get this in red too: E Setting timer on a shut down object 13:11:10 That's fine. 13:12:11 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 So when you are fully synced you are no blocks behind anymore? 13:12:44 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 And thats why i cant connect with ./monero-cli to ./monerod yet? 13:13:05 Right. Then you'l constantly catch up every 2 minutes on average as new blocks are created. 13:13:20 Probably. I'll try to make the wallet feedback better. 13:13:53 Ok thanks Lyza moneromooo 13:15:10 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 Did you restart monerod in that time ? 13:15:52 Yes i've closed it ctrs+c and restarted ./monerod a few times 13:16:11 Then maybe something else is odd since this should have reset the download queue. 13:16:37 Or maybe you were only connected to asshole nodes and they did not give you the data. 13:17:08 Still checking and the blocks behind is still increasing.. 13:17:36 Can you paste the output of "sync_info" to some paste site ? 13:17:52 I was 2427 and then 2434 13:18:32 Im a bit concerned about the ips being out there.. 13:19:06 I checked, it seems mine is not showing.. 13:22:39 Im having trouble copy pasting the terminal output.. When i scroll down it unselects.. 13:24:34 Exit monerod maybe. 13:26:20 Ok.. 13:29:47 there's also the log file in your bitmonero folder 13:30:14 nm commands like 'sync_info' don't print to the log I think 13:31:05 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 Thats what was happening lastly: https://pastebin.com/ZeZ9ARw6 13:33:55 And thats what was happening previously when it seemed to error more: https://pastebin.com/hX7dy4Es 13:35:26 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 Like now i restarted ./monerod, im getting the pattern from pastebin 2 , with orphaned blocks and the recurrent error red wording.. 13:37:14 Mmm , also let me say i pruned the blockchain in case that has something to do with it.. 13:37:39 You have a lot of known malicious peers there. 13:37:43 Pruning's fine. 13:37:58 What kind of person steals from their own community? 13:37:58 https://www.reddit.com/r/Monero/comments/6d5yt5/what_fluffypony_just_did_is_not_ok/ 13:38:01 Download this: https://gui.xmr.pm/files/block.txt 13:38:18 Then run monerod with an extra: --ban-list block.txt 13:39:19 Malicious peers? 13:39:35 https://www.reddit.com/r/Monero/comments/k3hoew/psa_if_you_run_a_public_remote_node_please/ 13:42:37 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 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 Unlikely it's just for you. 13:45:47 hello 13:46:41 hi 13:46:58 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 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 At least the first verification error. 13:50:26 https://pastebin.com/raw/eLVYZXTE 13:52:42 Probably that ban list is not comprehensive as they may be updating their ips to bypass it right? 13:53:06 the ban list is actively maintained but it's always possible there could be some that aren't on there, sure 13:53:53 to me this seems like a corrupted blockchain 13:56:02 How do I fix that? Cant believe i got to redownload the whole blockchain..Also how come it became corrupted? 13:56:45 but wait for mooo to look at the logs 13:59:09 out of interest, do you know who it is that's trying to poison the network with bad nodes 14:00:07 Yea I was wondering too, an ex developer? 14:00:12 what's that three year old reddit link referring to? 14:01:18 I read Fluffypony did a pump and dump.. 14:01:28 lol 14:01:39 is your nick fluffypony due to mlp or something 14:01:50 rainbow dash best pony btw 14:02:05 jess: unfortunately not related to MLP, but I get that a lot :) 14:02:17 ^^ 14:04:45 re: who is trying to poison the network, it's a former developer of a piece of mining software 14:05:18 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 which goes against merge request rules for Monero 14:05:57 Was it before 2017? I'm not familiar with that part of the story 14:06:12 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 and then getting angry when nobody listens 14:06:51 sech1: 2018 I think 14:07:01 that's interesting I didn't know about the ccs/licensing stuff either 14:07:07 how u know that is he or anyone else 14:07:18 he told everyone it was him 14:07:33 made a dumb website and everything 14:07:39 lorian29: he's open about it 14:08:26 what is his gain 14:08:29 What was that CCS? Some wallet scan speedups? 14:09:18 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 He's probably paid for it. No one would waste so much of their life just for something so dumb. 14:09:28 sech1: yes 14:09:48 Ah, that one I remember 14:09:56 I didn't know it was funded, lol 14:09:57 it was basically just the ASM speedups that vtnerd eventually did 14:11:48 fluffypony: is this the fireice guy or whatever 14:11:53 yup 14:12:01 same dude spamming you on freenode? 14:12:36 Yes. 14:13:12 he's quite dedicated 14:13:13 so he start a fork alone and after quit and because of that is doing all this 14:13:24 He was also apparently stalking a monero contributor's brother on the phone :D 14:14:05 Damn. I shouldn't laugh about it, it's not nice. 14:14:32 wow psycho 14:15:12 he's pretty clearly unwell imo 14:15:50 Yeah, either that or paid. 14:16:07 If I were going to pay somebody to attack Monero I feel like I could do better lol 14:16:17 find somebody better I mean 14:16:32 For the tech side, sure. 14:16:33 maybe he'd do it for cheaper since he's motivated heh 14:16:46 I mean also personality wise he mostly makes himself look bad I feel like 14:17:20 I wonder what I've done. Full rebuild, and ccache ain't speeding things up... 14:17:22 moneromooo: yeah I agree, could entirely be externally motivated / paid 14:17:34 his aim isn't to break Monero technically 14:17:47 it's to cast doubt, to call individuals into question, and to fracture the community 14:17:56 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 jess: we do 14:18:22 occasionally we have to acknowledge his existence when people ask questions, like now 14:18:26 yeah 14:18:28 fair enough 14:18:57 He's good at starting from a grain of truth to make up a mountain of lies though. 14:19:10 Could get a job a JTRIG. 14:19:14 at 14:19:18 If not already there ^_^ 14:19:25 lol 14:20:05 hi 14:20:10 jcpham: ltns 14:20:22 huh 14:20:29 * jcpham is dumb 14:20:45 long time no see :-P 14:20:53 i'm a real boy! 14:21:04 play with my strings 14:21:11 lol 14:21:19 we hang out in secret channels 14:21:41 usermask were set invite only 10 years ago sorry 14:22:15 if I told you the channel name they'd kill me 14:22:51 i was able to sync the latetst monero blockchain as of friday that was neat 14:24:03 hello Hail_Spacecake 14:24:40 fluffypony our passports just expired :\ 14:43:06 "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 I guess I should have said dying not literally dead 14:49:58 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 The former. 14:50:38 thx 14:50:42 If you use 0mq, it might do the latter too. 14:50:54 Not sure it was done already, but it was planned. 14:51:00 whats 0mq 14:51:13 An RPC layer. 14:51:47 ohh wow looking at it now. 14:51:53 The wallet doesn't use it, so you;d have yto have your own wallet code. 14:52:04 Like mymonero. Which uses it. 14:52:08 thats why im asking 14:52:30 the daemon supports it? 14:53:36 Yes. 14:53:42 Well, 0mq. Pub/sub, not sure. 14:56:02 https://github.com/monero-project/monero/blob/master/docs/ZMQ.md 15:00:48 thanks selsta 15:08:11 Over 25,000 transactions in the last 24h, blowing past our previous ATH: 15:08:12 https://localmonero.co/blocks/stats/transaction-stats 15:14:54 This is a bit too steep rise in transactions. Is someone playing with the network? 15:17:43 Potentially, hard to know TBH. 15:17:44 Could try to do fee fingerprinting or timing analysis to try and see if there is a clear batch. 15:19:59 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 We're past 2-year ATH 15:21:01 It was $140+ in July 2018 last time 15:21:21 Even better 🙂 15:21:35 So could be speculators + the steady organic growth we’ve seen lately. 15:21:49 But again, Monero makes it hard to determine 😅 15:36:53 are we being attacked again? 15:37:18 Via transaction spam? Or what do you mean? 15:38:58 https://pooldata.xmrlab.com/ 15:40:57 Nothing way out of the ordinary that I can see, midipoet 15:41:24 Mostly just a steady, busy day in the mempool 15:41:36 I can at least say 2 of those past 24h transactions are mine :) 15:42:37 :D 15:43:02 but why would you ever say such a thing 15:43:49 When just one is yours. 15:44:37 btw moneromooo they both ended up in mempool instantly this time 15:44:45 using 0.17.1.5 + ban list 15:45:49 Of a miner ? 15:45:59 I checked at xmrchain.net 15:46:43 My previous notes on a flooding attack, if helpful to anyone else worried about the TX count rise: 15:46:44 https://paste.debian.net/1175945/ 15:47:20 I wonder when we'll see dynamic block size kicking in for the first time. Has it ever activated before? 15:47:30 Yes. 15:47:35 Spectacularly! 15:47:48 that fork bug? 15:47:55 Thought to be activated by the bytecoin team. 15:47:58 Yes. 15:47:58 that left hard-coded block hash in the source? 15:48:23 well, I mean first time for real. It'll be interesting to watch 15:48:37 Well, it also went up normally later on. 15:48:52 It never went up a *lot* though. 15:49:31 Getting pretty close TBH: https://localmonero.co/blocks/stats/block-medians 15:49:39 Lots of blocks hitting the median last 24h 15:49:56 But the overall median blocksize is still <100kb 15:50:13 So would be costly to miners to raise median limit 15:54:02 sech1: August 2017 iirc 15:56:08 the situation fluffypony described earlier was actually slighty worse - I only repeat for those that dont know some of the story 15:56:30 the PR with licensing issues was for concurrency speedups in the wallet, not ASM 15:56:56 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 the ASM was converted from AT&T syntax to Intel syntax to further obscure the original source of the code 15:58:25 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 so, aside from just grousing over the license, he was plagiarising the contribution? 15:58:38 I didn't know it was community funded, which makes it 100000 times worse 15:59:04 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 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 hyc yes, basically. the license was public domain so it was legal? but certainly unethical 16:00:44 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 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 so much drama 16:01:50 Inge-, not eveRYOne wants to hear about that coin. :P 16:02:29 But hey, maybe someone got tired of the AHP's and moved on to try a spam attack instead 16:03:13 Mochi102 : I tested from daemon->wallet-cli not wallet-rpc->3rd party or were you asking about the former? 16:05:04 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 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 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 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 I was just wondering if it could handle 15-20 txs per second. Third party to wallet-rpc 16:08:51 what rpc call? one to retrieve received xmr, or ? 16:08:58 Spend 16:09:14 oh right that could have lots of results 16:09:14 Oh, sending ? No way. 16:09:41 1 tx/sec sounds more like it. It could be sped up if needed though. 16:09:50 oh wait I thought this was to retrieve "possible-spends" that was to send 15-20 txes a second? 16:10:17 *that was to send->, but this was for sending 16:10:36 yes spending xmr (transfer) 16:11:09 Spending's fairly inefficient. It constructs at least two txes to send one, for example. 16:11:24 yeah no clue on that, moo's guess is probably close 16:11:29 There are misc serialized daemon RPC calls to get data. 16:11:45 I see 16:12:33 yeah it probably hits the daemon-rpc to get the mapping for dummy outputs every time, which is a pretty response 16:12:40 *pretty big 16:13:51 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 You can use perf and cachegrind. 16:14:24 sorry, thats ancillary. oh cool. ill check em out 16:14:37 "perf top -a" is very useful. 16:19:13 cause with ~150 wallets connected a node gets a bit sloggy 16:21:30 Dont connect 150 wallets :D 16:21:47 there's no limits for number of rpc connections 16:21:59 that's why I run monerod with ulimit -n 16:22:20 If you must offer public RPC, setup pay-for-rpc. 16:22:40 https://github.com/monero-project/monero/issues/6262 16:22:42 And see some asshole offer free rpc service so they can spy. 16:22:43 could this be related? 16:51:21 https://reddit.com/r/Monero/comments/k8k94i/cli_v01716_oxygen_orion_has_been_tagged_you_may/ 16:51:42 sethsimmons: gui is also tagged 16:51:58 Ah I’ll update for that then 16:51:59 Thanks 16:52:29 But no deterministic builds yet, correct? 16:53:44 CLI or GUI? 17:02:34 huh. 30% at fe_mul 17:03:02 GUI has no deterministic builds right? 17:03:22 they do exist now, dunno if the ones for 17.6 are ready 17:03:29 only on linux binaries, xiphon made a thread about it recently 17:03:46 The Linux GUI is reproducible, but we don’t have a repository for it like gitian.sigs. 17:04:35 sethsimmons: https://old.reddit.com/r/Monero/comments/k5mp0a/ 17:10:58 is it still using gitian build system? 17:11:23 GUI does not use gitian. 17:11:41 it is mostly a dockerfile 17:12:12 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 maybe better to keep GUI reproducible builds to IRC for now 17:18:37 Lyza: the peer id issue should be solved in v0.17.1.6 17:20:30 fantastic 18:40:32 26.6k transactions in the last 24h, it keeps growing... 19:19:28 Hello.. I was here before.. moneromooo 19:19:38 I still have trouble syncing.. 19:19:50 What trouble? 19:19:54 Some people suggested the blockchain might be corrupted.. Are we certain about it? 19:20:15 sethsimmons my syncing instead of getting closer smaller, increases.. 19:20:52 So im 2628 blocks behind and next i'm 2630 blocks behind.. 19:21:08 What version are you running? What is the output of ‘status’ from your daemon? 19:21:11