Skip to main content

QUE.com Inforgraphic - History of Bitcoin

New to Bitcoin? You're lucky day, here's an infographic to easy learn about the History of Bitcoin.QUE.com.History-of-Bitcoin-InfographicInfographic by Fried.com

In addition. On July 20, 2017, the bitcoin miners voted, 97% in favor, on the Bitcoin Improvement Proposal (BIP) 91. The proposal, by Bitmain Warranty engineer James Hilliard, was to activate Segregated Witness (SegWit). Some members of the bitcoin community felt that adopting BIP 91 without increasing the block-size limit would simply delay confronting the issue and that it favored people who wanted to treat bitcoin as a digital investment rather than as a transactional currency. They announced implementation of Bitcoin Cash as a hard fork for August 1. It inherited the transaction history of the bitcoin currency on that date, but all later transactions were separate. Block 478558 was the last common block and thus the first Bitcoin Cash block was 478559. Bitcoin Cash wallet started to reject BTC block and BTC transactions since 13:20 UTC, Aug 1st 2017 because it used a timer to initiate a fork. It implements a block size increase to 8 MB. Bitcoin Cash started futures trading at 0.5 BTC on July 23, but dropped to 0.1 BTC by July 30. Market cap appeared since 23:15 UTC, August 1, 2017. On August 9th, it was 30% more profitable to mine on the original chain.[9] Even though the fork allows for a higher block size, block generation was so sporadic that the original chain was 920 MB bigger than the chain of the fork, as of August 9th. Source: WikiPedia.org

Source: https://que.com/history-of-bitcoin-infographic/

Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​
http://buddypress.org/ - Wordpress (Open Source and Free)http://elgg.org/ - (Open Source and Free)Commercial Social Networks software
http://www.socialengine.com/ ($299 Stand Alone, $29/mo Cloud)http://www.jomsocial.com/ (run with Joomla, need to know CMS)http://www.boonex.com/ (very expensive, $399 for Standard)http://www.anahitapolis.com/http://www.oxwall.org/http://sharetronix.com/http://www.moosocial.com/http://www.jcow.net/http://phpdolphin.comhttp://www.grou.ps (from free to Commercial, I left my networks and they are selling it http://www.phpfox.com/ (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company)http://www.ning.com (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:
http://www.whaddya.com/2011/09/windows-needs-your-credentials.html