Poll: the wishlist that you want most from service provided by DotWallet and Mempool.
Your valuable advice will be heard and carefully examined, and tipped.
An API for dotwallet which allows back-end automatic payments. We have a payroll issue at@SLictionary, because there's no easy way to have our back-end initiate a payment and send it to a paymail account. We wish to batch-process payments once a month, or once a week, or once per day. We don't want to screen scrape a wallet interface to initiate a payment which might happen a day or a week after a user does something. Think about a contest-winnings. The contest is 1 week, and we wish to pay 500 users a nickel each, all on Friday at noon. Does either dotwallet or mempool offer this? We're happy to write directly to mempool if so, but this would require us creating our own wallet as well.
I thought I've added my comment.
Use micropayment in DotWallet could use the payment in back-end.
I think invisible button from moneybutton and relay one can do the same trick.
Invisible MB is no good, it takes too much time to instantiate the user. We hope to have serviced our customer in a time faster than it takes for us to authorized invisible MB. So again, this is our suggestion for both DotWallet but would be better as a suggestion for@mempool. If you want details I can explain the situation privately?
Call it #0: SPEED
Need a wallet API which is super fast. No more swiping.... (3 seconds go by)... and waiting for confirmation on a transaction which is just a penny or two. At@SLictionary we wish to fully TRUST our users, and use the honor system, but while still collecting the money per swipe. SPEED is one of our core values. We'll consider any wallet or mining API which allows us to simply trust our users, and if we get "bilked" of our penny, so be it. We can always just ban that paymail account. Would b interested in hearing your thoughts on this LZ.
No, invisible money button requires lengthy authentication by the user, which is even slower. So it's not a solution for@SLictionary. Is dotwallet faster swipes and confirmations than MB? Our app intends to deliver a service to the user in as short a time as possible, seconds. We aren't a "destination" site. We judge our effectiveness based on how fast we get RID of the user after we give them the service.
Yes, authorize takes too long. Our service is fast, we cannot afford to put users thru the ringer of IMB authorization. so again, we recommend the same suggestion as written above. Best if its the miner who offers direct API payments.
Run/Jigs support.
Generate / export timelocked transactions to allow people to store offline.
Allow apps to generate raw TX without broadcasting, and use the SIGHASH flags.
stay tuned for the Run support.
what should timelocked transactions do? I think we can leave it to applications and the wallet could have the ability to sign off chain transactions/payment channel and chose not to broadcasting. good idea.
Agreed on letting apps handle it, but no wallet currently allows generating of rawTx w/out broadcast. even without being able to set SIGHASH flags, this would still be powerful.
Apps are too slow because this is not decoupled. Users should not and will not care if the tx is broadcasted, only if the app used is properly updated when action is taken.
With rawTx, I can fire off the tx to a MAPI asynchronously and continue processing. it is app's job to make sure they get paid, no need to punish the user by making them wait.