You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if the use of the words 'debit' and 'credit' in the definitions of 'mint' and 'burn' are intentionally used in the technical accounting sense of the term or not. The current wording implies that accounts are credit-normal (like a liability) and the total supply is debit-normal (like an asset). If that's the case, I think that that should be made explicit in the readme and the verbiage on
No, this is not intentional and there is no relation to the technical terms. We should probably change the wording to avoid confusion.
Perhaps drop the terms entirely:
#### `mint`
increase the `totalSupply` by increasing the balance of a specific address
(requires auth)
#### `burn`
decrease the `totalSupply` by decreasing the balance of a specific address
(requires auth)
My own two cents is that using the double entry accounting terms can lend a lot of clarity since they have implications about money supply invariants - in this case totalSupply == sum(balances). The only question would be which accounts are debit/credit normal but I think making user balances credit normal would be most natural.
I'm wondering if the use of the words 'debit' and 'credit' in the definitions of 'mint' and 'burn' are intentionally used in the technical accounting sense of the term or not. The current wording implies that accounts are credit-normal (like a liability) and the total supply is debit-normal (like an asset). If that's the case, I think that that should be made explicit in the readme and the verbiage on
ds-token/README.md
Lines 18 to 24 in 13e0934
The text was updated successfully, but these errors were encountered: