The Origins of iEthereum
2122 Days ago, on October 9, 2017, in a galaxy far away the ERC20 iEthereum token was created on the Ethereum network in block
2122 Days ago, on October 9, 2017, in a galaxy far away the ERC20 iEthereum token was created on the Ethereum network in block 4350256.
The iEthereum deployer address is 0x1af00FD719E00347A517aF0716dbcAEED9A7B230
The iEthereum contract address is 0x859a9C0b44cb7066D956a958B0b82e54C9e44b4B
The originating transaction hash is 0xe97b27e217b86b229bd44686d1095b43232e0c378db82427ea7c5d1666326df8
When iEthereum launched back in 2017, I remember conversations with fellows regarding the tokens reference to the Human Standard Token. The HumanStandardToken does deserve a complete article in and of itself in the future to fully understand the capability and inner workings of the iEthereum token. We will save this information for a later date.
One of the reasons to start this newsletter community is to document past fundamentals to iEthereum that are now starting to be disappeared through time and restricted access to archival internet history.
We have all read things that we go back to lookup for a present reference use and we can not find. Searches are omitted, links are broken and/or archival records restricted.
The history of iEthereum, in terms of cryptocurrency, is interesting with a level of intrigue and mystery.
The logo of Ethereum within the Apple logo
Launched under MIT license
Strategically did not launch using an ICO
The governing of throttle to thwart adoption
The continued price manipulation at a high level
And of course, according to my memory, Github recorded a fork of the Human Standard Token to create the original iEthereum.
If anybody reading this has the ability to access Github for archives older than 5 years, please confirm my recollection. I would appreciate being forwarded the documents to add to our own iEthereum library. This article is being written to point internet researchers in the right direction.
Fortunately, there are other methods to highlight the iEthereum origin being the Human Standard Token.
Another confirmation is to copy and paste the source code into Google's BARD AI.
BARD: "The contract source code you provided is for a HumanStandardToken, which is a type of ERC-20 token. ERC-20 tokens are a standard set of rules that allow tokens to be transferred and interacted with in a consistent way.
The HumanStandardToken contract includes the following features:
Initial Finite Supply: The total number of tokens that will ever be created is specified when the contract is deployed.
Decimal, Symbol & Name: The token can be given a name, symbol, and number of decimal places.
approveAndCall() functionality: This allows a contract to be notified when an approval has occurred.
The contract also includes some optional features, such as the ability to send ether to the contract and the ability to customize the token's name, symbol, and decimal places.
The HumanStandardToken contract is a good example of a well-designed ERC-20 token. It includes all of the necessary features and is easy to use.
Here are some of the benefits of using the HumanStandardToken contract:
It is a standard contract, which means that it can be used with other ERC-20 tokens.
It is well-designed and easy to use.
It includes all of the necessary features for an ERC-20 token.
If you are looking to create an ERC-20 token, the HumanStandardToken contract is a good option. It is a well-designed and easy-to-use contract that includes all of the necessary features." ---
It turns out that the Human Standard Token is a token factory that creates a standard, fully open sourced code; intended for user simplicity, with greater security and compliance while creating token specific originality. In terms of iEthereum, an original contract with unique iEth ticker to recognize the iEthereum name, identified decimals as 8 and a set finite supply of 18,000,000.
Consensys deployed the Standard Token Factory to the Ethereum mainnet in June of 2016.