freenode #monero

16 Dec 2020

[XMR] Be excellent to each other and welcoming to newcomers || getmonero.org || Dev: #monero-dev || Pool related: #monero-pools || Price chat: #monero-markets || OTC: #monero-otc || People can & do log this channel || DON'T USE Changelly, Freewallet or Minergate: reddit.com/r/monero/wiki/avoid

• 02:15
  sethsimmons
  sysadmin64 are you in here?
• 02:33
  nioc
  sethsimmons: why would he be here? lulz
• 02:51
  sethsimmons
  Idk figured a troll who “compiles Linux from scratch” would know how to join a different IRC channel.
• 11:13
  Toophoned
  Are you working on v0.17.1.8 yet?
• 11:13
  dEBRUYNE
  ^ jess
• 11:13
  jess
  argh
• 11:58
  DavidFromBE
  downloads.getmonero.org/gui/win64install --> 0.17.1.6
• 11:59
  selsta
  DavidFromBE: caching issue, try private browser
• 12:00
  DavidFromBE
  indeed, thanks
• 13:24
  klotzhauer
  I'm running a local node and downloaded the entire blockchain. I see some sync issues. The client says "Daemon blocks remaining: 2(1)" and it needs 2 or 3 minutes to get in sync again. Computer hardware or my broadband connection shouldn't be an issue.
• 13:26
  selsta
  Please apply the block list: download gui.xmr.pm/files/block.txt and add `--ban-list /path/to/block.txt` to your daemon
• 13:27
  klotzhauer
  So it seems like a DoS issue?
• 13:28
  selsta
  Are you using CLI or GUI?
• 13:29
  selsta
  If you use CLI you can ignore it.
• 13:29
  klotzhauer
  gui atm
• 13:29
  selsta
  Yep, GUI needs the block list.
• 13:30
  selsta
  You can add the ban list flag in Settings -> Node -> Daemon startup flags
• 13:35
  klotzhauer
  added that list, and it seems the client is staying in sync. thanks!
• 13:35
  selsta
  There is an ongoing sybil attack, we are working on it but there will be a couple more releases ready until it is fully resolved.
• 13:36
  selsta
  Still, network operates fine.
• 13:37
  klotzhauer
  why is cli not affected?
• 13:39
  selsta
  The GUI expects the daemon to be synced, the CLI can transact even if the +2 issue is happening
• 14:20
  DavidFromBE
  running daemon on windows, it seems i'm always 2 block behind : Height: 2253489/2253491 (99.9%) on mainnet
• 14:21
  DavidFromBE
  so I can't send a tx because the wallet wants to wait for the sync to finish
• 14:23
  Lyza
  <DavidFromBE> reddit.com/r/Monero/comments/kdqj5i…d_at_first_without_ban_list/gfy1x01
• 14:24
  Lyza
  these are directions for adding the ban list. you can also still transact using the CLI without the ban list
• 14:24
  Lyza
  ban list will hopefully no longer be necessary soon but for now the GUI does still need it
• 14:29
  DavidFromBE
  Lyza: thank you so much
• 14:30
  Lyza
  you bet
• 19:33
  lza_menace
  is "THROW EXCEPTION: error::out_of_hashchain_bounds_error" in wallet rpc logs due to ongoing sybil?
• 21:03
  lza_menace
  resolved by reinstating the ban list and using latest tagged release
• 21:06
  anchor[m]
  I hope the ban list is only temporary
• 21:30
  sethsimmons
  Long term fixes are in the works, and a DNS-based ban-list should be available in the next point release.