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.

emski

I havent done anything since I've started the delegate 2 days ago.
Current situation:
"blockchain_head_block_num": 5892,
"blockchain_head_block_time": "20140611T202600",

Is there a convenient way to check If I'm on the "main" chain ? ( or at least with some confidence )
The number I have looks consistent with the one bytemaster shows. (it increased proportionally with time difference)
Does this mean that my delegate synchronized to the "main" blockchain ? (or at least the one bytemaster posted)
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

alt

the newst code can't create wallet, here is the error msg

(wallet closed) >>> wallet_create default
new_passphrase:
new_passphrase (verify):
20015 brain_key_too_short: brain key is too short

    {}
    th_a  client.cpp:686 wallet_create

    {}
    th_a  common_api_client.cpp:212 wallet_create

    {"command":"wallet_create"}
    th_a  cli.cpp:574 execute_command


mauritso

#213
Quote from: Xeldal on June 11, 2014, 08:30:31 PM
fresh build and now i can't find ./bitshares_client

root@we:~/bitshares_toolkit# gdb ./bitshares_client
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
./bitshares_client: No such file or directory.
(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.


The client is in ~/bitshares_toolkit/programs/client/

gdb ~/bitshares_toolkit/programs/client/bitshares_client
BTS: maurits

Xeldal

#212
fresh build and now i can't find ./bitshares_client

root@we:~/bitshares_toolkit/programs/client# gdb ./bitshares_client
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
./bitshares_client: No such file or directory.
(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.



Edit: changed ~/bitshares_toolkit# to ~/bitshares_toolkit/programs/client#

alt


can't build because ntohl() in bitshares_toolkit/libraries/fc/src/network/ntp.cpp
add headfile

#include <arpa/inet.h>

bitcoinerS

get_info
{
  "blockchain_head_block_num": 5739,
  "blockchain_head_block_time": "20140611T201700",
>>> approve bitcoiners

bytemaster

"blockchain_head_block_num": 5847,
"blockchain_head_block_time": "2014-06-11 T 19:43:15",
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.

bytemaster

I just added a query to NTP to help keep all delegates on the same approximate time.   This should help cut down of any forks caused for this reason and simplify the setup of 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.

bitcoinerS

Quote from: toast on June 11, 2014, 04:17:40 PM
For now if you want to sync up you can save your wallet / wipe data dir / copy wallet back in

I deleted wallet and reimported my delegate keys. Now get_info gets:

"blockchain_head_block_num": 5730,
  "blockchain_head_block_time": "20140611T190730",
>>> approve bitcoiners

ffwong

I have been late for registering as initial delegate.

So I tried to register on blockchain as mentioned by ByteMaster. When I tried "wallet_account_register", it said I have insufficient fund to register (as I have zero funding).

Did anyone try register on blockchain before? Or anyway to get sufficient fund to register?

Cast me some votes. I am running:
- dragonball for Bitshares 2.0 net
- delegate.fftt for PTS (DPOS) net

toast

For now if you want to sync up you can save your wallet / wipe data dir / copy wallet back in
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.

alexxy

seems like i'm on fork also


  "blockchain_head_block_num": 5543,
  "blockchain_head_block_time": "20140611T160700",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 28.877642155403393,
  "network_num_connections": 3,
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

toast

Quote from: emski on June 11, 2014, 03:47:12 PM
Can anyone explain the difference in blockchain_head_block_num?

Some people are on forks, eric is working on updating the fork resolution on another branch
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.

emski

Can anyone explain the difference in blockchain_head_block_num?
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

muse-umum

 UTC+8 23:26

"blockchain_head_block_num": 5624,
"blockchain_head_block_time": "20140611T151900",