Author Topic: Dry Run 2: The Real Deal  (Read 107827 times)

0 Members and 1 Guest are viewing this topic.

Xeldal

  • Guest
How to import PTS wallet?

I see the bitcoin, electrum, multibit, armory, and keyhotee import commands. 

Is there no command for PTS yet?

Offline bytemaster

+5% for that brief description .. we should add that to the techtalk about titan
+1
For the latest updates checkout my blog: http://bytemaster.bitshares.org
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.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
+5% for that brief description .. we should add that to the techtalk about titan

Offline bytemaster

More confused now. Could you please tell the diff among

1)Public key  which we used as wallet address
2)what is  account key? Is it the same as public key
3) what is balance key?

Is there any command that i can use to discover  these keys





same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?

suppose there is something wrong , how can a name map to 2 different private keys?

Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated  when someone sends you a titan transaction or you import keys into the account from an external source.

In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.

Importing the key into two places will probably confuse the wallet right now.

In an attempt to simplify concepts we have decided to NOT overload the term 'address' as used in bitcoin.

Accounts have Public Keys which we are calling your Account Key and contain automatically generated addresses from TITAN or from imported bitcoin wallets.
An address is the hash of a public key used to control a balance (spendable entry in the blockchain).

Our goal is that users never have to think much about their Account Keys and NEVER about their addresses. 

« Last Edit: June 19, 2014, 03:28:32 pm by bytemaster »
For the latest updates checkout my blog: http://bytemaster.bitshares.org
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.

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
More confused now. Could you please tell the diff among

1)Public key  which we used as wallet address
2)what is  account key? Is it the same as public key
3) what is balance key?

Is there any command that i can use to discover  these keys





same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?

suppose there is something wrong , how can a name map to 2 different private keys?

Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated  when someone sends you a titan transaction or you import keys into the account from an external source.

In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.

Importing the key into two places will probably confuse the wallet right now.
« Last Edit: June 19, 2014, 03:01:20 pm by sfinder »
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline bytemaster


same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?

suppose there is something wrong , how can a name map to 2 different private keys?

Every account has the 'account key' and under the account key are any number of 'balance keys' that are generated  when someone sends you a titan transaction or you import keys into the account from an external source.

In theory no funds should be sent directly to an 'account key', but only to a key derived from the account key.

Importing the key into two places will probably confuse the wallet right now. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
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.

Offline crazybit


same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?

suppose there is something wrong , how can a name map to 2 different private keys?

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile

same question here.... anyone knows the answer
i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline crazybit

i have registered account "crazybit" and "james", when tried to export the private key of "james" and import to the account "crazybit" , it can be done without error, is that expected? if yes, will the balance of account "james" combined to the account "crazybit"?

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
Thanks, it works.
another issue.
some  transmit  from alt to delegate-alt are pending  in both two node.
clear_pengding_transactions can clear these transmit in node alt, but not clear in node delegate-alt.
Code: [Select]
delegate (unlocked) >>> wallet_clear_pending_transactions
OK
delegate (unlocked) >>> wallet_account_transaction_history
.....
   pending   2014-06-19T10:28:45 alt                 delegate-alt        test flood...                           10.000000 DRINK        0.000000 XTS        01e5be55
   pending   2014-06-19T10:28:45 alt                 delegate-alt        test flood...                           11.000000 DRINK        0.000000 XTS        026b787c
   pending   2014-06-19T10:28:45 alt                 delegate-alt        test flood...                           10.000000 DRINK        0.000000 XTS        17a8965b
   pending   2014-06-19T10:28:45 alt                 delegate-alt        test flood...                           11.000000 DRINK        0.000000 XTS        58d8f9be
   pending   2014-06-19T10:30:15 alt                 delegate-alt        test flood...                           11.000000 DRINK        0.000000 XTS        83c3757e
   pending   2014-06-19T10:30:15 alt                 delegate-alt        test flood...                           11.000000 DRINK        0.000000 XTS        af8ba6db
   pending   2014-06-19T10:30:15 alt                 delegate-alt        test flood...                           10.000000 DRINK        0.000000 XTS        1abf5dfe

crash with wallet_clear_pending_transactions
Code: [Select]
default (unlocked) >>> wallet_clear_pending_transactions

