BitShares Forum
Main => General Discussion => Topic started by: bytemaster on May 02, 2014, 07:42:32 pm
-
Anyone who cares to compile the code can now connect to the XT network by running this command:
./bts_xt_client --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.182:8765 --data-dir data
When you first launch the client it will ask you to create an account. For now keep the first password it asks you for blank, this will keep everything but your private keys unencrypted. When asked for your second password enter something strong enough to protect your spending keys.
You will be given a command line interface... here are some basic commands you may want to try:
>>>help
>>>import_bitcoin_wallet "full_path_to_wallet" "bitcoinwalletpassword"
>>>rescan
>>> getbalance
678238484237
>>>getnewaddress "account"
ArU5RfEEHypBzs8FaAZ4arfvc8TfZFSgX
>>>sendtoaddress ArU5RfEEHypBzs8FaAZ4arfvc8TfZFSgX ALL_YOUR_MONEY
About to broadcast transaction:
Inputs:
678238484237 claim_by_pts PiSCkixAS9t7XXcXV8VpxLXAAzg1TkfG4d
Outputs:
10000 claim_by_signature ArU5RfEEHypBzs8FaAZ4arfvc8TfZFSgX
678238474070 claim_by_signature PQnSj1kY8zftZCrZUbEqewEZNFWkEby1W
Total in: 678238484237
Total out: 678238484070
Fee: 167
Send this transaction? (Y/n)
>>> Y
Transaction sent (id is 14bd6552eef12700e5316b6cad5f4dcd0f3b4170)
>>>
-
The wallet functions are very crude right now, but they get the job done.
The web interface to the wallet will be made available as soon as it is ready.
-
+5%
-
+5%
-
Is the nightly build wallet ok for test?
In http://bitshares.org/downloads/
-
Is the nightly build wallet ok for test?
In http://bitshares.org/downloads/
Probably not for 24 hours.
-
Awesome \o/
-
What's in the genesis block? Doesn't include a really old AGS donation of mine
-
How can I get block's transactions? I can't get that using getblock or get_block_by_number.
I can see there're transactions in block 26 like below but don't know how I can get transactions in it using command or rpc:
>>> get_block_by_number 26
{
"version": 0,
"block_num": 26,
"prev": "8b9fec8966c166561b3ff1208afa85d40e372406",
"timestamp": "20140502T194000",
"next_fee": 1000,
"next_reward": 200,
"total_shares": 395999999969737,
"trx_mroot": "14bd6552eef12700e5316b6cad5f4dcd0f3b4170",
"trustee_signature": "1fd4cd992fd9a5219708a1f3a9a6bfd07fcbe75084fed2022e54e43fb50d90704e476c3ed650c6e8ddab777fb1867d6b1b334ebe142ec67b2f3e5639b4f613a1ee"
}
-
I need to add an rpc call for that.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Should be feb 28 th snapshot.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
import_private_key then getbalance is not giving me anything from my feb28 snapshot keys
-
+5%
-
import_private_key then getbalance is not giving me anything from my feb28 snapshot keys
Rescan?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Import private key does not work with btc or pts keys
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
could anyone pls sent me some test btsx ? thanks
-
Import private key does not work with btc or pts keys
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
how to import pts keys
-
-- Using /usr as ICU root
Found ICU version 4.8.1.1
CMake Error at CMakeLists.txt:43 (MESSAGE):
Error, BitShares require ICU version 52.1 or 53.1
-
+5% +5% +5%
-
Import private key does not work with btc or pts keys
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Why not?
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/rpc/rpc_server.cpp#L1147
Looks like the wallet has the private key so it should know that it can spend the output in the genesis block when it rescans. We shouldn't have to do a separate "sweep" transaction for the balance to show.
-
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
could anyone pls sent me some test btsx ? thanks
pls ignore it, as i have missed the private key of above address, seems there is a bug, the generated address was not saved to the wallet when i use CTRL+C to terminate the client but not use the command "quit" to exit
-
>>> getnewaddress CrazyBit
spending passphrase:
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH : CrazyBit
>>> ^C
bts_xt_client.exe --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.
182:8765 --data-dir D:\bitshares\VS2013_update\programs\bts_xt\Debug\Client
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
>>> getnewaddress CrazyBit
spending passphrase:
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH : CrazyBit
>>> quit
unbelievable, the private key come back again,is it possible to generate the same key in different time? as the operation history enclosed above, i terminate the client without saving the key to the wallet, and i can get the same key "EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH" after i re-launch the client.
-
I think there's a pool of keys it generated when it made the wallet and it's just giving them back to you in the same order. Try deleting your default wallet and see if you get a new set of keys.
-
BTS wallet's approach seems to be HD wallet.
Refer https://en.bitcoin.it/wiki/Deterministic_wallet (https://en.bitcoin.it/wiki/Deterministic_wallet)
>>> getnewaddress CrazyBit
spending passphrase:
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH : CrazyBit
>>> ^C
bts_xt_client.exe --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.
182:8765 --data-dir D:\bitshares\VS2013_update\programs\bts_xt\Debug\Client
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
>>> getnewaddress CrazyBit
spending passphrase:
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH : CrazyBit
>>> quit
unbelievable, the private key come back again,is it possible to generate the same key in different time? as the operation history enclosed above, i terminate the client without saving the key to the wallet, and i can get the same key "EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH" after i re-launch the client.
-
BTS wallet's approach seems to be HD wallet.
Refer https://en.bitcoin.it/wiki/Deterministic_wallet (https://en.bitcoin.it/wiki/Deterministic_wallet)
From the code from wallet.cpp(wallet::new_public_key), I think that it will generate the same series of keys if you start from the same wallet key password and the same encrypted_base_key.
-
I need to add an rpc call for that.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Thanks for the feedback.
I see that getblock returns signed_block_header which doesn't have transaction ids. If it returns digest_block by calling fetch_digest_block, that'll satisfy my needs. Anyway, another api returning block_trxs.fetch(blocknumber) is also fine.
-
I am caught by a compile error as the following.
/home/XXXX/bitshares_toolkit/libraries/fc/GitSHA3.cpp:6:29: error: ‘HEAD’ was not declared in this scope
#define GIT_UNIX_TIMESTAMP3 HEAD-HASH-NOTFOUND
It seems g++ treats "HEAD" as a token instead of whole "HEAD-HASH-NOTFOUND". Is it an issue of gcc version?
My g++ version is 4.8.1
Anyone know how to solve it? Thanks.
p.s. I've followed the build guide for Ubuntu.
-
I am caught by a compile error as the following.
/home/XXXX/bitshares_toolkit/libraries/fc/GitSHA3.cpp:6:29: error: ‘HEAD’ was not declared in this scope
#define GIT_UNIX_TIMESTAMP3 HEAD-HASH-NOTFOUND
It seems g++ treats "HEAD" as a token instead of whole "HEAD-HASH-NOTFOUND". Is it an issue of gcc version?
My g++ version is 4.8.1
Anyone know how to solve it? Thanks.
p.s. I've followed the build guide for Ubuntu.
Replace HEAD-HASH-NOTFOUND with 1398967484 and try building again.
-
Just tested bts_xt_client. The ratio between bts_xt_balance and ags_balance from the same wallet is 1.6395. Shouldn't it be 3.33 according to the Feb 28th snapshot?
-
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
could anyone pls sent me some test btsx ? thanks
You should have some funds.
-
EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
could anyone pls sent me some test btsx ? thanks
You should have some funds.
got it ,thanks
-
Are we sure that change-addresses are stored correctly in the database? if I send a tx to some addresses (generated with the utility "bts_create_key") and kill the terminal with CTRL+C .. restart the client again and type 'getbalance' it get a 0 in contrast to what I expect as change!? Maybe I made some mistake?
-
ghmm cannot see my adresses
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
>>> list_receive_addresses
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
>>> list_send_addresses
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
Its build of git master
-
Btw also how to import pts wallet?
-
ghmm cannot see my adresses
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
>>> list_receive_addresses
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
>>> list_send_addresses
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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:375 open
Its build of git master
is your wallet there?
/home/alexxy/.bitsharesxt/default_wallet.dat
do you have it named something else? open_wallet othername
-
yep its there
alexxy@x240 ~/Src/bitshares_toolkit/build/programs/bts_xt $ LANG=C ls -lh ~/.bitsharesxt/default_wallet.dat
-rw-r--r-- 1 alexxy alexxy 2.1K May 3 21:58 /home/alexxy/.bitsharesxt/default_wallet.dat
-
"open_wallet default"?
-
Are we sure that change-addresses are stored correctly in the database? if I send a tx to some addresses (generated with the utility "bts_create_key") and kill the terminal with CTRL+C .. restart the client again and type 'getbalance' it get a 0 in contrast to what I expect as change!? Maybe I made some mistake?
I believe the client does not usually automatically save after running rpc commands; someone seems to be looking at this: https://github.com/BitShares/bitshares_toolkit/pull/50
-
"open_wallet default"?
same problem =\
-
Call create new address a few times the rescan and your balance will be there.
Will add a crtl-c catch.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
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.
-
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.
Same problem with your recent changes
creating default config file /home/alexxy/.bitsharesxt/config.json
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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
>>>
-
I am caught by a compile error as the following.
/home/XXXX/bitshares_toolkit/libraries/fc/GitSHA3.cpp:6:29: error: ‘HEAD’ was not declared in this scope
#define GIT_UNIX_TIMESTAMP3 HEAD-HASH-NOTFOUND
It seems g++ treats "HEAD" as a token instead of whole "HEAD-HASH-NOTFOUND". Is it an issue of gcc version?
My g++ version is 4.8.1
Anyone know how to solve it? Thanks.
p.s. I've followed the build guide for Ubuntu.
Replace HEAD-HASH-NOTFOUND with 1398967484 and try building again.
Thank you :)
Sent from my iPhone using Tapatalk
-
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.
Same problem with your recent changes
creating default config file /home/alexxy/.bitsharesxt/config.json
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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
>>>
There should be no need to call "open_wallet" from the CLI. It is opened automatically.
-
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
BFL73TtraijmhJ457ba1NTrePDNN9p6vG : heyD
Could anyone please send me some bts ?
-
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
BFL73TtraijmhJ457ba1NTrePDNN9p6vG : heyD
Could anyone please send me some bts ?
sent you some just now, please check.
-
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
BFL73TtraijmhJ457ba1NTrePDNN9p6vG : heyD
Could anyone please send me some bts ?
sent you some just now, please check.
Thanks.
But I still have not received. How many confirmations are needed ?
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
BFL73TtraijmhJ457ba1NTrePDNN9p6vG : heyD
>>> getinfo
{
"balance": 0,
"version": 0,
"protocolversion": 0,
"walletversion": 0,
"blocks": 3505,
"connections": 0,
"unlocked_until": 0
}
>>> getblockcount
3505
>>> getbalance
0
>>>
>>> get_transaction_history
[]
-
suppose it should be done within 30 seconds, seems this is something wrong ,my transaction was not included in the new block
>>> getblockcount
4294967295
>>> get_transaction_history
[[
"9bec511a3e1149bf0b6b1ec274d2de40d3f6698f",{
"trx": {
"version": 0,
"stake": 1467989992,
"vote": 68,
"valid_until": "19700101T000000",
"inputs": [{
"output_ref": {
"trx_hash": "735687d2efeb25ee92e5c1d5696183c6b26077a1",
"output_idx": 0
},
"input_data": ""
},{
"output_ref": {
"trx_hash": "735687d2efeb25ee92e5c1d5696183c6b26077a1",
"output_idx": 1
},
"input_data": ""
}
],
"outputs": [{
"amount": {
"amount": 5000,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "BFL73TtraijmhJ457ba1NTrePDNN9p6vG"
}
},{
"amount": {
"amount": 294579,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "Fiw2xbEHacPCKaagsJhanFjXRojusWnav"
}
}
],
"sigs": [
"1f968aa426af73add678f80c9374746444d54f37b2bdc68911d687119f751089437871eb76773a592bb28928f422b2deb000d4f332242f34672b28745a1a726edc",
"1fc06e77bf668d2e6ac80087bc4095375eea7161853b358e38e3b5e1f2d9a57fa0464264b0e9b9d8b72f68f67574416be7b610182c5a6c515fac7001f7fdc65eb3"
]
},
"memo": "",
"block_num": 4294967295,
"to": [],
"from": [],
"delta_balance": [],
"valid": false,
"fees": []
}
],
]
>>>
-
suppose it should be done within 30 seconds, seems this is something wrong ,my transaction was not included in the new block
I received 10,000 bts just now. But I am not sure whether they're sent by you. And I am also a little confused by the 'getblockcount', the count I got was quite different from what you got.
>>> getbalance
10000
>>> get_transaction_history
[[
"46f0660d71beb637d7a0997b6e9f2f027fc0279e",{
"trx": {
"version": 0,
"stake": 1904589218,
"vote": 68,
"valid_until": "19700101T000000",
"inputs": [{
"output_ref": {
"trx_hash": "735687d2efeb25ee92e5c1d5696183c6b26077a1",
"output_idx": 0
},
"input_data": ""
},{
"output_ref": {
"trx_hash": "735687d2efeb25ee92e5c1d5696183c6b26077a1",
"output_idx": 1
},
"input_data": ""
}
],
"outputs": [{
"amount": {
"amount": 10000,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "BFL73TtraijmhJ457ba1NTrePDNN9p6vG"
}
},{
"amount": {
"amount": 289579,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "36J4jwynAFmqFyTQVjUvcS15KDvjnYuhh"
}
}
],
"sigs": [
"1fff2614a317162890069fc89763bfc68190c79221aaec17681fe59b3a3c3245f31303cd0a1420cb862c37e95d41eac959aee2834d17bc7f1d6ebaa9e2972bd0f6",
"2064003beaca6ce21277235f814ec1b8035e7ebc0de33235de4f26905f47e977f31539ebcc4ff8aa0a3849dd6b0f355da91fd6088c69312efba74309095fd537c8"
]
},
"memo": "",
"block_num": 4294967295,
"to": [[
"36J4jwynAFmqFyTQVjUvcS15KDvjnYuhh",
"36J4jwynAFmqFyTQVjUvcS15KDvjnYuhh"
]
],
"from": [[
"BFL73TtraijmhJ457ba1NTrePDNN9p6vG",
"heyD"
]
],
"delta_balance": [[
0,
10000
]
],
"valid": true,
"fees": []
}
]
]
>>> getblockcount
3582
-
you should have it now,my transaction has been included in the new block
>>> list_receive_addresses
address : account
--------------------------------------------------------------------------------
BFL73TtraijmhJ457ba1NTrePDNN9p6vG : heyD
Could anyone please send me some bts ?
-
I received 10,000 bts just now. But I am not sure whether they're sent by you. And I am also a little confused by the 'getblockcount', the count I got was quite different from what you got.
i triggered 2 transactions , seems the network only accept the 10,000 one, but not accept the 5,000 one, i also confused.
for the block no. issue, my blockchain DB has not been completely synchronized yet when i issue the "getblockcount", do not know if it is due to this.
-
I don't know whether I can or how to import my multibit wallet or pts wallet. Could anyone send me some?
my address:
An2Siuwq3LhiebtxjAoaMER4JSrFMoRDb
Just a few is OK. Thanks.
-
I don't know whether I can or how to import my multibit wallet or pts wallet. Could anyone send me some?
my address:
An2Siuwq3LhiebtxjAoaMER4JSrFMoRDb
Just a few is OK. Thanks.
Sent.
>>> sendtoaddress An2Siuwq3LhiebtxjAoaMER4JSrFMoRDb 1111
About to broadcast transaction:
Inputs:
10000 claim_by_signature BFL73TtraijmhJ457ba1NTrePDNN9p6vG
Outputs:
1111 claim_by_signature An2Siuwq3LhiebtxjAoaMER4JSrFMoRDb
8722 claim_by_signature EKP1QAViRcVzStV39rYCfvPuVLgzfMJMH
Total in: 10000
Total out: 9833
Fee: 167
Send this transaction? (Y/n)
Y
Transaction sent (id is 277db551e1aa585e99b1af4aa1a0e34dc3d72239)
@CrazyBit
>>> sendtoaddress EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH 3333
About to broadcast transaction:
Inputs:
8722 claim_by_signature EKP1QAViRcVzStV39rYCfvPuVLgzfMJMH
Outputs:
3333 claim_by_signature EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH
5222 claim_by_signature Ntk2b1jqUTFW6SKns3uL1PSDvmyux5Fr3
Total in: 8722
Total out: 8555
Fee: 167
Send this transaction? (Y/n)
Y
Transaction sent (id is a38b7268cdfaccc59dd22a1020482aac37c51453)
Please check whether they work or not.
-
I don't know whether I can or how to import my multibit wallet or pts wallet. Could anyone send me some?
my address:
An2Siuwq3LhiebtxjAoaMER4JSrFMoRDb
Just a few is OK. Thanks.
Sent.
Received 1111. Thank you :)
-
problem importing pts wallet..
> import_bitcoin_wallet ~/.bitshares-pts/wallet.dat xxx
spending passphrase:
std
{}
th_a import_bitcoin_wallet.cpp:339 import_bitcoin_wallet
Unable to import bitcoin wallet ~/.bitshares-pts/wallet.dat
{"wallet_dat":"~/.bitshares-pts/wallet.dat"}
th_a wallet.cpp:555 import_bitcoin_wallet
-
What about bitsharestalk.org from being a keyhotee founder?
-
problem importing pts wallet..
> import_bitcoin_wallet ~/.bitshares-pts/wallet.dat xxx
spending passphrase:
std
{}
th_a import_bitcoin_wallet.cpp:339 import_bitcoin_wallet
Unable to import bitcoin wallet ~/.bitshares-pts/wallet.dat
{"wallet_dat":"~/.bitshares-pts/wallet.dat"}
th_a wallet.cpp:555 import_bitcoin_wallet
Try to input the absolute path...
-
problem importing pts wallet..
> import_bitcoin_wallet ~/.bitshares-pts/wallet.dat xxx
spending passphrase:
std
{}
th_a import_bitcoin_wallet.cpp:339 import_bitcoin_wallet
Unable to import bitcoin wallet ~/.bitshares-pts/wallet.dat
{"wallet_dat":"~/.bitshares-pts/wallet.dat"}
th_a wallet.cpp:555 import_bitcoin_wallet
Try to input the absolute path...
tried with absolute path.
unspecified
error durring aes 256 cbc decrypt final
{"s":"error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt"}
th_a aes.cpp:244 aes_decrypt
unable to decrypt key
{}
th_a import_bitcoin_wallet.cpp:176 decrypt
{}
th_a import_bitcoin_wallet.cpp:339 import_bitcoin_wallet
Unable to import bitcoin wallet /home/slava/.bitshares-pts/wallet.dat
{"wallet_dat":"/home/slava/.bitshares-pts/wallet.dat"}
th_a wallet.cpp:555 import_bitcoin_wallet
-
problem importing pts wallet..
> import_bitcoin_wallet ~/.bitshares-pts/wallet.dat xxx
spending passphrase:
std
{}
th_a import_bitcoin_wallet.cpp:339 import_bitcoin_wallet
Unable to import bitcoin wallet ~/.bitshares-pts/wallet.dat
{"wallet_dat":"~/.bitshares-pts/wallet.dat"}
th_a wallet.cpp:555 import_bitcoin_wallet
import_bitcoin_wallet , this command is for bitcoin wallet import, not pts wallet, you could try to import the PTS address private key directly with command import_private_key
-
I experienced below situation but don't know if it's a bug.
I made my last transaction three hours ago and left the wallet untouched. I tried to make another transaction just now but failed to do it. Re-scanned and tried again, still failed. The 'getinfo' command shown me that all the blocks had been downloaded. Then closed wallet, opened wallet, tried again, worked.
-
Bitcoin wallet import works for pts wallets.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I experienced below situation but don't know if it's a bug.
I made my last transaction three hours ago and left the wallet untouched. I tried to make another transaction just now but failed to do it. Re-scanned and tried again, still failed. The 'getinfo' command shown me that all the blocks had been downloaded. Then closed wallet, opened wallet, tried again, worked.
What was the failure?
I may have seen this.
It appears that the client can stall out from time to time and stop fetching blocks. This may be the primary cause.
-
I experienced below situation but don't know if it's a bug.
I made my last transaction three hours ago and left the wallet untouched. I tried to make another transaction just now but failed to do it. Re-scanned and tried again, still failed. The 'getinfo' command shown me that all the blocks had been downloaded. Then closed wallet, opened wallet, tried again, worked.
What was the failure?
I may have seen this.
It appears that the client can stall out from time to time and stop fetching blocks. This may be the primary cause.
FYI. The transaction history.
"de5292bbc497f13dacbc3dd11c626dc962d24de7",{
"trx": {
"version": 0,
"stake": 349173969,
"vote": 68,
"valid_until": "19700101T000000",
"inputs": [{
"output_ref": {
"trx_hash": "a38b7268cdfaccc59dd22a1020482aac37c51453",
"output_idx": 1
},
"input_data": ""
}
],
"outputs": [{
"amount": {
"amount": 1234,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "N94JT5RdUJJbUL8UzoUquTe9vTGA4W6ds"
}
},{
"amount": {
"amount": 3821,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "BEQa8SSgjNJ8S9HHnzwmhoquZWF87asTg"
}
}
],
"sigs": [
"1fcba25cce2b99b1a3333a6f904fe97a71b1b3c65c8b8790ecfa66582de3a344f1ee050d76b235be78ea73953ac40c447953faf055ff76ec79eda2bd3128aba1be"
]
},
"memo": "",
"block_num": 4294967295,
"to": [],
"from": [],
"delta_balance": [],
"valid": false,
"fees": []
}
],[
"814b62f89f5f612ce7eefd9ed32b9aecd9ebf60a",{
"trx": {
"version": 0,
"stake": 349173969,
"vote": 68,
"valid_until": "19700101T000000",
"inputs": [{
"output_ref": {
"trx_hash": "a38b7268cdfaccc59dd22a1020482aac37c51453",
"output_idx": 1
},
"input_data": ""
}
],
"outputs": [{
"amount": {
"amount": 1234,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "N94JT5RdUJJbUL8UzoUquTe9vTGA4W6ds"
}
},{
"amount": {
"amount": 3821,
"unit": 0
},
"claim_func": 2,
"claim_data": {
"owner": "LHYVFVMQPbx2Dvvv44UmJnAGVSFenTkAf"
}
}
],
"sigs": [
"203316cd1e79411ee786b23b216dcdffa79ca71334996822e4b17c21aeecddebf9f7c08dfd6d7c14f1497d2308a3f1a22fd81d54559ac64d5c4a99d78d8ec16f30"
]
},
"memo": "",
"block_num": 4294967295,
"to": [],
"from": [],
"delta_balance": [],
"valid": false,
"fees": []
}
BTW, this is the network with single trustee. Why not test with the 100 delegates mode? Is it because the coding still not finished or too complicated to do it with command line ?
-
I just updated the get_transaction_history console output to be more useful... TODO: sort it by block.trx
# BLK DATE FROM | TO AMOUNT
------------------------------------------------------------------------------------------
0 0.293 20140502T191333 genesis | 1639344262294 | id: afccc58ef106631c710b961b32f2576f14d2e6f7
1 0.267 20140502T191333 genesis | 305512261904 | id: 89242aade0d342077194150a2dd733fed9d9245b
2 0.255 20140502T191333 genesis | 109499407940 | id: a3ebf7b17cf2f845e266351663f87c95d865f268
3 0.263 20140502T191333 genesis | 128774738658 | id: 5dc2a12a783c197bbdc32534bee0e891e7304164
4 0.249 20140502T191333 genesis | 622260421073 | id: d78d173e83d81b680d289275374236c111eefde6
5 0.248 20140502T191333 genesis | 106776657727 | id: 6b80d51f468605648f8d44e739e1d260b1b29bf6
6 0.251 20140502T191333 genesis | 432829920502 | id: 586b10bcf20ae8007b519dfa2583d415d27ce0d4
7 -1.1 19700101T000000 | 0 | id: 9cb253a99ec103bdb06c708e795c0e3b56cb982d
8 0.265 20140502T191333 genesis | 101209831755 | id: 94730d6833aa91d9eccfddef98951a3df8f1f429
9 0.110 20140502T191333 genesis | 1284167 | id: 34bbbdc5b07a814b407975274c4eacb98e607c61
10 0.205 20140502T191333 genesis | 85721321479 | id: b389027a9a310c94fbce9b47be9c5f0368f29dc7
11 0.157 20140502T191333 genesis | 154768621 | id: a8d4fafd529def320ccb07e438a894f0928461af
12 0.247 20140502T191333 genesis | 349577854561 | id: e850d5962bc74878367c639487fc0ce58cefcec7
13 0.257 20140502T191333 genesis | 254582576372 | id: cdd0c6d9daf0f99078f6ac257eedd31a36044042
14 2461.0 20140503T155730 | EWJBpZvLQiGWmUqnVFKuTfhc4fQ7adfaH -300167 | id: 341a25a7779e656e9f27f5101be289e7c5c9d69e
15 0.253 20140502T191333 genesis | 344432654350 | id: 9dd1a33843a2148be557d66bf74e48c92b5c8039
16 0.246 20140502T191333 genesis | 274335547048 | id: 951624662df7f8a59a7af34a431860dd4136f074
17 0.245 20140502T191333 genesis | 117410588060 | id: d134f0384ca873635a5599dd443a025ec64d9ca2
18 0.254 20140502T191333 genesis | 179705583678 | id: f38342bdf1f51c0aed70c622e45823fdfc0ddf64
19 0.242 20140502T191333 genesis | 164520222296 | id: b3d456a579f92f984c4d0e166b1218ad0edd304d
20 0.117 20140502T191333 genesis | 491746733 | id: 8b21e01bef920d1e4b3450ea755862f286381ae2
21 0.250 20140502T191333 genesis | 263230468840 | id: 72f82b1be3986a2a505fd7efb81bb19e9627d9b0
22 0.181 20140502T191333 genesis | 460088375 | id: 058ce6d37d56da03d33b588e8c3fc27cfbf3c001
23 0.164 20140502T191333 genesis | 22269664 | id: c7dff9c920f8bdc211cdbcaa10808b7b2218a15a
24 26.0 20140502T194000 ArU5RfEEHypBzs8FaAZ4arfvc8TfZFSgX | -167 | id: 14bd6552eef12700e5316b6cad5f4dcd0f3b4170
25 0.261 20140502T191333 genesis | 254246502897 | id: f23a4dac4f97e417c1607ebd4c47dc6db8d3fa59
26 0.243 20140502T191333 genesis | 627396809204 | id: e453c153476dddd51b21ff1c0784cb04bf39f8ed
27 0.158 20140502T191333 genesis | 122459030 | id: 7cf697a1145442eb0e497c29725719a6af6f241b
28 0.260 20140502T191333 genesis | 356141110985 | id: 67d83bfaea765addbab23f21085045c8a687e3c8
29 0.106 20140502T191333 genesis | 678238484237 | id: 67feccb3297d598a39c4a047d525a70c6bbddf50
-
transaction history is now sorted for easier understanding.
-
@bytemaster
i created new wallet, stopped client with quit and started it again
$ ./bts_xt_client --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.182:8765
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
================================================================
$
Now it doesnt even start. its latest build of git master
-
Can you send me log at .bitshares/log.txt via email?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
-
Can you send me log at .bitshares/log.txt via email?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Check pm.
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
Sent
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
Sent
9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs
me too :)
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
Sent
9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs
me too :)
Sent
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
Sent
9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs
me too :)
Sent
Oddly I still see my original balance... trying again
-
shares pls
8iP4ZbwtSjBy4aZk3uQX8fc4YsbFsXti1
Sent
9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs
me too :)
Sent
Oddly I still see my original balance... trying again
anyway i couldnt create a wallet ...dont know why
-
I think the network stopped producing blocks
-
I will look into it
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Ok... I am tracking down some issues that came up during the test.
The trustee client crashed and unfortunately didn't leave me a log file... I believe the trustee crashed because of a double spend attempt because the console output was showing:
ref_outs.insert( in.output_ref ).second: duplicate input detected
{}
th_a chain_database.cpp:532 validate_unique_inputs
error validating block
{}
th_a chain_database.cpp:605 validate
unable to push block
{"b":{"version":0,"block_num":5062,"prev":"c3a6817ff18b221a3f0ced1987aa4fd882c6b410","timestamp":"20140504T232030","next_fee":1000,"next_reward":200,"total_shares":395999996945235,"trx_mroot":"27b930b49ee4335465d97c133c3f6379a2d40594","trustee_signature":"20352b5dc9459935d8a4255ae045e8555cd1c055a3443824b2dc75e08cef870c6861ce59ccd6873fe1485a8c0575ace9b96046d3528285a8fc54149f221dc6c3ed","trxs":[{"version":0,"stake":2139203267,"vote":68,"valid_until":"19700101T000000","inputs":[{"output_ref":{"trx_hash":"97a20c118182918a5eee1f757a3eda3e4abaa265","output_idx":0},"input_data":""}],"outputs":[{"amount":{"amount":50000,"unit":0},"claim_func":2,"claim_data":{"owner":"9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs"}},{"amount":{"amount":449833,"unit":0},"claim_func":2,"claim_data":{"owner":"CLockCY7he5zPY63Kdy7j1LVQpxfSVcs5"}}],"sigs":["1f1eeed94057a6974212a65c4b964e6b0841da39ee6140f2eb08e7acfd5b76f7e80081bd3f40bdb98a18659c79438092c21bc6e010419302db3cc5fafde2c2dced"]},{"version":0,"stake":2139203267,"vote":68,"valid_until":"19700101T000000","inputs":[{"output_ref":{"trx_hash":"97a20c118182918a5eee1f757a3eda3e4abaa265","output_idx":0},"input_data":""}],"outputs":[{"amount":{"amount":25000,"unit":0},"claim_func":2,"claim_data":{"owner":"9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs"}},{"amount":{"amount":474833,"unit":0},"claim_func":2,"claim_data":{"owner":"MqDmbm2crF6E7oDBYH3Qc3Py5qVKqGksk"}}],"sigs":["2023434635f795511c46a44f5e43aa4dd3852c1f8d151084692da5de004aeaea1f67437436f8aa8f9092451226a945c4b3169f10de4a9e28c426dcb377171c9ed2"]},{"version":0,"stake":2139203267,"vote":68,"valid_until":"19700101T000000","inputs":[{"output_ref":{"trx_hash":"97a20c118182918a5eee1f757a3eda3e4abaa265","output_idx":0},"input_data":""}],"outputs":[{"amount":{"amount":10000,"unit":0},"claim_func":2,"claim_data":{"owner":"9kRiJhCRhokS8SeKxFcfvgBTZW6fVGvvs"}},{"amount":{"amount":489833,"unit":0},"claim_func":2,"claim_data":{"owner":"7cDCPx1BC7F6hd7w2t7Q69WPNNAxK13UN"}}],"sigs":["1f66226c9d21a96df41934d74243034738e35ed4bf9fed1429866c76084bc7259a589d555ce5cab60af524d582af9aeb4357be0c516a39992d00442f7f8fb72a38"]}]}}
th_a chain_database.cpp:615 push_block
Apparently some wallet files are unable to open and generate an error
I have a list of things that we will look into and then relaunch the test.
Thanks for your help.
-
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.
Same problem with your recent changes
creating default config file /home/alexxy/.bitsharesxt/config.json
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
{"type":5}
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
>>>
@bytemaster
i created new wallet, stopped client with quit and started it again
$ ./bts_xt_client --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.182:8765
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
================================================================
$
Now it doesnt even start. its latest build of git master
I was having these problems as well. Just pushed a fix it may work for you now. I guess you would have to manually test (http://bitshares.org/documentation/group__manual__testing.html) if the server has been taken down.
-
Import private key does not work with btc or pts keys
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Why not?
https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/rpc/rpc_server.cpp#L1147
Looks like the wallet has the private key so it should know that it can spend the output in the genesis block when it rescans. We shouldn't have to do a separate "sweep" transaction for the balance to show.
WIF private keys (like from doing 'dumpprivkey' from the PTS console) can now be imported using 'importprivkey'.
-
Seems like bts_xt started working for me. Can someone send some to Pvt7L5BDpTgaNaTt4cKHCAApeWZqQ33T9
PS does pts and keyhotee id import working? If so how?
-
Seems like bts_xt started working for me. Can someone send some to Pvt7L5BDpTgaNaTt4cKHCAApeWZqQ33T9
PS does pts and keyhotee id import working? If so how?
Just now, when I am trying to send some bts to this address, I failed.
Then when I try to look up the transaction history, the program crashed (Windows).
I reopened the client and tried again, still crashes.
bytemaster, do you need my log file about this or are you already looking into this issue?
-
Latest git master doesnt builds
https://github.com/BitShares/bitshares_toolkit/issues/55
-
Latest git master doesnt builds
https://github.com/BitShares/bitshares_toolkit/issues/55
Heh, now it builds but old bug returns
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
-
Recreated wallet works. Can someone send something to AaJRoHN43fcT4pqVWPRFnpTGXBPc5Sahg
BTW how to import pts wallet?
-
Recreated wallet works. Can someone send something to AaJRoHN43fcT4pqVWPRFnpTGXBPc5Sahg
BTW how to import pts wallet?
import_bitcoin_wallet works for btc and pts wallet.
import_bitcoin_wallet("d:/pts.wallet", "password")
-
I cannot get beyond block 5061!?
-
Server is down while we fix a few things.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Server is down while we fix a few things.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Hope we can test with the 100 delegates mode rather than single trustee.
-
The web wallet has not been updated for 7 days.
Anyone knows where I can get the newest status of this part?
-
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.
-
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?
-
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
-
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.
-
Deterministic wallet?
-
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....
-
Having problems sending..
>>> 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
-
Having problems sending..
>>> 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.
-
Having problems sending..
>>> 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
-
Heh, now it builds but old bug returns
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.
//std::unordered_map<address,std::string> receive_addresses;
std::unordered_set<receive_address> receive_addresses;
-
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?!
-
how about the progress?
-
how about the progress?
+5%
-
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 ?
-
Not at my side
-
This test was very helpful and we learned some critical details:
1) We learned our wallet data storage (flat-file JSON) is subject to corruption and catastrophic failure despite efforts to write a backup, move it into place, etc. It also didn't scale well. So I have created a new wallet that uses a database for managing the data.
2) Internal testing revealed some network-layer issues that we have been fixing and are now mostly fixed.
3) We are doing some studies now on network propagation delay to make sure that 30 second block intervals are safe.
4) We have identified a challenge in paying delegates... micro-payments from the transaction fees are 'unspendable' by normal means because the fees are higher than the output amount.
5) While working to solve these issues in the background I was also thinking about how we were going to handle fees paid in BitUSD, etc.
6) The trustee client crashed and was a single point of failure. We are working on approaches to help our trustee (and delegates) rapidly recover from failure to keep the network running without delay or manual intervention.
Overall I am pleased to say that we have an updated framework in place that should be able to handle all of our chain forks and actually enable full up DPOS with delegate signing rather than relying on a trustee. When integrated with the crash recovery code should provide a much better experience.
-
This test was very helpful and we learned some critical details:
1) We learned our wallet data storage (flat-file JSON) is subject to corruption and catastrophic failure despite efforts to write a backup, move it into place, etc. It also didn't scale well. So I have created a new wallet that uses a database for managing the data.
2) Internal testing revealed some network-layer issues that we have been fixing and are now mostly fixed.
3) We are doing some studies now on network propagation delay to make sure that 30 second block intervals are safe.
4) We have identified a challenge in paying delegates... micro-payments from the transaction fees are 'unspendable' by normal means because the fees are higher than the output amount.
5) While working to solve these issues in the background I was also thinking about how we were going to handle fees paid in BitUSD, etc.
6) The trustee client crashed and was a single point of failure. We are working on approaches to help our trustee (and delegates) rapidly recover from failure to keep the network running without delay or manual intervention.
Overall I am pleased to say that we have an updated framework in place that should be able to handle all of our chain forks and actually enable full up DPOS with delegate signing rather than relying on a trustee. When integrated with the crash recovery code should provide a much better experience.
+5% +5%
-
Change the bts total share to 80 trillion for what?
-
4) We have identified a challenge in paying delegates... micro-payments from the transaction fees are 'unspendable' by normal means because the fees are higher than the output amount.
Why not a fee market between delegate and users?
-
Change the bts total share to 80 trillion for what?
The exact value of the constant isn't particularly important, as your assets are best measured in bips. The share supply just needs to be scaled so that it is sufficiently divisible, but not overly divisible that it requires excessive storage. Bitcoin has 2.1 quadrillion shares; we are currently using 80 trillion.
-
:'(
the bts wallet downloaded from“http://bitshares.org/downloads/” Windows: May 9, 0:21:21 bts_wallet.tar.gz
seems like it's different with what you compiled &tested？
the command such as getinfo is not existed
D:\bts>bts.exe data
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
================================================================
listening for rpc connections on 127.0.0.1:1666
connecting to bitshares network: 107.170.30.182:8765
connected to bitshares network
help
Commands:
quit
login - enter your password to load your wallet file
unlock - enter your password to unlock your private keys
lock - lock your private keys
importkey PRIV_KEY [label] [rescan]
importwalletkey PRIV_KEY [label] [rescan]
import_bitcoin_wallet WALLET_DAT - load a bitcoin-qt or PTS wallet.
balance - print the wallet balances
newaddr [label] - print a new wallet address
listaddr - print the wallet address(es)
transfer AMOUNT UNIT to ADDRESS
buy AMOUNT UNIT
sell AMOUNT UNIT
short AMOUNT UNIT
cover AMOUNT UNIT
add margin AMOUNT bts to UNIT
cancel ID IDX
html FILE
json FILE
market QUOTE BASE
show orders QUOTE BASE
-
where is the sources for new wallet? ;)
-
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.
Now automatically saves after every command that would require the wallet to be unlocked: https://github.com/BitShares/bitshares_toolkit/commit/1300929e64bed39f24e4f137bc2171dda9af2758
We may want to save on other big operations as well, e.g. rescan.
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
-
Holy moly ... wohooo
-
New test network with full DPOS + P2P connections will be out next week.
good news!
-
New test network with full DPOS + P2P connections will be out next week.
It seems that the web gui is still not ready. How can we vote without gui？Command line？
-
I am fine with command line
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
happy to hear this news and hope it is a sucess one
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
we are excited !!!
Sent from my ALCATEL ONE TOUCH 997D using Tapatalk
-
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.
Now automatically saves after every command that would require the wallet to be unlocked: https://github.com/BitShares/bitshares_toolkit/commit/1300929e64bed39f24e4f137bc2171dda9af2758
We may want to save on other big operations as well, e.g. rescan.
Seems Dan was working on the Berkeley DB based wallet which will be more scalable, it should not require to save the entire wallet after the RPC command which changes the wallet data,and it may also solve the old version wallet can not open issue.
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
if Nightly Builds from http://bitshares.org/downloads/ can be used for test? with GUI?
-
Keep up the great work, y'all. Looking forward to it.
-
I downloaded the nightly build and try to open the wallet but it says that I'm missing MSVCP120.dll. Where can I get it?
-
I downloaded the nightly build and try to open the wallet but it says that I'm missing MSVCP120.dll. Where can I get it?
install visual2003 tools
-
how to run . wrong msg is down.
D:\bitshares\bts_wallet>bts_wallet --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrd
r9pXXKk --connect-to 107.170.30.182:8765 --data-dir D:\bitshares\bts_wallet
================================================================
= =
= Welcome to BitShares XT =
= =
= This software is in alpha testing and is not suitable for =
= real monetary transactions or trading. Use at your own =
= risk. =
= =
= Type 'help' for usage information. =
================================================================
Usage: bts_wallet [DATADIR]
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
When???
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
When???
This evening,
-
Does test network still works?
Btw with latest changes i cannot import pts wallet anymore (its encrypted with pass)
New test network with full DPOS + P2P connections will be out next week.
When???
This evening,
Really? 8)
-
This evening,
Really? 8)
I wouldn't believe a newbie with 2 posts in this board.
It's done when its done. They might release the P2P tesnet wallet this week.
-
This evening,
Really? 8)
I wouldn't believe a newbie with 2 posts in this board.
It's done when its done. They might release the P2P tesnet wallet this week.
+5%
for a second thought it may have been a BM alias lol
-
This evening,
Really? 8)
I wouldn't believe a newbie with 2 posts in this board.
It's done when its done. They might release the P2P tesnet wallet this week.
+5%
for a second thought it may have been a BM alias lol
I don't think Dan speaks Chinese.
-
I hope the wallet will be ready for download soon
-
This evening,
Really? 8)
I wouldn't believe a newbie with 2 posts in this board.
It's done when its done. They might release the P2P tesnet wallet this week.
+5%
for a second thought it may have been a BM alias lol
I don't think Dan speaks Chinese.
he could of used google translate
-
Is to use the Google translator, I am more optimistic, you can ignore what I said!
-
New test network with full DPOS + P2P connections will be out next week.
now Wednesday……
-
New test network with full DPOS + P2P connections will be out next week.
now Wednesday……
Are you afraid that the Invictus team have lost access to calenders or what?
Or do you have another metric for measuring weeks, that start and end on wednesdays?
We're only halfway the "next" week and he did not write in "a" or "this" week, so your post is a week early.
-
Are you afraid that the Invictus team have lost access to calenders or what?
Or do you have another metric for measuring weeks, that start and end on wednesdays?
We're only halfway the "next" week and he did not write in "a" or "this" week, so your post is a week early.
Reading this made me LOL
-
come on guys -- this post is just for testing purposes of BitShares XT launch.
I know ... all of us can't wait to see it launched ... but pls if you test BitSharesXT client ... you're welcome to post here...
otherwise .. pls calm down & and show a little bit more be patience ... delays etc. were discussed on many other posts...
i can understand your feelings about ... I can hardly expect launch also ... but we need to assist here not to complain...
Last said ... Good things come to those who wait.
Happy coding…
my 2 BTSXT
cass
-
come on guys -- this post is just for testing purposes of BitShares XT launch.
I know ... all of us can't wait to see it launched ... but pls if you test BitSharesXT client ... you're welcome to post here...
otherwise .. pls calm down & and show a little bit more be patience ... delays etc. were discussed on many other posts...
i can understand your feelings about ... I can hardly expect launch also ... but we need to assist here not to complain...
Last said ... Good things come to those who wait.
Happy coding…
my 2 BTSXT
cass
Yes, since we have gone such far , let us keep going as usual .
We should go in a hurry but not in a rush.
-
I downloaded the nightly build and try to open the wallet but it says that I'm missing MSVCP120.dll. Where can I get it?
Visual C++ Redistributable Packages for Visual Studio 2013
http://www.microsoft.com/en-us/download/details.aspx?id=40784
-
I have working DPOS chain with instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
This is working with full P2P mode, DPOS delegates producing blocks, and the new level_db based wallet....
I will be refining this a tad further and keep you all posted on when we can resume the test.
-
I have working DPOS chain with instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
This is working with full P2P mode, DPOS delegates producing blocks, and the new level_db based wallet....
I will be refining this a tad further and keep you all posted on when we can resume the test.
+5%
-
I have working DPOS chain with instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
This is working with full P2P mode, DPOS delegates producing blocks, and the new level_db based wallet....
I will be refining this a tad further and keep you all posted on when we can resume the test.
+5%
Plan to test it this weekend
-
I have working DPOS chain with instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
This is working with full P2P mode, DPOS delegates producing blocks, and the new level_db based wallet....
I will be refining this a tad further and keep you all posted on when we can resume the test.
+5%
Plan to test it this weekend
I have updated the testing instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
Primary changes are in the API usage and wallet management. The primary goal is to get people away from sending to an 'address' and instead sending to an 'account' where the account is a hierarchal key. Every time you send to an account it will use a different public key (address) and eventually this will allow automation of privacy enhancing transactions.
We have also extended the API / implemented more of it. See info here:
blockchain_get_block <block_hash> Retrieves the block header for the given block hash
blockchain_get_block_by_number <block_number> Retrieves the block header for the given block number
blockchain_get_blockcount Returns the number of blocks in the longest block chain.
blockchain_get_blockhash <block_num> Returns hash of block in best-block-chain at index provided..
blockchain_get_delegates [first] [count] Returns the list of delegates sorted by vote
blockchain_get_name_record <name> Retrieves the name record
blockchain_get_names [first] [count] Returns the list of reserved names sorted alphabetically
blockchain_get_transaction <transaction_id> Get detailed information about an in-wallet transaction
get_info Provides common data, such as balance, block count, connections, and lock time
help [command] Lists commands or detailed help for specified command.
network_add_node <node> <command> Attempts add or remove <node> from the peer list or try a connection to <node> once
network_get_connection_count Returns the number of connections to other nodes.
network_get_peer_info Returns data about each connected node.
stop Stop BitShares server
validate_address <address> Return information about given BitShares address.
wallet_close Closes the curent wallet if one is open.
wallet_create <wallet_name> <password> Opens the wallet of the given name
wallet_create_receive_account <account_name> Add new account for receiving payments
wallet_create_sending_account <account_name> <account_key> Add new account for sending payments
wallet_get_account <account_name> Lists all foreign addresses and their labels associated with this wallet
wallet_get_balance [account_name] [minconf] [asset] Returns the wallet's current balance
wallet_get_name Returns the wallet name passed to wallet_open
wallet_get_transaction_history [count] Retrieves all transactions into or out of this wallet.
wallet_import_bitcoin <filename> <password> Import a BTC/PTS wallet
wallet_import_private_key <key> [account_name] [wallet_rescan_blockchain] Import a BTC/PTS private key in wallet import format (WIF)
wallet_list_receive_accounts [start] [count] Lists all foreign addresses and their labels associated with this wallet
wallet_list_reserved_names [account_name] Lists all reserved names controlled by this wallet, filtered by account.
wallet_list_sending_accounts [start] [count] Lists all foreign addresses and their labels associated with this wallet
wallet_lock Lock the private keys in wallet, disables spending commands until unlocked
wallet_open <wallet_name> <password> Opens the wallet of the given name
wallet_open_file <wallet_file> <password> Opens the wallet at the given path.
wallet_register_delegate <name> <data> Registeres a delegate to be voted upon by shareholders.
wallet_rename_account <current_account_name> <new_account_name> Lists all reserved names controlled by this wallet, filtered by account.
wallet_rescan_blockchain [starting_block] Rescan the block chain from the given block
wallet_rescan_blockchain_state Rescans the genesis block and state (not the transactions)
wallet_reserve_name <name> <data> Retrieves the name record
wallet_transfer <amount> <sending_account_name> [invoice_memo] [from_account] [asset_id] Sends given amount to the given address, assumes shares in DAC
wallet_unlock <spending_pass> <timeout> Unlock the private keys in the wallet to enable spending operations
If you are curious about the new transaction structure you can view an example json dump here:
{
"expiration": null,
"delegate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTSKh6JP6QzMmeUmmK1T16gxgadrJ547ocGT",
"amount": 154321,
"claim_input_data": ""
}
},{
"type": "deposit_op_type",
"data": {
"amount": 54321,
"condition": {
"asset_id": 0,
"delegate_id": 8,
"condition": "withdraw_signature_type",
"data": {
"owner": "XTSAg5YxD9reTXr5iQWBZEJrLzzMxMxvnFhy"
}
}
}
}
],
"signatures": [
"2028da68efe2696ab7895e86c1b35affbb7cd1b71d8f33124fe81ad785ace3ed55226e0e622098b9c45f8660801b4b929556102c3da549d887c5da99262b5c6275"
]
}
As you can see this transaction is entirely human readable outside the context of the blockchain, it is transferring 154321 from XTSKh6JP6QzMmeUmmK1T16gxgadrJ547ocGT and sending 54321 to XTSAg5YxD9reTXr5iQWBZEJrLzzMxMxvnFhy while paying a fee of 100000.
-
I have working DPOS chain with instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
This is working with full P2P mode, DPOS delegates producing blocks, and the new level_db based wallet....
I will be refining this a tad further and keep you all posted on when we can resume the test.
+5%
Plan to test it this weekend
I have updated the testing instructions here: http://bitshares.org/documentation/group__dpos__manual__testing.html
Primary changes are in the API usage and wallet management. The primary goal is to get people away from sending to an 'address' and instead sending to an 'account' where the account is a hierarchal key. Every time you send to an account it will use a different public key (address) and eventually this will allow automation of privacy enhancing transactions.
We have also extended the API / implemented more of it. See info here:
blockchain_get_block <block_hash> Retrieves the block header for the given block hash
blockchain_get_block_by_number <block_number> Retrieves the block header for the given block number
blockchain_get_blockcount Returns the number of blocks in the longest block chain.
blockchain_get_blockhash <block_num> Returns hash of block in best-block-chain at index provided..
blockchain_get_delegates [first] [count] Returns the list of delegates sorted by vote
blockchain_get_name_record <name> Retrieves the name record
blockchain_get_names [first] [count] Returns the list of reserved names sorted alphabetically
blockchain_get_transaction <transaction_id> Get detailed information about an in-wallet transaction
get_info Provides common data, such as balance, block count, connections, and lock time
help [command] Lists commands or detailed help for specified command.
network_add_node <node> <command> Attempts add or remove <node> from the peer list or try a connection to <node> once
network_get_connection_count Returns the number of connections to other nodes.
network_get_peer_info Returns data about each connected node.
stop Stop BitShares server
validate_address <address> Return information about given BitShares address.
wallet_close Closes the curent wallet if one is open.
wallet_create <wallet_name> <password> Opens the wallet of the given name
wallet_create_receive_account <account_name> Add new account for receiving payments
wallet_create_sending_account <account_name> <account_key> Add new account for sending payments
wallet_get_account <account_name> Lists all foreign addresses and their labels associated with this wallet
wallet_get_balance [account_name] [minconf] [asset] Returns the wallet's current balance
wallet_get_name Returns the wallet name passed to wallet_open
wallet_get_transaction_history [count] Retrieves all transactions into or out of this wallet.
wallet_import_bitcoin <filename> <password> Import a BTC/PTS wallet
wallet_import_private_key <key> [account_name] [wallet_rescan_blockchain] Import a BTC/PTS private key in wallet import format (WIF)
wallet_list_receive_accounts [start] [count] Lists all foreign addresses and their labels associated with this wallet
wallet_list_reserved_names [account_name] Lists all reserved names controlled by this wallet, filtered by account.
wallet_list_sending_accounts [start] [count] Lists all foreign addresses and their labels associated with this wallet
wallet_lock Lock the private keys in wallet, disables spending commands until unlocked
wallet_open <wallet_name> <password> Opens the wallet of the given name
wallet_open_file <wallet_file> <password> Opens the wallet at the given path.
wallet_register_delegate <name> <data> Registeres a delegate to be voted upon by shareholders.
wallet_rename_account <current_account_name> <new_account_name> Lists all reserved names controlled by this wallet, filtered by account.
wallet_rescan_blockchain [starting_block] Rescan the block chain from the given block
wallet_rescan_blockchain_state Rescans the genesis block and state (not the transactions)
wallet_reserve_name <name> <data> Retrieves the name record
wallet_transfer <amount> <sending_account_name> [invoice_memo] [from_account] [asset_id] Sends given amount to the given address, assumes shares in DAC
wallet_unlock <spending_pass> <timeout> Unlock the private keys in the wallet to enable spending operations
If you are curious about the new transaction structure you can view an example json dump here:
{
"expiration": null,
"delegate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "XTSKh6JP6QzMmeUmmK1T16gxgadrJ547ocGT",
"amount": 154321,
"claim_input_data": ""
}
},{
"type": "deposit_op_type",
"data": {
"amount": 54321,
"condition": {
"asset_id": 0,
"delegate_id": 8,
"condition": "withdraw_signature_type",
"data": {
"owner": "XTSAg5YxD9reTXr5iQWBZEJrLzzMxMxvnFhy"
}
}
}
}
],
"signatures": [
"2028da68efe2696ab7895e86c1b35affbb7cd1b71d8f33124fe81ad785ace3ed55226e0e622098b9c45f8660801b4b929556102c3da549d887c5da99262b5c6275"
]
}
As you can see this transaction is entirely human readable outside the context of the blockchain, it is transferring 154321 from XTSKh6JP6QzMmeUmmK1T16gxgadrJ547ocGT and sending 54321 to XTSAg5YxD9reTXr5iQWBZEJrLzzMxMxvnFhy while paying a fee of 100000.
send 154321 with 100000 fee? isn't the transfer fee too high?
-
That was a dust transaction and the wallet was set to use the same fee as bitcoin. Much higher than the min required which was just 150.
-
send 154321 with 100000 fee? isn't the transfer fee too high?
I think the unit here is satoshi as the amount is of int64_t type. So 100000 is 0.01 but it's still higher than BTC as it's currently about 0.0001. If we consider the price of BTS compared with BTC, 0.01 is fine for the moment.
-
New public test launched.. https://bitsharestalk.org/index.php?topic=4714.msg60255#msg60255