BitShares Forum

Main => General Discussion => Topic started by: toast on June 23, 2014, 09:24:08 pm

Title: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 09:24:08 pm
"wow toast what a provocative title I hope you're not implying anything"

There are some important changes this time around, please read carefully.

1) Approval voting! "wallet_set_delegate_trust_level" is now effectively a boolean (0 or >0) - your wallet will pick up to 33 of your approved delegates to vote for per share in your deposit.
2) Delegates set their own income as a % of transaction fees, which cannot be changed and is visible to everyone. The new "how to register delegate guide" shows you how to set this.
3) You must register a delegate right off the bat - you cannot upgrade a non-delegate to become a delegate.
4) There are no initial delegates from previous dry runs. They are all ours and all start with 0 votes.


Let's begin!

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

* 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.

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

Delete old files in "/Users/USERNAME/Library/Application Support/BitShares XTS"
Download Mac Wallet 0.0.5:     http://bitshares.org/BitSharesXT-0.0.5.dmg   (Updated June 24, 2014, 07:34:46 PM)



Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 23, 2014, 09:35:35 pm
Removing the initial delegates was a good idea as the network was terribly slow initially.
Title: Re: Dry Run 5: The Final Countdown
Post by: tonyk on June 23, 2014, 09:38:37 pm
Enjoy while testing!

http://www.youtube.com/watch?v=TcJ-wNmazHQ   
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 09:43:05 pm
Enjoy while testing!

http://www.youtube.com/watch?v=TcJ-wNmazHQ

tsk tsk someone didn't read the OP
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 23, 2014, 09:52:22 pm
Updated OP to include download link to updated Mac Wallet.
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 23, 2014, 09:54:19 pm
I added my delegates and followed the instructions.
There are no votes for my delegates.
Shall I make a transaction ?
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 09:55:38 pm
I added my delegates and followed the instructions.
There are no votes for my delegates.
Shall I make a transaction ?

Do it!
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 23, 2014, 09:59:57 pm
Done! Transfers complete. Seems the delegates are now in top101.
Should I have unusually large amounts of XTS ?

Code: [Select]
emski (unlocked) >>> wallet_account_balance
emski:
    142,111.51466 XTS
angel:
    10.00000 XTS
batman:
    100.00000 XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: tonyk on June 23, 2014, 10:03:57 pm
Enjoy while testing!

http://www.youtube.com/watch?v=TcJ-wNmazHQ

tsk tsk someone didn't read the OP

Sorry I did not! I did not know that there is a treat for non-testers!


At least I post in the right threads :))
https://bitsharestalk.org/index.php?topic=5244.msg69189#msg69189
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 23, 2014, 10:07:09 pm
Peer XXXXXXXXXXX:65019 disconnected us: You offered us a block that we reject as invalid
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 10:07:52 pm
Enjoy while testing!

http://www.youtube.com/watch?v=TcJ-wNmazHQ

tsk tsk someone didn't read the OP

Sorry I did not! I did not know that there is a treat for non-testers!


At least I post in the right threads :))
https://bitsharestalk.org/index.php?topic=5244.msg69189#msg69189

LOL
Title: Re: Dry Run 5: The Final Countdown
Post by: clout on June 23, 2014, 10:08:07 pm
bad link for mac wallet
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 23, 2014, 10:08:53 pm
If you just joined and are having a hard time getting connections, disconnect and reconnect you may get more.

We are working on an update to the peer discovery that will make this unnecessary.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 23, 2014, 10:09:26 pm
bad link for mac wallet

Fixed...
Title: Re: Dry Run 5: The Final Countdown
Post by: zhangweis on June 23, 2014, 10:10:43 pm
I'll try 100% pay rate and see what will happen.  ;) I guess it's not good to allow delegates to set pay rate as it's not fair to the small amount shareholders as finally the pay rate will go up to 100% and no interest will be paid to shareholders. Everyone has to live on the mining pay instead of interest. I hope I'm wrong on this.
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 23, 2014, 10:12:01 pm
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
Will this be OK next delegate round ?
Title: Re: Dry Run 5: The Final Countdown
Post by: Mrrr on June 23, 2014, 10:12:19 pm
Isn't this supposed to be the part where the Empire strikes back? And dry run 6 the part where BM returns all Zen from Dagobah and sorts out DPOS? Anyways, good luck with testing. Its not an excuse I know but I lack the technical skills to participate :) Godspeed.
Title: Re: Dry Run 5: The Final Countdown
Post by: clout on June 23, 2014, 10:15:50 pm
whats the deal with the gravatar? ive never used it before. does it work on this wallet?
Title: Re: Dry Run 5: The Final Countdown
Post by: vikram on June 23, 2014, 10:33:26 pm
"wallet_next_block_production_time": null,
"wallet_seconds_until_next_block_production": null,
Will this be OK next delegate round ?

Should change once you get elected in the next delegate round. Make sure you have block production enabled. Let us know if it doesn't.
Title: Re: Dry Run 5: The Final Countdown
Post by: bitcoinerS on June 23, 2014, 10:58:19 pm
Seems creating new assets is very expensive this time..

Code: [Select]
wallet_asset_create USD "US Dollar" bitcoiners "Free money for all" null 1000000000 100
20010 insufficient_funds: insufficient funds

    {"required":"2,097.25001 XTS","available":"10.00000 XTS"}
Title: Re: Dry Run 5: The Final Countdown
Post by: bitcoinerS on June 23, 2014, 11:26:50 pm

Code: [Select]
>>> wallet_list_unspent_balances
           BALANCE                                   OWNER                     VOTE
--------------------------------------------------------------------------------------------------------------------------
     489.80000 XTS    XTSFLCMZWboYQB9gjzXKBHRqnwBAbAQXn3XD10 assert_exception: Assert Exception
!"unimplemented condition type":
    {}
    th_a  cli.cpp:1082 print_unspent_balances
Title: Re: Dry Run 5: The Final Countdown
Post by: alexxy on June 23, 2014, 11:27:37 pm
Any idea why i cannot register delegates?

Code: [Select]
alexxy (unlocked) >>> wallet_account_register "lexx" "alexxy" null 75   
10 assert_exception: Assert Exception
opt_account.valid():
    {}
    th_a  wallet.cpp:1883 register_account

    {"account_to_register":"lexx","public_data":null,"pay_with_account_name":"alexxy","delegate_production_fee":75}
    th_a  wallet.cpp:1942 register_account

    {"account_name":"lexx","data":null}
    th_a  client.cpp:2285 wallet_account_register

    {}
    th_a  common_api_client.cpp:532 wallet_account_register

    {"command":"wallet_account_register"}
    th_a  cli.cpp:535 execute_command
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 11:29:23 pm
Any idea why i cannot register delegates?

Code: [Select]
alexxy (unlocked) >>> wallet_account_register "lexx" "alexxy" null 75   
10 assert_exception: Assert Exception
opt_account.valid():
    {}
    th_a  wallet.cpp:1883 register_account

    {"account_to_register":"lexx","public_data":null,"pay_with_account_name":"alexxy","delegate_production_fee":75}
    th_a  wallet.cpp:1942 register_account

    {"account_name":"lexx","data":null}
    th_a  client.cpp:2285 wallet_account_register

    {}
    th_a  common_api_client.cpp:532 wallet_account_register

    {"command":"wallet_account_register"}
    th_a  cli.cpp:535 execute_command

Maybe rescan? It doesn't recognize your KID
Title: Re: Dry Run 5: The Final Countdown
Post by: alexxy on June 23, 2014, 11:31:05 pm
Any idea why i cannot register delegates?

Code: [Select]
alexxy (unlocked) >>> wallet_account_register "lexx" "alexxy" null 75   
10 assert_exception: Assert Exception
opt_account.valid():
    {}
    th_a  wallet.cpp:1883 register_account

    {"account_to_register":"lexx","public_data":null,"pay_with_account_name":"alexxy","delegate_production_fee":75}
    th_a  wallet.cpp:1942 register_account

    {"account_name":"lexx","data":null}
    th_a  client.cpp:2285 wallet_account_register

    {}
    th_a  common_api_client.cpp:532 wallet_account_register

    {"command":"wallet_account_register"}
    th_a  cli.cpp:535 execute_command

Maybe rescan? It doesn't recognize your KID

Already did rescan, And i have some XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 11:32:34 pm
Any idea why i cannot register delegates?

Code: [Select]
alexxy (unlocked) >>> wallet_account_register "lexx" "alexxy" null 75   
10 assert_exception: Assert Exception
opt_account.valid():
    {}
    th_a  wallet.cpp:1883 register_account

    {"account_to_register":"lexx","public_data":null,"pay_with_account_name":"alexxy","delegate_production_fee":75}
    th_a  wallet.cpp:1942 register_account

    {"account_name":"lexx","data":null}
    th_a  client.cpp:2285 wallet_account_register

    {}
    th_a  common_api_client.cpp:532 wallet_account_register

    {"command":"wallet_account_register"}
    th_a  cli.cpp:535 execute_command

Maybe rescan? It doesn't recognize your KID

Already did rescan, And i have some XTS

Does "lexx" exist locally?
Title: Re: Dry Run 5: The Final Countdown
Post by: bitcoinerS on June 23, 2014, 11:35:20 pm
wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_production_fee]

Code: [Select]
  delegate_production_fee (uint32_t, optional, defaults to 255): A value between 0 and 100% delegates, 255 for non delegates

I am confused. What is delegate production fee?
Title: Re: Dry Run 5: The Final Countdown
Post by: alexxy on June 23, 2014, 11:35:41 pm
Any idea why i cannot register delegates?

Code: [Select]
alexxy (unlocked) >>> wallet_account_register "lexx" "alexxy" null 75   
10 assert_exception: Assert Exception
opt_account.valid():
    {}
    th_a  wallet.cpp:1883 register_account

    {"account_to_register":"lexx","public_data":null,"pay_with_account_name":"alexxy","delegate_production_fee":75}
    th_a  wallet.cpp:1942 register_account

    {"account_name":"lexx","data":null}
    th_a  client.cpp:2285 wallet_account_register

    {}
    th_a  common_api_client.cpp:532 wallet_account_register

    {"command":"wallet_account_register"}
    th_a  cli.cpp:535 execute_command

Maybe rescan? It doesn't recognize your KID

Already did rescan, And i have some XTS

Does "lexx" exist locally?

No. I did a try for different names however i always get this error
Title: Re: Dry Run 5: The Final Countdown
Post by: bitcoinerS on June 23, 2014, 11:39:22 pm

Does "lexx" exist locally?

No. I did a try for different names however i always get this error



create local account "lexx" first

wallet_account_create lexx
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 23, 2014, 11:57:00 pm
^^  yep. It is not very clear, we will make a better error.
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 24, 2014, 01:34:34 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
Title: Re: Dry Run 5: The Final Countdown
Post by: networker on June 24, 2014, 02:05:08 am
Can someone send me some XTS for registering as a delegate?
I create my account again and all XTS I used to have disappeared.
My XTS address: XTS8SbFTJXZk5bANCDL69a97zPDhGafbcBNN2Q3FgeEHSrLSep7UW
account name: networker
Thanks!
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 02:42:22 am
Anyone can help?
>> wallet_enable_delegate_block_production mao-delegate true

10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
    {}
    bitshares  wallet.cpp:1265 enable_delegate_block_production

    {}
    bitshares  common_api_client.cpp:802 wallet_enable_delegate_block_production

    {"command":"wallet_enable_delegate_block_production"}
    bitshares  cli.cpp:535 execute_command
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 02:46:00 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.
Title: Re: Dry Run 5: The Final Countdown
Post by: taoljj on June 24, 2014, 02:46:15 am
Anyone can help?
>> wallet_enable_delegate_block_production mao-delegate true

10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
    {}
    bitshares  wallet.cpp:1265 enable_delegate_block_production

    {}
    bitshares  common_api_client.cpp:802 wallet_enable_delegate_block_production

    {"command":"wallet_enable_delegate_block_production"}
    bitshares  cli.cpp:535 execute_command

mao-delegate is not a delegate.try to register new one.

Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 24, 2014, 02:48:20 am
XTS5vPz2LsE1KkmRrjXWD9p8r8F8DM1YBU1zcfhN1ZbfAYJ5PBKFL

Do me a favor for xts...
Title: Re: Dry Run 5: The Final Countdown
Post by: taoljj on June 24, 2014, 02:54:50 am
wallet_account_vote_summary does not work.

Code: [Select]
tao (unlocked) >>> wallet_account_vote_summary
Delegate                 Votes
         --------------------------------------------------------------
tao (unlocked) >>> wallet_account_vote_summary taolje-pay100
Delegate                 Votes
         --------------------------------------------------------------
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 03:11:11 am
wallet_account_vote_summary does not work.

Code: [Select]
tao (unlocked) >>> wallet_account_vote_summary
Delegate                 Votes
         --------------------------------------------------------------
tao (unlocked) >>> wallet_account_vote_summary taolje-pay100
Delegate                 Votes
         --------------------------------------------------------------

Correct have not updated it for approval voting.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 03:13:48 am
wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_production_fee]

Code: [Select]
  delegate_production_fee (uint32_t, optional, defaults to 255): A value between 0 and 100% delegates, 255 for non delegates

I am confused. What is delegate production fee?

It defines the percent of transaction fees that your delegate will keep as a fee for producing the block, the rest are paid as dividends to the shareholders.   A value between 0 and 100.
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 03:18:02 am
wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_production_fee]

Code: [Select]
  delegate_production_fee (uint32_t, optional, defaults to 255): A value between 0 and 100% delegates, 255 for non delegates

I am confused. What is delegate production fee?

It defines the percent of transaction fees that your delegate will keep as a fee for producing the block, the rest are paid as dividends to the shareholders.   A value between 0 and 100.

Should be renamed to "delegate pay rate"
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 24, 2014, 04:22:52 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.
btsdac is a  unregistered  account name,  since I don't have XTS to registered it , can you send XTS to my  address  XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 
directly   thanks 
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 04:29:20 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.

You must add him as a contact account (local -> add)

Anyone can help?
>> wallet_enable_delegate_block_production mao-delegate true

10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
    {}
    bitshares  wallet.cpp:1265 enable_delegate_block_production

    {}
    bitshares  common_api_client.cpp:802 wallet_enable_delegate_block_production

    {"command":"wallet_enable_delegate_block_production"}
    bitshares  cli.cpp:535 execute_command

Looks like you did not register as delegate
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 05:38:57 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.

You must add him as a contact account (local -> add)

How to add him as a contact account? What is your mean (local -> add)?

Anyone can help?
>> wallet_enable_delegate_block_production mao-delegate true

10 assert_exception: Assert Exception
delegate_record.valid() && delegate_record->is_delegate():
    {}
    bitshares  wallet.cpp:1265 enable_delegate_block_production

    {}
    bitshares  common_api_client.cpp:802 wallet_enable_delegate_block_production

    {"command":"wallet_enable_delegate_block_production"}
    bitshares  cli.cpp:535 execute_command

Looks like you did not register as delegate
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 05:42:11 am
Don't have the gui here... You can go to "console" tab and type "wallet_add_contact <name> <key>" then "wallet_transfer 10 XTS your_name his_name"
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 05:48:31 am
>> wallet_add_contact <btsdac> <XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7>

Error: invalid command "wallet_add_contact"
>> wallet_add_contact btsdac XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7

Error: invalid command "wallet_add_contact"
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 05:49:47 am
>> wallet_add_contact <btsdac> <XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7>

Error: invalid command "wallet_add_contact"
>> wallet_add_contact btsdac XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7

Error: invalid command "wallet_add_contact"

sorry "wallet_add_contact_account"
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 05:52:16 am
>> wallet_add_contact <btsdac> <XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7>

Error: invalid command "wallet_add_contact"
>> wallet_add_contact btsdac XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7

Error: invalid command "wallet_add_contact"

sorry "wallet_add_contact_account"
I did, it success! tnx Toast
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 05:55:30 am
Can someone send me some XTS for registering as a delegate?
I create my account again and all XTS I used to have disappeared.
My XTS address: XTS8SbFTJXZk5bANCDL69a97zPDhGafbcBNN2Q3FgeEHSrLSep7UW
account name: networker
Thanks!
I just did.
Title: Re: Dry Run 5: The Final Countdown
Post by: lzr1900 on June 24, 2014, 06:02:31 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 06:06:05 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Need your account name, then I can send you some xts
Title: Re: Dry Run 5: The Final Countdown
Post by: lzr1900 on June 24, 2014, 06:09:01 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Need your account name, then I can send you some xts
just added..
account name:lzr1900
thank you!
Title: Re: Dry Run 5: The Final Countdown
Post by: boombastic on June 24, 2014, 07:02:58 am
How can I update an registered account (non-delegate) to be an delegate? 

I've imported keyhotee id, it's already registered on blockchain. 
Code: [Select]
wallet_account_update_registration keyhotee keyhotee {} 50
doesn't give me delegate.
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 07:30:29 am
How can I update an registered account (non-delegate) to be an delegate? 

I've imported keyhotee id, it's already registered on blockchain. 
Code: [Select]
wallet_account_update_registration keyhotee keyhotee {} 50
doesn't give me delegate.
Seems you currently cant
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 07:32:30 am
Seems to work fast & reliable - impressive.

@ dcchong /  btsdac  /  lzr1900  / networker   XTS on the way  :)
Title: Re: Dry Run 5: The Final Countdown
Post by: betax on June 24, 2014, 07:34:31 am
What is the total XTS for this run?
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 07:37:08 am
Have two delegates .. one with 100% pay .. and one with 1% pay ..
result after 1 block produced
Quote
default (unlocked) >>> wallet_get_account xeroc-delegate-1
{
  "name": "xeroc-delegate-1",
  "delegate_info": {
    "votes_for": 4417007646,
    "blocks_produced": 1,
    "blocks_missed": 0,
    "delegate_production_fee": 100,
    "pay_balance": 115351,
    "next_secret_hash": "dba590a81b7ab85eec6b58698c239ee284709be6",
    "last_block_num_produced": 1115
  },
}
default (unlocked) >>> wallet_get_account xeroc-delegate 
{
  "delegate_info": {
    "votes_for": 4416893447,
    "blocks_produced": 1,
    "blocks_missed": 0,
    "delegate_production_fee": 1,
    "pay_balance": 1152,
    "next_secret_hash": "49a30ec6b4e81300a19e2ee058243e718920fb43",
    "last_block_num_produced": 1118
  },
}
Works nicely at my side ..
+5%
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 07:37:36 am
What is the total XTS for this run?
default (unlocked) >>> blockchain_get_asset_record XTS   
{
  "id": 0,
  "symbol": "XTS",
  "name": "BitShares XTS",
  "description": "Stake in future BitShares X chains",
  "public_data": null,
  "issuer_account_id": 0,
  "precision": 100000,
  "current_share_supply": 199999644238112,
  "maximum_share_supply": 1000000000000000,
  "collected_fees": 443332869,
  "registration_date": "20140620T000000"
}
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 24, 2014, 08:05:29 am
Seems to work fast & reliable - impressive.

@ dcchong /  btsdac  /  lzr1900  / networker   XTS on the way  :)

thanks a lot  :P
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 24, 2014, 08:10:36 am
very stable up now.
thank you, I3 team.
Title: Re: Dry Run 5: The Final Countdown
Post by: alexxy on June 24, 2014, 08:18:51 am
Well my delegates are up and running on node with 60+ connections =D
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 24, 2014, 08:18:59 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.
btsdac is a  unregistered  account name,  since I don't have XTS to registered it , can you send XTS to my  address  XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 
directly   thanks

send you 2 xts...
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 08:23:50 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Need your account name, then I can send you some xts
just added..
account name:lzr1900
thank you!
100 XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 24, 2014, 08:34:09 am
The wallet's status bar is yellow now. what does it mean ?
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 08:36:12 am
Code: [Select]
btsdac                             XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 who can seed me a little XTS for tesing  thanks
I can, but please give me your account name.
btsdac is a  unregistered  account name,  since I don't have XTS to registered it , can you send XTS to my  address  XTS7zkdnkqt4EQkWtBbB7SXmvJryBVBBRFUvJ8RpvxeoMZc7ceou7 
directly   thanks
100 XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 24, 2014, 08:36:50 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Need your account name, then I can send you some xts
just added..
account name:lzr1900
thank you!

Did you registered your account name "lzr1900" ?   I can't send you xts...
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 08:42:55 am
This Dry run test seems really stable.
Can someone send me some funds to test?
XTS6xBnJ1VuxBzbGPSWx2evLumdExjno47XiY7BVbuuZxKsp5bKgz
account name:lzr1900
thanks a lot.. +5%
Need your account name, then I can send you some xts
just added..
account name:lzr1900
thank you!

Did you registered your account name "lzr1900" ?   I can't send you xts...
Actually I have already sent to him 100 XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 08:44:56 am
Quote
default (unlocked) >>> blockchain_get_account_record lzr1900
No record found.
Seems to be not registered ..
@Saleh: you have created a contact for him?


BTW:
"blockchain_average_delegate_participation": 87.521663778162917,
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 08:45:56 am
Did you registered your account name "lzr1900" ?   I can't send you xts...

You can added him to be your contact on here: "Directory" -> "Unregistered" -> Button +New or just use the Console
Title: Re: Dry Run 5: The Final Countdown
Post by: Saleh on June 24, 2014, 08:48:21 am
Quote
default (unlocked) >>> blockchain_get_account_record lzr1900
No record found.
Seems to be not registered ..
@Saleh: you have created a contact for him?


BTW:
"blockchain_average_delegate_participation": 87.521663778162917,

June 24, 2014 at 4:24:00 PM GMT+8   mao-delegate1   lzr1900   Hey   100 XTS   0.01 XTS

He is in my Unregistered contact list. Directory -> Unregistered
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 24, 2014, 08:52:03 am
The wallet's status bar is yellow now. what does it mean ?
good news!!!
it was red, now it is yellow, I suppose when it get's "green " we will have to  "walk"... to the moon...get ready guys only a few seats left  :)

Sent from my ALCATEL ONE TOUCH 997D using Tapatalk

Title: Re: Dry Run 5: The Final Countdown
Post by: ebit on June 24, 2014, 09:03:17 am
very stable up now.
thank you, I3 team.

Thanks.Very Much.
I see sun.
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 09:06:53 am
Code: [Select]
wallet-1 (unlocked) >>> wallet_list_unspent_balances XTS light
           BALANCE                                   OWNER                     VOTE
--------------------------------------------------------------------------------------------------------------------------
   5,547.38100 XTS    XTS4arCCJXnKaKRRx17bX3cq8WKYR6ntzS2s10 assert_exception: Assert Exception
!"unimplemented condition type":
    {}
    th_a  cli.cpp:1082 print_unspent_balances
wallet-1 (unlocked) >>>

 ???
I reopened a ticket on that issue: https://github.com/BitShares/bitshares_toolkit/issues/330
Title: Re: Dry Run 5: The Final Countdown
Post by: gyhy on June 24, 2014, 09:30:52 am
 +5%
Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 24, 2014, 09:32:34 am
some funds pls XTS7zLgcAUW9Yqt9CEXfY5vMiaaRjREchNva1HBhPVAasW7kr94ZB thx
Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 24, 2014, 09:40:18 am
very stable up now.
thank you, I3 team.

Thanks.Very Much.
I see sun.

agreed working like charme currently .. stable!
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 09:44:04 am
some funds pls XTS7zLgcAUW9Yqt9CEXfY5vMiaaRjREchNva1HBhPVAasW7kr94ZB thx

Done, enjoy  :)
Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 24, 2014, 09:47:41 am
some funds pls XTS7zLgcAUW9Yqt9CEXfY5vMiaaRjREchNva1HBhPVAasW7kr94ZB thx

Done, enjoy  :)

Thx :) You got some EUR in exchange
Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 24, 2014, 09:48:33 am
some funds pls XTS7zLgcAUW9Yqt9CEXfY5vMiaaRjREchNva1HBhPVAasW7kr94ZB thx
Code: [Select]
BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1354.0    2014-06-24T09:38:00 light               cass                                                           30.00000 XTS         0.10000 XTS        1bbf57b8

Thx :) You got some EUR in exchange also
Title: Re: Dry Run 5: The Final Countdown
Post by: lzr1900 on June 24, 2014, 09:52:38 am
Quote
default (unlocked) >>> blockchain_get_account_record lzr1900
No record found.
Seems to be not registered ..
@Saleh: you have created a contact for him?


BTW:
"blockchain_average_delegate_participation": 87.521663778162917,

June 24, 2014 at 4:24:00 PM GMT+8   mao-delegate1   lzr1900   Hey   100 XTS   0.01 XTS

He is in my Unregistered contact list. Directory -> Unregistered
thank you @CalabiYau @Saleh @dcchong @xeroc !Received your test funds!Awesome.
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 09:56:00 am
some funds pls XTS7zLgcAUW9Yqt9CEXfY5vMiaaRjREchNva1HBhPVAasW7kr94ZB thx

Done, enjoy  :)

Thx :) You got some EUR in exchange

Thx, works at the speed of light !  Comfortable exchange rate btw  8)
Title: Re: Dry Run 5: The Final Countdown
Post by: yangsbo on June 24, 2014, 11:08:24 am
who send me xts

XTS7r3LZb1hJMRkRb4JLL53mkVhcYKoC9AwJ5iqKFueQ17mePt7if

yangsbo1
Title: Re: Dry Run 5: The Final Countdown
Post by: ebit on June 24, 2014, 11:11:53 am
Code: [Select]
wallet_get_account light
{
  "index": 4,
  "id": 324,
  "name": "light",
  "public_data": null,
  "owner_key": "XTS8k1x5PppXVDrVy61jqkd4bfqzvYMFUJiJYuMBFhqpswKgfb3BH",
I might have imported another private key to the already created account and messed up  everything :-[

You are rich! ;D
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 11:18:05 am
You are rich! ;D
Says the guy who accidentally sent 6k PTS to AGS ;-)

... just kidding ..

In some sense we are all rich .. at least in terms of knowledge ..
Title: Re: Dry Run 5: The Final Countdown
Post by: bdnoble on June 24, 2014, 11:45:23 am
Hey so... How do I increase my max connections? I can't seem to find that command.


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 5: The Final Countdown
Post by: bdnoble on June 24, 2014, 11:53:46 am
Never mind, seems it was increased by default. :)


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 24, 2014, 01:00:14 pm
who send me xts

XTS7r3LZb1hJMRkRb4JLL53mkVhcYKoC9AwJ5iqKFueQ17mePt7if

yangsbo1

100xts
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 01:16:44 pm
who send me xts

XTS7r3LZb1hJMRkRb4JLL53mkVhcYKoC9AwJ5iqKFueQ17mePt7if

yangsbo1

Some more !
Title: Re: Dry Run 5: The Final Countdown
Post by: wackou on June 24, 2014, 01:39:03 pm
wow, connected to the network immediately (with a lot of stable connections), transactions go through blazingly fast, this dry run really looks good. Great work!
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 01:47:37 pm
PTS market seems to like this new test-run
http://imgur.com/NY8ZkOH
same thing on bter.com
http://imgur.com/2UIsqkR

Only chinese seem to not get it yet .. http://imgur.com/citT76C
Maybe we should tell them ... about the currently successful testnetwork
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 01:48:51 pm
"blockchain_head_block_num": 1458,
  "blockchain_head_block_time": "20140624T104230",
  "blockchain_head_block_time_rel": "3 hours old",
  "blockchain_confirmation_requirement": 25,
  "blockchain_average_delegate_participation": 66.142763588736088,
  "network_num_connections": 23,
  "ntp_time": "20140624T134630.850705",
  "ntp_error_seconds": -8.1481929999999991,
  "wallet_unlocked_seconds_remaining": 44518,
  "wallet_next_block_production_time": "20140624T135430",
  "wallet_seconds_until_next_block_production": 480,
  "wallet_local_time": "20140624T134630",
  "blockchain_random_seed": "1573311c2cff2aa5b316cc752a5fb71791ebde1e",
  "blockchain_shares": 199999665574760,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T020828",
  "wallet_version": 100

Chain hanging here

