Pages:
Author

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

jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
Guys, do you realise how *tiny* Dero's daily trading volume is?

I just checked over on coincodex.com.  If the figure is accurate for the past 24 hours... a little over $20,000.  This is almost literally *nothing*.  It is 0.0001% of the total daily trading volume of all cryptos tracked by coinmarketcap.  It is 0.02% of Monero's 24h trading volume.

And how cheap it is.  It is still possible to acquire, relatively speaking, a substantial portion of the total supply.  For less than $500 you get about 0.05% of the currently circulating supply.  In comparison, for the same amount, you get 0.0000003% of currently circulating bitcoin, and 0.00001% of currently circulating Monero.

If Dero lives up even to half its potential, we are in for a wild ride over the next few years.
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
::)difficulty of monero hashrate is 515MH for 220$ price. DERO Difficulty 40MH for 49cents price. It's about 10X time bigger then it need to be. 6-8MH is a maximum hashrate for Dero, Developers work hard, i know. Now i switch to mode "invest step by step". GPU mining died this day, this is hard work to develop anti-asic resist, will waiting. Don't panic, DERO is a long-term project, nothing scared happened now, hope soon all would done and hashrate come back to 6-8-10MH. Wink

Here's a question.  Although I am not sure you are correct to compare hashrates and raw price directly quite like this, I agree difficulty for Dero is very high.  But why is this?  Shouldn't market forces ensure that the difficulty for each coin is about right, in terms of capital expenditure and energy costs for mining each coin?  Perhaps the reason is that the market thinks that the *potential* for Dero is higher than other coins, therefore justifying a higher current difficulty than for other comparable coins based on their *current* market price?

Possibly in partial answer to my own question, perhaps asics are dumping on Dero more than other coins because Dero is still using an asic-compatible POW version, whereas many other coins have changed their POW to try to defeat ASICs.  But I don't know.

I think I have an even better answer now, which is obvious in retrospect.  If you look at cryptunit.com, you'll notice immediately that all the more profitable coins are the CryptoNightV7 ones, and all the Cryptonight (classic, let's say) coins are down the toilet.  The difference is really substantial; we are talking nearly an order of magnitude.  It makes no sense at all right now to be mining any Cryptonight classic coins on your own CPU/GPU hardware (and I have stopped for the meantime).

However, look over at nicehash.  There market forces ensure that CryptonightV7 and Cryptonight classic coins are more or less equally profitable; the current bid price for V7 is in the region of 0.1965 bitcoin/mH/day, while for classic it is in the region of 0.03, a whopping difference and which roughly corresponds to the differences in profitability on cryptunit.   In fact I nicehashed some Dero over the past few days using some bitcoin and it made perfect sense - if anything it is actually slightly more profitable (or worthwhile, depending on your aims here) to use nicehash for the older Cryptonight classic than to use it for the V7.  The ask prices for hashes seem more stable on Cryptonight classic too, which means it is easier to lowball your bid price and still secure the hashes you need.  (Incidentally, I got slightly more coins by using nicehash than I would on stocks.exchange - about 10% more - or the even pricier southxchange; if you try it, just make sure you lowball your offer so much you are only getting your order filled about 50% of the time and ignore all the warning emails.)

I suspect nearly all the hashrate for Dero and the other classic coins right now is due to a combination of asics and nicehash.  We are waiting longer than the others for a POW update, but I suspect, knowing our devs, that the wait will be worth it...
member
Activity: 224
Merit: 11
                                                   


How to start using Dero                Downloads                Whitepaper                Support      



About DERO  

The Dero Project has written a unique new blockchain technology that is based on the CryptoNote protocol. Dero's goal is to create a unique state of the art blockchain technology with enhanced reliability, privacy, security, usability, and portability by bringing together some of the best proven technologies like the CryptoNote protocol and smart contracts, thereby allowing for the creation of truly private smart contracts.

The Dero development team has implemented complete SSL across the Dero network which is a first on any blockchain. This encrypts the entirety of our network traffic, which greatly reduces our attack surface, while simultaneously preventing ISPs or other users from analyzing Dero’s network traffic.




