You may have interest in this command:
wallet_address_create <account_name> [label] [legacy_network_byte]
                      Creates an address which can be used for a simple (non-TITAN) transfer.
Creates an address which can be used for a simple (non-TITAN) transfer.

Parameters:
  account_name (string, required): The account name that will own this address
  label (string, optional, defaults to ""):
  legacy_network_byte (int32_t, optional, defaults to -1): If not -1, use this as the network byte for a BTC-style address.

Returns:
  string

aliases: new_address


What options are there for scanning transactions?

What is the point of “prefixes” in blockchain_get_transaction? What would make transactions share a prefix?

I think if the 'exact' parameter is omitted, the 'prefix' should be a full transaction id, otherwise it could be a part of trx id.
Usage:
blockchain_get_transaction <transaction_id_prefix> [exact]
                      Get detailed information about an in-wallet transaction

Parameters:
  transaction_id_prefix (string, required): the base58 transaction ID to return
  exact (bool, optional, defaults to false): whether or not a partial match is ok


blockchain_list_address_transactions seems to be what I want but I'd prefer a block number.

Are there other commands that I missed that could be used for transaction scanning?

There is a 'block_num' field in the returned object of 'blockchain_list_address_transactions', isn't it?
Or maybe you need 'blockchain_get_block_transactions'?

why is it so hard for this exchanges to take a snapshot

Perhaps because the value is too low.

The problem is that the program creates so much RAM usage that after several hours of downloading blocks, it will get a ram access error (forgot the english term). I have 2 GB now.  Of course I always use "Quit".

Edit: Now it shows 1,3 GB ram usage in the taskmanager. In a while it will show 1,6666666 TB!
Then crash.

E2: This problem has been there since such a long time, I cannot check my balance since months!

2GB is a bit tight..
When you find it's eating much RAM, you could try Quit and re-launch the wallet.
Wish it helps.

Quote from: Rune on January 01, 2015, 08:42:58 pm

dritz3r, you received BTS from the last sharedrop to AGS and PTS. As a result you also received DVS.

I am trying to import my wallet and nothing happend. My donations are made after magic date Feb 28. Beside PTS can we receive BTC back. It's clear that 'social consensus' don't exist any more and I didn't received any BTS.

If you want BTS instead of DVS, just wait for a new version of BTS wallet (maybe release in next week).
Since you have AGS, you may have VOTE and DNS, which will be converted to BTS in the new wallet.

@Excoin your delegate is missing blocks again.

Quote from: abit on January 10, 2015, 10:15:29 am

Code: [Select]

(wallet closed) >>> blockchain_get_block_signee 1303717
10 assert_exception: Assert Exception
!(c.data[1] & 0x80): signature is not canonical
    {}
    th_a  elliptic.cpp:496 fc::ecc::public_key::public_key

    {}
    th_a  common_api_client.cpp:2323 bts::rpc_stubs::common_api_client::blockchain_get_block_signee

    {"command":"blockchain_get_block_signee"}
    th_a  cli.cpp:579 bts::cli::detail::cli_impl::execute_command

Anybody else get this as well?
Exception raises while querying block 1303717,1303906,1303982 and more, the biggest block number with this issue is 1319180.

After re-downloaded the whole block chain the exception remains still.

I'm running [email protected] 64bit and [email protected] 64bit.

Known issue:

https://bitsharestalk.org/index.php?topic=12448.msg164197#msg164197

https://github.com/BitShares/bitshares/issues/1165

On linux you can manually implement the commit vikram made to fix it and recompile to solve the issue, it's a one-line fix.

Thanks!

Then it stopped again and I went to bed shutting down the computer. Now I had a nice sleep and wake up in the hope for the best. Then "critical error, please start again".

It's best to quit the wallet (by clicking menu File->Quit) before shut down the computer.

Quote from: xiahui135 on January 09, 2015, 04:52:57 pm

Quote from: cgafeng on January 09, 2015, 04:44:29 pm

刚创建的钱包需要输入2次一样的密码，这是设置钱包密码，以后你的钱包都需要输入这个密码才能进入

重装了，每次打开，都是解锁界面。让输入密码，然后输入之后软件提示密码错误。
不论选择什么，都是输入密码。。。

那是你之前有设置过密码了，如果钱包里没币的话可以把钱包删了重新创建钱包。
windows开始菜单中选择运行，输入%APPDATA%\BitShares会打开bts钱包目录，如果你确定以前创建的钱包没币的话可以直接把整个BitShares目录删除，再打开客户端。

删除还是小心点好。
把目录改个名字就可以了，或者移动到其他盘。以后要是想起密码可以改回来。