Dry Run 2: The Real Deal

[spartako]

I created some LOVE and voted all delegated not-init

Code: [Select]

wallet_set_delegate_trust_level bitcoiners 5
wallet_set_delegate_trust_level cgafeng 5
wallet_set_delegate_trust_level puppies 5
wallet_set_delegate_trust_level bts101 5


1363.1    2014-06-13T12:51:15 spartako            bts101              some love and votes                     100.000000 LOVE        0.010000 XTS        099ce495
   1363.0    2014-06-13T12:51:15 spartako            bitcoiners          some love and votes                     100.000000 LOVE        0.010000 XTS        05565fb6
   1363.2    2014-06-13T12:51:15 spartako            cgafeng             some love and votes                     100.000000 LOVE        0.010000 XTS        5dc0461f
   1363.3    2014-06-13T12:51:15 spartako            puppies             some love and votes                     100.000000 LOVE        0.010000 XTS        9b4a97ba

Please vote for spartako

[Troglodactyl]

I have one question.

I have latest build (pulled one hour ago from this post time)

I'm seeing following value:
 "blocks_produced": 0

But i see
"last_block_num_produced": 4294967295


So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.



Can someone explain this to me ?

djdexter (unlocked) >>> wallet_get_account djdexter-1
{
  "index": 4,
  "id": 301,
  "name": "djdexter-1",
  "public_data": null,
  "owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
  "active_key_history": [[
      "20140610T232300",
      "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
    ]
  ],
  "delegate_info": {
    "votes_for": 3000000,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140610T232300",
  "last_update": "20140610T232300",
  "meta_data": null,
  "account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
  "trust_level": 0,
  "private_data": null
}

4294967295 is the maximum value for an unsigned (never negative) 32 bit integer, and is not an actual block number that has been created in the chain.  Basically it says that because it was never changed to something legitimate, because you never produced a block.

[betax]

Damm it, off for a week (not checked) and I am not a delegate now . Time to catch up!

[djdexter]

I have one question.

I have latest build (pulled one hour ago from this post time)

I'm seeing following value:
 "blocks_produced": 0

But i see
"last_block_num_produced": 4294967295


So it basically says that there is at least one block produced with following number "4294967295", but it does not count this block on blocks_produced placeholder.



Can someone explain this to me ?

djdexter (unlocked) >>> wallet_get_account djdexter-1
{
  "index": 4,
  "id": 301,
  "name": "djdexter-1",
  "public_data": null,
  "owner_key": "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y",
  "active_key_history": [[
      "20140610T232300",
      "XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y"
    ]
  ],
  "delegate_info": {
    "votes_for": 3000000,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140610T232300",
  "last_update": "20140610T232300",
  "meta_data": null,
  "account_address": "XTSFhKaGFphYT6avaCFWpTVGRVSGhw9r9Pxh",
  "trust_level": 0,
  "private_data": null
}

[djdexter]

Info:
djdexter-1 *                       XTS61oES21C3VkpczAoAZEBWCEF2bPdBGwPSfBupyN34LKmF79y5Y           2014-06-10T23:23:00   0

Physical machine:
Intel i3 (last gen)
8 GB rm
Stable DSL(15 Mbps up/down)
UPS backup
Regular backups / maintenance (system administration)

Virtual machine (only one running)
OS: Ubuntu 14.04
Bitshares_toolkit

-Development/IT background
-Log analysis
-Debugging
-OBDR restore procedures ( one button disaster recovery )


If needed in future i can spin more machines on dedicated systems or cloud.

[BTSdac]

_{roy (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL   
roy001                             XTS7warBpmsDK7zEvEGYCmbdTwn6P9FP8fDQWCLuj3Ay3gBrAXRqw           2014-06-13T11:54:15   0             
"OK"}


I d like to become a delegate ,
could you vote me a delegate ,thank you

CPU :i7-3370K  ; RAM:32GB, netspeed:50M, Shanghai or Qingdao  China ,
I also can hire  a VPS in aliyun

Br

[cgafeng]

Code: [Select]

cgafeng (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL
cgafeng *                          XTS8daF9rX4LiWghT2LbkV1ds2NtiZjEdCiXkkmP6ua3S6s2Vsx8n           2014-06-13T09:28:00   0

I would like to run delegate and register as delegate, can i get vote?

Hardware:
Amazon EC2

Location:
us west

[xeroc]

Strangly my delegate nr 61 is up and running but not producing a block according to  blockchain_get_account_record init-delegate-61

[wackou]

Interestingly I had 4 delegates running (on the same node, same client, same wallet) all of which produced blocks in the SAME fork (I guess) and only one of them made it to this particular genesis.json.

Same issue here, I had delegates 82 -> 85 included, and the new genesis.json only lists 82 and 84 with the correct keys (which are up and running now), but 83 and 85 don't have the same key as before. Not that it matters a lot, if this was done on purpose then don't bother, but maybe something else went wrong? Let us know if we can help in any other way than just having the delegate running.

[networker]

Please add me too if there is a vacancy
networker-01: XTS7hVUNvkxAwspen2XkTwY2sD3JB5g1GhviK5isvXzM6HRVVZ1TA
networker-02: XTS5P8rbowbZaNsmUJ6biWRa2y7qHDHSdEosAN16SyABpfjzyG7qe
networker-03: XTS7ut6vArPQvCzb4xNVxHuuQCnwxL9aZGSNwwJsnDYo5MRnbA6Ja
networker-04: XTS8dN5PS1abbWDC5kRoVveiGrjVJCV1ByC6LUahbwyZ8qetTpepY
networker-05: XTS5MYSmHzern8b6TMS42N2BB3cPCkHg9RxC5ogeiBseqGoYnhVDB
Name:
Location: GuangDong, China

Hardware:
Intel  i7 3770k
4 GB ddr3 1600mhz ram
500GB HD


Software:

OS Ubuntu server 14.04  64bit

[sfinder]

 

[spartako]

init-delegate-21,init-delegate-22,init-delegate-23,init-delegate-24 are working.

I have also created a new delegate spartako, and tried to vote for other non-init delegates (bitcoiners and bts101) but I see only bitcoiners with some votes and bts101 remains at zero votes.

[xeroc]

Note that we removed some delegates for this round due to inactivity (or rather, inactivity as seen on our fork).
You can check if yours were the ones we removed here:
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json

Interestingly I had 4 delegates running (on the same node, same client, same wallet) all of which produced blocks in the SAME fork (I guess) and only one of them made it to this particular genesis.json. How can it be that one delegate is accepted for producing block in the 'main fork' while the others are not? Only thing I can think about is that a fork started with one of my delegates?!

Delegates in question:
init-delegate-58
init-delegate-59
init-delegate-60
init-delegate-61 (up, running and producing blocks)

[welk1n]

Am I on the main chain?

Code: [Select]

welk1n (unlocked) >>> wallet_list_receive_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL   
welk1n-d-5                         XTS6z7aMnBmXi7qL9uHfgWS6d1wedEpvQNTrwgeGb8h1MH9WVXtRC           NO                    0             
init-delegate-33 *                 XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA           2014-06-01T00:00:00   0             
init-delegate-32 *                 XTS7p56UNQLyWc3NB2yeT4VVtYhanf6wFC356c6vbfpvQ9CHUmg6X           2014-06-01T00:00:00   0             
init-delegate-31 *                 XTS5urryfpdjZgwavKwufJ9A1d816LFaPbSQLu5eP2G76B7hbtuxj           2014-06-01T00:00:00   0             
init-delegate-30 *                 XTS6f8fzmUDQp63nTYgsA2GQtvFoPvKrmTmuhkCvQUCnKUJwxTxtx           2014-06-01T00:00:00   0             
"OK"
welk1n (unlocked) >>> info
{
  "blockchain_head_block_num": 452,
  "blockchain_head_block_time": "20140613T060600",
  "blockchain_confirmation_requirement": 290,
  "blockchain_average_delegate_participation": 27.713059472716125,
  "network_num_connections": 7,
  "wallet_unlocked_seconds_remaining": 997346,
  "wallet_next_block_production_time": "20140613T060700",
  "wallet_seconds_until_next_block_production": 52,
  "wallet_local_time": "20140613T060608",
  "blockchain_random_seed": "32fa7e7088b6984898073462f227a7e24c9e5630",
  "blockchain_shares": 9999980679465,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T190834",
  "wallet_version": 100
}


[bitcoinerS]

I just added an RPC call: wallet_account_export_private_key   that will give you the key you want.  Simply import that key into your other wallet.

Ok. Thanks. Done. Please enable (vote for) this delegate (bitcoiners)