Topic: 💸  DigiCube  🔷  NOW ON RAWX (NEW MCXNOW)  💸  EARN 50K CUBE/WEEK WITH TWITTER! - page 174. (Read 460478 times)

well I got a s1 just dusting right now )

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 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)*

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

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

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 


[
{
"addr" : "[2001:2002:51e3:f310:e1cb:7a90:1a4e:8051]:8888",
"services" : "00000001",
"lastsend" : 1460312147,
"lastrecv" : 1460312146,
"conntime" : 1460307031,
"version" : 60080,
"subver" : "/Windows:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Windows)/",
"inbound" : false,
"releasetime" : 0,
"height" : 602970,
"banscore" : 0
},
{
"addr" : "[2001:0:9d38:90d7:304a:3111:a41f:9f0c]:61410",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311075,
"conntime" : 1460307389,
"version" : 60080,
"subver" : "/Windows:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Windows)/",
"inbound" : true,
"releasetime" : 0,
"height" : 602979,
"banscore" : 0
},
{
"addr" : "[2001:0:5ef5:79fb:3c52:3b60:9ca7:496b]:62737",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311692,
"conntime" : 1460307481,
"version" : 60080,
"subver" : "/Beanbag:0.6.4/DigiCube:1.6.0/DigiCube:1.6.0(v1.6.0.0-Source)/",
"inbound" : true,
"releasetime" : 0,
"height" : 602983,
"banscore" : 0
},
{
"addr" : "[2001:0:9d38:6ab8:34cc:7d8:a2ae:f4c4]:56646",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311692,
"conntime" : 1460307640,
"version" : 60080,
"subver" : "/Windows:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Windows)/",
"inbound" : true,
"releasetime" : 0,
"height" : 602988,
"banscore" : 0
},
{
"addr" : "[2001:0:9d38:6ab8:3419:11b7:bb3a:f2a1]:52691",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311692,
"conntime" : 1460308858,
"version" : 60080,
"subver" : "/Beanbag:0.6.4/DigiCube:1.6.0/DigiCube:1.6.0(v1.6.0.0-Source)/",
"inbound" : true,
"releasetime" : 0,
"height" : 603046,
"banscore" : 0
},
{
"addr" : "213.108.119.84:8888",
"services" : "00000001",
"lastsend" : 1460312145,
"lastrecv" : 1460312146,
"conntime" : 1460308869,
"version" : 60080,
"subver" : "/Windows:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Windows)/",
"inbound" : false,
"releasetime" : 0,
"height" : 603046,
"banscore" : 0
},
{
"addr" : "[2001:0:5ef5:79fb:2c8a:2bb2:e486:79ab]:58814",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311692,
"conntime" : 1460309425,
"version" : 60080,
"subver" : "/Beanbag:0.6.4/DigiCube:1.6.0/DigiCube:1.6.0(v1.6.0.0-Source)/",
"inbound" : true,
"releasetime" : 0,
"height" : 603070,
"banscore" : 0
},
{
"addr" : "185.41.154.126:8888",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460312146,
"conntime" : 1460309964,
"version" : 60080,
"subver" : "/Lawnchair:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Source)/",
"inbound" : false,
"releasetime" : 0,
"height" : 603091,
"banscore" : 0
},
{
"addr" : "77.251.63.42:8888",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460312146,
"conntime" : 1460310295,
"version" : 60080,
"subver" : "/Lawnchair:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Source)/",
"inbound" : false,
"releasetime" : 0,
"height" : 603104,
"banscore" : 0
},
{
"addr" : "164.132.25.194:8888",
"services" : "00000001",
"lastsend" : 1460312152,
"lastrecv" : 1460312151,
"conntime" : 1460311593,
"version" : 60080,
"subver" : "/Source:0.6.4/DigiCube:1.2.0/DigiCube:1.2.0(v1.2.0.0-Source)/",
"inbound" : false,
"releasetime" : 0,
"height" : 555247,
"banscore" : 0
},
{
"addr" : "[2001:0:5ef5:79fb:1836:3368:a0ce:6a5b]:58578",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460311705,
"conntime" : 1460311702,
"version" : 60080,
"subver" : "/Beanbag:0.6.4/DigiCube:1.6.0/DigiCube:1.6.0(v1.6.0.0-Source)/",
"inbound" : true,
"releasetime" : 0,
"height" : 602935,
"banscore" : 0
},
{
"addr" : "[2001:0:5ef5:79fd:105f:32f4:b395:4d71]:52664",
"services" : "00000001",
"lastsend" : 1460312146,
"lastrecv" : 1460312125,
"conntime" : 1460312055,
"version" : 60080,
"subver" : "/Windows:0.6.4/DigiCube:1.8.0/DigiCube:1.8.0(v1.8.0.0-Windows)/",
"inbound" : true,
"releasetime" : 0,
"height" : 603171,
"banscore" : 0
}
]



I have yet to ever see a wallet actually make a notification to users to update their versions :/
I'm sure it's nothing difficult in the coding to broadcast a network wide message to update the client, or just have the client/daemon automatically check for new versions. why is this something still not implemented in the software?

Thanks a lot bro. I started Cube when everyone was saying that there will be something big in block 500k that cube will increase blah blah. Well, it is true that trading is like a gamble and baaam I lost haha.

Holy shit dude. Consider all this lost, you can continue following it but right now all your CUBE is imaginary money as far as your economic status is concerned.

If you're in need of financial assistance for college you should talk to the college's financial advisor ASAP. Get a job/continue working and get real financial advice from people who know what they're talking about.
Maybe some place like https://www.reddit.com/r/personalfinance/ can help slightly. You always stand to lose more than you gain with trading and you're losing right now.


I hope you make it out.

Well sadly it's true

If repairwallet is not helping you can try this:

1. Make sure your wallet has download the blockchain completely.
2. Open CMD and cd to whatever directory you have the DigiCube.exe in.
3. Type in Digicube -rescan and hit enter
4. The wallet will rescan the blockchain you have and rebuild the transaction list



I truly hope you are not serious.

When I check in Cube Richlist, I saw this different.

This is not fair. Something went wrong.




iGotSpot how you fix that?

I do hope so coz I'm a college student right now and I used up all my money because I thought that I can help my parents then the huge dump happened. I really don't know what to do but to wait for a miracle.

IN YOUR DREAMS.. well just keep on dreaming.. but its a big NO.. cube might rise soon but we cannot expect too much for it.. look at the presstab richlist.. the bigholders just keep on dumping their stake. even it will reach block 620 theres nothing change the fact that who's got bigger cubes can only benefit.. It's a miracle that cubes still hold the price of 400 satoshi. but i dont know how long can it last.. sorry dude but who know's .. you might be correct someday.. hopefully.. 

I hope cube's value will rise again :\

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

i'm on the same version (1. as you are, i closed the wallet and restarted it, and no problems. how exactly did you do the update?

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.

ok well you can wait until spots replies to you. the other option i'm thinking you can try is resync the wallet to the blockchain. go to the wallet's data directory, and delete all the files/folders EXCEPT do NOT delete the "wallet.dat" file

just be sure to download the recent blockchain from his site and put that those files in the data directory, and see if that takes care of the issue.

THanks for that but for me nothing happen,
I got this message:


15:03:15
repairwallet
15:03:15
Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers of the issue. (code -2)