roslinpl
Legendary
 Offline
Activity: 2212
Merit: 1199
|
 |
March 15, 2014, 09:55:27 PM |
|
Another pool! And again I wish god luck and many miners! |
|
|
|
|
|
|
|
|
|
Make sure you back up your wallet regularly! Unlike a bank account, nobody can help you if you lose access to your BTC.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
mintzone
|
|
March 15, 2014, 11:06:43 PM |
|
Another pool! And again I wish god luck and many miners! Hasn't this pool been around for a while?  But, another pool can't be a bad thing! |
DGB is my and the future's coin of choice! Don't cry if you don't invest  |
|
|
agx.io
Member
Offline
Activity: 84
Merit: 10
|
|
March 16, 2014, 01:39:51 AM |
|
Quick summary to AGX's exciting Beta Launch Day: AGX has 11 trading pairs available including DGB/BTC, DOGE/BTC, RIC/BTC, BC/BTC, VTC/BTC, USDE/BTC, NOBL/BTC, MAX/BTC, LTC/BTC, LEAF/BTC, and AUR/BTC. We'll be adding additional pairs quickly; follow @AustinGlobalX on Twitter for updates.
Trading is FREE during Beta. Come check out AGX and let us know what you think!
- The Austin Global Team
Find us at:
agx.io
bitcointalk.org/index.php?topic=507474
bitcointalk handles: "agx.io," "AustinGlobal"
twitter.com/AustinGlobalX
austinglobal.tumblr.com
|
|
|
|
|
torchwood-uk
Member
Offline
Activity: 84
Merit: 10
|
|
March 16, 2014, 01:40:09 AM
Last edit: March 17, 2014, 05:28:45 PM by torchwood-uk |
|
 Pool is around 27MH/s and finding blocks regularlyhttp://dgb.mining-man.com
DDoS resistant dedicated server
Payout cron run every minute
Round earnings credited after only 15 confirms
Dashboard stats updated every minute |
|
|
|
|
|
tomvalois
|
|
March 16, 2014, 02:06:49 AM |
|
I am trying to compile DigiByte for 32-bit Lubuntu. I followed the instructions at: https://github.com/digibyte/DigiByteProjectEverything went well until I tried to compile the qt wallet. At this point, here is what happens. When I type: ~/DigiByteProject$ qmake "USE_UPNP=-" digibyte-qt.pro I get: Project MESSAGE: Building with QRCode support Project MESSAGE: Building without UPNP support Project MESSAGE: Building with QRCode support Project MESSAGE: Building with UPNP support Removed plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. WARNING: TARGET is empty and then when I type: make I get: make: Nothing to be done for `first'. Any ideas? |
|
|
|
|
|
mintzone
|
|
March 16, 2014, 05:12:15 AM |
|
Quick summary to AGX's exciting Beta Launch Day: AGX has 11 trading pairs available including DGB/BTC, DOGE/BTC, RIC/BTC, BC/BTC, VTC/BTC, USDE/BTC, NOBL/BTC, MAX/BTC, LTC/BTC, LEAF/BTC, and AUR/BTC. We'll be adding additional pairs quickly; follow @AustinGlobalX on Twitter for updates.
Trading is FREE during Beta. Come check out AGX and let us know what you think!
- The Austin Global Team
Find us at:
agx.io
bitcointalk.org/index.php?topic=507474
bitcointalk handles: "agx.io," "AustinGlobal"
twitter.com/AustinGlobalX
austinglobal.tumblr.com
Your exchange looks great and is functional  Keep up the good work, guys! |
DGB is my and the future's coin of choice! Don't cry if you don't invest |
|
|
grynca
Member
Offline
Activity: 84
Merit: 10
|
|
March 16, 2014, 07:19:02 AM |
|
www.DigiForce.cc Call to Arms: - We need more DigiMen ! - Now fighting the coinwars with DigiShield !! - PPLNS, 0% fee - 24/7 support at grynca@digiforce.cc - DigiByte only dedicated pool - Hosted in cloud with dynamic load scaling - both US and EU stratum servers Join The Force !
|
|
|
|
|
|
|
BlazingHashes
Member
Offline
Activity: 106
Merit: 10
|
|
March 16, 2014, 10:23:23 AM |
|
|
|
|
|
|
torchwood-uk
Member
Offline
Activity: 84
Merit: 10
|
|
March 16, 2014, 10:48:31 AM |
|
http://dgb.mining-man.com
DDoS resistant dedicated server
Payout cron run every minute
Round earnings credited after only 15 confirms
Dashboard stats updated every minuteWe have setup a US stratum for Digibyte at stratum+tcp://us.stratum.mining-man.com with port 3332 the other stratum is in the EU. If you are on the EU Stratum then please set the US Stratum as your failover and if your are going onto the US stratum then please set the EU Stratum as your failover.
|
|
|
|
|
|
Cyriaque5962
|
|
March 16, 2014, 01:25:32 PM |
|
I did the same mistake exactly on cryptsy, sent 500 000 dgb from my dgb wallet to dogecoin wallet on cryptsy three days ago. For moment, no answer to my support on cryptsy. A friend found the transaction in the blockchain. I sent all informations to cryptsy , I'm waiting for an answer, hope they are not lost too. |
|
|
|
|
elrugrim
|
|
March 16, 2014, 03:27:33 PM |
|
Good luck on getting the coins back. Thats rough.
|
|
|
|
|
JpHysteriak
Newbie
Offline
Activity: 5
Merit: 0
|
|
March 16, 2014, 03:37:59 PM |
|
I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !
|
|
|
|
|
|
mintzone
|
|
March 16, 2014, 04:10:23 PM |
|
I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !
That really works? O.o Wow... I wonder how those .dat files work anyways |
DGB is my and the future's coin of choice! Don't cry if you don't invest |
|
|
xploited
Sr. Member
Offline
Activity: 304
Merit: 252
CLAM Dev
|
|
March 16, 2014, 05:12:35 PM |
|
I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !
That really works? O.o Wow... I wonder how those .dat files work anyways Interestingly enough because of how private keys are generated and how addresses are validated in the clients in any coins based on bitcoin if the address prefix is the same, 'D' in our case, both addresses and private keys will be valid on both coins blockchain. Thats not to say your coins come with you from one blockchain to the other, just that the private key generated for an address on one blockchain will also be valid on the other if the address prefix match. Now, you may ask yourself (as I did when I first discovered this), well, isn't this a security concern. Can't somebody on doge coin generate a private key that could access your address? This however is incredible improbable (or unfeasible depending on which term you like better) and no more likely then someone on the DigiByte blockchain generating an address that is already in use on the DigiByte blockchain. I could get into the absurdity of the numbers but needless to say the amount of possible addresses is beyond large. Imagine the number of atoms in all the matter on earth... and that would only be a small portion of the possible address space. People in the past have occasionaly sent their DigiBytes to a Doge address on an exchange. Because the private key to the address they were sending already existed on the Doge blockchain and was owned by the exchange, the exchange was able to import the private key from one blockchain to another and redeem the otherwise lost coins. This of course is totally up to the desecration of the exchange. We've looked into possible solutions but have only come up with bandaids that aren't worth implementing and don't actually fix the underlying cause. My only suggestion currently, as poor as a suggestion as it might be, is to remain diligent about verifying you are sending to a DigiByte address. Almost every instance of this has been related to DigiBytes being sent to an exchange. Double check your on the DigiByte deposit page when you generated a deposit address and that your not mixing up Doge and DGB or anyother coin that might start with D It also doesn't hurt to send a very small amount and verify it was deposited to your account correctly before you send a larger amount. Its much better to risk losing 1 DigiByte to the void then 50k. |
|
|
|
roslinpl
Legendary
Offline
Activity: 2212
Merit: 1199
|
|
March 16, 2014, 06:17:38 PM |
|
Whats up DigiCommunity!!! How's going? Any great news for DGB? |
|
|
|
|
|
btcash
|
|
March 16, 2014, 06:36:00 PM |
|
Whats up DigiCommunity!!! How's going? Any great news for DGB? Price is going up again. From 0.00000050 to 0.00000084 within 1 day. Digishield maybe becomes the new KWG. |
|
|
|
|
|
mintzone
|
|
March 16, 2014, 07:01:05 PM |
|
I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !
That really works? O.o Wow... I wonder how those .dat files work anyways Interestingly enough because of how private keys are generated and how addresses are validated in the clients in any coins based on bitcoin if the address prefix is the same, 'D' in our case, both addresses and private keys will be valid on both coins blockchain. Thats not to say your coins come with you from one blockchain to the other, just that the private key generated for an address on one blockchain will also be valid on the other if the address prefix match. Now, you may ask yourself (as I did when I first discovered this), well, isn't this a security concern. Can't somebody on doge coin generate a private key that could access your address? This however is incredible improbable (or unfeasible depending on which term you like better) and no more likely then someone on the DigiByte blockchain generating an address that is already in use on the DigiByte blockchain. I could get into the absurdity of the numbers but needless to say the amount of possible addresses is beyond large. Imagine the number of atoms in all the matter on earth... and that would only be a small portion of the possible address space. People in the past have occasionaly sent their DigiBytes to a Doge address on an exchange. Because the private key to the address they were sending already existed on the Doge blockchain and was owned by the exchange, the exchange was able to import the private key from one blockchain to another and redeem the otherwise lost coins. This of course is totally up to the desecration of the exchange. We've looked into possible solutions but have only come up with bandaids that aren't worth implementing and don't actually fix the underlying cause. My only suggestion currently, as poor as a suggestion as it might be, is to remain diligent about verifying you are sending to a DigiByte address. Almost every instance of this has been related to DigiBytes being sent to an exchange. Double check your on the DigiByte deposit page when you generated a deposit address and that your not mixing up Doge and DGB or anyother coin that might start with D It also doesn't hurt to send a very small amount and verify it was deposited to your account correctly before you send a larger amount. Its much better to risk losing 1 DigiByte to the void then 50k. Interesting response. Thanks xploited! |
DGB is my and the future's coin of choice! Don't cry if you don't invest |
|
|
DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
March 16, 2014, 07:08:43 PM |
|
I did it ! Just export your dogecoin privkey and import it on the dgb wallet. Works fine !
That really works? O.o Wow... I wonder how those .dat files work anyways Interestingly enough because of how private keys are generated and how addresses are validated in the clients in any coins based on bitcoin if the address prefix is the same, 'D' in our case, both addresses and private keys will be valid on both coins blockchain. Thats not to say your coins come with you from one blockchain to the other, just that the private key generated for an address on one blockchain will also be valid on the other if the address prefix match. Now, you may ask yourself (as I did when I first discovered this), well, isn't this a security concern. Can't somebody on doge coin generate a private key that could access your address? This however is incredible improbable (or unfeasible depending on which term you like better) and no more likely then someone on the DigiByte blockchain generating an address that is already in use on the DigiByte blockchain. I could get into the absurdity of the numbers but needless to say the amount of possible addresses is beyond large. Imagine the number of atoms in all the matter on earth... and that would only be a small portion of the possible address space. People in the past have occasionaly sent their DigiBytes to a Doge address on an exchange. Because the private key to the address they were sending already existed on the Doge blockchain and was owned by the exchange, the exchange was able to import the private key from one blockchain to another and redeem the otherwise lost coins. This of course is totally up to the desecration of the exchange. We've looked into possible solutions but have only come up with bandaids that aren't worth implementing and don't actually fix the underlying cause. My only suggestion currently, as poor as a suggestion as it might be, is to remain diligent about verifying you are sending to a DigiByte address. Almost every instance of this has been related to DigiBytes being sent to an exchange. Double check your on the DigiByte deposit page when you generated a deposit address and that your not mixing up Doge and DGB or anyother coin that might start with D It also doesn't hurt to send a very small amount and verify it was deposited to your account correctly before you send a larger amount. Its much better to risk losing 1 DigiByte to the void then 50k. Awesome explanation! |
|
|
|
DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
March 16, 2014, 07:10:39 PM |
|
Our goal is to reach over 1,000 followers on the following social media sites by next week! Share DigiByte with everyone you know and lets keep DigiByte growing! |
|
|
|
|
