|
Just wanted to let everyone know we worked late into the night and we are still figuring out what the best course of action for us to take is. Our main problem right now is a lack of hash. So if you have a miner we could use all the additional hash we can get right now while we get an update rolled out. More hash = more security & stability of the block chain.
|
|
|
|
Realized I never said thank you to AGX for handing the security breach a while back the way they did. I wad immediately informed and updated of the progress and reimbursed completely. Long story short I would recommend agx to anyone! +1 They are a great team to work with! Very professional! |
|
|
|
|
So after more research we have discovered a possible issue with the Bitcoin Core 0.9.1 code we implemented. This block delay issue does not appear to be related to DigiShield but how the 0.9.1 code was implemented.
The issue did not show up until several mining pools had updated. It appears a new multi-pool more recently updated to 2.9.1 and since they have most of the hash we are getting these delayed block times.
We are going to test out a few more things and compare code bases to make sure. The good news is if this is the issue we will not have to do a hard-fork to get the blockchain back on track. We will work on rolling out an update ASAP.
|
|
|
|
|
We also are seeing a timing pattern emerging. It started around the 28th of April it looks like. Over a month after DigiShield was implemented. Other coins with DigiShield like Dogecoin are not showing the same pattern. Either way we are on it.
|
|
|
|
Looks like it finally came. The delay is a bit concerning.
YC
Glad to hear it came through! We are definitely figuring out what the best option to fix it is right now. We are thinking an added filter to DigiShield would improve things along with multi-algo implementation. DigiByte's net hash has been dropping to 200-300 mh and then spiking up very high. DigiShield is working to stop the instamines by multi-pools but it is then lagging for a few minutes. Right now the best thing to do is get more hash on the network. Otherwise there is no option but to do a hard fork. Which we are planning on doing with the multi-algo implementation anyway. If you have a miner we could use the hash right now! |
|
|
|
Looks good, finally someone who at least puts some time down on a coin!
Now as long as you don't fuck up the release this coin will have a future!
Hah, found an old post of mine, nice to see how long this coin has been alive and doing well! Good luck with all future plans, devteam.  Thank you! |
|
|
|
Our goal is to reach over 5,000 followers on social media sites in the next two weeks! Share DigiByte with everyone you know and lets keep DigiByte growing! DigiByte to the moon! |
|
|
|
|
In your opinion what does #DigiByte need right now to become on of the top five coins in the crypto economy?
|
|
|
|
700 DGB Block finder bonus athttps://www.miningpool.coThis is a bonus promotion and does not come out of the block reward. Happy mining! Awesome promotion! We could use all the miners we can get right now! |
|
|
|
|
With Apple now allowing Crypto apps we will begin work on a DigiByte iPhone app. If someone would like to help us tackle this beast we could use the help!
|
|
|
|
|
DigiBye has now become a victim of its own success. Despite our integrity, our transparency and our contributions to the entire crypto currency community there are those who wish to maliciously attack us for their own person gain.
The current block times with multipools are a testimate to that. Had this happened to another coin or Bitcoin in the same proportions months could pass before the next block is found.
Crypto currency is an ever evolving market and field that is changing at an unprecedented pace. We will continue to adapt, improvise and overcome.
They key is to keep things in perspective. We see the light at the end of the tunnel. A brighter future will emerge for all of us. We can stand and work together or we can hang seperatly.
|
|
|
|
|
By the way.. Anyone who is reading this. Look up the "HR" account post history and you will quickly find which coin Dev it belongs to. It is sad they don't have better things to do with their time. Like actual development work. Now we are getting back to work.
|
|
|
|
everything can be fixed
 Especially when the starting point is cut and paste, misleading, diversionary replies like this:HR, thank you once again for pointing things out.
