Personalised Destination tags
Wo Jake
Great idea, this will allow users to expand their “accounts” on XUMM without having to fund new accounts every time (10 XRP).
The issue is, although this is a great idea to mitigate the cost of creating accounts, XUMM is built (frontend) to only display the whole wallet’s spendable balance, how do you plan to divide the spendable XRP based on “sub accounts/destination tags”?
Let me explain, when Account A gets 100 XRP on destination tag 280, and gets another 50 XRP on destination tag 279.
280: Savings
279: Allowance
How do you plan to divide those 2 (sub accounts)’s XRP accordingly, thanks.
Wo Jake
Not to mention that users could export their private keys and send payments through another application, so even if XUMM keeps track user’s sub-accounts locally, this just wont work :(.
C
Charl
Wo Jake: True, the main problem with this would be that it is device specific, so it won't reflect on other devices. It might also be redundant if the new 'Lite Accounts' get approved where it takes only 1XRP to activate the account. With that you can just set up lite accounts for the different requirements.
Trần Quốc-Bình
While I like your idea, but I don't think it is feasible.
The XRP coming in have a destination tag, so yes in theory you can separate the sub accounts. But, and this is a big But, when you use your XRP to send, there is no source tag to know which sub account you have sent to that from?
C
Charl
Trần Quốc-Bình: You could select a 'tag account' to send the XRP from.
From what I understand from destination tags is that its a 'local identifier' to indicate what sub account it belongs to. So all that account details would be stored locally on the device.
That being said, I am not sure if that kind of data would translate to other applications. So if you were to login to XRPtoolkit that sub account data would not be available seeing as all that is stored on the local device. But I have limited knowledge of how it all works so I could be wrong.
Trần Quốc-Bình
Charl: Like I said, I really like your idea, but being a programmer myself, I know the challenges of doing this feature. It's all about what you get from the effort you put in.
First, if you can create a new wallet with just another lock up 10 XRP or losing 2 XRP at the end of the usage. Why not just do that? It's not that hard to do now, considering the price of XRP is still $1 range.
Second, XRP wallets are decentralize, you can use XUMM, Ledger Live and also use EXODUS for the same wallet. So if the other wallets does not have the same feature, all your balances will not matches and thus seems like an unwanted bug. And the effort to get all other wallets developers to agree on this feature, the effort is too much?
Personally, I like to put forward and vote to only lose 0.1 XRP when closing an account because it is essentially only another transaction on the XRPL. Why do we must burn 2 XRP just to closed an account? If this closing fee is small, none of us would bother with sub accounts.
Bluesky7
It should not be mandatory but it is a good idea
C
Charl
Bluesky7: Correct, it should be an optional extra and not mandatory.