Dero's Key Features  

  • DERO is a completely new and unique CryptoNote blockchain written in Golang
  • DERO is the first blockchain to have complete SSL in the P2P layer
  • DERO will be the first CryptoNote blockchain to have 500 transactions per second on its native blockchain without any lightning networks, validators or off-blockchain solutions
  • DERO will be first CryptoNote blockchain to have smart contracts on its native chain without any extra layers or secondary blockchains
  • CryptoNote privacy
  • Smart contracts
  • Atomic swaps
  • Mobile and offline wallets
  • Lightweight wallets
  • Subaddresses
  • Escrow services on the blockchain
  • Address signing and certifying
  • Voting on a private blockchain




About The Developers  


There are three developers working on the Dero Project who have been working in the field of cryptography and blockchain development as a team for more than a decade. Dero's research and development team are devoted full time to the project, and can often be found in our Slack channel. For now, the development team are choosing to retain their privacy until the Dero Project incorporates.




Coin Specifications  
 

  • Proof-of-work (PoW) algorithm: CryptoNight
  • Max supply: 18.4 million for the first 8 years followed by an infinite emission rate after year 8 of ~157,000 DERO/year
  • Block reward: Smoothly varying
  • Block time: 120 seconds
  • Difficulty: Retargets at every block
  • Ticker: DERO




Dero's Roadmap  

 
  • Q1/2018 - Dero's new unique blockchain written and full Activation. - Completed ahead of schedule with the extra addition of complete SSL across Dero's network
  • Q2/2018 - Record CryptoNote TX/sec, GUI wallets, sub addresses, atomic swaps, and smart contract testing.
  • Q3/2018 - Smart contract support on chain. Q3 2018.
  • Q4/2018 - Strategic market expansion, team growth, and more (coming soon).




Dero Related Links  

Resource Links  

WEBSITE: https://dero.io/
FORUM: https://forum.dero.io/
EXPLORER: https://explorer.dero.io
OFFICIAL POOL: http://pool.dero.live/
BINARIES: http://seeds.dero.io/alpha/

Exchanges & Stats:

EXCHANGE: https://stocks.exchange/trade/DERO/BTC
EXCHANGE: https://www.southxchange.com/Balance/Index/DERO
Stats: https://coincodex.com/crypto/dero/
Stats: https://www.difficultychart.com/dero
Stats: https://www.cryptunit.com/coin/DERO





Articles and Media Content  


Dero: A new blockchain technology that brings CryptoNote privacy together with smart contracts.


Shifting from alpha to beta: CryptoNote with smart contracts





Support
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
I’ve been monitoring the network hashrate and many other things very closely, and the time has come where we are going to provide an update to everyone in the next 36 hours or less.

The Dero team will do our best to provide some clarity and transparency about what the development team has been up to, an update about where we’re headed, and how we plan to tackle the problem.

So, a network hashrate exceeding 35 MH/s and price cratering to ~$0.36US got your attention, eh? Well, this announcement ought to be interesting...

EDIT - I did manage to snag about 300 DERO before price rebounded. Thanks, suckas, for the cheap coinz.  Grin

I tried to take advantage too, but the ever reliable Stocks.Exchange managed to lose two XMR deposits for almost a week. They got it sorted out this morning about half a day too late to pick up some cheap DERO. Sigh.

Having said that, if you take the long term view that DERO is headed to a price in the triple digits (USD) then the difference between $0.35 and $0.50 is trivial.

Looking forward to the announcement. Hopefully it's an ASIC killer and we can get back to mining.

Regarding the small absolute difference in price now between $0.35 and $0.50, it depends on your approach.  It's still a big percentage difference.  Let's suppose we have $100 to invest.  That would buy 285 coins at the lower of these two prices, and 200 at the higher price of $0.50.  Fast forward to a hypothetical time when the coins are worth $100, and the difference is not trivial at all.  The small differences in price now magnify out.

It is only trivial if your aim is to acquire a certain number of coins within a certain time window (say the next month or whatever) and you will buy that number at whatever the price happens to be.  The cost difference now it won't make any difference a few years down the line when the price has increased substantially. 

But how many people are investing using the second approach?  Speaking for myself, I have a certain amount to invest, and I am trying to do it as wisely as possible.  I bet that is most people's approach in fact.  Anyway, for myself these small differences that are big in percentage terms do matter but I try not to be sad about them... there is more to life isn't there?
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
First, thanks to the Devs for all the work put into this project, and getting milestones achieved ahead of schedule.  Also, although I was initially sceptical, I see now the logic of waiting until the code is release or beta at least (currently it is only alpha) before releasing it as open source.  Patience, folks!  And now finally that I have my hardware issues sorted and my wallet is syncing, I do appreciate the newer and much speedier daemon sync.  Good work!

I am looking forward to the proof of work update, which I assume is the next major update in the pipeline that has been hinted at in recent days.  I wonder if Dero will go the IPBC route, and release a custom POW algorithm.  I see little point in going the V7 route, as most cryptonight coins have chosen to jump on Monero's bandwagon, and surely it will just be a matter of time before there are ASICS for that, too.  Is it technically possible to change the POW algorithm enough to defeat ASICS but not so much as to require a hard fork?  Now that would be a real cat-in-the-bag....
jr. member
Activity: 35
Merit: 1
...
Something of note though, when I run derod I get audio cracks whenever I play a video (VLC/Youtube/Twitch). This has never happened on this PC for the 6 years of its life.
...

I also reported that the new daemon appears to be very resource-hungry while syncing. It dramatically reduces CPU/whatever use when it does finally get all caught up, however.




Yes, from what I can tell it utilizes all CPU cores to increase performance.  Most applications keep core0 open to not disrupt minor operations.
full member
Activity: 420
Merit: 184
...
Something of note though, when I run derod I get audio cracks whenever I play a video (VLC/Youtube/Twitch). This has never happened on this PC for the 6 years of its life.
...

I also reported that the new daemon appears to be very resource-hungry while syncing. It dramatically reduces CPU/whatever use when it does finally get all caught up, however.

newbie
Activity: 5
Merit: 0
I tried running derod-windows-amd64.exe. It ran well until block 59960 and now fails with:

Code:
Block verification failed  rejecting since TX verification failed   blid=d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 com=BLKCHAIN

That same message repeats over and over.

Did my db get corrupted? Should I start from scratch?

I now run the latest version of derod*(2018-04-14 12:41) and was running the very previous one in the beginning.

Digging your issue.

Re-builded the whole chain from scratch and found no problem. Can you pls try to rebuild again. Stop derod daemon and delete the mainnet folder and try again.

So I finally got around to starting from scratch and synced over several days until I got to block 60707

Code:
Block verification failed  rejecting since TX verification failed   blid=a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc com=BLKCHAIN

That's on a stable PC, on an SSD but with an old 2500k though so it takes quite some time to sync. I think I'll try again when I get a better CPU sometime next month. Maybe I'll compile and sync on Linux at some point too.

Something of note though, when I run derod I get audio cracks whenever I play a video (VLC/Youtube/Twitch). This has never happened on this PC for the 6 years of its life.

Here is some more log if it's any help, first from last time the problem happened and then today's one

Code:
2018-04-14T12:57:00+02:00 DEBUG    : Deep Checks for block 7a5e475928b02ff838a6be7b9b9ac62dd792a474cf6343aa5b3bde44cf372d47 height 59958 cksum length 57866 
2018-04-14T12:57:03+02:00 DEBUG    : Deep Checks for block b0d6bd405872cf16cc4eccd9f2f113b7647c9bcb23a77bfd45165c04efa3a907 height 59959 cksum length 57866
2018-04-14T12:57:04+02:00 DEBUG    : Deep Checks for block d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 height 59960 cksum length 57866
2018-04-14T12:57:05+02:00 INFO     : level=warning msg="Block verification failed  rejecting since TX verification failed " blid=d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 com=BLKCHAIN
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 current block c73f520b96dec02fb7b8b568acc4b6b2212ba4c2f84027859b716cc0456b6798 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash c73f520b96dec02fb7b8b568acc4b6b2212ba4c2f84027859b716cc0456b6798 current block c3ae03fa47f29882715f85fd608e96d90c77276f18d6a2939b54fcfe7fd0f7bd no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash c3ae03fa47f29882715f85fd608e96d90c77276f18d6a2939b54fcfe7fd0f7bd current block cecd3cab31b51f45355025a3a80e240faba35f61b4e138a274bc3d9c8577635d no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash cecd3cab31b51f45355025a3a80e240faba35f61b4e138a274bc3d9c8577635d current block 95eb486fc90fd371fb7e90494ef81dee873995d7083ef264af43fdf876e773de no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash 95eb486fc90fd371fb7e90494ef81dee873995d7083ef264af43fdf876e773de current block 899a16d95959f4c9f04cdf1fb5c3f81a930b24f2498ddc490d9469aae3729d9f no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash 899a16d95959f4c9f04cdf1fb5c3f81a930b24f2498ddc490d9469aae3729d9f current block eb5e57b517559c6fd7d41fab39bf3d9d2eac736f48f2dda2715a327e497bf738 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash eb5e57b517559c6fd7d41fab39bf3d9d2eac736f48f2dda2715a327e497bf738 current block c6f4a5687336284be3395a250e90baf399a039db9dbceb85671146180806cc57 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash c6f4a5687336284be3395a250e90baf399a039db9dbceb85671146180806cc57 current block 381347e8ca612ff56e4d6833b2d05a203bfaf8e2d2d69443104a019cfd81f824 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash 381347e8ca612ff56e4d6833b2d05a203bfaf8e2d2d69443104a019cfd81f824 current block a38befab303db79bcfd24b3fdeb19f509fb4d05ecab48955eb039830419157d6 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash a38befab303db79bcfd24b3fdeb19f509fb4d05ecab48955eb039830419157d6 current block d73f4e1f8511a4af3778fc64dc76d88bb6747f7082792b76764b57c8f250deaa no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash d73f4e1f8511a4af3778fc64dc76d88bb6747f7082792b76764b57c8f250deaa current block 5ff51ff1a1430d612bbe9e28b7f1616f8339ba02cb0c6483eb4922c94c047cad no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash 5ff51ff1a1430d612bbe9e28b7f1616f8339ba02cb0c6483eb4922c94c047cad current block 766a4742ba0ae717b166b39a431c5d9a071a9b5bee11b579767e5466cd0e9048 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash 766a4742ba0ae717b166b39a431c5d9a071a9b5bee11b579767e5466cd0e9048 current block bcf33f53e11aaa9d3b5bfcdf581bb48d144402767f127bcb4c730ad3507637f9 no where in the chain, skipping it till we get a parent
2018-04-14T12:57:05+02:00 WARN     : Prev_Hash bcf33f53e11aaa9d3b5bfcdf581bb48d144402767f127bcb4c730ad3507637f9 current block 7f5b5ad587522ebc1904ca00a76a63961d672a04ddd9c68b8231a4911a0e27ce no where in the chain, skipping it till we get a parent
2018-04-14T12:57:07+02:00 DEBUG    : Deep Checks for block d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 height 59960 cksum length 57866
2018-04-14T12:57:08+02:00 INFO     : level=warning msg="Block verification failed  rejecting since TX verification failed " blid=d114638b05d78d8ea88eaf3c7468da1fd631f11d2548524204edf569be73a380 com=BLKCHAIN

