Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1419. (Read 3058812 times)

Thank you for the feedback, we have found a couple small issues that we are fixing before doing a full release.

both of these are real possibilities and are my fears as well if no new algorithm is applied...in fact the 2 people mining DGB with ASICS will mine the life out of DGB then dump coins on an exchange....end result is that price keeps plummeting yet difficulty has risen, DGB would then be toast since there is no incentive to mine anymore....this is all of course hypothetical, DGB will be modified well before this will happen but it's unfortunately the reality that all scrypt coins are facing

I'm testing currently this release , exactly x64 build :

- I can receive and sent DGB to others accounts (My main testing receiver DGB account was AGX.io and my secondary is a Android Wallet)
- Wallet backup & restore working perfectly
- Synchronize with DGB network without issue, I feel this version sync more fast with DGB network compared with v2.0.
- Ui Improvements are welcome 

Only one minor issue in UI, but not affect wallet functionality : http://s27.postimg.org/ewdnbld03/ui_bug.png -- the html code in the message "

Thanks for this RC Dev Team... 

Greetings from Venezuela

P2pool using DigiByte v2.0. Now with Cryptsy price displayed
Address: dgb.p2phash.com

P2Pool benefits:
* No registration required
* Distributed hashrate
* Immediate payouts after a block is found
* Higher payouts with transaction fees paid to miners
* No account hack possible

Fee: only 0.5%
Start mining within seconds! Just point your miner to p2phash.com:9022 and use the DigiByte address from your wallet for username, the password doesn't matter.

You can now follow us on twitter: https://twitter.com/P2PHash

Does anyone have any feed back on mining Maxcoin?

We are taking a very hard look at SHA-3 Keccak.

SHA stands for "Secure Hashing Algorithm" and is set by the National Institute of Standards and Technology (NIST).

http://en.wikipedia.org/wiki/Secure_Hash_Algorithm

SHA-0 Has been exploited.
SHA-1 Has been exploited.
SHA-2 What Bitcoin uses & most cryptos.
SHA-3 Next generation super secure hash. Maxcoin implemented SHA-3 Keccak

We have been researching much more into Keccak.
http://keccak.noekeon.org/
http://en.wikipedia.org/wiki/SHA-3

What really caught our attention:



Rumor has it a GPU miner for Keccak has already been developed. We are thinking we can modify Keccak for GPUs.

Huh?

We hate most is liar
The community should not deceive
Thank you for your reminding me

I'm not saying we should switch as I'm still largely undecided, its a difficult problem. If we were to change I'm personally becoming a fan of the approach that myriadcoin has taken with there algo design (at least on paper). To me it seems like a balanced approach and could be tweaked for digibyte and accommodate other algos if we so desired.  


It would require some changes to infrastructure where we would need pools for each algorithm and depending on which algo you mined you would use a different mining program.

It needs more research but its an interesting idea and worth exploring

Which algorithm should DigiByte switch to? Vote here: https://bitcointalksearch.org/topic/poll-which-algorithim-should-digibyte-switch-to-545759

Impossible to answer imo, this depends on how Digibyte will grow or decline. If all your efforts, dev's and community's efforts, will be rewarded by a huge amount of trade and nice value per coin in few months, lot of people will probably mine DGB as a standard, and it's not impossible to see an average net hashrate of 30 Ghs+ like the DOGE community.

Regarding the algorythm, I have a question because i have no knowledge in programming : is there any way to have a fast and secure algo which will give a maximum fixed amount of shares per minute/kilohash per minute AND per device?

Imagine an algo which will fix a maximum hashing power per devices (GPU Card/ASICS/Grid Seed/CPU etc...) at, for example, 200 Khs. Limited at something like 8 devices per IP/MAC adress, all people will have a proportionnal amount of coins, and will save a lot of electricity because  running a Graphic card at lower intensity will bring the electricity bill lower.

I'm just suggesting a beginning of reflexion, this is maybe not possible. Please gimme some light in this darkness

People will always mine, if, they can afford to. With BTC value going down, and all the alts ( at the moment ), many many people whom bought into mining hard core ( possibly foolishly & too heavily ), are either turning rigs off due to operating costs, or the inability to ROI, many are just selling.  As long as people can afford to, they will, new algos, that make better use of energy & operating costs are very attractive. At the moment, I hash scrypt , N & X11, with scrypt being a very low percentage. I can buy coin cheaper than it is to mine it in many cases ( with reg scrypt )

In the end we definitely do not want hashing power to become centralized & we like the idea that anyone should be able to mine DigiByte with very little associated costs.

The question is in the future how many people are actually going to be mining when we achieve main stream adoption? Maybe 5% of users a year from now? What are your thoughts?

Apparently he does. ^^

I fear that no one with asics are mining DGB...that would mean its not worth anyone's hashes...

I fear it's quite possible that in few months months there are 2 people mining DGB, and both have 300mh/s asics.

I agree 100% that a rush into a new algo would be bad. However, if a new algo is being considered, along with that should be a 'back up' plan just in case somthing bad happens..I would even go as far as to suggest a two algo back up. Mabey N-Scrypt and ____.   It may sound like over kill, however in my short time in crypto, I have seen great ideas crumble, due to the lack of 'back up plans' Im sure the team is considering all this, and I am more than likely stating the obvious, however sometimes the obvious things get overlooked, as we tend to over complicate as we try and essentially predict and do whats best for the future. Some of the points I would like to see is that any GPU miner can mine the coin, nVida & AMD, CPU miners aswell, & if a Algo(s) is chosen, & if the developement team(s) of the various miners do not support a new algo, that they have set in stone plans to do so.

-Happy Mining

Much agreed. You bring up some very valid points. And we are speculating that the mining software will be improved as time goes on for X11.

Since we are not the 1st coin to switch algos in a hard fork or the 1st to implement X11 we see no reason to rush into it. We still have 2-3 months before this could become an issue.

Also, there still are several arguments as to how ASICS could actually help DigiByte grow in the long run. We are not saying we agree with this, but there are some valid points to consider. Such as. if someone spends $10,000 on a Scrypt ASIC the only thing it is good for is mining Scrypt coins. So people will be mining Scrypt based coins well into the future with them. Also, the more invested someone becomes in a coin after spending that much money, the more they will want it to succeed.

A majority, but not all GPU miners tend to be a migratory crowd moving from the most profitable coin to the next coin with the newest features with the hopes of it becoming the next most profitable coin to mine. This is not a bad thing, but it is not good for the long term survival of any particular coin with an algo dominated by GPU miners.

Also, a lot of GPU miners tend to be very short term oriented and less likely to mine coins because they believe in them and want to support them long term.

Ideally, if we do switch algos we would like to make it something Unique to DigiByte that will help make us stand out. Much like DigiShield. This takes time and we definitely want to test it out.

We are researching many different algos at the moment including ones never before put into a crypto. This is a very broad and technically challenging are of study so it will take some time.

Still, if anyone has any further suggestions we are very open to hearing them. Thanks again for the feedback!