TOPIC: SPECIAL HTMLCOIN WORLD MEETING JUNE 17, 2017.

AGENDA: TO DECIDE THE DETAILS OF THE WALLET UPDATE AND RELATED MATTERS.

TIME: JUNE 17, 2017, AT 10:30 AM BRITISH SUMMER TIME (BST).

PARTICIPANTS:] ATTENDED BY 27 INDEPENDENT DEVELOPERS AND COMMUNITY MEMBERS.

COUNTRY OF ORIGIN: THE UNITED STATES OF AMERICA, THE UNITED KINGDOM OF GREAT BRITAIN AND NORTHERN IRELAND, THE REPUBLIC OF THE PHILIPPINES, THE PEOPLE'S REPUBLIC OF BANGLADESH, THE FEDERATIVE REPUBLIC OF BRAZIL, THE ISLAMIC REPUBLIC OF PAKISTAN, THE REPUBLIC OF SINGAPORE, ROMANIA, THE FRENCH REPUBLIC, THE UNITED ARAB EMIRATES (DUBAI), THE REPUBLIC OF COLOMBIA, THE UNITED MEXICAN STATES, THE REPUBLIC OF INDONESIA, THE SOCIALIST REPUBLIC OF VIETNAM, THE REPUBLIC OF INDIA, THE REPUBLIC OF BULGARIA, AND THE RUSSIAN FEDERATION.

WE AGREED ON THE FOLLOWING:

ABSTRACT

•    We decided that Blockchain will not be reversed as requested by Bleutrade but we offer a possible solution.

•    We invited a Cryptocurrency Expert and a Computer Science faculty to help us understand the technical problem.

•    We are implementing checkpointing for Htmlcoin to hinder and stop hacking risk and future attacks.

•    We are releasing an updated wallet.

•    We want to understand more about the Bleutrade Insolvency Enigma.

•    Summary of the meeting and Implications of our decision as a community.

DETAILS

1.    We, HTMLCOIN Developers and Community Members in attendance, decided that Blockchain will not be reversed from April 25, 2017, until the present date of this meeting.[/b]

1.1.    The request of Bleutrade to reverse the blockchain was not granted by the core team. However, we offer them a possible solution for their claim of insolvency of 5.6 Billion by swapping the claimed lost coin to a new coin. It is important to note that not all of their holdings are lost, if any. We are waiting for their response on this offer. See section 5 - 5.5 for more information about Bleutrade Insolvency Enigma.

1.2.   We are looking forward to resolving this issue of insolvency claim with Bleutrade because we were part of this exchange since their early days in 2014, Bleutrade is a family to us.

1.3.    We believe that reversing will do more harm than good. If the blockchain will be reversed, it will erase all 1 month worth of transaction, that would be a bigger disaster.

1.4.    If we reverse the blockchain this would mean that all transactions conducted from April 25, 2017, to date will be nullified, all transactions thereafter will turn to zero. Reversing the wallet is NOT an option.

2.    We invited a cryptocurrency expert, Peter Bushnell, a former constituent of The University of Oxford, and Zac Smith, a faculty of Computer Science of New Mexico University, to help us understand the extent of our coin’s technical problem.

2.1.    Peter Bushnell’s advised that checkpointing be added in the coin and that the blockchain should not be reversed. Zac Smith agreed on these recommendations as well. The two experts are instrumental in our present decision for the coin, moving forward.

3.    We are implementing checkpointing for Htmlcoin, as the new feature of the wallet to hinder and stop hacking risk and future attacks.

3.1.    Simply put, the checkpoint prevents attackers from replacing the existing chain with a different chain to protects against transaction reversal. Checkpoints are built into the Bitcoin code, they are defined as a block height and its hash, the Bitcoin software will only connect to chains with those checkpoints in.

3.2.    Automatic Checkpointing is real time checkpointing, rather than define them in the code they are broadcast from a node on the network. In the source code there will be a public key, only a node with a corresponding private key can send out checkpoints, that node will also need to configure a depth for the checkpoints, that is how many blocks there needs to be after a block before it is checkpointed, so a depth of 5 means that a block will be checkpointed when there are 4 confirmations for it making it 5 blocks deep from the top of the chain.

4.    We are releasing a new Wallets and Files.

4.1.     This is the location of the Windows Wallet: http://seed.htmlcoin.net/HTMLCoin-1.3.2.1-setup.exe

4.2     This is the location of the Mac Wallet: http://seed.htmlcoin.net/Htmlcoin-1.3.2.1-Mac.dmg

4.3     This is the Blockchain: http://seed.htmlcoin.net/htmlcoin_blockchain.zip

4.4.    This is our GitHub account: https://github.com/HTMLCOIN/HTML5

5.    The Bleutrade Insolvency Enigma.

5.1.    The Attacker Deposited 5.7 Billion to Bleutrade and Withdraw the coin.

5.2.    Bleutrade informed us that “The attacker DEPOSITED 5.6 Billion in Bleutrade, sold an amount to Doge and withdraw the remainder.”

5.3.    HTMLCOIN Team investigated and found out that the total amount stolen from the attacker in Bleutrade is 928440.36517198 DOGE. See the spreadsheet, https://docs.google.com/spreadsheets/d/1FOJC3ayvP2gV69QfddmLPuVb06OAqw2mWfoVVT02Hww/edit#gid=0

5.4.    Logic will dictate that the insolvency in Bleutrade should only be 928440.36517198 DOGE, not the 5.6 Billion HTMLCOINS as claimed by Bleutrade.

5.5.    Because of this Enigmatic Insolvency claim by Bleutrade, we are asking them to clarify why there is such a huge insolvency, given that the attacker deposited the amount of 5.6 Billion to Bleutrade, meaning Bleutrade do not own the 5.6 Billion HTMLCOIN in the first place. The 5.6 Billion is owned by the attacker.

5.6.    On June 8, 2017, Bleutrade informed us the GOOD NEWS that the attacker was denied by the network.

5.6.1.    Below are the 2 deposits deleted from the blockchain even after several confirmations:

5.6.1.1.    HTML5 c8d657812abc1779d924235e6938a5c35e7428f5916eec38c64ea34ec18217f2 4605383 2017-04-25 23:09:17 HRYCxScEBr8R4eLRc9zwsmU8jX8gvcoM6a 2947478457.86640000

5.6.1.2.    HTML5 9699446ff34e6224a177df2566c6503f791330256601c7126ad10ed225c61b3b 4604813 2017-04-25 16:16:14 HTENYcoKi3NYM13AhwrjzsEN9AGnVYYYui 2852036157.86640000

5.6.1.3.    Total: 5799514615.73279954 HTML5

5.7.    Activity and Identity of the Hacker.

Username yanmar

E-mail yanmar@weibsvolk.org

::: LOGIN 2017-04-25 16:06:56.578353+00

::: --- IP 146.185.31.214

::: --- LAST ACTIVITY 2017-04-26 00:49:30.656994+00

::: --- TIMEZONE -3

::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

::: --- LANGS en-US,en;q=0.8

::: LOGIN 2017-04-25 12:14:44.607931+00

::: --- IP 37.130.229.149

::: --- LAST ACTIVITY 2017-04-25 15:40:26.436481+00

::: --- TIMEZONE -3

::: --- BROWSER Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

::: --- LANGS en-US,en;q=0.8

Withdraws to:

HKW9SyBMMqmvqtFVt62M38p1DB3E7fPtN6

H8gG3N12VBxkTGXvVNnU8h14ZvivYDVSVs

HMQ85E73ckbVX5km3531HfMk4Kn8egmmpV

H9fcC7c4UpjABeAGKpaac1KFehjz6Ft5aX

HJ6AeP636JQMt8HqtaDvUYggupZ7U3uh5t

HUBWDWrMvxAwtAbKB48RAVrCZgwnqqbk51

HFncs5hxUFvxnieNqWC48xrVjYtTijb7Jj

HQmwFURL5Rkb43gRNitKd5RfW4zZ2NNMcC

5.8.    We understand that this is a challenge for both Bleutrade and HTMLCOIN Community. Because of this, we are here to cooperate with Bleutrade in resolving this enigma. We maintain open communication with Bleutrade.

6.    Summary of the meeting and Implications of our decision as a community.

6.1.    Reversing the blockchain will do more harm than good.

6.2.    Because we decided not to rollback the blockchain, all coins outside of Bleutrade, specifically in Yo Bit and Coin Gather, it will not turn to zero, they are legitimate.

6.3.    We have instructed Yo Bit and Coin Gather to resume trading.

6.4.    We are releasing an updated Windows Wallet, Mac Wallet, Blockchain File, and the HTMLCOIN account in GitHub.

6.5.    We understand that the Attacker Deposited 5.7 Billion to Bleutrade.

6.6.    That the attacker was denied by the network.

6.7.    That the 2 deposits were deleted from the Blockchain.

6.8.    That we need to understand more about the Bleutrades Insolvency Enigma and we are willing to cooperate in solving this issue.

6.9.    The attack that happened in Bleutrade is not an isolated case to HTMLCOIN. Other cryptocurrencies in Bleutrade were also a victim of a similar attack, such as Virtacoin, Ambercoin, et cetera.

6.10.    That we have the identity of the hacker.

6.11.    We are maintaining open communication to Bleutrade to explore possible solutions.

6.12.    Given with this experience, we are now implementing real-time checkpointing moving forward so that the will withstand possible attacks a feature that will make HTMLCOIN stronger in the future ahead.

SOURCE: https://docs.google.com/document/d/1JpkQpDVzDeU2C2tgwSh7I31VBEuy4eXiFY2kR36KFiM/edit?usp=sharing