Whatever the reason, this is the core protocol's job to deliver the basic "why" behind it all for the end user
4/12
For Step 2, people need an easy way to buy crypto.
Thankfully, in most places in the world, it's pretty easy to sign up for an exchange, go to an ATM, etc., and just buy a wide variety of cryptos.
Buying privately is another story, but still, you can get crypto.
5/12
For step 3, people need a way to get paid in crypto. Today this is either by working for a crypto company or using a service like @Bitwage or @coinbase's direct deposit service (or working for @rarepassenger)
Few services still but the demand is finally heating up on this.
6/12
And finally, after people have a reason for wanting crypto, after they are able to buy it, after they start getting paid in it, we have Step 3: people want to spend it. We're barely getting here now!
There's services like @IoniaPlatform that are coming up to make this easy
7/12
Note that this cycle repeats at different levels: some people want crypto and buy it, then are paid in it and spend it, and this increases the core value proposition, and a new pocket of society hits Step 1.
But we need to try to focus on the order of the steps!
8/12
The #BitcoinCash community largely jumped the gun and skipped to the last step. As a result, thousands of merchants have been onboarded, but almost no customers!
The #Bitcoin#LightningNetwork works a lot better than it used to, and most of the time these days payments go through.
But it will ALWAYS have far higher likelihood of failed payments than on-chain cryptos. Maxis who say "I've never had a problem" are likely lying!
π§΅time
1/8
Keeping it simple for brevity's sake: on networks without congestion, unless there's some bug or issue in the individual wallet implementation, your transaction will go through almost all the time.
Most common exception in my ~10 years of using crypto is connectivity issues
2/8
With Lightning, your payment can fail if the sender can't connect (just like on-chain), but ADDITIONALLY if:
-the RECIPIENT can't connect
-there's no payment route
-the payment is too large
-someone on the route can't connect or doesn't have enough liquidity
3/8
I'm a @FreeStateNH mover and libertarian, but I will NOT be voting for @jeremykauffman on Tuesday, or for any @LPNH candidates. The party has turned me from an easy, automatic "yes" voter on some races to "no" across the board, and I'll explain why below π
Neither A nor B is possible when voting for the LPNH this cycle. No candidate has a realistic chance of winning, and I don't like the message I would be sending with a vote of conscience.
2/8
Don't get me wrong: I like @jeremykauffman personally and respect (even admire) the work he's done with @LBRYcom and helping the @FreeStateNH gain exposure.
If he actually got elected I have no doubt his voting record would be stellar, and would improve liberty.
3/8
You can solve @Twitter's bot problem with one simple trick! No, this isn't clickbait, it's true. Just one new feature would make this super simple to solve.
First, you need crypto payments (fiat/dollars are too clunky and need to much verification). Twitter's "add tipping address" feature is a good start.
You just need a way to associate payments with tweets so people can see which post generated the tip. Why? Keep reading!
2/6
THE EASY TRICK:
Let users set a fee to comment on their tweets. That's it. Super simple!
Even at a sub-cent fee, those running bots will go broke spending all that money on extremely low-percentage scam links. They'll just stop doing it.
3/6