calyauwall (unlocked) >>> blockchain_list_forks
[
  1381,
  1456

Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 24, 2014, 01:51:23 pm
I am on 1791 but also can see the same forks
Title: Re: Dry Run 5: The Final Countdown
Post by: Nimrod on June 24, 2014, 02:28:21 pm
bad news  :-\

blockchain_list_forks

[
  1459,
  1460,
  1843,
  1844
]
Title: Re: Dry Run 5: The Final Countdown
Post by: Kenof on June 24, 2014, 02:41:36 pm
bad news  :-\

blockchain_list_forks

[
  1459,
  1460,
  1843,
  1844
]

seems i am on different chain:

Code: [Select]
list_forks
[
  1381,
  1456,
  1458,
  1459,
  1460,
  1842,
  1843,
  1844
]

it is strange how chain is being forked on sequential blocks
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 24, 2014, 02:46:29 pm
I have test flood transactions again.
send 1000 transactions( from node A to node B) in about 30 sectonds.

node B receive all these transactions in about 4 block: 1843 ~ 1846
but list_forks list 3 forks: 1842,1843,1844

node A seems switch to a fork chain, all these transactions are illegal.
Code: [Select]
delegate (unlocked) >>> wallet_account_transaction_history                                                                                                             
.....
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             46.000000 BTC         0.10000 XTS        fd31e9f7
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                            100.000000 BTC         0.10000 XTS        23f8eb96
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             51.000000 BTC         0.10000 XTS        f797e5a0
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             66.000000 BTC         0.10000 XTS        d181cadb
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             20.000000 BTC         0.10000 XTS        e7eb8fa2
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             47.000000 BTC         0.10000 XTS        d636cdff
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             49.000000 BTC         0.10000 XTS        f1b1d142
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             61.000000 BTC         0.10000 XTS        f1f7acdb

delegate (unlocked) >>> list_errors_brief
[[
    "20140624T142330.793862",
    "duplicate transaction"
  ],[
    "20140624T142500.943216",
    "duplicate transaction"
  ]
]


here is the scripts for test.
Code: [Select]
#!/usr/bin/expect -f

set timeout -1

set wallet_name "default"
set account_from "ob"
set account_to "delegate-alt"
set loop_time 1000
send_user "wallet name is: $wallet_name\n"
send_user "wallet passphrase: "
stty -echo
expect_user -re "(.*)\n"
stty echo
set wallet_pass $expect_out(1,string)

spawn ./bitshares_client --server --httpport 9989 --rpcuser alt --rpcpassword alt

#expect -exact "--- there are now 1 active connections to the p2p network"
expect -exact "(wallet closed) >>> "
send -- "info\r"
expect -exact "(wallet closed) >>> "
send -- "wallet_open $wallet_name\r"
expect -exact "$wallet_name (locked) >>> "
send -- "wallet_unlock 999999\r"
expect -exact "passphrase: "
send -- "$wallet_pass\r"
#expect -exact "$wallet_name (unlocked) >>> "
#send -- "wallet_rescan_blockchain\r"
sleep 2

for {set i 1} {$i < 11} {incr i 1} {
for {set j 1} {$j < 101} {incr j 1} {
  expect -exact "$wallet_name (unlocked) >>> "
  send -- "wallet_transfer $j BTC $account_from $account_to \"test flood...\"\r"
}
sleep 3
}
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_account_transaction_history\r"
interact
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 24, 2014, 03:13:03 pm
one point need to be notice.
I think from the scripts, should transfer exactly 1000 transactions.
but ether from acount delegate-alt or ob, there are 1003 transactions in the transaction_history
I have checked again. there are 13 transactions with amount 100.
maybe block 1846 is wrong, it only contain 3 transactions with amount 100.

I have test flood transactions again.
send 1000 transactions( from node A to node B) in about 30 sectonds.

node B receive all these transactions in about 4 block: 1843 ~ 1846
but list_forks list 3 forks: 1842,1843,1844

node A seems switch to a fork chain, all these transactions are illegal.
Code: [Select]
delegate (unlocked) >>> wallet_account_transaction_history                                                                                                             
.....
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             46.000000 BTC         0.10000 XTS        fd31e9f7
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                            100.000000 BTC         0.10000 XTS        23f8eb96
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             51.000000 BTC         0.10000 XTS        f797e5a0
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             66.000000 BTC         0.10000 XTS        d181cadb
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             20.000000 BTC         0.10000 XTS        e7eb8fa2
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             47.000000 BTC         0.10000 XTS        d636cdff
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             49.000000 BTC         0.10000 XTS        f1b1d142
      0.0    2014-06-24T14:28:30 ob                  delegate-alt        test flood...                             61.000000 BTC         0.10000 XTS        f1f7acdb

delegate (unlocked) >>> list_errors_brief
[[
    "20140624T142330.793862",
    "duplicate transaction"
  ],[
    "20140624T142500.943216",
    "duplicate transaction"
  ]
]


here is the scripts for test.
Code: [Select]
#!/usr/bin/expect -f

set timeout -1

set wallet_name "default"
set account_from "ob"
set account_to "delegate-alt"
set loop_time 1000
send_user "wallet name is: $wallet_name\n"
send_user "wallet passphrase: "
stty -echo
expect_user -re "(.*)\n"
stty echo
set wallet_pass $expect_out(1,string)

spawn ./bitshares_client --server --httpport 9989 --rpcuser alt --rpcpassword alt

#expect -exact "--- there are now 1 active connections to the p2p network"
expect -exact "(wallet closed) >>> "
send -- "info\r"
expect -exact "(wallet closed) >>> "
send -- "wallet_open $wallet_name\r"
expect -exact "$wallet_name (locked) >>> "
send -- "wallet_unlock 999999\r"
expect -exact "passphrase: "
send -- "$wallet_pass\r"
#expect -exact "$wallet_name (unlocked) >>> "
#send -- "wallet_rescan_blockchain\r"
sleep 2

for {set i 1} {$i < 11} {incr i 1} {
for {set j 1} {$j < 101} {incr j 1} {
  expect -exact "$wallet_name (unlocked) >>> "
  send -- "wallet_transfer $j BTC $account_from $account_to \"test flood...\"\r"
}
sleep 3
}
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_account_transaction_history\r"
interact
Title: Re: Dry Run 5: The Final Countdown
Post by: coolspeed on June 24, 2014, 03:43:00 pm
Hi core team,
Could you please make a formal public announcement about the fork issue? The cause, the status, the difficult part, or what are being tried.
Thanks.
Title: Re: Dry Run 5: The Final Countdown
Post by: nethyb on June 24, 2014, 03:44:06 pm
Can someone send me some XTS for testing...

nethyb XTS6UVhyKmJMCbaW5MSAm7ADc75TntWLFnVrYdhr3yr2J5H31kPPz

cheers...
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 24, 2014, 03:45:59 pm
Hi core team,
Could you please make a formal public announcement about the fork issue? The cause, the status, the difficult part, or what are being tried.
Thanks.
Dont you want to wait an hour to see if the network decides the correct branch?
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 24, 2014, 03:47:43 pm
 "blockchain_head_block_num": 1464,
  "blockchain_head_block_time": "20140624T145500",
  "blockchain_head_block_time_rel": "38 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 58.347775852108605,
  "network_num_connections": 22,
  "ntp_time": "20140624T153319.084075",
  "ntp_error_seconds": -8.6212110000000006,
  "wallet_unlocked_seconds_remaining": 41051,
  "wallet_next_block_production_time": "20140624T153530",
  "wallet_seconds_until_next_block_production": 131,
  "wallet_local_time": "20140624T153319",
  "blockchain_random_seed": "3a5173163059eda1d5752650e55cb63d84b0ee81",
  "blockchain_shares": 199999665881474,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T025730",
  "wallet_version": 100
}
--- there are now 21 active connections to the p2p network
--- there are now 22 active connections to the p2p network
--- syncing with p2p network, 418 blocks left to fetch

client still on strike - even after restart not syncing
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 03:48:37 pm
Hi core team,
Could you please make a formal public announcement about the fork issue? The cause, the status, the difficult part, or what are being tried.
Thanks.

Dan just came in (was doing a demo in the middle of alt's spam, LOL).
Doing triage now
Title: Re: Dry Run 5: The Final Countdown
Post by: taoljj on June 24, 2014, 03:49:25 pm
me too.
Code: [Select]
[
  1381,
  1456,
  1458,
  1459,
  1460,
  1461,
  1462,
  1464,
  1466,
  1842,
  1843,
  1844,
  1847,
  1855,
  1859,
  1867,
  1868,
  1878
]


bad news  :-\

blockchain_list_forks

[
  1459,
  1460,
  1843,
  1844
]

seems i am on different chain:

Code: [Select]
list_forks
[
  1381,
  1456,
  1458,
  1459,
  1460,
  1842,
  1843,
  1844
]

it is strange how chain is being forked on sequential blocks
Title: Re: Dry Run 5: The Final Countdown
Post by: bennyliaa on June 24, 2014, 04:39:20 pm
Anyone send me some XTS?Thanks.
XTS8iNHdqXtkCgraDREdMMUvQpb57czTTvaRXumJc6HYc7U2r77AF
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 04:44:41 pm
Anyone send me some XTS?Thanks.
XTS8iNHdqXtkCgraDREdMMUvQpb57czTTvaRXumJc6HYc7U2r77AF

Sent.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 04:51:20 pm
Thank you alt for your 1000 trx spam test, you fractured the network with that load and identified several bugs that we are trying to track down.

(http://bitshares.org/documentation/forks.png)
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 24, 2014, 04:58:05 pm
Thank you alt for your 1000 trx spam test, you fractured the network with that load and identified several bugs that we are trying to track down.

(http://bitshares.org/documentation/forks.png)
It's my pleasure to work with you guys for the great target.  ;)
Title: Re: Dry Run 5: The Final Countdown
Post by: bennyliaa on June 24, 2014, 05:15:08 pm
Anyone send me some XTS?Thanks.
XTS8iNHdqXtkCgraDREdMMUvQpb57czTTvaRXumJc6HYc7U2r77AF

Sent.

Hi BM, now I am using the window client for testing, and I found that the network's connection is 0, does it works well in this dry?
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 05:18:51 pm
Anyone send me some XTS?Thanks.
XTS8iNHdqXtkCgraDREdMMUvQpb57czTTvaRXumJc6HYc7U2r77AF

Sent.

Hi BM, now I am using the window client for testing, and I found that the network's connection is 0, does it works well in this dry?

Latest windows client won't work
Title: Re: Dry Run 5: The Final Countdown
Post by: clout on June 24, 2014, 05:19:48 pm
why is it that when I attempt to make more than 4 or 5 transactions in succession my wallet says that I have insufficient funds even when my balance exceeds the sum of the transfers? these are all transfers to myself.
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 05:22:10 pm
why is it that when I attempt to make more than 4 or 5 transactions in succession my wallet says that I have insufficient funds even when my balance exceeds the sum of the transfers? these are all transfers to myself.

Same as in bitcoin - when you make a transfer the remaining balance is in a new deposit ("trx output") which is not yet confirmed. In bitcoin there's an option to spend from "unconfirmed" outputs, we should add something similar probably.
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 24, 2014, 05:24:22 pm
Thank you alt for your 1000 trx spam test, you fractured the network with that load and identified several bugs that we are trying to track down.

(http://bitshares.org/documentation/forks.png)
It's my pleasure to work with you guys for the great target.  ;)

historical moments for sure !

(http://t0.gstatic.com/images?q=tbn:ANd9GcTGqgT5auPQwuY2hVqphaVrcGzSGju6FXc0u9Q86DCdcf6_-zWi8g)
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 24, 2014, 05:51:48 pm
Dan just pushed a possible fix for the forking issue, please update

EDIT: LOL nevermind he didn't push and went off to lunch. Hold tight for a little bit.
Title: Re: Dry Run 5: The Final Countdown
Post by: Xeldal on June 24, 2014, 06:08:52 pm
Dammit, burnt my house down already.  Left my keys inside as well.  Doh!    :-[
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 24, 2014, 06:22:34 pm
I've reproduced the "flood" fork using batch wallet_transfer [lots of data lots of times].
Got a lot of different errors in logs, don't know if it will be of any use I can provide it if needed.

The result is that the client became irresponsive even after restart.
If I use the initial datadir the client stops responding after 5-10 seconds but is still producing logs.
I had to create new datadir and copy the wallet so I can continue testing.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 06:52:15 pm
Dan just pushed a possible fix for the forking issue, please update

EDIT: LOL nevermind he didn't push and went off to lunch. Hold tight for a little bit.

I did push, just to the approval voting branch.
Title: Re: Dry Run 5: The Final Countdown
Post by: wackou on June 24, 2014, 07:27:36 pm
I wrote some scripts these last days for the dry runs to help me build an updated version of the bitshares client and run it easily, and thought some people might find them useful, so I put them here:

https://github.com/wackou/bitshares_delegate_tools

Comments/patches welcome ;)
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 07:35:33 pm
I just updated the Mac client to 0.0.5 (link in OP)
Title: Re: Dry Run 5: The Final Countdown
Post by: bitcoinerS on June 24, 2014, 07:42:34 pm
Is there a way to dump list_errors to a file?
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 24, 2014, 07:52:15 pm
I just updated the Mac client to 0.0.5 (link in OP)

What about the windows client?
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 08:32:45 pm
Is there a way to dump list_errors to a file?
Adding this feature now.
Title: Re: Dry Run 5: The Final Countdown
Post by: clout on June 24, 2014, 08:52:03 pm
I just updated the Mac client to 0.0.5 (link in OP)

link doesnt work
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 08:58:21 pm
I just updated the Mac client to 0.0.5 (link in OP)

link doesnt work

Fixed.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 24, 2014, 09:09:41 pm
We seem to be back to smooth sailing... alt, care to try your flood test again?
Title: Re: Dry Run 5: The Final Countdown
Post by: vikram on June 24, 2014, 09:20:41 pm
Is there a way to dump list_errors to a file?
Adding this feature now.

Done: https://github.com/BitShares/bitshares_toolkit/commit/b01e3293f1d740d734b115e02ccca45ca98d9f09
Title: Re: Dry Run 5: The Final Countdown
Post by: vikram on June 24, 2014, 09:53:46 pm
wallet_account_register <account_name> <pay_from_account> [public_data] [delegate_production_fee]

Code: [Select]
  delegate_production_fee (uint32_t, optional, defaults to 255): A value between 0 and 100% delegates, 255 for non delegates

I am confused. What is delegate production fee?

It defines the percent of transaction fees that your delegate will keep as a fee for producing the block, the rest are paid as dividends to the shareholders.   A value between 0 and 100.

Should be renamed to "delegate pay rate"

Done: https://github.com/BitShares/bitshares_toolkit/commit/613235eab279743b819af634249f11154b8352b7
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 25, 2014, 12:16:41 am
We seem to be back to smooth sailing... alt, care to try your flood test again?
I have test again.
805 transactions is done very soon, these are include in block 2614,2615.
the others 195 is  pending a while, finally include in block 2623,2624
fork happened at block 2614  and switch fork works.
I think bts101 is test at the same time, other 600 transactions are include in block 2614,2615

another issue is list_erros hung a long time about 5 minutes, because never clear.

anyway  it works very well now  :)
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 12:19:08 am
We seem to be back to smooth sailing... alt, care to try your flood test again?
I have test again.
805 transactions is done very soon, these are include in block 2614,2615.
the others 195 is  pending a while, finally include in block 2623,2624
fork happened at block 2614  and switch fork works.
I think bts101 is test at the same time, other 600 transactions are include in block 2614,2615

another issue is list_erros hung a long time about 5 minutes, because never clear.

anyway  it works very well now  :)

We're doing some spam of our own and it seems to still fragment the network... think it's a mix of

* long block processing time
* long block propogation (block not getting priority over trx)
* someone still didn't update after fork resolution bugfix
Title: Re: Dry Run 5: The Final Countdown
Post by: cdryan on June 25, 2014, 12:57:14 am
@bytemaster ;@toast
5轮测试后,看起来之前一直没有真正找到分岔的原因,真正定位到问题上。建议:
1.在测试版中,可以所有的代理接点连接到一个固定的接点,当代理接点生成一个块的时候,将生成的需要的LOG信息按顺序发送到这个固定的接点,这样在这个固定的接点上就可以很清楚了解什么时间,某个代表,导致了分岔,有一个整体的了解,配合代理接点更详细的LOG信息,真正定位问题点。
2.从已经开发的POS币上借鉴阻止分岔的好的设计方法。
3.如果在实际运行中发生了分岔,如何处理。
Title: Re: Dry Run 5: The Final Countdown
Post by: sfinder on June 25, 2014, 01:02:53 am
bm and toast, do you think we need to schedule a full load testing across continents?
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 01:05:47 am
@bytemaster ;@toast
5轮测试后,看起来之前一直没有真正找到分岔的原因,真正定位到问题上。建议:
1.在测试版中,可以所有的代理接点连接到一个固定的接点,当代理接点生成一个块的时候,将生成的需要的LOG信息按顺序发送到这个固定的接点,这样在这个固定的接点上就可以很清楚了解什么时间,某个代表,导致了分岔,有一个整体的了解,配合代理接点更详细的LOG信息,真正定位问题点。
2.从已经开发的POS币上借鉴阻止分岔的好的设计方法。
3.如果在实际运行中发生了分岔,如何处理。

Each case of fork has been different. We have fixed all previous ones and discover new ones when we do more serious stress testing. Existing POS systems are too different for us to learn from them. Suggestion to have centralized server doesn't help because central server is just like a delegate - if server works then delegate works, if delegate doesn't then server wouldn't.
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 01:09:15 am
bm and toast, do you think we need to schedule a full load testing across continents?

Doing that already, have delegates on several continents and all are bugs now occur only when we stress-test with high transaction volume (several times bitcoin max tx/second)
Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 25, 2014, 01:17:58 am
can i get some funds pls XTS5Ys6UMYxMYyQoNTpihwrVtXTyjWD1JLBkLYmx5AdeFHYtwKdhC (cassyo)
Title: Re: Dry Run 5: The Final Countdown
Post by: Nimrod on June 25, 2014, 01:24:04 am
new client

>> blockchain_list_forks

[
  2299,
  2577,
  2591,
  2634,
  2676,
  2681,
  2690
]
Title: Re: Dry Run 5: The Final Countdown
Post by: sfinder on June 25, 2014, 01:32:56 am
Great. I did some testing today and found most of transactions can be done in one confirmation. It will be a milestone . Good work .... ask dan to spend time with family if he get the chance and do not spend time with non technical questions on the forum

bm and toast, do you think we need to schedule a full load testing across continents?

Doing that already, have delegates on several continents and all are bugs now occur only when we stress-test with high transaction volume (several times bitcoin max tx/second)
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 02:04:18 am
appears a lot of people haven't updated since fork resolution code:

bts101/2/3
emski  ?
immortal ?
wackou?
asia?
taolj?
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 25, 2014, 02:12:44 am
I think  I have updated to the fork fix code,  I will try make a fresh compile.

can't compile the latest code, seems missing file.
Code: [Select]
CMake Error at libraries/fc/CMakeLists.txt:233 (add_executable):
  Cannot find source file:

    tests/udt_client.cpp

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx

Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 25, 2014, 02:15:54 am
I registered account "dcchong". Then, I send 5k xts to "dcchong" with another account "dcchong-test".(dcchong-test has 10k xts)

"dcchong" account show 0 xts, and "dcchong-test" account show 5k xts. Then I rescan blockchain with command "wallet_rescan_blockchain",

"dcchong" account show 5k xts, and "dcchong-test" account show 10k xts back, is it nomal?

(http://v1.freep.cn/3tb_140625101454gvpe512293.png)

(http://v1.freep.cn/3tb_1406251015265skk512293.png)
Title: Re: Dry Run 5: The Final Countdown
Post by: lzr1900 on June 25, 2014, 02:17:26 am
can i get some funds pls XTS5Ys6UMYxMYyQoNTpihwrVtXTyjWD1JLBkLYmx5AdeFHYtwKdhC (cassyo)
Sent you 50 XTS.
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 02:22:06 am
I registered account "dcchong". Then, I send 5k xts to "dcchong" with another account "dcchong-test".(dcchong-test has 10k xts)

"dcchong" account show 0 xts, and "dcchong-test" account show 5k xts. Then I rescan blockchain with command "wallet_rescan_blockchain",

"dcchong" account show 5k xts, and "dcchong-test" account show 10k xts back, is it nomal?

(http://v1.freep.cn/3tb_140625101454gvpe512293.png)

(http://v1.freep.cn/3tb_1406251015265skk512293.png)

rescan again in a few blocks and let us know.. seems like wallet sync bug
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 25, 2014, 02:24:14 am
I registered account "dcchong". Then, I send 5k xts to "dcchong" with another local account "dcchong-test".(dcchong-test has 10k xts)

"dcchong" account show 0 xts, and "dcchong-test" account show 5k xts. Then I rescan blockchain with command "wallet_rescan_blockchain",

"dcchong" account show 5k xts, and "dcchong-test" account show 10k xts back, is it normal?

(http://v1.freep.cn/3tb_140625101454gvpe512293.png)

(http://v1.freep.cn/3tb_1406251015265skk512293.png)


And then I spend xts with registered account "dcchong", it says insufficient funds:

RPC Server Error
In method 'wallet_transfer': 20010 insufficient_funds: insufficient funds {"required":"100.10000 XTS","available":"0.00000 XTS"} bitshares wallet.cpp:220 withdraw_to_transaction {"amount":10010000,"asset_id":0,"from_account_address":"XTSKTAhQ4BjSaYs3CaLy5o3mnV3t6qWmxBZS","trx":{"expiration":null,"delegate_slate_id":null,"operations":[],"signatures":[]},"required_signatures":[]} bitshares wallet.cpp:221 withdraw_to_transaction {"real_amount_to_transfer":100,"amount_to_transfer_symbol (500)
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 02:27:52 am
I just updated the Mac client to 0.0.5 (link in OP)

What about the windows client?

What about the windows client?
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 02:31:31 am
I think  I have updated to the fork fix code,  I will try make a fresh compile.

can't compile the latest code, seems missing file.
Code: [Select]
CMake Error at libraries/fc/CMakeLists.txt:233 (add_executable):
  Cannot find source file:

    tests/udt_client.cpp

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx


My bad, I forgot to add files.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 02:31:49 am
I just updated the Mac client to 0.0.5 (link in OP)

What about the windows client?

What about the windows client?

Valentine is working on that.
Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 25, 2014, 02:32:21 am
I try to rescan again, these are screenshot.

(http://v2.freep.cn/3tb_140625103107hltw512293.png)

(http://v1.freep.cn/3tb_14062510303566ri512293.png)
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 25, 2014, 02:45:51 am
hi bm,  still can't compile.

Code: [Select]
[ 46%] Built target udt
[ 47%] Building CXX object libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o
/root/bitshares_toolkit/libraries/fc/tests/udt_client.cpp: In function ‘int main()’:
/root/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:17:41: error: ‘memset’ was not declared in this scope
    memset(&(serv_addr.sin_zero), '\0', 8);
                                         ^
/root/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:26:18: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
    char* hello = "hello world! 3\n";
                  ^
/root/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:27:59: error: ‘strlen’ was not declared in this scope
    if (UDT::ERROR == UDT::send(client, hello, strlen(hello) + 1, 0))
                                                           ^
make[2]: *** [libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o] Error 1
make[1]: *** [libraries/fc/CMakeFiles/udt_client.dir/all] Error 2
make: *** [all] Error 2

Title: Re: Dry Run 5: The Final Countdown
Post by: dcchong on June 25, 2014, 02:59:11 am
After a few minutes I unlocked my wallet, my registered account "dcchong" is changed to "lzr1992".     :-[

(http://v1.freep.cn/3tb_140625105503j1j9512293.jpg)

Transactions history also changed.

(http://v2.freep.cn/3tb_140625105728deol512293.png)
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 03:01:18 am
After a few minutes I unlocked my wallet, my registered account "dcchong" is changed to "lzr1992".     :-[

(http://v1.freep.cn/3tb_140625105503j1j9512293.jpg)

Transactions history also changed.

(http://v2.freep.cn/3tb_140625105728deol512293.png)

fork/wallet syncing issue, Dan knows how to fix this and will do it tomorrow.
Title: Re: Dry Run 5: The Final Countdown
Post by: sfinder on June 25, 2014, 03:17:58 am
not able to compile . any comments

Code: [Select]
Scanning dependencies of target udt_client
[ 47%] Building CXX object libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp: In function 鈥榠nt main()鈥

              /home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:17:41: error: 鈥榤emset鈥was not declared in this scope
    memset(&(serv_addr.sin_zero), '\0', 8);
                                         ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:26:18: warning: deprecated conversion from string constant to 鈥榗har*鈥[-Wwrite-strings]
    char* hello = "hello world! 3\n";
                  ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:27:59: error: 鈥榮trlen鈥was not declared in this scope
    if (UDT::ERROR == UDT::send(client, hello, strlen(hello) + 1, 0))
                                                           ^
make[2]: *** [libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o] Error 1
make[1]: *** [libraries/fc/CMakeFiles/udt_client.dir/all] Error 2
make: *** [all] Error 2
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 03:22:05 am
not able to compile . any comments

Code: [Select]
Scanning dependencies of target udt_client
[ 47%] Building CXX object libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp: In function 鈥榠nt main()鈥

              /home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:17:41: error: 鈥榤emset鈥was not declared in this scope
    memset(&(serv_addr.sin_zero), '\0', 8);
                                         ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:26:18: warning: deprecated conversion from string constant to 鈥榗har*鈥[-Wwrite-strings]
    char* hello = "hello world! 3\n";
                  ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:27:59: error: 鈥榮trlen鈥was not declared in this scope
    if (UDT::ERROR == UDT::send(client, hello, strlen(hello) + 1, 0))
                                                           ^
make[2]: *** [libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o] Error 1
make[1]: *** [libraries/fc/CMakeFiles/udt_client.dir/all] Error 2
make: *** [all] Error 2

I'll comment that stuff out...
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 03:24:35 am
not able to compile . any comments

Code: [Select]
Scanning dependencies of target udt_client
[ 47%] Building CXX object libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp: In function 鈥榠nt main()鈥

              /home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:17:41: error: 鈥榤emset鈥was not declared in this scope
    memset(&(serv_addr.sin_zero), '\0', 8);
                                         ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:26:18: warning: deprecated conversion from string constant to 鈥榗har*鈥[-Wwrite-strings]
    char* hello = "hello world! 3\n";
                  ^
/home/daniel/bitshares_toolkit/libraries/fc/tests/udt_client.cpp:27:59: error: 鈥榮trlen鈥was not declared in this scope
    if (UDT::ERROR == UDT::send(client, hello, strlen(hello) + 1, 0))
                                                           ^
make[2]: *** [libraries/fc/CMakeFiles/udt_client.dir/tests/udt_client.cpp.o] Error 1
make[1]: *** [libraries/fc/CMakeFiles/udt_client.dir/all] Error 2
make: *** [all] Error 2

I'll comment that stuff out...

git pull
git submodule update
Title: Re: Dry Run 5: The Final Countdown
Post by: yangsbo on June 25, 2014, 03:33:04 am
I can not use bitsharexts windows wallet now . always blocks are syncing .
who have available windows wallet.
Title: Re: Dry Run 5: The Final Countdown
Post by: ebit on June 25, 2014, 03:34:37 am
I can not use bitsharexts windows wallet now . always blocks are syncing .
who have available windows wallet.

none
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 03:35:04 am
Am I on the forked chain ?

Code: [Select]
heyddryrun5 (unlocked) >>> info
{
  "blockchain_head_block_num": 2808,
  "blockchain_head_block_time": "20140625T033200",
  "blockchain_head_block_time_rel": "14 seconds old",
  "blockchain_confirmation_requirement": 302,
  "blockchain_average_delegate_participation": 61.773700305810401,
  "network_num_connections": 16,
  "ntp_time": "NTP time not available",
  "ntp_error_seconds": "NTP time not available",
  "wallet_unlocked_seconds_remaining": 9884,
  "wallet_next_block_production_time": "20140625T033530",
  "wallet_seconds_until_next_block_production": 196,
  "wallet_local_time": "20140625T033214",
  "blockchain_random_seed": "2d4a4addb3152c514e1dc8bfbce50e75ca7c532a",
  "blockchain_shares": 199999336346077,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T061658",
  "wallet_version": 100
}
heyddryrun5 (unlocked) >>> about
{
  "bitshares_toolkit_revision": "eb5bed05842718ac07ee26a20e264269f62efd42",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "3de924b33647a9a547b772a58415835f021f92b3",
  "fc_revision_age": "79 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 02:29:00"
}
heyddryrun5 (unlocked) >>> blockchain_list_forks
[
  1842,
  2035,
  2577,
  2591,
  2606,
  2607,
  2744,
  2788,
  2805
]
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 03:41:52 am
Am I on the forked chain ?

Code: [Select]
heyddryrun5 (unlocked) >>> info
{
  "blockchain_head_block_num": 2808,
  "blockchain_head_block_time": "20140625T033200",
  "blockchain_head_block_time_rel": "14 seconds old",
  "blockchain_confirmation_requirement": 302,
  "blockchain_average_delegate_participation": 61.773700305810401,
  "network_num_connections": 16,
  "ntp_time": "NTP time not available",
  "ntp_error_seconds": "NTP time not available",
  "wallet_unlocked_seconds_remaining": 9884,
  "wallet_next_block_production_time": "20140625T033530",
  "wallet_seconds_until_next_block_production": 196,
  "wallet_local_time": "20140625T033214",
  "blockchain_random_seed": "2d4a4addb3152c514e1dc8bfbce50e75ca7c532a",
  "blockchain_shares": 199999336346077,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T061658",
  "wallet_version": 100
}
heyddryrun5 (unlocked) >>> about
{
  "bitshares_toolkit_revision": "eb5bed05842718ac07ee26a20e264269f62efd42",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "3de924b33647a9a547b772a58415835f021f92b3",
  "fc_revision_age": "79 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 02:29:00"
}
heyddryrun5 (unlocked) >>> blockchain_list_forks
[
  1842,
  2035,
  2577,
  2591,
  2606,
  2607,
  2744,
  2788,
  2805
]

Looks like no, you can tell from:    "blockchain_head_block_time_rel": "14 seconds old",
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 25, 2014, 05:04:20 am
@bytemaster ;@toast
5轮测试后,看起来之前一直没有真正找到分岔的原因,真正定位到问题上。建议:
1.在测试版中,可以所有的代理接点连接到一个固定的接点,当代理接点生成一个块的时候,将生成的需要的LOG信息按顺序发送到这个固定的接点,这样在这个固定的接点上就可以很清楚了解什么时间,某个代表,导致了分岔,有一个整体的了解,配合代理接点更详细的LOG信息,真正定位问题点。
2.从已经开发的POS币上借鉴阻止分岔的好的设计方法。
3.如果在实际运行中发生了分岔,如何处理。

Each case of fork has been different. We have fixed all previous ones and discover new ones when we do more serious stress testing. Existing POS systems are too different for us to learn from them. Suggestion to have centralized server doesn't help because central server is just like a delegate - if server works then delegate works, if delegate doesn't then server wouldn't.
Dear BM and Toast
     I notice chain always have fork problem , I am not a programer,cannot been able to read C++ code. but can you explain some thing , maybe some question I ask are foolish.
1.how to judge which chain is the longer/main chain ?  chain honored by delegates have more voting/stake?
   
2.I think Dpos is a complicated algorithm, it many regulation,if all clients are honest,  which delegate have more chance to create block 
    (1).have more stake ?
    (2).have more voting ?
    (3).have network with more high speed ?
    (4).honest one ?
3.according to timestamp of block, does each client have the ability to judge if block itself received is the newest one  or very close to the newest ?  does client can judge if itself in a main chain or fork chain?
4.if a client/delegate doubt/find itself is in a fork chain , what itself can do now ?   inquiry from P2P network continually to find the main chain, or there is a seed node every clent/delegate can connect to check if itself is in main chain  if it doubt itself is in fork chain ?
5.if there are two chains in the P2P network.  and one client/delegate received two chains both , how to compare the two chains and select the longer one then broadcast longer one to P2P network again ,then make it much longer/longest.


Br
BTSDac
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 05:14:51 am
@bytemaster ;@toast
5轮测试后,看起来之前一直没有真正找到分岔的原因,真正定位到问题上。建议:
1.在测试版中,可以所有的代理接点连接到一个固定的接点,当代理接点生成一个块的时候,将生成的需要的LOG信息按顺序发送到这个固定的接点,这样在这个固定的接点上就可以很清楚了解什么时间,某个代表,导致了分岔,有一个整体的了解,配合代理接点更详细的LOG信息,真正定位问题点。
2.从已经开发的POS币上借鉴阻止分岔的好的设计方法。
3.如果在实际运行中发生了分岔,如何处理。

Each case of fork has been different. We have fixed all previous ones and discover new ones when we do more serious stress testing. Existing POS systems are too different for us to learn from them. Suggestion to have centralized server doesn't help because central server is just like a delegate - if server works then delegate works, if delegate doesn't then server wouldn't.
Dear BM and Toast
     I notice chain always have fork problem , I am not a programer,cannot been able to read C++ code. but can you explain some thing , maybe some question I ask are foolish.
1.how to judge which chain is the longer/main chain ?  chain honored by delegates have more voting/stake?
   
2.I think Dpos is a complicated algorithm, it many regulation,if all clients are honest,  which delegate have more chance to create block 
    (1).have more stake ?
    (2).have more voting ?
    (3).have network with more high speed ?
    (4).honest one ?
3.according to timestamp of block, does each client have the ability to judge if block itself received is the newest one  or very close to the newest ?  does client can judge if itself in a main chain or fork chain?
4.if a client/delegate doubt/find itself is in a fork chain , what itself can do now ?   inquiry from P2P network continually to find the main chain, or there is a seed node every clent/delegate can connect to check if itself is in main chain  if it doubt itself is in fork chain ?
5.if there are two chains in the P2P network.  and one client/delegate received two chains both , how to compare the two chains and select the longer one then broadcast longer one to P2P network again ,then make it much longer/longest.


Br
BTSDac

1) Longer simply means more blocks.
2) Each delegate in top 101 (elected by stake-vote) has a chance to produce a block once per round.
3) The client decides it is on the main chain if the most recent block has the most recent expected timestamp and it is the longest known chain. A client can know for sure it is on the main chain if more than half of the last round of delegates signed blocks on the chain it is currently on.
4) Just keep asking peers if they know a longer chain, just like bitcoin
5) Again, simply which chain is longer.


Our forking problems now are a result of two issues: long block production time and problems with transactions it thinks are duplicates when switching back to the main fork.
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 05:18:56 am
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       
Title: Re: Dry Run 5: The Final Countdown
Post by: toast on June 25, 2014, 05:19:54 am
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       

Doesn't matter, either 0 or >= 0.
We will change to "true/false" soon.
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 05:40:41 am
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       

Doesn't matter, either 0 or >= 0.
We will change to "true/false" soon.

Now I am trusting 3 delegates, will all of them get my votes every time I make a 'wallet_transfer' ?

If I am trusting more than 33 delegates, at most 33 of them get my votes per each transaction, right ?
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 05:44:29 am
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       

Doesn't matter, either 0 or >= 0.
We will change to "true/false" soon.

Now I am trusting 3 delegates, will all of them get my votes every time I make a 'wallet_transfer' ?

If I am trusting more than 33 delegates, at most 33 of them get my votes per each transaction, right ?

When you make a transfer it never uses your full set of delegates (that would be like a fingerprint tying it all together)... instead it uses a random subset of your trusted delegates.
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 05:47:13 am
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       

Doesn't matter, either 0 or >= 0.
We will change to "true/false" soon.

Now I am trusting 3 delegates, will all of them get my votes every time I make a 'wallet_transfer' ?

If I am trusting more than 33 delegates, at most 33 of them get my votes per each transaction, right ?

When you make a transfer it never uses your full set of delegates (that would be like a fingerprint tying it all together)... instead it uses a random subset of your trusted delegates.

So in such case, my votes will go to one or two of the three positive trusted delegates, but never all of them, right ?
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 05:53:47 am
appears a lot of people haven't updated since fork resolution code:

bts101/2/3
emski  ?
immortal ?
wackou?
asia?
taolj?

I've updated when i first saw this:
Quote
Dan just pushed a possible fix for the forking issue, please update
Then I went to sleep. I'll update again now and test.

You may add "angel" to the above list.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 05:56:39 am
I have made some updates to the client that appear to have reduced forks significantly.   TITAN transactions are relatively expensive to scan, if you have a wallet with even one account in it, then scanning a block with 1000 trxs could take several seconds.  If you have 100 accounts, it could take minutes. 

For this reason I have disabled the wallet scanning for wallets that have enabled delegates.   I do not recommend using your delegate account as a receiving account in the same wallet. 

We will be making optimizations in the future that will multi-thread this step and move it out of the critical path of block validation.
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 06:08:12 am
after my stress test:
Code: [Select]
emski (unlocked) >>> info
{
  "blockchain_head_block_num": 2941,
  "blockchain_head_block_time": "20140625T060600",
  "blockchain_head_block_time_rel": "45 seconds old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 58.720930232558139,
  "network_num_connections": 32,
  "ntp_time": "20140625T060645.437978",
  "ntp_error_seconds": 0.001075,
  "wallet_unlocked_seconds_remaining": 999999548,
  "wallet_next_block_production_time": "20140625T061000",
  "wallet_seconds_until_next_block_production": 195,
  "wallet_local_time": "20140625T060645",
  "blockchain_random_seed": "1cf580c025e9d7d048da0307920d80b6d256c3e8",
  "blockchain_shares": 199999133938247,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "19100126T011737",
  "wallet_version": 100
}
--- in sync with p2p network
emski (unlocked) >>> blockchain_list_forks
[
  1842,
  2577,
  2631,
  2938,
  2940
]
--- there are now 33 active connections to the p2p network
--- in sync with p2p network
emski (unlocked) >>> about
{
  "bitshares_toolkit_revision": "c0a8c268cd65dd7a7e4a7af0ef6f5c6c1ef763f8",
  "bitshares_toolkit_revision_age": "32 minutes ago",
  "fc_revision": "87a93940d046cc6715b67d9380dd280c27bdd867",
  "fc_revision_age": "10 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 08:57:10"
}
The client seems to be responsive now.
Title: Re: Dry Run 5: The Final Countdown
Post by: alt on June 25, 2014, 06:13:16 am
I have made some updates to the client that appear to have reduced forks significantly.   TITAN transactions are relatively expensive to scan, if you have a wallet with even one account in it, then scanning a block with 1000 trxs could take several seconds.  If you have 100 accounts, it could take minutes. 

For this reason I have disabled the wallet scanning for wallets that have enabled delegates.   I do not recommend using your delegate account as a receiving account in the same wallet. 

We will be making optimizations in the future that will multi-thread this step and move it out of the critical path of block validation.
this make sense

来自我的 HUAWEI P7-L00 上的 Tapatalk

Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:13:31 am
Is someone doing some spam testing?
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 06:15:26 am
Is someone doing some spam testing?
Me, results posted above.
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 06:21:13 am
well that is odd
Code: [Select]
emski (unlocked) >>> info
{
  "blockchain_head_block_num": 2948,
  "blockchain_head_block_time": "20140625T061600",
  "blockchain_head_block_time_rel": "53 seconds old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 58.550724637681157,
  "network_num_connections": 31,
  "ntp_time": "20140625T061653.296005",
  "ntp_error_seconds": 0.001075,
  "wallet_unlocked_seconds_remaining": 999998940,
  "wallet_next_block_production_time": "20140625T061900",
  "wallet_seconds_until_next_block_production": 127,
  "wallet_local_time": "20140625T061653",
  "blockchain_random_seed": "b0f162d7132eff5f36b57b5302fd9836386540b6",
  "blockchain_shares": 199999115209829,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "19100126T011737",
  "wallet_version": 100
}
emski (unlocked) >>> blockchain_list_forks
[
  1842,
  2577,
  2631,
  2938,
  2940,
  2943
]
--- there are now 30 active connections to the p2p network
emski (unlocked) >>> pure virtual method called
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  receive_from: Resource temporarily unavailable
Aborted (core dumped)
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 06:23:19 am
I've noticed that the CPU usages skyrockets during stress tests.
I'll increase the dedicated cores and see what happens.

EDIT: I still have a lot of pending transactions...
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:29:54 am
I've noticed that the CPU usages skyrockets during stress tests.
I'll increase the dedicated cores and see what happens.

The code is mostly single threaded right now..  we have a steady test running at 1 trx every 5 seconds that should run until fees eat up the funds. 

It appears that the stress test is causing some forking, likely because many delegates haven't updated to the very latest. 

Forks don't bother me too much as long as they resolve themselves in a timely manner.... it appears that is the case now.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:33:08 am
I just noticed a block with a timestamp almost 30 seconds in the future... very curious. 
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 25, 2014, 06:43:17 am
@bytemaster ;@toast
5轮测试后,看起来之前一直没有真正找到分岔的原因,真正定位到问题上。建议:
1.在测试版中,可以所有的代理接点连接到一个固定的接点,当代理接点生成一个块的时候,将生成的需要的LOG信息按顺序发送到这个固定的接点,这样在这个固定的接点上就可以很清楚了解什么时间,某个代表,导致了分岔,有一个整体的了解,配合代理接点更详细的LOG信息,真正定位问题点。
2.从已经开发的POS币上借鉴阻止分岔的好的设计方法。
3.如果在实际运行中发生了分岔,如何处理。

Each case of fork has been different. We have fixed all previous ones and discover new ones when we do more serious stress testing. Existing POS systems are too different for us to learn from them. Suggestion to have centralized server doesn't help because central server is just like a delegate - if server works then delegate works, if delegate doesn't then server wouldn't.
Dear BM and Toast
     I notice chain always have fork problem , I am not a programer,cannot been able to read C++ code. but can you explain some thing , maybe some question I ask are foolish.
1.how to judge which chain is the longer/main chain ?  chain honored by delegates have more voting/stake?
   
2.I think Dpos is a complicated algorithm, it many regulation,if all clients are honest,  which delegate have more chance to create block 
    (1).have more stake ?
    (2).have more voting ?
    (3).have network with more high speed ?
    (4).honest one ?
3.according to timestamp of block, does each client have the ability to judge if block itself received is the newest one  or very close to the newest ?  does client can judge if itself in a main chain or fork chain?
4.if a client/delegate doubt/find itself is in a fork chain , what itself can do now ?   inquiry from P2P network continually to find the main chain, or there is a seed node every clent/delegate can connect to check if itself is in main chain  if it doubt itself is in fork chain ?
5.if there are two chains in the P2P network.  and one client/delegate received two chains both , how to compare the two chains and select the longer one then broadcast longer one to P2P network again ,then make it much longer/longest.


Br
BTSDac

1) Longer simply means more blocks.
2) Each delegate in top 101 (elected by stake-vote) has a chance to produce a block once per round.
3) The client decides it is on the main chain if the most recent block has the most recent expected timestamp and it is the longest known chain. A client can know for sure it is on the main chain if more than half of the last round of delegates signed blocks on the chain it is currently on.
4) Just keep asking peers if they know a longer chain, just like bitcoin
5) Again, simply which chain is longer.


Our forking problems now are a result of two issues: long block production time and problems with transactions it thinks are duplicates when switching back to the main fork.
Code: [Select]
--- there are now 45 active connections to the p2p network
--- there are now 46 active connections to the p2p network
--- there are now 47 active connections to the p2p network
roy (unlocked) >>> info
{
  "blockchain_head_block_num": 2633,
  "blockchain_head_block_time": "20140625T062930",
  "blockchain_head_block_time_rel": "8 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 45.701357466063349,
  "network_num_connections": 47,
  "ntp_time": "20140625T063707.294604",
  "ntp_error_seconds": -0.014511,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T063707",
  "blockchain_random_seed": "736362e9df6cd562307b713aae1eb75c3d11b88d",
  "blockchain_shares": 199999351280463,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T023103",
  "wallet_version": 100

I think I am on a fork chain now ,but it seems that the client didn`t realize it , you can see this client have 46 p2p active connection,
if the client realize itself is in fork chain ,why he don`t ignore these 46 p2p active connection ,becasue these node all at the fork chain,   
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 06:43:52 am
I just noticed a block with a timestamp almost 30 seconds in the future... very curious.
Wasnt me, at least not intentionally. My server's time is synchronized via ntp.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:46:51 am
We do not disconnect nodes that are on a fork at the moment.  So you cannot use the connection count as an indicator of your fork status.
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 25, 2014, 06:48:25 am
I have updated to the latest code, and  doing some spam testing. why I get negative delegate votes?  ???

see from the block explorer,like block #2972

Code: [Select]
NET DELEGATE VOTES
bts101:  -0.1 XTS
bts102:  -0.1 XTS
bts103:  1 XTS

Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:48:42 am
Code: [Select]
HEIGHT    TIME                          TXN COUNT      SIGNING DELEGATE                                                 SIZE   
--------------------------------------------------------------------------------------------------------------------------------
2976      2014-06-25T06:43:30           38             vikram11                                                         11548   
2975      2014-06-25T06:39:00           19             init95                                                           4761   
2974      2014-06-25T06:38:30           167            init79                                                           40430   
2973      2014-06-25T06:38:00           235            init51                                                           56818   
2972      2014-06-25T06:37:30           113            init92                                                           27511   
2971      2014-06-25T06:37:00           466            init81                                                           112489 
2970      2014-06-25T06:36:30           310            immortal                                                         74989   
2969      2014-06-25T06:35:00           190            init52                                                           46074   
2968      2014-06-25T06:34:30           722            init54                                                           174862 
2967      2014-06-25T06:34:00           870            init76                                                           209853 
2966      2014-06-25T06:33:00           868            init58                                                           209664 
2965      2014-06-25T06:32:00           0              vikram6                                                          182     
2964      2014-06-25T06:31:30           2              init84                                                           856     
2963      2014-06-25T06:31:00           481            init100                                                          117256 
2962      2014-06-25T06:30:30           0              bts102                                                           182     
2961      2014-06-25T06:29:00           465            init77                                                           113400 
2960      2014-06-25T06:28:00           226            init45                                                           55326   
2959      2014-06-25T06:27:30           368            init66                                                           90929   
2958      2014-06-25T06:27:00           0              vikram10                                                         182     
2957      2014-06-25T06:25:30           2              init49                                                           664 

Looking good.. that is some serious stress testing... transaction rates north of Bitcoins 7 trx per second...
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 06:50:26 am
I am doing some spam testing. why I get negative delegate votes?  ???

see from the block explorer,like block #2972

Code: [Select]
NET DELEGATE VOTES
bts101:  -0.1 XTS
bts102:  -0.1 XTS
bts103:  1 XTS


This is very curious.... looks like a TRX fee amount.   
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 25, 2014, 06:56:28 am
We do not disconnect nodes that are on a fork at the moment.  So you cannot use the connection count as an indicator of your fork status.
I dont konw if you reply to me ,
Code: [Select]
  "blockchain_head_block_num": 2633,
  "blockchain_head_block_time": "20140625T062930",
  "blockchain_head_block_time_rel": "28 minutes old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 44.888888888888886,
  "network_num_connections": 45,
  "ntp_time": "20140625T065726.868608",
  "ntp_error_seconds": -0.014512000000000001,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T065726",
  "blockchain_random_seed": "736362e9df6cd562307b713aae1eb75c3d11b88d",
  "blockchain_shares": 199999351280463,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140624T023103",
  "wallet_version": 100

Code: [Select]
{
  "bitshares_toolkit_revision": "5c7b143f810a60f168dcae3dbdb3099aa3dde1a0",
  "bitshares_toolkit_revision_age": "32 hours ago",
  "fc_revision": "3de924b33647a9a547b772a58415835f021f92b3",
  "fc_revision_age": "83 hours ago",
  "compile_date": "compiled on Jun 23 2014 at 20:33:28"
it is obviously  that I am on a fork chain , but it seems that the clent did`t do any effort to back to main chain .
"network_num_connections": 45
and I have 45 connections,  it is close to max num of connections  50, I don`t konw if it  weaken the ability of client to find new node that on the main chain

Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 07:00:07 am
blockchain_get_pending_transactions shows []
while
wallet_account_transaction_history shows lots of pending transactions remaining (these from the stress test)/
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 07:04:02 am
Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_my_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL    BLOCK PRODUCTION ENABLED
heyd-naive                         XTS54aGvENZaziDPoTBWB8DVFzcTpezKm8stU7kbpQ7yuZZ483pzN           2014-06-24T01:26:30   NO             0              N/A                     
heyd-simple                        XTS6XSi2PDstduVswZycvq8EwenbpERqQUq57QEm6XpbZjPj7XQz3           2014-06-24T01:26:30   NO             0              N/A                     
heyd-young                         XTS7YRXr7X4euUsQoEF8R4M9ErGxaNGEKYfpqMNYvHFPSsQpciyLG           2014-06-24T01:26:30   NO             0              N/A                     
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10             YES                     
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40             YES                     
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30             YES                     

too-young
Code: [Select]
heyddryrun5 (unlocked) >>> blockchain_get_delegate_block_stats too-young
[[
    621,{
      "missed": false,
      "latency": null
    }
  ],[
    713,{
      "missed": false,
      "latency": null
    }
  ],[
    807,{
      "missed": false,
      "latency": null
    }
  ],[
    894,{
      "missed": false,
      "latency": null
    }
  ],[
    962,{
      "missed": false,
      "latency": null
    }
  ],[
    1088,{
      "missed": false,
      "latency": null
    }
  ],[
    1178,{
      "missed": false,
      "latency": null
    }
  ],[
    1278,{
      "missed": false,
      "latency": null
    }
  ],[
    1367,{
      "missed": false,
      "latency": null
    }
  ],[
    1421,{
      "missed": false,
      "latency": null
    }
  ],[
    1510,{
      "missed": false,
      "latency": null
    }
  ],[
    1585,{
      "missed": false,
      "latency": null
    }
  ],[
    1626,{
      "missed": false,
      "latency": null
    }
  ],[
    1713,{
      "missed": false,
      "latency": null
    }
  ],[
    1776,{
      "missed": false,
      "latency": null
    }
  ],[
    1842,{
      "missed": false,
      "latency": null
    }
  ],[
    1892,{
      "missed": false,
      "latency": null
    }
  ],[
    1942,{
      "missed": false,
      "latency": null
    }
  ],[
    1993,{
      "missed": false,
      "latency": null
    }
  ],[
    2089,{
      "missed": true,
      "latency": null
    }
  ],[
    2130,{
      "missed": false,
      "latency": null
    }
  ],[
    2201,{
      "missed": true,
      "latency": null
    }
  ],[
    2227,{
      "missed": true,
      "latency": null
    }
  ],[
    2301,{
      "missed": true,
      "latency": null
    }
  ],[
    2330,{
      "missed": true,
      "latency": null
    }
  ],[
    2418,{
      "missed": true,
      "latency": null
    }
  ],[
    2482,{
      "missed": true,
      "latency": null
    }
  ],[
    2533,{
      "missed": true,
      "latency": null
    }
  ],[
    2585,{
      "missed": true,
      "latency": null
    }
  ],[
    2598,{
      "missed": true,
      "latency": null
    }
  ],[
    2604,{
      "missed": true,
      "latency": null
    }
  ],[
    2657,{
      "missed": true,
      "latency": null
    }
  ],[
    2704,{
      "missed": true,
      "latency": null
    }
  ],[
    2737,{
      "missed": true,
      "latency": null
    }
  ],[
    2778,{
      "missed": true,
      "latency": null
    }
  ],[
    2824,{
      "missed": true,
      "latency": null
    }
  ],[
    2856,{
      "missed": true,
      "latency": null
    }
  ],[
    2893,{
      "missed": true,
      "latency": null
    }
  ],[
    2967,{
      "missed": true,
      "latency": null
    }
  ]
]

too-simple
Code: [Select]
heyddryrun5 (unlocked) >>> blockchain_get_delegate_block_stats too-simple
[[
    639,{
      "missed": false,
      "latency": null
    }
  ],[
    716,{
      "missed": false,
      "latency": null
    }
  ],[
    857,{
      "missed": false,
      "latency": null
    }
  ],[
    971,{
      "missed": false,
      "latency": null
    }
  ],[
    1073,{
      "missed": false,
      "latency": null
    }
  ],[
    1114,{
      "missed": false,
      "latency": null
    }
  ],[
    1202,{
      "missed": false,
      "latency": null
    }
  ],[
    1290,{
      "missed": false,
      "latency": null
    }
  ],[
    1374,{
      "missed": false,
      "latency": null
    }
  ],[
    1470,{
      "missed": false,
      "latency": null
    }
  ],[
    1561,{
      "missed": false,
      "latency": null
    }
  ],[
    1634,{
      "missed": false,
      "latency": null
    }
  ],[
    1772,{
      "missed": false,
      "latency": null
    }
  ],[
    1828,{
      "missed": false,
      "latency": null
    }
  ],[
    1887,{
      "missed": false,
      "latency": null
    }
  ],[
    1960,{
      "missed": false,
      "latency": null
    }
  ],[
    2011,{
      "missed": false,
      "latency": null
    }
  ],[
    2077,{
      "missed": false,
      "latency": null
    }
  ],[
    2136,{
      "missed": true,
      "latency": null
    }
  ],[
    2206,{
      "missed": true,
      "latency": null
    }
  ],[
    2277,{
      "missed": false,
      "latency": null
    }
  ],[
    2374,{
      "missed": true,
      "latency": null
    }
  ],[
    2451,{
      "missed": true,
      "latency": null
    }
  ],[
    2579,{
      "missed": true,
      "latency": null
    }
  ],[
    2625,{
      "missed": true,
      "latency": null
    }
  ],[
    2653,{
      "missed": true,
      "latency": null
    }
  ],[
    2666,{
      "missed": true,
      "latency": null
    }
  ],[
    2712,{
      "missed": true,
      "latency": null
    }
  ],[
    2742,{
      "missed": true,
      "latency": null
    }
  ],[
    2785,{
      "missed": false,
      "latency": 4294967268
    }
  ],[
    2945,{
      "missed": true,
      "latency": null
    }
  ],[
    2988,{
      "missed": true,
      "latency": null
    }
  ],[
    2992,{
      "missed": true,
      "latency": null
    }
  ]
]

Code: [Select]
heyddryrun5 (unlocked) >>> info
{
  "blockchain_head_block_num": 2995,
  "blockchain_head_block_time": "20140625T070730",
  "blockchain_head_block_time_rel": "57 seconds old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 58.179723502304149,
  "network_num_connections": 41,
  "ntp_time": "20140625T070827.387744",
  "ntp_error_seconds": -0.0011310000000000001,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": "20140625T072400",
  "wallet_seconds_until_next_block_production": 933,
  "wallet_local_time": "20140625T070827",
  "blockchain_random_seed": "57b2e227579fff49c5d77dac4e3588b75169ccc9",
  "blockchain_shares": 199999056733994,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T061658",
  "wallet_version": 100
}

Code: [Select]
heyddryrun5 (unlocked) >>> about
{
  "bitshares_toolkit_revision": "eb5bed05842718ac07ee26a20e264269f62efd42",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "3de924b33647a9a547b772a58415835f021f92b3",
  "fc_revision_age": "83 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 02:29:00"
}
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 25, 2014, 07:08:09 am
I am doing some spam testing. why I get negative delegate votes?  ???

see from the block explorer,like block #2972

Code: [Select]
NET DELEGATE VOTES
bts101:  -0.1 XTS
bts102:  -0.1 XTS
bts103:  1 XTS


This is very curious.... looks like a TRX fee amount.   

I have three delegates in one wallet. see at block #2635, sometimes all the  three delegates can get the positive votes.
Code: [Select]
bts101:  3 XTS
bts102:  3 XTS
bts103:  3 XTS
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 07:09:11 am
Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.
wallet_enable_delegate_block_production   ?
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 07:10:48 am
Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.
wallet_enable_delegate_block_production   ?

You can see the output of wallet_list_my_accounts. Both of them have been set to produce blocks.
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 07:11:15 am
I just noticed that the default bandwidth limit may be a cause of forks with the stress testing going on.  A delegate with 40 connections that produces a block that is 200KB is going to have a hard time propagating that block with a 100KB / second limit.

There are command line arguments to adjust this and I am increasing the default size.
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 07:25:19 am
I just noticed that the default bandwidth limit may be a cause of forks with the stress testing going on.  A delegate with 40 connections that produces a block that is 200KB is going to have a hard time propagating that block with a 100KB / second limit.

There are command line arguments to adjust this and I am increasing the default size.

Thank you bytemaster for your hard work. But I guess it's 3AM in VA at this moment. Have a good rest and fight against the forks tomorrow.
Title: Re: Dry Run 5: The Final Countdown
Post by: laow on June 25, 2014, 07:32:03 am
I just noticed that the default bandwidth limit may be a cause of forks with the stress testing going on.  A delegate with 40 connections that produces a block that is 200KB is going to have a hard time propagating that block with a 100KB / second limit.

There are command line arguments to adjust this and I am increasing the default size.

Thanks bytemaster for your hard work. But I guess it's 3AM in VA at this moment. Have a good rest and fight against the forks tomorrow.
+5%  you guys need  a good rest.
Title: Re: Dry Run 5: The Final Countdown
Post by: dexinwong on June 25, 2014, 07:48:47 am
Thank you, you have worked hard!
Title: Re: Dry Run 5: The Final Countdown
Post by: muse-umum on June 25, 2014, 08:08:10 am
Strange that my delegates too-young and too-simple are always missing blocks. They are among the top 101.

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_my_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL    BLOCK PRODUCTION ENABLED
heyd-naive                         XTS54aGvENZaziDPoTBWB8DVFzcTpezKm8stU7kbpQ7yuZZ483pzN           2014-06-24T01:26:30   NO             0              N/A                     
heyd-simple                        XTS6XSi2PDstduVswZycvq8EwenbpERqQUq57QEm6XpbZjPj7XQz3           2014-06-24T01:26:30   NO             0              N/A                     
heyd-young                         XTS7YRXr7X4euUsQoEF8R4M9ErGxaNGEKYfpqMNYvHFPSsQpciyLG           2014-06-24T01:26:30   NO             0              N/A                     
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10             YES                     
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40             YES                     
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30             YES                     

too-young
Code: [Select]
heyddryrun5 (unlocked) >>> blockchain_get_delegate_block_stats too-young
[[
    621,{
      "missed": false,
      "latency": null
    }
  ],[
    713,{
      "missed": false,
      "latency": null
    }
  ],[
    807,{
      "missed": false,
      "latency": null
    }
  ],[
    894,{
      "missed": false,
      "latency": null
    }
  ],[
    962,{
      "missed": false,
      "latency": null
    }
  ],[
    1088,{
      "missed": false,
      "latency": null
    }
  ],[
    1178,{
      "missed": false,
      "latency": null
    }
  ],[
    1278,{
      "missed": false,
      "latency": null
    }
  ],[
    1367,{
      "missed": false,
      "latency": null
    }
  ],[
    1421,{
      "missed": false,
      "latency": null
    }
  ],[
    1510,{
      "missed": false,
      "latency": null
    }
  ],[
    1585,{
      "missed": false,
      "latency": null
    }
  ],[
    1626,{
      "missed": false,
      "latency": null
    }
  ],[
    1713,{
      "missed": false,
      "latency": null
    }
  ],[
    1776,{
      "missed": false,
      "latency": null
    }
  ],[
    1842,{
      "missed": false,
      "latency": null
    }
  ],[
    1892,{
      "missed": false,
      "latency": null
    }
  ],[
    1942,{
      "missed": false,
      "latency": null
    }
  ],[
    1993,{
      "missed": false,
      "latency": null
    }
  ],[
    2089,{
      "missed": true,
      "latency": null
    }
  ],[
    2130,{
      "missed": false,
      "latency": null
    }
  ],[
    2201,{
      "missed": true,
      "latency": null
    }
  ],[
    2227,{
      "missed": true,
      "latency": null
    }
  ],[
    2301,{
      "missed": true,
      "latency": null
    }
  ],[
    2330,{
      "missed": true,
      "latency": null
    }
  ],[
    2418,{
      "missed": true,
      "latency": null
    }
  ],[
    2482,{
      "missed": true,
      "latency": null
    }
  ],[
    2533,{
      "missed": true,
      "latency": null
    }
  ],[
    2585,{
      "missed": true,
      "latency": null
    }
  ],[
    2598,{
      "missed": true,
      "latency": null
    }
  ],[
    2604,{
      "missed": true,
      "latency": null
    }
  ],[
    2657,{
      "missed": true,
      "latency": null
    }
  ],[
    2704,{
      "missed": true,
      "latency": null
    }
  ],[
    2737,{
      "missed": true,
      "latency": null
    }
  ],[
    2778,{
      "missed": true,
      "latency": null
    }
  ],[
    2824,{
      "missed": true,
      "latency": null
    }
  ],[
    2856,{
      "missed": true,
      "latency": null
    }
  ],[
    2893,{
      "missed": true,
      "latency": null
    }
  ],[
    2967,{
      "missed": true,
      "latency": null
    }
  ]
]

too-simple
Code: [Select]
heyddryrun5 (unlocked) >>> blockchain_get_delegate_block_stats too-simple
[[
    639,{
      "missed": false,
      "latency": null
    }
  ],[
    716,{
      "missed": false,
      "latency": null
    }
  ],[
    857,{
      "missed": false,
      "latency": null
    }
  ],[
    971,{
      "missed": false,
      "latency": null
    }
  ],[
    1073,{
      "missed": false,
      "latency": null
    }
  ],[
    1114,{
      "missed": false,
      "latency": null
    }
  ],[
    1202,{
      "missed": false,
      "latency": null
    }
  ],[
    1290,{
      "missed": false,
      "latency": null
    }
  ],[
    1374,{
      "missed": false,
      "latency": null
    }
  ],[
    1470,{
      "missed": false,
      "latency": null
    }
  ],[
    1561,{
      "missed": false,
      "latency": null
    }
  ],[
    1634,{
      "missed": false,
      "latency": null
    }
  ],[
    1772,{
      "missed": false,
      "latency": null
    }
  ],[
    1828,{
      "missed": false,
      "latency": null
    }
  ],[
    1887,{
      "missed": false,
      "latency": null
    }
  ],[
    1960,{
      "missed": false,
      "latency": null
    }
  ],[
    2011,{
      "missed": false,
      "latency": null
    }
  ],[
    2077,{
      "missed": false,
      "latency": null
    }
  ],[
    2136,{
      "missed": true,
      "latency": null
    }
  ],[
    2206,{
      "missed": true,
      "latency": null
    }
  ],[
    2277,{
      "missed": false,
      "latency": null
    }
  ],[
    2374,{
      "missed": true,
      "latency": null
    }
  ],[
    2451,{
      "missed": true,
      "latency": null
    }
  ],[
    2579,{
      "missed": true,
      "latency": null
    }
  ],[
    2625,{
      "missed": true,
      "latency": null
    }
  ],[
    2653,{
      "missed": true,
      "latency": null
    }
  ],[
    2666,{
      "missed": true,
      "latency": null
    }
  ],[
    2712,{
      "missed": true,
      "latency": null
    }
  ],[
    2742,{
      "missed": true,
      "latency": null
    }
  ],[
    2785,{
      "missed": false,
      "latency": 4294967268
    }
  ],[
    2945,{
      "missed": true,
      "latency": null
    }
  ],[
    2988,{
      "missed": true,
      "latency": null
    }
  ],[
    2992,{
      "missed": true,
      "latency": null
    }
  ]
]

Code: [Select]
heyddryrun5 (unlocked) >>> info
{
  "blockchain_head_block_num": 2995,
  "blockchain_head_block_time": "20140625T070730",
  "blockchain_head_block_time_rel": "57 seconds old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 58.179723502304149,
  "network_num_connections": 41,
  "ntp_time": "20140625T070827.387744",
  "ntp_error_seconds": -0.0011310000000000001,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": "20140625T072400",
  "wallet_seconds_until_next_block_production": 933,
  "wallet_local_time": "20140625T070827",
  "blockchain_random_seed": "57b2e227579fff49c5d77dac4e3588b75169ccc9",
  "blockchain_shares": 199999056733994,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T061658",
  "wallet_version": 100
}

Code: [Select]
heyddryrun5 (unlocked) >>> about
{
  "bitshares_toolkit_revision": "eb5bed05842718ac07ee26a20e264269f62efd42",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "3de924b33647a9a547b772a58415835f021f92b3",
  "fc_revision_age": "83 hours ago",
  "compile_date": "compiled on Jun 25 2014 at 02:29:00"
}

I guess I've found the reason.

The transactions which registered delegates are now in pending status. LOL.. Maybe the shitty forks caused this.

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_account_transaction_history
BLK    .TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    475.3    2014-06-24T01:27:00 heyd-simple         heyd-simple         register heyd-young                         0.00000 XTS         0.10001 XTS        fd713570
    475.2    2014-06-24T01:27:00 heyd-simple         heyd-simple         register heyd-simple                        0.00000 XTS         0.10001 XTS        d4d3ec6e
    475.1    2014-06-24T01:27:00 heyd-simple         heyd-simple         register heyd-naive                         0.00000 XTS         0.10001 XTS        413f7028
    548.0    2014-06-24T02:12:30 UNKNOWN             UNKNOWN                                                         0.00000 XTS         0.00000 XTS        fb12b7a3
   pending   2014-06-24T02:12:30 heyd-simple         heyd-simple         register too-young as a delegate            0.00000 XTS         2.19716 XTS        341cfdce
    549.0    2014-06-24T02:13:00 UNKNOWN             UNKNOWN                                                         0.00000 XTS         0.00000 XTS        76705286
    549.1    2014-06-24T02:13:00 UNKNOWN             UNKNOWN                                                         0.00000 XTS         0.00000 XTS        e1b5a153
   pending   2014-06-24T02:13:00 heyd-simple         heyd-simple         register sometimes-naive as a d...          0.00000 XTS         2.19716 XTS        5950588d
   pending   2014-06-24T02:13:00 heyd-simple         heyd-simple         register too-simple as a delegate           0.00000 XTS         2.19716 XTS        04c88bc2
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 11:12:51 am
I want to be part of the history and made a new setup with Linux  (Mint 17)  ;)

Please sent me funds to:

XTS56sZxFnCHsRqifrnaeEcdK6X9vJnfGgYYE2HMguTpCBctmr96F
Title: Re: Dry Run 5: The Final Countdown
Post by: spartako on June 25, 2014, 11:23:59 am
I want to be part of the history and made a new setup with Linux  (Mint 17)  ;)

Please sent me funds to:

XTS56sZxFnCHsRqifrnaeEcdK6X9vJnfGgYYE2HMguTpCBctmr96F

Sent
Code: [Select]
3294.0    2014-06-25T11:23:00 spartako            liondani                                                      100.00000 XTS         0.10000 XTS        e585dd45
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 11:28:37 am
I am doing some spam testing. why I get negative delegate votes?  ???

see from the block explorer,like block #2972

Code: [Select]
NET DELEGATE VOTES
bts101:  -0.1 XTS
bts102:  -0.1 XTS
bts103:  1 XTS


This is very curious.... looks like a TRX fee amount.   


toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       
Title: Re: Dry Run 5: The Final Countdown
Post by: Nimrod on June 25, 2014, 11:45:17 am
The balances are not displayed correctly. After sending XTS, balances is not reduced.
Title: Re: Dry Run 5: The Final Countdown
Post by: betax on June 25, 2014, 11:51:56 am
I have just send you 10 and 10 and have seen my balance being reduced
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 25, 2014, 12:02:46 pm
 "blockchain_head_block_num": 3332,
  "blockchain_head_block_time": "20140625T115400",
  "blockchain_head_block_time_rel": "3 minutes old",
  "blockchain_confirmation_requirement": 296,
  "blockchain_average_delegate_participation": 55.131004366812228,
  "network_num_connections": 16,
  "ntp_time": "20140625T115700.766031",
  "ntp_error_seconds": -1.0356639999999999,
  "wallet_unlocked_seconds_remaining": 28850,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T115700",
  "blockchain_random_seed": "7e8177ce75a26d56e0ab22b764396b84d4beb660",
  "blockchain_shares": 199999120397457,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T195750",
  "wallet_version": 100

Seems to be on the right chain, delegates prod. enabled: yes, production: null - since several hours. Advice ?
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 12:07:50 pm
"blockchain_head_block_num": 3332,
  "blockchain_head_block_time": "20140625T115400",
  "blockchain_head_block_time_rel": "3 minutes old",
  "blockchain_confirmation_requirement": 296,
  "blockchain_average_delegate_participation": 55.131004366812228,
  "network_num_connections": 16,
  "ntp_time": "20140625T115700.766031",
  "ntp_error_seconds": -1.0356639999999999,
  "wallet_unlocked_seconds_remaining": 28850,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140625T115700",
  "blockchain_random_seed": "7e8177ce75a26d56e0ab22b764396b84d4beb660",
  "blockchain_shares": 199999120397457,
  "network_num_connections_max": 200,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20140625T195750",
  "wallet_version": 100

Seems to be on the right chain, delegates prod. enabled: yes, production: null - since several hours. Advice ?

Are your delegates in top101 ?
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 25, 2014, 12:13:04 pm
Record for 'calyau1' -- Registered on 2014-Jun-24 06:37:00, last update was 4 hours ago
Owner's key: XTS6p1iZUm9rbbDLvJZJzKwjsBhkhekbAk5L73oogvdJuNfPGBqz9
NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   PRODUCTION RATIO    LAST BLOCK #    TOTAL PAY           
----------------------------------------------------------------------------------------------------------------------------------------------------
2.16265382%         3               9               0.25                1358            1.62617 XTS

calyauwall (unlocked) >>> blockchain_get_account_record_by_id 402
Record for 'calyau2' -- Registered on 2014-Jun-24 06:38:00, last update was 4 hours ago
Owner's key: XTS88mbZ8waajty9SJSkf54VUF7nHY424jXojjFHsbqX5nxmuYRYv
NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   PRODUCTION RATIO    LAST BLOCK #    TOTAL PAY           
----------------------------------------------------------------------------------------------------------------------------------------------------
2.40896889%         3               8               0.2727              1451            1.59168 XTS

Getting lost yesterday somewhere in a fork....
Title: Re: Dry Run 5: The Final Countdown
Post by: bdnoble on June 25, 2014, 12:20:39 pm
So I tried to pull the latest and I removed data directory just in case, but now when I try to import private key it says that scanning has been disabled because there are active delegates. So how am I supposed to get my delegate back and producing blocks?! Help?


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 12:21:57 pm
Record for 'calyau1' -- Registered on 2014-Jun-24 06:37:00, last update was 4 hours ago
Owner's key: XTS6p1iZUm9rbbDLvJZJzKwjsBhkhekbAk5L73oogvdJuNfPGBqz9
NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   PRODUCTION RATIO    LAST BLOCK #    TOTAL PAY           
----------------------------------------------------------------------------------------------------------------------------------------------------
2.16265382%         3               9               0.25                1358            1.62617 XTS

calyauwall (unlocked) >>> blockchain_get_account_record_by_id 402
Record for 'calyau2' -- Registered on 2014-Jun-24 06:38:00, last update was 4 hours ago
Owner's key: XTS88mbZ8waajty9SJSkf54VUF7nHY424jXojjFHsbqX5nxmuYRYv
NET VOTES           BLOCKS PRODUCED BLOCKS MISSED   PRODUCTION RATIO    LAST BLOCK #    TOTAL PAY           
----------------------------------------------------------------------------------------------------------------------------------------------------
2.40896889%         3               8               0.2727              1451            1.59168 XTS

Getting lost yesterday somewhere in a fork....

You are out of top101.
You need more votes.
Here is the list of the last few delegates (including yours):
Code: [Select]
96   init95                        0.0025031948 %      35              3
420  wackou-delegate-1             0.0025020826 %      19              11
395  btsjohn                       0.0025011953 %      16              17
** Standby:
462  clout-delegate15              0.0025000069 %      1               11
450  clout-delegate4               0.0025000069 %      1               10
452  clout-delegate8               0.0025000060 %      0               11
453  clout-delegate10              0.0025000060 %      0               14
339  taolje-pay0                   0.0024765832 %      29              8
361  init2winit                    0.0024070940 %      14              20
441  crazybit-delegate             0.0018774286 %      0               3
433  coolspeed-test                0.0016483689 %      7               0
331  delegate-alt                  0.0013923371 %      23              0
308  alt                           0.0010789097 %      0               18
392  mao-delegate1                 0.0005101363 %      5               10
364  sometimes-naive               0.0005083279 %      16              12
419  bdnoble                       0.0005000848 %      2               4
304  dele-puppy                    0.0003308709 %      20              0
406  happyshares-2                 0.0000932572 %      9               3
408  happyshares-5                 0.0000932565 %      7               3
410  happyshares-6                 0.0000805051 %      9               3
302  slavix                        0.0000802706 %      18              4
409  happyshares-4                 0.0000773216 %      9               3
313  toast                         0.0000755696 %      21              0
307  blockchainer                  0.0000702511 %      17              3
388  valzav                        0.0000699903 %      0               0
323  spartako1                     0.0000649903 %      0               9
407  happyshares-3                 0.0000612354 %      8               4
380  delegate                      0.0000556920 %      14              3
405  happyshares-1                 0.0000451723 %      8               3
306  bits                          0.0000450317 %      18              3
90   init89                        0.0000353147 %      21              0
63   init62                        0.0000249683 %      20              0
402  calyau2                       0.0000240897 %      3               8
401  calyau1                       0.0000216265 %      3               9
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 25, 2014, 12:25:59 pm
So I tried to pull the latest and I removed data directory just in case, but now when I try to import private key it says that scanning has been disabled because there are active delegates. So how am I supposed to get my delegate back and producing blocks?! Help?
Forks were caused by delegates that were busy calculating signatures during stress test and missed producing blocks ..
thus BM temporarily disabled TITAN parsing for delegates ..

As a result (until the wallet is multithreaded) you should not manage delegates and your own pocket-money account in the same wallet!

I am pretty sure this is just temporary
Title: Re: Dry Run 5: The Final Countdown
Post by: CalabiYau on June 25, 2014, 12:41:52 pm
Quote
You are out of top101.
You need more votes.

Thanks, so I can just be patient  :)
Title: Re: Dry Run 5: The Final Countdown
Post by: bdnoble on June 25, 2014, 12:53:02 pm

So I tried to pull the latest and I removed data directory just in case, but now when I try to import private key it says that scanning has been disabled because there are active delegates. So how am I supposed to get my delegate back and producing blocks?! Help?
Forks were caused by delegates that were busy calculating signatures during stress test and missed producing blocks ..
thus BM temporarily disabled TITAN parsing for delegates ..

As a result (until the wallet is multithreaded) you should not manage delegates and your own pocket-money account in the same wallet!

I am pretty sure this is just temporary

Well if I can't use the private keys to import my delegate back into my wallet... How do I get it back?


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 5: The Final Countdown
Post by: vlight on June 25, 2014, 12:59:59 pm
You are out of top101.
You need more votes.
Looks like it is very hard to get to top101, even on the test chain.  :-X
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 25, 2014, 01:01:50 pm

So I tried to pull the latest and I removed data directory just in case, but now when I try to import private key it says that scanning has been disabled because there are active delegates. So how am I supposed to get my delegate back and producing blocks?! Help?
Forks were caused by delegates that were busy calculating signatures during stress test and missed producing blocks ..
thus BM temporarily disabled TITAN parsing for delegates ..

As a result (until the wallet is multithreaded) you should not manage delegates and your own pocket-money account in the same wallet!

I am pretty sure this is just temporary

Well if I can't use the private keys to import my delegate back into my wallet... How do I get it back?
What are you talking about?

Sure you can .. but you cannot parse 'non-delegate' accounts for their TITAN addresses ... as this step might be too time-consuming AT THE MOMENT!
nothing else .. delegates always sign with the exact same key ... while all transactions on the blockchain generate stealth addresses for payments .. finding payments that concern you is a little more complex .. and as a consequence together with the mass-stress-test .. your wallet takes to much time parsing TITAN transactions ..

Thus, (FOR THE MOMENT) fetching TITAN transaction for a local account is disabled if you have a running delegate
and thus, you should (FOR THE MOMENT) not mix delegate-accounts and non-delegate-accounts in one single wallet!

Thats all I say .. sure you cann move private keys over and over .. funds are safe!
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 25, 2014, 01:03:05 pm
Looks like it is very hard to get to top101, even on the test chain.  :-X
That's somehow desired .. isn't it?
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 01:12:10 pm
I want to be part of the history and made a new setup with Linux  (Mint 17)  ;)

Please sent me funds to:

XTS56sZxFnCHsRqifrnaeEcdK6X9vJnfGgYYE2HMguTpCBctmr96F

Sent
Code: [Select]

3294.0    2014-06-25T11:23:00 spartako            liondani                                                      100.00000 XTS         0.10000 XTS        e585dd45

thanks  ;)
Title: Re: Dry Run 5: The Final Countdown
Post by: vlight on June 25, 2014, 01:27:13 pm
Looks like it is very hard to get to top101, even on the test chain.  :-X
That's somehow desired .. isn't it?
Well, yes. But not if the same person has multiple delegates there.  :-\
Title: Re: Dry Run 5: The Final Countdown
Post by: sfinder on June 25, 2014, 01:37:39 pm
Hi BM/ Toast,

Should we need to limit one wallet only can have one delegate  in the next test run?



Looks like it is very hard to get to top101, even on the test chain.  :-X
That's somehow desired .. isn't it?
Well, yes. But not if the same person has multiple delegates there.  :-\
Title: Re: Dry Run 5: The Final Countdown
Post by: coolspeed on June 25, 2014, 01:38:55 pm
my delegate crashed.
with the output:

Code: [Select]
Bus error (core dumped)
I don't know where I can find the core file. I didn't run it in gdb.

Title: Re: Dry Run 5: The Final Countdown
Post by: cass on June 25, 2014, 01:41:17 pm
some funds pls XTS7fpNtioF8Xqoq453RGkAqR1ZdGV8cZFN5gPybxgrjZS8hZCy5i (cassyo) thx
Title: Re: Dry Run 5: The Final Countdown
Post by: emski on June 25, 2014, 01:44:31 pm
my delegate crashed.
with the output:

Code: [Select]
Bus error (core dumped)
I don't know where I can find the core file. I didn't run it in gdb.
When my HDD space finished I saw the same error.
Title: Re: Dry Run 5: The Final Countdown
Post by: coolspeed on June 25, 2014, 01:47:26 pm
I used mac qt-wallet 0.0.5 to vote for "coolspeed-test". I remember I voted up for it.
But the trx reports I voted down for "coolspeed-test". Could you tell what happend?
In this trx I sent all my balance to myself, just to vote for "coolspeed-test".
This trx is in Block #3434

Title: Re: Dry Run 5: The Final Countdown
Post by: coolspeed on June 25, 2014, 01:49:12 pm
my delegate crashed.
with the output:

Code: [Select]
Bus error (core dumped)
I don't know where I can find the core file. I didn't run it in gdb.
When my HDD space finished I saw the same error.

Oops! My SSD is filled up.
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 25, 2014, 01:55:28 pm
I used mac qt-wallet 0.0.5 to vote for "coolspeed-test". I remember I voted up for it.
But the trx reports I voted down for "coolspeed-test". Could you tell what happend?
In this trx I sent all my balance to myself, just to vote for "coolspeed-test".
This trx is in Block #3434
You tx voted for bytemaster .. check your upvotes
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 02:18:19 pm
Quote
484  liondani-delegate-1           0.0000000000 %      0               0               
485  liondani-delegate-2           0.0000000000 %      0               0               
486  liondani-delegate-4           0.0000000000 %      0               0               
487  liondani-delegate-3           0.0000000000 %      0               0               
488  liondani-delegate-5           0.0000000000 %      0               0               
489  liondani-delegate-8           0.0000000000 %      0               0               
490  liondani-delegate-9           0.0000000000 %      0               0               
491  liondani-delegate-10          0.0000000000 %      0               0               
492  liondani-delegate-7           0.0000000000 %      0               0               
493  liondani-delegate-6           0.0000000000 %      0               0               

Much appreciated to get some votes  ;)
Title: Re: Dry Run 5: The Final Countdown
Post by: spartako on June 25, 2014, 02:42:02 pm
some funds pls XTS7fpNtioF8Xqoq453RGkAqR1ZdGV8cZFN5gPybxgrjZS8hZCy5i (cassyo) thx

Sent
Code: [Select]
3537.0    2014-06-25T14:40:34 spartako            cassyo                                                        100.00000 XTS         0.10000 XTS        a615f279
Title: Re: Dry Run 5: The Final Countdown
Post by: coolspeed on June 25, 2014, 02:42:41 pm
I used mac qt-wallet 0.0.5 to vote for "coolspeed-test". I remember I voted up for it.
But the trx reports I voted down for "coolspeed-test". Could you tell what happend?
In this trx I sent all my balance to myself, just to vote for "coolspeed-test".
This trx is in Block #3434
You tx voted for bytemaster .. check your upvotes

yeah.. I did vote for myself and bytemaster. The problem is, it turned out to be a vote down for myself.
Title: Re: Dry Run 5: The Final Countdown
Post by: liondani on June 25, 2014, 02:50:19 pm
some funds pls XTS7fpNtioF8Xqoq453RGkAqR1ZdGV8cZFN5gPybxgrjZS8hZCy5i (cassyo) thx

Code: [Select]
   pending   2014-06-25T14:48:56 liondani            cassyo                                                         10.00000 XTS         0.10000 XTS        f2379650

do you get them?
Title: Re: Dry Run 5: The Final Countdown
Post by: xeroc on June 25, 2014, 03:19:24 pm
I used mac qt-wallet 0.0.5 to vote for "coolspeed-test". I remember I voted up for it.
But the trx reports I voted down for "coolspeed-test". Could you tell what happend?
In this trx I sent all my balance to myself, just to vote for "coolspeed-test".
This trx is in Block #3434
You tx voted for bytemaster .. check your upvotes

yeah.. I did vote for myself and bytemaster. The problem is, it turned out to be a vote down for myself.
the tx shows netto votes .. so maybe there are votes left .. cant check atm
Title: Re: Dry Run 5: The Final Countdown
Post by: bdnoble on June 25, 2014, 03:51:47 pm


So I tried to pull the latest and I removed data directory just in case, but now when I try to import private key it says that scanning has been disabled because there are active delegates. So how am I supposed to get my delegate back and producing blocks?! Help?
Forks were caused by delegates that were busy calculating signatures during stress test and missed producing blocks ..
thus BM temporarily disabled TITAN parsing for delegates ..

As a result (until the wallet is multithreaded) you should not manage delegates and your own pocket-money account in the same wallet!

I am pretty sure this is just temporary

Well if I can't use the private keys to import my delegate back into my wallet... How do I get it back?
What are you talking about?

Sure you can .. but you cannot parse 'non-delegate' accounts for their TITAN addresses ... as this step might be too time-consuming AT THE MOMENT!
nothing else .. delegates always sign with the exact same key ... while all transactions on the blockchain generate stealth addresses for payments .. finding payments that concern you is a little more complex .. and as a consequence together with the mass-stress-test .. your wallet takes to much time parsing TITAN transactions ..

Thus, (FOR THE MOMENT) fetching TITAN transaction for a local account is disabled if you have a running delegate
and thus, you should (FOR THE MOMENT) not mix delegate-accounts and non-delegate-accounts in one single wallet!

Thats all I say .. sure you cann move private keys over and over .. funds are safe!

Okay I think I understand now. I'll see if I can get it working.


Sent from my iPhone using Tapatalk
Title: Re: Dry Run 5: The Final Countdown
Post by: vikram on June 25, 2014, 04:24:53 pm
toast. We have approval voting now. But I am still able to vote against some delegates (I know it won't take effect really). And do trust level 10,30,40 make any difference ?

Code: [Select]
heyddryrun5 (unlocked) >>> wallet_list_accounts
NAME (* delegate)                  KEY                                                             REGISTERED            FAVORITE       TRUST LEVEL   
bytemaster *                       XTS7AkLRGApanDEs8fUbpmJtjUn6sTFSC64AENVCqfshWZ2bPjnSy           2014-06-23T21:09:30   NO             -30       
sometimes-naive *                  XTS5kppbLHPT6JV7aGGXQ3Nu4TvtR1u388uau6Yqv1J9Ni64rnFnc           2014-06-24T02:12:30   NO             10       
too-simple *                       XTS5Def6N9bsueAX2YnvQNKHzbphG1Qx9syKthF9BFFSZZT5EkS3x           2014-06-24T02:12:30   NO             40       
too-young *                        XTS6Kp6598CtJhDVauQwQKVLBZZ34o9W55CR2vhCNRezvKL2KHQtB           2014-06-24T02:12:00   NO             30       
welk1n-b *                         XTS5Q9zjvW6WKBhxYT6oY5qmbywbKv8N4K2HkL8XHYxx41dpDsndm           2014-06-24T03:26:00   NO             -10       

Doesn't matter, either 0 or >= 0.
We will change to "true/false" soon.

Done: https://github.com/BitShares/bitshares_toolkit/commit/3d45435a8b856b3dc66e403397de4a5d9c50e815

You will need to re-trust your trusted delegates with:
Code: [Select]
wallet_set_delegate_trust <delegate_name> true
Title: Re: Dry Run 5: The Final Countdown
Post by: BTSdac on June 25, 2014, 04:27:17 pm
I list the transaction_history of same account in two computer , but the result is different
Code: [Select]
roy (unlocked) >>> wallet_account_transaction_history btsdac
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    954.0    2014-06-24T05:51:30 mao-delegate1       btsdac                                                        100.00000 XTS         0.00000 XTS        fbb58eb5
   1125.0    2014-06-24T07:28:00 calyau              btsdac              cheers                                     22.00000 XTS         0.00000 XTS        1bcea32a
   1209.0    2014-06-24T08:16:00 XTS5vPz2LsE1KkmR... btsdac              test                                        2.00000 XTS         0.00000 XTS        ac3f9ede
   1379.0    2014-06-24T09:51:00 calyau              btsdac              more                                      100.00000 XTS         0.00000 XTS        77ebfa3b
   3660.1    2014-06-25T16:16:30 btsdac              btsdac02                                                       10.00000 XTS         0.10000 XTS        6309495b
   3660.2    2014-06-25T16:16:30 btsdac              btsdac01                                                       10.00000 XTS         0.10000 XTS        e3f5beec
   3660.0    2014-06-25T16:16:30 btsdac              btsdac02                                                        1.00000 XTS         0.10000 XTS        5fd5d73b

Code: [Select]
roy (unlocked) >>> wallet_account_transaction_history btsdac
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    954.0    2014-06-24T05:51:30 mao-delegate1       btsdac                                                        100.00000 XTS         0.00000 XTS        fbb58eb5
   1125.0    2014-06-24T07:28:00 calyau              btsdac              cheers                                     22.00000 XTS         0.00000 XTS        1bcea32a
   1209.0    2014-06-24T08:16:00 XTS5vPz2LsE1KkmR... btsdac              test                                        2.00000 XTS         0.00000 XTS        ac3f9ede
   1379.0    2014-06-24T09:51:00 calyau              btsdac              more                                      100.00000 XTS         0.00000 XTS        77ebfa3b
   3054.0    2014-06-25T08:03:30 btsdac              btsdac              register btsdac                             0.00000 XTS         0.10001 XTS        88060599
   pending   2014-06-25T08:05:00 btsdac              btsdac              update btsdac                               0.00000 XTS         0.10002 XTS        0cef7cd5
   pending   2014-06-25T08:05:00 btsdac              btsdac              update btsdac                               0.00000 XTS         0.10002 XTS        bb15b624
   3069.0    2014-06-25T08:15:00 btsdac              btsdac              register btsdac01                           0.00000 XTS         0.10001 XTS        c79fd85b
   3078.0    2014-06-25T08:22:30 btsdac              btsdac              register btsdac02 as a delegate             0.00000 XTS         2.19724 XTS        3e584981
   3086.0    2014-06-25T08:30:47 btsdac              jeffreylee                                                     10.00000 XTS         0.10000 XTS        47a41975
   3602.0    2014-06-25T15:31:57 btsdac              btsdac01                                                        1.00000 XTS         0.10000 XTS        a60ea647
   3663.0    2014-06-25T16:18:23 btsdac              btsdac01                                                       10.00000 XTS         0.10000 XTS        62686cf6
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 04:52:04 pm
I list the transaction_history of same account in two computer , but the result is different
Code: [Select]
roy (unlocked) >>> wallet_account_transaction_history btsdac
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    954.0    2014-06-24T05:51:30 mao-delegate1       btsdac                                                        100.00000 XTS         0.00000 XTS        fbb58eb5
   1125.0    2014-06-24T07:28:00 calyau              btsdac              cheers                                     22.00000 XTS         0.00000 XTS        1bcea32a
   1209.0    2014-06-24T08:16:00 XTS5vPz2LsE1KkmR... btsdac              test                                        2.00000 XTS         0.00000 XTS        ac3f9ede
   1379.0    2014-06-24T09:51:00 calyau              btsdac              more                                      100.00000 XTS         0.00000 XTS        77ebfa3b
   3660.1    2014-06-25T16:16:30 btsdac              btsdac02                                                       10.00000 XTS         0.10000 XTS        6309495b
   3660.2    2014-06-25T16:16:30 btsdac              btsdac01                                                       10.00000 XTS         0.10000 XTS        e3f5beec
   3660.0    2014-06-25T16:16:30 btsdac              btsdac02                                                        1.00000 XTS         0.10000 XTS        5fd5d73b

Code: [Select]
roy (unlocked) >>> wallet_account_transaction_history btsdac
    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                                             AMOUNT             FEE              ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    954.0    2014-06-24T05:51:30 mao-delegate1       btsdac                                                        100.00000 XTS         0.00000 XTS        fbb58eb5
   1125.0    2014-06-24T07:28:00 calyau              btsdac              cheers                                     22.00000 XTS         0.00000 XTS        1bcea32a
   1209.0    2014-06-24T08:16:00 XTS5vPz2LsE1KkmR... btsdac              test                                        2.00000 XTS         0.00000 XTS        ac3f9ede
   1379.0    2014-06-24T09:51:00 calyau              btsdac              more                                      100.00000 XTS         0.00000 XTS        77ebfa3b
   3054.0    2014-06-25T08:03:30 btsdac              btsdac              register btsdac                             0.00000 XTS         0.10001 XTS        88060599
   pending   2014-06-25T08:05:00 btsdac              btsdac              update btsdac                               0.00000 XTS         0.10002 XTS        0cef7cd5
   pending   2014-06-25T08:05:00 btsdac              btsdac              update btsdac                               0.00000 XTS         0.10002 XTS        bb15b624
   3069.0    2014-06-25T08:15:00 btsdac              btsdac              register btsdac01                           0.00000 XTS         0.10001 XTS        c79fd85b
   3078.0    2014-06-25T08:22:30 btsdac              btsdac              register btsdac02 as a delegate             0.00000 XTS         2.19724 XTS        3e584981
   3086.0    2014-06-25T08:30:47 btsdac              jeffreylee                                                     10.00000 XTS         0.10000 XTS        47a41975
   3602.0    2014-06-25T15:31:57 btsdac              btsdac01                                                        1.00000 XTS         0.10000 XTS        a60ea647
   3663.0    2014-06-25T16:18:23 btsdac              btsdac01                                                       10.00000 XTS         0.10000 XTS        62686cf6

Interesting, I gather you rescanned the chain...
Title: Re: Dry Run 5: The Final Countdown
Post by: bytemaster on June 25, 2014, 04:56:36 pm
This Dry Run is now over... here is where we are at:

It appears that we resolved many issues and that the primary cause of forks right now is network propagation delay caused by CPU load, bandwidth throttling, and the single-threaded nature of the code. 

I would like to separate logic bugs from performance induced bugs because we have ways to significantly enhance performance over time.  Dry run 6 will focus on eliminating the effects of performance from the equation while introducing many small enhancements at the same time.

Stay tuned.