So its been a little while since I've posted. For anyone that might remember I was working on the Android Wallet for Earthcoin. I've been silent for a while now, not because I had stopped working or forgot about earthcoin but because I had no positive news to report. Well, I finally have some news I wanted to share While I had managed to create the DigiByte wallet Earthcoin has remained elusive even though a large portion of my time was spent on it. While I wouldn't call making the DigiByte wallet easy per say, it was much easier then the Earthcoin wallet. As some might know the Earthcoin code implements the transaction comment field which complicated things significantly. The serialization had to be updated to handle the new field and with the help of HashEngineering it seems we've finally done just that. There are still some bugs to work out but transactions are working in both directions There is still an issue with saving the blockchain state to the wallet which is caused by the change in serialization but this is a huge step forward. I'll keep everyone posted as we iron out the last problems. A little sneak peak below.  |
|
|
|
What a dilemma, I sent 10,000 Digibyte coins to an exchange, I generated a deposit address and sent the the coins only to realise that I sent them to a different coin wallet, in my haste I made the mistake of mistaking Digital coin For Digibyte coin as the shortened letters for both coins are very similar and could be mistaken for each other, I was lead to believe that you can't actually send coins to a different coin wallet the client doesn't let you, in this case it did.  Obviously these coins never arrived at the exchange and now they are floating around lost in space and time, maybe in a hundred thousand years someone will download a Digibyte client and it will randomly generate the address and the recipient will be a billionaire in a split second. oh well some you win and some you lose. You can contact the exchange. They might be be able to help you out. There were 2 other who had the same issue with coins they send to coinmarket. They wouldn't release private keys to the addresses(understandable) but they can import the private key into their digibyte client and redeem them for you. I can't say if they will or won't as thats really up to the exchange, but it is possible to retrieve them. @Digibyte It seems that a few people now have done this. There was a discussion a while ago about changing "DGB" to "DIGI". I personally was in favour of DIGI at the time & still am. Is this discussion now dead or could we arrange a vote on it before Digibyte becomes even more widely adopted? It would be a shame if someone ever loses a large holding because of this avoidable issue. I've been considering this and I haven't come up with a way to do this without invalidating every current DGB address, which is not a good plan. You can change the name to DIGI from DGB but the root of the problem will still exist. Any coin based off the bitcoin source and having address's starting with 'D' will have addresses that are valid on each others network. I don't believe theres any way around it at this point. If someone has a solution I'm all ear! xploited is suddenly x2 on the cool scale; as they have only one ear and are obviously a pirate. No no no, I'm not a pirate. I'm the van gogh of crypto  |
|
|
|
What a dilemma, I sent 10,000 Digibyte coins to an exchange, I generated a deposit address and sent the the coins only to realise that I sent them to a different coin wallet, in my haste I made the mistake of mistaking Digital coin For Digibyte coin as the shortened letters for both coins are very similar and could be mistaken for each other, I was lead to believe that you can't actually send coins to a different coin wallet the client doesn't let you, in this case it did. Obviously these coins never arrived at the exchange and now they are floating around lost in space and time, maybe in a hundred thousand years someone will download a Digibyte client and it will randomly generate the address and the recipient will be a billionaire in a split second. oh well some you win and some you lose. You can contact the exchange. They might be be able to help you out. There were 2 other who had the same issue with coins they send to coinmarket. They wouldn't release private keys to the addresses(understandable) but they can import the private key into their digibyte client and redeem them for you. I can't say if they will or won't as thats really up to the exchange, but it is possible to retrieve them. @Digibyte It seems that a few people now have done this. There was a discussion a while ago about changing "DGB" to "DIGI". I personally was in favour of DIGI at the time & still am. Is this discussion now dead or could we arrange a vote on it before Digibyte becomes even more widely adopted? It would be a shame if someone ever loses a large holding because of this avoidable issue. I've been considering this and I haven't come up with a way to do this without invalidating every current DGB address, which is not a good plan. You can change the name to DIGI from DGB but the root of the problem will still exist. Any coin based off the bitcoin source and having address's starting with 'D' will have addresses that are valid on each others network. I don't believe theres any way around it at this point. If someone has a solution I'm all ear! |
|
|
|
How do you create addresses without a wallet. It there an online tool like for bitcoin that works for digibyte? Or does digibyte use the same hash methods as bitcoin or litecoin?
DigiByte uses the Scrypt algorithm instead of SHA-256. I believe Scrypt is used for Proof of Work but I'm pretty sure the addresses are still created using sha-256. They do also start with a 'd'. Something like https://github.com/litecoin-project/liteaddress.org shouldnt be that hard to modify. Something in javascript is likely the ideal solution because a hosted service would let the hoster see the private key. In javascript its all done locally. Very interesting. The DigiByte addresses start with a "D" represented by a Base58 check encoding. https://en.bitcoin.it/wiki/Base58Check_encodingYes, sorry, your absolutely correct. I was was not case sensitive there, which matters. In the source its defined at https://github.com/digibyte/DigiByteProject/blob/master/src/base58.h#L281 To know what you need to change to liteaddress.org to adapt it to your coin, simply use a diff tool to compare bitaddress.org to liteaddress.org code. The differences besides the strings for to "Bitcoin" or "Litecoin" will be the parts that need to be changed. Those parts relate the public and private addresses. I have it up and running at http://digiaddress.org but the paper wallet image hasn't been updated yet which is why I haven't been spreading the news, not that I'm keeping it secret its just isn't fully ready yet and I'm no graphics artist  |
|
|
|
What a dilemma, I sent 10,000 Digibyte coins to an exchange, I generated a deposit address and sent the the coins only to realise that I sent them to a different coin wallet, in my haste I made the mistake of mistaking Digital coin For Digibyte coin as the shortened letters for both coins are very similar and could be mistaken for each other, I was lead to believe that you can't actually send coins to a different coin wallet the client doesn't let you, in this case it did. Obviously these coins never arrived at the exchange and now they are floating around lost in space and time, maybe in a hundred thousand years someone will download a Digibyte client and it will randomly generate the address and the recipient will be a billionaire in a split second. oh well some you win and some you lose. You can contact the exchange. They might be be able to help you out. There were 2 other who had the same issue with coins they send to coinmarket. They wouldn't release private keys to the addresses(understandable) but they can import the private key into their digibyte client and redeem them for you. I can't say if they will or won't as thats really up to the exchange, but it is possible to retrieve them. |
|
|
|
I had nothing better to do  and i made a 6 second backplate teaser for digibyte. Feel free to use it for whatever you want! Go Digibyte!!!! http://youtu.be/E170kvY6CWs+1 thats awesome. great job! Sent you a few DGBs, keep up the great work! |
|
|
|
Ahh bugger, just sent 50k to coinmarket, only problem is i transferred them to a Doge address (still half asleep) what happens now? i have a feeling they are gone.
I don't think your going to like to hear this but there almost certainly gone. Since both coins are originally based off of litecoin the checksum for the addresses would be identical on either coin where they both start with 'D'. To the client it would look like a valid address, because for all intents and purposes it is. The problem is that the Dogecoin address you sent to is valid on the DigiByte network but the private key does not exist so its a un-accessible address. PM me the transaction ID and I can take a look to confirm He *could* recover the un-accessible address if he has the private key of the other one. Thats what guys in #bitcoin told us. Just use "dumpprivkey <address>" in one client and "importprivkey <key>" in the other client. Interesting. So he would need the private key for the dogecoin address he sent it to then correct? I guess that would make sense. The private keys would also be valid on either network if the addresses are valid. |
|
|
|
Does that mean the qt client is wrong or that it isn't actually giving the total? I've been going to Help->Debug Window->console typing in gettxoutsetinfo which currently says "total_amount" : 4601.00000000 |
|
|
|
Ahh bugger, just sent 50k to coinmarket, only problem is i transferred them to a Doge address (still half asleep) what happens now? i have a feeling they are gone.
I don't think your going to like to hear this but there almost certainly gone. Since both coins are originally based off of litecoin the checksum for the addresses would be identical on either coin where they both start with 'D'. To the client it would look like a valid address, because for all intents and purposes it is. The problem is that the Dogecoin address you sent to is valid on the DigiByte network but the private key does not exist so its a un-accessible address. PM me the transaction ID and I can take a look to confirm |
|
|
|
|
I set a node up at
54.200.198.82
for anyone looking for more nodes
|
|
|
|
How does 0 order drive the price down?
dunno... but I too think that is happening... what else could be the reason for doing that? and fail to coinmarket that its even possible... I'll let the dev confirm but what your witnessing is a graphic error due to the precision that is being used to display the coin value. It is not actually 0, its 0.0000034 or whatever it would work out to but is being display without enough precision to show the amount properly. It happens when someone buys or sells an amount and the amount left over is less then the precision allows for. |
|
|
|
The best thing we can do is to drum up interest in DGB with a publicity stunt of some kind.....
shame those clever shibes already sponsored the Jamaican bob sled team , that kind of publicity would kick things off big time.
I'm not sure if as awesome as the jamaican bob sled team but I suggested to the other devs that we should send digibyte to the moon. I do mean that in the physical, rocket ship, space suit kinda way. They likely thought I was joking, but I was only half joking http://en.wikipedia.org/wiki/List_of_proposed_missions_to_the_Moon |
|
|
|
Please don't talk to me about Doge  Just throwing a price out there to test the water. I already have quite a few but am open to counter offers  Anyway, who knows if they will be worth anything when they hit an exchange? I totally agree, that why I suggested I had no way to determine value. You asking for a quarter of the coins is what seemed insane, regardless of price. If you actually knew how many coins there were before offering it seems manipulative. By suggesting someone might have 500 anyone who doesn't know how to easily verify how many coins there are could easily think everyone has 500 coins and his 10 or 20 are meaningless, thus offering them to you for practically nothing. For anyone interested you can check the total amount of coins generated using the qt client, go to Help->Debug Window click on the Console tab and enter: gettxoutsetinfo |
|
|
|
You need to add nodes to your config file. To be honest I don't know where that is on a Win OS but once you find it try adding these lines: addnode=71.105.130.10
addnode=148.251.15.235
there is also a way to do it from the debug console using "addnode 71.105.130.10 add" On windows it should be located by default at c:\users\<username>\AppData\Roaming\cryptographicanomaly\cryptographicanomaly.conf where <username> is your windows username. You need to make sure you turn on "view hidden folders" or you will not be able to see the AppData directory in Windows Explorer. |
|
|
|
WTB 500 CGA for 0.05 BTC. PM me if you're interested.
Just so you know, the total amount of coins currently produced is 2098. So your asking for almost 1/4 of the supply for .05 BTC. I have no way to determine value but your offer seems insane. |
|
|
|
For anyone that missed the post a few pages ago about what were currently working on *We have a functioning Windows, Max, Linux & Android wallet with QR code support.
*We have had over 10,000 wallets downloaded in the first 3 weeks. 50,000 hits on the web site so far.
*Work is being done on an awesome DigiByte promotional video.
*Many updates are being developed for the DigiByte website.
*We are working on the DigiByte how-to guides.
*We have started work on a DGB exchange.
*We are working on getting the DigiByte foundation started.
*We are working on a light version of the DigiByte wallet for speed.
*The DigiMan is being redesigned to anyone can use him on merchandises, videos etc.
*We have layed out a marketing & advertisement plan to put DigiByte in front of a few million people once a few other things are in place.
*We are working on upgrading servers to handle more users on the DigiByte website.
*Improvements are being made to the DNS seeders.
We spent a month planning and initially making DigiByte. As of today we are only 3 weeks old. We understand people get frustrated when the price drops, but this is a market and markets cycle. We are working hard each and every day to make DigiByte better. If we could accomplish all of this overnight we would. Things take time to complete. We are trying to be as engaged as we can on here to make sure you all know we are working hard.
|
|
|
|
Chunky Pools: I have been mining for just about 6 hours there, i have 692 coins but zero confirmed? WTF? (700hash)
I mine there too, the confirmations are really slow but I always get the correct amount. Can't comment on why just that they will eventually confirm. |
|
|
|
now appears but continues to give another address new account and my balance is 0
What version of windows are you using? If its giving you an address then its making a wallet.dat file which should be in the directory that I gave previously. If you close the DigiByte wallet, copy the .dat file to that directory, reopen the digibyte wallet you backup address should be there. If you don't see the .dat file in that directory my only guess would be your version of windows is old and storing it somewhere else, but thats just a guess. I'm much more a linux expert then windows. |
|
|
|
I did it, I transferred from my computer to the dropbox and then the dropbox to another computer, and it created a new address and my balance is 0
The folder that you need to copy your wallet .dat file is at C:\Users\<username>\AppData\Roaming\DigiByte Once you place it there and close and reopen the wallet your should see your balance. there is not nothing but this also can not transfer to this location <username> is referring to your windows username. so if your windows username was "Sam" the directory would be at C:\Users\Sam\AppData\Roaming\DigiByte |
|
|
|
|
Show Posts
