Dry Run 7: The Power of DPOS

[suwoder]

send me some XTS please, Thanks.
XTS7rhnNyCyjwBNnDtqRPkUEEC7kbycrDFdxHfD76cozHcV17KCLY

[Fox]

Please help me understand how transaction size (# of XTS within a tx) impacts the block commitment time.  I have many transactions marked as PENDING.

Code: [Select]

wallet_account_transaction_history
I have sent numerous transactions of varying the size from 10, 100, 1000 and 10000 XTS per transaction.  The 10 & 100 XTS transactions typically approve in the very next block.  The 1000 XTS transactions are hit and miss, with some going straight away and others left PENDING for a number of minutes.  The 10000 XTS transactions nearly all are left PENDING, now for hours.  Each PENDING transactions lists a FEE of 0.10000 XTS. 

I have restarted the client, clearing the peer database and resyncing the blockchain:

Code: [Select]

./bitshares_client --clear-peer-database --resync-blockchain
I have rescanned the blockchain:

Code: [Select]

wallet_rescan_blockchain
The transactions remain PENDING.  I believe they will expire in 48 hours, but am wondering how the network [should] process these transaction when posted with:

Code: [Select]

wallet_transfer <amount_to_transfer> <asset_symbol> <from_account_name> <to_account_name> [memo_message]
Thanks,
Fox

[dxtr]

How is the network going to deal with transaction flooding?
I know that when there is value put in network, then making thousands of transactions means money, but let's assume that there is a triggering event, that causes hundreds or even thousands of users to, simultaneously, create a transaction of any kind.
Now there are max 30tx/blk, but there might be a peak demand of network for 500 or 15k transactions per minute - then all those transactions are pending, effectively blocking new transactions from entering into blockchain.
On the other hand all delegates know what those pending transactions are, and how many are there.
What if delegates could control block production rate and/or block capacity in order to deal with pending transactions faster.
Something like delegate A sees that there are over 500 pending transactions, so he issues a block with indicator that block creation rate should be increased.
Now the whole network can agree or disagree - they all have necessary data to verify.
Next in queue, delegate B validates this aswell and if he agrees, he confirms A's suggestion, and delegate C will produce next block faster.
Then, if pending operation decreases to 100, delegate D can suggest decreasing rate to normal, delegate E can confirm, and delegate F can produce a block at normal rate.
There could be more than one thresholds for pending operations amount so that rate and/or capacity of a block could have many shifting gears.

I don't know if it's worth something, or am I just making a fool of myself

[HackFisher]

Not sure if I have to post here...

I have installed the GUI 0.8 version. I have created an account "zeus" and put a password.

The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.

I pressed the button "lock" and after a couple of minutes my wallet was locked. I put the password to unlock it and just waiting and waiting and waiting and never unlocked...

 


On another note... From the 5 minutes I got the chance to look at it the first thing that came to my mind was that this looks like counterparty..and I don't like counterparty..Nxt platform is much nicer...

thats a bug!
don't lock it next time...
delete folder chain
path:
C:\Users\********yourrusername*******\AppData\Roaming\BitShares XTS\chain

and run the client again

This is a known issue, they are waiting because scanning transactions in the background, we need enhancement of ui feedback of this.
I do not think you need to delete you chain dir, you can see the scanning progress if you are in cli.

https://github.com/BitShares/web_wallet/issues/91

[liondani]

Not sure if I have to post here...

I have installed the GUI 0.8 version. I have created an account "zeus" and put a password.

The account showed some numbers 3 Accounts, 2 delegates etc. when I was clicking on them nothing was showing.

I pressed the button "lock" and after a couple of minutes my wallet was locked. I put the password to unlock it and just waiting and waiting and waiting and never unlocked...

 


On another note... From the 5 minutes I got the chance to look at it the first thing that came to my mind was that this looks like counterparty..and I don't like counterparty..Nxt platform is much nicer...

thats a bug!
don't lock it next time...
delete folder chain
path:
C:\Users\********yourrusername*******\AppData\Roaming\BitShares XTS\chain

and run the client again

[cass]

send me some funds please, Thanks.
XTS6fFRG8YePxSRwMNvvpQndEc7HqmxmcqmLvTsCn8J9F3vtMg5k4

just sent

[bytemaster]

kind of bad news after one day's hardworking.....

Looks like we got some forks..

Code: [Select]

>>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         2     YES                  NO
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        18     YES                 YES
           3378
     29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb                        lexx-6             34      8862 2014-07-02T11:45:45        14     YES                 YES
     745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978           heyd-haiyaoce100lun             33      8618 2014-07-02T11:46:00         5     N/A                  NO
           4852
     0204f5c0b49fddcff6bfd2659975e3f0549ea626                         init5              0       182 2014-07-02T18:22:45         0     YES                 YES
     f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d                      longclaw              1       426 2014-07-02T18:42:30        41     N/A                  NO
           5099
     4361a302b417e72030ee4a7a54f6cbb12246ef18                         init3             35      8722 2014-07-02T19:30:30         8     YES                 YES
     279026c0485e73d51f435bd08b14c59b45cdb9a2                    oathkeeper             35      8722 2014-07-02T19:31:00         8     N/A                  NO


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
  "bitshares_toolkit_revision_age": "6 hours ago",
  "fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jul  2 2014 at 09:46:48"
}


