Author Topic: Dry Run 7: The Power of DPOS  (Read 40892 times)

0 Members and 1 Guest are viewing this topic.

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
Re: Dry Run 7: The Power of DPOS
« Reply #75 on: July 02, 2014, 07:16:51 am »
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs
beg some funds plz!

Offline liondani

  • Hero Member
  • *****
  • Posts: 3731
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: Dry Run 7: The Power of DPOS
« Reply #76 on: July 02, 2014, 07:40:11 am »
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs
beg some funds plz!

sent

Offline CalabiYau

Re: Dry Run 7: The Power of DPOS
« Reply #77 on: July 02, 2014, 08:05:15 am »
some fuel sent @ dexinwong / domis-1 / radiumlau2 /   scroodge /

Offline liondani

  • Hero Member
  • *****
  • Posts: 3731
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: Dry Run 7: The Power of DPOS
« Reply #78 on: July 02, 2014, 08:15:16 am »
some fuel sent @ dexinwong / domis-1 / radiumlau2 /   scroodge /

sent

only error with radiumlau2 
Code: [Select]
liondani (unlocked) >>> wallet_transfer 33 XTS liondani radiumlau2
10 assert_exception: Assert Exception
is_valid_account( to_account_name ):
    {}
    th_a  wallet.cpp:1792 transfer_asset

    {"real_amount_to_transfer":33,"amount_to_transfer_symbol":"XTS","from_account_name":"liondani","to_account_name":"radiumlau2","memo_message":""}
    th_a  wallet.cpp:1874 transfer_asset

    {}
    th_a  common_api_client.cpp:771 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:538 execute_command

Offline CalabiYau

Re: Dry Run 7: The Power of DPOS
« Reply #79 on: July 02, 2014, 08:29:22 am »
some fuel sent @ dexinwong / domis-1 / radiumlau2 /   scroodge /
sent

radiumlau2          XTS8k9Vv9MBMgJcivZFgNa41jBW5wsVAH9c3Pwv9cNQTrba3oz8iF

name due to "forensic" address approach  ;)

Offline liondani

  • Hero Member
  • *****
  • Posts: 3731
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: Dry Run 7: The Power of DPOS
« Reply #80 on: July 02, 2014, 08:46:07 am »
sent

Offline vikram

Re: Dry Run 7: The Power of DPOS
« Reply #81 on: July 02, 2014, 08:48:11 am »
i sent funds to myself. found the transaction in block 1462 but I did not receive the funds in my account. my wallet showed the transaction previously. i cleared the pending transactions and that transaction disappeared but the funds were not in my account. what does this mean?

If you have any enabled delegate accounts, try using the 'wallet_delegate_enable_transaction_scanning true' command and then rescan that block. Let us know if this does not fix the problem.

Offline vikram

Re: Dry Run 7: The Power of DPOS
« Reply #82 on: July 02, 2014, 08:50:18 am »
alt: Thanks for the funds.  fox-delegate-98 all set and produced its first block (1857).

All:
I cannot seem to make proper use of my wallet from the Dry Run 6 within the current client on Dry Run 7.  Oddly, I can receive funds to my named account, but cannot send them. 

The wallet contains the account "fox" imported from Keyhotee a few rounds back.  I've built a clean Bitshares Client on a new VM and copied the "wallets" folder to the ~\.BitSharesXTS folder.  The client starts normally, and successfully opens, unlocks and lists a balance. 

Code: [Select]
about
  "bitshares_toolkit_revision": "57d5b15aecb682d8426d067458fec2da851b248f",
  "bitshares_toolkit_revision_age": "3 hours ago",
  "fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
  "fc_revision_age": "9 hours ago",
  "compile_date": "compiled on Jul  2 2014 at 04:04:17"

get_info
{
  "blockchain_head_block_num": 1917,
  "blockchain_head_block_age": "36 seconds old",
  "blockchain_head_block_timestamp": "20140702T045330",
  "blockchain_average_delegate_participation": 98.92262487757101,
  "blockchain_blocks_left_in_round": 2,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199999593864828,
  "blockchain_random_seed": "577ce365588a0bbc0efb115efa67ead8a6223d93",
  "blockchain_database_version": 109,
  "blockchain_version": 104,
  "network_num_connections": 8,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140702T045406",
  "ntp_error": -0.37929400000000002,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "27 hours in the future",
  "wallet_unlocked_until_timestamp": "20140703T080438",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}

The account is registered on the blockchain:
Code: [Select]
blockchain_list_accounts fox 1
I can receive funds, but sending fails:
Code: [Select]
wallet_transfer 100 XTS fox alt "thanks for the funds"
7 bad_cast_exception: Bad Cast
Invalid cast from type 'int64_type' to Object
    {"type":"int64_type"}
    th_a  variant.cpp:505 get_object

    {}
    th_a  wallet.cpp:2492 get_priority_fee

    {"real_amount_to_transfer":100,"amount_to_transfer_symbol":"XTS","from_account_name":"fox","to_account_name":"alt","memo_message":"thanks for the funds"}
    th_a  wallet.cpp:1877 transfer_asset

    {}
    th_a  common_api_client.cpp:771 wallet_transfer

    {"command":"wallet_transfer"}
    th_a  cli.cpp:538 execute_command

What must I do to resolve my sending issues and restore full wallet functionality?  Perhaps my wallet copy/paste (export/import) method is flawed.  Any insight is greatly appreciated.

-Fox

It is currently not recommended to keep wallets between Dry Runs, but for this particular issue, you can try running 'wallet_set_priority_fee 0.1' to fix it.

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
Re: Dry Run 7: The Power of DPOS
« Reply #83 on: July 02, 2014, 08:50:32 am »
DATE   FROM   TO   MEMO   AMOUNT   FEE
2014年7月2日 GMT+8下午4:13:00   liondani   dexinwong      33 XTS   0 XTS
2014年7月2日 GMT+8下午3:40:15   liondani   dexinwong      50 XTS   0 XT


 :D :D :D

Offline vikram

Re: Dry Run 7: The Power of DPOS
« Reply #84 on: July 02, 2014, 08:54:59 am »
damn, still cannot import keyhotee, problem is in my brainkey because it contains characters like "!" and "@", after "!" no letters are scanned and get wrong keyhotee id scanned  :-\

so i join to the population of beggars, please send me some funds to play with

domis-1
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8

thanks

So even entering you brainkey in quotes "<brainkey>" does not work?

If you are on Windows, you can try running the latest nightly build of Keyhotee from: http://bitshares.org/resources/downloads/ which has a button to copy your private key for an identity. You can then import this private key into the BitShares client using 'wallet_import_private_key <keyhotee_private_key>'. I was able to successfully claim my name from the genesis block using this method. Updated Mac and Linux Keyhotee builds coming soon.

Others please let us know if you have trouble with the brainkeys as well.

Offline vikram

Re: Dry Run 7: The Power of DPOS
« Reply #85 on: July 02, 2014, 09:01:38 am »
Found this today:
Code: [Select]
wallet-1 (unlocked) >>>
Program received signal SIGBUS, Bus error.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
37      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.
(gdb)

Then tried to run and exit manually and got this:
Code: [Select]
(wallet closed) >>> exit
[Thread 0x7fffebd3d700 (LWP 7840) exited]

Program received signal SIGSEGV, Segmentation fault.
bts::db::level_map<fc::ripemd160, bts::blockchain::block_record>::find (this=0xe8, key=...)
    at /root/bitshares_toolkit/libraries/db/include/bts/db/level_map.hpp:170
170                iterator itr( _db->NewIterator( ldb::ReadOptions() ) );
(gdb)

Restarted the whole system and everything works , for now.  ???

Make sure you are using the latest build and wiped your data directory from the previous dry run, and let us know if it happens again. Thanks!

Offline wackou

Re: Dry Run 7: The Power of DPOS
« Reply #86 on: July 02, 2014, 09:05:16 am »
Found this today:
Code: [Select]
wallet-1 (unlocked) >>>
Program received signal SIGBUS, Bus error.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
37      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.
(gdb)

happened to me too in a previous run, searched for quite some time, and then realized this happened because I ran out of space on my VPS (because p2p.log exploded and ate > 50GB). Maybe this is the same for you (and the reboot cleaned some stuff hence why it seems to work for you now)
Please vote for witness wackou! More info at http://digitalgaia.io

Offline cgafeng

Re: Dry Run 7: The Power of DPOS
« Reply #87 on: July 02, 2014, 09:21:25 am »
Code: [Select]
delegate (unlocked) >>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         2     YES                  NO
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        18     YES                 YES

BTC:1EYwcZ9cYVj6C9LMLafdcjK9wicVMDV376

Offline alt

  • Hero Member
  • *****
  • Posts: 2806
    • View Profile
  • BitShares: baozi
Re: Dry Run 7: The Power of DPOS
« Reply #88 on: July 02, 2014, 09:41:34 am »
get 1 fork
Code: [Select]
delegate (unlocked) >>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        16     YES                 YES
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         4     N/A                  NO
alexxy should  produce block 2841 at 09:10:45, but I get this block at 09:11:01(latency 16s)
vikram10 didn't get that block in time by alexxy obvious, produce another block after 2840 at 09:11:00.
Code: [Select]
delegate (unlocked) >>> blockchain_list_blocks 2840 3
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    TOTAL FEES      LATENCY PROCESSING TIME
-------------------------------------------------------------------------------------------------------------------
2840    2014-07-02T09:10:30 init76                          31      8717    3.10000 XTS     3       0.626981       
2841    2014-07-02T09:10:45 alexxy                          32      8854    3.20000 XTS     16      0.634879       
N/A     MISSED              N/A                             N/A     N/A     N/A             N/A     N/A           
2842    2014-07-02T09:11:15 testz                           33      8714    3.30000 XTS     5       0.613875 

Offline CalabiYau

Re: Dry Run 7: The Power of DPOS
« Reply #89 on: July 02, 2014, 09:51:13 am »

So even entering you brainkey in quotes "<brainkey>" does not work?
(...)
Others please let us know if you have trouble with the brainkeys as well.

This hint solved my "é" problem - import o.k. thx