A smart contract with a stablecoin (or a wrapped stabblecoin) would probably solve for this use case.
You want to avoid leaving a bank password in clear text for the process running in cron; so it would really be best for the bank to support Read-Only and Read-Write access tokens
Trying to figure out if this should be: - Crypto-native from day 1 (smart contracts + stablecoins) - Fiat-first with crypto as backend (abstract the blockchain) - Pure fiat (traditional banking APIs)
What would you actually use?
Just curious, if you didn't have smart contracts, you would have 20 destination addresses, and then a spreadsheet that you'd use each month and then run a local wallet to do the sending to the different parties, right? That's pretty easy.
Could that be automated on the client-side with macros or a custom program (ie no smart contracts?)
It's probably simple to find a validated smart contract that splits its inputs to multiple outputs?
If there is transaction privacy for the smart contracts, then how to verify that the contract actually still sends to the correct - initially configured - parties?
And then logging. Task accounting implies logging, but logs are bytes that cost money in a blockchain so is the transaction log sufficient