Yes, apparently processing time on the database accesses is growing with the dataset.     Empty blocks use to take .005 seconds are now taking 1 second which turns into 1 second per hop and thus increases the potential for forks.   We know ways to accelerate this. 

[sfinder]

kind of bad news after one day's hardworking.....

Looks like we got some forks..

Code: [Select]

>>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         2     YES                  NO
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        18     YES                 YES
           3378
     29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb                        lexx-6             34      8862 2014-07-02T11:45:45        14     YES                 YES
     745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978           heyd-haiyaoce100lun             33      8618 2014-07-02T11:46:00         5     N/A                  NO
           4852
     0204f5c0b49fddcff6bfd2659975e3f0549ea626                         init5              0       182 2014-07-02T18:22:45         0     YES                 YES
     f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d                      longclaw              1       426 2014-07-02T18:42:30        41     N/A                  NO
           5099
     4361a302b417e72030ee4a7a54f6cbb12246ef18                         init3             35      8722 2014-07-02T19:30:30         8     YES                 YES
     279026c0485e73d51f435bd08b14c59b45cdb9a2                    oathkeeper             35      8722 2014-07-02T19:31:00         8     N/A                  NO


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
  "bitshares_toolkit_revision_age": "6 hours ago",
  "fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jul  2 2014 at 09:46:48"
}


[sfinder]

just wondering how you can list the assets that other than XTS. which command do you use for following list?
 

It seems I lost 100 FREE.

I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:

Init balance: 1,000,0000 FREE

Code: [Select]

3411.11   2014-07-02T11:55:15 spartako-w          spartako-w          1.000000 FREE       0.10000 XTS                                                1b8b05d1
   3432.12   2014-07-02T12:01:00 spartako-w          demonstra           100.000000 FREE     0.10000 XTS                                                68a98a80
   3447.9    2014-07-02T12:05:30 spartako-w          bitdraw             100.000000 FREE     0.10000 XTS                                                30626c46

Finale balance: 999,700.000000 FREE but should be 999,800 FREE

[bytemaster]

Our XTS balance will be reset on the next dry run right?
I'm asking this because i sent ~700K XTS by mistake (trying to vote for a delegate).

Dry runs take the last snapshot of the blockchain? or is always using the original genesis.json balance?

