Now I have to go, I have many things to finish. If I will use all my energies answering people's questions, I might exhaust myself and not be able to address the most urgent needs such as coins specs, website enhancement, building team leaders in various countries, and talk to potential investors.
If I will not be answering questions here such as "why...this and that..." meaning I am working hard for the community.
Also, I am finishing my doctoral dissertation as well, while doing my baby project htmlcoin, so it's really hard for me to entertain small talk, like; this coin is a scam, the coin is a sh**t, and sometimes, the post makes me laugh, they don't know how hard it is to be a developer dealing with many people all wanting my attention.
Like HTML, I will endure, since 2014 HTMLCOIN stood the test of time, and the coin and the community is here to stay 
|
|
|
|
Asking for everyone to deposit their coins onto exchanges when withdrawals are disabled sounds very fishy... Swaps can be done for folks who keep their coins in wallets, so why the need for exchanges?? Either enable withdrawals so people don't feel that their coins are being held hostage or process swaps without waiting for 75% of coins to be on exchanges.. HTML5 is a very promising coin, with dedicated dev team that has supported the project since the beginning. Thank you!However we need the DEVs to be more straight-forward regarding their decisions. We need explanations for some of the conditions imposed on HTML5 coin holders such as such as: - depositing 75% onto exchanges as a requirement to trigger the coin-swap
-It would be a manual labor for us to do manual swapping more than 2500 people.- asking to deposit our coins to exchanges when withdrawals are disable is sketchy and smells scammy.. Again, you may not deposit it, and we will do the manual swap for you, that would mean labor job for us. I think I need to change 50 dollars per swap...lol... with my time and effort (Joke)- why cant we have specific timelines for the coin-swap are needed, perhaps break it up in stages, how long each stage will last (ie: 1:1, then 1:2 - we need timelines)
No specific timeline because the coin is being built, and we have to do a battery of testing. Tech project always fails timeline.We need the coin-swap to be handled outside of 75% exchange deposit requirement - either enable withdrawals or coin-swap w/o 75% requirement. With recent BleuTrade hack how do we know that our coins won't be hacked once deposited? HTMLCOIN cannot be hack anymore, we enable real-time checkpointing.I think the coin-swap should be scheduled on a specific date regardless of how many coins are on exchanges.
I already explain this in the previous question If you agree with above points please reply to make your vote known to the DEVs.
I already replied as the dev, but not voting This coin has a good name and lots of potentials, we just need the DEVs to be more transparent about the decisions made and answer the questions that are raised by coin holders.
Yes, we are, the most users we have are from the Latin American Countries. A huge concentration in Vietnam, China, Philippines, and the Middle East. We have a considerable number in Eastern Europe, followed by France and Spain. We will continue to focus on the Asian countries, especially China, to get more users and community members from there. |
|
|
|
|
Frequently Asked Questions & Guidelines for the Htmlcoin Swapping 2017
Who: All Htmlcoin Holders
What: Swapping old htmlcoin to the new htmlcoin.
How: One to one ratio (1:1) during the specified swap dates. One to two or less ratio (1:2 or <) for late swappers. The further you swap from the scheduled date, the lower the swap ratio you will get.
When: After 75% Percent of all coins in circulation accounted in the exchange sites
Where: Exchange Sites and Manual.
Why: To upgrade coins specifications.
Exchange Sites: Currently, no one can withdraw, this is in preparation for the swap day. All traders can continue to trade and able to deposit.
>>>IF your coins are located on the Exchange Sites, you do nothing. The exchange will do it for you automatically.
>>> IF your coins are located in the wallet, you have to show proof:
On the right side must show the latest transaction.
Send am htmlcoin to any address to do this, we suggest sending one (1) htmlcoin or less.
Take a picture with your finger in the photo pointing the amount.
A screenshot is not acceptable.
We may ask additional information, such as your wallet address, to see in the explorer the exact amount, as shown in the picture.
You will be asked to email it to the specified email address, wait for more updates.
>>> IF your coins are located in the paper wallet, you must show the address.
Nota Bene: Old HTMLCOIN mined during or after the swap date will not be honored.
*These guidelines above may change anytime.
|
|
|
|
|
Frequently Asked Questions & Guidelines for the Htmlcoin Swapping 2017
Who: All Htmlcoin Holders
What: Swapping old htmlcoin to the new htmlcoin.
How: One to one ratio (1:1) during the specified swap dates. One to two or less ratio (1:2 or <) for late swappers. The further you swap from the scheduled date, the lower the swap ratio you will get.
When: After 75% Percent of all coins in circulation accounted in the exchange sites
Where: Exchange Sites and Manual.
Why: To upgrade coins specifications.
Exchange Sites: Currently, no one can withdraw, this is in preparation for the swap day. All traders can continue to trade and able to deposit.
>>>IF your coins are located on the Exchange Sites, you do nothing. The exchange will do it for you automatically.
>>> IF your coins are located in the wallet, you have to show proof:
On the right side must show the latest transaction.
Send am htmlcoin to any address to do this, we suggest sending one (1) htmlcoin or less.
Take a picture with your finger in the photo pointing the amount.
A screenshot is not acceptable.
We may ask additional information, such as your wallet address, to see in the explorer the exact amount, as shown in the picture.
You will be asked to email it to the specified email address, wait for more updates.
>>> IF your coins are located in the paper wallet, you must show the address.
Nota Bene: Old HTMLCOIN mined during or after the swap date will not be honored.
*These guidelines above may change anytime.
|
|
|
|
Developers are you still planning to implement POS/POW and a 10 minute block time. A 10 block time would be good to help the price increase, limiting the supply by a factor of what 10?
We will update you guys on the proposed specs |
|
|
|
No, Please solve the main problem with yobit now.
There is no withdrawal for Yo Bit, this is in preparation for the swap. |
|
|
|
SITEMAP DRAFT FOR HTMLCOIN NEW WEBSITE 2017 Please send your suggestions to email@htmlcoin.com -HOME Video Explainer Current price of HTMLCOIN in SATOSHI & Dollar All wallets Github CoinMaeketCap Contact Us/Get updates The Team Core Team Independent Community Developers List of authorised websites and email domains. Our Advocacy Mission Vission Goals & Objectives Road Maps 5 Year Strategic Plans Business Development -SPECS All technical info of the coin Proof of Developer (Certifications) Explorer Mining Pools Wallet Update Instructions Source Code -TRADEExchanges Merchants Authorized Coin Sellers -SERVICEAll applications develop for the coin -NEWSMust be in blog format Links of important outside news -COMMUNITYAbout the community List of Social Media List of Forums Facebook Groups in various counties Independent developers page/blogs/website -LIBRARYWhite Paper Road Maps Strategic Plans Branding Guidelines Infographic Repository Group Official Documents
|
|
|
|
SITEMAP DRAFT FOR HTMLCOIN NEW WEBSITE 2017 Please send your suggestions to email@htmlcoin.com -HOME Video Explainer Current price of HTMLCOIN in SATOSHI & Dollar All wallets Github CoinMaeketCap Contact Us/Get updates The Team Core Team Independent Community Developers List of authorised websites and email domains. Our Advocacy Mission Vission Goals & Objectives Road Maps 5 Year Strategic Plans Business Development -SPECS All technical info of the coin Proof of Developer (Certifications) Explorer Mining Pools Wallet Update Instructions Source Code -TRADEExchanges Merchants Authorized Coin Sellers -SERVICEAll applications develop for the coin -NEWSMust be in blog format Links of important outside news -COMMUNITYAbout the community List of Social Media List of Forums Facebook Groups in various counties Independent developers page/blogs/website -LIBRARYWhite Paper Road Maps Strategic Plans Branding Guidelines Infographic Repository Group Official Documents
|
|
|
|
 HTMLCOIN SWAPPING 2017
HTMLCOIN is swapping this 2017 with a new feature that includes the many applications of "Smart Contracts" and the security provided by "Real-Time Checkpointing."
All coins in the three (3) exchange sites are safe and will be swap to a stronger version, with all the latest features of the leading cryptocurrency in the market. This huge step that we are undertaking will make our coin relevant and responsive to the demand of the "Internet of Things."
Current owners of HTMLCOIN will now be able to swap to at ratios between 1:1. Late swapper will be at the ratio of 1:2 or less, depending on the time. The further you swap from the scheduled date, the lower the swap ratio will be.
Cryptocurrency exchanges Bleutrade, YoBit, and CoinGather are currently preparing to facilitate the swaps.
Let us know if you have features/specifications that the new HTMLCOIN should have, contact us: email@htmlcoin.com.
More details of the swap will be posted soon, stay tuned!
|
|
|
|
HTMLCOIN SWAPPING 2017
HTMLCOIN is swapping this 2017 with a new feature that includes the many applications of "Smart Contracts" and the security provided by "Real-Time Checkpointing."
All coins in the three (3) exchange sites are safe and will be swap to a stronger version, with all the latest features of the leading cryptocurrency in the market. This huge step that we are undertaking will make our coin relevant and responsive to the demand of the "Internet of Things."
Current owners of HTMLCOIN will now be able to swap to at ratios between 1:1. Late swapper will be at the ratio of 1:2 or less, depending on the time. The further you swap from the scheduled date, the lower the swap ratio will be.
Cryptocurrency exchanges Bleutrade, YoBit, and CoinGather are currently preparing to facilitate the swaps.
Let us know if you have features/specifications that the new HTMLCOIN should have, contact us: email@htmlcoin.com.
More details of the swap will be posted soon, stay tuned!
|
|
|
|
|
We will be announcing soon!
|
|
|
|
We need a clear answer from the developper.
You told us previously that trading on bleutrade is the only secure way to buy and sell html5 coin, which i did, and now you are telling us anywhere but bleutrade is okay to buy from?! What is this dev?
Now i have my html5 coin stuck in a frozen market in bleutrade, i can withdraw them, i cant trade them, this issue with bleutrade has to be solved as soon as possible!!
This issue is a big issue. You have even written by only from bleutrade in red and capital letters!!!
You have to communicate with bleutrade and give them whatever they want for solving this situation!!!
Are you going to do anything ?
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. |
|
|
|
I updated the wallet HTML5COIN put a new version, but it does not work with the network,what do I do? I have the old wallet now I cant send them to the exchange.
Copy contents of this archive to your HTMLCoin data directory found in the following locations. If the folder is not there already then please create it.
Windows XP
C:\Documents and Settings\YourUserName\Application data\HTML5
Windows Vista/7/8/10
C:\Users\YourUserName\Appdata\Roaming\HTML5
Linux
./HTML5/
Mac
~/Library/Application Support/HTML5/ |
|
|
|
6.5. We understand that the Attacker Deposited 5.7 Billion to Bleutrade.
Where these the Cryptsy coins? It has been said before the Cryptsy coins were burned (as they should be), was this how they were burned? Good to see the communication of the minutes of the meeting. Improved communication is often the best way to increase confidence in any project.
We do not know what happen to those unwithdrawn HTMLCOINS from Cryptsy. |
|
|
|
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.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.exe4.2 This is the location of the Mac Wallet: http://seed.htmlcoin.net/Htmlcoin-1.3.2.1-Mac.dmg4.3 This is the Blockchain: http://seed.htmlcoin.net/htmlcoin_blockchain.zip4.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
|
|
|
|
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.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.exe4.2 This is the location of the Mac Wallet: http://seed.htmlcoin.net/Htmlcoin-1.3.2.1-Mac.dmg4.3 This is the Blockchain: http://seed.htmlcoin.net/htmlcoin_blockchain.zip4.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
|
|
|
|
|
Show Posts
