libera #monero

4 Jul 2022

[XMR] Be excellent to each other and welcoming to newcomers || getmonero.org || Dev: #monero-dev || Pool related: #monero-pools || Price chat: #monero-markets || People can & do log this channel

• 12:18
  tokenberry33
  hi
• 12:19
  tokenberry33
  How to add specific reward to block 1
• 12:20
  tokenberry33
  For example on file cryptonote_basic_impl.cpp  if(const cryptonote::block = 1) { reward = 10; return true; }
• 12:21
  tokenberry33
  This can happen inside function "get_block_reward"
• 12:41
  tokenberry33
  Is any real hacker here to help on how to reward specific block
• 12:43
  Mochi103
  lol
• 12:44
  uncle_rae
  o_0
• 12:44
  Mochi103
  For your own fork of Monero tokenberry33 ?
• 12:44
  tokenberry33
  For testing reason
• 12:45
  tokenberry33
  I'm playing with testnet
• 12:46
  tokenberry33
  I want to check monero behavior in the future
• 12:47
  moneromooo
  That's exactly where you'd do it, yes.
• 12:54
  tokenberry33
  What do you mean please
• 12:55
  tokenberry33
  Adding height in last part of function  get_block_reward  failed
• 12:55
  moneromooo
  I was just confirming what you said about doing it in get_block_reward is correct.
• 12:56
  tokenberry33
  I must change this function on blockchain too maybe in tx_pool
• 12:57
  tokenberry33
  Everywhere that this function appear
• 12:58
  tokenberry33
  Monero code must be more modular is too messy
• 13:16
  tokenberry33
  I c here need of changing too much code
• 13:16
  tokenberry33
  Has anyone here a more elegant solution
• 13:17
  selsta
  look at how other forks did it, there is no other solution
• 13:19
  tokenberry33
  I dont have any example of other forks doing this
• 13:23
  selsta
  no other fork has a premine at height 1?
• 13:23
  selsta
  isn't this what all forks do?
• 13:23
  moneromooo
  :D
• 13:24
  tokenberry33
  They do this in genesis block i want for test reason to do in block 1 in block 111111 etc
• 13:25
  tokenberry33
  I want to c what will happen to fees if u change reward on some blocks.....
• 13:25
  tokenberry33
  Test!
• 13:27
  moneromooo
  I think I did this ages ago to test cumulative emission higher than 64 bit. I do not remember having to change anything else than get_block_reward for the actual reward change.
• 13:28
  moneromooo
  IIRC I rigged some high block to emit $LOTS.
• 13:29
  moneromooo
  If you don't want the hassle of adding height as a paramter, you can always do, eg, if emitted_so_far == 17e8, return $LOTS.
• 13:29
  moneromooo
  Replace 17e8 with the actual block 0 reward.
• 13:30
  moneromooo
  And for some high up block, there's a daemon command... prnt_coinbase_sum or so... which tells you the emitted amount. Use that for the next block.
• 13:34
  tokenberry33
  to change emission until block 10 for example
• 13:34
  tokenberry33
  Do u have this code to c
• 13:40
  tokenberry33
  How to change this line without changing code anywhere else
• 13:40
  tokenberry33
  const int emission_speed_factor = EMISSION_SPEED_FACTOR_PER_MINUTE - (target_minutes-1);
• 13:41
  tokenberry33
  "until height 10  EMISSION_SPEED_FACTOR_PER_MINUTE  = xxxxx "
• 13:58
  moneromooo
  I would just special case those heights in get_block_reward, and leave the general case alone.
• 14:03
  tokenberry33
  This function get_block_reward need to change on lot of files
• 14:03
  tokenberry33
  Do you have more elegant solution
• 14:07
  tokenberry33
  Do you remember where are your  test cumulative emission
• 14:12
  moneromooo
  I don't think I kept that. And it was a couple years ago now.
• 14:32
  tokenberry33
  Not possible to search on your disk with some specific pattern?
• 14:46
  tokenberry33
  Any elegant solution for this get_block_reward
• 14:47
  tokenberry33
  Let's not change anywhere only in cryptonote_basic_impl.cpp  file
• 15:11
  tokenberry33
  Moneromooo is possible to change only cryptonote_basic_impl.cpp file and not other because monero code is little messy and maybe touching messy things will bring more mess