<x​fedex:matrix.org> If I do a time-expensive RPC call to daemon, does it get executed in a different thread or it blocks all the RPC calls to monerod?

Mostly the latter.

<x​fedex:matrix.org> This includes the calc pow RPC method?

After looking, I think this one does not need the main lock.

Easy to see though. sleep(100) in the RPC endpoint, try to call another.

Hi there, I have a question about Monero. Can someone tell me if after introduction of CLSAG in Oxygen Orion, it was mandatory for transactions to use CLSAG over MLSAG, or is MLSAG still in use?

<x​fedex:matrix.org> No, MLSAG is not in use anymore, except for transactions prior to the fork

MLSAG was allowed for 720 blocks after the CLSAG fork (it happened in October 2020), then they were forbidden

<d​goon21:matrix.org> Hi. I have questions around the current checkpoint system for Monero nodes. I have been playing around with a radxa zero 1gb sbc. I have synced pruned nodes on it consistently in under a week, but this sync speed relies on monero dns checkpoints to do most of the heavy lifting. Is there currently any discussion or desire from the core devs to end the dns checkpoint system? Also if<clipped message>

<d​goon21:matrix.org> this system was ended, would there be any major downsides to adding my own checkpoints, such as 2 month old block hashes, to still get reasonable sync speeds on under powered devices? I don't believe there would be but I wanted to checkin to be sure. Thanks.

monero does not use DNS checkpoints

there is a system in place but as far as I know it has never been used

what you are talking about is likely the `--fast-block-sync` flag, but that one does not use any kind of DNS system

You can always custom compile and add your own fast sync hashes, but since they are reproducible you can also just confirm that the ones in the repository are correct.

<d​goon21:matrix.org> Thank you so much for the response. Does --fast-block-sync only use the hardcoded checkpoints in github.com/monero-project/monero/bl…rc/checkpoints/checkpoints.cpp#L210 ?

There are two different systems. One is for fast sync system and one is the checkpoint system you linked.

if you look at this link you can see this hash being changed: monero-project/monero #8805/files#diff-3dcea545b20bc1145f2766e64ca91d4e547d6072462970fd67830e1be6cdf793R5585

the file src/blocks/checkpoints.dat contains the fast sync hashes

you can generate it with this command: ./monero-blockchain-export --output-file checkpoints.dat --block-stop 2851000 --blocksdat

<d​goon21:matrix.org> If my understanding is correct, nodes use this checkpoint list up to block 2661600 and then they are left to fully verify the chain from there? This would leave the node to complete 10% of the sync with no fast-block-sync help?

<d​goon21:matrix.org> *roughly

No, the checkpoint list are just checkpoints. They don't have any verification benefits.

The fast sync system allows the daemon to skip known hashes, but that's separate from the checkpoint system you linked.

Unfortunately they have the same name in the source code so it's complicated to explain.

I set checkpoints and the fast sync hash usually to the same block height so yes the daemon would have to do 10% without any fast sync.

<d​goon21:matrix.org> That makes sense. Is there a reason the fast-sync hash list is only updated on major releases?

It's always updated in the release branch. It's rarely updated in the master branch.

but no specific reason otherwise apart from not having to do 2 PRs per release

<d​goon21:matrix.org> Thanks a lot for answering all my questions.

if someone uses master branch they can update it themselves :P