Which pool is the best in your opinion? I would like to see some suggestions.
Suprnova, I have used them for 3 years with no problems, highly recommend them Totally agree, OC has always run great pools! |
|
|
|
Everything seems fine at the moment. I know the past has been a bit unstable, but since the latest wallets were released using a standardized version of OpenSSL things seem ok. The most important thing is that all the wallets i have checked or helped out with other users recently have all been on the correct block height, which points toward the consensus issues we had in the past were caused by OpenSSL 1 of the things that makes a blockchain that relies on staking unstable, is the distribution, or lack of. If you look at the block explorer top 100 you can see the majority of distribution is still within the first 25 wallets. While this is a lot better that some other projects it still shows where forking can occur. I look at the statistics every day and can see the difficulty value fluctuate regularly. This means people with large balances are not leaving their wallets open 24/7, or at least constantly staking a portion of their balances. When a wallet with a large balance that has been offline for a while, comes back online their staking potential is much greater, and can cause the their wallet to stake intensely, until the difficulty rises to compensate. This has always been an issue with any blockchain, especially if more that 1 wallet is doing the same intense staking simultaneously. Usual rules... >>Connectivity<<1) If your wallet is showing as offline, firstly restart it. if it still doesn't connect, check the debug.log and look for any 'misbehaving' messages 2) If it still shows offline after restarting it or you do see misbehaving messages in the debug log. You will need to re-sync. I've posted detailed steps on how to do this in previous posts >>Missing staking rewards<<1) Every wallet at some stage will inevitably show an invalid or unaccepted stake, this is caused by the block being found by more that 1 wallet at the same time, so the reward for that block will only be given to 1 of those wallets. 2) If you have recently had to re-sync you may need to rescan for missing transactions, especially if you have had many successive invalid transactions due to a fork. Kill the wallet and start it form the command line but also use the -rescan switch e.g. rubies-core-qt-win-v1.2.1.0.exe -rescan If anyone still has connectivity or wallet issues let us know. I hope this info help  My wallet currently contains 303k RBIES with 291k of those being on one address, would it help if this was spread over more addresses? The last time my wallet forked I was only staking around 40k or so RBIES, the other times it was 3-4x that amount that it was stuck on. no that's fine. once the balance starts to stake it will be split up into new addresses anyway. If you expand the coin control panel you will see all the smaller amounts that make up the entire balance |
|
|
|
Everything seems fine at the moment. I know the past has been a bit unstable, but since the latest wallets were released using a standardized version of OpenSSL things seem ok. The most important thing is that all the wallets i have checked or helped out with other users recently have all been on the correct block height, which points toward the consensus issues we had in the past were caused by OpenSSL 1 of the things that makes a blockchain that relies on staking unstable, is the distribution, or lack of. If you look at the block explorer top 100 you can see the majority of distribution is still within the first 25 wallets. While this is a lot better that some other projects it still shows where forking can occur. I look at the statistics every day and can see the difficulty value fluctuate regularly. This means people with large balances are not leaving their wallets open 24/7, or at least constantly staking a portion of their balances. When a wallet with a large balance that has been offline for a while, comes back online their staking potential is much greater, and can cause the their wallet to stake intensely, until the difficulty rises to compensate. This has always been an issue with any blockchain, especially if more that 1 wallet is doing the same intense staking simultaneously. Usual rules... >>Connectivity<<1) If your wallet is showing as offline, firstly restart it. if it still doesn't connect, check the debug.log and look for any 'misbehaving' messages 2) If it still shows offline after restarting it or you do see misbehaving messages in the debug log. You will need to re-sync. I've posted detailed steps on how to do this in previous posts >>Missing staking rewards<<1) Every wallet at some stage will inevitably show an invalid or unaccepted stake, this is caused by the block being found by more that 1 wallet at the same time, so the reward for that block will only be given to 1 of those wallets. 2) If you have recently had to re-sync you may need to rescan for missing transactions, especially if you have had many successive invalid transactions due to a fork. Kill the wallet and start it form the command line but also use the -rescan switch e.g. rubies-core-qt-win-v1.2.1.0.exe -rescan If anyone still has connectivity or wallet issues let us know. I hope this info help |
|
|
|
An update on my wallet situation.
My last successful stake was on October 30th, my wallet contains around 200 failed stakes without even 1 successful stake. Each failed stake is roughly 1-5 seconds after the next and goes on like this for hours on end before the wallet forks and have to resync.
This cycle keeps repeating itself no matter what.
Hi, can you tell me what block number you are on, and which version of the wallet you are using, also, if its a deamon / windows or MacOS platform you are in |
|
|
|
haha, i recognise this source code |
|
|
|
Hi All Im deving for other coins at the moment, can someone tell me how to work out the 'checkpoint of stake modifier' values within kernel.cpp ? This is for one of those oh so popular PoS coins at the moment  // Hard checkpoints of stake modifiers to ensure they are deterministic
static std::map<int, unsigned int> mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
;
Bump! I am interested how to get a Stake Modifier Checksum for the Genesis Block? I got this error: ERROR: AddToBlockIndex() : Rejected by stake modifier checkpoint height=0, modifier=0x0000000000000000
ERROR: LoadBlockIndex() : genesis block not accepted You need to comment out this check while creating the genesis block example.. https://github.com/mammix2/boostcoin-core/blob/master/src/main.cpp#L2074-L2075Then uncomment it once you're up and running |
|
|
|
I just wanted to say ocminer is a super guy and trustworthy. He will get the Suprnova pool sorted out.
Yep i agree too. I've worked on and off with OC for many years on various stuff and can say he's cool |
|
|
|
Well thinking about one thing. If one will have dual cpu xeon server with say 32gb ram, could it be used to create own virtual cloud to mine zcoin?
I have a dedicate server dual xeon 12 core(24 threads) with 32GB ram and I also mined this pool suprnova but it's not good . Out of interest what speeds are you getting using this? |
|
|
|
Problems keeps persisting my wallet is off again it stuck on block 7000 this problem has been persisting for 5 days now and the Rbies I've sent to this wallet is not yet showing up,I have downloaded the new wallet version ,added new nodes.
I had this problem repeated for three or four times. Everytime I tried the same solution suggested by gamblingbad Delete all files but not wallet.dat and start rbies wallet again.
and last time I did it (more than a week ago) it finally worked out correctly: now am synching staking and get an average of 10-12 connections to rubies network without the need to add nodes. All I can say is try again that way. I have done what you instructed and the wallet is now syncing again,but I don't if it will stuck again and from what what block,hopefully it will fully sync and all my current balance will show up. we are working on an update to fix these issues. For the moment keep checking your block height against the block explorer before you send or receive, as they are always correct. |
|
|
|
|
There are still a number of people running older wallets.
You must all be running the latest wallet to ensure stability of the network
This is a list pulled from the block explorer, of nodes that are not updated
148.251.90.34 80012 rubies:1.2.0.2 Germany
5.189.144.97 81204 rubies:1.2.0.5 Germany
202.125.20.50 80012 rubies:1.2.0.3 Australia
188.163.106.58 80012 rubies:1.2.0.3 Ukraine
81.171.81.135 80012 rubies:1.2.0.3 Netherlands
185.40.87.141 80012 rubies:1.2.0.3 Turkey
83.36.156.210 80012 rubies:1.2.0.3 Spain
185.40.87.140 80012 rubies:1.2.0.3 Turkey
195.214.175.144 80012 rubies:1.2.0.3 Turkey
104.49.160.145 80012 rubies:1.2.0.3 United States
71.28.134.204 80012 rubies:1.2.0.3 United States
158.38.214.19 80012 rubies:1.2.0.3 Norway
84.209.7.165 80012 rubies:1.2.0.3 Norway
109.70.48.106 80012 rubies:1.2.0.3 Denmark
|
|
|
|
There is something wrong with the new wallet, this is the 3rd time I have had to re-sync since the update. Each time this happens it shows I'm staking over 150k coins at once so it may be an issue with the staking code.
My wallet currently has about 250k RBIES in it.
We are looking into upgrading to a newer code base, but want to make sure its a straight forward upgrade process. One of the key things is for everyone to use the same wallet version, especially the latest as we standardised the OpenSSL and DB version used. If you look at the nodes on the network, there are still a lot of older wallets which can cause issues like these. http://blockexplorer.betterbets.io:8080/networkNote to everyone: Please make sure you are using the latest version of the wallet, and If you are building your own, please make sure you use OpenSSL v1.0.1L and BerkeleyDB4
Official wallets can be downloaded from here:
https://betterbets.io/app/content/wallet/
|
|
|
|
|
We're doing some updates and maintenance on the block explorer so it will be offline / not accurate for a few hours
|
|
|
|
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!lpP9ikooyKRxJDmut2TOCNjJfwMZwpMn5XKVGR0oR3kEdit: 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! |
|
|
|
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 |
|
|
|
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. |
|
|
|
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. |
|
|
|
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#msg16300229For 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] |
|
|
|
Any issues with the blockchain? My wallet stopped on block 165599 and won't go any further, just shows 171k rubies on stake and thats it.
Just checked, and all the nodes and exchanges are on the same correct block height. Looks like you'll need to re-sync. Follow my instructions in previous posts if you need help with this. I did notice after those buy orders were placed the PoS weight jumped up high quickly, as if someone who had a lot of RBIES in there wallet for a long time brought them back online again. General note: If you can all check your wallet block height matches the explorer, and report back if its very different. |
|
|
|
Is this a natural occurence in wallet qt. it appears below at the left side it says: "ID17- Some tx maybe invalid due to a fork, check the following before sending" can some explain this text? thank you
The notification is there to warn all users they must upgrade the the latest wallet version. If you follow the bit.ly link in the warning it will take you here: https://bitcointalk.org/index.php?topic=1364104.msg16300229#msg16300229 |
|
|
|
Is it same problem again now?
Doesn't seem to be, i checked all services and exchanges are on the same block height. I reckon the drop in Staking weight is simply that a big bag holder has closed their wallet |
|
|
|
|
Show Posts
