DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
September 14, 2014, 09:38:28 AM |
|
We just checked our seed nodes & the block explorers. They are all showing the same block & the same chain. All appears to be well there.
Could you please contact Bittrex? They have disabled DGB. We just contacted them & will report when we find out what the issue is. Thanks for the heads up!
|
|
|
|
DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
September 14, 2014, 09:45:53 AM |
|
|
|
|
|
rossr1
|
|
September 14, 2014, 10:10:22 AM |
|
Any update regards DGB wallet being disabled on Bittrex?
|
|
|
|
DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
September 14, 2014, 10:11:15 AM |
|
If anyone including mining pools, block explorers, exchanges or others are experiencing chain issues with the DigiByte wallet please restart your wallet to re-sync it.
|
|
|
|
MinersPoolEU
Member
Offline
Activity: 96
Merit: 10
|
|
September 14, 2014, 10:16:24 AM |
|
If anyone including mining pools, block explorers, exchanges or others are experiencing chain issues with the DigiByte wallet please restart your wallet to re-sync it.
To be sure, what is the blockhash of the block height 173867 please ?
|
|
|
|
DigiByte (OP)
Legendary
Offline
Activity: 1722
Merit: 1051
Official DigiByte Account
|
|
September 14, 2014, 10:25:14 AM |
|
If anyone including mining pools, block explorers, exchanges or others are experiencing chain issues with the DigiByte wallet please restart your wallet to re-sync it.
To be sure, what is the blockhash of the block height 173867 please ? DigiByte.co Seed:root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f HashDragon Seed:root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f CryptoPool Insight Explorer:BlockHash 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f Personal Wallet:18:18:54 getblockhash 173867 18:18:54 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f
|
|
|
|
MinersPoolEU
Member
Offline
Activity: 96
Merit: 10
|
|
September 14, 2014, 10:42:45 AM |
|
DigiByte.co Seed: root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f
HashDragon Seed: root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f
CryptoPool Insight Explorer: BlockHash 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f
Personal Wallet: 18:18:54 getblockhash 173867 18:18:54 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f
Ok thanks, same blockhash here too
|
|
|
|
ycagel
|
|
September 14, 2014, 11:40:30 AM |
|
Awesome news! One of the biggest Bitcoin expos out there! Will you have a booth or just an attendee? Any speaking? YC
|
|
|
|
thrassos
|
|
September 14, 2014, 12:05:21 PM |
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm?
|
|
|
|
bogglor
Sr. Member
Offline
Activity: 266
Merit: 250
DigiByte? Yes!
|
|
September 14, 2014, 12:35:53 PM |
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm? Yes, it looks right now.
|
My current miner setup: Linux - Ubuntu 12.04, Two 1.3Mh/s Scrypt ASICs, Two Radeon HD 7850 GPU mining different algos (usually qubit or skein). Click here for my DGB Address QR code. DGB Address: D6ZLjbSWu2mse3EqtoSn93nFrJ85wPKBF5 I have the DGB Gaming Wallet on my Galaxy S6
|
|
|
The_Cashier
|
|
September 14, 2014, 01:08:59 PM |
|
If anyone including mining pools, block explorers, exchanges or others are experiencing chain issues with the DigiByte wallet please restart your wallet to re-sync it.
To be sure, what is the blockhash of the block height 173867 please ? DigiByte.co Seed:root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f HashDragon Seed:root@:~# digibyted getblockhash 173867 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f CryptoPool Insight Explorer:BlockHash 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f Personal Wallet:18:18:54 getblockhash 173867 18:18:54 00000000000005894b36b2b43faa0a61ba611b22e5b19ac64cc7a206b011860f Confirmed, same blockhash for p2-pool.eu
|
|
|
|
24hralttrade
|
|
September 14, 2014, 01:28:44 PM |
|
https://bittrex.com/NewsAzure maintenance in progress, wallets will peroidically become unavailabe. As previously announced, we are in an Azure maintenance window. Wallets will go offline for short periods (30-45min).
|
|
|
|
RJF
|
|
September 14, 2014, 01:38:29 PM |
|
https://bittrex.com/NewsAzure maintenance in progress, wallets will peroidically become unavailabe. As previously announced, we are in an Azure maintenance window. Wallets will go offline for short periods (30-45min). People are always so quick to blame the coin when they see a problem on an exchange. Some of these "exchanges" are held together with bubblegum and tape but their GUI looks good! At least Bittrex put up a message telling everyone there was maintenance going on...
|
DNotesVault“First, they ignore you. Then, they laugh at you. Then, they fight you. Then you win!” – Mahatma Gandhi Prepare for your future now, check out CRISP For Retirement and our complete family of CRISP savings plans.
|
|
|
|
ycagel
|
|
September 14, 2014, 02:10:32 PM |
|
A few more notes:
1.Mintpal support finally got back to me and they said there is an error with the quantity of DGB being sent to a physical wallet. They cancelled and I did a smaller test and it worked. When I reverted back to the original transaction, it hung again. I also asked them to restart and reindex their wallet, so just something for folks to think about when trading with their platform.
2.I have thinking about various ways for folks to protect their interest in DGB. I have heard of everything from dumping keys, paper wallets and even cold storage. In regards to cold storage, can someone explain the process and how the liquidity flow works if you are looking to "connect" back to the Internet and sell, trade, etc? I particularly use Coinbase, which is the only option at this point. Like to understand more how this process works.
Thanks to everyone. Keep up the momentum and great work. Can't do it without you folks as you are leading us to the final destination for DGB!
YC
|
|
|
|
ycagel
|
|
September 14, 2014, 02:20:00 PM |
|
Did some more research and it seems to be called deep cold storage: Deep cold storage refers to keeping a reserve of Bitcoins offline, using a method that makes retrieving coins from storage significantly more difficult than sending them there. This could be done for safety's sake, such as to prevent theft or robbery.
Because Bitcoins can be sent to a wallet by anyone knowing the wallet address, it is trivial to put a wallet in cold storage but to keep a copy of the addresses needed to send funds to it.
A simple example of deep cold storage is opening a safe deposit box and putting a USB stick containing an encrypted wallet file in it. The public (sending) addresses can be used any time to send additional bitcoins to the wallet, but spending the bitcoins would require physical access to the box (in addition to knowledge of the encryption password).
Deep cold storage would typically be used for holding large amounts of bitcoins, or for a trustee holding bitcoins on behalf of others. In such a case, additional precautions should be taken beyond a simple example of a single safe deposit box.
The box could be accessed by bank or maintenance personnel, so the contents of the box alone should not be sufficient to access the wallet. The box could be stolen or destroyed in a disaster, or the media could become unreadable, so the box should not contain the only copy of the wallet. The trustee could die or become incapacitated. If access to the wallet or knowledge of its location is lost, or encryption passwords are lost, the bitcoins are gone forever. Provisions should be made so that the box can be accessed by someone else as appropriate, including any encryption passwords. Source: https://en.bitcoin.it/wiki/Cold_storageA few more notes:
1.Mintpal support finally got back to me and they said there is an error with the quantity of DGB being sent to a physical wallet. They cancelled and I did a smaller test and it worked. When I reverted back to the original transaction, it hung again. I also asked them to restart and reindex their wallet, so just something for folks to think about when trading with their platform.
2.I have thinking about various ways for folks to protect their interest in DGB. I have heard of everything from dumping keys, paper wallets and even cold storage. In regards to cold storage, can someone explain the process and how the liquidity flow works if you are looking to "connect" back to the Internet and sell, trade, etc? I particularly use Coinbase, which is the only option at this point. Like to understand more how this process works.
Thanks to everyone. Keep up the momentum and great work. Can't do it without you folks as you are leading us to the final destination for DGB!
YC
|
|
|
|
bogglor
Sr. Member
Offline
Activity: 266
Merit: 250
DigiByte? Yes!
|
|
September 14, 2014, 05:45:14 PM |
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm? Yes, it looks right now. I noticed something else with the Skein pool. This isn't a big deal, but we found an orphan block which isn't being reported in the pool statistics. I know we don't get any credit, but shouldn't that be listed in the pool?
|
My current miner setup: Linux - Ubuntu 12.04, Two 1.3Mh/s Scrypt ASICs, Two Radeon HD 7850 GPU mining different algos (usually qubit or skein). Click here for my DGB Address QR code. DGB Address: D6ZLjbSWu2mse3EqtoSn93nFrJ85wPKBF5 I have the DGB Gaming Wallet on my Galaxy S6
|
|
|
iikun
Legendary
Offline
Activity: 1062
Merit: 1003
|
|
September 14, 2014, 05:52:40 PM |
|
Did some more research and it seems to be called deep cold storage: Deep cold storage refers to keeping a reserve of Bitcoins offline, using a method that makes retrieving coins from storage significantly more difficult than sending them there. This could be done for safety's sake, such as to prevent theft or robbery.
Because Bitcoins can be sent to a wallet by anyone knowing the wallet address, it is trivial to put a wallet in cold storage but to keep a copy of the addresses needed to send funds to it.
A simple example of deep cold storage is opening a safe deposit box and putting a USB stick containing an encrypted wallet file in it. The public (sending) addresses can be used any time to send additional bitcoins to the wallet, but spending the bitcoins would require physical access to the box (in addition to knowledge of the encryption password).
Deep cold storage would typically be used for holding large amounts of bitcoins, or for a trustee holding bitcoins on behalf of others. In such a case, additional precautions should be taken beyond a simple example of a single safe deposit box.
The box could be accessed by bank or maintenance personnel, so the contents of the box alone should not be sufficient to access the wallet. The box could be stolen or destroyed in a disaster, or the media could become unreadable, so the box should not contain the only copy of the wallet. The trustee could die or become incapacitated. If access to the wallet or knowledge of its location is lost, or encryption passwords are lost, the bitcoins are gone forever. Provisions should be made so that the box can be accessed by someone else as appropriate, including any encryption passwords. Source: https://en.bitcoin.it/wiki/Cold_storageA few more notes:
1.Mintpal support finally got back to me and they said there is an error with the quantity of DGB being sent to a physical wallet. They cancelled and I did a smaller test and it worked. When I reverted back to the original transaction, it hung again. I also asked them to restart and reindex their wallet, so just something for folks to think about when trading with their platform.
2.I have thinking about various ways for folks to protect their interest in DGB. I have heard of everything from dumping keys, paper wallets and even cold storage. In regards to cold storage, can someone explain the process and how the liquidity flow works if you are looking to "connect" back to the Internet and sell, trade, etc? I particularly use Coinbase, which is the only option at this point. Like to understand more how this process works.
Thanks to everyone. Keep up the momentum and great work. Can't do it without you folks as you are leading us to the final destination for DGB!
YC
I'm not sure its quite required just yet. I'd say writing it to a usb is safe enough, the data is supposed to outlast you if you don't use it too often. Not quite as safe as a safety deposit, but a whole lot cheaper.
|
|
|
|
thrassos
|
|
September 14, 2014, 06:18:22 PM |
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm? Yes, it looks right now. I noticed something else with the Skein pool. This isn't a big deal, but we found an orphan block which isn't being reported in the pool statistics. I know we don't get any credit, but shouldn't that be listed in the pool? Thank you bogglor. This should be fixed now, as there was an issue with nomp stratum; it could not verify the submitted block because the blockhash using to do the verification was not correct. Moreover, the specific block is not shown as orphan in the transactions of our wallet (I will have to check this). [digibyte-skein] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"14f","ip":"xxx.xxx.xxx.xxx","port":5019,"worker":"xxxxxxxxxx","height":173577,"blockReward":757083663854,"difficulty":0.62335653,"shareDiff":"1802.29621833","blockDiff":1312.094260319,"blockDiffActual":1312.094260319,"blockHash":"0000000000245ca8930225c59debd1a267bcdbde27f2a77a2b810c68350bcfb9"}
|
|
|
|
HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
September 14, 2014, 07:55:52 PM |
|
The market is going very strong! Watch out when you buy, maybe placing a buy order some lower will benefit you overnight because healthy markets take a dump.
And this market is looking very healthy! I'm sooooooo tempted to go after another batch right now, and forget about waiting until January . . .
|
|
|
|
|