bsips
bsips copied to clipboard
bitshares
Initial draft of recurring monthly withdrawals
It popped up in Telegram that including an auto-payment feature would be nice to have for withdrawal feature. Meaning: Automatically transfer the maximum amount for each period to the configured receiver.
What do you think?
This would require additional processing on-chain. I don't see a significant advantage for users - recipients have to check for incoming funds anyway.
Can someone check how often withdrawals have been used yet? We should keep an eye on the cost/benefit ratio of these things.
@pmconrad One review of the blockchain operations through June 2018 indicates
- 17 withdraw permission create (Operation 26)
- 0 withdraw permission update (Operation 27)
- 0 withdraw permission claim (Operation 28)
- 0 withdraw permission delete (Operation 29)
This would require additional processing on-chain. I don't see a significant advantage for users - recipients have to check for incoming funds anyway.
I agree with this. Since the software does not have an architecture to process "stuff" on a timed basis (except for maintenance interval), I would also prefer not to automate things too much.
One of the design principles, originally, was to have actions explicitly executed.
Hence, we could as well do similar to vesting balances in that balances accumulate according to some rule (e.g. unit-step function with monthly reset) and then let users explicitly claim.
