Pages:
Author

Topic: [ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts - page 98. (Read 123199 times)

jr. member
Activity: 37
Merit: 11
newbie
Activity: 185
Merit: 0
member
Activity: 246
Merit: 10
Token That Will Transform The Venture Capital Mark
I just saw your project. please tell me, will you conduct ico? if not, where can I get your tokens? and for what they will serve on your platform?
member
Activity: 308
Merit: 33
dero dev, bootstrap please I have slow connection to sync.

New code is faster to sync and haven't seen a single issue during syncing. P2P layer has been written from scratch to avoid network disconnects/dangling connections issues etc.
Download latest from http://seeds.dero.io/alpha/ and start derod* daemon. we do not recommend bootstrap chain database now.
Try syncing first and if you feel any sync issue, will arrange chain database.
newbie
Activity: 36
Merit: 0
I could not withdraw.

sorry
I could withdraw.
E-mail confirmation was required from yesterday.
It was moving to the junk e-mail box.
newbie
Activity: 36
Merit: 0
newbie
Activity: 80
Merit: 0
DERO wallets are back online on stocks.exchange https://stocks.exchange/trade/DERO/BTC .
Wallet are re-designed and written to handle millions of transactions and to work on low resources.
Users can deposit/withdraw any amount and no restrictions on withdraw limit.
Integrated payment address are used by stocks exchange for deposits, so no problem of missing payment_ID etc.
Thanks stocks exchange for integrating new DERO rpc commands in short time.
Numerous optimizations have been carried out in both DERO daemon and wallet. Each and every minute detail/problem is looked carefully and being solved in right manner.



Great. Thanks.
member
Activity: 126
Merit: 51
dero dev, bootstrap please I have slow connection to sync.
newbie
Activity: 105
Merit: 0
DERO wallets are back online on stocks.exchange https://stocks.exchange/trade/DERO/BTC .
Wallet are re-designed and written to handle millions of transactions and to work on low resources.
Users can deposit/withdraw any amount and no restrictions on withdraw limit.
Integrated payment address are used by stocks exchange for deposits, so no problem of missing payment_ID etc.
Thanks stocks exchange for integrating new DERO rpc commands in short time.
Numerous optimizations have been carried out in both DERO daemon and wallet. Each and every minute detail/problem is looked carefully and being solved in right manner.


"No restrictions on withdraw limit" - HELLYEA. Finally I can move my bag to my wallet. Keeping it on Stocks.exchange makes me nervous.  Cheesy
member
Activity: 308
Merit: 33
DERO wallets are back online on stocks.exchange https://stocks.exchange/trade/DERO/BTC .
Wallet are re-designed and written to handle millions of transactions and to work on low resources.
Users can deposit/withdraw any amount and no restrictions on withdraw limit.
Integrated payment address are used by stocks exchange for deposits, so no problem of missing payment_ID etc.
Thanks stocks exchange for integrating new DERO rpc commands in short time.
Numerous optimizations have been carried out in both DERO daemon and wallet. Each and every minute detail/problem is looked carefully and being solved in right manner.

newbie
Activity: 36
Merit: 0
stocks.exchange disabled deposit again
They disabled withdrawal of all coins .
Stopped after Dero's deposit succeeded yesterday.
Is it me only?
full member
Activity: 420
Merit: 184
The audit will accomplish being able to tell people who are concerned about the code release (of which there have been numerous) that an outsider audit has occurred and code will be released when it's ready. That buys the Dero team a longer runway to develop in private without community blowback.

As for auditing new releases, if the community thinks that would be beneficial I'd be willing to.

You haven't really addressed the two key points I brought up: 1) the audit team (or person) must be competent programming in golang; 2) any audit team or person which is competent in golang could also use their access to the source code - even if just read only - to push out an insta-fork coin.

Frankly, only a few people have complained about the source being closed currently, and CaptDero has said this is only temporary. I really don't get why any of you clamoring to see the source code are so vexed about this because any investment of time or hashrate into a crypocurrency is pretty much an act of faith in the first place (a bit ironic, I realize, given that cryptocurrencies are supposed to enable trustless transactions...). Yes, I understand the concern about CaptDero getting killed by a bolt of lightning or whatever and the project going tit's up as a result, but again, that seems to be a reasonable risk for maintaining a competitive advantage for a few more weeks.

If a competent and trustworthy team or even individual can be found to audit the code then I'm all for it getting audited; but if there is any doubt as to the trustworthiness, at least, then I am ABSOLUTELY AGAINST auditing it.
newbie
Activity: 16
Merit: 0
stocks.exchange disabled deposit again
member
Activity: 224
Merit: 11
Hello everyone, the team has gone over the feedback from the last several pages very thoroughly.

We completely understand where the feedback and discussions are coming from, and it's going to take us a little bit of time to bring everything together.

Dero is going to get the code out for the public to see when we can (you can all view it), and we will work very hard to build, and maintain your trust in all areas.
member
Activity: 223
Merit: 21
DCAB
I work in network security 9-5, which has hammered concerns into my head regarding any long running process with an internet connection.

I’d personally like to have an outsider audit the existing codebase because I believe I’m not the only one concerned with the delay of code release (seen numerous threads regarding this previously). I believe it could be a solid way to assure the community of the team’s intregrety, allow them to take their time with release, and overall be a net positive for the coin and it’s stakeholders

You make a compelling argument, and in principle I don't disagree with it, or the desire to have the audit done before proceeding further with development, but on a practical level there are two issues that make this somewhat difficult: the DERO team has to believe the external audit team is both competent (ie - capable of auditing their golang code) and trustworthy (ie - not likely to run off with said code and make their own insta-fork).

I'm not saying you aren't trustworthy... but I'm not saying you are, either.



Agreed, there is inherent risk. In a perfect scenario we wouldn't have to trust anyone. And I'm certainly  not saying you need to or even should be trusting me. There are issues with proving the outsiders doing the audit are trustworthy.

I'm not saying I should be the one to do the audit, I'd be honored for certain if the team and community would trust me with that, but not necessary.

However, on the flip side, having an outsider audit (the auditors would not need write access, only read) would distribute the level of the trust to part of the community and the team so new community members can feel better about CaptDero and the team's current dev cycle.
member
Activity: 223
Merit: 21
DCAB
I'd prefer just waiting the extra days/weeks for the focus of code to be released, rather than diverting attention to setup an alpha auditing group to appease a handful of community members, when the code will be changing post audit.  Seems pointless.
...

Yeah, I totally agree. @cpmcgrat has posted some good stuff in this thread, and overall I agree with his position that the code should be audited* but I also think his panties are too tightly wadded, so to speak. I also can't help but point out that this sort of complaining only tends to happen when a market is in a bear trend; everyone loved Facebook and saw no problem with its egregious data collection practices until Cambridge Analytica came along and used that data to influence much of the US to vote for The Donald (don't blame me - I always vote for the Libertarian candidate).


