Author Topic: BitShares 2 Release Coordination Thread  (Read 28392 times)

0 Members and 1 Guest are viewing this topic.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
is there a way to see my voting power (+proxies)?

Offline Spectral

General question: Where should I post bugs/log files? Is there a "technical" thread after release?
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade
{
  "id": "1.6.39",
  "witness_account": "1.2.6956",
  "last_aslot": 0,
  "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy",
  "vote_id": "1:49",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

^^^^ I was active throughout all the testnet :)
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline Spectral

Witnesses, please post also if you were active on testnet. That will decide my vote. Thanks
I was active towards the end of the testnet, and had a witness up with feeds the entire oct5 testnet.

witness spectral (1.6.30)
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?
Does it show up in wallet settings under balance claims?

No

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?
Does it show up in wallet settings under balance claims?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
theoretically it should be able to do so .. the corresponding calls are simply not yet exposed for "easy use" ..

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true

Is that possible in the win lightwallet or OpenLedger?

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]

But my balance does not update?

you should give this command:
Code: [Select]
withdraw_vesting "1.13.52" 97 BTS true
wallet_account_set_approval spartako

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]

But my balance does not update?

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
I was travelling last night and ran out of battery, always happens :)
Witness ready and separate node on 40.127.190.171:1777

Code: [Select]
get_witness betaxtrade
{
  "id": "1.6.39",
  "witness_account": "1.2.6956",
  "last_aslot": 0,
  "signing_key": "BTS6JhLDwYRKSa7FjEmfhy4VHHMn8SZySc8RJrbc5mWyCvERV3coy",
  "vote_id": "1:49",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline ncinic

  • Full Member
  • ***
  • Posts: 67
    • View Profile

Offline noisy

Take a look on: https://bitsharestalk.org/index.php/topic,19625.msg251894.html - I have a crazy idea - lets convince cryptonomex developers to use livecoding.tv

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]
get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]
wallet_account_set_approval spartako

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav


80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged