interesting note about ext4 there, is btrfs similarly "safe"?

Monero Fluorine Fermi (v0.18.0.0) binaries are online at getmonero.org

^ ledger users do not upgrade yet, ledger version locks their app and there is mo update yet

no*

Still says: Current Version: 0.17.3.2 - Oxygen Orion on the site, yet downloads v18

Also hashes are still old.

Just want to take a moment to celebrate the first major released in almost two years!

Mochi101: it's a CDN issue, the non CDN version has the correct links web.getmonero.org/downloads

should be fixed once binaryFate comes online

2 years?

feels like yesterday

ok selsta

2020 was a forgettable year. it should count as 1 year tbh

Also we had ATH daily transactions today.

I've updated the CDN (again), it's quite an unclear and unrelieable UI that they keep changing every few months.

Hopefully good now

Please hard reload (like SHIFT+CTRL+R) and if still old, try with guest/anonymous window which forces fetching anew. Let me know

Mochi101 selsta ^

Good now, no hard reload required. Thanks binaryFate

TIL web browsers have hard reloads.

:/

The v0.18 CLI looks amazing!

Hypothetically speaking, If only BlackRock had the permission to add digitally-signed blocks (with BlackRock key) to the monero blockchain, how will they go about discarding transactions from bad actors? AFAIK, this can't be done because monero transactions are already indistinguishable from each other thanks to CLSAG, one-time-addresses, range proofs of pedersen commitments. So BlackRock won't know which transaction they are including or not-including

in the blocks under this hypothetical scenario. BlackRock could be handling transations from Sisters-of-Charity or a drug-cartel, so BlackRock won't know which transaction they are dealing with. So why do we require Monero to be permission-less?

For one thing, this kind of censorship would work by forcing you to disclose your tx details to BlackRock (or whatever censoring middleman). If you don't, they refuse to broadcast and mine your transaction

But the root problem with that line of reasoning is that since the network is open-source, nobody in their right mind would choose to accept to run a version of the software that allowed only BlackRock to mine blocks in the first place

So if they tried to push such a thing, they would just end up excluding themselves

And thanks to p2pool, we are now (potentially) immune to pool censorship too (if they ever got compromised or forced to implement such policies)

merope, what if I start a company called WhiteRock and I do not require anyone to reveal their tx secrets as per how I define the protocol. I alone can add digitally signed blocks with my key. And then I ask people to trust me that I will only mint/burn my Schmonero token, such that 1 SXMR = 1 USD. I think people will use Schmonero because exchange rate is pegged to USD. And if I add more features like Layer 2 channels that anyone can host, and settle

on my Layer 1, and have other features like easy to use atomic swaps, then people will come.

"then people will come" - you can't just assume that

maybefbi: you're welcome to fork Monero and make a centralized USD stablecoin. It won't be Monero lol

In fact, what you've just described is the definition of a bank

What if the company shuts down? We just no longer have a blockchain?

Like literally a traditional bank

kayabaNerve, yeah it will be Schmonero

maybefbi: call it... SWIFT

lol

While there are plenty of dumb crypto "investors", what you have there is a completely centralized system with you as a trusted middleman

agreed

but it will be anonymous

So you'd just join the pile of thousands of such "enterprises" who scammed a few dumb idiots of some money

the on-chain data might be anonymous, but users would almost certainly end up revealing their identity to you (even just accidentally, through ip/fingerprinting)

maybefbi: this is called mobilecoin

merope, ip/fingerprinting. this is a problem with Monero also.

jwinterm, let me look into mobilecoin and other such shitcoins lol

it is basically monero but the company that runs the signal messenger app launched it and they are in charge of verifying txs on the network

so it is like company verified monero

and definitely a low-tier shitcoin

not the same kind of problem, because you can run your own node, and transactions are relayed using Dandelion++ between nodes - so it's extremely hard/almost impossible to figure out which node first submitted a tx

maybefbi: endor00 kayabaNerve See existing research:

Li, Y., Yang, G., Susilo, W., Yu, Y., Au, M. H., & Liu, D. (2021). Traceable monero: Anonymous cryptocurrency with enhanced accountability.

there's also so many legal questions/concerns

Zhang, Y., & Xu, H. (2022). Accountable monero system with privacy protection.

Rucknium[m]: The discussion is full privacy, just without PoW.

Because why PoW when you can shim in a corp

... shouldn't this be in #monero-offtopic or literally any better channel?

Side note, the above research is interesting, even if I don't endorse it (in its proposed usage)

kayabaNerve: That's not how the discussion started in -dev

Rucknium[m], looking at it. thanks

This started in -dev? D:

Sorry then

I mean, it's a good discussion to be had - knowing why things work the way they do is just as important as knowing how they work, in environments like this

Oh. Yes. Just those more limited messages do suggest that research on how a corp could break privacy

Yet the above messages elaborated as "do not require anyone to reveal"

We have a new record. 2022-07-19 17:44:30.270 [P2P3] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:414 [216.174.105.167:18080 OUT] Sync data returned a new top block candidate: 2670961 -> 2671381 [Your node is 420 blocks (14.0 hours) behind]

This is the closed I have been to getting head in way too long

I just tried to send a transfer whlie 420 blocks behind and eventually got the error: Error: daemon is busy. Please try again later.

Is this just because the node is not fully synced?

It considers itself busy till it finished syncing once.

"Syncing" here is defined loosely, if you lose all peers I think it'll consider itself synced.

So I *think* out_peers 0 + out_peers 12 should basically tell it to start accepting RPC.

+in_peers

so frustrating. So its been over a week now and the node will not sync any closer to head than ~450 blocks. WHY?!?!

maybe it *is* syncd and one of its peers is lying about chain height?

well, I just --enable-dns-blocklist and see if that makes any difference running overnight. night all

At some point we should move to version 1.0

Maybe with Seraphis

duso: what is your current blockheight?

is it the same as on xmrchain.net ?

which version are you using?

Move versioning to 1.0 upon inclusion of Seraphis protocol monero-project/meta #721

duso, one thing to do is add "--add-priority-node " to your monerod startup, with the ip address of some node you kinda trust

gingeropolous: shouldn't be necessary on a normal working node

indeed

selsta: 2022-07-20 03:27:46.284 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:414 [92.117.219.164:18080 OUT] Sync data returned a new top block candidate: 2671189 -> 2671715 [Your node is 526 blocks (17.5 hours) behind]

duso: what is your current block height (enter status), what version are you running?

selsta: Monero 'Oxygen Orion' (v0.17.3.2-release) and Height: 2671189/2671701 (99.9%) on mainnet

as a first step i would recommend to update to v0.18.0.0

what is your computer hardware and what storage do you use? you said something about VM in the past IIRC

to review as briefly as possible - 6+ years ago built node in freebsd jail on FreeNAS. 9 Months ago upgraded FreeNAS FreeBSD 12.1 to TrueNAS FreeBSD 13 and monerod crashed, stopped syncing. 2 weeks built new jail and installed monerod, copied over old blockchain 9 months behind, worked, quickly synced to ~450 blocks behind but never any further

hardware is Intel xeon E3-1230v6 with 32GB ram backed with raidz1 ZFS array on rust drives.

If I stop the daemon running for a day, it will again quickly sync to about 450 blocks behind head, but can't seem to sync any further.

I will upgrade to monerod v0.18 as soon as its in the pkg repository

does it also start to ban peers?

selsta: ban or block? I see lots of blocked peers in the log

yes it's likely that your db has an issue

it fails to verify a block -> blocks peer thinking they are sending garbage data -> stays stuck

did you copy this from the node that crashed?

yes

use v0.18 plus sync from scratch, it should solve all the issues

selsta: so just delete the old blockchain and resync 130+ GB of data? Isn't there a way to recheck the old existing blockchain? I'm down here in country australia, 130GB is a lot of trips for carrier pidgeon internet here

you can run --prune-blockchain --sync-pruned-blocks which should reduce overall required traffic

but no, there is no "fix database" function

corruption can mean anything

ok, will try that