09:57:24 <Stealthy> tx-notify not getting called
09:57:40 <Stealthy> getting pissed off lol
10:00:11 <asymptotically> Stealthy: did you use a full path to the program you want it to run?
10:01:07 <Stealthy> --tx-notify '/usr/bin/php /home/monero/notify/tx_notify.php'
10:01:35 <Stealthy> tried with/without quotations
10:02:01 <Stealthy> full path, relative path to service workingdir
10:03:36 <asymptotically> hmmm. can you replace it with a shell script that writes to a file? just one like #!/bin/sh echo 'it works!!' >> /tmp/log
10:03:54 <Stealthy> shellsception
10:04:46 <Stealthy> will try
10:06:15 <Stealthy> hard to debug since the walletrpc log doesnt tell you about attempts either
10:06:25 <Stealthy> or not in my case, who knows
10:11:09 <Stealthy> can any of those arguments go into the config file as they are
10:11:22 <Stealthy> ie tx-notify= rathern than --tx-notify
10:11:27 <Stealthy> or is that gray area as well
10:13:04 <Stealthy> so far i get the impression that i choose the quirkiest of coins of all
10:21:06 <newyearday> hello
10:22:34 <newyearday> how to give block height to get_block_reward in  cryptonote_basic_impl.cpp
10:22:50 <newyearday> i tried with m_db->height adding blockchain.h but no success
10:32:34 <newyearday> anyone here
10:32:41 <Stealthy> run while you can
10:34:50 <newyearday> ?
10:37:33 <newyearday> threat?
10:40:16 <newyearday> any suggestion please
10:40:50 <Stealthy> yea
10:40:58 <Stealthy> switch to a proper coin and toolchain
10:44:24 <newyearday> moneromooo are u here
11:08:27 <wibe> a wallet is simultaniously a node and vice versa right?
11:08:55 <newyearday> no
11:09:20 <newyearday> node = daemon
11:09:42 <newyearday> wallet can work with daemon elsewhere
11:10:49 <wibe> using a remote node for syncronizing the blockchain?
11:11:17 <newyearday> depends on what u need
11:11:42 <newyearday> if u need 99.9 privacy run daemon better
11:11:47 <newyearday> on your pc
11:13:46 <wibe> my question is more related to my package manager.
11:14:28 <wibe> i want to identify the cli wallet and ask myself to install "monero-0.15.0.1" or the monero-core..."
11:14:52 <wibe> which one contains the node and which one the wallet
11:15:01 <wibe> or are both usable as is
11:15:41 <newyearday> monero-wallet-cli
11:15:47 <newyearday> monerod daemon
11:19:08 <asymptotically> wibe: i think that monero-core is the gui, or at least that used to be the name of the repo for it
11:19:25 <asymptotically> monero-0.15.0.1 probably contains the daemon, cli wallet, and some other utilities
11:20:57 <newyearday> hello asymptotically
11:21:11 <asymptotically> hello ne
11:21:14 <asymptotically> hello newyearday *
11:35:49 <wibe> alright thanks
16:44:29 <f8e3> hi
16:44:53 <f8e3> when prober formatted hashes.txt file? checksum filename
16:45:22 <f8e3> when not embedded clearsign hashes.txt
16:46:12 <f8e3> when proper verify: gpg --keyid-format long --with-fingerprint --show-keys fluffypony.asc
16:46:22 <f8e3> when change to binaryFate ..
16:46:30 <f8e3> i hvae now stake, just reportn
16:46:58 <binaryFate> f8e3 don't understand your question
16:47:23 * f8e3 not surprised
17:53:42 <selsta> binaryFate: the person was asking for formatting in the `hashes  filename` format so that `shasum -c` understands it
17:57:25 <selsta> at least that was part of what they are asking
18:37:26 <binaryFate> oh ok. Did we ever have that? As long as it remains readable for non-command line people too why not.
19:20:15 <selsta> binaryFate: yes it used to be in this format
19:22:33 <selsta> hash[doublespace]filename
19:25:38 <selsta> see e.g. https://gui.xmr.pm/files/hashes-v0.15.0.3.txt
20:02:35 <yanmaani> I read something about Chainalysis and Monero. I am curious, how much can they find exactly? I know transaction amount, source, and recipient are hidden. But what exactly can be seen?
20:02:58 <yanmaani> I suppose you could draw the conclusion that a transfer happened at time T, and if there's a lot of transfers something might have happened.
20:03:06 <yanmaani> Are there any other such fingerprints?
20:05:16 <moneromooo> A fair amount. Payment IDs. Whether you use an input younger than 10 blocks. Fake out distribution. Custom fields in extra data. Non default fee. Probably many others.
20:08:27 <ndorf> i thought inputs younger than 10 blocks were invalid after v12 fork?
20:12:10 <yanmaani> But the only information I can glean from that is whether a person is _active_, correct?
20:12:18 <yanmaani> and of course when he's spending
20:12:40 <yanmaani> but can I for example look at coins getting sent to me and observe "right, that's the guy with the strange fees"?
20:27:20 <selsta> ndorf: yep
22:59:03 <binaryFate> <selsta> binaryFate: yes it used to be in this format <--- not the main hash file, see for instance previous one https://repo.getmonero.org/monero-project/monero-site/-/merge_requests/1238/diffs#diff-content-73b69ca944025615c3c819db83643787def82faa
23:01:22 <binaryFate> I personally find putting hash first makes it harder for people to check "with their eyes" as finding the right line is slithly discouraging, compared to having binaries name first
23:01:37 <selsta> binaryFate: a few versions ago, because I got that format from fluffy
23:01:58 <selsta> can look it up tomorrow
23:02:11 <binaryFate> It's subtle and subjective. We should just make sure not to forget non-command line people. Overall goal is that as many people as possible are actually checking.
23:51:22 <ndorf> the filename first format is also accepted by sha*sum -c
23:52:30 <ndorf> i.e. this one:
23:52:31 <ndorf> % sha256sum --tag /dev/null
23:52:31 <ndorf> SHA256 (/dev/null) = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855