Named “Elastic” because a hat’s proportion-value can grow/shrink depending on a change in rDAI balance. Hats are not static in v1 rDAI
Copying Victor’s comment from another post:
Non-users can increase a wallet’s rDAI balance without any action by the wallet owner, either by calling payInterest on behalf of someone else or by sending rDAI directly. This will increase the amounts going to the recipients proportionally, circumventing our integer-based fixed Tribute amount framework. How can we design such that user decisions about how much to send as Tribute don’t get out of whack due to external actions?
Based on Brian and Ethan’s research, changing the contracts themselves is the only way to solve this problem. How can we fix it with minimal changes to the contracts? Is this a task we should take on ourselves, or just put together an argument why it’s necessary?