This is a special thanks to Jared, DigiByte and the community. I was around from the first day of DigiByte, where I came to translate DGB thread to another language. From then on, I traded DGB back and forth starting with 0.625 BTC worth DGB, which was awarded from translation. Once in a while I made 75BTC with DGB alone. Later I lost some. That was my biggest lesson. Then I learnt to sell anything when the time is right. You cannot just be tied to a coin even if you love it, where you can buy it back lower, at times (not the case when it is popular). This was mostly my strategy and the source of my success. I had 373m DGB back in the last rise. I sold 315m DGB between 450-760sat and selling some slowly at this current rise. I know DGB can go really high. I love DGB and thanks to Jared, I am a millionaire now. I was buying DGB at 6sat to 30sat and people at polo trollbox was making fun of me  and it is now really feeling great seeing them rekt with DGB rise and they totally missed it out. Well, Jared, many thanks again. I will still be around to watch your success. And let me know if any crowd funding is needed for the sake of DGB. Cheers up. Best, Halinyo  Congratulations, very happy for you! |
|
|
|
Sorry, but i understand absolut nothing, zero, nada You own DGB? Why? DGB is faster than Bitcoin DGB has cheaper TX's than Bitcoin DGB has better scaling and Transaction capacity than Bitcoin DGB is cheaper to get into than Bitcoin. The profit potential is very high DGB can be earned from playing games, absolutely free DGB has Segwit (for those interested, not my thing though) |
|
|
|
Guys, I really need your help. I have dbg inside the coinomi wallet. I have contacted support but they reply very hard, they are evasive and 5 days have passed without a fix..... Now they just don't answer at all. I am having troubles when I try to send DGB on android 5.1 I tried sending to different addresses and I even tried sending to a newly creted DGB wallet inside the same coinomi app. It just doesn't work. It has 2 main errors: - frequently it gives " could not send coins - broadcast transaction error " - less frequently it freezes at " please wait while your transaction is being prepared and sent " Even uninstalled and the reinstalled the app.It does not work. It doesn't matter if I change the fee,the receiving address or the amount I want to send. Doesn't work with qr scan or with send money request. Doesn't work even if I make a secondary dgb wallet inside coinomi and try to send to it. The same issue occurs when I try to exchange my dgb balance inside coinomi. Also I tried on different devices with different OS.No result. Always the same errors. They gave me this to backup my private key ( https://coinomi.com/recovery-phrase-tool.html ) but it doesn't show my correct public key when I input the wallet's recovery phrase. And it doesn't show any of my previous / actual addresses in the derived addresses field...... How the hell can I get those coins out of there??? I have a recovery phrase and a public key as resources. Make sure you set number of words for seed phrase to 18, and coin to Digibyte. You shouldn't have any problems after that. I did, did not work I think their tool is outdated. Try this https://github.com/iancoleman/bip39I have modified this for Digibyte locally, but don't have anywhere to host/drop it. Add this to the code in it's respective place with sublime text, or another editor. Maybe someone can host a modified file. digibyte: {
magicPrefix: '\x19Digibyte Signed Message:\n',
bip32: {
public: 0x0488b21e,
private: 0x0488ade4
},
pubKeyHash: 0x1E,
scriptHash: 0x05,
wif: 0x80,
dustThreshold: 0,
dustSoftThreshold: 100000,
feePerKb: 100000,
estimateFee: estimateFee('digibyte')
}, {
name: "DigiByte",
onSelect: function() {
network = bitcoin.networks.digibyte;
DOM.bip44coin.val(20);
},
}, |
|
|
|
Guys, I really need your help. I have dbg inside the coinomi wallet. I have contacted support but they reply very hard, they are evasive and 5 days have passed without a fix..... Now they just don't answer at all. I am having troubles when I try to send DGB on android 5.1 I tried sending to different addresses and I even tried sending to a newly creted DGB wallet inside the same coinomi app. It just doesn't work. It has 2 main errors: - frequently it gives " could not send coins - broadcast transaction error " - less frequently it freezes at " please wait while your transaction is being prepared and sent " Even uninstalled and the reinstalled the app.It does not work. It doesn't matter if I change the fee,the receiving address or the amount I want to send. Doesn't work with qr scan or with send money request. Doesn't work even if I make a secondary dgb wallet inside coinomi and try to send to it. The same issue occurs when I try to exchange my dgb balance inside coinomi. Also I tried on different devices with different OS.No result. Always the same errors. They gave me this to backup my private key ( https://coinomi.com/recovery-phrase-tool.html ) but it doesn't show my correct public key when I input the wallet's recovery phrase. And it doesn't show any of my previous / actual addresses in the derived addresses field...... How the hell can I get those coins out of there??? I have a recovery phrase and a public key as resources. Make sure you set number of words for seed phrase to 18, and coin to Digibyte. You shouldn't have any problems after that. |
|
|
|
I have digibytes stored in a paper wallet and was wondering how I import it to a non paper wallet when I want to.. Thanks
Anyone? From debug window console on the core wallet importprivkey "digibyteprivkey" ( "label" ) ( rescan ) or just importprivkey "digibyteprivkey" that should do the trick. That was posted a few pages back. +1 From debug command console. importprivkey. Adds a private key (as returned by dumpprivkey) to your wallet. This may take a while, as a rescan is done, looking for existing transactions. Optional [rescan] parameter added in 0.8.0. Note: There's no need to import public key, as in ECDSA (unlike RSA) this can be computed from private key. importprivkey<DGBprivkey> [label] [rescan=true] after you import a private key you MUST create a new backup of your wallet. |
|
|
|
It is 4 days since last reply of Dev about NO PAYOUT FROM OFFICIAL DGB POOL. People should know that DEVELOPER didn't pay DGB coins to MINERS. Developer decided just not talking about this. HEY People they STOLE My MONEY. IF I don't get reply, I WILL POST EVERY WERE I CAN THAT DGB IS A SCAM COIN
you sound like a child |
|
|
|
Is there anyway to recover password from my old wallet.dat. I have some dgb in it but cannot remember the password so cannot restore anything jared
Try this https://github.com/gurnec/btcrecover |
|
|
|
I rest my case. Everyone has said their piece and anyone with a cent of common sense can see what there is to see here and make their appropriate decisions.
When someone attacks you publicly accusing you of trying to extort them when they actually turned down the business deal of their lives, and then so calmly turns the world upside down and calls you the attacker, well, we all know what that is, or at least those of us who are successful do (because being successful means staying clear of those types).
Good luck Jared.
_______________________________________________________________________________ ________________
I made lots of money with DGB and I'll always remember it fondly, something that could have been great, but it's time to say goodbye. Always best to leave while you're a winner.
Oh, by the way, did anybody think to ask just how DigiByte got on CryptoID? They're soooo busy that they can't even document what they're doing (not even release notes? that should be a cut and paste of the coding . . . more or less . . . anybody with just a little exposure to that knows what I'm talking about), can't get anything right with lightweight wallets, DiguSign, etc., and complain about you reporting the issues, do you think it was DigiByte? Hell no! They don't want you to have that much blockchain info. They don't want you to have a rich list. Has anyone checked to see if what Jared said yesterday really jives with the real data rich list?
If you are answering these questions with a "no", or "don't know", do yourself a favor and do a reality check. That's just one of many examples too. And if you're asking what the others are, go back and read again, starting in 2014. And if you're too lazy, then save yourself the pain and start looking at the 2nd generation cryptocurrencies - many are already doing what DigiByte says it wants to someday do (without a road map of course, we all know the drill by now, maybe it'll change again, but by that time someone else will have it implemented - a day late, a dollar short). With these kinds of attitudes, complacency and arrogance, they wouldn't be able to make this thing successful even if someone gave it to them.
Just my assessment. Good luck with yours.
And don't blame me. 350 is still a phenomenal cash out level.
Cheers
This is an open source project and community; majority wins. If you really think it was such a great business deal, you can present it here. If the community believes it's great, then it will be the direction. If it's really that great, someone else will take you up on the offer. DGB doesn't need any one person to promote an idea or direction. If they are against DGB best interest, the majority will decide the path forward. Anyone can promote DGB. Anyone can contribute to the code, or direction of the project. There is no reason for this bickering. You sound like a millennial. Too much good contribution from you over the years to succumb to this. |
|
|
|
|
i was pages behind when I commented. I don't want to comment anymore. disregard
|
|
|
|
Will transactions from a core 4.0.3 wallet still be accepted in the blockchain?
I sent several transactions 25 minutes ago and they still have not been confirmed.
Please upgrade to v6.14.2. You probably have no peers. Over 97% of network has upgraded. Update includes 100's of changes to boost speed and efficiency. https://github.com/digibyte/digibyte/releases/tag/v6.14.2My wallet says that I have 8 connections to the network... I thought this wasn't a mandatory wallet upgrade. Has the code been changed to not allow connections or transactions from 4.0.3 wallets? The difference between 4.0.3 and 6.14.2 is like moving from a horse-drawn carriage to a corvette in terms of capability. Any reason why you are keeping a 4.0.3 wallet? Soft fork means there is no specific block height or time for activation. It also means in the process of changing (1) both wallets are still backward compatible. But once changes lock in, the lock in phase serves as a warning for rest of network to upgrade. The protocol changes go into effect once the active stage is reached. (2) This does create a fork. But it's not really a fork (!!!), when... Update to 6.14.2 and your DGB will be there. Wait, what?  my thoughts exactly. |
|
|
|
This might help those of us "non-experts" clear up some technical questions . . . or at least get started down that road towards objective, non-biased information with which to make informed decisions. Let me know if it helps and what else you have/find. TIA https://achow101.com/2016/04/Segwit-FUD-ClearupThis source is better because instead of cherry-picking myths and debunking them as your link does, this one plain and simply lists the pros and cons. who is this article by? I see scaremongering with little or even no evidence to back any of it up. I don't see how it is a better or more correct source of information, like you say it is. I was never convinced that your concerns were totally unfounded but this cannot be your foundation. Scaremongering...are you kidding me...Just do a god damned google search. http://www.deadalnix.me/2016/10/17/segwit-is-not-great/You are convinced segwit is great and could do no wrong. For that, you will never see the potential downfalls without bias. I'm fucking done here. |
|
|
|
This might help those of us "non-experts" clear up some technical questions . . . or at least get started down that road towards objective, non-biased information with which to make informed decisions. Let me know if it helps and what else you have/find. TIA https://achow101.com/2016/04/Segwit-FUD-ClearupThis source is better because instead of cherry-picking myths and debunking them as your link does, this one plain and simply lists the pros and cons. |
|
|
|
pump is over. thanks for playing again.
I don't think so, it's just corrections because of BTC rise (check other alts). + coming segwit activation has positive influence on market  and if devs fix those silly small qt deficiencies it will definitely go up much higher lol. everything should look perfectly right, like new grs, ltc etc ... many thanks for the 6.14.2 LTC and DGB will see positive gains because of segwit and being on Poloniex , the exchange with the most traded bitcoin. Other coin like grs not on Poloniex will never get anywhere in value. I was told by insiders with more btc then most of you can dream of that dgb will be going over 100 soon. Price is the only thing it will help. Arguably, price is all that matters. Segwit's one technical merit of TX malleability will not outweigh the burden of the rest of the technical debt and 30,000+ lines of bullshit code it brings along. Additionally, the fix will be for segwit tx's only, and you can say goodbye to normal tx's when segwit is here. DGB was once my favorite for its scaling innovations, speed, and lack of politics. Can't wait to dump and be done with this nonsense. Thanks for the heads up. I think it will hit 200+ this time. We will see. Keep me updated. I know the Gulden lead developer left out segwit on purpose(after the codebase update) as he had some reservations about it, instead they spent the time on revamping the wallet and adding new innovative features. I am sure digibyte has a plan and I am still heavily invested but if bitcoin decide not to go with Segwit and dgb moves onto Segwit , can it be rolled back and only have normal tx's ? Absolutely not. From http://www.deadalnix.me/2016/10/17/segwit-is-not-great/ (this is a good read btw) "Transaction malleability The primary reason SegWit was created is to solve transaction malleability. Currently, it is possible to modify a transaction in such a way that its id changes, but the transaction remains valid. This is an issue for various reasons that are fairly technical, but it is indeed worth fixing. To do so, SegWit effectively creates a new transaction format which doesn’t suffer from the problem. However, the constraint is that the new format must fit in the old one. For this reason, anyone can spend transaction are created, and all transaction have an empty signature where none is needed. Overall, this waste space and makes the transaction format bigger and more complex than it needs to be." Another good read http://www.wallstreettechnologist.com/2016/12/03/core-segwit-you-need-to-read-this/ (live site is currently down) https://archive.fo/ZnPmFSo if DGB decide to move away from segwit, it's game over. I'm sure there will be exploits either way. Good luck. |
|
|
|
pump is over. thanks for playing again.
I don't think so, it's just corrections because of BTC rise (check other alts). + coming segwit activation has positive influence on market and if devs fix those silly small qt deficiencies it will definitely go up much higher lol. everything should look perfectly right, like new grs, ltc etc ... many thanks for the 6.14.2 LTC and DGB will see positive gains because of segwit and being on Poloniex , the exchange with the most traded bitcoin. Other coin like grs not on Poloniex will never get anywhere in value. I was told by insiders with more btc then most of you can dream of that dgb will be going over 100 soon. Price is the only thing it will help. Arguably, price is all that matters. Segwit's one technical merit of TX malleability will not outweigh the burden of the rest of the technical debt and 30,000+ lines of bullshit code it brings along. Additionally, the fix will be for segwit tx's only, and you can say goodbye to normal tx's when segwit is here. DGB was once my favorite for its scaling innovations, speed, and lack of politics. Can't wait to dump and be done with this nonsense. Thanks for the heads up. I think it will hit 200+ this time. We will see. Keep me updated. |
|
|
|
So to let the community know, right now there are ASIC manufacturers attempting to block segwit activation on LTC and BTC.
This is absolute bullshit and you should be ashamed of yourself. Nobody is required to signal for segwit. Anyone who runs a node or pool/miners is free to signal or not signal for whatever the fuck they want. Quit pushing propaganda. I never though Digibyte would stoop this low. This is appalling. Please read for yourself, from the company itself: https://blog.bitmain.com/en/regarding-recent-allegations-smear-campaigns/
You obviously didn't read the full article. It's a very well written piece. Why are you bringing Bitcoin politics here? Instead of arguing the technical aspects of Segwit, you are bashing Bitmain. So professional. ASICboost has not been used on mainnet. If it was, grats to everyone on their 30% efficiency increase. "Segwit first and foremost fixes the transaction malleability issue which has plagued us all for a long time." oh really? how many times has digibyte been affected by malleability? What about the other 70% of the hashrate that isn't signaling for Segwit. Are they "blocking" segwit. Or do they feel segwit is not a good upgrade? I'll fucking say it again; nobody is required to signal for segwit, you are pushing a false narrative. To say that people are "blocking" Segwit implies that people need to do whatever the core team says. Chastising users for exercising their preferred configuration with open source software. I'm so disappointed in you right now. Why the hell are we talking about Bitcoin, Bitmain, ASICboost, and people "blocking" segwit on BTC and LTC anyways? Thanks for moving the fucking goalposts. Anyone with half a brain can see what is going on here. I'm not going to waste my time any longer. This is just ridiculous, grow up. |
|
|
|
|
anyone looking to sell around 500k to 1mil?
|
|
|
|
Hopefully none of them. It was a horrible decision to leave segwit as a soft fork for DGB. Should have made it a hard fork, or just left it out. Horrible decision. Even from a marketing standpoint it would have been better to HF. Can you elaborate why a hard fork would have been better? You should research for yourself. If I spoon feed it to you, it will be biased information. Damned if i do, damned if i don't. Most of the time people ignore the facts, or shift the goal posts. I don't have time for that shit. Anyways, I highly recommend you research it for yourself |
|
|
|
So to let the community know, right now there are ASIC manufacturers attempting to block segwit activation on LTC and BTC.
This is absolute bullshit and you should be ashamed of yourself. Nobody is required to signal for segwit. Anyone who runs a node or pool/miners is free to signal or not signal for whatever the fuck they want. Quit pushing propaganda. I never though Digibyte would stoop this low. This is appalling. |
|
|
|
Hopefully none of them. It was a horrible decision to leave segwit as a soft fork for DGB. Should have made it a hard fork, or just left it out. Horrible decision. Even from a marketing standpoint it would have been better to HF. |
|
|
|
|
Show Posts
