Current BTSX share supply over 2 billion?

[ripplexiaoshan]

I agree.

who hold the extra supply before this bug was found ?

I am curious too... Also, I am curious about where does the burning fee eventually go, are they untouchable?  It seems we have to read the code to get more involved in the mysteries of the system...

It is not spendable by any transaction or any private key.  It simply takes it out of one account and then subtracts it from the supply.

Thanks for clarifying. Since there was no official announcement or explanation about this issue before this post was raised, most of the users didn't know this issue.

However, considering the seriousness of this issue, do you mind providing more details?  I am asking for this because some competitors, most of them from NXT community, are attacking BTSX due to this bug. They are blaming the untransparency of BTSX system. After all, creating BTSX from thin air is terrible terrible issue.  If we know more details, we can let them shut up.

For example, is now the supply correct? You said you burned your own fund to get the supply back to normal, but actually it seems now the supply is still larger than what it's supposed to be. Maybe you only burned a amount that make the supply below 2 billion, but not to the supposed amount? 

[bytemaster]

I agree.

who hold the extra supply before this bug was found ?

I am curious too... Also, I am curious about where does the burning fee eventually go, are they untouchable?  It seems we have to read the code to get more involved in the mysteries of the system...

It is not spendable by any transaction or any private key.  It simply takes it out of one account and then subtracts it from the supply.

[ripplexiaoshan]

I agree.

who hold the extra supply before this bug was found ?

I am curious too... Also, I am curious about where does the burning fee eventually go, are they untouchable?  It seems we have to read the code to get more involved in the mysteries of the system... 

[bytemaster]

FYI we are monitoring the supply to detect any and all deviations as soon as they happen and there are now API calls that allow everyone else too double check by summing all balances. 

[Mysto]

Yes, laddies and gentlemen, the BTSX supply is over 2 billion as a result of multiple bugs identified and fixed weeks ago.  The surplus supply will be burned from our own funds to return it to the proper supply.  We didn't want to spook people until we had the burn operation implemented so that we could correct it.

So where did this extra supply end up going?

1) Mostly to the delegates... our calculation of delegate pay was off and thus we miscalculated the running supply.   We stated earlier our intent to compensate delegates for the extra hard work they were doing, this particular bug just helped us do what we were planning on anyway.  Delegates running at a discount didn't have their pay burned like it was supposed to be.

2) Some white hat individuals who identified bugs and reported them to us privately after they exploited them.  We were able to fix the bugs without much being created.

can i step up and take public glory now?  ;) lol

haha

[xeroc]

hat's off to the white hats

+5%

[mavisjames]

Yes, laddies and gentlemen, the BTSX supply is over 2 billion as a result of multiple bugs identified and fixed weeks ago.  The surplus supply will be burned from our own funds to return it to the proper supply.  We didn't want to spook people until we had the burn operation implemented so that we could correct it.

So where did this extra supply end up going?

1) Mostly to the delegates... our calculation of delegate pay was off and thus we miscalculated the running supply.   We stated earlier our intent to compensate delegates for the extra hard work they were doing, this particular bug just helped us do what we were planning on anyway.  Delegates running at a discount didn't have their pay burned like it was supposed to be.

2) Some white hat individuals who identified bugs and reported them to us privately after they exploited them.  We were able to fix the bugs without much being created.

can i step up and take public glory now?  ;) lol

[alt]

This is a big event

I think our client is a serious commercial program

However, we have recently always be BUG problems

I think, this is not just a technical problem

I think this is the working procedures and testing procedures of the problem

I think there is no reasonable place there

To this problem, I have some suggestions：

We should establish a professional test team

Every code change, should pass their tests, and respect its views, then eventually released

@bytemaster I don't know whether you agree with it?

Or, have you ever thought about what better solution to do?

In short, we need a more rigorous

+5%
This Chinese man said he just graduated from junior high school.
we can see how much he want to contribute to this community
I agree him that we need to be more careful for the release.
and thanks bytemaster and mr white hat very much.  :D

[bytemaster]

I agree. 

[Musewhale]

Yes, laddies and gentlemen, the BTSX supply is over 2 billion as a result of multiple bugs identified and fixed weeks ago.  The surplus supply will be burned from our own funds to return it to the proper supply.  We didn't want to spook people until we had the burn operation implemented so that we could correct it.

So where did this extra supply end up going?

1) Mostly to the delegates... our calculation of delegate pay was off and thus we miscalculated the running supply.   We stated earlier our intent to compensate delegates for the extra hard work they were doing, this particular bug just helped us do what we were planning on anyway.  Delegates running at a discount didn't have their pay burned like it was supposed to be.

2) Some white hat individuals who identified bugs and reported them to us privately after they exploited them.  We were able to fix the bugs without much being created.

This is a big event

I think our client is a serious commercial program

However, we have recently always be BUG problems

I think, this is not just a technical problem

I think this is the working procedures and testing procedures of the problem

I think there is no reasonable place there

To this problem, I have some suggestions：

We should establish a professional test team

Every code change, should pass their tests, and respect its views, then eventually released

@bytemaster I don't know whether you agree with it?

Or, have you ever thought about what better solution to do?

In short, we need a more rigorous

[bytemaster]

Can management of the supply be automated within the network to avoid future error or potential manipulation? I have no technical expertise here, just wondering as a user.

It is automated when the automation works :) 

[starspirit]

Can management of the supply be automated within the network to avoid future error or potential manipulation? I have no technical expertise here, just wondering as a user.

[liondani]

I just saw this thread, ran "info" twice and happened to see it cross back below 2 billion!  Here's a copy-paste with block numbers for posterity:

Code Select Expand


default (locked) >>> info
{
  "blockchain_head_block_num": 555311,
  "blockchain_head_block_age": "10 seconds old",
  "blockchain_head_block_timestamp": "2014-09-22T21:32:20",
  "blockchain_average_delegate_participation": "92.66 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.19309 BTSX",
  "blockchain_share_supply": "2,000,000,001.77099 BTSX",
  "blockchain_blocks_left_in_round": 88,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-22T21:47:10",
  "blockchain_random_seed": "f328415b9decc04a75b559f9c2148d42f90d81c2",
  "client_data_dir": "/home/cc/btsx/.BitSharesX",
  "client_version": "v0.4.16",
  "network_num_connections": 12,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T21:32:30",
  "ntp_time_error": -0.019689999999999999,
  "wallet_open": true,
  "wallet_unlocked": false,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
default (locked) >>> info
{
  "blockchain_head_block_num": 555312,
  "blockchain_head_block_age": "8 seconds old",
  "blockchain_head_block_timestamp": "2014-09-22T21:32:30",
  "blockchain_average_delegate_participation": "93.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.19307 BTSX",
  "blockchain_share_supply": "1,999,999,999.79720 BTSX",
  "blockchain_blocks_left_in_round": 87,
  "blockchain_next_round_time": "at least 14 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-22T21:47:00",
  "blockchain_random_seed": "72a2e5b13c7efa04310038145f8951f62ab50043",
  "client_data_dir": "/home/cc/btsx/.BitSharesX",
  "client_version": "v0.4.16",
  "network_num_connections": 12,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T21:32:38",
  "ntp_time_error": -0.019691,
  "wallet_open": true,
  "wallet_unlocked": false,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}


[CLains]

hat's off to the white hats

[tonyk]

2) Some white hat individuals who identified bugs and reported them to us privately after they exploited them.  We were able to fix the bugs without much being created.

Which white hats? The mysterious yet well acquainted with the code 'emf'?