Does anyone have a calculator that does the following?
Inputs in current DGB, BTC and USD prices. If you think put in future pricing, you can generate an ROI. It would allow you to change pricing of BTC and DGB respectively to see what the fiat investment is worth. Here is an example.
Current:
BTC: $400
DGB: 20
Investment: $1000
Future:
BTC: $700
DGB: 50
Investment: ?
ROI: ?
Would be very helpful. Any ideas?
YC
Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1190. (Read 3058816 times)
October 19, 2014, 10:08:46 AM
October 19, 2014, 10:08:19 AM
I think marketing and adoption should take in all stages of DGB development.
It does not matter if we have anything fully completed. Ad is Ad
It does not matter if we have anything fully completed. Ad is Ad
October 19, 2014, 10:02:54 AM
Love to see the dedication Jared! Lot of good things seem to be happening, which is nice. With the upgrades, I anticipate we will see less issues in trading and exchanges. We should then continue to focus on marketing and adoption!
YC
We want to get iOS, Android (completed), Electrum (test wallet running), Coinpunk and Tipbots all operational before we consider a major upgrade like this. We are working on all these projects simultaneously.
We also are working on DigiPay as a payment service & trading platform. We have a lot of development going on right now! Good things are around the corner!
Note: Chinese translation is compiled into v3.0.2 as well. Binaries coming tomorrow
YC
Finally got back my money from mintpal. I guess they are honest fellows afterall 
I stumbled on a bug it seems but now all's fine.
Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
Thanks for the feedback! This is a great idea and we will look into it for sure. This is also a lot to take on and code in. We want to get things streamlined & working very well before we consider doing this thought. I stumbled on a bug it seems but now all's fine.Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
We want to get iOS, Android (completed), Electrum (test wallet running), Coinpunk and Tipbots all operational before we consider a major upgrade like this. We are working on all these projects simultaneously.
We also are working on DigiPay as a payment service & trading platform. We have a lot of development going on right now! Good things are around the corner!
Note: Chinese translation is compiled into v3.0.2 as well. Binaries coming tomorrow
October 19, 2014, 08:59:26 AM
Greetings Everyone,
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of things going on right now in the background so stay tuned for more news!
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of things going on right now in the background so stay tuned for more news!
Great work team!
As always i´m looking forward to the update.
When the android wallet is coming online. maybe we should first test it with the community members.
After that we could promote the wallet with free digibyte when they first installed?
How is the job hiring going,any new members on board?
Keep the ball rolling guys!
October 19, 2014, 06:14:01 AM
Finally got back my money from mintpal. I guess they are honest fellows afterall I stumbled on a bug it seems but now all's fine.
Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
Thanks for the feedback! This is a great idea and we will look into it for sure. This is also a lot to take on and code in. We want to get things streamlined & working very well before we consider doing this thought. I stumbled on a bug it seems but now all's fine.Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
We want to get iOS, Android (completed), Electrum (test wallet running), Coinpunk and Tipbots all operational before we consider a major upgrade like this. We are working on all these projects simultaneously.
We also are working on DigiPay as a payment service & trading platform. We have a lot of development going on right now! Good things are around the corner!
Note: Chinese translation is compiled into v3.0.2 as well. Binaries coming tomorrow
October 19, 2014, 05:57:17 AM
anyone running a pool with vardiff could give me targetdiff, minvardiff and maxvardiff for each algos please
bump October 19, 2014, 04:28:06 AM
Finally got back my money from mintpal. I guess they are honest fellows afterall I stumbled on a bug it seems but now all's fine.
Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
I stumbled on a bug it seems but now all's fine.Looking forward to news! but I'd like to throw the rock once again: multi-algo + aux-pow= safest pow coin ever, multialgo alone makes a 51% attack just a bit trickier. I see some people ideologically against merge mining, but considering the total value of the mined dgb a day is little over 1 BTC (or am I wrong?) so the cost of a 51% attack trough rented miners should be in the order of the few hundred dollars a day, that's chips. Even when dgb price rises you still have to consider that its hashrate is distributed trough 5 algorithms, so the miners of each algo get 1/5th of the total, making the hashrate go down the drain
If you mergemine with the main coins and orphan the blocks with lowest -estimated- "actual" difficulty (dunno if that's how it works already) then a 51% attack becomes as hard as 51% attacking all the coins alltoghether, making it cost in the order of milion dollars a day.
Lastly, there are bound to be many coins around for each popular algorithm, and as we've seen even BTC does not totally monopolize sha, it's normal that we'll have a few big players in the mining industry, this means that if even the largest coins don't work together to build up hashrate they'll all be under the 51% attack threat from a "rogue" miner. Even if dgb becomes the N1 coin, it'll still have hashrate issues (especially since it's a multi algorythm coin) unless it's merge mined.
Forking is usually bad, but since dgb is still in a somewhat letargic period it's better to do all the forkings now than later.
October 19, 2014, 03:32:58 AM
Greetings Everyone,
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of thins going on right now in the background so stay tuned for more news!
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of thins going on right now in the background so stay tuned for more news!
Thanks, our wallets are updated. Hope everything goes well now with the previous issues
October 19, 2014, 02:42:58 AM
Greetings Everyone,
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of things going on right now in the background so stay tuned for more news!
First off, a note on the rate of DigiByte production. We have read most of the comments on here regarding the price of DigiByte and the rate of DigiByte production and we understand some of your concers. As of now we have no plans to change the rate of production as we want to leave the core protocol variables alone. We feel we are right where we need to be. We have a very powerful marketing campaigned outlined that will bring more users into DGB. Once this happens we will need all the coins we can get in circulation.
Secondly, we have now pushed all the fixes for the bugs everyone has been experiencing to the master branch on github. If you are a mining pool operator please help us test v3.0.2 by building from source. If all goes well we will release v3.0.2 binaries to the public tomorrow (we have compiled and tested on all os's with no problems.) We have also updated the seed nodes to v3.0.2 as well.
https://github.com/digibyte/DigiByteProject
We have compiled & successfully tested the upgraded DigiByte Android wallet. We plan to put this back on the play store on Wednesday.
We will be releasing the official DigiByte Wiki to the public this coming Friday.
We have a lot of things going on right now in the background so stay tuned for more news!
October 18, 2014, 04:31:16 PM
anyone running a pool with vardiff could give me targetdiff, minvardiff and maxvardiff for each algos please
October 17, 2014, 05:55:06 PM
Fantastic work! Let's see what happens!
YC
I will fire it up! Good Work. Gonna publish @reddit as well! THX
Here we go... Crossposting getting started!
http://www.reddit.com/r/Digibyte/comments/2jj9dn/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_voting_btercom_please_vote_and_get/
YC
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
I will fire it up! Good Work. Gonna publish @reddit as well! THX
Here we go... Crossposting getting started!
http://www.reddit.com/r/Digibyte/comments/2jj9dn/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_voting_btercom_please_vote_and_get/
https://twitter.com/Alttrade/status/523222376813981699
Retweet!
October 17, 2014, 01:59:43 PM
Fantastic work! Let's see what happens!
YC
I will fire it up! Good Work. Gonna publish @reddit as well! THX
Here we go... Crossposting getting started!
http://www.reddit.com/r/Digibyte/comments/2jj9dn/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_voting_btercom_please_vote_and_get/
YC
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
I will fire it up! Good Work. Gonna publish @reddit as well! THX
Here we go... Crossposting getting started!
http://www.reddit.com/r/Digibyte/comments/2jj9dn/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_voting_btercom_please_vote_and_get/
October 17, 2014, 01:28:45 PM
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
I will fire it up! Good Work. Gonna publish @reddit as well! THX
Here we go... Crossposting getting started!
http://www.reddit.com/r/Digibyte/comments/2jj9dn/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_voting_btercom_please_vote_and_get/
http://www.reddit.com/r/dogecoin/comments/2jjbo7/digibyte_%E6%9E%81%E7%89%B9%E5%B8%81_contribution_get_tipped/
October 17, 2014, 12:41:16 PM
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
Good news, always good to be added to BTER.
Wow my (OUR) repetitive messages worked at least to get it added
I think working with HongKong closely will take DGB to the BTER and some other Chinese market.
Otherwise, within vote we are limited and not easy to get to the top, I think.
October 17, 2014, 12:30:32 PM
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
Good news, always good to be added to BTER.
October 17, 2014, 12:20:29 PM
Just got an email that DGB has been added to the voting list at BTER. Not sure how we get to the top, but it would be nice to get added. Jared, can we tell BTER about our Asian presence?
https://bter.com/voting
YC
https://bter.com/voting
YC
October 17, 2014, 07:26:04 AM
October 17, 2014, 05:13:16 AM
My withdrawal went through perfectly. It may be confusing because of the big text box below, but you don't need to put anything in there.
Took less than 3 hours for mine to go through
As of now the withdrawas still is not processed. I put the dgb address where it says withdrawal address but it disappeared as I ressed save canges so I added a not ein the big box below asking to send the dgb to my address, no answer as of yet...
October 17, 2014, 04:14:45 AM
DigiByte, Jared... It is good to hear from you. It has been some time.
Do we have any updates on the fate of DGB ? Any solid list of plans etc ? Thanks.
Do we have any updates on the fate of DGB ? Any solid list of plans etc ? Thanks.
October 17, 2014, 03:06:34 AM
My withdrawal went through perfectly. It may be confusing because of the big text box below, but you don't need to put anything in there.
Took less than 3 hours for mine to go through
Jump to: