BitShares Forum

Main => General Discussion => Topic started by: toast on June 20, 2014, 12:26:19 am

Title: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 12:26:19 am
In this dry run, all initial delegates start with tons of downvotes. This means any new delegate is automatically ahead of all the initial delegates.

We will start a new thread for when we have the GUI ready for everyone to properly start delegate campaigns. This is a good chance to start positioning yourselves to succeed in the scramble for delegate positions when we launch the real thing. Enterprising technical users might start figuring out how to offer their services to non-technical users.

Let's begin!

* Step 1 **REQUIRED**: Open this in another tab   https://www.youtube.com/watch?v=Z-TOHc7I1pc

* Step 2: Wipe all your old data-dirs. Note that you might have both  ~/.BitSharesXTS  and  ~/BitShares\ XTS  - kill them all.

* Step 3: Pull latest and build.

* Optional Step 4:  If you are an initial delegate and a good citizen, do what you did before (import old private keys, make sure to wallet_enable_delegate_block_production). Details are sparse on purpose, since you probably want to skip this and go straight to 5.

* Step 5: Follow this guide: https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-Registering-Names-And-Delegates

You will notice that you need funds to register your name / register as delegate. You have two options:
* import a key with funds
* ask someone nicely

This is the tech support thread. We'll open another related to delegate campaigns in the next day or two.

Edit: Blocks will be reaaaal slow near the start. Initial delegates, get online!
Title: Re: Dry Run 3: A Game of Delegates
Post by: alt on June 20, 2014, 12:34:51 am
So I should register a new delegate without use the init delgate?
who can send me some XTS to register a new delegate please...
my account is delegate-alt
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 12:36:27 am
So I should register a new delegate without use the init delgate?
who can send me some XTS to register a new delegate please...

Your delegates were already producing blocks.. You produced blocks 2-4... O.o
Check your get_info

edit: yes you are in genesis block with old keys
Title: Re: Dry Run 3: A Game of Delegates
Post by: alt on June 20, 2014, 12:40:25 am
So I should register a new delegate without use the init delgate?
who can send me some XTS to register a new delegate please...

Your delegates were already producing blocks.. You produced blocks 2-4... O.o
Check your get_info

edit: yes you are in genesis block with old keys
but as what you said, my  votes is -1%,  I should register a new one to win the vote right?
Title: Re: Dry Run 3: A Game of Delegates
Post by: alt on June 20, 2014, 12:43:57 am
should pull branch master or dryrun3?
Title: Re: Dry Run 3: A Game of Delegates
Post by: zhangweis on June 20, 2014, 12:44:03 am
I need some fund to register delegate.

Can someone send me some fund? Thanks.

my address is XTS85s81zMdkgEuQRySuRWDWcWRoqzHv1qnssG6mAtRb1SGMmFGHN
Title: Re: Dry Run 3: A Game of Delegates
Post by: zhangweis on June 20, 2014, 12:47:54 am
I've imported the delegate keys and unlocked the wallet but wallet_next_block_production_time is null.

Anything I need to do?

default (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL   
unelected-btszhangwei2 *           XTS6yyGEujvofqgQRfwvwWxMjZiFJwE4kBE1BpXtGpmhZ8aC58Dmb           2014-06-01T00:00:00   0         
unelected-btsjohn2 *               XTS7kcfTvho6h7juwajcNxBQA9rmiqd5iSFMZYywwbWRk9wqjo2Np           2014-06-01T00:00:00   0         
unelected-btszhangweis *           XTS7CoMc1xHodpiVYS8gukQRhmrpxaBEz7oMaUy434HBLbJegtFo1           2014-06-01T00:00:00   0         
unelected-btsjohn *                XTS6sSu1DhZUxpnoLz1wYvwsowUQpa4zyHFkqo972fKnU6xrEKVx8           2014-06-01T00:00:00   0         
btsjohn                            XTS85s81zMdkgEuQRySuRWDWcWRoqzHv1qnssG6mAtRb1SGMmFGHN           NO                    0         
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 10,
  "blockchain_head_block_time": "20140620T004300",
  "blockchain_head_block_time_rel": "3 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 10.1010101010101,
  "network_num_connections": 4,
  "ntp_time": "20140620T004615.160231",
  "ntp_error_seconds": -0.023188,
  "wallet_unlocked_seconds_remaining": 99999813,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140620T004615",
  "blockchain_random_seed": "a4636e0bfcdfdda1c5222c6569ece324a37c4d74",
  "blockchain_shares": 9999957995000,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20170820T102948",
  "wallet_version": 100
}
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 12:48:55 am
So I should register a new delegate without use the init delgate?
who can send me some XTS to register a new delegate please...

Your delegates were already producing blocks.. You produced blocks 2-4... O.o
Check your get_info

edit: yes you are in genesis block with old keys
but as what you said, my  votes is -1%,  I should register a new one to win the vote right?

You're still in top 101! ;)

Yes, you should make a new delegate if you want to ensure you stay in once lots more people make delegates
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 12:49:15 am
I've imported the delegate keys and unlocked the wallet but wallet_next_block_production_time is null.

Anything I need to do?

wallet_enable_delegate_block_production true
Title: Re: Dry Run 3: A Game of Delegates
Post by: zhangweis on June 20, 2014, 12:54:50 am
I've imported the delegate keys and unlocked the wallet but wallet_next_block_production_time is null.

Anything I need to do?

wallet_enable_delegate_block_production true

Thanks it works. BTW, it should be
wallet_enable_delegate_block_production <delegate name> true
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 01:08:10 am
should pull branch master or dryrun3?

master
Title: Re: Dry Run 3: A Game of Delegates
Post by: cgafeng on June 20, 2014, 01:23:09 am
Code: [Select]
  "network_num_connections": 7,
  "ntp_time": null,
  "wallet_unlocked_seconds_remaining": 999643,

the ntp_time is null, need to make it valid?
And how?
i run on windows7.
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 01:32:47 am
Did the cost to register a delegate double in this dry run?
Title: Re: Dry Run 3: A Game of Delegates
Post by: alt on June 20, 2014, 01:40:57 am
I have register 2 account with the same name alt?
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 01:45:06 am
I have register 2 account with the same name alt?

I only see one in blockchain so nobody validated it... did the wallet allow you to create the transaction and show it in your history?
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 01:47:55 am
I have register 2 account with the same name alt?

I only see one in blockchain so nobody validated it... did the wallet allow you to create the transaction and show it in your history?

Actually I see both in the chain DB but they are the same account... filing an issue
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 01:48:22 am
How many block confirmations are required for a delegate registration to be confirmed?

Should be just 1, but there is some trouble propogating transactions it seems. Will definitely be confirmed when seen node delegate confirms it
Title: Re: Dry Run 3: A Game of Delegates
Post by: alt on June 20, 2014, 01:54:03 am
1.  I register alt, it's pending long time
2.  I register again. wrong msg like " this key already in use ..."
3. I change account name from alt to other
4. I register alt again, it's still pending.
afeter a while, when I see agin, 2 alt in the delegate list

Code: [Select]
(wallet closed) >>> blockchain_get_account_record_by_id 314
Record for 'alt' -- Registered on 2014-Jun-20 01:36:30, last update was 14 minutes ago
Owner's key: XTS5BiobWRQUk2X8YEBLCcXvDHE9Nhs5WDhPasqUM95t21hm46KRu
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
0%                  0%                  0%                  0               0               4294967295      0.000000 XTS
(wallet closed) >>> blockchain_get_account_record_by_id 315
Record for 'alt' -- Registered on 2014-Jun-20 01:36:30, last update was 14 minutes ago
Owner's key: XTS5ffw8Xeoh2huecLD3L4rppvpBeoBekNSkyG2ivR1LiwsZKr1um
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
0%                  0%                  0%                  0               0               4294967295      0.000000 XTS
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 02:00:19 am
registered a new account, registered as delegate 'xeldal'
I was able to import pts wallets bitcoin private keys but I'm unable to import an electrum wallet file.

wallet_import_electrum "/root/Imports/default-wallet" "walletPassWord" "xeldal"

I'm unsure of the file type if i need one for the "default-wallet" from electrum

does anyone know more about this?

Code: [Select]
xeldal-w (unlocked) >>> wallet_import_electrum "/root/Imports/wallet-elec" "passWoRd" xeldal
4 parse_error_exception: Parse Error
failed to parse electrum wallet
    {}
    th_a  electrum.cpp:232 electrumwallet

    {}
    th_a  electrum.cpp:273 import_electrum_wallet
error importing bitcoin wallet /root/Imports/wallet-elec
    {"wallet_dat":"/root/Imports/wallet-elec","account_name":"xeldal"}
    th_a  wallet.cpp:2637 import_electrum_wallet

    {}
    th_a  common_api_client.cpp:332 wallet_import_electrum

    {"command":"wallet_import_electrum"}
    th_a  cli.cpp:529 execute_command
Title: Re: Dry Run 3: A Game of Delegates
Post by: welk1n on June 20, 2014, 02:00:36 am
Code: [Select]
well (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_time": "20140620T015641",
  "blockchain_head_block_time_rel": "0 second old",
  "blockchain_confirmation_requirement": 202,
  "blockchain_average_delegate_participation": 0,
  "network_num_connections": 0,
  "ntp_time": "20140620T015641.483649",
  "ntp_error_seconds": -0.076316999999999996,
  "wallet_unlocked_seconds_remaining": 9999553,
  "wallet_next_block_production_time": "20140620T015800",
  "wallet_seconds_until_next_block_production": 79,
  "wallet_local_time": "20140620T015641",
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 9999999984056,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20141013T193554",
  "wallet_version": 100
}


The same issue occurred on my server.
Can anyone use the network_get_peer_info command , and give me an available node.
I should manually to add the available node.
Title: Re: Dry Run 3: A Game of Delegates
Post by: yinchanggong on June 20, 2014, 02:02:34 am

This is the tech support thread. We'll open another related to delegate campaigns in the next day or two.

Edit: Blocks will be reaaaal slow near the start. Initial delegates, get online!
Does this mean that the GUI will be ready in the weekend?

来自我的 M353 上的 Tapatalk

Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 02:37:28 am
I've got a seed node up at 95.85.33.16:8764
Code: [Select]
well (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_time": "20140620T015641",
  "blockchain_head_block_time_rel": "0 second old",
  "blockchain_confirmation_requirement": 202,
  "blockchain_average_delegate_participation": 0,
  "network_num_connections": 0,
  "ntp_time": "20140620T015641.483649",
  "ntp_error_seconds": -0.076316999999999996,
  "wallet_unlocked_seconds_remaining": 9999553,
  "wallet_next_block_production_time": "20140620T015800",
  "wallet_seconds_until_next_block_production": 79,
  "wallet_local_time": "20140620T015641",
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 9999999984056,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20141013T193554",
  "wallet_version": 100
}


The same issue occurred on my server.
Can anyone use the network_get_peer_info command , and give me an available node.
I should manually to add the available node.
Title: Re: Dry Run 3: A Game of Delegates
Post by: crazybit on June 20, 2014, 02:44:13 am
a bit confusion, why the standby delegate can generate the block?
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:45:08 am
a bit confusion, why the standby delegate can generate the block?

Where did you see this?
Title: Re: Dry Run 3: A Game of Delegates
Post by: cgafeng on June 20, 2014, 02:46:58 am
blockchain_list_delegates

Code: [Select]
** Standby:
59          unelected-delegate-northamerica10                   104274678792        -1.042808056 %      0               4
28          delegate-alt             6927                104666022311        -1.046721697 %      3               1
3           unelected-investor       0                   105174557291        -1.051807404 %      0               4
42          unelected-xeldal-4       9074                105197805022        -1.052039742 %      2               2
23          unelected-spartako-delegate-30                   105539117380        -1.055453181 %      0               4
41          crazybit                 9215                106210341099        -1.062165737 %      2               2
66          unelected-testz1         0                   106224251086        -1.062304974 %      0               4
12          unelected-btszhangwei2   10364               107577021064        -1.075833321 %      3               1
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:52:26 am
blockchain_list_delegates

Code: [Select]
** Standby:
59          unelected-delegate-northamerica10                   104274678792        -1.042808056 %      0               4
28          delegate-alt             6927                104666022311        -1.046721697 %      3               1
3           unelected-investor       0                   105174557291        -1.051807404 %      0               4
42          unelected-xeldal-4       9074                105197805022        -1.052039742 %      2               2
23          unelected-spartako-delegate-30                   105539117380        -1.055453181 %      0               4
41          crazybit                 9215                106210341099        -1.062165737 %      2               2
66          unelected-testz1         0                   106224251086        -1.062304974 %      0               4
12          unelected-btszhangwei2   10364               107577021064        -1.075833321 %      3               1

Right... where do you see that they are producing blocks while on standby? Those are just their history
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 02:52:43 am
a bit confusion, why the standby delegate can generate the block?

Where did you see this?

My standby delegate unelected-puppies4 is still creating blocks. Just generated block 92.
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:55:21 am
a bit confusion, why the standby delegate can generate the block?

Where did you see this?

My standby delegate unelected-puppies4 is still creating blocks. Just generated block 92.

The list is a bit misleading as it shows the delegates for the *next* round. Since we are not to block 101 yet this means that your "standby" is still in active list.

We will change the labels to be more clear.
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 02:56:46 am
Ah.   Thanks for clearing that up.   Makes sense now.   I was wondering why no real delegates had produced a block yet.

Sent from my SCH-I535 using Tapatalk

Title: Re: Dry Run 3: A Game of Delegates
Post by: HackFisher on June 20, 2014, 03:02:30 am
blockchain_list_delegates

Code: [Select]
** Standby:
59          unelected-delegate-northamerica10                   104274678792        -1.042808056 %      0               4
28          delegate-alt             6927                104666022311        -1.046721697 %      3               1
3           unelected-investor       0                   105174557291        -1.051807404 %      0               4
42          unelected-xeldal-4       9074                105197805022        -1.052039742 %      2               2
23          unelected-spartako-delegate-30                   105539117380        -1.055453181 %      0               4
41          crazybit                 9215                106210341099        -1.062165737 %      2               2
66          unelected-testz1         0                   106224251086        -1.062304974 %      0               4
12          unelected-btszhangwei2   10364               107577021064        -1.075833321 %      3               1

Right... where do you see that they are producing blocks while on standby? Those are just their history

This is some issue on CLI, just reported:
https://github.com/BitShares/bitshares_toolkit/issues/360 (https://github.com/BitShares/bitshares_toolkit/issues/360)
Title: Re: Dry Run 3: A Game of Delegates
Post by: Harvey on June 20, 2014, 03:16:39 am
Night gathers, and now my watch begins.
-Jon Snow

 +5%
Title: Re: Dry Run 3: A Game of Delegates
Post by: sfinder on June 20, 2014, 03:40:44 am

how can i transfer xts to following un- registered  account "sexy"?
wallet_transfer 100 XTS pan2pan-05 XTS59v2BLFU2uSS7dy63Aaaz89rs6PhunrFZwg2VioqoEGAHATKfG "hello qqqq"

Code: [Select]

wallet_account_list_public_keys sexy
[{
    "hex": "02230668a3b8030189007da49a5dff6b96cb9d59471ec5a789fcad29f9371ea3c0",
    "native_pubkey": "XTS59v2BLFU2uSS7dy63Aaaz89rs6PhunrFZwg2VioqoEGAHATKfG",
    "native_address": "XTSEbfsfQ8CyCNiq8NRpF2NB4hY2zhKs5iuj",
    "pts_normal_address": "Pq2mGxbEkWFLQxDnrbdLPEpusDNRDDkpoC",
    "pts_compressed_address": "PZC4T568ev8XQSNpZYV55oMPV82axvYRfh",
    "btc_normal_address": "1J6z8su6zQJGcgQwV6yVEDarcxwbQQH4fR",
    "btc_compressed_address": "12GHJzPztpBTcAZyC3qDvn7LEsbm6Gvn2p"
  }

Code: [Select]
wallet_transfer 100 XTS pan2pan-05 XTS59v2BLFU2uSS7dy63Aaaz89rs6PhunrFZwg2VioqoEGAHATKfG "hello qqqq"
10 assert_exception: Assert Exception
is_valid_account_name( account_name ):
    {}
    th_a  wallet.cpp:2780 is_valid_account

    {"real_amount_to_transfer":100,"amount_to_transfer_symbol":"XTS","from_account_name":"pan2pan-05","to_account_name":"XTS59v2BLFU2uSS7dy63Aaaz89rs6PhunrFZwg2VioqoEGAHATKfG","memo_message":"hello qqqq"}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command


Code: [Select]

wallet_account_list_public_keys sexy
[{
    "hex": "02230668a3b8030189007da49a5dff6b96cb9d59471ec5a789fcad29f9371ea3c0",
    "native_pubkey": "XTS59v2BLFU2uSS7dy63Aaaz89rs6PhunrFZwg2VioqoEGAHATKfG",
    "native_address": "XTSEbfsfQ8CyCNiq8NRpF2NB4hY2zhKs5iuj",
    "pts_normal_address": "Pq2mGxbEkWFLQxDnrbdLPEpusDNRDDkpoC",
    "pts_compressed_address": "PZC4T568ev8XQSNpZYV55oMPV82axvYRfh",
    "btc_normal_address": "1J6z8su6zQJGcgQwV6yVEDarcxwbQQH4fR",
    "btc_compressed_address": "12GHJzPztpBTcAZyC3qDvn7LEsbm6Gvn2p"
  }
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 03:44:02 am
Do it by name?
If they are on same wallet just use name locally.
If they are different wallets then you need to make contact account wallet you are sending from with key of local account int wallet who is receiving.
Title: Re: Dry Run 3: A Game of Delegates
Post by: sfinder on June 20, 2014, 04:07:03 am
Do it by name?
If they are on same wallet just use name locally.
If they are different wallets then you need to make contact account wallet you are sending from with key of local account int wallet who is receiving.

got it . thanks
Title: Re: Dry Run 3: A Game of Delegates
Post by: sfinder on June 20, 2014, 04:15:13 am
it cost me 20.981502 XTS to be a delegate.....  tooooooo    expensive .....................

Quote
BLK    .TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 193.0    2014-06-20T04:06:00 sexy                sexy                update sexy as a delegate                  0.000000 XTS       20.981502 XTS        0f14b5ed
Title: Re: Dry Run 3: A Game of Delegates
Post by: alexxy on June 20, 2014, 04:52:03 am
I cannot import my keyhotee id

Code: [Select]

account_name == registered_account->name: Attempt to import a private key belonging to another account
    {"account_with_key":"unelected-alexxy","account_name":"alexxy"}
    th_a  wallet.cpp:1068 import_private_key

seems problem is that there is 2 accounts with same key

Code: [Select]
alexxy (unlocked) >>> blockchain_get_account_record alexxy
Record for 'alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
This account is not a delegate.
alexxy (unlocked) >>> blockchain_get_account_record unelected-alexxy
Record for 'unelected-alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
-0.0068075%         1.08177718%         -1.0885847%         0               4               4294967295      0.000000 XTS
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 04:55:24 am
I cannot import my keyhotee id

Code: [Select]

account_name == registered_account->name: Attempt to import a private key belonging to another account
    {"account_with_key":"unelected-alexxy","account_name":"alexxy"}
    th_a  wallet.cpp:1068 import_private_key

seems problem is that there is 2 accounts with same key

Code: [Select]
alexxy (unlocked) >>> blockchain_get_account_record alexxy
Record for 'alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
This account is not a delegate.
alexxy (unlocked) >>> blockchain_get_account_record unelected-alexxy
Record for 'unelected-alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
-0.0068075%         1.08177718%         -1.0885847%         0               4               4294967295      0.000000 XTS

Whoops, my bad. Should check for dupes in keyhotee list before making initial delegates.
Title: Re: Dry Run 3: A Game of Delegates
Post by: alexxy on June 20, 2014, 04:57:15 am
Whoops, my bad. Should check for dupes in keyhotee list before making initial delegates.

So effectevely this account is unreachable on dry run 3?
Title: Re: Dry Run 3: A Game of Delegates
Post by: bitcoinerS on June 20, 2014, 04:57:52 am
Ok. My delegate is up and running. (unelected-bitcoiners)

Code: [Select]
blockchain_get_account_record unelected-bitcoiners
Record for 'unelected-bitcoiners' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
0.07001704%         1.10094467%         -1.0309276%         0               4               4294967295      0.000000 XTS

Still it has not produced any blocks yet. Maybe it needs more votes.

Please vote for bitcoiners!

Code: [Select]
>>> blockchain_list_delegates
..
** Standby:
..
58          unelected-bitcoiners     7187180011          110083397524        -1.029067755 %      0               4               


Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 05:03:10 am
^^ you can make a new delegate and get in top 101 pretty easily. unelected-bitcoinerS is not getting in any time soon with all the initial downvotes
Title: Re: Dry Run 3: A Game of Delegates
Post by: sfinder on June 20, 2014, 05:32:55 am
^^ you can make a new delegate and get in top 101 pretty easily. unelected-bitcoinerS is not getting in any time soon with all the initial downvotes
it is too expensive to be a delegate around 21 XTS.   
Title: Re: Dry Run 3: A Game of Delegates
Post by: xeroc on June 20, 2014, 05:41:10 am
I am going to miss today as I am on holiday .. delegates will be up tomorrow
Title: Re: Dry Run 3: A Game of Delegates
Post by: bitcoinerS on June 20, 2014, 06:12:34 am
Hopefully this truly is a dry run and no real shares are lost, as I may have just deleted a wallet that I did not back up.
Title: Re: Dry Run 3: A Game of Delegates
Post by: emski on June 20, 2014, 06:38:45 am
I've noticed that i cant wallet_enable_delegate_producing_blocks right after I register the account as delegate.
And it takes more than 2 blocks for newly registered delegate to be marked as a delegate in wallet_list_accounts.
Is this expected ?

PS: After few minutes it is ok however several blocks were created in the meantime
Title: Re: Dry Run 3: A Game of Delegates
Post by: emski on June 20, 2014, 06:52:18 am
There are delegates with negative "VOTES FOR".
66          unelected-testz1         -885053986          106224251086        -1.071245313 %      0               4

Some of the initial delegates lack unelected prefix.
41          crazybit                 9215                106210341099        -1.06225431 %       2               2
40          coolspeed                0                   109830374550        -1.09845984 %       0               4
28          delegate-alt             6927                104666022311        -1.046808958 %      3               1
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json
Title: Re: Dry Run 3: A Game of Delegates
Post by: crazybit on June 20, 2014, 07:17:26 am
There are delegates with negative "VOTES FOR".
66          unelected-testz1         -885053986          106224251086        -1.071245313 %      0               4

Some of the initial delegates lack unelected prefix.
41          crazybit                 9215                106210341099        -1.06225431 %       2               2
40          coolspeed                0                   109830374550        -1.09845984 %       0               4
28          delegate-alt             6927                104666022311        -1.046808958 %      3               1
https://raw.githubusercontent.com/BitShares/bitshares_toolkit/master/libraries/blockchain/genesis.json

my delegate got 106210341099 against votes in genesis block and drop into inactive list now :'(
Title: Re: Dry Run 3: A Game of Delegates
Post by: xeroc on June 20, 2014, 07:29:16 am
That is expected behaviour! Read OP
Title: Re: Dry Run 3: A Game of Delegates
Post by: xeroc on June 20, 2014, 07:35:48 am
I cannot import my keyhotee id

Code: [Select]

account_name == registered_account->name: Attempt to import a private key belonging to another account
    {"account_with_key":"unelected-alexxy","account_name":"alexxy"}
    th_a  wallet.cpp:1068 import_private_key

seems problem is that there is 2 accounts with same key

Code: [Select]
alexxy (unlocked) >>> blockchain_get_account_record alexxy
Record for 'alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
This account is not a delegate.
alexxy (unlocked) >>> blockchain_get_account_record unelected-alexxy
Record for 'unelected-alexxy' -- Registered on 2014-Jun-01 00:00:00, last update was 19 days ago
Owner's key: XTS6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEgnEm5N
VOTES FOR           VOTES AGAINST       NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   LAST BLOCK #    TOTAL PAY           
--------------------------------------------------------------------------------------------------------------------------------
-0.0068075%         1.08177718%         -1.0885847%         0               4               4294967295      0.000000 XTS

Whoops, my bad. Should check for dupes in keyhotee list before making initial delegates.
thats why i reminded you that xeroc is a registered delegate from a keyhotte id .. it seems you change the name of my keyhotee id .. need to check though
Title: Re: Dry Run 3: A Game of Delegates
Post by: betax on June 20, 2014, 08:36:43 am
"hi how long does it take to register a delegate? I have registered mine a 15 minutes ago and still pending."

I'm registered now.

Title: Re: Dry Run 3: A Game of Delegates
Post by: laow on June 20, 2014, 08:55:08 am
I use  "wallet_account_update_registration" to update one of my accounts as delegate, it cost me 20 xts. 
Before the transaction is confirmed(the account became a delegate), I type the same command many times.
I can see form "wallet_account_transaction_history",  there are many pending 20 xts transaction and my balance is reduce.
I only need to pay 20 xts once to become a delegate.  How can I get my pending xts back?

"wallet_account_register" seems have the same problem.
Title: Re: Dry Run 3: A Game of Delegates
Post by: muse-umum on June 20, 2014, 09:14:40 am
Could anyone please explain the relationship between 'vote' and 'transfer' ?  In order to 'vote',  do I have to 'transfer' ? Any documents ?


Edit: I found some article here : https://github.com/BitShares/bitshares_toolkit/wiki/AYNTK_Voting Thanks for xeroc
Title: Re: Dry Run 3: A Game of Delegates
Post by: wackou on June 20, 2014, 09:16:05 am
Could someone send me ~21XTS to register a new delegate? Thanks!  :D

send to "wackou" (registered on the blockchain as XTS8SCY7ZFAK72uL1jQjWtchDRvf3nz1m7rkDeEn818WRdZiqEo5f)

btw, I successfully imported my keyhotee founder account/key (great!), however there are no funds associated with it. I thought there would be one day of AGS (and hence some BTS) for keyhotee founders, or did I miss something?
Title: Re: Dry Run 3: A Game of Delegates
Post by: spartako on June 20, 2014, 09:38:12 am
I wake up early morning for the test, I registered spartako but my transactions was pending for long time and I believed I was in a fork....so then I have done a BIG mistake and removed all my BitSharesXTS directory without saving my private key :( (I was actually sleeping...)
Then I realized that I was in the good chain and now spartako is lost....I registered a new account spartako-delegate and voted against spartako.

So please vote AGAINST spartako and vote FOR spartako-delegate.
Free LOVE for everyone vote for spartako-delegate ;)
Title: Re: Dry Run 3: A Game of Delegates
Post by: betax on June 20, 2014, 10:37:45 am
I wake up early morning for the test, I registered spartako but my transactions was pending for long time and I believed I was in a fork....so then I have done a BIG mistake and removed all my BitSharesXTS directory without saving my private key :( (I was actually sleeping...)
Then I realized that I was in the good chain and now spartako is lost....I registered a new account spartako-delegate and voted against spartako.

So please vote AGAINST spartako and vote FOR spartako-delegate.
Free LOVE for everyone vote for spartako-delegate ;)

Just seen you are at the top again, did you recover your XTS?
Title: Re: Dry Run 3: A Game of Delegates
Post by: spartako on June 20, 2014, 10:45:06 am

Just seen you are at the top again, did you recover your XTS?

No I can't recover no more my XTS, I think the only way to remove spartako from the delegate list is a lot of people voting against him.
Title: Re: Dry Run 3: A Game of Delegates
Post by: bdnoble on June 20, 2014, 11:54:33 am

I wake up early morning for the test, I registered spartako but my transactions was pending for long time and I believed I was in a fork....so then I have done a BIG mistake and removed all my BitSharesXTS directory without saving my private key :( (I was actually sleeping...)
Then I realized that I was in the good chain and now spartako is lost....I registered a new account spartako-delegate and voted against spartako.

So please vote AGAINST spartako and vote FOR spartako-delegate.
Free LOVE for everyone vote for spartako-delegate ;)

Add me to the list of people who deleted a wallet and lost the keys. :P bdnoble-1 is no good but I think bdnoble is working. :)

Good thing this is a test run. I think we were all a little too excited.


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 3: A Game of Delegates
Post by: wackou on June 20, 2014, 12:05:42 pm
Thanks for the XTS and the LOVE!

also set wallet_set_delegate_trust_level spartako -1  and  wallet_set_delegate_trust_level spartako-delegate 1

please also wallet_set_delegate_trust_level wackou 1 ;)
Title: Re: Dry Run 3: A Game of Delegates
Post by: boombastic on June 20, 2014, 12:19:15 pm
Does delegate requires wallet unlocked to perform duty?

Answer to my own question: yes, wallet needs to be unlocked

Code: [Select]
10 assert_exception: Assert Exception
_wallet->is_unlocked(): Wallet must be unlocked to produce blocks
Title: Re: Dry Run 3: A Game of Delegates
Post by: bytemaster on June 20, 2014, 01:24:14 pm
Great work everyone.  I am working to improve handling of pending transactions with the goal of providing better diagnostics about why they are pending. 

Sorry to hear about the delegates that lost their private keys. 
Title: Re: Dry Run 3: A Game of Delegates
Post by: wackou on June 20, 2014, 01:28:25 pm
btw, I only have 1 new delegate up and running for now, but I can see that there are still some unelected-delegates in the list of active ones. Should I create more new delegates in order to "push" the unelected ones out, or should we just wait until more people join in?
Title: Re: Dry Run 3: A Game of Delegates
Post by: coolspeed on June 20, 2014, 01:28:30 pm
Unfortunately I found once my delegate name "coolspeed" is registered. I guess it is registered in genesis block. But I couldn't export my private key that time. But I have backed up all my recent datadirs.

How can I find back my private key (or wallet) of "coolspeed"? Which file should I overwrite, if it is possible?
Thanks.


=====================================================
UPDATE:

I've solved it. I copyed my old wallet dir, opened it in the new client, and then dumped my private key.
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 02:37:19 pm
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

Code: [Select]
xeldal-w (unlocked) >>> wallet_transfer 10 LOVE xeldal pts-jmob
20010 insufficient_funds: insufficient funds

    {"required":"0.010000 XTS","available":"0.000000 XTS"}
    th_a  wallet.cpp:210 withdraw_to_transaction

    {"amount":10000,"asset_id":0,"from_account_address":"XTSEsJxLS48MQR1TT1o9JryjA4tF9Poho52r","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAzXHYc8VhagagoKwnPMuhnkpv8RD7HkQR","amount":10000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSHXEoQBBLUJnrFu3D5s3xgyGsTRG7mihaM"]}
    th_a  wallet.cpp:211 withdraw_to_transaction

    {"real_amount_to_transfer":10,"amount_to_transfer_symbol":"LOVE","from_account_name":"xeldal","to_account_name":"pts-jmob","memo_message":""}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command

I assume its in a pending transaction somewhere
No sign of it in the receive wallet.
blockchain_get_pending_transactions returns [] nothing

Where is the LOVE?
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:39:27 pm
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

Code: [Select]
xeldal-w (unlocked) >>> wallet_transfer 10 LOVE xeldal pts-jmob
20010 insufficient_funds: insufficient funds

    {"required":"0.010000 XTS","available":"0.000000 XTS"}
    th_a  wallet.cpp:210 withdraw_to_transaction

    {"amount":10000,"asset_id":0,"from_account_address":"XTSEsJxLS48MQR1TT1o9JryjA4tF9Poho52r","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAzXHYc8VhagagoKwnPMuhnkpv8RD7HkQR","amount":10000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSHXEoQBBLUJnrFu3D5s3xgyGsTRG7mihaM"]}
    th_a  wallet.cpp:211 withdraw_to_transaction

    {"real_amount_to_transfer":10,"amount_to_transfer_symbol":"LOVE","from_account_name":"xeldal","to_account_name":"pts-jmob","memo_message":""}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command

I assume its in a pending transaction somewhere
No sign of it in the receive wallet.
blockchain_get_pending_transactions returns [] nothing

Where is the LOVE?

"required":"0.010000 XTS","available":"0.000000 XTS"

You need XTS to pay the fee
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 02:44:40 pm
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

Code: [Select]
xeldal-w (unlocked) >>> wallet_transfer 10 LOVE xeldal pts-jmob
20010 insufficient_funds: insufficient funds

    {"required":"0.010000 XTS","available":"0.000000 XTS"}
    th_a  wallet.cpp:210 withdraw_to_transaction

    {"amount":10000,"asset_id":0,"from_account_address":"XTSEsJxLS48MQR1TT1o9JryjA4tF9Poho52r","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAzXHYc8VhagagoKwnPMuhnkpv8RD7HkQR","amount":10000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSHXEoQBBLUJnrFu3D5s3xgyGsTRG7mihaM"]}
    th_a  wallet.cpp:211 withdraw_to_transaction

    {"real_amount_to_transfer":10,"amount_to_transfer_symbol":"LOVE","from_account_name":"xeldal","to_account_name":"pts-jmob","memo_message":""}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command

I assume its in a pending transaction somewhere
No sign of it in the receive wallet.
blockchain_get_pending_transactions returns [] nothing

Where is the LOVE?

"required":"0.010000 XTS","available":"0.000000 XTS"

You need XTS to pay the fee

I know.  What I'm saying is "Where is the LOVE?"
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

So if you have insufficient funds you just get robbed of whatever you were trying to send? 
I know thats not how its supposed to work.
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:51:20 pm
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

Code: [Select]
xeldal-w (unlocked) >>> wallet_transfer 10 LOVE xeldal pts-jmob
20010 insufficient_funds: insufficient funds

    {"required":"0.010000 XTS","available":"0.000000 XTS"}
    th_a  wallet.cpp:210 withdraw_to_transaction

    {"amount":10000,"asset_id":0,"from_account_address":"XTSEsJxLS48MQR1TT1o9JryjA4tF9Poho52r","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAzXHYc8VhagagoKwnPMuhnkpv8RD7HkQR","amount":10000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSHXEoQBBLUJnrFu3D5s3xgyGsTRG7mihaM"]}
    th_a  wallet.cpp:211 withdraw_to_transaction

    {"real_amount_to_transfer":10,"amount_to_transfer_symbol":"LOVE","from_account_name":"xeldal","to_account_name":"pts-jmob","memo_message":""}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command

I assume its in a pending transaction somewhere
No sign of it in the receive wallet.
blockchain_get_pending_transactions returns [] nothing

Where is the LOVE?

"required":"0.010000 XTS","available":"0.000000 XTS"

You need XTS to pay the fee

I know.  What I'm saying is "Where is the LOVE?"
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

So if you have insufficient funds you just get robbed of whatever you were trying to send? 
I know thats not how its supposed to work.

Ah, sounds like a wallet sync bug... filing an issue
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 02:51:30 pm
You can probably rescan to get it back
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 02:54:29 pm
You can probably rescan to get it back

Yes, this fixed it. Thanks
Title: Re: Dry Run 3: A Game of Delegates
Post by: bytemaster on June 20, 2014, 02:56:02 pm
I tried to send 10 LOVE from one of my accounts to another.  The sending account has no XTS and I get "insufficient funds"
Yet it removes the 10 LOVE

Code: [Select]
xeldal-w (unlocked) >>> wallet_transfer 10 LOVE xeldal pts-jmob
20010 insufficient_funds: insufficient funds

    {"required":"0.010000 XTS","available":"0.000000 XTS"}
    th_a  wallet.cpp:210 withdraw_to_transaction

    {"amount":10000,"asset_id":0,"from_account_address":"XTSEsJxLS48MQR1TT1o9JryjA4tF9Poho52r","trx":{"expiration":null,"delegate_id":null,"operations":[{"type":"withdraw_op_type","data":{"balance_id":"XTSAzXHYc8VhagagoKwnPMuhnkpv8RD7HkQR","amount":10000000,"claim_input_data":""}}],"signatures":[]},"required_signatures":["XTSHXEoQBBLUJnrFu3D5s3xgyGsTRG7mihaM"]}
    th_a  wallet.cpp:211 withdraw_to_transaction

    {"real_amount_to_transfer":10,"amount_to_transfer_symbol":"LOVE","from_account_name":"xeldal","to_account_name":"pts-jmob","memo_message":""}
    th_a  wallet.cpp:1759 transfer_asset

    {}
    th_a  common_api_client.cpp:502 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:529 execute_command

I assume its in a pending transaction somewhere
No sign of it in the receive wallet.
blockchain_get_pending_transactions returns [] nothing

Where is the LOVE?

This failed before it could make it into pending transactions.
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 03:01:09 pm
This failed before it could make it into pending transactions.

Right, I was confused because wallet_account_balance was showing my account had be decremented.
Title: Re: Dry Run 3: A Game of Delegates
Post by: bitcoinerS on June 20, 2014, 03:03:20 pm
Send me some LOVE or XTS or whatever other asset to "play with"

XTS63FqvmnBD9TcnMktEcL9FY6V6n1HWv2cC45xAMvcgetMEB2nDc

(and vote for bitcoiners :)
Title: Re: Dry Run 3: A Game of Delegates
Post by: clout on June 20, 2014, 03:27:19 pm
I am currently missing blocks even though I am connected to the network and my delegates are enabled. Why might this be?
Title: Re: Dry Run 3: A Game of Delegates
Post by: boombastic on June 20, 2014, 04:08:34 pm
Check log for information.  I had experienced same thing.  I set wallet_unlock 999.  When 999 seconds passed, wallet is locked and my delegate stopped producing.  Try unlocking it for a longer period.


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 3: A Game of Delegates
Post by: Fox on June 20, 2014, 04:11:18 pm
I'm ready to help test!  I'll need some XTS to get started (and a bit of guidance).  Thus far I have used wallet_import_keyhotee to connect my wallet to my ID. 

Does that allow you to send XTS to my name "fox", or must I paste the "account_address" into this thread then register the account thereafter?

Thanks,
Fox
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 04:18:15 pm
I'm ready to help test!  I'll need some XTS to get started (and a bit of guidance).  Thus far I have used wallet_import_keyhotee to connect my wallet to my ID. 

Does that allow you to send XTS to my name "fox", or must I paste the "account_address" into this thread then register the account thereafter?

Thanks,
Fox

I just sent 1 XTS to "fox"
Title: Re: Dry Run 3: A Game of Delegates
Post by: coolspeed on June 20, 2014, 04:27:24 pm
Why do I "coolspeed" have so many down votes that I can never be a delegate?

Code: [Select]
40          coolspeed                163989998           109830374550        -1.096870184 %      0               4
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 04:37:46 pm
Why do I "coolspeed" have so many down votes that I can never be a delegate?

Code: [Select]
40          coolspeed                163989998           109830374550        -1.096870184 %      0               4

Because you were an initial delegate - you should have been named "unelected-coolspeed" so you could make a new "coolspeed" with 0 but we messed up.
Title: Re: Dry Run 3: A Game of Delegates
Post by: bitcoinerS on June 20, 2014, 04:41:35 pm
It seems every block produced by a delegate increases votes for that delegate.. Why?
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 04:49:48 pm
It seems every block produced by a delegate increases votes for that delegate.. Why?

delegate pay automatically votes for the delegate that produced it. Since it has to be voting for someone it might as well vote for the guy who produced it
Title: Re: Dry Run 3: A Game of Delegates
Post by: Fox on June 20, 2014, 04:56:29 pm
Quote
I just sent 1 XTS to "fox"

Thank you toast and spartako.  I will now attempt to become a delegate.
Title: Re: Dry Run 3: A Game of Delegates
Post by: cgafeng on June 20, 2014, 04:59:20 pm
Can someone please send me some XTS?  8)

XTS8k1x5PppXVDrVy61jqkd4bfqzvYMFUJiJYuMBFhqpswKgfb3BH

I'm trying to register "light".

Thanks.
sent.
Title: Re: Dry Run 3: A Game of Delegates
Post by: taoljj on June 20, 2014, 05:08:21 pm
registered a new account, registered as delegate 'xeldal'
I was able to import pts wallets bitcoin private keys but I'm unable to import an electrum wallet file.

....

How to import pts wallets bitcoin private keys to get XTS? Thanks all.


Done.thanks
Title: Re: Dry Run 3: A Game of Delegates
Post by: coolspeed on June 20, 2014, 05:11:12 pm

Why do I "coolspeed" have so many down votes that I can never be a delegate?

Code: [Select]
40          coolspeed                163989998           109830374550        -1.096870184 %      0               4

Because you were an initial delegate - you should have been named "unelected-coolspeed" so you could make a new "coolspeed" with 0 but we messed up.

Could you extract that name back for me in next dry run or real chain?



Sent from my iPhone using Tapatalk
Title: Re: Dry Run 3: A Game of Delegates
Post by: cgafeng on June 20, 2014, 05:13:46 pm
There are something weird.
I send some xts and get this.

Code: [Select]
cgafeng (unlocked) >>> wallet_account_transaction_history
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      0.0    2014-06-20T17:03:30 cgafeng             vlight              have fun                                  10.000000 XTS        0.010000 XTS        633c66a8


Code: [Select]
cgafeng (unlocked) >>> blockchain_get_transaction 633c66a8
{
  "trx": {
    "expiration": null,
    "delegate_id": null,
    "operations": [],
    "signatures": []
  },
  "signed_keys": [],
  "validation_error": null,
  "required_deposits": [],
  "provided_deposits": [],
  "deposits": [],
  "withdraws": [],
  "balance": [],
  "net_delegate_votes": [],
  "chain_location": {
    "block_num": 0,
    "trx_num": 0
  }
}
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 05:33:57 pm
registered a new account, registered as delegate 'xeldal'
I was able to import pts wallets bitcoin private keys but I'm unable to import an electrum wallet file.

....

How to import pts wallets bitcoin private keys to get XTS? Thanks all.

For PTS wallet you will use wallet_import_bitcoin

Code: [Select]
wallet_import_bitcoin <wallet_filename> <passphrase> <account_name>                                   Imports a bitcoin wallet
Imports a bitcoin wallet

Parameters:
  wallet_filename (filename, required): the path to the bitcoin wallet you would like to import.
  passphrase (passphrase, required): the bitcoin wallet's password, not your bitshares wallet password.
  account_name (account_name, required): the account name to receive the contents of the wallet, you must create this account first if it does not exist.


https://github.com/BitShares/bitshares_toolkit/wiki/Bitshares-commands:-Wallet#wallet_import_bitcoin

You'll need to upload your wallet.dat file to your server


Title: Re: Dry Run 3: A Game of Delegates
Post by: Fox on June 20, 2014, 05:34:48 pm
Now I'm looking for some votes.  Anyone willing to:
Code: [Select]
wallet_set_delegate_trust_level fox 1
Thanks in advance.
Title: Re: Dry Run 3: A Game of Delegates
Post by: cgafeng on June 20, 2014, 05:35:38 pm
Because i still have not registered the account(not enough funds.)
It is actually "light", not "vlight"    8)


Also, should i post my bts address or public key in order to receive XTS ?

The vlight is just the name in my wallet, it actually send to you public address XTS8k1x5PppXVDrVy61jqkd4bfqzvYMFUJiJYuMBFhqpswKgfb3BH.
It seens transfer failure , and my xts didn't get back even after wallet_rescan_blockchain.
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 05:46:57 pm
With "screen -S delegate" is there any way to get more than 1 screens worth of scrollable history?

Title: Re: Dry Run 3: A Game of Delegates
Post by: Fox on June 20, 2014, 06:14:54 pm
I'd like to issue a new asset, but am lacking XTS to do so.  Looks like I'll need about 20 XTS to create it.  I hope to trade for some LOVE once I get it issued.  :)

Also, still hoping to get in as a delegate:
Code: [Select]
wallet_set_delegate_trust_level fox 1
Title: Re: Dry Run 3: A Game of Delegates
Post by: boombastic on June 20, 2014, 06:16:29 pm
Ctrl+a then press [ now you are in vim alike environment, ctrl+b to scroll page backward, ctrl+f scroll forward, check out man screen for details


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 3: A Game of Delegates
Post by: boombastic on June 20, 2014, 06:18:16 pm
Ctrl+a ? for help


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 3: A Game of Delegates
Post by: Xeldal on June 20, 2014, 06:31:58 pm
Ctrl+a then press [ now you are in vim alike environment, ctrl+b to scroll page backward, ctrl+f scroll forward, check out man screen for details


Sent from my iPhone using Tapatalk

Excellent.  Thank you.
Title: Re: Dry Run 3: A Game of Delegates
Post by: taoljj on June 20, 2014, 06:53:25 pm
registered a new account, registered as delegate 'xeldal'
I was able to import pts wallets bitcoin private keys but I'm unable to import an electrum wallet file.

....

How to import pts wallets bitcoin private keys to get XTS? Thanks all.

For PTS wallet you will use wallet_import_bitcoin

Code: [Select]
wallet_import_bitcoin <wallet_filename> <passphrase> <account_name>                                   Imports a bitcoin wallet
Imports a bitcoin wallet

Parameters:
  wallet_filename (filename, required): the path to the bitcoin wallet you would like to import.
  passphrase (passphrase, required): the bitcoin wallet's password, not your bitshares wallet password.
  account_name (account_name, required): the account name to receive the contents of the wallet, you must create this account first if it does not exist.


Thanks +5% +5%

https://github.com/BitShares/bitshares_toolkit/wiki/Bitshares-commands:-Wallet#wallet_import_bitcoin

You'll need to upload your wallet.dat file to your server
Title: Re: Dry Run 3: A Game of Delegates
Post by: CalabiYau on June 20, 2014, 06:55:12 pm
Surprisingly I managed to set up everything to run a delegate account. Thank you for the guidance to a non-coder and the interesting insight in this childbirth.

Now some

wallet_set_delegate_trust_level calyau1 10 / calyau2 10 / calyau3 10

would be appreciated.
 
Title: Re: Dry Run 3: A Game of Delegates
Post by: toast on June 20, 2014, 07:29:16 pm
Because i still have not registered the account(not enough funds.)
It is actually "light", not "vlight"    8)


Also, should i post my bts address or public key in order to receive XTS ?

The vlight is just the name in my wallet, it actually send to you public address XTS8k1x5PppXVDrVy61jqkd4bfqzvYMFUJiJYuMBFhqpswKgfb3BH.
It seens transfer failure , and my xts didn't get back even after wallet_rescan_blockchain.
The transfer was successful and i have registered the account right away. Thanks.

However, when trying to register the delegate, there was an error that the account does not exist. After restarting it seems that i can register the delegate but i need at least 11 XTS more.

 Why so expensive  :o  ???
Damn, my XTS account balance just disappeared. Was almost 10 XTS, now 0 XTS  :o

Without new transactions.


Code: [Select]
(unlocked) >>> wallet_account_update_registration light light null true
20010 insufficient_funds: insufficient funds

    {"required":"20.981502 XTS","available":"0.000000 XTS"}

try rescanning, it's the wallet sync bug xeldal noticed
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 07:42:54 pm
You're right ^

I still need 11 XTS more to register a delegate.

If someone can send it i will try to increase their trust if possible  ;D

XTS8k1x5PppXVDrVy61jqkd4bfqzvYMFUJiJYuMBFhqpswKgfb3BH

I just sent you 7.  Its all I had

Code: [Select]
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   pending   2014-06-20T19:42:15 dele-puppy          light                                                          7.000000 XTS        0.010000 XTS                      2815cc4f
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 08:07:27 pm
Yeah.  It's still pending
Code: [Select]
pending   2014-06-20T19:42:15 dele-puppy          light                                                          7.000000 XTS        0.010000 XTS        2815cc4f

Ive tried
Code: [Select]
network_broadcast_transaction 2815cc4f but it throws an error
Code: [Select]
wallet (unlocked) >>> network_broadcast_transaction 2815cc4f
7 bad_cast_exception: Bad Cast
Invalid cast from type 'string_type' to Object
    {"type":"string_type"}
    th_a  variant.cpp:505 get_object

    {"command":"network_broadcast_transaction"}
    th_a  cli.cpp:529 execute_command
wallet (unlocked) >>>
 
Perhaps I have the syntax wrong.  The blocks don't seem to be running out of transaction space, but nobody seems to want my .01XTS fee.  Is there a better way to fix this than to wallet_clear_pending_transactions and try again?
Title: Re: Dry Run 3: A Game of Delegates
Post by: CalabiYau on June 20, 2014, 08:08:11 pm
I just sent you 7.  Its all I had

Code: [Select]
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   pending   2014-06-20T19:42:15 dele-puppy          light                                                          7.000000 XTS        0.010000 XTS                      2815cc4f



thanks, but i still have not received anything from your account  :o

Sent some XTS
Title: Re: Dry Run 3: A Game of Delegates
Post by: CalabiYau on June 20, 2014, 08:12:20 pm
Received some love from bitcoiners  :)  thx
Title: Re: Dry Run 3: A Game of Delegates
Post by: puppies on June 20, 2014, 08:28:03 pm
I just sent you 7.  Its all I had

Code: [Select]
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   pending   2014-06-20T19:42:15 dele-puppy          light                                                          7.000000 XTS        0.010000 XTS                      2815cc4f

thanks, but i still have not received anything from your account  :o

Looks like it finally got included on block 1653.  Can you confirm if you received it?  the transactions now shows up in my account history as unknown with a balance of 0XTS, but my account balance has been debited.
Title: Re: Dry Run 3: A Game of Delegates
Post by: bytemaster on June 20, 2014, 08:39:25 pm
Hey everyone I am sad to report that we have to reset this dry run due to a major flaw in the initial condition setup resulting in the negative votes-for everyone saw.  Unfortunately I cannot fix this without a reset.

New chain has launched that fixes this issue and the double registration issue.