I tried out building, running and also the manual test yesterday. Unless I completely missed something, the only functions available in the client are for importing private keys, generating new receiving addresses and sending bitshares to an address.
Is there any way to test trustee block generation? I tried looking at log.txt, but I could only see votes being cast.
What is the server's role in the setup?
Did both clients use the server at the same time?
What does the server know about the clients? For example, does the server know if one client is a trustee?
I'm not sure what I should've been expecting from an update dubbed "a big update", it felt like I was using a very crippled bitcoin wallet. There wasn't an asset generation option anywhere to be found, but it does make bitshares liquid, which is good for everyone.
I tried building today's pull from the bitshares_toolkit repo, but it's failing with :
/bitshares_toolkit/libraries/rpc/rpc_client.cpp: In member function ?bts::blockchain::transaction_id_type bts::rpc::detail::rpc_client_impl::sendtoaddress(const bts::blockchain::address&, const bts::blockchain::asset&, const string&, const string&)?: /home/esh/software/coins/bitshares_toolkit/libraries/rpc/rpc_client.cpp:78:193: error: no matching function for call to ?fc::rpc::json_connection::call(const char [14], fc::variant, fc::variant, fc::variant, fc::variant)? return _json_connection->call("sendtoaddress", fc::variant((std::string)address), fc::variant(amount), fc::variant(comment), fc::variant(comment_to));
Also, the ' Launch the Clients ' section of the manual test lists the command to run the clients with a Bitshares-PTS address rather than a true Bitshares address, and that fails without an error message so it should be fixed too.
Thanks for keeping us posted.