Main Menu

Dry Run 4: A New Hope

Started by toast, June 20, 2014, 08:46:34 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 2 3 4 5 6 All
User actions

vikram

#13
June 20, 2014, 11:51:29 PM
Quote from: zhangweis on June 20, 2014, 09:25:56 PM
I got something like below, notice the wallet_seconds_until_next_block_production is -14. Any idea?

default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 4,
  "blockchain_head_block_time": "20140620T212300",
  "blockchain_head_block_time_rel": "2 minutes old",
  "blockchain_confirmation_requirement": 244,
  "blockchain_average_delegate_participation": 13.333333333333334,
  "network_num_connections": 4,
  "ntp_time": "20140620T212514.774930",
  "ntp_error_seconds": -0.033466000000000003,
  "wallet_unlocked_seconds_remaining": 99999796,
  "wallet_next_block_production_time": "20140620T212500",
  "wallet_seconds_until_next_block_production": -14,
  "wallet_local_time": "20140620T212514",
  "blockchain_random_seed": "afeecdf51c48e6d33f41a334e0e57d554cdcd86f",
  "blockchain_shares": 9999853094228,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20170821T070830",
  "wallet_version": 100
}
Edit:
seems like caused by this error:
network_get_connection_count() >= _min_delegate_connection_count: Client must have 5 connections before you may produce blocks

This is a known issue; cause unknown: https://github.com/BitShares/bitshares_toolkit/issues/362

bytemaster

#12
June 20, 2014, 10:14:47 PM
Quote from: emski on June 20, 2014, 10:02:21 PM
I've enabled all my delegates.
And I've registered few more.
However I still see some negative VOTES FOR. Is this expected?
6           unelected-delegate-6     -104917529          102557509978        -1.026658773 %      0               1

I only fixed half the issue... we can ignore it for this run (it is a harmless bug...).  There were two places in the code that needed to change and I only got one of them.   I have checked in a fix that should go into effect the next dry run.   For now we will just ignore it.

The bug should only effect the unelected initial delegates. 

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

emski

#11
June 20, 2014, 10:02:21 PM
I've enabled all my delegates.
And I've registered few more.
However I still see some negative VOTES FOR. Is this expected?
6           unelected-delegate-6     -104917529          102557509978        -1.026658773 %      0               1
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

zhangweis

#10
June 20, 2014, 09:47:17 PM
Quote from: bytemaster on June 20, 2014, 09:41:22 PM
If you have less than 5 connections, shut down and reconnect.

Thanks and it works by restarting client.
Weibo:[url="http://weibo.com/zhangweis"]http://weibo.com/zhangweis[/url]

bytemaster

#9
June 20, 2014, 09:41:22 PM
If you have less than 5 connections, shut down and reconnect. 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

zhangweis

#8
June 20, 2014, 09:25:56 PM
I got something like below, notice the wallet_seconds_until_next_block_production is -14. Any idea?

default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 4,
  "blockchain_head_block_time": "20140620T212300",
  "blockchain_head_block_time_rel": "2 minutes old",
  "blockchain_confirmation_requirement": 244,
  "blockchain_average_delegate_participation": 13.333333333333334,
  "network_num_connections": 4,
  "ntp_time": "20140620T212514.774930",
  "ntp_error_seconds": -0.033466000000000003,
  "wallet_unlocked_seconds_remaining": 99999796,
  "wallet_next_block_production_time": "20140620T212500",
  "wallet_seconds_until_next_block_production": -14,
  "wallet_local_time": "20140620T212514",
  "blockchain_random_seed": "afeecdf51c48e6d33f41a334e0e57d554cdcd86f",
  "blockchain_shares": 9999853094228,
  "network_num_connections_max": 12,
  "network_protocol_version": 103,
  "wallet_open": true,
  "wallet_unlocked_until": "20170821T070830",
  "wallet_version": 100
}
Edit:
seems like caused by this error:
network_get_connection_count() >= _min_delegate_connection_count: Client must have 5 connections before you may produce blocks
Weibo:[url="http://weibo.com/zhangweis"]http://weibo.com/zhangweis[/url]

bytemaster

#7
June 20, 2014, 09:22:08 PM
Quote from: Xeldal on June 20, 2014, 09:20:34 PM
Getting build errors

Code Select
Scanning dependencies of target wallet_tests
[100%] Building CXX object tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o
/root/bitshares_toolkit/tests/wallet_tests.cpp: In function 'boost::unit_test::test_suite* init_unit_test_suite(int, char**)':
/root/bitshares_toolkit/tests/wallet_tests.cpp:597:62: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
     if ( fc::is_directory( *directory_itr ) && (directory_itr->filename().string()[0] != '_') )
                                                              ^
/root/bitshares_toolkit/tests/wallet_tests.cpp:604:85: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
                                                                        directory_itr->filename().string());
                                                                                     ^
/root/bitshares_toolkit/tests/wallet_tests.cpp:609:85: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
                                                                        directory_itr->filename().string());
                                                                                     ^
make[2]: *** [tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/wallet_tests.dir/all] Error 2
make: *** [all] Error 2


Known issue... safe to ignore, it is just one of the tests.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

sfinder

#6
June 20, 2014, 09:21:55 PM
compile error at 99%-100%

Code Select


[100%] Building CXX object tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o
/home/daniel/bitshares_toolkit/tests/wallet_tests.cpp: In function 鈥榖oost::unit_test::test_suite* init_unit_test_suite(int, char**)鈥

                                                                                                                                        /home/daniel/bitshares_toolkit/tests/wallet_tests.cpp:597:62: error: base operand of 鈥>鈥has non-pointer type 鈥榝c::directory_iterator鈥
     if ( fc::is_directory( *directory_itr ) && (directory_itr->filename().string()[0] != '_') )
                                                              ^
/home/daniel/bitshares_toolkit/tests/wallet_tests.cpp:604:85: error: base operand of 鈥>鈥has non-pointer type 鈥榝c::directory_iterator鈥
                                                                        directory_itr->filename().string());
                                                                                     ^
/home/daniel/bitshares_toolkit/tests/wallet_tests.cpp:609:85: error: base operand of 鈥>鈥has non-pointer type 鈥榝c::directory_iterator鈥
                                                                        directory_itr->filename().string());
                                                                                     ^
make[2]: *** [tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/wallet_tests.dir/all] Error 2
make: *** [all] Error 2
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Xeldal

#5
June 20, 2014, 09:20:34 PM
Getting build errors

Code Select
Scanning dependencies of target wallet_tests
[100%] Building CXX object tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o
/root/bitshares_toolkit/tests/wallet_tests.cpp: In function 'boost::unit_test::test_suite* init_unit_test_suite(int, char**)':
/root/bitshares_toolkit/tests/wallet_tests.cpp:597:62: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
     if ( fc::is_directory( *directory_itr ) && (directory_itr->filename().string()[0] != '_') )
                                                              ^
/root/bitshares_toolkit/tests/wallet_tests.cpp:604:85: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
                                                                        directory_itr->filename().string());
                                                                                     ^
/root/bitshares_toolkit/tests/wallet_tests.cpp:609:85: error: base operand of '->' has non-pointer type 'fc::directory_iterator'
                                                                        directory_itr->filename().string());
                                                                                     ^
make[2]: *** [tests/CMakeFiles/wallet_tests.dir/wallet_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/wallet_tests.dir/all] Error 2
make: *** [all] Error 2

toast

#4
June 20, 2014, 09:17:22 PM
Quote from: sfinder on June 20, 2014, 09:11:27 PM
Can we use BIP to pay registration fee ? Has the BIP function been implemented ?

No, probably won't be for XT
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

zhangweis

#3
June 20, 2014, 09:12:43 PM Last Edit: June 20, 2014, 09:23:03 PM by zhangweis
I've seen 1 block now.
Can someone send me some fund to register as delegate? Thanks in advance.

XTS8eghNapYmPzsmweCn7EVQLDqUKH91hj3GCowusMm8vRhkLM5Zk
Weibo:[url="http://weibo.com/zhangweis"]http://weibo.com/zhangweis[/url]

sfinder

#2
June 20, 2014, 09:11:27 PM
Can we use BIP to pay registration fee ? Has the BIP function been implemented ?
微博：星在飘我在找|BTS X 受托人delegate ID：baidu
和中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

toast

#1
June 20, 2014, 08:46:34 PM
QuoteHey everyone I am sad to report that we have to reset this dry run due to a major flaw in the initial condition setup resulting in the negative votes-for everyone saw.  Unfortunately I cannot fix this without a reset.

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

Let's begin!

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

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

* Step 3: Pull latest and build.

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

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

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

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

Edit: Blocks will be reaaaal slow near the start. Initial delegates, get online!
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.
Print
Go Up Pages 1 2 3 4 5 6 All
User actions