We have definitely been hit very, very hard by multi-pools. You can't expect that not to happen when the price doubles over night. We are checking into more things as well. The network is still there and working but blocks are a bit sluggish. Once again we are doing everything we can to make DigiByte the best it can be!
To extremely specific and concise technical issues like this:Another post based on hard data. The issue began after Feb. 22. and has PROGRESSIVELY gotten worse. Since you haven't had time to read all these posts, I thought I'd repost this since it is quite important. And you might want to go back and read the last few pages.  Check the data for the whole network. Not just one mining pool.
This is whole network data. current block: 132,795 DGB released days 142 * 1440(24*60) = 204480 I haven't checked the data myself but you have to factor in the multipools attacks from a while ago. They caused a lot of blocks to be mined very slowly and would've totally thrown the total coins minted out of balance. Also, remember that the minting of coins isn't actually balanced by the system, only the difficulty factor. You need to check the data yourself. If you look at the blockchain, you'll see that the issue began with the implementation of DigiShield, and has nothing to do with the multipool attacks. Block discovery was perfectly in line with DGB coding until Feb. 22, 2014. Take a look at the blockchain up to that date and divide by the number of days that DGB had been in existence. http://explorer.cryptopoolmining.com/chain/DigiByteThe issue began back then and has progressively gotten worse. I repeat: The issue began after Feb. 22. and has PROGRESSIVELY gotten worse.- How would the issue progressively get worse if the number of multipools in existence is same as back then but with less than 50% the hashrate they had back then?
- Why wouldn't you look at a DigiShield-ASIC incompatibility thesis since the only thing that has also grown progressively since that date is the use of ASIC?
- To sum things up, why wouldn't you get serious with really troubleshooting the issue?
- And why were you not aware of the issue before now? (Why wasn't anyone aware of the issue?)
- Isn't this your coin that you intimately know? Don't you take responsibility for it?
Do I need to open a support ticket at Craptsy? We've also been talking a bit about this on the "Whattomine - profitability website with basic api" thread (. . . if you're looking for troubleshooting and controlled testing ideas . . . my time is limited to being a contributor, not a Dev, and not even a full time hobbyist - anyone doing testing/troubleshooting, please post your hard data and initial assumptions). https://bitcointalk.org/index.php?topic=567730.msg7106535#msg7106535Would you like to help us improve DigiByte? Or are you going to continue your negative trolling campaign indefinetly? It is quite entertaining. Do you have any solutions to offer for any of the problems facing Cryptocurrency right now? Are you ready to help improve things for everyone or are you in this for yourself? If you are not happy with DigiByte or you have nothing to contribute in a positive manner or anything better to do with your time... Move on. Go attack another coin and spread fud there. The question is which coin you are coming from... Or which exchange?... with your newbie account? It is flattering to be drawing this attention... Lol |
|
|
|
So many people don't understand this, it blows my mind. Gpus can only go so far, even with x11/qrk and the like.
Think of GPUs as though they are people. That's your user base. The argument behind ASIC resistant is not to fight efficiency, rather it is to support a widely distributed user base. Everyone has a computer (well, not everyone, but you get the idea) and they are multitasking (that's why "everyone" has one). ASICs are specialized, and, by definition, your average man on the street will never have one (they can't do other practical things that the average man wants), and that means that you say goodbye to universal adoption, as in KYSGB. Efficiency is good, but not at the cost of your widely distributed user base, that is if you want to survive. Why do you think so much emphasis is being given to CPU mining by those energy efficient algos out there? Would it be that they're looking to be even more inclusive still? And the anonymity bit, I mean, get off it. That will never fly long term. What regulator is going to allow that? And why wouldn't you want your name stamped on your money anyway? It's mine, and I want it to say so - especially if it's robbed so I can get it back (but that's another issue, for another day - we've got to take baby steps, one at a time ). AHH AHH AHH in the 1900's Oil lamp users had a HUGE user base...20 yrs later, not many ppl used em. In 1900 flying from point A to point B was impossible.. now you cant look up w/o seeing an airplane almost. 15 Years ago, talking on a phone in your car was a pipe dream.. now we have them in our pockets. Do not discount technology ever. This IS business, not some get rich quick scheeme. How the hell are oil lamps and planes related to cryptocoin hashing? You compare apples and oranges, seriously.  Easily.. technological improvements. DGB has practically HANDED coins in ABUNDANCE to gpu miners for 5+ months, that is what I call 'SUPPORTING THE USER BASE', times change, technology improves, and the WISE miner will have ALL technologies to mine, the get rich quick , tin foil hat people will sit and wait and wait and hope and hope..meanwhile the DEV is out there, in the real world trying to make things happen for the benifit of all interested for tomorrow. In many cases scrypt asics are cheaper to buy than GPU's if you look @ it in a MH pr/dollar or even MH pr/kwh basis. Amen. We realize the relationships we are cementing right now and connections being made in this deal are going to benifit DigiByte long term and the entire Crypto world. But more importantly help advance dectralized banking in order to put it in the hands of the masses and change the world for the better. |
|
|
|
|
If Bitcoin had just experienced the same dramatic increase in hash rate all at once it could take a month to find the next block. DigiShield is working!
|
|
|
|
|
HR, thank you once again for pointing things out.
We have definitely been hit very, very hard by multi-pools. You can't expect that not to happen when the price doubles over night. We are checking into more things as well. The network is still there and working but blocks are a bit sluggish. Once again we are doing everything we can to make DigiByte the best it can be!
|
|
|
|
1000+ physical retail stores? Many people have said this before on this thread: with what? With a $583,662 market cap? (Based on theoretical coin supply and not the real coin supply after factoring in the block discovery issue.) http://coinmarketcap.com/ Who's going to fund those purchases and with what? And that's not to mention a totally erratic confirm that can last up to more than an hour. Does that sound like something read to go primetime? Give me a break. Got to get the coin right first. The market cap at this point doesn't matter. Why would it? Please explain. Confirm times right now does not matter, if there is a problem it's nothing that can't be fixed. It's not some kind of a fundamental problem you're making it out to be. We absolutely agree, everything can be fixed. Block times right now are the result of a massive influx of multi-pool hash that left to almost nothing. We were hit by almost every multi-pool all at once. This would kill off most other coins before DigiShield as it could take weeks to find the next block. |
|
|
|
The initial post someone made was taking data from a pool not the block chain. We are booting up a laptop to look at the blockchain.
The first time I mentioned it was here (check out the time stamp) - with no response.
I'm curious. With DBG stuck on block 131993 for over an hour and a half now, I started looking at the block chain and I noticed that it's been taking progressively longer to find blocks, with only an average of 10.66 blocks found per hour over the last 24 hours.
Only an average of 19.25 blocks found per hour over the last 5 days?
I've quickly searched a bit, but I haven't found anything on this. Forgive me if I've missed it.
Add: 131994 was just found - just under 2 hours between blocks!
The second time was here - again, no response. Reasonable expectations are an extremely important part of, if not perhaps even the most important aspect of, any endeavor, but equally so is the window of opportunity for its implementation. Fear of making a mistake can paralyze projects, leading to over cautiousness and missed opportunities, while unconscious brazenness can lead to almost certain short term disaster. It's a balancing act that normally plays out over a considerable amount of time, and even then it's tough to get right. Accelerate things by a factor of 10, and we might begin to just begin to get an idea as to how much more difficult that balancing act will be within the present context. I think I understand both sides of this highly charged issue. An algo change is not an overnight venture (unless it is stop-gap, cut and paste, and, as we know, that Digibyte is not), but the urgency felt by many is also well worth noting – the rate at which cryptocurrencies are evolving is increasing exponentially and I too share the worry that it will come too late. There's nothing like a great idea ahead of its time that gets beaten out by someone else who is quicker to bring it to market. Nothing like a good product that's too late! I mentioned earlier how an average of only 10.66 blocks were being found per hour over the last 24 hours, and 19.25 per hour over the last 5 days, and I'm not exactly sure what that is due to, but if it has anything to do with a dwindling of the widely distributed user base and an increase in ASIC mining, that would not be a good sign for time being on DGB's side (either way, there's obviously something wrong with that output for a 60 second coin, and very disconcerting considering that mining is the foundation that everything else rests on at this time . . . perhaps it's another completely unrelated issue to further complicate things . . .). In any event, along with 'getting it right', I think we can probably also all agree that time is of the essence and there's no time to waste! We've got a supersonic balancing act on our hands and all eyes are on the Dev team. If English bookmakers were to place bets on this, I'd bet that the bet would be: “can they do it in time?” (Just to add a bit of "big game" pressure to the mix while we're at it. ) I want to wish the Dev team the best of luck with this very stressful 24/7 project you have on your hands, and to also thank you for keeping us up-to-date and in-the-loop. Rest assured that you can count on my/our help with testing and whatever else I/we might be able to do. Here's to getting a great job done in time! As of 2014-06-02 21:03:42 Last 24 hours: only 410 blocks found of a supposed 1440 theoretical programed 60 second blocks.
Previous 24 hours: only 280 blocks found
Previous 24 hours: only 166 blocks foundWhat would be the explanation for this? In order to be competitive with ASIS resistant coins (and the few still competitive scrypt coins), on a relative profitability basis, actually mining the coin, DGB would have to be valued at around 120 satoshi, and that, of course, is based on a 60 second block find basic assumption. With blocks being found at only around 1/4 of the rate of what should be the case . . . well, I'll let you all do the math. Blockchain Explorer: http://explorer.cryptopoolmining.com/chain/DigiByteSomething is very wrong with this picture. This information is coming from 1 mining pool. Not the entire DigiByte network. HR. Thank you for posting this. Did not catch most of these posts. We have been really really busy with 10 different things.. Both of us are analyzing the issue right now. It appears DigiBytes own popularity is now causing some new issues with multipools. |
|
|
|
|
It appears we had a massive momentary spike in hash rate. DigiShield works but with such a large increase it will take time to average out again. Other coins this could take weeks. We are still looking more into it.
|
|
|
|
Brick & mortar refers to a physical retail store not a specific company or chain. We are in LA working on a deal to get DigiByte accepted in 1000+ physical retail stores.
Holy Moly! This is a game changer. 1000+ physical retail stores? Many people have said this before on this thread: with what? With a $583,662 market cap? (Based on theoretical coin supply and not the real coin supply after factoring in the block discovery issue.) http://coinmarketcap.com/ Who's going to fund those purchases and with what? And that's not to mention a totally erratic confirm that can last up to more than an hour. Does that sound like something read to go primetime? Give me a break. Got to get the coin right first. What do you think drives adoption? There is not a block discovery issue. You are only pulling data from one mining pool. It blows my mind that you continue to insist upon saying the same thing in the face of the facts, and those facts come from your own blockchain posted on your own web. http://explorer.cryptopoolmining.com/chain/DigiByte The numbers are the numbers, and the math is the math, but to insist on the same lame response is nothing short of idiotic. Block discovery is WAY OFF from what it should be, and that's based on very elementary comparative calculations using the DGB blockchain data, time, and coin specs. I'm really starting to wonder about you. Think about it this way: I’ve got a relatively new apartment building whose construction was faulty and now has a leaky roof and cracking walls and I’m telling you that it can easily be converted into a luxury hotel. Are you selling that? That's what it's increasingly looking like. In the crypto biz, if you don’t have a widely distributed user base, you ain’t got diddly squat, and anything else you want to talk about is pie in the sky (i.e. a sham). But let’s say, for argument’s sake, that there is someone who either dearly needs a huge tax write-off or has his/her head up you know what, and you get the money from those supposed investors. What do think we should really expect from people who don’t know how to make their coin work correctly, much less keep their website up-to-date? When Daddy Warbucks runs out of pump money, look out below (IMVHO). So far today, there has been an approximate $124,000 of USD equivalent volume on MintPal and $40,000 on Cryptsy and it's showing all the signs of a parabolic pattern with a volume spike that’s more often than not associated with a blow off top. The pattern is currently in a “second/last chance to sell phase”. The pattern targets well below 30, and quickly. However, that’s not to say that is a guaranteed outcome. There’s still a chance, however small it might be, that DGB could just as quickly run to 400 turning that volume spike into one of the most powerful breakout patterns imaginable, eventually targeting 2000 satoshi within a month. That's what Daddy Warbucks is hoping for, but he's going to need a lot of suckers (again IMVHO). That’s the technical side of things. Everyone must make their own decision, regarding both the technicals AND the fundamentals. BTW, the only thing I will commend you on is leaving my posts intact and allowing plurality of opinion so people can inform themselves as best they can and then make the best decision they can on their own and for themselves. From day one we have not deleted a single post nor will we. The initial post someone made was taking data from a pool not the block chain. We are booting up a laptop to look at the blockchain. Not sure why you are trolling so hard. We are doing are best to make something happen for DigiByte here. And we are well on are way to making that happen right now. Will reply shortly with more blockchain info. |
|
|
|
|
Show Posts
