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
The goal of Monero for most Cake users I imagine is to replace regular fiat so I think having the ability to create budgets via automatic transactions via defined rules and automatic sub account creation would be a huge boost to encouraging a circular economy and improving general day to day spending, this would be extremely powerful when combined with #1330.
The way I envision this is that for instance you'd have your primary account where you would receive payments then you could have a rule that says for example every 15th of a month, transfer 0.2 XMR to the sub account called "Savings" and then with the creation of other sub accounts, there could be an option to display the balances of each sub account on the main screen without needing to go into the dropdown menu.
The text was updated successfully, but these errors were encountered:
Unrelated to budgets but another nice addition would the option to choose which sub account the monero is going to be taken from as well as which subaddress is used.
The goal of Monero for most Cake users I imagine is to replace regular fiat so I think having the ability to create budgets via automatic transactions via defined rules and automatic sub account creation would be a huge boost to encouraging a circular economy and improving general day to day spending, this would be extremely powerful when combined with #1330.
The way I envision this is that for instance you'd have your primary account where you would receive payments then you could have a rule that says for example every 15th of a month, transfer 0.2 XMR to the sub account called "Savings" and then with the creation of other sub accounts, there could be an option to display the balances of each sub account on the main screen without needing to go into the dropdown menu.
The text was updated successfully, but these errors were encountered: