Better UX around depositing credits #13

New issue

Open

opened 2018-07-20 17:19:55 +02:00 by kauffj · 3 comments

kauffj commented

2018-07-20 17:19:55 +02:00

(Migrated from github.com)

As someone putting credits in to tip right away, it is confusing to know at what point they can be tipped.

It could be cool if the bot DM'ed/tweeted something like:

"Your deposit has been noticed by our bot. It will be spendable in approx 15 min (after 6 block confirmations)."
"Your deposit has been confirmed. Tip freely!"

As someone putting credits in to tip right away, it is confusing to know at what point they can be tipped. It could be cool if the bot DM'ed/tweeted something like: - "Your deposit has been noticed by our bot. It will be spendable in approx 15 min (after 6 block confirmations)." - "Your deposit has been confirmed. Tip freely!"

kauffj commented

2018-08-13 17:01:12 +02:00

(Migrated from github.com)

This just happened to me again today and was confusing / discouraging.

filipnyquist commented

2018-08-15 14:45:52 +02:00

(Migrated from github.com)

I'll take a look at how the best way of integrating this when I get home in a few hours, might be able to do this one in this sprint or next.

nikooo777 commented

2018-12-06 13:53:45 +01:00

(Migrated from github.com)

We should let users spend funds after 1 block as we're not talking about big amount of money.

This issue implies that the bot observes lbrycrd balances and constantly monitors changes. It's doable but needs better exploration as to how it would be achieved.

One quick (partial) solution is to better inform the user when they request the deposit address.

We should let users spend funds after 1 block as we're not talking about big amount of money. This issue implies that the bot observes lbrycrd balances and constantly monitors changes. It's doable but needs better exploration as to how it would be achieved. One quick (partial) solution is to better inform the user when they request the deposit address.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/twitter-tipbot#13

No description provided.