Delegates, start your engines!

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

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

toast

Thanks for participating!

We are taking this network down and will be launching again soon. We will start helping people with their delegate campaigns during this next run.
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.

bytemaster

Quote from: puppies on June 12, 2014, 09:22:53 PM
If we're not running into bugs,  Is there anything special us non power users could do to help?   Does it help to recompile and test the latest?   

Sent from my SCH-I535 using Tapatalk

We are about to merge in the latest from Eric and relaunch the network and hopefully avoid forks this time. 
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.

puppies

If we're not running into bugs,  Is there anything special us non power users could do to help?   Does it help to recompile and test the latest?   

Sent from my SCH-I535 using Tapatalk

[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

toast

Quote from: Kenof on June 12, 2014, 09:00:01 PM
I hope you will give a chance to register as delegate to other users that was too late for the latest test.

The next test we will have everyone start voting on delegates like the real thing.
Anyone can register as a delegate at any time, this was just for *initial* delegates.
Whether or not you get voted in is another matter.
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.

Kenof

I hope you will give a chance to register as delegate to other users that was too late for the latest test.
Making life easier.

bytemaster

Quote from: bitcoinerS on June 12, 2014, 04:38:13 PM
I am not sure what is going on with multiple blockchains being tracked by various clients. I have latest code, pulled today, running on two computers. One is a delegate node on VPS server and one is a desktop client. They seem to be on different blockchains.
delegate node

get_info
{
  "blockchain_head_block_num": 6219,
  "blockchain_head_block_time": "20140612T163445",


desktop client

get_info
{
  "blockchain_head_block_num": 5993,
  "blockchain_head_block_time": "20140612T155045",


Yep... the chains are forking left and right because the network code doesn't know how to sync.  Eric is working through bugs revealed in his testing and has some fixes developed but not yet verified.  I think our problems are a combination of time sync and network latency.   Once we have his code ready we will do another reset and check to make sure we have solved the forking issue.
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.

bitcoinerS

I am not sure what is going on with multiple blockchains being tracked by various clients. I have latest code, pulled today, running on two computers. One is a delegate node on VPS server and one is a desktop client. They seem to be on different blockchains.
delegate node

get_info
{
  "blockchain_head_block_num": 6219,
  "blockchain_head_block_time": "20140612T163445",


desktop client

get_info
{
  "blockchain_head_block_num": 5993,
  "blockchain_head_block_time": "20140612T155045",
>>> approve bitcoiners

xeroc

confirm .. latest git-head compiles smoothly

bdnoble

Quote from: mauritso on June 12, 2014, 11:51:42 AM
Scanning dependencies of target dev_tests
[ 98%] Building CXX object tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/dev_tests.cpp:3:10: fatal error: 'dev_fixture.hpp' file not found
#include "dev_fixture.hpp"
         ^
1 error generated.
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2


Same here.

You can comment out the dev_tests in the CMakeLists.txt in the tests folder. Although I think if you pull the latest that fix has already been made.

Quote
#add_executable( dev_tests dev_tests.cpp )
#target_link_libraries( dev_tests deterministic_openssl_rand bts_client bts_cli bts_wallet bts_blockchain bts_net bitcoin fc ${BOOST_LIBRARIES} ${OPENSSL_LIBRARIES} ${PLATFORM_SPECIFIC_LIBS} ${crypto_library}  ${rt_library} )
:)

mauritso

Scanning dependencies of target dev_tests
[ 98%] Building CXX object tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o
/Users/maurits/bitsharesxts/bitshares_toolkit/tests/dev_tests.cpp:3:10: fatal error: 'dev_fixture.hpp' file not found
#include "dev_fixture.hpp"
         ^
1 error generated.
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2


Same here.
BTS: maurits

xeroc

Quote from: cass on June 12, 2014, 09:26:51 AM
same for me here! Got same error first time now!
+ 1 from my side :-(

cass

Quote from: welk1n on June 12, 2014, 06:34:00 AM
[ 98%] Built target deterministic_signature_test
Scanning dependencies of target dev_tests
[ 98%] Building CXX object tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o
/data/bts/0612/bitshares_toolkit/tests/dev_tests.cpp:3:27: fatal error: dev_fixture.hpp: No such file or directory
#include "dev_fixture.hpp"
                           ^
compilation terminated.
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2



I compiled the project everyday and use the day time as  folder name .
This error is  occurred the first time. ( under the 0612 folder )


root@xxxx:/data/bts# ll
total 28
drwxr-xr-x  7 root root 4096 Jun 12 14:08 ./
drwxr-xr-x  3 root root 4096 Jun  8 09:36 ../
drwxr-xr-x  3 root root 4096 Jun  9 13:12 0609/
drwxr-xr-x  3 root root 4096 Jun 10 12:34 0610/
drwxr-xr-x  3 root root 4096 Jun 11 10:11 0611/
drwxr-xr-x  3 root root 4096 Jun 12 14:08 0612/


same for me here! Got same error first time now!
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

xeroc

When are votes for a delegate counting??

I made a new delegate, voted for him and transmitted fund to that delegate:

default (unlocked) >>> wallet_list_unspent_balances
           BALANCE                                   OWNER                     VOTE
--------------------------------------------------------------------------------------------------------------------------
        6000000000    XTS4zCs7x5h1cjLSouVH6LTKRvVTzyfnAuLt                        +xeroc-tmp


However no votes are counted:

default (unlocked) >>> blockchain_get_account_record xeroc-tmp
{
  "id": 309,
  "name": "xeroc-tmp",
  "public_data": {},
  "owner_key": "XTS5tc6NTjfE78hZAJYuZU8Q1uYSzAo48G6xHCdvY1JrBtHHFYgta",
  "active_key_history": [[
      "20140611T091000",
      "XTS5tc6NTjfE78hZAJYuZU8Q1uYSzAo48G6xHCdvY1JrBtHHFYgta"
    ]
  ],
  "delegate_info": {
    "votes_for": 0,
    "votes_against": 0,
    "blocks_produced": 0,
    "blocks_missed": 0,
    "pay_balance": 0,
    "next_secret_hash": "0000000000000000000000000000000000000000",
    "last_block_num_produced": 4294967295
  },
  "registration_date": "20140611T091000",
  "last_update": "20140611T091000",
  "meta_data": null
}

welk1n

[ 98%] Built target deterministic_signature_test
Scanning dependencies of target dev_tests
[ 98%] Building CXX object tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o
/data/bts/0612/bitshares_toolkit/tests/dev_tests.cpp:3:27: fatal error: dev_fixture.hpp: No such file or directory
#include "dev_fixture.hpp"
                           ^
compilation terminated.
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2



I compiled the project everyday and use the day time as  folder name .
This error is  occurred the first time. ( under the 0612 folder )


root@xxxx:/data/bts# ll
total 28
drwxr-xr-x  7 root root 4096 Jun 12 14:08 ./
drwxr-xr-x  3 root root 4096 Jun  8 09:36 ../
drwxr-xr-x  3 root root 4096 Jun  9 13:12 0609/
drwxr-xr-x  3 root root 4096 Jun 10 12:34 0610/
drwxr-xr-x  3 root root 4096 Jun 11 10:11 0611/
drwxr-xr-x  3 root root 4096 Jun 12 14:08 0612/

ElMato

Go to libraries/fc
git checkout f01d25788e88d0a77520f192719bc2dd6898d6b7