01:26:20 has monero some timestamp check that decide independently about block version from other parameters 01:51:41 There's a v1_till variable or so, somewhere right near the fork table. 01:52:08 i changed this to 0 01:52:22 Can't think of anything else. 01:52:42 is crazy i have change even original version on hardfork.h 01:52:47 everything! 01:53:06 i did original_version = 12; 01:53:28 when i debug i c that version is 1 01:53:32 IIRC your problem is the serialization bails midway. 01:53:46 The traces should show you the line where it stops. 01:53:57 why when i insert version 1 daemon start 01:54:17 i insert this mginfo trace but nothing 01:54:32 MGINFO("trace"); 01:54:41 every second line 01:55:15 I'm fairly sure the log you posted had a few traces in it. 01:55:39 that common_trace ? 01:56:33 http://paste.debian.net/1139229/ 01:57:23 look line 38,39,40 01:58:41 on gdb the first line give the error is ss << tx_blob; 01:59:21 I think I told you to put this in the serialization code in cryptonote_basic.h. That's what apparently bailing. 01:59:47 Both in transaction and transaction_prefox. 02:00:36 i insert it even there and again the output was the same "trace,trace,trace" 02:00:48 on daemon.log 02:01:15 OK. Then I guess it's bailing earlier even. Is your blob empty ? 02:01:30 no if i insert version 1 works 02:01:37 when i insert 12 02:01:46 is error 02:01:57 You're really really sure you put those logs in the tx serialization code, right ? 02:02:04 yes!! 02:02:21 Dunno then. Very odd. 02:02:52 i inserted after BEGIN_SERIALIZE() on basic.h 02:03:11 and the same "trace,trace,trace" 02:04:10 Guess you can break in gdb in the parse_tx_from_blob function then step. 02:04:13 the starnge is that on gdb i c version 1 after inserting 12 on hardfork.h,genesis start 02:04:36 after step what 02:04:54 After step you step again till you find what fails. 02:05:19 You might have to step a lot. n for next (run calls in one go), s to dive down into the call. 02:05:47 so step not next 02:05:55 ok i do it right now 02:06:43 Both. n if you don't care about the call (ie, smart pointer stuff, logs, etc). s for stuff like serialialization code. 02:06:50 is better here the break ss << tx_blob; or CHECK_AND_ASSERT_MES(r, false, "Failed to parse transaction from blob"); 02:07:15 You want to first break before the call that sets r. 02:15:27 binary_archive.h:101 first line after step 02:15:46 now again step 02:15:55 or next 02:17:01 Dude. I'm not telestepping for you, come on. 02:18:24 same file line 67 02:20:29 102,103,104 and after on postypes.h i have "value has been optimized out" 02:21:13 You can build with -O0 to fix most of these. 02:21:32 u mean to insert more bytes 02:21:35 on genesis 02:22:25 after 105 on binary_archive.h im back on format_utils 02:22:49 on the line that error start 02:26:16 what do u mean with "build with -O0" 02:30:52 moneromooo please can u explain what is need 02:34:50 -O0 is a gcc option to not optimize. 02:35:31 so u mean to change compiling type and i'll be ok? 02:36:02 or i'll have more info on debugging 02:36:29 It'll fix most of the "value has been optimized out". 02:36:51 Though you should be able to do most of the stepping without -O0. 02:37:25 ok 02:37:58 but where to insert in which cmake file 02:38:48 Replace current -O option, revert when done debugging. 02:41:31 so i remove on cmakelists the "-O0" with "-O" 02:41:34 ok 06:38:29 hey 16:07:48 niocbrrrrrr: updates? 20:14:46 hi 20:55:02 https://reason.com/2020/04/09/one-mans-battle-with-the-irs-over-bitcoin-privacy/ 20:57:54 Wonder how many millionaires there are who just so happened to mine Monero during its first two weeks? 20:58:09 In fairness, you can be compelled to divulge your audit key to the IRS. 21:03:36 what if they were lost in a 🚤 21:07:41 boating accident! 22:24:37 https://it.slashdot.org/story/20/04/09/2014207/signal-threatens-to-dump-us-market-if-earn-it-act-passes 22:32:40 Smooth been around these parts in the last week?