Testing BitShares XT Launch...

[xeroc]

Not at my side

[BTSdac]

So are the other active peers somewhere, because loading the blockchain stops at around block 6000.
I know BM stopped the main node. But did he mean he stop the one, single trustee? that what describe it?!

any news ?

[jae208]

how about the progress?

 

[sudo]

how about the progress?

[xeroc]

So are the other active peers somewhere, because loading the blockchain stops at around block 6000.
I know BM stopped the main node. But did he mean he stop the one, single trustee? that what describe it?!

[crazybit]

Heh, now it builds but old bug returns

Code: [Select]

1238056ms       th_a                 main ] bad_cast
Invalid cast from type '6' to Object
    {"type":6}
    th_a  variant.cpp:498 get_object
unable to load /home/alexxy/.bitsharesxt/default_wallet.dat
    {"wal":"/home/alexxy/.bitsharesxt/default_wallet.dat"}
    th_a  wallet.cpp:442 open                   main.cpp:157


coz the wallet data structure was changed after 5May, the wallet created before that day can not be opened if the client is built with the latest code.

Code: [Select]

       //std::unordered_map<address,std::string>                      receive_addresses;
       std::unordered_set<receive_address>                          receive_addresses;


[xeroc]

Having problems sending..

Code: [Select]

>>> getbalance
180499303231
>>> sendtoaddress BvoktQoKdxB6AjZabBkxGret12rMUsJ2s 180499303231
assert
!"Unable to collect sufficient unspent inputs":
    {"requested_amount":{"amount":180499304884,"unit":0},"total_collected":{"amount":180499303231,"unit":0}}
    th_a  wallet.cpp:315 collect_inputs
{"amount":180499303231,"unit":0} to BvoktQoKdxB6AjZabBkxGret12rMUsJ2s
    {"amnt":{"amount":180499303231,"unit":0},"to":"BvoktQoKdxB6AjZabBkxGret12rMUsJ2s"}
    th_a  wallet.cpp:771 send_to_address


You cannot send your full balance, as a transaction fee is required.

Perhaps we need some mechanism to adjust the amount downward by the necessary amount and ask for confirmation if it's okay.

Had the very same issue .. took some time until I figured out to reduce the fee .. mabe you can make this dialog a little more readble

[vikram]

Having problems sending..

Code: [Select]

>>> getbalance
180499303231
>>> sendtoaddress BvoktQoKdxB6AjZabBkxGret12rMUsJ2s 180499303231
assert
!"Unable to collect sufficient unspent inputs":
    {"requested_amount":{"amount":180499304884,"unit":0},"total_collected":{"amount":180499303231,"unit":0}}
    th_a  wallet.cpp:315 collect_inputs
{"amount":180499303231,"unit":0} to BvoktQoKdxB6AjZabBkxGret12rMUsJ2s
    {"amnt":{"amount":180499303231,"unit":0},"to":"BvoktQoKdxB6AjZabBkxGret12rMUsJ2s"}
    th_a  wallet.cpp:771 send_to_address


You cannot send your full balance, as a transaction fee is required.

Perhaps we need some mechanism to adjust the amount downward by the necessary amount and ask for confirmation if it's okay.

[bitcoinerS]

Having problems sending..

Code: [Select]

>>> getbalance
180499303231
>>> sendtoaddress BvoktQoKdxB6AjZabBkxGret12rMUsJ2s 180499303231
assert
!"Unable to collect sufficient unspent inputs":
    {"requested_amount":{"amount":180499304884,"unit":0},"total_collected":{"amount":180499303231,"unit":0}}
    th_a  wallet.cpp:315 collect_inputs
{"amount":180499303231,"unit":0} to BvoktQoKdxB6AjZabBkxGret12rMUsJ2s
    {"amnt":{"amount":180499303231,"unit":0},"to":"BvoktQoKdxB6AjZabBkxGret12rMUsJ2s"}
    th_a  wallet.cpp:771 send_to_address


[bytemaster]

Deterministic wallet?

We cannot go fully to a deterministic wallet because we need the ability to import foreign private keys... but it will be a hybrid....

[xeroc]

Deterministic wallet?

[bytemaster]

I just added some extra code to save the wallet on Ctrl+C. 

The key generation algorithm is deterministic so you you can always regenerate your change addresses.

can your exception handling cater for the scenarios that the client crashed or computer power off suddenly?

power failure cannot be handled. Only way to is to sync wallet changes immiediently on disk

It should be saving after every major wallet operation...   One thing that I have realized is that we need to switch to using a database for the wallet so that we can do partial saves with proper logging without the performance hit of having to encrypt / save the entire wallet. 

[alexxy]

I just added some extra code to save the wallet on Ctrl+C. 

The key generation algorithm is deterministic so you you can always regenerate your change addresses.

can your exception handling cater for the scenarios that the client crashed or computer power off suddenly?

power failure cannot be handled. Only way to is to sync wallet changes immiediently on disk

[crazybit]

I just added some extra code to save the wallet on Ctrl+C. 

The key generation algorithm is deterministic so you you can always regenerate your change addresses.

can your exception handling cater for the scenarios that the client crashed or computer power off suddenly?

[xeroc]

Server is down while we fix a few things.

Good to know..

Once you active 'real' p2p this will be very exciting!!

The web wallet has not been updated for 7 days.
Anyone knows where I can get the newest status of this part?

I guess the guys over there are busy getting the server and backends running .. GUI is (in my opinion) secondary to the network/protocol it self.