04:46:15 -xmr-pr- vtnerd opened pull request #6770: Fix ZMQ pruned bulletproof transactions 04:46:15 -xmr-pr- > https://github.com/monero-project/monero/pull/6770 09:37:14 Thx iDunk, it works using debug-static-all target. 09:59:38 I've a bug when trying to do a transfer (CLSAG, PR #6739), my password doesn't work anymore when it's asked again: 09:59:44 https://gist.github.com/grydz/51596bce8f86eeaf4ac8401dd214f75f 10:00:26 (Obviously this is the same one used when I start monero-wallet-cli) 10:09:51 grydz: what commit are you on? 10:10:03 we reverted 1 commit, try to git fetch 10:33:38 selsta: since he's checked out a pull request, will he not have to rebase it too? 10:33:59 or revert it himself 10:34:00 yes 11:13:51 hmmmmmm getting a "Error: internal error: Transaction sanity check failed" on a transfer 11:13:53 that's a new one 11:15:35 fluffypony: afaik temporary workaround is sending smaller amount 11:15:48 yeah smaller amount seems to work 11:16:04 xiphon: do you know about this ^ ? afaik you added some retry code 11:35:26 selsta, commit 8a9214e 11:36:12 grydz: rebase with master 12:33:53 Thanks, it works. I'm back to my initial untrusted secret problem which should only be related to the device part (https://gist.github.com/grydz/dc76dae3fee6fb3d20d519a01c355318) :D 12:48:17 So close, eh? 12:49:17 Hmmm I hope so :P 16:27:46 not a big deal, but just curious in case someone happens to have an idea: does the monero blockchain have much of an impact on SSD performance degradation? 16:29:19 hyyc said he wore a microsd out running a full node, after 2 years i think 16:32:28 ah, okay! Thanks... that's exactly what I was concerned about, especially since it's an internal (not practical to replace) drive. It was becoming a bit of a hassle keeping the database on an external drive, but seems worth the piece of mind 16:43:24 im not sure how much a microsd compares to an ssd though, ive never heard of anything other than that one microsd comment 16:52:53 Meeting in #monero-research-lab begins at 17:00 UTC (about 10 minutes from now) 17:40:43 Should we set a fork height for the network upgrade? 17:41:50 I would never use non-removable internal storage for the blockchain 17:42:11 whether microSD or SSD or whatever 17:43:02 now that we also store the txpool in the DB, the I/O load can get pretty intense, it will certainly wear out any device in a few years 17:43:16 s/fork height/block height 17:43:22 the only way to prevent such wear is if the device capacity is several times larger than the DB 18:05:26 Probably would be a good idea 18:05:35 Lots to do on the checklist (if we're using that) 18:05:53 We should use that :) 18:05:55 that's the point 18:06:08 https://github.com/monero-project/meta/issues/500 18:07:23 ErCiccione[m]: Don't we usually set one right before the tag 18:07:31 iirc it is typically one of the last pull requests 18:07:58 Yeah we should definitely use it, now and in the future 18:08:57 dEBRUYNE: I might be misremembering, but i thought the last time we kinda said "should we set it?" and we did. I hoped to spark the same reaction :P