0 Members and 1 Guest are viewing this topic.
Quote from: Xeldal on September 15, 2014, 04:31:59 pmright. I don't use this wallet for anything but the delegate.How else can you produce blocks without setting block production true. Maybe I'm not understanding what your saying.once you have an active delegate that produces blocks ... the wallet does not scan incoming transaction weather they are intended for you or not .. so if you wanted to "trade" or "transfer" funds from within that wallet you will certainly fail seeing it in the transaction history .. as a result the funds seem lost/not transfered ...isn't that the issue you are having?If you really want to use the wallet as a regular user (non-delegate) .. you should not have a delegate imported and should also therefor not habe block production enabled ... then everything should work as intended
right. I don't use this wallet for anything but the delegate.How else can you produce blocks without setting block production true. Maybe I'm not understanding what your saying.
******** Lock old VPS walletwallet_delegate_set_block_production delegate.xeldal true
sudo apt-get updatesudo apt-get install cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev libbz2-dev libboost-dev libboost-all-dev ntpgit clone https://github.com/dacsunlimited/bitsharesx.gitgit clone https://github.com/Bitsuperlab/operation_tools.gitcd bitsharesxgit checkout v0.4.15git submodule initgit submodule updatecmake .makecd ~/bitsharesx/programs/clientscreen -S delegate./bitshares_client --server --httpport 9989 --rpcuser user --rpcpassword pass******** wait for chain to syncwallet_create xeldalunlock 99999999wallet_import_private_key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx******** Lock old VPS walletwallet_delegate_set_block_production delegate.xeldal true******** exit delegate screen (Ctrl + A + D)screen -S feedscd ~/operation_tools/btsxfeed/nano config.json.sample******** edit with delegate info etc******** save to config.json (F3)******** exit nano (Ctrl X)./btsx_feed_auto.py USD BTC CNY GLD******** exit feeds screen (Ctrl + A + D)
network_set_advanced_node_parameters { "desired_number_of_connections": 20, "maximum_number_of_connections": 20 }
wow .. you are running this as ROOT?? not recommended!! besides that it looks ok to me although your fc_revision_age looks rather 'old'have you run "git submodule update" too? or are you running the windows binary?
"client_data_dir": "/root/.BitSharesX", "client_version": "v0.4.15", "network_num_connections": 15, "network_num_connections_max": 20,
xeldal (unlocked) >>> about{ "blockchain_name": "BitShares X", "blockchain_description": "Decentralized Autonomous Exchange", "client_version": "v0.4.15", "bitshares_toolkit_revision": "26ea35eb21d67763ade4d2344afced0d60f7fbd2", "bitshares_toolkit_revision_age": "38 hours ago", "fc_revision": "3ee5f756fbbb0bd115442eceac2273c060d6b21a", "fc_revision_age": "64 hours ago", "compile_date": "compiled on Sep 15 2014 at 09:41:21"}
-- there are now 28 active connections to the p2p network--- there are now 29 active connections to the p2p network--- there are now 30 active connections to the p2p network--- there are now 29 active connections to the p2p network--- there are now 30 active connections to the p2p network--- there are now 29 active connections to the p2p network--- there are now 0 active connections to the p2p network--- there are now 1 active connections to the p2p network--- there are now 0 active connections to the p2p network--- there are now 1 active connections to the p2p network
Downloaded 0.4.15 x86.For the first time Kaspersky did not flag it as 'potentially dangerous software'. I do not know if it because of the code itself, or because I have downloaded 14 of the 16 versions before that...
I wish dacsunlimted would leave or at least make a note on github when they remove a version and replace it with another. It seems whenever they add the -a or -b it is a replaced versionv 0.4.15-a works fine on windows 7 64 bit.
Quote from: cube on September 14, 2014, 03:28:27 pmQuote from: Xeldal on September 14, 2014, 01:20:56 pmCode: [Select]:~/bitsharesx# git checkout 0.4.15error: pathspec '0.4.15' did not match any file(s) known to git.The correct name is v0.4.15-RC1.hmm. I think this is replaced with v0.4.15, which is replaced by v0.4.15 patch-aI don't know about the checkout tag for patch-a. I assumed it was just v0.4.15 again? Hard to know without explanation/direction.This is what v0.4.15 post patch-a gives me. I don't think i have the latest.Code: [Select]"blockchain_name": "BitShares X", "blockchain_description": "Decentralized Autonomous Exchange", "client_version": "v0.4.15", "bitshares_toolkit_revision": "26ea35eb21d67763ade4d2344afced0d60f7fbd2", "bitshares_toolkit_revision_age": "14 hours ago", "fc_revision": "3ee5f756fbbb0bd115442eceac2273c060d6b21a", "fc_revision_age": "40 hours ago", "compile_date": "compiled on Sep 14 2014 at 10:32:53"EDIT:v0.4.15-a worked for me.
Quote from: Xeldal on September 14, 2014, 01:20:56 pmCode: [Select]:~/bitsharesx# git checkout 0.4.15error: pathspec '0.4.15' did not match any file(s) known to git.The correct name is v0.4.15-RC1.
Code: [Select]:~/bitsharesx# git checkout 0.4.15error: pathspec '0.4.15' did not match any file(s) known to git.
:~/bitsharesx# git checkout 0.4.15error: pathspec '0.4.15' did not match any file(s) known to git.
"blockchain_name": "BitShares X", "blockchain_description": "Decentralized Autonomous Exchange", "client_version": "v0.4.15", "bitshares_toolkit_revision": "26ea35eb21d67763ade4d2344afced0d60f7fbd2", "bitshares_toolkit_revision_age": "14 hours ago", "fc_revision": "3ee5f756fbbb0bd115442eceac2273c060d6b21a", "fc_revision_age": "40 hours ago", "compile_date": "compiled on Sep 14 2014 at 10:32:53"
Quote from: arubi on September 14, 2014, 12:36:58 pmI tried rescan to recover the transactions in the gui, but nothing changed.i'd call it display bug ...go to "console" and type "wallet_account_transaction_history" ... you'll see your transactions
I tried rescan to recover the transactions in the gui, but nothing changed.
File not found in the download site because the filename is incorrect.BitSharesX-v0.4.15-x86.exe
Windows version not working.Msvcr120d.dll missingEdit: x64 version works
Mandatory Update???
How about any problems/issues, thread?Should everybody open new thread, whenever the window is too dark for his/her liking?
Quote from: testz on September 14, 2014, 06:22:04 amQuote from: tonyk on September 14, 2014, 05:33:59 am...https://github.com/dacsunlimited/bitsharesx/releasesRequired upgrade by block #494000Yes, mandatory, everybody should update until block #494000 (Monday).Windows binary will be available soon.Shouldn't be official thread for this?... or this one is good enough?
Quote from: tonyk on September 14, 2014, 05:33:59 am...https://github.com/dacsunlimited/bitsharesx/releasesRequired upgrade by block #494000Yes, mandatory, everybody should update until block #494000 (Monday).Windows binary will be available soon.
...https://github.com/dacsunlimited/bitsharesx/releasesRequired upgrade by block #494000