Show Posts

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.


Messages - spartako

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 27
31
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 14, 2015, 12:32:24 pm »


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

32
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 14, 2015, 08:47:12 am »


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"
      }
    ]
  }
]

33
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 13, 2015, 06:01:43 pm »
Plese vote for spartako, I'm in the active witness list but I have 0 votes  ???

I just voted for all witness that are here

Edit: Now I have votes, thanks!

34
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 13, 2015, 04:57:02 pm »
spartako (1.6.15) up ready for producing blocks

Code: [Select]
get_witness spartako
{
  "id": "1.6.15",
  "witness_account": "1.2.333",
  "last_aslot": 0,
  "signing_key": "BTS7qFryjVpfkndAW4siraK1dV4f8gGxRsgnry7ErPFRjirdwVJEG",
  "vote_id": "1:25",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

35
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 13, 2015, 03:57:39 pm »
compiling...

36
Technical Support / Re: Request: Standalone Webwallet
« on: October 13, 2015, 03:27:40 pm »
  +5%

37
General Discussion / Re: The Final Countdown!
« on: October 13, 2015, 12:55:35 pm »
 +5%

38
We are already using the telegram group and it working quite well for coordination, so I prefer using telegram instead skype

39
General Discussion / Re: Graphene GUI testing and feedback
« on: October 11, 2015, 02:58:47 pm »
How do you close a 'usd-collateral-holder' position?

When I 'Update Position' and 'Collateral change   -424.46933 CORE' the CORE asset is displayed in the 'usd-collateral-holder' balance

Then when I try to transfer the 'CORE' to my account name, the GUI says 'usd-collateral-holder' is 'Not your account'

Also, all my collateral-holders Memo Keys says 'Not a valid public key'

Same problem here

40
General Discussion / Re: October 5 Test Network
« on: October 11, 2015, 02:01:11 am »
spartako_bot went in a minor fork and started to notify false alarm to witnesses (spartako witness producer was in the main fork and didn't missed any blocks), this is the error that I found:

Code: [Select]
2606729ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 0002315c15ad904d17192c8080121ba774c1a962, 143708
2606729ms th_a       fork_database.cpp:58          push_block           ] Head: 143799, 000231b77729fe84f473d51aabdbf31e530d1b82
2606730ms th_a       application.cpp:429           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:78 _push_block

    {"new_block":{"previous":"0002315b615b561c0ea5eab6aa74aee790f5de0c","timestamp":"2015-10-11T00:28:30","witness":"1.6.11","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6551667be1ad32fe674e9f4df852f0afe69450ccb396036026e97f468de4af7d1d0613c69ef2d9d35125e7a2bd7098dbc2fa1d44dff9aaa20a6a2cfa04fa5d2f","transactions":[]}}
    th_a  db_block.cpp:197 _push_block


Tomorrow I will change the code of spartako_bot adding a backup nodes list for prevent this type of problems.

41
Technical Support / Re: [Python] Price Feed Script for BitShares 2.0
« on: October 10, 2015, 04:58:51 pm »
 thanks!!
+5%

42
General Discussion / Re: October 5 Test Network
« on: October 10, 2015, 03:33:55 pm »
I update my observer node to the latest master I was not able to publish the feed for SILVER.
I got a strange error that you can find here:

https://github.com/cryptonomex/graphene/issues/371

Thanks to bitcube that helped me on telegram (thanks a lot!!!) I switched to a previous commit e68e99ed3ae11ddac607e983e7549e8278fdecc4 and I was able to broadcast the tx but my witness producer started to missing blocks.

So I suspect that if some witness producer update to latest master risk going into a fork.

43
General Discussion / Re: October 5 Test Network
« on: October 09, 2015, 10:40:47 am »
Many delegates went in a big minor fork (~35% partecipations) and also spartako and spartako_bot

I removed the blockchain and resynced with the main chain using this seed node:
188.165.233.53:1777

This is the error then I found:
Code: [Select]
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:78 _push_block

    {"new_block":{"previous":"00018aeac52ac578eead894ddaefb832bab051d0","timestamp":"2015-10-09T10:10:21","witness":"1.6.19","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6a191cc3c9f8ea6d06f1e3546931a35873961b0b0defe5689a35de504c448ddc3818793a52abbe65da08faa70b5700df2c13088629dd9c1c43a13a2f3ac9fc8c","transactions":[]}}
    th_a  db_block.cpp:197 _push_block
901261ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 00018aec0d81d4f086eaffcecc9a028749483c49, 101100
901262ms th_a       fork_database.cpp:58          push_block           ] Head: 101115, 00018afb2ccf99a7986cf678b67613061ba56d0f
901262ms th_a       application.cpp:429           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}

44
General Discussion / Re: October 5 Test Network
« on: October 09, 2015, 09:57:35 am »
Could someone send some large amount of CORE to dummy9?
I guess this account is used to send the initial 1000 CORE to newly registered users and now it stopped doing that as it has no CORE.
I just sent 100K to dummy9

45
General Discussion / Re: October 5 Test Network
« on: October 09, 2015, 07:33:58 am »
It didn't work for me. I had to choose another peer node to sync from, I guess the seed node is not on the latest master yet maybe.

mindphlux.witness is back up & on the latest master.

I helped mindphlux searching a new seed node in my logs, I tried the network_get_connected_peers command but give me a permission error probably because it is a restricted API (I will try to specify apiaccess file in config.ini)

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 27