[ANN] Rubies (RBIES) Gaming and casino entertainment currency.

[mammix2]

I have tried to update to the Mac v1.2.1.0 version, but now the wallet crashes on the splash screen before it even opens up. I've backed up my wallet.dat file, and followed all the steps that you have detailed here: https://bitcointalk.org/index.php?topic=1364104.msg16300229#msg16300229

For the record, the app only crashes if I leave my original wallet.dat file in the "rubies" directory. But if I remove it from the directory, the wallet loads normally, but I don't have access to my wallet.

Any help?

There are a couple of way you can do this.
1) Use your old wallet and move all your coins to another wallet such as an exchange or a friends wallet temporarily. Backup then remove the wallet.dat file. Then run the new wallet and move the coins back in.
2) Use your old wallet and export your private keys using the debug console. dumpprivkey <rubiesaddress> Backup then remove the wallet.dat file. Run your new wallet. then import the private keys... importprivkey <rubiesprivkey> [label]

[hopenotlate]

I recently installed new version 1.2.1.0 of rubies wallet  (followed all steps suggested here https://bitcointalk.org/index.php?topic=1364104.msg16300229#msg16300229 ) and opened it a couple of hours ago after some days  I wasn't opening it.

At the moment it shows 0 active connections to rubies network ( not staking because wallet is offline) and it displays the green check meaning wallet is updated and says " Downloaded block 167398 of transaction history. Last received block was generated 51 seconds ago" whilst blockexplorer on downright corner shows current blockheight is 169547 and 28 active connections.

Any idea on whats happening with me.

Just to implement BTCforJoe feedback, I'm experiencing wallet crashes as well since I updated to the new wallet ( that I did just the same day of wallet release) but not sure which particular event makes it crushing because I let it open staking when I'm away from keyboard.
Also past days  I noticed that synching process was way slower than usual.



edit:

Closed and reopened my wallet: it initially had 2/3 active connections to rubies network, started syncing process and now (it reached block 167404 so just 6 blocks more than before) it is again in situation I descibed above ( 0 connection, not staking ,...).

[mammix2]

I recently installed new version 1.2.1.0 of rubies wallet  (followed all steps suggested here https://bitcointalk.org/index.php?topic=1364104.msg16300229#msg16300229 ) and opened it a couple of hours ago after some days  I wasn't opening it.

At the moment it shows 0 active connections to rubies network ( not staking because wallet is offline) and it displays the green check meaning wallet is updated and says " Downloaded block 167398 of transaction history. Last received block was generated 51 seconds ago" whilst blockexplorer on downright corner shows current blockheight is 169547 and 28 active connections.

Any idea on whats happening with me.

Just to implement BTCforJoe feedback, I'm experiencing wallet crashes as well since I updated to the new wallet ( that I did just the same day of wallet release) but not sure which particular event makes it crushing because I let it open staking when I'm away from keyboard.
Also past days  I noticed that synching process was way slower than usual.



edit:

Closed and reopened my wallet: it initially had 2/3 active connections to rubies network, started syncing process and now (it reached block 167404 so just 6 blocks more than before) it is again in situation I descibed above ( 0 connection, not staking ,...).

Using your debug console, run getblockbynumber 167398 then compare the hash with the same block on the explorer. If its not the same, i suspect your wallet has some incorrect block data created with the massive PoS weight fluctuations we had last week.

[hopenotlate]

I recently installed new version 1.2.1.0 of rubies wallet  (followed all steps suggested here https://bitcointalk.org/index.php?topic=1364104.msg16300229#msg16300229 ) and opened it a couple of hours ago after some days  I wasn't opening it.

At the moment it shows 0 active connections to rubies network ( not staking because wallet is offline) and it displays the green check meaning wallet is updated and says " Downloaded block 167398 of transaction history. Last received block was generated 51 seconds ago" whilst blockexplorer on downright corner shows current blockheight is 169547 and 28 active connections.

Any idea on whats happening with me.

Just to implement BTCforJoe feedback, I'm experiencing wallet crashes as well since I updated to the new wallet ( that I did just the same day of wallet release) but not sure which particular event makes it crushing because I let it open staking when I'm away from keyboard.
Also past days  I noticed that synching process was way slower than usual.



edit:

Closed and reopened my wallet: it initially had 2/3 active connections to rubies network, started syncing process and now (it reached block 167404 so just 6 blocks more than before) it is again in situation I descibed above ( 0 connection, not staking ,...).

Using your debug console, run getblockbynumber 167398 then compare the hash with the same block on the explorer. If its not the same, i suspect your wallet has some incorrect block data created with the massive PoS weight fluctuations we had last week.

Not sure if i did things correctly so will post some screenshot so you may check what I'm talking about.

This is what my wallet shows  ( its just a partial cut of the whole window because am not aware if I run some risk in showing publicly the whole one: just let me know if you need it):


and this is what I find on blockexplorer:



Please have a look if I understood you correctly and, in case, what may be the problem with my wallet.

[mammix2]

you did it all correctly

But as suspected you will need to re-sync. Follow the instructions i've posted in the past, and make sure you have a copy of your wallet.dat before starting.

[BTCforJoe]

Well, my shit's all fucked up.

Tried to bring the wallet.dat over to the new version. Copied and pasted in the rubies directory from the backup. Didn't work. The new version just crashes every time I try to open it up.

I tried opening up the new version from scratch after replacing the wallet.dat with my old one. Crashed.

I tried letting the new version sync completely before closing it and then replacing the wallet.dat. Crashed.

I've tried exporting my private key from my old wallet, and then importing it into the new wallet. Nothing.

And now when I open up my old wallet, it shows a balance of much lower than what I had before this whole goddamn ordeal. Call me a complete idiot, but what the fuck am I doing wrong?

[mammix2]

Well, my shit's all fucked up.

Tried to bring the wallet.dat over to the new version. Copied and pasted in the rubies directory from the backup. Didn't work. The new version just crashes every time I try to open it up.

I tried opening up the new version from scratch after replacing the wallet.dat with my old one. Crashed.

I tried letting the new version sync completely before closing it and then replacing the wallet.dat. Crashed.

I've tried exporting my private key from my old wallet, and then importing it into the new wallet. Nothing.

And now when I open up my old wallet, it shows a balance of much lower than what I had before this whole goddamn ordeal. Call me a complete idiot, but what the fuck am I doing wrong?

Don't worry you'll be fine. I'll explain things a bit better here:

The wallet.dat file in the previous wallet was created with a different version of BerkeleyDB that is not compatible with the the latest wallet. The has happened due to us standardizing on the DB version used in all of the pre-compiled wallets we supply.

You said you were moving your existing wallet.dat file into the new wallet. This won't work. First Send all your coins to a temporary location, make a backup of the old wallet.dat then delete it. The new version will create a brand new wallet.dat file. Then send the coins from the temporary wallet / exchange back into your new version wallet.

But before you do any of this, the next option maybe be better...

Using the private keys is an easier way to do all this, but you need to make sure you are exporting all the private keys for every address. With staking, coins get moved into new addresses all the time in the background. In your old wallet, Use coin control to check if you have many addresses with smaller balances in. If you do. gather up those addresses and send the balances back to yourself to a new address. Then once they have confirmed, dump the private keys for that new address instead.
Then import the private keys in to the new wallet version. The new wallet will automatically rescan for any missing TX

[robelneo]

My wallet is still stuck to 36% although I am seeing that it is syncing is there a way to sync it fast I had the new wallet version I want to start staking Rbies with the new version,some of my Rbies are on wallet exchange I am more comfortable to have my Rbies on my desktop wallet.

[mammix2]

My wallet is still stuck to 36% although I am seeing that it is syncing is there a way to sync it fast I had the new wallet version I want to start staking Rbies with the new version,some of my Rbies are on wallet exchange I am more comfortable to have my Rbies on my desktop wallet.

wow that is slow, in your last post you were on 35%!

I've uploaded my latest copy of the blockchain for you. Once extracted, overwrite the intended files and folders, don't let them merge. And make sure you start the wallet using the -rescan switch so all your TX will be rebuilt

https://mega.nz/#!lNwjADyC!lpP9ikooyKRxJDmut2TOCNjJfwMZwpMn5XKVGR0oR3k


Edit:
Also if any of you think you are not connected to the network correctly, e.g. stuck on a previous block. Use this method as a quick way to get back on the BlockChain!

[BTCforJoe]

Well, my shit's all fucked up.

Tried to bring the wallet.dat over to the new version. Copied and pasted in the rubies directory from the backup. Didn't work. The new version just crashes every time I try to open it up.

I tried opening up the new version from scratch after replacing the wallet.dat with my old one. Crashed.

I tried letting the new version sync completely before closing it and then replacing the wallet.dat. Crashed.

I've tried exporting my private key from my old wallet, and then importing it into the new wallet. Nothing.

And now when I open up my old wallet, it shows a balance of much lower than what I had before this whole goddamn ordeal. Call me a complete idiot, but what the fuck am I doing wrong?

Don't worry you'll be fine. I'll explain things a bit better here:

The wallet.dat file in the previous wallet was created with a different version of BerkeleyDB that is not compatible with the the latest wallet. The has happened due to us standardizing on the DB version used in all of the pre-compiled wallets we supply.

You said you were moving your existing wallet.dat file into the new wallet. This won't work. First Send all your coins to a temporary location, make a backup of the old wallet.dat then delete it. The new version will create a brand new wallet.dat file. Then send the coins from the temporary wallet / exchange back into your new version wallet.

But before you do any of this, the next option maybe be better...

Using the private keys is an easier way to do all this, but you need to make sure you are exporting all the private keys for every address. With staking, coins get moved into new addresses all the time in the background. In your old wallet, Use coin control to check if you have many addresses with smaller balances in. If you do. gather up those addresses and send the balances back to yourself to a new address. Then once they have confirmed, dump the private keys for that new address instead.
Then import the private keys in to the new wallet version. The new wallet will automatically rescan for any missing TX

Great! Thanks for this information; it's very helpful. I'll give this a shot and report back. Again, thanks for taking the time to write this out for me Question, would YoBit be a good temporary wallet for me to send my rubies? There's no issues with the fork, right?

[moneypot]

Starting tomorrow October 11.  Office hours are weekdays from 9:30AM - 5:30PM EST. 

Floor means that Rubies will be worth at least that amount going forward.  This means if you bought at the floor price, you would stand to make at least ~6% if you stake the coins for the year and will also benefit from any floor price increases.   

There will still be room for speculation and no dumping on exchanges will ever happen on Moneypot's part.

Moneypot will be offering same conversion buybacks on Rubies sold for 12 hours to allow faster deposits and wagering (Will expand on this part further later).

[moneypot]

The game is currently under development and should arrive in about a month.  For the time being, it will be the only true bustabit type game on Moneypot.

We expect the game to bring more attention to Rubies and profits from the game will go towards solidifying or increasing the floor price of Rubies.

[fortunecrypto]

Starting tomorrow October 11.  Office hours are weekdays from 9:30AM - 5:30PM EST. 

Floor means that Rubies will be worth at least that amount going forward.  This means if you bought at the floor price, you would stand to make at least ~6% if you stake the coins for the year and will also benefit from any floor price increases.   

There will still be room for speculation and no dumping on exchanges will ever happen on Moneypot's part.

Moneypot will be offering same conversion buybacks on Rubies sold for 12 hours to allow faster deposits and wagering (Will expand on this part further later).

This is a good development some unbelievers are dumping Rbies on Yobit have bought some to stake unfortunately Yobit wallet is off for our signature campaign I have to sell some of my coins just to purchase Rbies,I know rebound is forth coming.

[JackpotRacer]

Starting tomorrow October 11.  Office hours are weekdays from 9:30AM - 5:30PM EST. 

Floor means that Rubies will be worth at least that amount going forward.  This means if you bought at the floor price, you would stand to make at least ~6% if you stake the coins for the year and will also benefit from any floor price increases.   

There will still be room for speculation and no dumping on exchanges will ever happen on Moneypot's part.

Moneypot will be offering same conversion buybacks on Rubies sold for 12 hours to allow faster deposits and wagering (Will expand on this part further later).

This is a good development some unbelievers are dumping Rbies on Yobit have bought some to stake unfortunately Yobit wallet is off for our signature campaign I have to sell some of my coins just to purchase Rbies,I know rebound is forth coming.

how much is 2M rubies with a floor of 1000 Satoshi ? thx

[mammix2]

We're doing some updates and maintenance on the block explorer so it will be offline / not accurate for a few hours

[Lanzador]

The game is currently under development and should arrive in about a month.  For the time being, it will be the only true bustabit type game on Moneypot.

We expect the game to bring more attention to Rubies and profits from the game will go towards solidifying or increasing the floor price of Rubies.

Will this include the bonus system currently in-use by the original BaB?

[Trade_BTC]

Really good news here I'm happy with my Rubies staking while all this has been worked on.

[gamblingbad]

Will there be a bankroll for rbies holders to invest?

[robelneo]

Now that my wallet is fully sync and start staking I am buying more Rbies at a very low price I still believe that Rbies will get back on it's former status as one of the best crypto currency to invest,hopefully it would get back at 3000 satoshis

[Dogedigital]

Will there be a bankroll for rbies holders to invest?

Yes. Itll be the first bankroll for moneypot v2 and will open up betting for all moneypot apps if they enable it.