Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: scan failure? Bad address  (Read 852 times)

0 Members and 1 Guest are viewing this topic.

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1337
    • View Profile
scan failure? Bad address
« on: December 08, 2014, 03:35:14 AM »

KEY9EZUvQjARsbqxC☻DQ261f6irmi1MxJj89 was found as a key and thus crashed my client... Stan also had scan failure just like me... I restarted my client and saw this assertion where the key was invalid.


How does a key like that get created? looks like a raw address... hacker?
Hired by blockchain | Developer
delegate: dev.sidhujag

merockstar

  • Guest
Re: scan failure? Bad address
« Reply #1 on: December 08, 2014, 03:38:37 AM »
I think I just had a similar error. Before attempting a transaction and segmentation faulting.

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1337
    • View Profile
Re: scan failure? Bad address
« Reply #2 on: December 08, 2014, 03:39:06 AM »
I think I just had a similar error. Before attempting a transaction and segmentation faulting.

Must have just happened.. Stan had it too.
Hired by blockchain | Developer
delegate: dev.sidhujag

Offline onceuponatime

Re: scan failure? Bad address
« Reply #3 on: December 08, 2014, 03:45:14 AM »
I am getting "Failure during transaction scanning" in my v0.4.24

Tried restarting, same.

Tried rescanning, starts off, but then same.

Uninstalled and then reinstalled, said: "Failure during transaction scanning"

Tried rescanning and watched closely. It rescanned 99% and then "Failure during transaction scanning".

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1337
    • View Profile
Re: scan failure? Bad address
« Reply #4 on: December 08, 2014, 03:51:53 AM »
I am getting "Failure during transaction scanning" in my v0.4.24

Tried restarting, same.

Tried rescanning, starts off, but then same.

Uninstalled and then reinstalled, said: "Failure during transaction scanning"

Tried rescanning and watched closely. It rescanned 99% and then "Failure during transaction scanning".

It just happened... check the logs..
Hired by blockchain | Developer
delegate: dev.sidhujag

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1337
    • View Profile
Re: scan failure? Bad address
« Reply #5 on: December 08, 2014, 04:00:47 AM »
wonder which delegate signed the block.. maybe they tampering with the chain somehow.. dont know the consensus on how blocks are accepted intot he chain... thought its a majority between all 101 delegates? Dunno maybe just a loophole with the pub key address validation.

Nothing was pushed to master so its not the code, either someone signed a bad block on purpose or the validation isn't right.
« Last Edit: December 08, 2014, 04:03:13 AM by jsidhu »
Hired by blockchain | Developer
delegate: dev.sidhujag

Offline clayop

Re: scan failure? Bad address
« Reply #6 on: December 08, 2014, 04:53:53 AM »
Are transactions stopped? Is current situation serious or just a happening?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline onceuponatime

Re: scan failure? Bad address
« Reply #7 on: December 08, 2014, 05:47:49 AM »
Are transactions stopped? Is current situation serious or just a happening?

Is this an emergency?

Are core devs aware of it?

Offline emailtooaj

Re: scan failure? Bad address
« Reply #8 on: December 08, 2014, 05:58:38 AM »
Ditto!
I'm having the same "Failure During Transaction Scanning" error.

I've restarted everything to no avail!
Sound Editor of Beyondbitcoin Hangouts. Listen to latest here - https://beyondbitcoin.org support the Hangouts! BTS Tri-Fold Brochure https://bitsharestalk.org/index.php/topic,15169.0.html
Tip BROWNIE.PTS to EMAILTOOAJ

Offline cn-members

  • Sr. Member
  • ****
  • Posts: 365
    • View Profile
Re: scan failure? Bad address
« Reply #9 on: December 08, 2014, 06:20:54 AM »
last month I had to  export all my private keys , exit the wallet , rename the wallet data folder ,  start the wallet , create a new one , import all my private keys (BTSfniksefNRKENFKfFNDKFNKD,this kind of private key ) , then wait for a rescan , solved the problem .

Simple rescan didn't solve it .
BTS中文区发言人公共账号,帮助社区有效沟通与交流。
Chinese Community Spokesman Account,to help the effective communication between Chinese and other members of the community.We're not translators to do regular translations , but will help with vital ones as we see fit and available at that time.

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1337
    • View Profile
Re: scan failure? Bad address
« Reply #10 on: December 08, 2014, 06:42:11 AM »
Anyone try to delete mail folder?
Hired by blockchain | Developer
delegate: dev.sidhujag

zerosum

  • Guest
Re: scan failure? Bad address
« Reply #11 on: December 08, 2014, 06:56:44 AM »
Anyone try to delete mail folder?

If I would expect somebody to come with the most illogical solution that works, that will be *Dani the Lion* ...so just try it, I say.

merockstar

  • Guest
Re: scan failure? Bad address
« Reply #12 on: December 08, 2014, 07:06:56 AM »
Anyone try to delete mail folder?

yes. works for the segmentation fault im experiencing in a different thread. still getting the scanning error though.

Offline svk

Re: scan failure? Bad address
« Reply #13 on: December 08, 2014, 07:09:02 AM »
Same here:

Code: [Select]
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Beginning scan at block 1209398...
Scan failure.
Worker: dev.bitsharesblocks

Offline alt

Re: scan failure? Bad address
« Reply #14 on: December 08, 2014, 07:32:01 AM »
here is the patch for client, delegate don't need to upgrade.
Code: [Select]
diff --git a/libraries/wallet/transaction_ledger.cpp b/libraries/wallet/transaction_ledger.cpp
index 0623a6c..0d6e98a 100644
--- a/libraries/wallet/transaction_ledger.cpp
+++ b/libraries/wallet/transaction_ledger.cpp
@@ -1178,6 +1178,11 @@ bool wallet_impl::scan_deposit( const deposit_operation& op, const vector<privat
           // TODO: FC_THROW( "withdraw_option_type not implemented!" );
           break;
        }
+       case withdraw_escrow_type:
+       {
+          // TODO: FC_THROW( "withdraw_option_type not implemented!" );
+          break;
+       }
        default:
        {
           FC_THROW( "unknown withdraw condition type!" );

 

Google+