Delegates, start your engines!

Started by toast, June 09, 2014, 01:54:36 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 ... 9 10 11 12 13 14 15 16 17
User actions

sfinder

#20
June 09, 2014, 04:56:03 AM
Quote from: toast on June 09, 2014, 04:24:09 AM
@sfinder  I'm not sure what's going on, have not encountered this issue yet on any build I tried. Which OS version?
my os is ubuntu 14.04 and i got following CMAKE error

CMake Error at programs/client/CMakeLists.txt:8 (target_include_directories):
  target_include_directories called with invalid arguments

daniel@ubuntu:~/bitshares_toolkit$ cmake .
-- The C compiler identification is GNU 4.8.2
-- The CXX compiler identification is GNU 4.8.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8")
-- Configuring BitShares on Linux
-- Using  as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib/x86_64-linux-gnu/libdb_cxx.sooptimized/usr/lib/x86_64-linux-gnu                        /libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Using custom FindBoost.cmake
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   system
--   filesystem
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
-- Using custom FindBoost.cmake
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   coroutine
-- Configuring project fc located in: /home/daniel/bitshares_toolkit/libraries/f                        c
-- Configuring fc to build on Unix/Apple
-- Using custom FindBoost.cmake
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   system
--   filesystem
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   coroutine
-- Setting up OpenSSL root and include vars to , /include
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libssl.a;/usr/lib/x86_64-linux-gnu/l                        ibcrypto.a (found version "1.0.1f")
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
-- Finished fc module configuration...
-- Found Curses: /usr/lib/x86_64-linux-gnu/libcurses.so
-- Found Readline: /usr/include
-- Using  as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib/x86_64-linux-gnu/libdb_cxx.sooptimized/usr/lib/x86_64-linux-gnu                        /libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Enabling Bitcoin Core Wallet Imports
CMake Error at programs/client/CMakeLists.txt:8 (target_include_directories):
  target_include_directories called with invalid arguments


-- Configuring incomplete, errors occurred!
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

cgafeng

#19
June 09, 2014, 04:55:07 AM
Code Select

