Main Menu

scan failure? Bad address

Started by jsidhu, December 08, 2014, 03:35:14 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

matt608

Cusknee has a problem which sounds related to this - can anyone help? He voted and his funds never came back.
https://bitsharestalk.org/index.php?topic=11847.msg159613#msg159613

toast

Quote from: cn-members on December 08, 2014, 02:32:28 PM
Quote from: bytemaster on December 08, 2014, 02:16:44 PM
Quote from: monsterer on December 08, 2014, 01:54:01 PM
Quote from: xeroc on December 08, 2014, 01:29:04 PM
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.

Thanks , need it ASAP ,  because it's the PLAY snapshot time .

https://github.com/BitShares/bitshares/releases/tag/v0.4.24.1
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

cn-members

Quote from: bytemaster on December 08, 2014, 02:16:44 PM
Quote from: monsterer on December 08, 2014, 01:54:01 PM
Quote from: xeroc on December 08, 2014, 01:29:04 PM
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.

Thanks , need it ASAP ,  because it's the PLAY snapshot time .
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.

bytemaster

Quote from: monsterer on December 08, 2014, 01:54:01 PM
Quote from: xeroc on December 08, 2014, 01:29:04 PM
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)

Very interesting.  Looks like something that was already fixed for our next release.  We will get a new release out today that addresses this issue among several others.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

monsterer

Quote from: xeroc on December 08, 2014, 01:29:04 PM
As long as delegates continue signing block it is a minor issue .. imho

To me a crash bug is still serious. Something which causes the delegates to crash is worse, of course. :)
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

xeroc

As long as delegates continue signing block it is a minor issue .. imho

monsterer

Quote from: CLains on December 08, 2014, 12:09:57 PM
It was a minor bug with the wallet.

I like your definition of 'minor' :p
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

CLains

It was a minor bug with the wallet.

Devs already handled it, so exchanges just needs to update and we are good.  ;)
Vote for BitSpace EOS Block Producer!

[url="https://steemit.com/eos/@bitspace/bitspace-eos-block-producer-candidate"]https://steemit.com/eos/@bitspace/bitspace-eos-block-producer-candidate[/url]

liondani

Quote from: alt on December 08, 2014, 07:33:25 AM
the problem is because somebody try a escrow transaction, but still not support by client

btsbots (unlocked) >>> blockchain_get_block 1209399
{
  "previous": "006648b96af11d06e3b6c55c8cf295d571148c51",
  "block_num": 1209399,
  "timestamp": "20141208T003100",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "b4864ba1493f38fa226b9d49e404c329a73419ff",
  "previous_secret": "690d2d987911bed1ef2283a683045de12a3cdf2f",
  "delegate_signature": "206be773a62d0005d750a45dfd16a71b1a8bbb5c3b087582603c6b6f4df93acbd3bb55c0e3112e9ce02a99723088e78b8168f79f781212dd47a2a95faa701d0112",
  "user_transaction_ids": [
    "4a7efe44c91909c1214762c186b8c57ae12a16f3",
    "d307c1e97d427428f1d5859d2be608ff1b2ccc6f"
  ]
}
btsbots (unlocked) >>> blockchain_get_transaction 4a7efe44c91909c1214762c186b8c57ae12a16f3
{
  "trx": {
    "expiration": "20141208T013055",
    "delegate_slate_id": null,
    "operations": [{
        "type": "deposit_op_type",
        "data": {
          "amount": 1000000,
          "condition": {
            "asset_id": 0,
            "delegate_slate_id": 9473675977916939725,
            "type": "withdraw_escrow_type",
            "data": {
              "owner": "BTSX111111111111111111113MQ7LD",
              "start_time": "20240917T192947",
              "duration": 3845107543,
              "original_balance": -4376472804032454471
            }
          }
        }
      },{

with me the problems started when trying to email somebody via the BTS wallet before it is officially supported...  I suggest they must somehow block commands for the client  as long as they are still  on BETA stage ...  at least for the gui...

Sent from my ALCATEL ONE TOUCH 997D

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

cn-members

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.

alt

the problem is because somebody try a escrow transaction, but still not support by client

btsbots (unlocked) >>> blockchain_get_block 1209399
{
  "previous": "006648b96af11d06e3b6c55c8cf295d571148c51",
  "block_num": 1209399,
  "timestamp": "20141208T003100",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "b4864ba1493f38fa226b9d49e404c329a73419ff",
  "previous_secret": "690d2d987911bed1ef2283a683045de12a3cdf2f",
  "delegate_signature": "206be773a62d0005d750a45dfd16a71b1a8bbb5c3b087582603c6b6f4df93acbd3bb55c0e3112e9ce02a99723088e78b8168f79f781212dd47a2a95faa701d0112",
  "user_transaction_ids": [
    "4a7efe44c91909c1214762c186b8c57ae12a16f3",
    "d307c1e97d427428f1d5859d2be608ff1b2ccc6f"
  ]
}
btsbots (unlocked) >>> blockchain_get_transaction 4a7efe44c91909c1214762c186b8c57ae12a16f3
{
  "trx": {
    "expiration": "20141208T013055",
    "delegate_slate_id": null,
    "operations": [{
        "type": "deposit_op_type",
        "data": {
          "amount": 1000000,
          "condition": {
            "asset_id": 0,
            "delegate_slate_id": 9473675977916939725,
            "type": "withdraw_escrow_type",
            "data": {
              "owner": "BTSX111111111111111111113MQ7LD",
              "start_time": "20240917T192947",
              "duration": 3845107543,
              "original_balance": -4376472804032454471
            }
          }
        }
      },{

alt

here is the patch for client, delegate don't need to upgrade.

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!" );


svk

Same here:

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

merockstar

Quote from: jsidhu on December 08, 2014, 06:42:11 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.

zerosum

Quote from: jsidhu on December 08, 2014, 06:42:11 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.

jsidhu

Anyone try to delete mail folder?
Hired by blockchain | Developer
delegate: dev.sidhujag

cn-members

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.

emailtooaj

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 - [url="https://beyondbitcoin.org"]https://beyondbitcoin.org[/url] support the Hangouts! BTS Tri-Fold Brochure [url="https://bitsharestalk.org/index.php/topic,15169.0.html"]https://bitsharestalk.org/index.php/topic,15169.0.html[/url]
Tip BROWNIE.PTS to EMAILTOOAJ

onceuponatime

Quote from: clayop on December 08, 2014, 04:53:53 AM
Are transactions stopped? Is current situation serious or just a happening?

Is this an emergency?

Are core devs aware of it?

clayop

Are transactions stopped? Is current situation serious or just a happening?
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

jsidhu

#6
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.
Hired by blockchain | Developer
delegate: dev.sidhujag

jsidhu

Quote from: onceuponatime 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".

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

onceuponatime

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".

jsidhu

Quote from: merockstar on December 08, 2014, 03:38:37 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

merockstar

I think I just had a similar error. Before attempting a transaction and segmentation faulting.

jsidhu

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