Author

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

full member
Activity: 434
Merit: 100
full member
Activity: 213
Merit: 100
Go to Help tab click debug  click console

Type (repairwallet)  in bottom press enter.

that fixed it for me
full member
Activity: 434
Merit: 100
full member
Activity: 213
Merit: 100
hero member
Activity: 840
Merit: 500
Borderless for People, Frictionless for Banks
Installed wallet 1.6 did all that is required says 95.7% done and I have a 0 CUBE balance ?
full member
Activity: 196
Merit: 100


No fancy graphics for now, just a simple link for new wallets:
http://freestaking.com/downloads/wallet
https://github.com/DigiCubeCrypto/DigiCube



Here is the long-awaited update to DigiCube, which I am still labeling as a development release. This wallet is not yet perfect, but is a work in progress that I am only posting prematurely to get the chain moving again. I do not normally post something in this iteration before a final build, but it's been long enough and we need to get the blockchain moving again

Upgrade Process
This is only a little more detailed than a standard fork. To update to DigiCube v1.6, please follow these instructions:

1) Close all DigiCube wallets that are running
2) Backup wallet.dat in as many places as you feel comfortable with
3) Delete all files in this data directory, but leave wallet.dat and DigiCube.conf here
4) Download the Bootstrap for block 500k here: http://freestaking.com/downloads/wallet/DigiCube16-Bootstrap.zip
5) Extract these two files to the same folder as in Step 3
6) REMOVE ALL NODES. Use these two, and only these two, nodes in DigiCube.conf, until more people have had time to update:

addnode=46.105.158.205
addnode=98.144.161.18

7) Ensure the only files in this folder are the two blk files from the bootstrap, DigiCube.conf, and wallet.dat
Cool Open DigiCube v1.6 and enjoy the new experience

- Not following these instructions will result in an error when loading the wallet

NOTE: It is highly suggested to go to debug window and do 'repairwallet' without the 's to ensure all coins are displaying properly
There is no loss between forks, but when wallet.dat is loading into a bootstrap it does not verify all blocks as thoroughly without a rescan

Known Issues
Periodic wallet crashes from the debug console window
  - Will fix later; priority is to get chain moving again ASAP

Invalid Checkpoint Alert
  - This is expected and actually a good sign. It's showing the bad blocks are being invalidated properly
Please report how the wallet performs. Yes, the landing page for web is loaded like crazy right now
  - This is to stress test wallets and see how much information they are able to process in that tab, they are not permanent



The most up to date information on the situation as a whole can now always be found in-wallet by using the 'On the Web' tab

Wallet crashes have been fixed. New wallet is uploaded:

http://freestaking.com/downloads/wallet



Apologies, I am new with this kind of installation... Persistent runrecoveryexception fatal error

1) Close all DigiCube wallets that are running                                                                                                                         Ok... Done
2) Backup wallet.dat in as many places as you feel comfortable with                                                                                          Ok... Done
3) Delete all files in this data directory, but leave wallet.dat and DigiCube.conf here                                                                     Where could I find or get DigiCube.conf? From Cube wallet 1.2 or 1.6? I only have the cube 1.2 application (no other files in the folder where it was extracted) when I extracted it before staking

4) Download the Bootstrap for block 500k here: http://freestaking.com/downloads/wallet/DigiCube16-Bootstrap.zip                           Ok... Done
5) Extract these two files to the same folder as in Step 3
6) REMOVE ALL NODES. Use these two, and only these two, nodes in DigiCube.conf, until more people have had time to update:

addnode=46.105.158.205
addnode=98.144.161.18


7) Ensure the only files in this folder are the two blk files from the bootstrap, DigiCube.conf, and wallet.dat

Cool Open DigiCube v1.6 and enjoy the new experience


full member
Activity: 434
Merit: 100
now my wellet :WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers of the issue 500248 of 522748 is it ok this or what 
full member
Activity: 434
Merit: 100
at blok 498k i have 19k now i have just 14k and not confermer ( i loss all my stake from 10 mars to 14 mars +5k cube from my balance )
sr. member
Activity: 458
Merit: 250
it is ok my wellet is fine and work Wink

do you have the right amount in your wallet?
full member
Activity: 231
Merit: 100
wallet now is working fine. balance is already confirm. though no follow up with developer , your such a snail dude.. i dont know if your busy jacking off...  Grin Grin Grin Grin
full member
Activity: 434
Merit: 100
full member
Activity: 231
Merit: 100
@IGOTSPOTS


hey dude, it can't repair the wallet , ,, !!! the problems is still the same.. "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)" I am now updated in the block and my wallet is working just fine. but my BALANCE remains on UNCONFIRMED STATUS.  do you have any remedy about this issue?
hero member
Activity: 728
Merit: 500
@Digicube,  thanks for releasing the new wallet and instructions. Working well here so far.

newbie
Activity: 57
Merit: 0
Got a stake but not Confirmed after 1 hour  still  1/6 Smiley

and when c-cex and other will be enabled  ?
newbie
Activity: 10
Merit: 0
It's when you found a block, but it's not accepted by the network (for example when someone else found the block slightly earlier).

Looks like the wallet is working fine now.. Sometimes dropping the number of connections because of older clients probably, and showing the old block number, but seems to be working..
full member
Activity: 196
Merit: 100
Can you please explain to me this "Orphaned" thing, coz if Google it the shitty movie appears.  Grin ROFL
hero member
Activity: 843
Merit: 1004
i have made a conf file withe this date:

addnode=46.105.158.205
addnode=98.144.161.18
addnode=81.227.243.16
addnode=76.184.252.182

but my wallet has no connection and the amount of cube are wrong, too.

i have delete all date in %appdata% digicube without the wallet.dat



edit:

working but really slow and i miss over 10k cube

Added the nodes too, but no connections  Huh
Any more new nodes?
newbie
Activity: 10
Merit: 0
When I issued getpeerinfo I saw that I was connected to a few older clients, while I only used the new nodes. Now it looks like it's trying to sync with older nodes with later (wrong) block numbers.. Is this a problem or is it working fine in the background? Block 500195 now, updated 5 seconds ago.
full member
Activity: 213
Merit: 100
befor the bug i have 24967cube in my wallet now i have 1659cube whats wrong? somebody have the same issue


Not sure unless any of the cube that you had was after block 500000.
sr. member
Activity: 458
Merit: 250
befor the bug i have 24967cube in my wallet now i have 1659cube whats wrong? somebody have the same issue


edit: you need only go to consol and must write repairwallet
Jump to: