and this too i marked the one line tht i dont understand. what does this mean?
http://vitalik.ca/files/ees_document_draft1.htmlAbstraction:
In Ethereum protocol development, one of the major overriding philosophies is the notion of abstraction: that the protocol itself should be as simple as possible, and as much as possible should be implemented in contract code instead of through hard protocol rules. Targets for abstraction include:
Account security (see
https://github.com/ethereum/EIPs/issues/86)
The transaction state transition function (ie. the rules by which a transaction is processed)
Ether (ie. make ether into a ERC 20 token just like the others)
Logs / events
The purpose of abstraction is the following:
Lower attack surface and lower core code complexity
The ability to more easily hardfork the public chain protocol to different protocol rules, as it can be done simply by swapping out contract code The ability to more easily swap out different rulesets on a test network or private implementation
The ability to switch between different rules on a per-application or per-user level (eg. some users want their accounts secured by ECDSA, some prefer Lamport for quantum-proofness, and in some private chain use cases industry or national standards require the use of specific forms of cryptography; the goal of EIP 86 is to support all of this)
EES may want to implement some of these abstraction features ahead of schedule.