Contract use/bandwidth as an input

Let's say I want to create a decentralized name-resolution contract that requires a fee (in ether) before returning an address associated with a given human-readable name. The fee would be equal to the amount of ether required to store the contract divided by the number of such fees paid thus far, where the excess would be returned to sender as more people accessed the service (i.e. the first person pays the whole fee, the second pays 1/2 that, and 1/2 of the original fee is returned to the first--although obviously the could be improved with some usage statistics in order to charge the first person as close as we can get to their eventual statistical share.)

So, will ECLL allow for self-referential variables of these sorts?
Sign In or Register to comment.