More on this @
www.Edisonx3.orgTweet this around via
http://twitter.com/EdisonArmyThread:
https://bitcointalk.org/index.php?topic=491711.0http://edisonx3.org/prelaunch2.pngImportant Facts about EdisonX3
Edison has its own Open Source (FAIR USE) Technology called the Edison Carbon Filament
The Edison Carbon Filament has its own unique code created to secure the network against security flaws and potential harmful threats for the community.
The team spent hours and weeks working on this new difficulty adjustment ALGORITHM to platform stay neat security functions for the next 1,000 years that Edison will be alive for.
EdisonX3 is defined as a Crypto Currency using Scrypt Algorithm with new implementation to solve Malleability issues. This is totally not HACKER FREE nor Bullet Proof. The network is setup just to stabilize against possible attacks, aside from double spending *51% attacks* and uncommon exploits created by the coind network. In addition, this will be used as a defense mechanism against large mining farms that out weight community hash power and punishing those who try to "PROFIT SWITCH" or "GAME ALTCOINS".
The point of EdisonX3 being spread out for 1,000 years, long block times for safety against the most recent Malleability Transaction issues (still a big problem for Bitcoin), and now halting the progress of monopolized coin farm strategies.
What is Transaction Malleability ?
While transactions are signed, the signature does not currently cover all the data in a transaction that is hashed to create the transaction hash. Thus while uncommon it is possible for a node on the network to change a transaction you send in such a way that the hash is invalidated. Note that this just changes the hash, the output of the transaction remains the same and the bitcoins will go to their intended recipient. However this does mean that, for instance, it is not safe to accept a chain of unconfirmed transactions under any circumstance because the later transactions will depend on the hashes of the previous transactions, and those hashes can be changed until they are confirmed in a block. (and potentially even after a confirmation if the block chain is reorganized) In addition clients must always actively scan for transactions to them; assuming a txout exists because the client created it previously is unsafe.
