1441
General Discussion / Re: JDS Dry Run #2
« on: October 09, 2014, 09:37:12 pm »Are you on master? Have you tried "git submodule init" and "git submodule update"?
My fault, sorry. Wrong fc version.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Are you on master? Have you tried "git submodule init" and "git submodule update"?
[ 73%] Building CXX object libraries/net/CMakeFiles/bts_net.dir/message_oriented_connection.cpp.o
/home/peter/rpmbuild/BUILD/jds-master/libraries/net/message_oriented_connection.cpp:31:19: error: cannot declare field 'bts::net::detail::message_oriented_connection_impl::_sock' to be of abstract type 'bts::net::stcp_socket'
In file included from /home/peter/rpmbuild/BUILD/jds-master/libraries/net/message_oriented_connection.cpp:9:0:
/home/peter/rpmbuild/BUILD/jds-master/libraries/net/include/bts/net/stcp_socket.hpp:12:7: note: because the following virtual functions are pure within 'bts::net::stcp_socket':
In file included from /usr/include/fc/network/tcp_socket.hpp:4:0,
from /home/peter/rpmbuild/BUILD/jds-master/libraries/net/include/bts/net/message_oriented_connection.hpp:2,
from /home/peter/rpmbuild/BUILD/jds-master/libraries/net/message_oriented_connection.cpp:8:
/usr/include/fc/io/iostream.hpp:24:26: note: virtual std::size_t fc::istream::readsome(const std::shared_ptr<char>&, std::size_t, std::size_t)
/usr/include/fc/io/iostream.hpp:46:27: note: virtual std::size_t fc::ostream::writesome(const std::shared_ptr<const char>&, std::size_t, std::size_t)
/home/peter/rpmbuild/BUILD/jds-master/libraries/net/message_oriented_connection.cpp: In member function 'void bts::net::detail::message_oriented_connection_impl::read_loop()':
/home/peter/rpmbuild/BUILD/jds-master/libraries/net/message_oriented_connection.cpp:143:57: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
pc, please give a DNS or BTSX account name for a tip.
PTS re-parsing has finished. I compared with @pc's quisquis datasource and now they have a match. Except some minor unmatch (less than 6 satoshi due to rounding issue), other pts balances are match.
@pc can you re-run your comparison script and confirm this?
Those diffs say both sides are form the same source.
or it'll get snapshotted into Just Dice Style DAC.
Look here: http://www1.agsexplorer.com/balances/14fXr2UTa17CadcZ911N7TBFqMLpqsfNae
Compare AGS balance with DNS balance. There is an obvious discrepancy in the numbers which doesn't appear to exist for other addresses which have AGS.
The mistake is persisting for each new DAC's genesis block it seems.
(The genesis block for LTS also had a discrepancy for this address - I first asked about these discrepancies in June, but nobody seems to have an answer.)
I've started a topic like this elsewhere, (e.g. https://bitsharestalk.org/index.php?topic=9510.0) but hope for more visibility here, because I'm so perplexed...
It's niggling me, so I may keep mentioning it until someone tells me to shut up, or some kind of answer is obtained!
Any ideas - what's going on?
In the previous link there was mention of a reward for checking AGS allocations.
I think we need a definitive record of distribution, if there isn't one which is sufficient/correct.
Quote from: BitJohnSo love the concept of Bitshares! But as you can see we have yet to add it as an option since we could not credit the customers from the first snapshot.
I mean should we at this point? I get requests for bitshares and all the variations we just have not felt right adding them after the missed snapshot.
Should we try to get them to add Bitshares?
(wallet closed) >>> help wallet_import_private_key
Usage:
wallet_import_private_key <wif_key> [account_name] [create_new_account] [rescan]
Loads the private key into the specified account. Returns which account it was actually imported to.
Parameters:
wif_key (wif_private_key, required): A private key in bitcoin Wallet Import Format (WIF)
account_name (account_name, optional, defaults to null): the name of the account the key should be imported into, if null then the key must belong to an active account
create_new_account (bool, optional, defaults to false): If true, the wallet will attempt to create a new account for the name provided rather than import the key into an existing account
rescan (bool, optional, defaults to false): If true, the wallet will rescan the blockchain looking for transactions that involve this private key