Because Elastic mining really doesn't behave like the more traditional coins, maybe it should treat mining more like how a pool looks at it.  In this case there would be a fixed number of XEL per pow block and instead of all or nothing, you would get a percent based on how much hash you contribute.  So the target would only effectively be used to throttle the amount of POW submissions, and it could be set differently for different miners on the same block which just alters their percent of the reward.

I'd have to think more if there are any downsides but the more I been looking into mining xel, the network really looks like one big pool to me.  The pow mining is just shares to determine your percent of the pow reward for that algo, and the bounty is equivalent to the pool finding a block, and even that should probably be distributed evenly across miners (not 100% sure if that would be correct).

Anyway, this idea may be way off base, but I think with xel we need to think outside the box.

This would leave the risk that a big miner could drive up the difficulty, then go offline leaving the remaining miners with such a difficult target that they may not get a POW reward for hours or days.

Could you please explain a little more how it is determined which Work Algo the miner gets (i.e. if there are currently 5 projects out there with different algos, how does the network decide which one I get).  If it's simply distributed evenly, then there may not be any issue here regarding the re-targeting; however, if there is a way for the miner to pick which algo they work on, then I would think they will figure out how to always go after the one with the best profitability based on difficulty / reward leaving some algos without any miners interested in working on them.

Been a while since I've used a NXT wallet, but i'm having an issue.  I keep getting the error "Could not validate unsigned bytes returned by the server".   This happens if I try to update my account, send xel, or submit work.  Screenshot below:

http://imgur.com/a/q37Hx

My account is XEL-8DES-WHKN-M6SZ-8JRP5.  I am using EK's AWS node to connect my browser.

Also, I am running a node which I can see in the Block Explorer / Peers page, but I don't see on EK's AWS peers page.  I've deleted the db and restarted but it still doesn't show up on EK's node.

Thx guys for the test xel.  Got the new version compiled and running w/o issues.

Can someone please send a few test xel to XEL-8DES-WHKN-M6SZ-8JRP5

Hi EK, I've spent some time reviewing the EPL logic and I think I am understanding it.  However, just to clarify, to me it looks like everything is a 32 bit operation.  For example I don't see any carry-save logic in the AddNode module for larger values and the shifters all look to be 32 bit as well.  Is there a plan to add functionality to allow larger operations, or did I just mis-interpret how your code works.

Also, as someone asked before about looping, I looked at the Repeat module and to me it looks like it would repeat a single operation, but not a group of operations, is that correct?

I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.

Ok, I've got it now.  I guess I was thinking the retargetting was happening based on the transactions being submitted due to the possibility of the initial target getting set too low and the miners flooding the network with low-target work.  I guess the trick will be figuring out what the initial target should be for the ad-hoc pow algos.  Maybe a conservative way to do this would be to start the target at the Bounty level and cut it by half each block until work is submitted or until it's at the minimum target.

Thanks EK, your explanation makes perfect sense.  I guess my question is more around the target.  In traditional mining, a pool would set this target.  So I'm still a little unclear within elastic what is setting the target (or determining that work is being submitted too quickly) as we are decentralized.  I'll dig into the miner code a bit more to understand (little rusty on java).

Also, if you have any suggestions on a small example epl you'd like to see, I'd like to try to put one together to better understand the epl / miner behavior.

Hi EK, question about ElasticPL.  I understand that the verify command identifies what work meets the bounty critieria, but what qualifies that the other pow work actually took place.  For example, in your good.epl, obviously only hashes beginning with 32 bits of zero meet the bounty, but what shows that the pow submissions were actual hashes for that block header and that one miner has higher hashrate than another?  Or in the elastic world are all miners equal regardless of how much work they do?

I'd like to look into epl and the miner a bit more, so I'm trying to better understand how this works.

Sad to see Waves drop like this, but the signs were there and fortunately I was able to get out with good profit thanks to Yobit.  Like others, I may buy back in once the massive selloff ends.  I can't see any reason to hold and watch value drop this much.

Same here, communication is the key to a crypto-currency.  Regardless of what the price is doing, getting these updates and seeing the progress allows investors to decide based on facts...not hype.  I really like DCR, keep up the great work devs.

I thought that's the point of the buy wall....unfortunately, this ICO is way oversold and a lot of people wanted a way out and the buy wall buy from the devs gave them a simple path to do this.  The vision of this coin is still viable, but I think it will be a while for the price to settle down.

I'm not sure why people thing buying and selling on Yobit is any worse than the Waves trading thread.  They may do some things you don't agree with (i.e. IOUs...and I don't agree with IOUs either), but not sure why you say it's a scam.  Seems safer than person to person trades on BCT.

They send you a Yobit code after you send your waves.  Once you enter the Yobit code, your Waves appear in your wallet.

I picked up some Waves cheap from the trading thread and sent them there...no issues.

I understand Yobit can be sketchy, but the comments on BCT are so hypocritical.  There are lots of people calling out ETH because their dev is basically centralizing the coin by making is HF decision, while here at Waves everyone is cheering on the devs decision to pick and choose the exchanges for the coin.  This is a decentralized currency...let the market decide.

WTB 4,500 WAVES @ 0.00045

I use this:

dcrctl -u [user] -P [password] --wallet setticketfee <fee amount>

The fee you use is up to you

Make sure you didn't include any extra spaces or carriage returns when paste in your seed.

Thanks Twiggy Smile, I've seen you reference this "Techpaper" a few times.  Is there an ETA for when we can expect this paper?

Does anyone know if we will be able to begin staking our coins beginning tomorrow, or is that scheduled for a later date?