* -  but for very different reasons, I suspect - I'm way more concerned about bugs like the kind that enabled a hacker to take over the entire Verge network and mine 20M coins.

I work in network security 9-5, which has hammered concerns into my head regarding any long running process with an internet connection.

I’d personally like to have an outsider audit the existing codebase because I believe I’m not the only one concerned with the delay of code release (seen numerous threads regarding this previously). I believe it could be a solid way to assure the community of the team’s intregrety, allow them to take their time with release, and overall be a net positive for the coin and it’s stakeholders


Yeah, a lot of us have technical backgrounds. Why don't you audit the code that is already posted?  Since the code will be changing until release (still in alpha right now) what will the audit accomplish?  You want to audit every release moving forward as well?



The audit will accomplish being able to tell people who are concerned about the code release (of which there have been numerous) that an outsider audit has occurred and code will be released when it's ready. That buys the Dero team a longer runway to develop in private without community blowback.

As for auditing new releases, if the community thinks that would be beneficial I'd be willing to.
jr. member
Activity: 35
Merit: 1
I'd prefer just waiting the extra days/weeks for the focus of code to be released, rather than diverting attention to setup an alpha auditing group to appease a handful of community members, when the code will be changing post audit.  Seems pointless.
...

Yeah, I totally agree. @cpmcgrat has posted some good stuff in this thread, and overall I agree with his position that the code should be audited* but I also think his panties are too tightly wadded, so to speak. I also can't help but point out that this sort of complaining only tends to happen when a market is in a bear trend; everyone loved Facebook and saw no problem with its egregious data collection practices until Cambridge Analytica came along and used that data to influence much of the US to vote for The Donald (don't blame me - I always vote for the Libertarian candidate).


* -  but for very different reasons, I suspect - I'm way more concerned about bugs like the kind that enabled a hacker to take over the entire Verge network and mine 20M coins.

I work in network security 9-5, which has hammered concerns into my head regarding any long running process with an internet connection.

I’d personally like to have an outsider audit the existing codebase because I believe I’m not the only one concerned with the delay of code release (seen numerous threads regarding this previously). I believe it could be a solid way to assure the community of the team’s intregrety, allow them to take their time with release, and overall be a net positive for the coin and it’s stakeholders


Yeah, a lot of us have technical backgrounds. Why don't you audit the code that is already posted?  Since the code will be changing until release (still in alpha right now) what will the audit accomplish?  You want to audit every release moving forward as well?

full member
Activity: 420
Merit: 184
In other news, the spikes in hashrate on the DERO network pale in comparsion to what Intensecoin is seeing: from ~4MH/s to >35MH/s. Their fork is scheduled to happen in about a month, so this ought to be interesting to watch.

full member
Activity: 420
Merit: 184
I work in network security 9-5, which has hammered concerns into my head regarding any long running process with an internet connection.

I’d personally like to have an outsider audit the existing codebase because I believe I’m not the only one concerned with the delay of code release (seen numerous threads regarding this previously). I believe it could be a solid way to assure the community of the team’s intregrety, allow them to take their time with release, and overall be a net positive for the coin and it’s stakeholders

You make a compelling argument, and in principle I don't disagree with it, or the desire to have the audit done before proceeding further with development, but on a practical level there are two issues that make this somewhat difficult: the DERO team has to believe the external audit team is both competent (ie - capable of auditing their golang code) and trustworthy (ie - not likely to run off with said code and make their own insta-fork).

I'm not saying you aren't trustworthy... but I'm not saying you are, either.

newbie
Activity: 105
Merit: 0
Stocks.exchange deposits/withdrawals seems to be back online. Are we now safe to withdraw larger amounts?
Pages:
Jump to: