00:16:23
ofrnxmr:xmr.mx:
Yes
00:17:19
ofrnxmr:xmr.mx:
Doesnt usully look like that, but it happens
05:09:39
binaryFate:
Latest binaries (CLI v0.18.4.6 and GUI v0.18.4.7) are now available at getmonero.org
08:30:12
ripening:unredacted.org:
Recommend a reliable and open matrix server for registration instead of the official one.
08:39:07
moneromooo:
You're absolutely right.
15:58:14
assholeorangecat:matrix.org:
hello just made a matrix account just testing love monero
16:29:52
assholeorangecat:matrix.org:
this is the official monero matrix group right? including the ones mentioned in the description? I joined some of them too trying to get to know how matrix works.
16:32:42
ofrnxmr:xmr.mx:
Pretty much
16:33:36
assholeorangecat:matrix.org:
awesome thank you for confirming :)
16:57:39
intr:unredacted.org:
lmao nice avatar
17:19:02
assholeorangecat:matrix.org:
@intr:unredacted.org: I can read your messages I can't find the option you talked about in settings :(
17:19:12
intr:unredacted.org:
Which client are you using?
17:19:34
assholeorangecat:matrix.org:
fluffy chat web
17:20:31
intr:unredacted.org:
I've never used that client. There should be an option somewhere to allow sending encrypted messages to unverified users
17:21:22
assholeorangecat:matrix.org:
ill do some research thank you
17:28:05
assholeorangecat:matrix.org:
@intr:unredacted.org: I only have the option "share keys with" and i have selected "all devices" i can read and send you messages not sure why it's not decrypting on your end 🫠when i click on the encryption lock all your device keys are enabled and not blocked
17:32:43
assholeorangecat:matrix.org:
it's ok though just wanted find out how to make friend request but it seems the only option is to start a private chat with someone and have that act as a contact I guess so nothing important thank you for trying though!
17:33:40
intr:unredacted.org:
@assholeorangecat:matrix.org Matrix has no concept of "friends", only DMs
17:33:54
intr:unredacted.org:
which are literally just rooms except only with 2 participants
17:38:48
assholeorangecat:matrix.org:
yes that makes sense. seems friend requests are redundant. you are still my friend now though. have a nice day I'm logging off now :)
17:47:52
intr:unredacted.org:
hah, see you around
17:56:31
plowsof:
My ai agent turned to me now and asked "what mean, "friend"?" im literally crine rn
18:26:45
rbrunner:
Qubic may soon stop to mine XMR: https://qubic.org/blog-detail/qubic-dogecoin-mining-how-it-works
18:27:53
sbt:nope.chat:
> no one cares
19:26:54
yang:
Is this a proper processing of the Blockchain sync, because there are so many "SYNHRONIZATION started" attempts? http://pastie.org/p/2Ziq7OseyD8q7xtWhHIzWG
19:47:17
yang:
it seems like it isn't syncing fast enough at all
19:47:29
yang:
there are more blocks made than the sync
19:47:48
yang:
Do I need to open any "computer ports" to sync faster?
19:52:31
rbrunner7:
No, some closed port are probably not the problem. What does the command status tell?
19:54:20
yang:
Qstatus ?
19:54:26
yang:
or status
19:54:47
rbrunner7:
just status, on the daemon command line
19:56:21
yang:
Refreshed 3105932/3105932, synced, daemon RPC v3.15, no SSL
19:56:51
yang:
it says 2 more years to still sync
19:56:55
rbrunner7:
That seems to come from some wallet app.
19:56:59
yang:
yes
19:57:52
rbrunner7:
The output of the daemon tells us the important info. Did you start the daemon yourself, from command line?
19:58:36
rbrunner7:
It looks something like this:
19:58:41
rbrunner7:
Height: 2958316/2958316 (100.0%) on testnet, not mining, net hash 5.30 kH/s, v16, 8(out)+4(in) connections, uptime 0d 0h 1m 1s
19:58:54
rbrunner7:
The "connections" info there is important.
19:58:59
yang:
yes, likyes, I started it with ./monerod
19:59:45
rbrunner7:
So please just go there, type status, return, and wait - if the daemon is syncing like crazy, it may take some time until the command succeeds and outputs info
20:01:01
yang:
rbrunner: the process is backgrounded...
20:01:29
yang:
do I execute "./monero-blockchain-stats" ?
20:02:28
rbrunner7:
No. Well, if the daemon is running in the background, it's difficult. Any chance to stop it there and run it for once, just for some tests, in the foreground?
20:02:51
yang:
Height: 3105952/3628087 (85.6%) on mainnet, not mining, net hash 1.94 GH/s, v16, 44(out)+684(in) connections, uptime 4d 21h 33m 33s
20:03:42
rbrunner7:
684 "in" connections? That can't really be, if you ask me ...
20:03:58
yang:
I have firewall, that is why I ask if i need to open some ports?
20:04:03
yang:
maybe its hammering the fw
20:04:42
rbrunner7:
As far as I know, usually, if there is something wrong with a firewall, you don't have connections.
20:05:17
btcdwed:
cake wallet is syncing faster for me, when i let cakewallet.exe through the FW
20:05:27
rbrunner7:
But you have plenty, and if you really have 684 incoming connections, which is crazy high, you have the opposite problem of too many connections
20:05:35
btcdwed:
true
20:08:05
yang:
netstat -alpn|grep ESTABLI|grep monerod|wc -l
20:08:06
yang:
92
20:08:40
rbrunner7:
In any case, first thing I would try now is "exit" and the restart the daemon
20:08:44
yang:
ok
20:09:21
yang:
it is a slow machine/drive though, so its possible that it just syncs slow
20:15:23
yang:
it uses overf 50% of the PC's memory
20:26:39
yang:
after this last message it kept growing in memory size, it went up to 2 GB RES, is this normal? I had to kill -9 it http://pastie.org/p/44Y2tVSEjt3OJm66epEQJ5
20:36:22
rbrunner7:
Well, I don't have much experience with running a Monero daemon with such low memory.
20:36:46
rbrunner7:
I mean, for a program like the Monero daemon 2 GB is not that much.
20:38:00
yang:
ok
20:38:10
yang:
yeah maybe I'll try to move it elsewhere
20:38:21
yang:
otherwise it will be slow and getting stuck on this one
20:38:25
rbrunner7:
In any case, be careful when terminating the daemon, always try to make it exit gracefully. If you just kill it outright chances are high the blockchain file corrupts, in which case you would have to start from scratch, unless you have a still-good backup of the file
20:38:40
yang:
ok
20:52:45
hyc:
no. killing the daemon is perfectly safe. pulling the power is dangerous.
20:53:52
hyc:
it is impossible to corrupt the DB with application-level crashes. only OS-level crashes are a liability, and if you're using syncmode=safe then they're crash-proof too
21:01:59
yang:
ok