00:39:40 I'd ack given my call for a moratorium on ecc dev but jeffro256: may want a new tx version after the fcmp++ HF (same time as jamtis)? 00:40:39 That raises the Q if we're going to have a 2.0 in 6-12 months 00:42:06 If there's still frequent consensus changes, I'd advocate shifting the versions over, not making a 1.0 10:11:23 Let's just shift from v0.18.x.x. to v19.x.x to satisfy everyone :) 15:35:15 What's wrong with sender privacy? 15:41:23 Ring signatures are not perfect (only 16 decoys). See EAE attack, for example 15:49:47 sech1 even see OSPEAD latest results show yesterday 15:49:53 4.2 effective ring size 15:49:59 4.2 effective ring size at worst 16:22:01 Where do I put the "nonce extra" in the Monero block header? Inside the transaction with the TxExtraTagNonce right? 16:22:08 Test 16:22:17 Why are my messages instantly deleted? 16:23:14 they are not 16:23:21 we can see them 16:26:54 test 16:46:51 "nonce extra" is put in the tx_extra field of the coinbase transaction. Yes, with the TX_EXTRA_NONCE tag. 17:12:15 The size can be anything? Can I have a 16 or 32 bytes extra nonce? 17:12:16 And the process would be as follows for a 16 byte nonce, correct? 17:12:18 1. call get_block_template with reserve_size = 17 (16+1) 17:12:20 2. unmarshal the `blocktemplate_blob` to a Block struct (provided by https://git.gammaspectra.live/P2Pool/consensus/src/branch/master/p2pool/stratum/stratum.go , a cool library i found) 17:12:22 3. edit the TxExtra to replace the 17 empty bytes with `TxExtraTagNonce` prefix + 16 random bytes 17:12:24 4. get the hashing blob with block.HashingBlob() and send it to miners for work 17:12:26 i'm unsure about the steps 2. and 3 17:12:47 The size can be anything? Can I have a 16 or 32 bytes extra nonce? 17:12:48 And the process would be as follows for a 16 byte nonce, correct? 17:12:50 1. call get\_block\_template with reserve\_size = 17 (16+1) 17:12:52 2. unmarshal the `blocktemplate_blob` to a Block struct (provided by https://git.gammaspectra.live/P2Pool/consensus/src/branch/master/monero/block/block.go , a cool library i found) 17:12:54 3. edit the TxExtra to replace the 17 empty bytes with `TxExtraTagNonce` prefix + 16 random bytes 17:12:56 4. get the hashing blob with block.HashingBlob() and send it to miners for work 17:29:02 @sech1 17:32:41 Size must be < 256 bytes 17:32:50 But you don't need a lot for tx_extra 17:37:01 are the steps i outlined correct? 18:12:37 yes, but you need to have a unique tx_extra for each miner 18:12:52 or they will mine on the same hashing blob 18:14:29 of course... i generate a different tx_extra for every single job for each miner 18:16:57 get_block_template returns hashing blob, but you can't use it directly. You need to edit the template (tx_extra in it), then recalculate the hashing blob. So steps 3-4 are correct 18:17:41 I mean you can use it directly, but only for solo mining 18:17:50 yes, and i rely on that Go implementation to calculate block.HashingBlob() 18:21:07 It should work. You can check it on testnet 18:56:31 (testnet synchronization is so slow 😦) 18:56:41 i mean stagenet 19:44:24 .merge+ 9720 9721 19:44:24 Added