Quote from: dxtr on June 26, 2014, 02:17:59 pm

I have 2 strange cases:
1)

dxtr-wallet (unlocked) >>> blockchain_list_blocks 409 3
    HEIGHT                          TIME      TXN COUNT                                                 SIGNING DELEGATE    SIZE LATENCY
----------------------------------------------------------------------------------------------------------------------------------------
       409           2014-06-26T13:28:00              2                                                         scroodge     584       
       410           2014-06-26T13:30:00              1                                                  delegate-dorian     499       1
       411           2014-06-26T13:32:00              0                                                          vikram9     182      25
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats vikram9
[[
    231,{
      "missed": false,
      "latency": null
    }
  ],[
    356,{
      "missed": false,
      "latency": null
    }
  ],[
    411,{
      "missed": false,
      "latency": 25
    }
  ]
]
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats scroodge
[[
    411,{
      "missed": false,
      "latency": 0
    }
  ]
]


One command, blockchain_get_delegate_block_stats says that both scroodge and vikram9 have produced the same block,
another command, blockchain_list_blocks 409 3 lists that block 409 was created by scroodge, not 411.

2) When I send some XTS from one and the same wallet account to another in this same wallet, transaction is processed, but XTS disappears from source and does not appear in target (one of accounts is a delegate, so there is no blockchain rescan afterwards [I think]).

Are those known issues?

I'm not sure about the transfer issue, but it sounds like you are right.  can you manually wallet_rescan_blockchain?  Maybe try turning off block production first.  If neither of those work I would export the private key of the account with funds close the wallet, create another one, and import the key.

As for the blockchain_get_delegate_block_stats that same issue was happening on the last testnet.  I can't remember exactly what Bytemaster said, but it was something along the lines of an issue with delegate ID.  Perhaps its similar to the wallet bug that makes it look like you have access to others accounts.

This is a known issue we are working on.

Quote from: alt on June 26, 2014, 01:29:01 am

how many block produced by delegate-baozi?

Code: [Select]

delegate (unlocked) >>> blockchain_get_account_record delegate-baozi
Record for 'delegate-baozi' -- Registered on 2014-Jun-25 21:54:00, last update was 4 hours ago
Owner's key: XTS6UxJfhUpHVRCUC5Xk5EVtmiCjh8ZoNFaAkaWunLKqAxKEHi76z
NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   PRODUCTION RATIO    LAST BLOCK #    TOTAL PAY
----------------------------------------------------------------------------------------------------------------------------------------------------
0.00604399%         0               1               0                   N/A             0.00000 XTS
Public data:
""
delegate (unlocked) >>> blockchain_get_delegate_block_stats delegate-baozi
[[
    142,{
      "missed": true,
      "latency": null
    }
  ],[
    143,{
      "missed": false,
      "latency": 1
    }
  ]
]


Good catch... this is what the seed node reports:

Quote

blockchain_get_delegate_block_stats delegate-baozi
[[
    142,{
      "missed": true,
      "latency": null
    }
  ]
]

This is part of a known bug that Vikram is looking into.

Untested fix: https://github.com/BitShares/bitshares_toolkit/commit/c5a4d1cf708829dd30fa3112dfbe9e3e184a7b2c

sexy missed 163
 by the way , how to export fork graph ?

blockchain_get_delegate_block_stats sexy
[[
    163,{
      "missed": false,
      "latency": 0
    }
  ]
]

Quote from: alt on June 26, 2014, 02:25:42 am

Quote from: bytemaster on June 26, 2014, 02:19:37 am

delegate-dorian  is the one who apparently skipped block 164 produced by init4

Are you around dorian to report the issue you saw?

I think the forks are all created by my node?
I have these account: delegate-alt, delegate-dorian, delegate-baozi, delegate-watchman, delegate-dragon
delegate-watchman product block 111 success.
delegate-dorian miss 165
delegate-alt miss 136
delegate-dragon miss 113
delegate-baozi miss 142

here is my version info

Code: [Select]

delegate (unlocked) >>> about
{
  "bitshares_toolkit_revision": "18edd548de8a55c432e940afa04a7050919bafc4",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "3914383cfcf8be4e57f60f5d5eb7e4e83de2e2b2",
  "fc_revision_age": "23 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 21:45:11"
}


"missed": false means the block was NOT missed.

Quote from: bytemaster on June 24, 2014, 03:13:48 am

Quote from: bitcoinerS on June 23, 2014, 11:35:20 pm

wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_production_fee]

Code: [Select]

  delegate_production_fee (uint32_t, optional, defaults to 255): A value between 0 and 100% delegates, 255 for non delegates

I am confused. What is delegate production fee?

It defines the percent of transaction fees that your delegate will keep as a fee for producing the block, the rest are paid as dividends to the shareholders.   A value between 0 and 100.

Should be renamed to "delegate pay rate"

Done: https://github.com/BitShares/bitshares_toolkit/commit/613235eab279743b819af634249f11154b8352b7

Quote from: bytemaster on June 24, 2014, 05:26:36 pm

Quote from: delulo on June 24, 2014, 05:04:34 pm

Quote

It does not divide in the mathematical sense.  It is purely thumbs up/down, yes/no but proportional to stake size.

That would mean that if I vote for 2 delegates my stake would have twice the impact as if I only vote for 1 delegate??

The way it is set up you can "vote" or "not vote" for up to N delegates.   Everyone has equal influence if you choose to exercise it.

Not voting under this system means that the other candidates have less support and thus are less likely to get in than the one you do vote for.

Is there still a default setting for the wallet that votes for delegates which score high in different parameters?

Not present at the moment. Currently, the wallet simply makes a random selection of your trusted delegates to vote for in a transaction.

some fork happend strange.
Just now, I found my delegate alt && dorian begin to miss  block.
So I wait until next block generate.
first I see the block generate normaly, block ID is 4231.
after a minutes, when block 4232 is sync.
I check block 4231 again, it's different with before, means dorian create  block 4231 but refuse by the main chain.
dorian  lose block 4176 && 423,  at that time,  forked occured at 4174 && 4229.
after restart the client, everything is ok now.

Code: [Select]

delegate (unlocked) >>> blockchain_get_delegate_block_stats 299
....
  ],[
    4130,{
      "missed": false,
      "latency": 0
    }
  ],[
    4176,{
      "missed": true,
      "latency": null
    }
  ],[
    4231,{
      "missed": true,
      "latency": null
    }
  ]
]


Code: [Select]

delegate (unlocked) >>> blockchain_list_forks
....
  4174,
  4180,
  4182,
  4218,
  4227,
  4229
]


What is output of 'about' command?

Quote from: bytemaster on June 18, 2014, 11:07:24 pm

wallet_import_armory should work now.  (actually Issue #90 says it needs testing, care to help test?)

Armory import seems not implemented at all yet... Tried it with actual values, as well as random values, gives OK all the time

Code: [Select]

>>> wallet_import_armory
wallet_filename: /this/file/does/not/exist
passphrase:
account_name: well, this is not an account
OK

This was a mistake; Armory has not been implemented yet.

And 2 more questions to end:
 - do you have the armory wallet import planned for soon? If not, I imagine there should be a way for me to export the private keys from Armory and import them as bitcoin(?) keys
 - how do I import my PTS wallet?

Armory import support is planned: https://github.com/BitShares/bitshares_toolkit/issues/90
In the meantime, you can manually import private keys using wallet_import_private_key.

For importing PTS wallet, you can use wallet_import_bitcoin.