00:05:51 ARM64 NEON is usually available, but even ARM is phasing that out in favor of SVE2 00:06:23 fwiw, master+testnet forkheight patch passes make test 00:12:09 took about 2 hours for test to run 00:12:31 5885 seconds in core_tests 00:14:42 Takes ~10 minutes here with my patch to replace PoW with keccak ^_^ 00:15:27 ETC already beat us to it 00:31:19 Oh hey, people talking about ARM yay 00:31:58 Got my PinePhone, unfortunately the bits in arch/community involve x86, not ARMv8 00:32:35 If I want a Monero CLI binary for PinePhone I need to download repo onto phone and run make release-static-linux-armv8, right? 00:36:11 * xmrscott[m] tests bridge just to make sure, can never tell 00:38:49 CPU for reference: https://en.wikipedia.org/wiki/ARM_Cortex-A53 00:39:17 did you try binaries on getmonero.org? 00:42:29 Oh wow, hur. Should have looked there first 00:42:49 Will try the Linux ARMv8 binary there. Thanks! 00:46:15 -xmr-pr- denisgoddard opened issue #6795: Feature request: alert on detection of possible "dust" input 00:46:15 -xmr-pr- > https://github.com/monero-project/monero/issues/6795 00:59:55 Follow up, is there a way to launch monerod to show current block sync state? 01:00:58 ./monerod status 01:07:18 It's working! Will upload video shortly! 01:57:36 FWIW, here's daemon starting up and running on PinePhone. Probably not super exciting for some, but being able to actually run a mobile wallet w/o Google or other malicious apps snooping on clipboard/private key is super exciting to me: https://twitter.com/kamenrannaa/status/1301337485121933312 01:57:50 Major props to whoever maintains the ARMv8 bin! 02:12:44 xmrscott[m]: what is the benefit to linux phone vs an android (minus google) phone like lineage or graphene? 02:16:13 To me, the main thing is precisely that, no worry of Google snooping anywhere on the HW/SW stacks 02:18:23 If you're referring to the phone itself rather than the notion of running Monero on a Linux phone, HW kill switches, easily replaceable parts, similar ecosystem to my PC which also runs Arch + Plasma 02:47:20 Also worth noting it is crazy simple to put whatever OS you want on it with Etcher. Maybe the ecosystem has changed in the last 4 years, but I remember it being quite painful to flash an Android tablet with CyanogenMod. It takes all of maybe 5 min to flash a 128gb sd, boot the Linux phone, and start dl'ing updates via the stock pkg manager 02:48:24 xmrscott[m]: yes the phone looks really great from those respects, but correct me if i am worng, but i think lineage and graphene are completly devoid of google anywhere in the stack. 02:50:03 i guess the seeming great benefit IMO would be being able to use .apk's and most of the software for mobile these days is already built for android? but perhaps there are a ton of apis that just don't exist on these other android oses, meaning an app devleoper would need to re-build their apps substantially anyway? 02:53:40 Probably best to take this conversation to -community 04:02:15 ack 04:55:26 fyi I did most of the ARM support 04:56:55 hah. couldn't remember my testnet wallet's password because it has none 04:57:59 last time I used it was a year ago, before the RandomX hardfork 04:59:41 and I now have 20% of testnet hashrate 14:40:48 testnet fork in 3 hours, is my node correct? 14:41:19 Sounds plausible. 14:41:32 should we ask fluffy to update testnet seed nodes? 14:41:45 Oh need to update mine! 14:41:50 Just build from master? 14:41:55 Or some branch? 14:42:03 master + 6794 14:42:14 I'll kick mine off 14:43:34 .merges 14:43:34 -xmr-pr- 6757 14:43:40 .merge+ 6794 14:43:45 Added 15:16:22 We should probably update this with whats done when people complete tasks: https://github.com/monero-project/meta/issues/500 15:16:33 I've updated what I know for sure, but didn't want to arbitrarily mark things off 15:37:35 Failed to get top block hash to check for new block's parent: MDB_NOTFOUND: No matching key/data pair found 15:37:49 I get this when importing testnet blockchain, am I doing anything wrong or is my current testnet db corrupted? 15:40:42 okay, deleting my current testnet db solved it 15:44:07 Does this suggest any issues that could arise in mainnet deployment? 15:47:18 doubt it, I had a super old testnet db on my system, no idea what was up with that 15:52:27 And testnet has gone through some quite wild times :) 15:53:34 I wonder whether it will split, with only few people on the new version, and the seed nodes on the old version 15:55:36 Would be splendid if gingeropolous has time to update the daemon for testnet.xmrchain.net, would be super-useful to "see something" 15:57:45 * selsta has two nodes running 15:58:55 one, so far 15:59:22 and for mysterious reasons a quite badly connected one, despite running for months ... 16:35:39 Getting this stacktrace with my testnet node: https://paste.centos.org/view/4ccdb41f 16:35:44 restarted and got the same thing 16:35:52 Its still running, however. 16:36:08 `Monero 'Nitrogen Nebula' (v0.16.0.0-9b44174ef)` 16:46:15 -xmr-pr- grcasanova opened issue #6796: Testnet multisig wallet block height is higher than the daemon's heigh... 16:46:15 -xmr-pr- > https://github.com/monero-project/monero/issues/6796 16:46:19 Can you paste that on a site that doesn't have wonky ssl (assuming it's not exit nodes ganging up on it) ? 16:47:02 https://www.irccloud.com/pastebin/Xa20Lh6I/ 16:47:29 Is this beter? 16:47:30 https://paste.debian.net/1162473/ 16:47:32 Ah thanks selsta 16:48:01 debian paste seems to be a good choice for everyone 16:48:22 I’ll use that in the future 🙂 16:49:20 I still think it'd be interesting to run an encrypted pastebin 16:49:37 Not sure about the liability of this, if any 16:52:03 https://cryptobin.co/ 16:52:50 that's a cool site 16:53:07 Looks similar to 0bin 16:55:36 Yes, thakns. 17:10:29 > next fork in 10 blocks 17:11:13 Hopefully, with only a handful of daemons :) 17:12:16 pins and needles... 17:20:32 rbrunner, selsta , xmrchain.net should be on proper daemon 17:20:37 matt daemon 17:20:50 Maett Daemon 17:21:09 Really nice, thanks 17:21:26 .merges 17:21:26 -xmr-pr- 6757 6794 17:22:54 Height: 1543937/1543937 (100.0%) on testnet, not mining, net hash 3.43 kH/s, v12 (next fork in 2 blocks), 6(out)+0(in) connections, uptime 0d 0h 3m 22s 17:23:03 must be on right daemon 17:23:20 i made it selsta ! thanks for the copypasta 17:25:24 ima start mining on xmrchain.net testnet whynot. whats the address to the testnet faucet? 17:25:38 9vmn8Vyxh6JEVmPr4qTcj3ND3FywDpMXH2fVLLEARyKCJTc3jWjxeWcbRNcaa57Bj36cARBSfWnfS89oFVKBBvGTAegdRxG 17:25:41 xmr.to faucet 17:25:47 danke 17:30:01 lol ... my "in" connections dropped from 50 to 4 with the fork happening 17:31:10 hmm my node has 0(out)+6(in) 17:34:39 i have 2 out 0 in 17:34:54 oh i have a priority node 17:39:53 I tried a transaction, and after about 1 minute it showed up in the explorer 17:40:11 Hah, first! 17:40:24 I will be mentioned in the history books 17:40:50 im trying to get my testnet seed node updated as well 17:41:25 rbrunner: you have done much to advance humanity 17:41:33 Thanks, thanks 17:41:41 Better issue a press release about how CLSAG is Advancing Humanity With Science (tm) 17:41:52 I'm told this is how these things are done 17:41:55 it has ZK and DAGs right? 17:41:58 both 17:42:13 gingeropolous is technically correct: the best kind of correct 17:43:23 so is new tx type "4" ? 17:43:49 Would make it easier for people to follow if luigi1111 or snipa could merge 6794 as soon as possible into master 17:44:17 it is merged 17:44:26 Ah, ok, sorry to nag then 17:45:03 naggers... 17:45:05 rbrunner, i think you sent an old style maybe? don't see any dize difference 17:45:54 Breaking: sizeof(CLSAG) == sizeof(MLSAG) 17:45:55 :( 17:45:59 I could make a post with instructions I guess 17:46:04 Well, I just let the wallet do its thing ... 17:46:14 (to participate in testnet) 17:47:11 right, well, the testnet is in that in-the-middle period. I dunno what the wallet is supposed to do or how it knows when to use what format 17:48:47 How to spot the new format anyway? Type 5? 17:49:05 this right? Monero 'Nitrogen Nebula' (v0.16.0.0-9fb2243db) 17:49:33 No, I mean how to see that in the block explorer, with a single tx displayed 17:50:09 i dunno. i just compared your transaction to one that was made about 10 days ago. if u click back enough in the explorer theres... ah lemme do it 17:50:39 https://testnet.xmrchain.net/tx/cbb85a217251126b57e7b8de3e9cdc48c8f27431e1382850ba1e3b0dc86e28d5 17:51:24 so i just compared that one to the one u made and it looked the same, at least regarding all the stats posted 17:51:31 That be MLSAG-sized 17:51:46 but the explorer may just be lying to me 17:52:13 Because maybe it does not know the new structures? 17:52:15 i haven't followed mwos repo to see if onion-explorer is modded 17:54:33 hmm my node apparently didn't apply the PR properly 17:54:34 Re-building, as I got forked off 17:55:27 fluffypony: please update your testnet seed node to master (if you are running one) 17:55:38 I'll check 17:55:54 I displayed my tx in the daemon, and I got a binary length of 2593 bytes. 17:56:13 A 2-2 txn should be closer to 1.9 kB IIRC 17:56:33 2-2 MLSAG is ~2.54 kB 17:57:27 Freshly built master: `Height: 2178760/2178760 (100.0%) on mainnet, not mining, net hash 1.29 GH/s, v12, 7(out)+8(in) connections, uptime 0d 0h 0m 58s` 17:57:42 oh 17:57:45 Maybe moneromooo knows what my wallet *should* produce right now, and what might prevent it from doing "the right thing" 17:57:49 Nvm I'm dumb, forgot the testnet flag 17:59:24 `Height: 1543945/1543945 (100.0%) on testnet, not mining, net hash 3.47 kH/s, v13 (next fork in 1.0 days), 1(out)+1(in) connections, uptime 0d 0h 0m 22s` 🙂 18:00:17 someone make a new tx :) 18:00:37 You mean in the new format? It is smaller, with only 1 input 18:00:39 oh there we go 18:00:40 https://testnet.xmrchain.net/tx/2208877ddf476815d34e5cabc5e4c607f0410a4b2c7439d819f0207e1224395a 18:00:57 that’s mine and not sure if that is correct 18:01:07 1.7246 kB vs 1.7334 kB on mainnet 18:03:15 Anyone want to send me some tXMR? `9tRQikyQRHf3vCoDFfU2KvPQnFTi95bzyK2Jcx5bN2XAFvVoyg73dgK1Qi3ppdNUDjZypS45Zn5j17ky8rGUMW6t1NhqbR9` 18:03:56 im compiling the wallet 18:04:59 In the pool, sethsimmons, the one ending on 1c 18:05:22 ty 18:05:29 New stacktrace when stopping/starting mining: https://paste.debian.net/1162495/ 18:05:44 was the previous stacktrace also from mining? 18:05:51 no 18:05:59 Previous was just when the node started 18:06:02 Just started mining now 18:06:35 Does CLSAG not activate until v14? 18:07:18 No idea, where is our lead dev when we need them. It's hardfork, and moneromooo is not around. Ts ts ts :) 18:08:07 59 blocks to unlock 18:08:34 My understanding is that we should already produce CLSAG transactions, but any old ones, e.g. in the pool, would still get processed for a grace period of 1 day. Might be wrong, however 18:08:35 well 2 hrs before i can send yah anything 18:08:43 CLSAG starts at v13, enforced at v14. 18:08:47 If you mined, yes 18:09:00 xmr.to faucet errored out 18:09:06 they did not update their node 18:09:13 moneromooo: anyway to confirm that a tx is a clsag tx? 18:09:22 print_tx TXID 18:09:32 If CLSAG, it... err 18:09:32 binaryFate: testnet nodes need to be updated for the CLSAG fork that just happened 🙂 18:09:38 * moneromooo checks 18:10:00 It should have rct type 5 18:10:04 okay, mine has 4 18:10:06 Maybe +json to see something? 18:10:11 Guess wallet still defaults to 4 18:10:20 Ah, possibly. 18:10:25 * gingeropolous smash wallet 18:10:30 * moneromooo afk for a few mins, I'll check after that 18:11:10 Noooo ... so I was not first person on Earth to make a CLSAG transaction on a Monero network. I am devastated. 18:13:12 The JSON of my transaction indeed says type 4 under "rct_signatures" 18:13:28 As displayed in the daemon 18:16:09 * moneromooo looks 18:16:15 -xmr-pr- dEBRUYNE-1 opened issue #6797: [SUGGESTION] Use a minimum value for the restore height of Ledger and ... 18:16:15 -xmr-pr- > https://github.com/monero-project/monero/issues/6797 18:17:42 hmmmmm 18:17:54 is there a ppa for boost dev for Xenial? 18:19:11 Can you translate that to English? 18:19:36 does that work? https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest 18:19:39 LOL rbrunner 18:19:49 selsta: that's runtime only, not dev 18:20:14 Eh, noob here, know neither "ppa" nor "Xenial" :) 18:21:23 A, sort of a package 18:21:25 I hope this is the right channel to ask this question - I'm just getting started with the Monero RPC Wallet API and am using this as a reference https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#set_daemon - my question is simple where a parameter is optional but does not specify a default value can I just send an empty string for instance (if the type is listed as a string in the docs)? 18:21:32 fluffypony: this is roughly what I've used in the past: https://paste.debian.net/1162499/ 18:21:39 I'm not aware of a proper PPA for the latest/recent dev 18:21:48 tks 18:21:59 should be able to replace the version numbers and be good after that IIRC 18:22:25 I'm just in the middle of syncing a monerod node on my local machine so I can do some testing of my own code but until then I'm a bit lost 18:22:51 you might want to set prefix to /usr/local so that it doesn't upset your package manager - not sure how to do that with b2 though 18:24:02 * moneromooo builds, will be a while 18:28:12 tks sethsimmons that worked perfectly 18:28:26 Nice :D 18:35:30 Nizumzen: Why would you want to send an empty string? 18:36:22 Typically empty means default for optional stuff. You can also just omit it. 18:38:34 dEBRUYNE: sorry I'm quite new to this - I have my JavaScript set up with default values for the parameters that specify what the default was but I was just a bit confused as to why some of the optional parameters had a default value and some didn't - I guess I am supposed to omit them completely from the POST request if they are optional, have no default value and the user has not specified a valid value 18:38:58 ? 18:44:18 is that correct or am I totally wrong? 18:48:57 If you don't send a field, and it's optional, it'll have some default value. 18:51:54 ok I'll leave those out then completely - thanks for your help all 19:19:32 So, rebuilt, testnet chain synced, and... it appears to make CLSAG txes. 19:19:53 This is my work branch though, as I can't run master without resyncing the whole chain. 19:20:25 It might be waiting for 10 blocks after the fork though. 19:21:55 Can whoever tried and got MLSAG try again after mining 10 blocks ? :) --fixed-difficulty 1 is great here. 19:22:00 (and --offline) 19:22:37 1951 bytes. Lovely ^_^ 19:22:45 :D 19:22:54 That looks right! 19:27:23 Not sure what you mean with "after mining 10 blocks". You mean on an own, private chain, not on the testnet chain? 19:27:30 Whichever. 19:27:40 If others mined the 10 blocks, it also works. 19:27:52 testnet forked ~60 blocks ago 19:28:34 But aren't we now already some dozens of blocks after the fork? 19:28:45 About 60 ^ 19:28:46 I keep getting `2020-09-03 19:25:16.419 E Unable to send transaction(s) via Dandelion++ stem` but that’s probably because I have `0(out)+7(in) connections ? 19:29:10 So what's the meaning of 10 blocks? I feel stupid. 19:29:27 I tested sending a tx 19:29:35 * selsta waiting for it to show up in mempool 19:30:03 10 blocks mean... the chain height be 10 more than the fork height. Plus or minus 1. 19:30:14 That's what the wallet uses to start using CLSAG. 19:30:16 yep, type 5 now 19:30:20 Good :D 19:31:35 Alright, seems we just did not wait long enough, maybe our test transactions missed by a single block 19:33:16 Is https://testnet.xmrchain.com/ still running correctly? It seems 1 block behind, and not showing 2 tx in the pool 19:33:41 gingeropolous: ^ seems 2 blocks behind 19:33:48 I just got b9df97f4ec023a8b2ba2160bf0dcf029d71d8b8eea571746e48d24b4db6d96f1 mined for me 19:34:42 With type 5 19:35:12 lol looks like https://testnet.xmrchain.net broke 19:35:15 it skipped 2 blocks 19:35:19 The 10 block delay is to avoid an unlikely case of a tx sent right after the fork (so using CLSAG) becoming invalid if somehow a reorg brings the chain back to pre-fork. It's really unlikely to happen in practice though I suppose. 19:35:42 Makes sense. 19:36:04 Even so, it'd become valid again soon, since it did not use outputs younger than 10 blocks. 19:36:15 moneromooo: Any idea about the no outgoing connection thing? Could it be that all other peers have me as an outgoing connection so I can’t find any? 19:36:15 So I suppose it's a bit of a pointless delay now. 19:36:16 Never saw a block explorer skip blocks, that's funny 19:36:28 Very few nodes running current master ? 19:36:37 Yes 19:36:45 CLSG txes so small the exploirer can't see them! 19:36:59 https://testnet.xmrchain.net/block/1544011 19:36:59 lol 19:37:19 Lol 19:38:25 selsta, did your tx get mined? If yes, which block? I am in 12 19:38:37 in 1544011 19:38:45 Ah, you beat me then :) 19:38:56 Maybe it just dies on decoding CLSAG txes. 19:39:06 Yes, my thought as well right now 19:39:51 And does not show them if in pool 19:42:15 perfect privacy! 19:42:38 Move over Phil Zimmerman... 19:45:52 Strange that https://community.xmr.to/explorer/testnet/ shows "old" testnet stuck since about 1 hour ago. I would have expected the numerous not-yet-updated testnet daemons to continue building their chain happily 19:46:33 They're probably not mining. 19:47:22 Yeah, interestingly it seems "our" hashrate did not sink 19:48:07 see https://monero.stackexchange.com/a/7981 19:48:29 only 70 blocks passed so it will take a while until accurate hashrate shows up 19:49:17 bc_dyn_stats N shows the average block time in the last N blocks. 19:49:29 Of course, law of small numbers applies. 19:49:39 Right, I forgot 19:49:59 82 avg sec/block 19:50:33 Interesting command 20:00:47 someone have an address I can dust 🙂 20:01:34 so a 1-2 CLSAG tx is 81% the size of MLSAG, does that look correct? 20:02:05 sethsimmons: A1aNRBZ4HRHA9zodJDzNLuHh3cfLQmCAAJ2NFWLLiCag7EuYUdd36ncdxgK234LPJmcN8Sk2vzSozAMLuf2iE9kE2sMkQcR 20:03:11 Are these types of warnings in GUI as well? 20:03:12 `Warning: Some input keys being spent are from blocks that are temporally very close, which can break the anonymity of ring signatures. Make sure this is intentional!` 20:03:17 I've never seen that before! 20:03:34 no 20:04:38 The "temporally very close" is probably not a bad thing now. It used to be due to split txes, but this does not happen anymore post rct. 20:07:55 How can I verify the size of my TX without an explorer? 20:08:08 print_tx isn't an option in monero-wallet-cli 20:08:17 print_tx TXID +hex 20:08:21 wc -c 20:08:27 Paste the hex 20:08:29 ^D 20:08:33 Divide by 2. 20:08:49 [wallet 9tRQik]: print_tx c55e0b7158731f52733166914304d034bd3d762a089f65b76fbbc364713fc6f3 20:08:49 Error: Unknown command 'print_tx', try 'help' 20:08:55 inside daemon 20:08:57 Is that only an RPC command? 20:09:00 Ahhhh 20:09:03 ty 20:09:20 Weird that you cant do it inside the wallet 21:40:59 if you're running monerod headless, you can run rpc commands with e.g. `monerod print_tx ...` 22:31:51 Man, I *so* hate this rx_slow_hash code. It's confusing as heck. 22:37:48 .merges 22:37:48 Merge queue empty 22:38:57 .merge+ 6111 22:39:02 ... 22:39:42 btw I still have this issue with 6111 22:39:49 though it seems to only happen on my machine 22:40:48 Did it not get fixed by allowing more time for the reorg ? 22:42:29 I did not try anything yet, you said you will try to reproduce first. I can try increasing line 154? 22:42:38 156* 22:43:08 I reproduced one of them from time to time IIRC, fixed by bumping the alloted time. 22:43:42 .merge- 6111 22:43:42 Removed 22:43:50 Meh, don't care enough. 22:44:44 ok will try 23:12:21 For trezor support: https://github.com/monero-project/monero/pull/6798 23:16:15 -xmr-pr- ph4r05 opened pull request #6798: Trezor: Enable CLSAG support for Trezor client 23:16:15 -xmr-pr- > https://github.com/monero-project/monero/pull/6798 23:16:32 too late, bot 23:28:29 .merge+ 6111 23:28:35 (can’t reproduce anymore) 23:28:59 Added 23:29:02 Good. My recollection was it got fixed by longer timeots. 23:56:19 moneromooo: do you want 6745 included in the next HF? 23:58:29 I was hoping for more review first. 23:59:11 Especially for the question in the first chunk of comments.