Code:
2018-04-19T19:22:38+02:00 DEBUG    : Deep Checks for block a2a741d29635c25073b1b5863de39a8daf09da59cd42a41b4ec045166b25eb70 height 60700 cksum length 57866 
2018-04-19T19:22:39+02:00 DEBUG    : Deep Checks for block eac794b64c9d090d2f8c16304ee5a530064930e5207fed8df34640dc9951c517 height 60701 cksum length 57866
2018-04-19T19:22:41+02:00 DEBUG    : Deep Checks for block 733a911c256033b368bf5ae3f8897d79a7e0bf194cc520c27d2f059cf6fdd3cd height 60702 cksum length 57866
2018-04-19T19:22:41+02:00 WARN     : Dial failed err dial tcp 89.38.96.169:18089: connectex: No connection could be made because the target machine actively refused it.
2018-04-19T19:22:41+02:00 DEBUG    : Deep Checks for block 5e727d0ce22bf3c47b12a0fba206a7aadad0a6e1e9e32db6d9d96b5f65d6ac45 height 60703 cksum length 57866
2018-04-19T19:22:42+02:00 DEBUG    : Deep Checks for block 4f40a0b420c43709fd21ae615588c68d759eeb9118c77226db46f2e8cee7c9a7 height 60704 cksum length 57866
2018-04-19T19:22:42+02:00 DEBUG    : Deep Checks for block 488210de41b040d185d0454ae65733f7d5b3d11dbea7b4b78ce4651a88cf6dd4 height 60705 cksum length 57866
2018-04-19T19:22:43+02:00 DEBUG    : Deep Checks for block eb687908e9976338dec1d755cf559bfe968e41dd2059f0d5d0a210fa8084385c height 60706 cksum length 57866
2018-04-19T19:22:43+02:00 DEBUG    : Deep Checks for block a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc height 60707 cksum length 57866
2018-04-19T19:22:43+02:00 INFO     : level=warning msg="Block verification failed  rejecting since TX verification failed " blid=a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc com=BLKCHAIN
2018-04-19T19:22:43+02:00 WARN     : Prev_Hash a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc current block 9df6df04af43707cfca2ca2ccf8ff93bad54d2930e89782b85dc6a34376292f1 no where in the chain, skipping it till we get a parent
2018-04-19T19:22:43+02:00 WARN     : Prev_Hash 9df6df04af43707cfca2ca2ccf8ff93bad54d2930e89782b85dc6a34376292f1 current block 289abb5dad3b24d76133b199d2bafc5c54a31354166e47c46d1bdbb472525a82 no where in the chain, skipping it till we get a parent
2018-04-19T19:22:43+02:00 WARN     : Prev_Hash 289abb5dad3b24d76133b199d2bafc5c54a31354166e47c46d1bdbb472525a82 current block 5cb5f10d43e39d55238c2040c89adde88665843445bda94949de7244035a4cce no where in the chain, skipping it till we get a parent
2018-04-19T19:22:44+02:00 DEBUG    : Deep Checks for block a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc height 60707 cksum length 57866
2018-04-19T19:22:44+02:00 INFO     : level=warning msg="Block verification failed  rejecting since TX verification failed " blid=a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc com=BLKCHAIN
2018-04-19T19:22:44+02:00 WARN     : Prev_Hash a8d4e1b02c5b3123c42c59df2f427ad76ea875fa9ec463c5fba004aeef5f85cc current block 9df6df04af43707cfca2ca2ccf8ff93bad54d2930e89782b85dc6a34376292f1 no where in the chain, skipping it till we get a parent
2018-04-19T19:22:44+02:00 WARN     : Prev_Hash 9df6df04af43707cfca2ca2ccf8ff93bad54d2930e89782b85dc6a34376292f1 current block 289abb5dad3b24d76133b199d2bafc5c54a31354166e47c46d1bdbb472525a82 no where in the chain, skipping it till we get a parent
sr. member
Activity: 504
Merit: 254

Yes, good old stocks.exchange takes incompetence to depths that would make the Mariana Trench envious.  I really like how you have to go through CloudFlare's DDOS check every 5 minutes on their site, too; it makes me feel totally secure they know what they are doing over there.  Tongue

But, yeah - I do take the long view on DERO (thanks in part to our previous discussions, I should note), however, I did stop mining because seeing my mightiest* 1.9kH/s CN rig get reduced to bring in like 1 DERO per day was too depressing to contemplate. It also does ~56MH/s on Ethash so switched it over to MUSIC while all this forking gets sorted out.

* - admittedly not mighty, but GPUs were very hard to come by.

The whole exchange is, as we like to say back in the Motherland, "as useful as a chocolate teapot". Too bad as it's currently far better to mine XMR and buy DERO. My poor old HD7950s with a combined ~10KH/s would currently get 5.5 DERO per day, or I can mine XMR and buy 7x that many. Easy math.

full member
Activity: 420
Merit: 184
So, a network hashrate exceeding 35 MH/s and price cratering to ~$0.36US got your attention, eh? Well, this announcement ought to be interesting...

EDIT - I did manage to snag about 300 DERO before price rebounded. Thanks, suckas, for the cheap coinz.  Grin

I tried to take advantage too, but the ever reliable Stocks.Exchange managed to lose two XMR deposits for almost a week. They got it sorted out this morning about half a day too late to pick up some cheap DERO. Sigh.

