[BTSX] Is this a bug?

[vikram]

This should be fixed since 0.4.21 final. Let us know otherwise.

[nethyb]

I had similar issue after upgrading the client (ubuntu command line) to "v0.4.21-RC1" last night, thinking that it may help with EXPIRED transactions issue I had with the pool. https://bitsharestalk.org/index.php?topic=6236.msg136549#new

On upgrade I was unable to wallet_transfer to any of the numerous local accounts from any of the wallets registered accounts.

As I use local accounts as a way to transfer pool payments to BTSX account keys this was a critical issue for me, so I rolled back the client version and re-synced just to get these payments out.

I haven't yet tried again with the new "v0.4.21", will let you know if OK tonight.

I have the client wallet folder logs if it turns out there is an issue and someone needs them - let me know.

./bitshares_client --version
{
  "blockchain_name": "BitShares X",
  "blockchain_description": "Decentralized Autonomous Exchange",
  "client_version": "v0.4.21-RC1",
  "bitshares_toolkit_revision": "34650324eba1025bd46929576db6621502f89fef",
  "bitshares_toolkit_revision_age": "34 hours ago",
  "fc_revision": "307252e23adfb43b41a6a4ff5683c72f86c0083a",
  "fc_revision_age": "43 hours ago",
  "compile_date": "compiled on Oct 22 2014 at 14:35:19",
  "boost_version": "1.54",
  "openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
  "build": "linux 64-bit"
}

[Yao]

details:

getStackTrace@app.js:66677:28
 ○ request@app.js:73627:31
 ○ get_account@app.js:74909:30
 ○ refresh_account@app.js:74123:41
 ○ app.js:67078:36
 ○ $watchCollectionAction@app.js:21529:19
 ○ $digest@app.js:21632:31
 ○ $apply@app.js:21885:31
 ○ app.js:19026:28
 ○ dispatch@app.js:4371:14
 ○ handle@app.js:4057:33