cgafeng (locked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
cgafeng (delegate)       670.177299 XTS           XTS5V87vRKu7K9z3nBDEprCnyyxESaTZDZubUPVc9uhfEdY6hj4Us           2014-06-09T03:57:45   0

I use wallet_account_register to register as delegate, are my delegate name is cgafeng?
when i use blockchain_list_delegates, i don't find my name.
BTC:1EYwcZ9cYVj6C9LMLafdcjK9wicVMDV376

toast

#18
June 09, 2014, 04:47:51 AM
Quote from: welk1n on June 09, 2014, 04:44:44 AM
How to be registered?         

NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL   
welk1n-d-5               0.000000 XTS             XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC           NO                    0             
welk1n-d-4               0.000000 XTS             XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA           NO                    0             
welk1n-d-3               0.000000 XTS             XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X           NO                    0             
welk1n-d-2               0.000000 XTS             XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj           NO                    0             
welk1n-d-1               0.000000 XTS             XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx           NO                    0             
"OK"

Looks like "registered" status is buggy.  Actually I see you made new accounts, you should not need to - if you just import your keys and rescan you will have pre-registered accounts "init-delegate-N". If you want to register new accounts you can use "wallet_account_register"
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

welk1n

#17
June 09, 2014, 04:44:44 AM
How to be registered?         

NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL   
welk1n-d-5               0.000000 XTS             XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC           NO                    0             
welk1n-d-4               0.000000 XTS             XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA           NO                    0             
welk1n-d-3               0.000000 XTS             XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X           NO                    0             
welk1n-d-2               0.000000 XTS             XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj           NO                    0             
welk1n-d-1               0.000000 XTS             XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx           NO                    0             
"OK"

toast

#16
June 09, 2014, 04:44:36 AM Last Edit: June 09, 2014, 04:48:15 AM by toast
Quote from: Troglodactyl on June 09, 2014, 04:38:18 AM
Quote from: toast on June 09, 2014, 04:22:45 AM
@trog   looks fine to me. "blockchain_list_registered_accounts" shows ALL accounts, not just yours.
Yours were all pre-registered with 'init-delegate-N' and not the names you gave us.

That isn't the issue.  The issue is that my accounts don't seem to be properly linking to the blockchain registered accounts on rescanning, so it looks like my delegates are inactive even though I have their keys in the wallet and it's unlocked.

What do you mean? I see your 4 accounts in both lists, they are in reversed order though.
It looks like you are producing blocks too (2 or 3 per delegate just now)

edit: the only thing I see is that "registered" is "NO" when it should be "YES" - this is a display bug only I think
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Troglodactyl

#15
June 09, 2014, 04:38:18 AM
Quote from: toast on June 09, 2014, 04:22:45 AM
@trog   looks fine to me. "blockchain_list_registered_accounts" shows ALL accounts, not just yours.
Yours were all pre-registered with 'init-delegate-N' and not the names you gave us.

That isn't the issue.  The issue is that my accounts don't seem to be properly linking to the blockchain registered accounts on rescanning, so it looks like my delegates are inactive even though I have their keys in the wallet and it's unlocked.

toast

#14
June 09, 2014, 04:24:09 AM
@sfinder  I'm not sure what's going on, have not encountered this issue yet on any build I tried. Which OS version?
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

toast

#13
June 09, 2014, 04:22:45 AM Last Edit: June 09, 2014, 04:24:50 AM by toast
@xeldal   great point, totally need more room in display. For now you can use secret command "enable_raw" before "wallet_list_receive_accounts" to get a raw json dump and see your names. Will fix soon.

@trog   looks fine to me. "blockchain_list_registered_accounts" shows ALL accounts, not just yours.
Yours were all pre-registered with 'init-delegate-N' and not the names you gave us.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Troglodactyl

#12
June 09, 2014, 04:03:36 AM Last Edit: June 09, 2014, 04:10:52 AM by Troglodactyl
Code Select
Troglodactyl_dw (unlocked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
troglodactyl-delegate-5  0.000000 XTS             XTS66egtaE9cVPqzNYew5tu2zYjGMroFUTHJYZfRmUukezVxEQ7mF           NO                    0
init-delegate-65         0.000000 XTS             XTS8TouigRWFaQ8Bxt5YrPQJwR77RKFuCmbs5hTtuiQbzgNexwzef           NO                    0
init-delegate-64         0.000000 XTS             XTS5EVghckGywFQL4StpqMiYEiRJvpSKBUUe35ePL4RMyDcwk97ko           NO                    0
init-delegate-63         0.000000 XTS             XTS8aNGydnsjGn2YH7xEvocgYF2tC6zTnuLosqYJ9DyD9n3sfrxGC           NO                    0
init-delegate-62         0.000000 XTS             XTS5DmPZBzrAxmQ5CQHQxfZ5fLWKVJ1kDvdqcBYbwBm7nuqBEcFX2           NO                    0
"OK"
Troglodactyl_dw (unlocked) >>> blockchain_list_registered_accounts init-delegate-62 4
NAME                     KEY                                                             REGISTERED            VOTES FOR      VOTES AGAINST  TRUST LEVEL
init-delega... (delegate)XTS5DmPZBzrAxmQ5CQHQxfZ5fLWKVJ1kDvdqcBYbwBm7nuqBEcFX2           2014-06-01T00:00:00   86821738348    0              0
init-delega... (delegate)XTS8aNGydnsjGn2YH7xEvocgYF2tC6zTnuLosqYJ9DyD9n3sfrxGC           2014-06-01T00:00:00   117449299698   0              0
init-delega... (delegate)XTS5EVghckGywFQL4StpqMiYEiRJvpSKBUUe35ePL4RMyDcwk97ko           2014-06-01T00:00:00   111941118448   0              0
init-delega... (delegate)XTS8TouigRWFaQ8Bxt5YrPQJwR77RKFuCmbs5hTtuiQbzgNexwzef           2014-06-01T00:00:00   105192196131   0              0
Troglodactyl_dw (unlocked) >>>

My account registration seems to be inconsistent.  Not sure what's going on there.  I cleared my data and then re-imported the wallet files.  I changed the names of the delegates that should be registered manually for consistency.

Does rescanning only check balances and not key registration?

Xeldal

#11
June 09, 2014, 03:58:59 AM Last Edit: June 09, 2014, 04:02:40 AM by Xeldal
Name is cut off with ...

Code Select
Xeldal-1 (unlocked) >>> wallet_list_receive_accounts
NAME                     BALANCE                  KEY                                                             REGISTERED            TRUST LEVEL
init-delega... (delegate)0.000000 XTS             XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit           2014-06-01T00:00:00   0
"OK"

How to >>> wallet_get_account init-delega??

is there another way to find this name somewhere?

Edit: clarity

sfinder

#10
June 09, 2014, 03:49:02 AM
Toast, have you updated GIT? I guess everyone will have the same problem as i experienced
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

sfinder

#9
June 09, 2014, 03:33:00 AM Last Edit: June 09, 2014, 03:35:06 AM by sfinder
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

Code Select
cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

toast

#8
June 09, 2014, 03:31:00 AM
What is your cmake --version?

Code Select
cmake version 2.8.12.2
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

sfinder

#7
June 09, 2014, 03:27:43 AM
check in new code from git but not able to do cmake. please check following error message


--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   coroutine
-- Setting up OpenSSL root and include vars to , /include
-- Finished fc module configuration...
-- Could NOT find Curses (missing:  CURSES_LIBRARY CURSES_INCLUDE_PATH)
-- Using  as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib/x86_64-linux-gnu/libdb_cxx.sooptimized/usr/lib/x86_64-linux-gnu/libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Enabling Bitcoin Core Wallet Imports
CMake Error at programs/client/CMakeLists.txt:8 (target_include_directories):
  target_include_directories called with invalid arguments


-- Configuring incomplete, errors occurred!
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

alt

#6
June 09, 2014, 03:17:39 AM
I'm ready, thank you  :)
Print
Go Up Pages 1 ... 9 10 11 12 13 14 15 16 17
User actions