Having said that, if you take the long term view that DERO is headed to a price in the triple digits (USD) then the difference between $0.35 and $0.50 is trivial.

Looking forward to the announcement. Hopefully it's an ASIC killer and we can get back to mining.

Yes, good old stocks.exchange takes incompetence to depths that would make the Mariana Trench envious.  I really like how you have to go through CloudFlare's DDOS check every 5 minutes on their site, too; it makes me feel totally secure they know what they are doing over there.  Tongue

But, yeah - I do take the long view on DERO (thanks in part to our previous discussions, I should note), however, I did stop mining because seeing my mightiest* 1.9kH/s CN rig get reduced to bring in like 1 DERO per day was too depressing to contemplate. It also does ~56MH/s on Ethash so switched it over to MUSIC while all this forking gets sorted out.

* - admittedly not mighty, but GPUs were very hard to come by.
sr. member
Activity: 504
Merit: 254
I’ve been monitoring the network hashrate and many other things very closely, and the time has come where we are going to provide an update to everyone in the next 36 hours or less.

The Dero team will do our best to provide some clarity and transparency about what the development team has been up to, an update about where we’re headed, and how we plan to tackle the problem.

So, a network hashrate exceeding 35 MH/s and price cratering to ~$0.36US got your attention, eh? Well, this announcement ought to be interesting...

EDIT - I did manage to snag about 300 DERO before price rebounded. Thanks, suckas, for the cheap coinz.  Grin

I tried to take advantage too, but the ever reliable Stocks.Exchange managed to lose two XMR deposits for almost a week. They got it sorted out this morning about half a day too late to pick up some cheap DERO. Sigh.

Having said that, if you take the long term view that DERO is headed to a price in the triple digits (USD) then the difference between $0.35 and $0.50 is trivial.

Looking forward to the announcement. Hopefully it's an ASIC killer and we can get back to mining.
newbie
Activity: 5
Merit: 0
Thank's DERO project for fast support and answers
full member
Activity: 420
Merit: 184
I’ve been monitoring the network hashrate and many other things very closely, and the time has come where we are going to provide an update to everyone in the next 36 hours or less.

The Dero team will do our best to provide some clarity and transparency about what the development team has been up to, an update about where we’re headed, and how we plan to tackle the problem.

So, a network hashrate exceeding 35 MH/s and price cratering to ~$0.36US got your attention, eh? Well, this announcement ought to be interesting...

EDIT - I did manage to snag about 300 DERO before price rebounded. Thanks, suckas, for the cheap coinz.  Grin
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
I am having some issues with the wallet.  First attempt switching over to new Golang wallet.  The daemon is synced (though with warning messages about TX rejected due to low fees - I assume I can ignore these messages?) but the wallet is unable to sync and just crashes after a partial sync with partial balance at 33246/62895:

unexpected fault address 0x38c1040

fatal error: fault
[signal 0xc0000005 code=0x0 addr=0x38c1040 pc=0x6a67a8]

followed by a bunch of stuff I can copy and paste into a PM if necessary.
Pls PM and also send the wallet logs created in same directory(upload somewhere and PM link).
Also include details of OS/arch and output of version command.

I apologise for potentially wasting CaptDero's time on this (though not sure if s/he spent any or not).

It turns out, I believe, that the issue was insufficient disk space.  I noticed that the free space on the disk was very low, and once I cleared out some files, the problem went away.
member
Activity: 224
Merit: 11
I’ve been monitoring the network hashrate and many other things very closely, and the time has come where we are going to provide an update to everyone in the next 36 hours or less.

The Dero team will do our best to provide some clarity and transparency about what the development team has been up to, an update about where we’re headed, and how we plan to tackle the problem.
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
::)difficulty of monero hashrate is 515MH for 220$ price. DERO Difficulty 40MH for 49cents price. It's about 10X time bigger then it need to be. 6-8MH is a maximum hashrate for Dero, Developers work hard, i know. Now i switch to mode "invest step by step". GPU mining died this day, this is hard work to develop anti-asic resist, will waiting. Don't panic, DERO is a long-term project, nothing scared happened now, hope soon all would done and hashrate come back to 6-8-10MH. Wink

