Does anyone have experience with throwing around tipping links from

Bitcoin.com or Paytaca? How do you effectively use it. Have you seen one claimed more often than the other?

We don't have a more universal way that more wallets could claim?

I would really like to start tipping people BCH again effectively.

@joemar_taganna could other wallets implement your scheme? It's trustless, right? I mean as in: you don't hold the funds, they are in a contract, so could be redeemed with other wallets or created by someone else?

I don't think what they use is entirely trustless. My suggestion is this: https://codeberg.org/Flowee/pay/issues/3

Someone tried to tip me a couple of weeks ago, even using the bitcoin com wallet I never actually received the funds. Not sure what went wrong, I kind of expect it just poofed in the ether. Or bcom has it now. No clue.

yes, it is trustless. it uses shamir secret sharing to split the private key into shards. 2 out of 3 shards is needed to reconstruct the private key, only one shard is saved on the backend server. 1 is embedded into the URL that is shared, and 1 is kept on the wallet app for recovery. if we want to make the claiming work with any wallet, we need to setup a shared server for saving the shards. we could also just open up our API for saving these shards and for claiming so it works with all wallets…if there is interest from other wallet devs.

we have no way to claim the gifts without the shared URLs as we only have one shard out of 3 for each gift. so it is “trustless”, unless you understand the term differently.

Hmm. I was thinking maybe it was solved with a contract (no server secret), just some secret in the shared URL would allow spending and after some timeout another secret would allow reclaiming. I clearly haven't thought this through.

the URL is given to you when the user claims, at that point your server has all the shards. Hence, not entirely trustless.

sorry, i gave the wrong info. the URL gives the hash of the shard. the server has the copy of this hash that maps to the corresponding complementary shard.

aha, relevant detail indeed. So the wallet downloads the serverside shard and does the work wallet-side?

yes

What I like about this direction is that I think it could allow us to write “bch cheques” for tipping- I keep wishing I could leave a paper note in the hotel room or for the bartender that says, “Thanks for your help! Have a good week. Here’s a tip in bitcoin cash. Just enter these 3 words at www.thanks.cash/fromJohn69/GRACIAS JULIA ONTARIOROCKS/“ before Julia checks it I must log/commit on my end those 3 words and an amount. But that’s it, there’s no further friction for me. Imho this is a fun easy least frictional way to tip. I don’t need my phone with me at that moment. Just a napkin. I can also just text the words. Not super secure but it’s not for large amounts. Even if there must be a central hackable db (in the interest of low friction) the risk is limited to merely the amount i tip and further by the validity window such as 72 hours. The greater downside to a central server is not the hack risk, but the risk that the maintainer goes AWOL and the mechanism breaks. We’ve already had at least half a dozen tipping services come and go. Security is not why they are gone. Imagine an onchain system that would just always work going forward. Folks could get used to that real fast(!)… not just for tipping but any payments. It’s p2p cash, but with a middle man, but the middle man is an onchain contract. After 500 blocks the amount is returned to giver. Maybe this architecture means that: - maybe the receiver doesn’t get word of successful collection until the following block. Thats fine! No one said tips must settle instantly (payments yes. Tips, not so vital). - maybe each individual brute force attempt on the contract (guessing the phrase) could cost as little as 1sat. That’s fine! Guess away. Welcome to try to grab my $8. All Transactions welcome. - maybe it’s not possible to auto-return to the giver. That’s fine! I’ll take responsibility for snatching back my tip using the phrase anytime I want. When you consider the “problems” of implementing a way to send bch using only a phrase (bare minimum friction Short Shared Secret acceptably vulnerable to mitm), then also consider that in exchange for this convenience people would be willing to sacrifice a bit of what we are not used to consider sacrificing- timeliness, security, etc. it’s ok. Karen and everyone in the world already understands shared secrets. They don’t need to be taught public key cryptography at the beginning. Hell maybe they’ll never learn it. Most coinbase traders never will. PKC not necessary unless you require L1 security. For throwing small payments around, who knows, short shared secrets might ironically blow up as the most common sending method like AOL continued to grow even after true Internet access could be had for less. Btc needs an “L2” for congestion. That is not the need of bch. Perhaps the bch L2 is for mass convenience (yes, in exchange for a little security, as is the rule). What other chain could implement something like this on-chain? Any? I think it’s a value proposition few other projects could offer.