pjalakas
Member
Offline
Activity: 72
Merit: 10
|
|
July 29, 2017, 11:09:36 PM |
|
dbix 0.05 to month more buying lets DO IT!!!!
|
|
|
|
jordan coins
|
|
July 29, 2017, 11:15:19 PM |
|
ok...will someone fix this "could not find gdbix. pls check gdbix path and try again". Wallet before these last two was working fine.
|
|
|
|
mur1
Newbie
Offline
Activity: 13
Merit: 0
|
|
July 31, 2017, 11:13:20 AM |
|
When will the difficulty issue be fixed. Ive heard the devs been saying for the past month it will be soon but this soon never comes. It cant be taking this long to sort out such a crucial issue... what is going on? No devs are active here why is that.... absolutely no interaction with the community at all...
|
|
|
|
|
CrytpoGod27
|
|
July 31, 2017, 04:56:41 PM |
|
This is just a pump n dump coin. Don't buy this.
|
|
|
|
jakasi2
Newbie
Offline
Activity: 27
Merit: 0
|
|
July 31, 2017, 04:58:28 PM |
|
Sounds promising. I think the devs will wait a few days untill this bitcoin user activated soft fork is resolved and the market stabilizes.
|
|
|
|
4fanbtc (OP)
|
|
July 31, 2017, 08:12:31 PM |
|
Announcement Starting today ArabianChain will begin its accent to Block 67000 which should take around 2-3 weeks giving everyone ample time to prepare for this upgrade. For those of you familiar with mining ether you will remember the Geth 1.5.X.X which brought the Ethereum Blockchain to a stable state. The upgrade primarily contained the EIP155 (replay protection), EIP161 (state clearing), and EIP170 (code size limit) Improvements to the RPC API and the initial release of the stable Go API, iOS and Android support. The release basically overhauled the build infrastructure supporting Geth.
ArabianChain has enacted a similar Upgrade same as Expanse, Ethereum Classic and other surviving Ethereum forks of the same ilk. Thanks to our dedicated dev team and their extensive knowledge of all things Ethereum they were able to implement something similar however much more advanced to include the FluxDbix Algo based on the Ubiq Version which also will take care of the sporadic occasional lengthy Block times and the difficulty issues that have plagued the BlockChains of Ethereum and all of its forks including ArabianChain DBIX. Please research the Ethereum Geth 1.5.x.x Upgrade to help familiarize yourself with new changes.
|
|
|
|
|
iamnewhere
|
|
July 31, 2017, 08:52:24 PM Last edit: July 31, 2017, 09:15:50 PM by iamnewhere |
|
Some issue with Windows Wallet: When i just start it with "dbixwall.exe" it complained about the path to old gdbix.exe, i changed it to new path but when i start dbixwall.exe again he cannot connect to IPC - if i start gdbix manually it works without any issues. Could there be some issue with old config from previous client? So starting "bin\gdbix.exe" and then "dbixwall.exe" works without issues, just the "dbixwall.exe" cannot start the "bin\gdbix.exe" somehow correctly or is still looking somewhere wrong (even if i changed path at settings). EDIT: in log he complains about "-syncmode" parameter which doesn't exist, if i change "-syncmode=fast" to "--fast" in "Settings" of client he doesn't save it - where is the config file for this parameter to edit? i think thats the issue he doesn't start gdbix.exe with dbixwall.exe together EDIT2: workaround (at least working for me that way) just create inside the wallet folder a file called "start.bat" with the content: @echo off start .\bin\gdbix.exe --fast --cache=512 start dbixwall.exe
then start the "start.bat" instead of starting the wallet directly - just leave the gdbix.exe command line window open in background - seems to work fine for me
|
|
|
|
wariner
Legendary
Offline
Activity: 1257
Merit: 1004
pool.sexy
|
|
August 01, 2017, 08:08:44 AM |
|
All 7 dbix wallet of pool.sexy are updated to v1.5
|
Pool.sexy - Pool ETH-ETC-EXP-UBQ-ZEC-DBIX..and more low fee Discussionmy BTC: 1KiMpRAWscBvhRgLs8jDnqrZEKJzt3Ypfi
|
|
|
youretz
Member
Offline
Activity: 126
Merit: 10
|
|
August 01, 2017, 12:25:55 PM |
|
I give up, sell all the coins and stop mining.
|
|
|
|
digiworld1
|
|
August 01, 2017, 01:18:19 PM |
|
Day dreaming? It takes eth and other coins atleast afew yrs to make their names.
|
|
|
|
rdevil67
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 01, 2017, 01:20:50 PM Last edit: August 01, 2017, 01:31:14 PM by rdevil67 |
|
BUGReport, because your github repo does not have the "issue" tab: LinuxWallet does not work, even with QT5 workaround. trying to fix? qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init qt.network.ssl: QSslSocket: cannot resolve sk_new_null qt.network.ssl: QSslSocket: cannot resolve sk_push qt.network.ssl: QSslSocket: cannot resolve sk_free qt.network.ssl: QSslSocket: cannot resolve sk_num qt.network.ssl: QSslSocket: cannot resolve sk_pop_free qt.network.ssl: QSslSocket: cannot resolve sk_value qt.network.ssl: QSslSocket: cannot resolve SSL_library_init qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf qt.network.ssl: QSslSocket: cannot resolve SSLeay qt.network.ssl: QSslSocket: cannot resolve SSLeay_version qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method qt.network.ssl: QSslSocket: cannot call unresolved function sk_num QQmlApplicationEngine failed to load component qrc:///main.qml:88 Cannot assign object to property
Update / compiled it myself Result, GUI runs, but with more errors and complaining gdbix is too old (1.5.0+ needed). (same errors from earlier quote) qrc:///main.qml:88:5: QML Connections: Cannot assign to non-existent property "onError" qrc:///main.qml:88:5: QML Connections: Cannot assign to non-existent property "onFailure" qrc:///main.qml:88:5: QML Connections: Cannot assign to non-existent property "onPassphraseRequest" qrc:///main.qml:88:5: QML Connections: Cannot assign to non-existent property "onButtonRequest" qrc:///main.qml:88:5: QML Connections: Cannot assign to non-existent property "onMatrixRequest" file:///opt/Qt5.6.1/5.6/gcc_64/qml/QtQuick/Controls/Styles/Base/ApplicationWindowStyle.qml:65:50: Unable to assign ApplicationWindow_QMLTYPE_136_QML_188 to ApplicationWindow_QMLTYPE_219 file:///opt/Qt5.6.1/5.6/gcc_64/qml/QtQuick/Controls/Styles/Base/BusyIndicatorStyle.qml:82: TypeError: Cannot read property 'running' of null file:///opt/Qt5.6.1/5.6/gcc_64/qml/QtQuick/Controls/Styles/Base/BusyIndicatorStyle.qml:98: TypeError: Cannot read property 'running' of null file:///opt/Qt5.6.1/5.6/gcc_64/qml/QtQuick/Controls/Styles/Base/BusyIndicatorStyle.qml:73:46: Unable to assign BusyIndicator_QMLTYPE_41 to BusyIndicator_QMLTYPE_157 qrc:///components/PasswordDialog.qml:25: ReferenceError: parent is not defined qrc:///main.qml:89: ReferenceError: trezor is not defined
good so far: it shows my coins EndUser Experience: not so good, you need to compile all on your own to make it "stable"
|
|
|
|
digiworld1
|
|
August 01, 2017, 01:24:38 PM |
|
Announcement Starting today ArabianChain will begin its accent to Block 67000 which should take around 2-3 weeks giving everyone ample time to prepare for this upgrade. For those of you familiar with mining ether you will remember the Geth 1.5.X.X which brought the Ethereum Blockchain to a stable state. The upgrade primarily contained the EIP155 (replay protection), EIP161 (state clearing), and EIP170 (code size limit) Improvements to the RPC API and the initial release of the stable Go API, iOS and Android support. The release basically overhauled the build infrastructure supporting Geth.
ArabianChain has enacted a similar Upgrade same as Expanse, Ethereum Classic and other surviving Ethereum forks of the same ilk. Thanks to our dedicated dev team and their extensive knowledge of all things Ethereum they were able to implement something similar however much more advanced to include the FluxDbix Algo based on the Ubiq Version which also will take care of the sporadic occasional lengthy Block times and the difficulty issues that have plagued the BlockChains of Ethereum and all of its forks including ArabianChain DBIX. Please research the Ethereum Geth 1.5.x.x Upgrade to help familiarize yourself with new changes. Thanks for the update 4fanbtc! we support Dubaicoin
|
|
|
|
RPS13
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 01, 2017, 05:37:01 PM |
|
Well im a bit disappointed in the quality of the new windows wallet First of all i have the same issues with the gdbix path that is not resolved by updating the path names in the settings tab. I did get it to work with the workaround that Iamnewhere posted earlier. And now i cant figure out how to get my old v1.0.1_49-2 wallet account in to this new v2.0 software?? Ive tried exporting the wallet from the old version to a .dbixwall file and import that same file in the new v2.0 software. It tells me the import went ok, but then i still see nothing in the account list?
|
|
|
|
RPS13
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 01, 2017, 05:48:44 PM |
|
oh yeah, also the weirdest thing:
When i tried to create a new wallet account in the v2.0 software, everything works as expected. A new address is created with a balance of zero (obviously).
However when i tried running the old v1.0.1_49-2 software again, my old account was gone and the new account that was generated from within the v2.0 software showed up instead! With a balance of zero of course! I thought; jeeeez now ive done it... ive lost my old wallet account and all my mined coins in there...
But it turns out, i still had the console running with the new gdbix deamon. Closing that and restarting the v1.0.1_49-2 software thankfully restored my old wallet! Pfew!!! Crisis averted....
|
|
|
|
RPS13
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 01, 2017, 06:13:52 PM |
|
Ok finally got the new wallet working somehow.... Ive done an "Export gdbix account to directory" from the old software and then manually moved the file that was generated to the gdbix keystore directory, which is apparently located at: C:\Users\*USER*\AppData\Roaming\Dubaicoin\keystore Then firing up the new v2.0 software and i finally see my old account with the right balance
|
|
|
|
RPS13
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 01, 2017, 06:33:36 PM |
|
EDIT: in log he complains about "-syncmode" parameter which doesn't exist, if i change "-syncmode=fast" to "--fast" in "Settings" of client he doesn't save it - where is the config file for this parameter to edit? i think thats the issue he doesn't start gdbix.exe with dbixwall.exe together You are correct, sir! The syncmode parameter doesnt exist. When trying to run the gdbix deamon from a command line with the --syncmode=fast argument it will fail to start since an incorrect argument is passed. The right argument should be --fast as you suggested. The thing is that you cant change this argument within the new v2.0 software, because the setting never gets saved. So on a restart the software will always try to run gdbix with the --syncmode=fast argument. Who the hell tested this software??? Perhaps an outdated version of gdbix was supplied with the new v2.0 software?
|
|
|
|
hossminer
Newbie
Offline
Activity: 12
Merit: 0
|
|
August 01, 2017, 06:39:56 PM |
|
dbix.one is up and running with version 1.5! Block 67000 let's go
|
|
|
|
Cryptorios
|
|
August 01, 2017, 07:09:16 PM |
|
Some issue with Windows Wallet: When i just start it with "dbixwall.exe" it complained about the path to old gdbix.exe, i changed it to new path but when i start dbixwall.exe again he cannot connect to IPC - if i start gdbix manually it works without any issues. Could there be some issue with old config from previous client? So starting "bin\gdbix.exe" and then "dbixwall.exe" works without issues, just the "dbixwall.exe" cannot start the "bin\gdbix.exe" somehow correctly or is still looking somewhere wrong (even if i changed path at settings). EDIT: in log he complains about "-syncmode" parameter which doesn't exist, if i change "-syncmode=fast" to "--fast" in "Settings" of client he doesn't save it - where is the config file for this parameter to edit? i think thats the issue he doesn't start gdbix.exe with dbixwall.exe together EDIT2: workaround (at least working for me that way) just create inside the wallet folder a file called "start.bat" with the content: @echo off start .\bin\gdbix.exe --fast --cache=512 start dbixwall.exe
then start the "start.bat" instead of starting the wallet directly - just leave the gdbix.exe command line window open in background - seems to work fine for me working perfectly . thank you
|
|
|
|
|