This thread was bumped today (4th Nov 2013) by a BTT member, the information within is out of date.Up to date information and announcements will be posted on BTT shortlyHey BitcoinTalkers
Been a while since I posted the original eMunie thread, and I stated that I would only post here in the future with any major developments. Well, I have a ton to share, as things have been pretty busy over here.
Due to these changes/improvements/additions the launch date has slipped by quite a lot, it was originally penciled for ~21st June, but even when posting the original thread, there were policies and philosophies in the design that I wasn't sure would stay, or might change. Which is why I didn't spend the time completing the whitepaper, as I felt that information might become outdated. Currently there is a tentative launch date set sometime around the end of July.
In this post I'll be addressing some technical elements, new features, the new and improved eMu generation model and how that will work. Plus some information on features that we are planning/building in to the system. Some of it I will keep out, as the features are innovative, but could easily be implemented by others, and I'm not a fan of my idea's being stolen before I've executed them.
All of what I post technically will be brief, and more detail will be included in the published whitepaper when methods are finalized.
Transactional ModelOriginally the eMunie transaction model shared a lot in common with the Bitcoin design, single chain, in and out transactions cross signed using ECDSA scripts and other similarities. From day one, this did not "feel" correct, it is limiting, it is susceptible to 51% attacks via forking and while its design is acceptable to a minor currency implementation, moving forward, it does not scale well enough to be considered a "fiat" challenger.
We decided to redesign 70% of our transaction model and refactor our code.
So how does it work now?Confirming transactions continues to operate in much the same manner, a forward and back search of the block chain is performed, verifying that the current transaction dependencies are legitimate and continuing in a recursive fashion until either the transaction worth is fulfilled by the transactions it depends on (ie you don't need to do a full tree scan), an eMu generation block is encountered, or the genesis. Coupled with our efficient POW algorithm (although slightly revised which I'll get into later on) this original method is still the basis of our transaction confirmation functionality and processing.
The main changes are in the "block chain" itself, and the way that transactions are recorded and stored.
eMunie now uses multiple chains, think of the ledger as more of a block tree, than a block chain. There may be many 1000's of small, interconnected chains, all holding valid transactions, and all able to validate transactions across other chain sections. "Forks", or new chains in eMunie are good, they strengthen the system and make a 51% attack impractical if not nigh on impossible, as there are so many chains, taking them all over is rather difficult. Transactions are verified in multiple blocks, with many "hatchers" (or miners as is the lingo here) in the system verifying the same transaction over and over and including a reference to that transaction in many blocks, within many chains.
Double spends are also EXTREMELY difficult with eMunie, as the system now favors a rolling balance over a "transaction in/out" method such as Bitcoin. As soon as you create a transaction, that transaction is distributed to the network as an intention, and it is logged. All nodes now know about this intended transaction and will include it in any subsequent balance calculation should they need it.
Upon the transaction clearing, that transaction is included in 1 or many blocks, and your rolling balance will calculate to the same as when performed using the transaction intention.
Transaction intentions take huge priority over other system messages, so to perform that double spend would require you to be very targeted in where it is sent to, know all about the current network position (its very dynamic) and sent immediately after the original transaction. Should you successfully achieve a double spend, soon after your rolling balance when calculated by nodes in the system will enter a negative balance, that peer and wallet address will then be immediately blacklisted forever.
.... NEXT eMu Generation ....