That's all pretty freakin' awesome, but I have a question.

Hive account@dan, Just wondering what you can tell us about what you mean in the document when you refer to "billing".

My understanding from reading the whitepaper, and from listening to you, is that the cost of running a DApp in EOS is a combination of the cost of purchasing the EOS tokens that grants you a guaranteed minimum resource capacity for your dApp, plus the less transactional cost of inflation to pay for the running of the infrastructure etc.

Then your new document talks about "billing", and those waters get muddy real fast. For example, in a chapter about a new compression feature in the EOS blockchain.... It's a great feature, because as described, there are a lot of cases where the data you might need to attach into the blockchain for guaranteed immutable public record purposes may often be large but compressible. You give examples, such as "the ABI specification and the Ricardian contract associated with an account/contract" that could seriously do with some compressing, but then in that same short chapter says "By utilizing transaction compression the blockchain can more efficiently store and transmit large numbers of transactions and bill users less for transactions with compressible data than transactions with incompressible data."

Maybe you can clarify what you mean by "bill user" here?