11:06:12 Has anybody actually read The Monero Standard? 11:06:36 I bought it to support the idea only 11:06:47 is it any good at all? 11:18:19 it's useful for staying in the loop, without having to stay attached to chat or github 11:52:20 I think he meant the book https://monerostandard.com/ 11:52:24 and not https://localmonero.co/the-monero-standard/weekly/95 11:52:34 and not https://localmonero.co/the-monero-standard/ 12:00:02 yeah the book sorry 12:00:39 Louis.signet another book, entirely free or purchasable https://masteringmonero.com/ 17:33:16 Median block size limit: 294.50 kB 17:33:27 Recent transaction spike increased block size a little 17:33:41 from 300000 bytes to 301568 bytes 17:37:02 the heaviest block with biggest penalty was https://p2pool.io/explorer/block/3095592 17:37:12 0.597956 XMR mined instead of 0.6 XMR 17:38:56 Pls teach me how to mine 17:39:04 Nice 17:39:54 That's a fresh one too 17:40:01 serhack is based 17:42:30 there can be penalties? 17:43:08 Yeah, if block size exceed current block size limit. 17:43:15 310KB > 300KB 17:44:30 it's fine still, miners will include the TX if the fees compensate for the penality. Block reward was 0.597956, Actual reward was 0.607024 17:45:15 ignoring one 146/2 TX would have produced a lower reward probably, else why it got mined... 18:22:09 That's odd... skipping one of those big txes would have dropped fees by 0.002025, so fee reward would have been 0.007043 18:23:14 But without penalty, the total reward would have been 6.007043 > 6.007024? 18:23:59 unless theres a rounding issue, seems like you need to drop 2 of the big tx to go under the limit 18:24:58 Just one, why two? 18:25:39 nvm i moved the decimal when i shouldnt have 18:28:00 Maybe the miner round and decided that 0.007 == 0.007 ? But yeah, if the miner wanted more he should have left one of the big TX in the mempool 18:29:27 Maybe they're optimizing for maximum blocksize increase, while still remaining above 0.6 xmr net reward? 18:30:17 But we can only speculate, without actually knowing what the miner's mempool looked like when they built that template 18:30:29 Maybe, as at the end it's what matter. 18:30:29 Miners expect 0.6. Tail emission is what pay miners, not the fees 18:30:32 whos the miner? just some solo guy? 18:32:09 IIRC sech1 said that `monerod`'s block construction algorithm doesn't quite choose the best set of txs for highest block revenue. IIRC P2Pool has a slightly better algorithm that takes a little more time to find its solution. 18:33:28 A naive exhaustive search would complete in about O(n choose k) time probably. 18:34:21 yes, p2pool uses better algorithm to pick transactions and usually gets higher block reward when blocks are full 18:34:33 snex: in that case, the miner can be a sole miner or a pool that is NOT p2pool. As there is only one output of 0.607023719333. 18:35:28 the best solution can be found by discrete knapsack solver, but it takes O(n*k) time where k = 300000 (block size), it's too slow 18:35:31 (p2pool produce an output for each miners that had mined block in the sidechain) 18:35:45 https://github.com/SChernykh/p2pool/blob/master/src/block_template.cpp#L761 18:36:55 IIRC monerod uses an algorithm that tends to create slightly bigger blocks and slightly smaller block reward 18:37:03 compared to p2pool 18:38:46 how unique are tx in terms of size vs reward? if they tend to look very similar you could just cache a bunch of optimal solutions 18:38:58 not very unique 18:39:11 often they have the exact same size and fee 18:39:36 no need, current algorithm is already pretty good: https://github.com/SChernykh/p2pool/blob/master/src/block_template.cpp#L457 18:39:50 Which it what you was as privacy is expected 18:40:18 s/was/want/g 20:57:37 How do you guys know if an exchange is a member in CryptoSafe Alliance? 21:09:57 or Crypto Defenders Alliance 22:39:13 I guess if they are big enough they are part of the CSA. KYC => CSA at least