(don't make me cry ...  )

They always reset to genesis and are not snapshots.   XTS networks should never have any value, they are just like the BTC test network.

[ElMato]

Our XTS balance will be reset on the next dry run right?
I'm asking this because i sent ~700K XTS by mistake (trying to vote for a delegate).

Dry runs take the last snapshot of the blockchain? or is always using the original genesis.json balance?

(don't make me cry ...  )

[Kenof]

damn, still cannot import keyhotee, problem is in my brainkey because it contains characters like "!" and "@", after "!" no letters are scanned and get wrong keyhotee id scanned 

so i join to the population of beggars, please send me some funds to play with

domis-1
XTS8c3oGHR9XNSRPV9yYZspcPC2HMowrp6pyadyywpRMFeCSw94E8

thanks

So even entering you brainkey in quotes "<brainkey>" does not work?

If you are on Windows, you can try running the latest nightly build of Keyhotee from: http://bitshares.org/resources/downloads/ which has a button to copy your private key for an identity. You can then import this private key into the BitShares client using 'wallet_import_private_key <keyhotee_private_key>'. I was able to successfully claim my name from the genesis block using this method. Updated Mac and Linux Keyhotee builds coming soon.

Others please let us know if you have trouble with the brainkeys as well.

1st method unfortunately didn't work, then tried as suggested with keyhotee exporting private key, that worked like charm, thanks

@liondani
Thank you very much for funds, you have my vote 

PS.
more forks 

[emski]

Looks like we got some forks..

Code: [Select]

>>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         2     YES                  NO
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        18     YES                 YES
           3378
     29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb                        lexx-6             34      8862 2014-07-02T11:45:45        14     YES                 YES
     745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978           heyd-haiyaoce100lun             33      8618 2014-07-02T11:46:00         5     N/A                  NO
           4852
     0204f5c0b49fddcff6bfd2659975e3f0549ea626                         init5              0       182 2014-07-02T18:22:45         0     YES                 YES
     f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d                      longclaw              1       426 2014-07-02T18:42:30        41     N/A                  NO
           5099
     4361a302b417e72030ee4a7a54f6cbb12246ef18                         init3             35      8722 2014-07-02T19:30:30         8     YES                 YES
     279026c0485e73d51f435bd08b14c59b45cdb9a2                    oathkeeper             35      8722 2014-07-02T19:31:00         8     N/A                  NO


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
  "bitshares_toolkit_revision_age": "6 hours ago",
  "fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jul  2 2014 at 09:46:48"
}


Dont know if it is coincidence but I attempted to make ~2k transactions around block 5095.
EDIT: Some of them are still pending but they are processed at steady rate.

[bitcoinerS]

Looks like we got some forks..

Code: [Select]

>>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           2840
     e44923abbdc141cb2fa3e9338d89029e152256c7                      vikram10             34      8862 2014-07-02T09:11:00         2     YES                  NO
     6f1a88b185cf482735dc3921ab9f090bae9146e9                        alexxy             32      8854 2014-07-02T09:10:45        18     YES                 YES
           3378
     29d75ae255e7bc34d53ca2ac903d4c7bfcc45dbb                        lexx-6             34      8862 2014-07-02T11:45:45        14     YES                 YES
     745a989bfd91eb2e2cfd0f0195b03ecfd9e9e978           heyd-haiyaoce100lun             33      8618 2014-07-02T11:46:00         5     N/A                  NO
           4852
     0204f5c0b49fddcff6bfd2659975e3f0549ea626                         init5              0       182 2014-07-02T18:22:45         0     YES                 YES
     f550c1dd1c8c2fa521a8a0f2f421857e1a04f78d                      longclaw              1       426 2014-07-02T18:42:30        41     N/A                  NO
           5099
     4361a302b417e72030ee4a7a54f6cbb12246ef18                         init3             35      8722 2014-07-02T19:30:30         8     YES                 YES
     279026c0485e73d51f435bd08b14c59b45cdb9a2                    oathkeeper             35      8722 2014-07-02T19:31:00         8     N/A                  NO


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "85d44b47f23e66c7fb8c6c639a298dba9b20e09a",
  "bitshares_toolkit_revision_age": "6 hours ago",
  "fc_revision": "60a8f3d3bef46f988fb1b00b2a4f217bfecf7cd8",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Jul  2 2014 at 09:46:48"
}


[clout]

Do you guys now why some windows computers will not open the gui? On one of my computers says "There is no disk in the drive. Please insert a disk into drive F:."