02:05:09 <monerouser1144> Hi all, I noticed the following in monerod's log ("REORGANIZE on height"/"BLOCK ADDED AS ALTERNATIVE ON HEIGHT"/"REORGANIZE SUCCESS"). It's not something to worry about, is it? TIA http://paste.debian.net/1172779/
02:07:29 <monerouser1144> PS: I am using latest monerod v0.17.1.3 with the new --ban-list option using selsa's ban list.
02:08:24 <moneromooo> It's a catastrophe for whoever mined the block that got bumped.
02:08:37 <moneromooo> The one who mined the new one is very happy.
02:08:44 <moneromooo> Others don't really care.
02:10:40 <monerouser1144> OK, I just wanted to make sure it wasn't due to some new type of network attack. Thx.
02:59:24 <gingeropolous> .resolve donate.getmonero.org
02:59:29 <gingeropolous> !resolve donate.getmonero.org
04:37:38 <lza_menace> you figure it out gingeropolous?
04:38:30 <lza_menace> wowbux has that function (#wownero)
04:38:37 <lza_menace> but not sure if it resolves txt
07:16:47 <rbrunner> Test: Still needing voice to post directly on IRC?
07:17:13 <rbrunner> Seems not :)
07:17:35 <rbrunner> Let's see how long that holds ...
07:28:30 <Visionz[m]> Anybody else having syncing issues?
07:28:50 <Visionz[m]> For the past two days my wallet is not able to fully sync.
07:33:37 <selsta> Visionz[m]: use a custom remote node
07:34:01 <selsta> as explained here https://github.com/monero-project/monero-gui/issues/3140#issuecomment-706440354
07:38:09 <Visionz[m]> <selsta "Visionz: use a custom remote nod"> Awesome thanks. Is node.xmr.to usually more reliable?
07:38:32 <selsta> which remote node did you use? or were you using simple mode?
07:39:39 <selsta> see here for more information https://reddit.com/r/Monero/comments/jv8v2r/psa_if_you_run_a_public_remote_node_please/
07:39:41 <Visionz[m]> Simple mode.
07:40:24 <selsta> switching to an updated remote node solves this
07:40:34 <selsta> e.g. the xmr.to one
07:43:24 <Visionz[m]> <selsta "switching to an updated remote n"> Yes I did switch to xmr.to and it solved my issue. I was wondering if xmr.to send to be more reliable than others?
07:43:41 <Visionz[m]> * Yes I did switch to xmr.to and it solved my issue. I was wondering if xmr.to tends to be more reliable than others?
07:45:13 <selsta> difficult to say
09:29:57 <Visionz[m]> Ok. Thanks for the info though.
11:03:34 * liz[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/QcfysyRsIvQlxSRkDaFkjcPg/message.txt >
11:18:46 <selsta> liz[m]: in restricted mode this is not possible to avoid fingerprinting
12:17:40 <midipoet> https://www.hownormalami.eu/
12:17:44 <midipoet> might be off topic
12:17:56 <midipoet> but whatever. think its important enough to share
12:18:07 <midipoet> or scary enough, or whatever adjective you wish to use
12:18:45 <Lyza> is the creepy part that the EU is harvesting global facial data?
12:20:31 <charolastra> "This is an art project by Tijmen Schep that shows how face detection algoritms are increasingly used to judge you. It was made as part of the European Union's Sherpa research program.
12:20:31 <charolastra> No personal data is sent to our server in any way. Nothing. Zilch. Nada. All the face detection algorithms will run on your own computer, in the browser."
12:22:02 <midipoet> to be fair, those in the SHERPA project are fairly good (some are my colleagues). i
12:22:17 <midipoet> its clear that other "project" and "companies" are not so benign
12:24:36 <Lyza> yeah I saw the part about not harvesting data and immediately went "oh so they're harvesting data"
12:25:09 <Lyza> but Idk anything about who' running this I was mostly joshin. Surprised the algorithms run that well in the browser though, in JavaScript
12:25:23 <Lyza> if that's what it's doin
12:26:00 <charolastra> we have stuff like WebASM and fast processors now
12:27:34 <midipoet> Lyza: i don' think SHERPA could lie so blatantly about whether or not there is data sent to the server. would not be good optics
12:27:57 <Lyza> I'm from the US when I hear Sherpa I think of Tibet
12:28:12 <midipoet> Tibet is nice also
12:29:38 <Lyza> yeah though at this point I'd just assume keep wearing a mask in public forever tyvm
12:29:58 <Lyza> get me one of those ones that messes with recognition heh
12:41:10 <charolastra> that page is rather buggy and doesn't detect me at all. maby i don't look human
12:44:14 <Lyza> this is actually a new captcha method. sorry to say charolastra it turns out you're a bot =p
12:45:33 <charolastra> something i've suspected for along time
13:00:42 <moneromooo> cohcho: #monero-site
13:02:07 <moneromooo> Frenn_: no
13:02:58 <Frenn_> moneromooo: is there a way to calculate/estimate ? like make a request to node ?
13:03:15 <moneromooo> There's a RPC to get you the current fee.
13:03:28 <moneromooo> Something like estimate_fee or similar name.
13:03:43 <moneromooo> It's guaranteed to stay valid for 10 blocks IIRC.
13:37:05 <arandomguyxmr> hi, it seems mymonero node got stuck
13:37:24 <arandomguyxmr> i've been waiting for hours but no progress
13:39:04 <arandomguyxmr> anyone do know how to fix this?
13:39:05 <moneromooo> Try #mymonero, but AFAIK it's fairly common-ish, just needs their server to catch up.
14:41:13 <Frenn_> thx !
21:43:15 <raz> hm, my last tx was over an hour ago, shouldn't full balance be unlocked now?
21:46:24 <dEBRUYNE> Do you use a local node?
21:46:44 <raz> no, osx gui client in easy mode
21:50:02 <dEBRUYNE> Is your wallet and daemon fully synced?
21:50:06 <dEBRUYNE> The status bars on the left
21:50:24 <raz> well, it says two blocks remaining... trying restart
21:52:39 <raz> hm, how long should it take to sync up 2 blocks
21:52:42 <raz> it just hangs there
21:56:03 <raz> sigh, now it jumps between 1 and 2 daemon blocks remaining
21:56:04 * raz rolls eyes
21:59:09 <Inge-> raz: what block height?
21:59:25 <raz> Height: 2232840/2232842 (99.9%) on mainnet
21:59:58 <raz> local height: 1 (0.0%)
21:59:58 <Inge-> didn't AHP's start sending out a HIGHER block number ?
22:00:01 <raz> that's what console says
22:00:35 <raz> i could send a successful transaction earlier... and then it went into this state
22:01:24 <raz> guess i'll re-create the wallet and hope it syncs better then
22:02:17 <Inge-> cna you choose remote node in simple mode?
22:02:27 <Inge-> if so, that might help.
22:02:30 <raz> i can only tell it to switch node
22:02:40 <raz> when i do that it shows a different ip in console, but stays stuck in same place
22:04:02 <selsta> raz: see here https://github.com/monero-project/monero-gui/issues/3140#issuecomment-706440354
22:04:18 <selsta> ^ for switching to a custom node and resolving this issue
22:05:35 <selsta> 22:59 <+Inge-> didn't AHP's start sending out a HIGHER block number ? <-- yes and that is causing outdated nodes to get stuck in sync mode
22:05:57 <raz> tried that
22:06:16 <selsta> what is the issue now?
22:06:18 <raz> yay, now it's syncing i think
22:06:21 <selsta> ok
22:06:33 <raz> well now it says 72k blocks remaining
22:06:36 <raz> seems it jumped back in time
22:06:41 <raz> i also got my balance back, i'm rich again!
22:06:54 <Inge-> Funds are Safu
22:06:54 <selsta> 72k wallet blocks or daemon blocks?
22:07:00 <raz> wallet blocks
22:07:20 <selsta> okay, wait for it to sync afterwards transacting should work fine again
22:07:28 <raz> awesome, thx so much
22:08:28 <Inge-> selsta: do you know if updating node to .1.3 is enough, or if it needs other juju as well, such as banning known AHP's, deleting p2pstate.bin, increasing outgoing connections ?
22:08:48 <selsta> from what I have seen updating to 1.3 is enough
22:09:01 <selsta> all reports of this issue were from outdated nodes
22:09:23 <Inge-> Will be interesting to see what the trixy hobbitses do next
22:09:56 <selsta> free audit