Here's a question.  Although I am not sure you are correct to compare hashrates and raw price directly quite like this, I agree difficulty for Dero is very high.  But why is this?  Shouldn't market forces ensure that the difficulty for each coin is about right, in terms of capital expenditure and energy costs for mining each coin?  Perhaps the reason is that the market thinks that the *potential* for Dero is higher than other coins, therefore justifying a higher current difficulty than for other comparable coins based on their *current* market price?

Possibly in partial answer to my own question, perhaps asics are dumping on Dero more than other coins because Dero is still using an asic-compatible POW version, whereas many other coins have changed their POW to try to defeat ASICs.  But I don't know.
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
Been getting "Result rejected by the pool" across all my miners, and "SOCKET ERROR - your IP is banned" on one of them (but only one).  This has been going on a while - have endless screenfuls of these messages - seems I have been burning through electricity for nothing.

Have now stopped and restarted the miners, and the problem seems to have gone away, for now.  There have been no recent config or miner changes.  What could cause this to happen all of a sudden, and then go away as mysteriously as it came?

Is this with xmr-stak? If so, it happens to me occasionally, but only when mining DERO for some reason. Just like for you stopping and restarting the miners (after the requisite 10 minute ban passes) solves the problem.


If you are using vardiff, the base diff was increased to prevent webminers. Try fixed diff.

Edit:  In case you need the fixed diff calculation, it is [ hashrate x 30 ] and in xmr-stak you can set up fixed diff like so:  WalletAddress.Difficulty+WorkerName (Official Pool)

Thanks for these answers.  I realised that I am using a quite-out-of-date version of xmr-stak so I've upgraded to the latest version (published 12 hours ago) and am trying that.  If I still run into problems I'll try using fixed hashrate.

EDIT: I am using fixed hashrate anyway.  Seems like a good idea.  Latest versions of xmr-stak give you web access to your miners which is very nice for monitoring.
jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
::)difficulty of monero hashrate is 515MH for 220$ price. DERO Difficulty 40MH for 49cents price. It's about 10X time bigger then it need to be. 6-8MH is a maximum hashrate for Dero, Developers work hard, i know. Now i switch to mode "invest step by step". GPU mining died this day, this is hard work to develop anti-asic resist, will waiting. Don't panic, DERO is a long-term project, nothing scared happened now, hope soon all would done and hashrate come back to 6-8-10MH. Wink

Here's a question.  Although I am not sure you are correct to compare hashrates and raw price directly quite like this, I agree difficulty for Dero is very high.  But why is this?  Shouldn't market forces ensure that the difficulty for each coin is about right, in terms of capital expenditure and energy costs for mining each coin?  Perhaps the reason is that the market thinks that the *potential* for Dero is higher than other coins, therefore justifying a higher current difficulty than for other comparable coins based on their *current* market price?

newbie
Activity: 5
Merit: 0
 ::)difficulty of monero hashrate is 515MH for 220$ price. DERO Difficulty 40MH for 49cents price. It's about 10X time bigger then it need to be. 6-8MH is a maximum hashrate for Dero, Developers work hard, i know. Now i switch to mode "invest step by step". GPU mining died this day, this is hard work to develop anti-asic resist, will waiting. Don't panic, DERO is a long-term project, nothing scared happened now, hope soon all would done and hashrate come back to 6-8-10MH. Wink
jr. member
Activity: 35
Merit: 1
Been getting "Result rejected by the pool" across all my miners, and "SOCKET ERROR - your IP is banned" on one of them (but only one).  This has been going on a while - have endless screenfuls of these messages - seems I have been burning through electricity for nothing.

Have now stopped and restarted the miners, and the problem seems to have gone away, for now.  There have been no recent config or miner changes.  What could cause this to happen all of a sudden, and then go away as mysteriously as it came?

Is this with xmr-stak? If so, it happens to me occasionally, but only when mining DERO for some reason. Just like for you stopping and restarting the miners (after the requisite 10 minute ban passes) solves the problem.




If you are using vardiff, the base diff was increased to prevent webminers. Try fixed diff.

Edit:  In case you need the fixed diff calculation, it is [ hashrate x 30 ] and in xmr-stak you can set up fixed diff like so:  WalletAddress.Difficulty+WorkerName (Official Pool)

Pages:
Jump to: