« previous next »
Pages: [1]   Go Down

Author Topic: Lost Market Order  (Read 1318 times)

0 Members and 1 Guest are viewing this topic.

September 11, 2015, 07:23:50 am Reply #4

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: Lost Market Order
The wallet generates a new key for every order .. hence there is no key reuse but you may nees to regenerate more keys ..
Logged
September 11, 2015, 01:40:07 am Reply #3

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Re: Lost Market Order
Solved with 50000 keys regeneration. Few months ago, he experienced similar problem, so he regenerated keys 22000 at that time. Because of previous regeneration, 22000 did not work now, but larger number worked.
Logged
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop
September 10, 2015, 06:02:07 am Reply #2

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: Lost Market Order
did he wait for the rescan to complete after regeneration of the keys? He may also scan the block with the tx directly .. alternatively if he is a heavy trade he may nees to regenerate even more keys
Logged
September 10, 2015, 05:31:57 am Reply #1

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Lost Market Order
A Korean community member lost his (huge) market order. In wallet_account_transaction_history, the order is shown as from his ID to UNKNOWN. He followed recover fund wiki (generated keys 10500, 11000, 12000, 22000) but had no change. Please help him and thanks in advance.
Logged
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop
Pages: [1]   Go Up
« previous next »
 

Page created in 0.21 seconds with 26 queries.