Addresses (Public Keys):

  • Bitcoin (BTC)
  • Bitcoin Cash (BCH)
  • SmartCash (SMART)


Nothing yet...

  • $
  • Ethereum's ecosystem is currently seeing a kind of mini-chain split. Although the Constantinople Hard Fork should be officially postponed, apparently every tenth Miner failed to install the appropriate updates. Apparently, a part of Ethereum Miner heard the bang: Despite the recent shift in the Constantinople Hard Fork have apparently taken about ten percent of miners, the new Ethereum implementation. reported January 17, citing data from Compared to the hash rate before (actually) canceled Hard Fork, the ethereum network now lacks between 10 and 20 TH / s. This means that about ten percent of miners have made the Constantinople update. So far it is still unclear whether and how many ether miners have consciously decided to take this step. It's likely that the announcement of the shift of Hard Fork has not penetrated to every miner. This suggests that it makes little economic sense for miners to address the overwhelming majority of the network's other miners and implement the version of Constantinople prone to reentrancy attacks. In addition, the Mining Difficulty on the Constantinople Blockchain is slowly but surely decreasing. Nevertheless, it has yet to show that this was not an intended chain split. Beware of transactions Node operators should now pay attention to which blockchain they participate in. Because even Ethereum developers are not immune to participate in the Constantinople Blockchain. For example, "Hard Fork Coordinator" Afrie Schoedon found that his node was included in the Constantinople Blockchain. If even the devs of their blockchain can not be sure, Ethereum users should be careful too. It can not be ruled out that ETH transactions will end up on the wrong blockchain. Until there is more clarity as to whether the ten percent of ether miners are feeling better and following the upgrade instructions posted on January 15 to get back on the right steamer.

  • ETH Fork postponed Shortly before the Constantinople Hardfork was supposed to be activated, the Ethereum developers blew it off. The reason: security researchers have found a bug. For Ethereum Node operators this means: You need an update again. The Constantinople Hardfork at Ethereum should actually have been activated today, on 16 January. It was considered uncontroversial and unproblematic, as it was supported by all developers and exchanges. Now the Ethereum Foundation announced that the Fork will be canceled: "The Ethereum Core Developers and the Ethereum Security Community were made aware that ChainSecurity discovered potential problems with Constantinople on January 15, 2019. We are investigating the potential issues and will follow up on an update. "Cautioned by key stakeholders in the Ethereum community," the best course of action will be to delay the planned Constantinople Fork, which will be at block 7,080,000 on the 16th January 2019 would have happened. " Anyone who runs a node - whether private, miner, stock exchange, or wallet service - must update Geth or Parity before the blockchain block reaches 7,080,000. For Geth there is already the release 1.8.21, for Parity Version 2.2.7. Alternatively, users can also downgrade to versions 1.8.19 or 2.2.4. For "normal users", ie those who use MyEtherWallet, Trezor, Ledger or Metamask, there is nothing to do. Your application will continue to run smoothly once the service providers have updated their node. The reason for the delay is that ChainSecurity has detected a problem with EIP-1283. In a post, ChainSecurity explains in depth what the bug is about. EIP-1283 lowered gas prices for a certain operation (SSTORE). That's the planned effect. However, an undesirable side effect of this is that reentrancy attacks can occur when smart contracts perform certain functions (address.transfer or address.send). The Consensys wiki explains that the "Reentrancy Attack" covers a wide range of smart contract issues: "One of the big dangers of calling external contracts is that they can take control of the control stream and thereby change your data in a way that the calling function not expected. This class of bugs can take many forms, and the two big bugs that led to the collapse of the DAO belonged to it. " The code of EIP-1283 is, in a surprising manner, vulnerable, ChainSecurity explains: "It simulates a secure shared credit service. Two parties can band together to get something, decide how to split the balance, and then receive a payment if both agree. "An attacker can attack a smart contract that involves them with a transaction , Then the attacker performs a storage operation - which, thanks to the benefits of EIP-1283, now fits into a transfer or send function - manipulating the distribution of assets so that everything goes to him instead of both parties. In itself, such a contract is well conceivable. A contract gets a deposit on it distributes it according to a certain scheme to the owners of the contract. Sounds useful. However, security analysis by ChainSecurity and TrailOfBits has not yet found a contract on the blockchain that is vulnerable. "However, there is a risk of more than 0 percent that some existing treaties will be affected," the Ethereum Foundation said. In order to give the analysts the time to examine the risks with care, it was decided that the Hard Fork be postponed. When exactly, nobody knows yet. Just removing EIP-1283 from the Hardfork features can also have unwanted side effects and at the very least has to be tested. In addition, the Ethereum developers want the feature yes, and maybe there is a way to activate it without any attack surface spanning. Too much time, the developers can not do it. Because Constantinople also defuses the Difficulty Bomb. This is an algorithm that determines that the difficulty of mining increases exponentially at some point in time. This is slow, but then faster and faster, until the network is virtually frozen, because nobody finds a block anymore. The effect is already visible: the number of blocks found on the day has fallen from a good 6,000 in December to a good 5,500 daily. It is expected that the Difficulty Bomb will be felt more and more clearly from February onwards

  • Banks in India: If you use Bitcoin your account will be closed Reports in the social media show that banks in India are threatening to close their accounts with Bitcoin and other cryptocurrency customers. This move is the latest step in the banking sector in a country where cryptocurrencies seem almost forbidden. Measures to contain Bitcoin On Friday (January 11, 2019), Morgan Creek founder and partner Anthony Pompliano released a tweet about the recent move by Indian banks to prevent Bitcoin trading. Banks warn their clients not to trade cryptocurrencies, otherwise they risk closing their accounts. The announcement even stated that banks do not need to send any further correspondence prior to the liquidation of client accounts. Pomp's Tweet came straight to the Twitter user, CryptoGirl, who commented on the situation as follows: INDIAN BANKS, WHO NOW REFUSE OUR CONFIRMATION BY RESERVING THE RIGHT TO CLOSE OUR ACCOUNTS WITHOUT ANY OTHER ANNUNCIATION WHEN WE ACT WITH # CRYPTOVER TRANSACTIONS. THE ABILITY TO DECIDE WHAT WE MAKE WITH OUR OWN MONEY IS THE REAL REASON WHY WE MUST INVEST #buidl & BELIEVE IN #bitcoin-there are also reports of similar news at Kotak Mahindra Bank. According to CryptoGirl, the bank has even put its threat into action. In an update, the bank issued a notice on the closure of cryptocurrency transaction accounts. Bitcoin is almost forbidden Unsurprisingly, the reaction to social media triggered outrage, as many claim that bitcoin is already almost banned in India with this action. In 2018, the Reserve Bank of India (RBI) banned banks to facilitate crypto transactions. India's Supreme Court will issue a final ruling on the RBI crypto-currency ban in September. A coalition of stakeholders questioned the decision and the matter remains unresolved for the time being. The government did not respond in October 2018 to a Supreme Court term. Before official regulations are available, the banking system in India is trying to stem the crypto trade. Since the government does not adopt a definite attitude towards cryptos, the RBI ban remains the de facto regulation in the country. #btc #bitcoin #news #india #bank #ban

No supporters yet.

No pledges yet.


  • Standard $1 a month