Author Topic: Dry Run 2: The Real Deal  (Read 146746 times)

0 Members and 1 Guest are viewing this topic.

Offline muse-umum

  • Hero Member
  • *****
  • Posts: 717
  • BitShares everything
    • View Profile
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

I am running with old version (built more than 30 hours ago) and now has 12 connections.

Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>

Maybe you can use the  wallet_get_account commands


welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
  "index": 10,
  "id": 33,
  "name": "init-delegate-33",
  "public_data": null,
  "owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
  "active_key_history": [[
      "20140615T021914",
      "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
    ]
  ],
  "delegate_info": {
    "votes_for": 99732150532,
    "votes_against": 0,
    "blocks_produced": 137,
    "blocks_missed": 18,
    "pay_balance": 5988191,
    "next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
    "last_block_num_produced": 6140
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null,
  "account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
  "trust_level": 0,
  "private_data": null
}

I meant the the head numbers of all the blocks produced by the given delegate.

Like : init-delegate-33 has produced following blocks: 1, 1000, 2332,3344 ............ 6140

Offline taoljj

  • Full Member
  • ***
  • Posts: 177
    • View Profile
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

I am running with old version (built more than 30 hours ago) and now has 12 connections.

Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>


 +5%
BTS      Witness: delegate.taoljj

Offline welk1n

  • Jr. Member
  • **
  • Posts: 26
    • View Profile
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

I am running with old version (built more than 30 hours ago) and now has 12 connections.

Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>

Maybe you can use the  wallet_get_account commands


welk1n (unlocked) >>> wallet_get_account init-delegate-33
{
  "index": 10,
  "id": 33,
  "name": "init-delegate-33",
  "public_data": null,
  "owner_key": "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA",
  "active_key_history": [[
      "20140615T021914",
      "XTS7SDs7tmoYe96wjRzYqavAu4nehaMUTh3TbkGe9EPWNbA1P2XPA"
    ]
  ],
  "delegate_info": {
    "votes_for": 99732150532,
    "votes_against": 0,
    "blocks_produced": 137,
    "blocks_missed": 18,
    "pay_balance": 5988191,
    "next_secret_hash": "419c0a4c97a2ea0847778747fdb7c5470ac6a1e6",
    "last_block_num_produced": 6140
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null,
  "account_address": "XTSG6FH3Q32yVgoafyJLnPS5JTo9juK5rWY4",
  "trust_level": 0,
  "private_data": null
}

Offline crazybit


I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
which one is my wallet file, is it included in folder ./bitshare XTS/ wallet?

XTS wallet use level db, it does not like bitcoin wallet which has only one wallet.dat file, you need to back the whole "wallets" folder.

Offline muse-umum

  • Hero Member
  • *****
  • Posts: 717
  • BitShares everything
    • View Profile
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

I am running with old version (built more than 30 hours ago) and now has 12 connections.

Suggestion: Is it possible to have a command that allows us to list the blocks produced by a given delegate account name?
like blocks_produced_by_delegate <delegate_account_name>
« Last Edit: June 15, 2014, 02:18:56 pm by heyD »

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
FWIW: Last night I updated, which put me at 3-4 connections after launch instead of 1.  I manually added nodes until I was up to about 9, and left it for the night.  This morning I was down to 5, and apparently on a fork quite a few blocks behind on the chain.  My suspicion is that the cause is too many leaf nodes all on the old version so they only have one connection.

Offline BTSdac

  • Hero Member
  • *****
  • Posts: 1219
    • View Profile
  • BitShares: K1

I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
which one is my wallet file, is it included in folder ./bitshare XTS/ wallet?
github.com :pureland
BTS2.0 API :ws://139.196.37.179:8091
BTS2.0 API 数据源ws://139.196.37.179:8091

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
I'm running test node with large allowed number of connections
can someone try to add me as peer?

79.173.81.171:8764

Added successfully.

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
When I launched the command "wallet_list_unspent_balances" I obtained a segfault:

Code: [Select]
default (unlocked) >>> wallet_list_unspent_balances
           BALANCE                                   OWNER                     VOTE
--------------------------------------------------------------------------------------------------------------------------
          10000000    XTSBq9D8nqMyn192B6Dt8HF62k9U7nwqJcv6                        +mauritso
        8989970000    XTSMFChKHFVFjZfSNZt8nAibo1bDvBouEwJM                        +bts101
            990000    XTSLuMuRnXiAYh4jiT64isaK6VWaM6KRLYKu                        +bts101
         265343474    XTSFCEgUceUsCjgHybTsYgJ7JJkUDc8cTYUm                        +cgafeng
           1970000    XTS63HYCB2AUNKKn5e6pPCGATeJy6LxQSBxR                        +bts101

Program received signal SIGSEGV, Segmentation fault.
0x00000000006659f9 in bts::cli::detail::cli_impl::format_and_print_result(std::string const&, std::vector<fc::variant, std::allocator<fc::variant> >, fc::variant const&) ()
    at /home/fabiux/ssd/bitshares_toolkit/libraries/cli/cli.cpp:791
791                                   if (delegate_rec->name.size() > 21)
(gdb)
wallet_account_set_approval spartako

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
@Devs: Now that I can import my keyhotee ID (lower-letter case issue resolved)
I wonder if I made sth wrong as I cannot see and funds tied to that account ('xeroc') .. I thought we get a stake on XTS as beeing a keyhotee founder?!

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani

IMO you should deal with a bit more respect to devs! Just said...

I was certain everybody has a sense of humour, especialy on forums like this where people in most cases have high IQs (me excluded)  :)

PS I am tired to say sorry guys but if I have insulted some of you...          sorry!
« Last Edit: June 15, 2014, 12:50:13 pm by liondani »

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
The Indian bitsharesX (wallet) tester
for anybody wanted to see them in action...



IMO you should deal with a bit more respect to devs! Just said...
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline mauritso

  • Full Member
  • ***
  • Posts: 64
    • View Profile
I would like to get voted in, I would appreciate it if someone votes for me:

Code: [Select]
wallet_set_delegate_trust_level mauritso 1
If I am a delegate at the start of the XTS network I will launch a Amazon EC2 instance (m1.small/m3.medium/m3.large depending on the requirements in a location of your choosing) and keep it running for at least a month. After my amazon credit is gone, I am still a delegate and it got enough money in transaction fees I will probably switch to a dedicated host.
« Last Edit: June 15, 2014, 12:41:23 pm by mauritso »
BTS: maurits

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
The Indian bitsharesX (wallet) tester
for anybody wanted to see them in action...


Offline zhangweis

  • Sr. Member
  • ****
  • Posts: 305
    • View Profile
Code: [Select]
Loading blockchain from "/root/.BitSharesXTS/chain"
Starting JSON RPC server on port 57466 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
    {"method":"read","len":23,"over":1}
    th_a  datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
    {"type":"uint8_t"}
    th_a  raw.hpp:440 unpack
optional<fc::exception>
    {"type":"fc::exception"}
    th_a  raw.hpp:164 unpack
Error unpacking field last_error
    {"field":"last_error"}
    th_a  raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
    {"type":"bts::net::potential_peer_record"}
    th_a  raw.hpp:440 unpack
what is wrong

I solved this by deleting ~/.BitsharesXT dir. But remember to backup your wallet. Or maybe you can try run ./bitshare_client --clear-peer-database --resync-blockchain
Weibo:http://weibo.com/zhangweis