@linzheming is on PowPing!

PowPing is a place where you can earn Bitcoin simply by socializing, for FREE.
Never tried Bitcoin? It's OK! Just come, socialize, and earn Bitcoin.
Check out linzheming's activities
Total Economy: 15.46 USD
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.
slictionary tipped:
0.08 USD
1 year ago
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.
linzheming replied:
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.
slictionary replied:
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.
slictionary replied:
#0 = "Ground Zero"
linzheming replied:
Use dotwallet micropayment for that. and I bet invisible button from moneybutton will do the same trick.
slictionary replied:
slictionary replied:
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.
linzheming replied:
Authorize first then everything happened in the backend.
slictionary replied:
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.
Expense & Income tracker by different apps, w/ dashboards
linzheming replied:
Very helpful if we successfully grab enough attention from apps. Not enough apps right now.
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.
linzheming tipped:
6.38 USD
1 year ago
linzheming replied:
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.
joshua replied:
Make your own trust or inheritance schemes. They could just sit somewhere and only be valid at a later date.
joshua replied:
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.
joshua replied:
@linzheming was the 0.05 BSV a double tip on purpose? Or a bug? If so I don't see on this thread or my notifications. Only a few bytes are different in the rawtx in the OP_RETURN https://whatsonchain.com/tx/cb5d72460ebc0c57059f622de3785e74ae0e80bb795bfa4ba8b18e5ea379785f https://whatsonchain.com/tx/a94ef3fa62a7bc0de872fc92dfae078d823f8f53cb03678b93a4bbd63add6dd8 Cc@unwriter
joshua replied:
Also thank you very much for the tips!
linzheming replied:
a bug it might be. I tipped and I don't see the result so I tipped again.
joshua tipped:
6.37 USD
1 year ago
joshua replied:
sent it back sir.
make your wishes.
10. Pay to different miner(s) with different fees?
9. Free quota to mine consolidate utxo transactions.
joshua replied:
yes please.
8. Allowing assemble tx with different sighashs.
joshua replied:
1000%
7. Pay bitcoin fees by wired transfer/paypal USD and get invoiced.
6. Separate data UTXO from funds. by using different HD path.
5. Double spending detection and prevention or even insurance.
Request: Remove OAuth as the login system and implement key signature validation instead.
linzheming tipped:
1.28 USD
1 year ago
linzheming replied:
Will do.
joshua replied:
Based AF.
linzheming replied:
What's "Based AF"?
marsface tipped:
0.01 USD
1 year ago
joshua replied:
linzheming tipped:
1.28 USD
1 year ago
slictionary tipped:
0.01 USD
1 year ago
linzheming replied:
New English learned.
slictionary replied:
BOOOOOOOO!! Joshua! @linzheming here: https://slictionary-fc2a0.web.app/testit/based/txid Might as well get your definitions here, we're paying you! "Pictures are worth 1,000 words"-- Fred Barnard
joshua replied:
Aw man. totally missed this. Guess 'I can do better'
slictionary replied:
LOL
4. UTXO management, manage your own UTXO for your app. That saves a lot.
slictionary tipped:
0.08 USD
1 year ago
slictionary replied:
Yes, this would be a DotWallet function, yes? Have a feature on@SLictionary which needs this.
linzheming replied:
This should be simple. if all your transaction go through our wallet/API we can index them.
3. An interface for application to apply for APPID and use the ID to get BIP32 pubkey/sig from m/APPID/anypath from the seed of the user.
joshua replied:
seems interesting.
建议尽快推出App,集成bsv导航、新闻、中国炮兵、快速买卖币,各应用APP等,打造成区块链的支付宝。
linzheming replied:
哈哈哈这个不在我路线图上。
2. Payment channel related API, the way miner deal with nLocktime and nSequence.
joshua replied:
Yes plz.
1. UTXO status query, check for the spent status of a particular UTXO.