First stack with new wallet.
321543 cube give me only 6103 ?All 321543 was in one transaction
Strange
Status: 3923 confirmations
Date: 4/11/2016 09:29
Debit: -321543.183774 CUBE
Credit: 321543.183774 CUBE
----------------------
Credit: 6103.00 CUBE
Net amount: +6103.00 CUBE
Transaction ID:
You've hit the max. Thanks for supporting DigiCube  Split them into two transactions so tomorrow you get two stakes and those two combined will be larger than the one you got today. Actually, don't touch it. When you stake, it splits, so it already did it for you AFTER BLOCK 620k - You will be able to do it in one like you did above since the limits will be raised |
|
|
|
cube down it well be at 1 satochi shit price
Honestly dude, I wish you would just dump already and go bother someone else After all this time trying to help, you don't even have the .conf made. So many people wasted so much time on you just for you to turn around and act like a dumb asshole Fuck off dude, you won't even follow the simplest instructions given to you multiple times by many people; there is nothing anyone can do to help fix this level of ignorance |
|
|
|
|
That is proving that you are not following my instructions in the post above yours..
|
|
|
|
Close Wallet Add reservebalance=99999999 to DigiCube.conf until you are fully synced Delete everything except wallet.dat and DigiCube.conf Use the bootstrap if you want to, or sync from block 1 Open wallet DigiCube.conf should contain this: addnode=164.132.25.194
addnode=76.184.252.182
addnode=98.144.161.18
addnode=213.108.119.84
addnode=185.41.154.126
addnode=46.105.158.205
addnode=98.144.161.18
addnode=81.227.243.16
addnode=151.80.9.3
addnode=76.106.178.14
addnode=75.159.1.10
addnode=164.132.25.19
addnode=46.105.158.20
addnode=85.25.44.20
addnode=178.33.209.21
reservebalance=99999999 You are probably staking and trying to submit invalid blocks and getting yourself banned from peers. I am just guessing, though, because there are no problems at all on the network itself; this issue is definitely a local conflict Make sure it is named DigiCube.conf, not Digicube.conf or digicube.conf or DigiCube.conf.txt or anything else |
|
|
|
|
Make sure you have it named exactly
DigiCube.conf
|
|
|
|
|
The only thing you needed to do was rename it to DigiCube.conf
I have no idea what you are even doing or attempting to do anymore dude
|
|
|
|
Just so you guys know.. as a community, the best thing you can possibly do right now is keep this thread on page one and get all the chatboxes talking about the fork. This is a big change, and we don't need much help from outside, but doing this will help DigiCube more than anything else right now while we wait for the fork to kick in this week Start getting people riled up again! Just mention iGotSpots and people will go insane  |
|
|
|
it should be DigiCube.conf not Digicube.conf
There's nothing wrong with it, as long as the filename is correct whether it consists of uppercase or lowercase letters they are acceptable. DigiCube.conf is necessary |
|
|
|
I have had issues with banning old nodes before, so I chose to forego it in CUBE Yes, it's only a few lines, but adding more network rules just for convenience really mucks up efficiency. Even if it's a very small amount of work, that is added stress on each node. No reason to ban them in CUBE, though, because most people are very diligent and update quickly We also have the 'On the Web' tab in the wallet. I can add updates and alerts in there if needed. Network alerts are something I should have been doing, though, I will agree with that, but I have just been swamped trying to get a whole lot of things together at once Most of you don't even have any idea what I've been working on the past couple months at least you could make a seed node that way, to feed us from clean source. i'm pretty tired of syncing that soab every time for 30-40 min I have many seeds up that are full of peers. They are on the FreeStaking.com DNS |
|
|
|
|
It doesn't matter, but I hope the public never finds out who satoshi is
|
|
|
|
|
The only people I see losing money in a Shapeshift hack is Shapeshift itself. Customers should feel safe just by how the site operates
People posting not to leave coins on exchange are correct, but that sentiment does not apply to this situation
|
|
|
|
I think I will load up on a nice chunk of cubes  just wanted to be sure everything is working, and that dev is on it like white on rice  i'm d3m0nkingx on the rich list, for any that care. I just keep hoping people will think to hold coin and push the price, and not panic when the dumpers get scared and bail out. *edit* to many ppl don't know how to manage their finances well, and if we could all work together on this we could really make this coin hit the moon guys (girls too if are any lol)* If we get more hash on http://www.cubeminers.com when it's back up (Paul is currently doing maintenance on it), it will help hold/increase the price everyday |
|
|
|
I have had issues with banning old nodes before, so I chose to forego it in CUBE Yes, it's only a few lines, but adding more network rules just for convenience really mucks up efficiency. Even if it's a very small amount of work, that is added stress on each node. No reason to ban them in CUBE, though, because most people are very diligent and update quickly We also have the 'On the Web' tab in the wallet. I can add updates and alerts in there if needed. Network alerts are something I should have been doing, though, I will agree with that, but I have just been swamped trying to get a whole lot of things together at once Most of you don't even have any idea what I've been working on the past couple months Oh no doubt, that I agree you have a full plate, and quite an impressive job at that. That would be great to add any alerts to the web tab, I actually really like that feature of the wallet, quick access to all the info I need The good thing about that tab is that I can update the page in the background and push it to everyone's wallet without anyone needing to update the client. It just pulls the page from a freestaking.com page I use for the Qt so it can be edited on the server and show up in everyone's wallet with important info and links ;p |
|
|
|
I have had issues with banning old nodes before, so I chose to forego it in CUBE Yes, it's only a few lines, but adding more network rules just for convenience really mucks up efficiency. Even if it's a very small amount of work, that is added stress on each node. No reason to ban them in CUBE, though, because most people are very diligent and update quickly We also have the 'On the Web' tab in the wallet. I can add updates and alerts in there if needed. Network alerts are something I should have been doing, though, I will agree with that, but I have just been swamped trying to get a whole lot of things together at once Most of you don't even have any idea what I've been working on the past couple months |
|
|
|
I can't do that, this is new update and new sync. I already clean all from v1.2, 1.6, now I used 1.8 and it is fresh sync and update, but suddenly the problem from v 1.2 and 1.6 it appear in v1.8. Made in Error again.
guys how many months until you learn that this is not error in your wallet, this is error on the network. the warning means you should be cautious. now go to console and type "getpeerinfo". you'll see many nodes, and some of them old versions - those old wallets produce that chaos. not you. you are ok. to be sure - open presstab's explorer and compare last block number (and its hash) there and in your wallet Current block in the 'On the Web' tab is from the explorer. Or you can view the explorer in the wallet in that tab, as well |
|
|
|
Here are some more on v1.8:
addnode=164.132.25.194
addnode=76.184.252.182
addnode=98.144.161.18
addnode=213.108.119.84
addnode=185.41.154.126
THNX SPOT whay wallat cube at yobit is off and look price at 4k per coin?? and what happen in request to add digicube at poloniex Yobit has not responded to my emails for months. Consider them not on the same fork for now Gotta keep bugging Poloniex to get added. You were doing a good job hypin people up before to request it, keep them going |
|
|
|
|
Here are some more on v1.8:
addnode=164.132.25.194
addnode=76.184.252.182
addnode=98.144.161.18
addnode=213.108.119.84
addnode=185.41.154.126
|
|
|
|
Changelog:- Minimum Coin Age Required for 2000% stake rate has been increased 10x
- Maximum Per-Block Staking Reward has been increased 10x
These changes are to further curb inflation. Version 1.0 had 1990% average inflation. Version 1.6 has about 1440% average inflation; nice drop, but not far enough. Version 1.8 will be adjusted further if inflation does not respond as expected. This will be a change to reward long-term holders while encouraging those with no interest in the future of the coin to just get out and move on C-CEX and Bittrex have both been updated to v1.8 My wallet started acting up yesterday had tons of random orphaned blocks quantities all over the place, currently running new wallet.. Any ideas? What version were you running previously? The version right before this you sent me the link around 5days ago Please post a screenshot of the orphans if possible so I can see what the amounts were |
|
|
|
Changelog:- Minimum Coin Age Required for 2000% stake rate has been increased 10x
- Maximum Per-Block Staking Reward has been increased 10x
These changes are to further curb inflation. Version 1.0 had 1990% average inflation. Version 1.6 has about 1440% average inflation; nice drop, but not far enough. Version 1.8 will be adjusted further if inflation does not respond as expected. This will be a change to reward long-term holders while encouraging those with no interest in the future of the coin to just get out and move on C-CEX and Bittrex have both been updated to v1.8 My wallet started acting up yesterday had tons of random orphaned blocks quantities all over the place, currently running new wallet.. Any ideas? What version were you running previously? |
|
|
|
Changelog:- Minimum Coin Age Required for 2000% stake rate has been increased 10x
- Maximum Per-Block Staking Reward has been increased 10x
These changes are to further curb inflation. Version 1.0 had 1990% average inflation. Version 1.6 has about 1440% average inflation; nice drop, but not far enough. Version 1.8 will be adjusted further if inflation does not respond as expected. This will be a change to reward long-term holders while encouraging those with no interest in the future of the coin to just get out and move on C-CEX and Bittrex have both been updated to v1.8 |
|
|
|
|
Show Posts
