test

<agentpatience> test ok.

Seems like running a full node works best when I use my own list that bans all TOR nodes. Black hats love to hide behind TOR.

.merges

.merge- 7272

Removed

.merge+ 7281 7282

Added

kayabaNerve: I tend to agree with mooo - there is precious little documentation around Monero's inner workings, the truth really is in the code

someone working on an alt implementation will need to literally keep tabs on every single PR and then figure out if it's something that has to be ported

it's a LOT of effort

fluffypony: Yep

that's how copy protction works in open source :P

hyc: Except you can just fork the node :P Not too hard to copy

"that's how copy protction works in open source :P" <-- bang on. I think that the value lies in human resources and in the ability to attract new productive members.

I was attracted because of switching to CPU mining and a working CCS system. I'm fed up with working for free.

But everybody has his own story I guess.

And regarding CPU mining - I also observed how the dynamics of BTC works. It's unsustainable. Mining BTC is only profitable at certain moments of the cycle. After the cycle, you may as well trash the ASIC miner, as it's of no use anymore.

So I though, that if anything prevails, it's the CPU oriented coins, and this is where I want to invest my time.

With Monero being the biggest one plus private. It's a matter of time until the public realizes it.

The only thing that could break it, is quantum computing, but this is for now a buzzword for me, rather than anything else.

I saw some claims that you need like 20 million qubits to break the cryptography

still up in the air if that is even remotely feasible

Inge-: Correct me if I'm wrong. Do you mean specifically "the current state of cryptography"? Can't we simply increase the number of bits of our algos if the processing power makes a leap?

My knowledge here is very shallow, but AFAIK yes, you can delay by adding bits. But it is hard to retroactively add bits to existing transactions on public ledgers.

Inge-: There has been a recent paper by MRL on the topic... github.com/insight-decentralized-co…/master/writeups/technical_note.pdf

For those who prefer video content, also an interview with the authors: monerotalk.live/post-quantum-monero-update

Thanks!

Hi

Lol @Inge- “But it is hard to retroactively add bits to existing transactions on public ledgers.” < yep

Anyways, from a cryptographic perspective, adding more bits only helps in some cases.

For attacks that involve Grover’s algorithm, its ability to find an input scales with O(N^1/2) so doubling the key size is a decent way to buy some time. :- )

However, the most likely & low hanging attacks on Monero’s cryptography would utilize Shor’s algorithm, which can factor large numbers and break the discrete log problem. In this case, adding more bits is NOT a robust way to increase security, because the task is a problem that is not “hard” (in the technical sense) for quantum computers.

It’s important to remember that quantum computers have paradigmatically-different abilities, and are not simply bigger or faster versions of current technology. The difference between a traditional computer and a quantum computer is analogous to the difference between a typewriter and a laptop. Sure, both can be used to take notes during a meeting, but a laptop can carry out functions (e.g. video editing) that a

typewriter fundamentally cannot.

So to mitigate those attack surfaces, instead of key size escalation, it’s necessary to switch to cryptography based on other mechanisms that fall into classes of problems that are “hard” for a quantum computer (e.g. shortest vector problem is hard for both classical & quantum computers)

Snipa: luigi1111w: we would need merges again :)

.merges

energizer bunnies I tell ya

Isthmus: <3

please also cli afterwards we need merges due to some conflict :P

“I thought, ‘I’m going to pump it and dump it,’ because I was interested and taking the ideas and implementing them in bitcoin. The bitcoin code base was far more interesting to me than monero, and I thought, ‘I’m not going to work on this codebase, it’s terrible,'” he recalls - fluffypony on Monero

jess: You need to save fluffypony's honor urgently ^^

Thanks for the comments.

on the testing parallelism.