Delegates, start your engines!

Started by toast, June 09, 2014, 01:54:36 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 2 3 4 5 6 7 8 9 10 11 ... 17
User actions

Xeldal

#200
June 11, 2014, 03:23:56 PM
"blockchain_head_block_num": 4360,
  "blockchain_head_block_time": "20140611T151115",

bitcoinerS

#199
June 11, 2014, 03:21:40 PM
Quote from: emski on June 11, 2014, 03:09:21 PM
My stats:
"blockchain_head_block_num": 5562,
  "blockchain_head_block_time": "20140611T150630",

here is mine..

get_info
{
  "blockchain_head_block_num": 2892,
  "blockchain_head_block_time": "20140611T151500",
>>> approve bitcoiners

emski

#198
June 11, 2014, 03:09:21 PM
My stats:
"blockchain_head_block_num": 5562,
  "blockchain_head_block_time": "20140611T150630",
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

Harvey

#197
June 11, 2014, 02:57:09 PM
Am I still on the main block chain?

harvey (unlocked) >>> get_info
{
  "blockchain_head_block_num": 846,
  "blockchain_head_block_time": "20140611T144330",
  "blockchain_confirmation_requirement": 290,
  "blockchain_average_delegate_participation": 5.7433808553971488,
  "network_num_connections": 1,
  "wallet_unlocked_seconds_remaining": 99999999841,
  "wallet_next_block_production_time": "20140611T145845",
  "wallet_seconds_until_next_block_production": 235,
  "wallet_local_time": "20140611T145450",
  "blockchain_random_seed": "5d454f22e86c8eeb0ac1505e1b70b68351a101ff",
  "blockchain_shares": 9999977806267,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "19880505T134930.027953",
  "wallet_version": 100
}
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:[url="wss://128.199.143.47"]wss://128.199.143.47[/url]:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:[url="ws://128.199.143.47:2018"]ws://128.199.143.47:2018[/url]

sfinder

#196
June 11, 2014, 04:10:47 AM
FYI.
dumpprivkey function does not work. 
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

toast

#195
June 11, 2014, 02:55:10 AM
I filed it, thanks for letting us know
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Xeldal

#194
June 11, 2014, 02:50:46 AM
Quote from: toast on June 11, 2014, 02:35:42 AM
Have you rescanned since the fix?
Rescan and then watch for changes - if it still gets out of sync then file an isse

After
Code Select
Xeldal (unlocked) >>> wallet_rescan_blockchain
Rescanning blockchain...
|----------------------------------------------------------------------------------------------------|
|====================================================================================================|
Scan complete.
OK


I still get
Code Select
Xeldal (unlocked) >>> blockchain_get_account_record_by_id 42
{
  "id": 42,
  "name": "init-delegate-42",
  "public_data": null,
  "owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
...~
    "blocks_produced": 20,
    "blocks_missed": 103,
    "pay_balance": 647337,
 
}
Xeldal (unlocked) >>> wallet_get_account init-delegate-42
{
  "index": 4,
  "id": 42,
  "name": "init-delegate-42",
  "public_data": null,
  "owner_key": "XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit",
...~
    "votes_for": 88888017429,
    "votes_against": 0,
    "blocks_produced": 8,
    "blocks_missed": 25,
    "pay_balance": 76161,



I would file an issue but Im not at all familiar with how that is done.

toast

#193
June 11, 2014, 02:35:42 AM
Quote from: Xeldal on June 11, 2014, 02:29:45 AM
Quote from: toast on June 11, 2014, 01:54:19 AM
Quote from: Xeldal on June 11, 2014, 01:47:18 AM
I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?

Code Select
Xeldal (unlocked) >>> about
{
  "bitshares_toolkit_revision": "26d5341e0fc5bf34971259141bec7e2468b862af",
  "bitshares_toolkit_revision_age": "4 hours ago",
  "fc_revision": "51de9e6abf1bc2fbd31794f7b625d83a82f67d3d",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jun 10 2014 at 18:24:51"
}


Have you rescanned since the fix?
Rescan and then watch for changes - if it still gets out of sync then file an isse
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Xeldal

#192
June 11, 2014, 02:29:45 AM
Quote from: toast on June 11, 2014, 01:54:19 AM
Quote from: Xeldal on June 11, 2014, 01:47:18 AM
I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?

Code Select
Xeldal (unlocked) >>> about
{
  "bitshares_toolkit_revision": "26d5341e0fc5bf34971259141bec7e2468b862af",
  "bitshares_toolkit_revision_age": "4 hours ago",
  "fc_revision": "51de9e6abf1bc2fbd31794f7b625d83a82f67d3d",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jun 10 2014 at 18:24:51"
}

bytemaster

#191
June 11, 2014, 02:01:17 AM
Quote from: denkhaus on June 10, 2014, 06:48:01 PM
Hi,

i wonder why do the net votes for delegates never change? Since some delegates producing blocks without missing a single opportunity, other delegates never produced a block at all.
I had the impression that delegate election is forced by the network itself?

It is because there is almost no transaction volume by regular use.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

toast

#190
June 11, 2014, 01:54:19 AM
Quote from: Xeldal on June 11, 2014, 01:47:18 AM
I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

I thought this was fixed, are you on latest?
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Xeldal

#189
June 11, 2014, 01:47:18 AM
I think its already been said but "wallet_get_account" never seems to update
while "blockchain_get_account_record" and "blockchain_get_account_record_by_id" update just fine.

it looks like all the same data fields only "wallet_get_account" adds:

"index"

"account_address":
  "trust_level"
  "private_data"

wackou

#188
June 10, 2014, 09:30:02 PM
PSA: for people trying to get this to work on debian and getting import errors for keys, make sure that you compile with gcc 4.8, as gcc 4.7 doesn't work (compiles correctly but then crashes randomly or fails importing keys in weird places...)
Please vote for witness wackou! More info at [url="http://digitalgaia.io"]http://digitalgaia.io[/url]

alexxy

#187
June 10, 2014, 07:29:19 PM
Does importing keyhotee works?
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

toast

#186
June 10, 2014, 06:58:03 PM
Quote from: denkhaus on June 10, 2014, 06:48:01 PM
Hi,

i wonder why do the net votes for delegates never change? Since some delegates producing blocks without missing a single opportunity, other delegates never produced a block at all.
I had the impression that delegate election is forced by the network itself?

Eventually it will be done by the client, and will be configurable per-user. There are no fixed blockchain rules.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.
Print
Go Up Pages 1 2 3 4 5 6 7 8 9 10 11 ... 17
User actions