Instead, you can use a cryptocurrency which supports declarative smart contracts, which a lay-person could read, write and understand.
Declarative smart contracts, over at https://byteball.org/
m / m^3 = 1/m^2
Which is the unit for fuel efficiency. It's expressed in imperial units but it's physically sound, not 'crap'. ;)
In other parts of the world you'll see this expressed as "liters per 100km" usually.
MPG is more pervasive than you might think. Even in metric, European Ireland it's the typical unit, despite speeds being in km/h and fuel being sold by the litre.
Since you seem to be interested, let me also add that litres are only accepted by, not part of, the SI. Also the SI spellings are "metre" and "litre".
I'm actually quite interested in the fact that any equation can be "sanity checked" by solving it for units only (without values). It's always handy to make sure I didn't forget some exponent here or there. And knowing extended units as a composition of fundamentals (some variation of mksa) is kind of entertaining intellectually.(e.g. Newton = m.kg/s^2, which really makes sense when you think about it). Going down to Planck units and their significance in this universe (discrete spacetime manifold? Is reality ultimately non-continuous?), and here I am wishing our conventional units (of time, distance, all) were integer multiples (e.g. Decimal exponents) of Planck units. But I'm digressing, aren't I.
As far as fuel and efficiency goes, I'm not much of a car person. I didn't know that mpg was used outside the US, that's an interesting historical artefact.
What you pay in transaction fees is the amount of bytes used to represent your data.
Byteball can then also store immutable data of various lengths, if you are willing to pay for it in the price of bytes for the storage of bytes you like to store.
Makes sense.
That means you can have a decentralized application and also have the security of the bitcoin network, for example.
Byteball is live right now, Iota is still in closed/private beta testing with less features.
http://www.tangleblog.com/2017/01/03/byteball-vs-iota-token/
http://www.the-blockchain.com/2016/12/11/happy-holidays-byte...
They both seem like interesting projects.
They dont even use the same underlying technology, unless you consider DAG to be a technology rather than a data-structure. Iota nodes are written in Java, Byteball is all in Node.js
As is usual in cryptocurrency world, if you want news and technical documentation on Byteball, you ask the Byteball people, do not ask Iota, and vice versa.
IOTA has something like "Monte Carlo Random Walk for Tip Selection by most Proof-of-Work" while Byteball has 12 trusted witnesses to stamp and order transactions as they see them, stamp only when satisfying consensus rules, a Main Chain can then be built from all possible transaction histories (branches). No proof-of-work aside from signatures.
Today all witnesses are run by main developer. A hub on the Byteball network can push witnesses, if users trust a particular hub they can check a box to pull the witness list, this is just user-friendliness.
The witnesses are supposed to be selected by humans by talking, like a popularity contest. There is no automatic protocol-selection process aside from described below.
Each user/transaction is allowed 1 mutation in the 12 list, so technically there can be more witnesses than 12 in the network, but only 12 selected in each transaction.
Then, when enough transactions have replaced same witness with a new one, the stability point, ie best parent, can be advanced and next witness can be replaced. See the whitepaper for more details on this advancing of "best parent" in the Main Chain. Like a snowball.
The process is user-driven, the costs to replace it by malicious intent is too high due to transaction fees, the limit on 1 mutation and hence slow time to actually replace all of them or a majority is also to ensure human herd-behaviour doesnt make bad decisions.