Program received signal SIGSEGV, Segmentation fault.
0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520) at /usr/include/c++/4.8/bits/stl_construct.h:75
75          { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
(gdb) bt
#0  0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520)
    at /usr/include/c++/4.8/bits/stl_construct.h:75
#1  __uninit_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*>
    (__result=0x174f520, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:75
#2  uninitialized_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*> (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:117
#3  __uninitialized_copy_a<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*, fc::array<unsigned char, 65ul> > (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:258
#4  vector (__x=..., this=0x7ffff50fff58) at /usr/include/c++/4.8/bits/stl_vector.h:316
#5  signed_transaction (this=0x7ffff50ffeb0, this@entry=0x0) at /home/alt/workspace/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/transaction.hpp:142
#6  bts::wallet::transaction_data::transaction_data (this=this@entry=0x7ffff50ffeb0)
    at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:145
#7  0x0000000000876025 in wallet_record (this=0x7ffff50ffea8) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:109
#8  pair (this=0x7ffff50ffe90) at /usr/include/c++/4.8/bits/stl_pair.h:127
#9  bts::wallet::wallet_db::clear_pending_transactions (this=0x15d1070) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/wallet_db.cpp:332
#10 0x000000000079d2cb in bts::rpc_stubs::common_api_client::wallet_clear_pending_transactions (this=0x1546978)
    at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_client.cpp:390
#11 0x00000000006f2d55 in bts::rpc_stubs::common_api_rpc_server::wallet_clear_pending_transactions_positional (this=this@entry=0x1548290, json_connection=...,
    parameters=...) at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:1231
#12 0x000000000076a231 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method (this=0x1548290, method_name=..., parameters=...)
    at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:6681
#13 0x00000000006530b0 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method (this=this@entry=0x1548290, method_data=..., arguments_from_caller=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:393
#14 0x000000000064d413 in direct_invoke_method (arguments=..., method_name=..., this=0x1548290)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:465
#15 bts::rpc::rpc_server::direct_invoke_method (this=<optimized out>, method_name=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:677
#16 0x000000000067e7b0 in bts::cli::detail::cli_impl::execute_command (this=this@entry=0x16053e0, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:568
#17 0x0000000000680998 in bts::cli::detail::cli_impl::execute_interactive_command (this=0x16053e0, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:556
#18 0x000000000065de0d in bts::cli::cli::execute_interactive_command (this=<optimized out>, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1685
#19 0x000000000067cc5a in bts::cli::detail::cli_impl::parse_and_execute_interactive_command (this=this@entry=0x16053e0, command=..., argument_stream=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:163
#20 0x000000000067d6bb in bts::cli::detail::cli_impl::execute_command_line (this=this@entry=0x16053e0, line=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:208
#21 0x000000000065d44d in bts::cli::detail::cli_impl::process_commands (this=this@entry=0x16053e0, input_stream=<optimized out>)
---Type <return> to continue, or q <return> to quit---
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1589
#22 0x000000000065daad in start (this=0x16053e0) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:82
#23 bts::cli::cli::start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1636
#24 0x0000000000589524 in start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:308
#25 operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:1809
#26 fc::detail::void_functor_run<bts::client::client::start()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x15f1ca0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#27 0x00000000005f9a6d in fc::task_base::run_impl (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#28 0x00000000005f9e15 in fc::task_base::run (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#29 0x00000000005f83b7 in run_next_task (this=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#30 fc::thread_d::process_tasks (this=this@entry=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#31 0x00000000005f86b1 in fc::thread_d::start_process_tasks (my=22316000) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#32 0x0000000000ab5cee in make_fcontext ()
#33 0x00000000015483e0 in ?? ()
#34 0x0000000000000000 in ?? ()

This has been fixed.

Offline bytemaster

crash with wallet_clear_pending_transactions
Code: [Select]
default (unlocked) >>> wallet_clear_pending_transactions

Program received signal SIGSEGV, Segmentation fault.
0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520) at /usr/include/c++/4.8/bits/stl_construct.h:75
75          { ::new(static_cast<void*>(__p)) _T1(std::forward<_Args>(__args)...); }
(gdb) bt
#0  0x000000000084d54d in _Construct<fc::array<unsigned char, 65ul>, fc::array<unsigned char, 65ul> const&> (__p=0x174f520)
    at /usr/include/c++/4.8/bits/stl_construct.h:75
#1  __uninit_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*>
    (__result=0x174f520, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:75
#2  uninitialized_copy<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*> (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:117
#3  __uninitialized_copy_a<__gnu_cxx::__normal_iterator<fc::array<unsigned char, 65ul> const*, std::vector<fc::array<unsigned char, 65ul> > >, fc::array<unsigned char, 65ul>*, fc::array<unsigned char, 65ul> > (__result=<optimized out>, __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_uninitialized.h:258
#4  vector (__x=..., this=0x7ffff50fff58) at /usr/include/c++/4.8/bits/stl_vector.h:316
#5  signed_transaction (this=0x7ffff50ffeb0, this@entry=0x0) at /home/alt/workspace/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/transaction.hpp:142
#6  bts::wallet::transaction_data::transaction_data (this=this@entry=0x7ffff50ffeb0)
    at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:145
#7  0x0000000000876025 in wallet_record (this=0x7ffff50ffea8) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/include/bts/wallet/wallet_records.hpp:109
#8  pair (this=0x7ffff50ffe90) at /usr/include/c++/4.8/bits/stl_pair.h:127
#9  bts::wallet::wallet_db::clear_pending_transactions (this=0x15d1070) at /home/alt/workspace/bitshares_toolkit/libraries/wallet/wallet_db.cpp:332
#10 0x000000000079d2cb in bts::rpc_stubs::common_api_client::wallet_clear_pending_transactions (this=0x1546978)
    at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_client.cpp:390
#11 0x00000000006f2d55 in bts::rpc_stubs::common_api_rpc_server::wallet_clear_pending_transactions_positional (this=this@entry=0x1548290, json_connection=...,
    parameters=...) at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:1231
#12 0x000000000076a231 in bts::rpc_stubs::common_api_rpc_server::direct_invoke_positional_method (this=0x1548290, method_name=..., parameters=...)
    at /home/alt/workspace/bitshares_toolkit/build/libraries/rpc_stubs/common_api_rpc_server.cpp:6681
#13 0x00000000006530b0 in bts::rpc::detail::rpc_server_impl::dispatch_authenticated_method (this=this@entry=0x1548290, method_data=..., arguments_from_caller=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:393
#14 0x000000000064d413 in direct_invoke_method (arguments=..., method_name=..., this=0x1548290)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:465
#15 bts::rpc::rpc_server::direct_invoke_method (this=<optimized out>, method_name=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/rpc/rpc_server.cpp:677
#16 0x000000000067e7b0 in bts::cli::detail::cli_impl::execute_command (this=this@entry=0x16053e0, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:568
#17 0x0000000000680998 in bts::cli::detail::cli_impl::execute_interactive_command (this=0x16053e0, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:556
#18 0x000000000065de0d in bts::cli::cli::execute_interactive_command (this=<optimized out>, command=..., arguments=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1685
#19 0x000000000067cc5a in bts::cli::detail::cli_impl::parse_and_execute_interactive_command (this=this@entry=0x16053e0, command=..., argument_stream=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:163
#20 0x000000000067d6bb in bts::cli::detail::cli_impl::execute_command_line (this=this@entry=0x16053e0, line=...)
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:208
#21 0x000000000065d44d in bts::cli::detail::cli_impl::process_commands (this=this@entry=0x16053e0, input_stream=<optimized out>)
---Type <return> to continue, or q <return> to quit---
    at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1589
#22 0x000000000065daad in start (this=0x16053e0) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:82
#23 bts::cli::cli::start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/cli/cli.cpp:1636
#24 0x0000000000589524 in start (this=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:308
#25 operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/client/client.cpp:1809
#26 fc::detail::void_functor_run<bts::client::client::start()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x15f1ca0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#27 0x00000000005f9a6d in fc::task_base::run_impl (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#28 0x00000000005f9e15 in fc::task_base::run (this=this@entry=0x15f1cb0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#29 0x00000000005f83b7 in run_next_task (this=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#30 fc::thread_d::process_tasks (this=this@entry=0x15483e0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#31 0x00000000005f86b1 in fc::thread_d::start_process_tasks (my=22316000) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#32 0x0000000000ab5cee in make_fcontext ()
#33 0x00000000015483e0 in ?? ()
#34 0x0000000000000000 in ?? ()

This has been fixed.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
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.

Offline bytemaster

@toast: Is  rpc yet fully implemented?
When i try to create a rpc-connection to my client at normal rpc-port i get timed out. It seems, some infinite loop freezes my computer fore some minutes until client crash.

try for yourself:

Code: [Select]
curl --user 'your_username' --data-binary '{"jsonrpc":"1.0","id":"my_id","method":"wallet_open","params":["default"]}' -H 'content-type:text/plain;' http://127.0.0.1:5679
When connecting over rpc-http port and adapt the path to /rpc, all is fine, though some void returning methods as
"wallet_open, wallet_create ..." sometimes return empty responses with Content-Length: 31.
Related to further processing this seems some unevaluable. Could you change that to standard rpc response?

Works for me. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
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.

Offline denkhaus

  • Newbie
  • *
  • Posts: 18
    • View Profile
@toast: Is  rpc yet fully implemented?
When i try to create a rpc-connection to my client at normal rpc-port i get timed out. It seems, some infinite loop freezes my computer fore some minutes until client crash.

try for yourself:

Code: [Select]
curl --user 'your_username' --data-binary '{"jsonrpc":"1.0","id":"my_id","method":"wallet_open","params":["default"]}' -H 'content-type:text/plain;' http://127.0.0.1:5679
When connecting over rpc-http port and adapt the path to /rpc, all is fine, though some void returning methods as
"wallet_open, wallet_create ..." sometimes return empty responses with Content-Length: 31.
Related to further processing this seems some unevaluable. Could you change that to standard rpc response?
« Last Edit: June 19, 2014, 12:20:17 pm by denkhaus »

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
fork happen now .......
can't see all these transaction now
22398 or 22635

before I test press 2000, 22398 is there.
now, change to another chain?
237 confirms is not safe?

try 2000 failed, the pending number is 1762, maybe not broadcast out by client.
always pending there.
start from  block 22635

I have do a press test, make 200 transfers in several seconds.
seems very good, all transactions is confirmed in 1 minute.
you can see block_num 22398 && 22399
Code: [Select]
blockchain_get_block_by_number 22399

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
try 2000 failed, the pending number is 1762, maybe not broadcast out by client.
always pending there.
start from  block 22635

I have do a press test, make 200 transfers in several seconds.
seems very good, all transactions is confirmed in 1 minute.
you can see block_num 22398 && 22399
Code: [Select]
blockchain_get_block_by_number 22399