Main Menu

Dry Run 2: The Real Deal

Started by toast, June 12, 2014, 11:24:02 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

muse-umum

Quote from: welk1n on June 15, 2014, 02:21:19 PM
Quote from: heyD on June 15, 2014, 02:12:31 PM
Quote from: Troglodactyl on June 15, 2014, 01:59:11 PM
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

taoljj

Quote from: heyD on June 15, 2014, 02:12:31 PM
Quote from: Troglodactyl on June 15, 2014, 01:59:11 PM
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

welk1n

Quote from: heyD on June 15, 2014, 02:12:31 PM
Quote from: Troglodactyl on June 15, 2014, 01:59:11 PM
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
}

crazybit

Quote from: BTSdac on June 15, 2014, 01:44:31 PM
Quote from: zhangweis on June 15, 2014, 10:39:27 AM

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.

muse-umum

#259
Quote from: Troglodactyl on June 15, 2014, 01:59:11 PM
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>

Troglodactyl

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.

BTSdac

Quote from: zhangweis on June 15, 2014, 10:39:27 AM

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?
[url="//github.com"]github.com[/url] :pureland
BTS2.0 API :[url="ws://139.196.37.179:8091"]ws://139.196.37.179:8091[/url]
BTS2.0 API 数据源ws:[url="//139.196.37.179:8091"]//139.196.37.179:8091[/url]

Troglodactyl

Quote from: alexxy on June 15, 2014, 10:05:37 AM
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.

spartako

When I launched the command "wallet_list_unspent_balances" I obtained a segfault:


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

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?!

liondani

#253
Quote from: cass on June 15, 2014, 12:09:11 PM

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!
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

cass

Quote from: liondani on June 15, 2014, 11:16:10 AM
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  - - -  █║▌║║█

mauritso

#251
I would like to get voted in, I would appreciate it if someone votes for me:

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.
BTS: maurits

liondani

The Indian bitsharesX (wallet) tester
for anybody wanted to see them in action...

[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

zhangweis

Quote from: BTSdac on June 15, 2014, 10:06:11 AM
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:[url="http://weibo.com/zhangweis"]http://weibo.com/zhangweis[/url]