>> Update <<
Livecoin have confirmed the update and are on the correct chain, trading is now available on there now.
|
|
|
C-Cex have updated and confirmed to be on the correct chain BetterBets.io have updated and confirmed to be on the correct chain
Trading and gambling is now available on these sites.
LiveCoin have been informed of the update, just waiting to hear back from them now
|
|
|
>>> Mandatory Wallet Update <<<We are currently tracking an incorrect chain fork that some of you may be connected to. Please check your wallet block height and the receiving wallet matches the official explorers before moving any coins. http://blockexplorer.betterbets.io:8080/YoBit: is confirmed to be on the correct chain, C-Cex: is confirmed to be on the wrong chain. please don't move coins to or from there until they we have confirmed they are back on the correct chain!Livecoin: is confirmed to be on the wrong chain. please don't move coins to or from there until they we have confirmed they are back on the correct chain!.BetterBets.io : Is confirmed to be on the correct chain >>> Downloads <<<Windows: https://mega.nz/#!0JwBhJjQ!czmHnmpEA5sTTFqwCp5k8ss3VM-woGHvipJeSVluXtQMac: https://mega.nz/#!oVYl3IAC!wDPvkIDFwbx4t7XR9CHiX1Nip8JOM-xdSlOjldSlZoMSource: https://github.com/BetterBetsLobos/rubies-coreNote: We have standardised the use of OpenSSL v1.0.1l and Berkeley DB4 across all the wallets. Using DB4 may cause some incompatibilities with previous Mac wallets.dat files. If you run the new wallet and find it errors. Please run the previous wallet temporarily to either export your private keys or move your balances out to a different wallet such as an exchange. Then clear all the support data and resync completely using the newest version. Then you can move your coins back into the latest wallet again. (Remember to always make a backup copy of your wallet.dat file before doing this, Sorry for any inconvenience this may cause!) If your wallet seems to be stuck, or is on different or higher block number than the official explorers you will need to re-sync to get back on the correct chain. Steps needed to resync:1) Close your wallet 2) locate your application support folders (In these locations) Windows:C:\Users\<<user name>>\AppData\Roaming\rubies Mac:/Users/<<user name>>/Library/Application Support/rubies Linux:/home/<<user name>>/.rubies 3) Make a backup of the wallet.dat file, store it somewhere safe 4) delete all the other files except wallet.dat and keep any rubies.conf files you may have created 5) Start the wallet and wait for it to re-sync, which might take about 30 mins Compare you results with the block explorer as that is correct to all the nodes. Please update as soon as you can as it helps keep the network up to date with the latest code and stability features.
|
|
|
DEV, you are doing something with MAIA? The wallet is still not synchronized .... Should be ok now, my wallet is staking and the network is moving...
|
|
|
>>> Update <<<< As you all know we have been battling a re-occurring forking issue for a while now. This seems to be caused by the inconsistencies of OpenSSL versions, which has been experienced on other projects.
To that end we will soon be pushing out a mandatory update that everyone must install asap, to ensure they are on the correct chain.
>>> Network Status <<< We're in a similar state where most of the services are on the correct chain... Here is the info . - both our main nodes are on the same chain - Yobit are on the same chain - C-Cex are not and will need to re-sync. I'll contact them asap to get this done - Block explorer is being re-synced
Once the new wallets are ready we will notify you when to update..
Thanks for supporting Rubies and being patient regarding the current issues.
|
|
|
Currently on block 157649 for me. My wallet stays open but I don't monitor it constantly.
ok, 157649 is the other chain, it's currently 100 ahead. once we have the network under control we'll send out details of new wallets and info if you need to re-sync.
|
|
|
yeah the majority of the network are now on the same chain at 157549. This is the status so far..
- both our main nodes are on the same chain - Yobit are on the same chain - C-Cex are not and will need to re-sync. I'll contact them asap to get this done - Block explorer is correct
Please check your wallets and ensure they match the block explorer height. if not you will need to resync. Contact us if you need help with this
|
|
|
Hey devs RBIES block explorer as well as the BetterBets RBIES hotwallet are not pushing withdrawals out properly ; this can be seen as the http://blockexplorer.betterbets.io:8080 is stuck at block #156975 while YoBit wallet is showing block #1573XX - So that's why, among others, both my RBIES withdrawals to c-cex & to yobit have not processed nor showed up on block explorer - ty for looking into this ^) i'll look into this ASAP Once we have the network issues under control, we'll be issuing new wallets with some more fixes in to combat this in the future
|
|
|
Hey devs RBIES block explorer as well as the BetterBets RBIES hotwallet are not pushing withdrawals out properly ; this can be seen as the http://blockexplorer.betterbets.io:8080 is stuck at block #156975 while YoBit wallet is showing block #1573XX - So that's why, among others, both my RBIES withdrawals to c-cex & to yobit have not processed nor showed up on block explorer - ty for looking into this ^) i'll look into this ASAP
|
|
|
>> Network Status Update <<
We have had a couple of reports from people making a withdrawal or deposit and not receiving it.. After checking we have had confirmation that all the services below are connected correctly to the network. (At the time of writing this post)
BetterBets: https://betterbets.io/ The official Block Explorer: http://blockexplorer.betterbets.io:8080/ C-Cex: https://c-cex.com/?p=rbies-btc LiveCoin: https://www.livecoin.net/trade/index YoBit: https://yobit.net/en/trade/RBIES/BTC
if you are experiencing difficulties making a withdrawal or deposit on any of these services, firstly check your wallet block height against the official explorer, and also check if the TX ID can be found on there too. Otherwise please PM me or leave a message in the Slack channel and we'll do our best to help solve it
Thanks M
|
|
|
Nice to see you again. I hope all will continue as planned and without any problems.
We need a windows wallet still. The one fuzzbawls had expired. Please send link. Thanks. Haven't received any payment yet Have you received your payment ? If everyone would just stop the moaning and give it some more time it will be fine. This is the reason I will withdraw from Bitcointalk as soon as everything is ok and start a dedicated forum for constructive discussion. I am not in a position right now to deal with everything. I have someone working hard to get withdrawals going from Livecoin (no, not Bryce) do that we can all get staking etc.
Then we will deal will other issues. Just stop the moaning, it achieves nothing.
Please put specific tech. issues in a PM and not here as it may be missed and wait. If there are general issues I will post them here.
Let's get the withdrawals going first and get coins staking and we'll work from there.
To be exact - nothing changed - you make empty offers (byback at ico price) out of the sudden you pull another developer out of your head. You still sitting at public computer huh ? Come on everybody - open your eyes ... You evade any question. Staking is not working, masternode is not working, bayback at ico - nothing, prrof of anything NOTHING ... You only ask for more ! Come on - buyback the coins but of course only with a trustworthy escrow ... Just to confirm, i reviewed and did the Escrow for the Windows wallet. So in answer to one of your question, yes Fuzzbawls did get paid. Im sure he will confirm or i can show you the TX if needed. i understand that things can be frustrating when there are network issues and teething problems, but give EBK1000 a little time. From the conversations i have had with him i have no reason to believe he is lying about being in hospital and not able to get to a PC so easily. But rest assured he is in contact.
|
|
|
Ive been getting this error when trying to open my Rbies wallet. Whats this mean? I went through the steps to dload new wallet as well and get the same This is probably caused by a corrupt database, which most of the time is caused by a power cut or the wallet not being closed cleanly. To fix this you will need to fully re-sync. Follow these steps ensuring you keep the wallet.dat file safe and do not delete it. Download the latest Rubies wallet Steps needed to resync:1) Close your wallet 2) locate your application support folders (In these locations) Windows:C:\Users\<<user name>>\AppData\Roaming\rubies Mac:/Users/<<user name>>/Library/Application Support/rubies Linux:/home/<<user name>>/.rubies 3) Make a backup of the wallet.dat file, store it somewhere safe 4) delete all the other files except wallet.dat and keep any rubies.conf files you may have created 5) Start the wallet and wait for it to re-sync, which might take about 20 mins Compare you results with the block explorer as that is correct to all the nodes.
|
|
|
Method not found (code -32601) what doe's it means?sorry i have not much knowledge. may be i am wrong
It means you entered the command wrong. This page should give you more information pertaining to the addnode RPC command that you can use to enter nodes through the command console. http://we.lovebitco.in/bitcoin-qt/command-reference/Just to follow this up. The 'addnode' rpc command isn't included in this current wallet. but you can still include addnode info in the rubies.conf file e.g. addnode=xx.xx.xx.xx
|
|
|
YoBit have confirmed they have updated to the latest code anyway
|
|
|
Both C-Cex and LiveCoin have updated and are back in sync. Any previous transactions that were stuck should have been processed now
|
|
|
I get continuously the following error even if i have libevent built. atdsrc\tor\compat_libevent.h:18:25: fatal error: event2/util.h: No such file or directory Dunno what could be the problem. Edit: BTW i have a prebuilt version of secp256k, which was working with many coins before. I can send it to you and you can give a try. This is why we are in a bit of a pickle. ok looking at your backslashes i assume your building on Windows... Basically you need to have the event libs compiled basic steps... 1) download the source from here http://libevent.org/2) extract using tar xvfz in MSYS 3) using MSYS perform the usual stuff... ./autogen.sh ./configure make make install (as long as you have autoreconf installed this will move the libs and headers into the correct MinGW paths. 4) ensure the MinGW lib and include paths are specified in the mojocoin.pro recipe Then try building again Yep, i'm on windows.I've did it this way. Probably that autoreconf stuff is fuckin me over and over again . How could i check if libevent is build correctly? i can't get to much information from make verify generally the event libs will build or you'll see an error. if make install worked correctly you'll find the libs and headers in these paths (note these are just a couple of examples. there are many more event libs and headers that should be in these paths)<path to MinGW>\msys\1.0\local\include\ event2\util.h<path to MinGW>\msys\1.0\local\lib\libevent.a If they dont exist, the error you get when building a wallet nearly always fails on event2\util.h file is missing, so this is a good place to start looking
|
|
|
---- POLL THREAD ----Bring some feedback to the game table. We would greatly appreciate all collected.
Cheers!! ●‿● More feedback would be great, thanks to everyone who has already participated.
I'm in the process of creating an entirely new version and concepts for Rubies to help it be more future proof. ~Bjorn There used to be a thriving high stake coin sector (100-200% annual stake)... That got completely trashed when Cryptsy went out of business. Don't laugh, coins like HYP and HBN peaked at very close to $1,000,000 cap... I've always thought that linking a high stake coin to a casino would be a perfect match... Because it adds another level of speculation/gambling to the whole experience. Just another 5% stake coin is pretty boring... Bet mining/staking is potentially a brilliant idea, but don't be afraid to get creative with all aspects of staking This whole idea and coin is really brilliant it just came at a time when people were banging out huge ICO's instead of looking for long term projects they were flipping ico. As a rubies holder I'm not that happy with price at all but as a stakeholder I am really happy. I guess stakeholders are the ones who made out best by far. I knew we would because bjorn and lobos know how to make successful businesses but damn I wish my rbies had been worth alot by now. im happy with the price right now, im catching stupid dumpers at a very low price. its yummy. lol me too
|
|
|
I get continuously the following error even if i have libevent built. atdsrc\tor\compat_libevent.h:18:25: fatal error: event2/util.h: No such file or directory Dunno what could be the problem. Edit: BTW i have a prebuilt version of secp256k, which was working with many coins before. I can send it to you and you can give a try. This is why we are in a bit of a pickle. ok looking at your backslashes i assume your building on Windows... Basically you need to have the event libs compiled basic steps... 1) download the source from here http://libevent.org/2) extract using tar xvfz in MSYS 3) using MSYS perform the usual stuff... ./autogen.sh ./configure make make install (as long as you have autoreconf installed this will move the libs and headers into the correct MinGW paths. 4) ensure the MinGW lib and include paths are specified in the mojocoin.pro recipe Then try building again
|
|
|
>> Update <<
EmpoEx have update their wallet so trading is now available again.https://empoex.com
|
|
|
|