libera #monero-dev

6 Dec 2022

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Monero GUI dev is at #monero-gui || Monero website dev is at #monero-site || Non-dev questions -> #monero, please || No fork help, you’re on your own

• 03:55
  ArtemVorotnikov[
  I wonder if block id override for 202612 can be reduced to just correct block id comparison and override after all these years?
• 05:48
  moneromoooo
  Probably not. It'd just take an asshole to start serving this block and wedge any new user syncing off them.
• 06:08
  ArtemVorotnikov[
  <moneromoooo> "Probably not. It'd just take..." <- You mean every single node that serves this block during sync?
• 06:11
  ArtemVorotnikov[
  > <@moneromoooo:libera.chat> Probably not. It'd just take an asshole to start serving this block and wedge any new user syncing off them.
• 06:11
  ArtemVorotnikov[
  * All nodes serve it during sync just like any other block. It just has a historic anomaly in block id calculation.
• 06:18
  moneromoooo
  Were there not two blocks ? I barely remember what happened now.
• 06:18
  moneromoooo
  Oh, two txes. nvm.
• 06:18
  ArtemVorotnikov[
  * All nodes serve it during sync just like any other block. It just has a historic anomaly in block id calculation which could be implemented with a simple override:... (full message at <libera.ems.host/_matrix/media/v3/do…2d3f6e2d6daf2b7d6b19794e5fc2222bb0f>)
• 06:19
  moneromoooo
  That looks a lot like what the current code does.
• 06:20
  moneromoooo
  Anyway, I see no need to change what works, but if you're reimplementing something, feel free to do it differently as long as correct.
• 06:21
  ArtemVorotnikov[
  yes, except current code serializes blob and keccaks it, I guess my proposal is just to hardcode it
• 06:22
  ArtemVorotnikov[
  * yes, except current code specifically for 202612 serializes blob and keccaks it, I guess my proposal is to just hardcode the override block id
• 06:22
  sech1
  to use override id, first you need to serialize and keccak the block you're overriding
• 06:25
  ArtemVorotnikov[
  sech1: why not just check against the 'supposed' block id?
• 06:26
  sech1
  Why would it matter
• 06:26
  sech1
  you're just changing the order of comparison
• 06:27
  ArtemVorotnikov[
  it's just making the code simpler fwiw
• 06:27
  moneromoooo
  I just looked at the code, I think the difference is you'd trigger on the exact block, instead of any possible block for that height ?
• 06:28
  ArtemVorotnikov[
  moneromoooo: 'correct' block id (if not for the override) is the commitment for that, no?
• 06:28
  moneromoooo
  I do not understand "commitment" in that context.
• 06:28
  ArtemVorotnikov[
  cryptographic commitment
• 06:30
  moneromoooo
  Well, I guess in the absence of a bug, the block hash commits to the content of the block, yes.
• 08:07
  volkovyuri[m]
  Hello! Gimme please email of the Core Team for some important questions... at site Getmonero.org I can't see full email and I see only "Email: dev[at]getmonero[dot]org"
• 08:07
  volkovyuri[m]
  Maybe email is dev⊙go ?
• 08:07
  volkovyuri[m]
  Help me please)
• 08:23
  moneromoooo
  Hmm. Quite a puzzle... Let me think...
• 08:25
  moneromoooo
  I think you may have the correct solution. It's not for support btw.
• 10:57
  » binaryFate eagerly waiting for important questions
• 11:02
  moneromoooo
  What is... your fate ?
• 11:03
  moneromoooo
  Helps to picture that scene from the Holy Grail on the bridge.
• 11:22
  binaryFate
  ... blue!