I'm up running and producing blocks on the latest source. 

I was having a hard time getting the cli wallet to run.  Turns out I had an empty wallet.json file that was causing all the ruckus.  I think it was an export from 0.9.2, as I had never saved a wallet on this box.  Probably just an ID 10 T error on my part, but I figured I would mention it in case anyone else is having the same issue. 

We just pushed some significant updates / improvements to the P2P code.    Please upgrade if you can and see how they work for you.

Quote from: Xeldal on September 11, 2015, 05:10:56 PM
I've yet to see my witness produce a block. 

Not sure what I'm doing wrong.  The witness is all synced and it shows I've got votes but my ID is never listed under active witnesses and never produces anything.  as far as I can tell.

Code Select Expand


get_witness delegate.xeldal
{
  "id": "1.6.1625",
  "witness_account": "1.2.22412",
  "last_aslot": 61295,
  "signing_key": "G.................5",
  "pay_vb": "1.13.179",
  "vote_id": "1:1624",
  "total_votes": "89849588541",
  "url": ""
}


Code Select Expand

"head_block_num": 156986,
  "head_block_id": "0002653a9daea9b627f0985b5f8f1061f3eb2afe",
  "head_block_age": "7 seconds old",
  "next_maintenance_time": "2 minutes in the future",
  "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3",
  "active_witnesses": [


You should be in soon.

I've yet to see my witness produce a block. 

Not sure what I'm doing wrong.  The witness is all synced and it shows I've got votes but my ID is never listed under active witnesses and never produces anything.  as far as I can tell.


get_witness delegate.xeldal
{
  "id": "1.6.1625",
  "witness_account": "1.2.22412",
  "last_aslot": 61295,
  "signing_key": "G.................5",
  "pay_vb": "1.13.179",
  "vote_id": "1:1624",
  "total_votes": "89849588541",
  "url": ""
}


"head_block_num": 156986,
  "head_block_id": "0002653a9daea9b627f0985b5f8f1061f3eb2afe",
  "head_block_age": "7 seconds old",
  "next_maintenance_time": "2 minutes in the future",
  "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3",
  "active_witnesses": [


I just saw some major spam, a block with over 100 transactions :)    Good work.   The Node JS code seemed to handle the spam well! 

https://bitsharestalk.org/index.php/topic,18349.msg235091.html#msg235091

New protocol for witnesses to try to stay in sync vs P2P.

I have been running the latest master for 2 days - non stop

Quote from: xeroc on September 08, 2015, 06:00:19 AM

Quote from: clayop on September 08, 2015, 04:34:26 AM

Quote from: puppies on September 08, 2015, 12:48:25 AM

Quote from: bytemaster on September 08, 2015, 12:15:59 AM
I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.

Same here

Same here

Quote from: abit on September 07, 2015, 07:51:55 PM

Quote from: Riverhead on September 07, 2015, 02:07:05 AM

Is there a way to claim witness pay yet? It would help to fund testing :).

get_object "1.13.178"
[{
    "id": "1.13.178",
    "owner": "1.2.67159",
    "balance": {
      "amount": 437000000,
      "asset_id": "1.3.0"

Yes, commands here:

Code Select Expand


get_vesting_balances in.abit
withdraw_vesting in.abit 100 CORE true


I think you're allowed to withdraw 4370 CORE.

Nice catch abit.

You can also withdraw your fee refunds by calling the vesting balance object like this
unlocked >>> withdraw_vesting 1.13.173 23957 CORE true
withdraw_vesting 1.13.173 23957 CORE true
{
  "ref_block_num": 46692,
  "ref_block_prefix": 3121941031,
  "expiration": "2015-09-08T09:14:30",
  "operations": [[
      33,{
        "fee": {
          "amount": 100000,
          "asset_id": "1.3.0"
        },
        "vesting_balance": "1.13.173",
        "owner": "1.2.63354",
        "amount": {
          "amount": 2395700000,
          "asset_id": "1.3.0"
        }
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "1f51a42c36cb50c3085808e14303d6e2edc407ef6d83f4d2524d438d10e4e5598818baccacf785f48f82ea8a8074975182eea23dd885ce7ac6088c2d219a19980a"
  ]
}


This will make having enough core to test much much easier.

If anyone needs CORE let me know.

Quote from: rnglab on September 08, 2015, 06:55:37 AM
bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

Code Select Expand

2838767ms th_a       wallet.cpp:2805               import_balance       ] balances: []
10 assert_exception: Assert Exception
operations.size() > 0: A transaction must have at least one operation
    {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}}
    th_a  transaction.cpp:51 validate

    {"name_or_id":"bitshares-argentina"}
    th_a  wallet.cpp:2846 import_balance


Voted you in:
get_witness bitshares-argentina
{
  "id": "1.6.708",
  "witness_account": "1.2.8573",
  "last_aslot": 0,
  "signing_key": "GPH7B4bszRYW5SKGFUKuM6ta95MUR81ZsjUTyxLAn4Pezu5Ck9xsw",
  "vote_id": "1:707",
  "total_votes": 978271461,
  "url": ""
}
]

Quote from: rnglab on September 08, 2015, 06:55:37 AM
bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

Code Select Expand

2838767ms th_a       wallet.cpp:2805               import_balance       ] balances: []
10 assert_exception: Assert Exception
operations.size() > 0: A transaction must have at least one operation
    {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}}
    th_a  transaction.cpp:51 validate

    {"name_or_id":"bitshares-argentina"}
    th_a  wallet.cpp:2846 import_balance


I have seen that error when attempting to claim a key that doesn't have any balance.  It is not going to be your signing key or active key that has a balance associated with it.

If you can get the gui up and running it is far easier to import your balance from a json.  You can automatically claim all balances. 

I just upgrade the node with my balances on it.  After it is done syncing I will vote your witness in.

bitshares-argentina node is back with last commit version.

nathan seems to have only ~1900 CORE, not enough to vote me in.

Also getting this error when trying to import_balance from a pre snapshot balance key:

2838767ms th_a       wallet.cpp:2805               import_balance       ] balances: []
10 assert_exception: Assert Exception
operations.size() > 0: A transaction must have at least one operation
    {"trx":{"ref_block_num":0,"ref_block_prefix":0,"expiration":"1970-01-01T00:00:00","operations":[],"extensions":[]}}
    th_a  transaction.cpp:51 validate

    {"name_or_id":"bitshares-argentina"}
    th_a  wallet.cpp:2846 import_balance


Quote from: clayop on September 08, 2015, 04:34:26 AM

Quote from: puppies on September 08, 2015, 12:48:25 AM

Quote from: bytemaster on September 08, 2015, 12:15:59 AM
I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.

Same here

Quote from: clayop on September 08, 2015, 04:34:26 AM

Quote from: puppies on September 08, 2015, 12:48:25 AM

Quote from: bytemaster on September 08, 2015, 12:15:59 AM
I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.

Thanks clay.  I'll build it now, and update all my nodes.

Quote from: puppies on September 08, 2015, 12:48:25 AM

Quote from: bytemaster on September 08, 2015, 12:15:59 AM
I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?

I think it is compatible, because I'm running on the latest commit version.