Quote from: CFAB on July 22, 2018, 02:03:19 AM

hey Serena Huh

its very obvious , oh wait guess youll tell us its not .

SURE Wink

I think your tinfoil hat needs adjustment.

Quote from: b9ron on July 22, 2018, 03:27:36 AM

Quote from: 0x000090 on July 21, 2018, 04:32:07 PM

Quote from: b9ron on July 21, 2018, 01:03:07 PM

At least your commits speak for themselves.

Mr Expert Blockchain Grin

That's just a cute way of yet again avoiding the point; can it be long now before your argument becomes accusing me of being mojo and/or serena? If you didn't mean to refute me, you should not have responded. But you did, and through your responses we have so far learned:

a) You have indicated that it is fine for the community to only have the ability to make pull requests, but not have any actual control over the project.
b) You have characterized dero as unfinished alpha stage software, and intimated that people should not use it like a bank, until "some years when everything will be stable with 0 risks and truly Open Source."
c) You demonstrate by point (b) that you do not understand that the blockchain is an immutable record, and that what happens with it now bears on whether people should trust it years from now.
d) You demonstrate by point (c) that you do not understand my initial point, which regarded the importance of being able to verify the code that was running on the network between the time the source was closed, and now.

This is what is meant when I say you have no understanding of blockchain; this, though it obviously escapes you, is what others can see by your words. And that rather than either agree or refute, you should instead point to a repo where I have forked a few projects, as though it says anything, rather than address the points themselves, says volumes.

The irony is that where I have not actually argued here against using or getting involved with dero, you yourself have inadvertently and voluntarily provided a few decent reasons why a person might do well to avoid it.

What are you talking about apple and orange once again ?

Yeah thanks, I know what's a Blockchain, is just a Data Structure a f*cking hashed linked list using hash instead of pointer... oh by the way, Dero isn't anymore a Blockchain but a DAG of hashed blocks.
My point was the code will be completely accessible in the future when the product will be ready not now in the early stage and if you can't deal with it, come back further.

The complete history of commit won't be publicly available until Dero Core Devs reveals their identity, that means it could probably never happen.

Once again bank doesn't trust any Blockchain Tech until they can control it or rewrite it from scratch.

Let's try this another way. Imagine that everyone who ran a monero node downloaded it in binary form from a specific server, and that you woke up tomorrow to news reports that this server had been found to have been compromised for the past two months -- the binaries had been replaced, and had been built by an unknown entity, using unknown code. The monero devs then recompiled from the current public sources, and all nodes updated to new binaries.

Should this affect people's trust in monero? Or should they say, oh well see the blockchain is a hashed linked list, and the source is public for the version now running, so everything is just fine, like you are doing for dero? Because the only functional difference between dero and this hypothetical is that the unknown entity is captain, so it comes down 100% to your trust in him, not in the code, not in the blockchain, not in anything else.

And the only way to change that, is to verify all the code (which as I have also pointed out, does not even suffice entirely, as you are still trusting that the code you see is what was actually running).