WEBVTT

00:00:05.900 --> 00:00:08.460
Welcome to the Bitcoin Street Journal, Bitcoin

00:00:08.460 --> 00:00:11.060
Market Update podcast, your daily source for

00:00:11.060 --> 00:00:14.140
live updates on the Bitcoin market. Join us as

00:00:14.140 --> 00:00:16.660
we delve into current Bitcoin technical analysis,

00:00:17.239 --> 00:00:21.420
track Bitcoin, BTC prices, explore market capitalization

00:00:21.420 --> 00:00:24.559
trends, and analyze market supply. Stay ahead

00:00:24.559 --> 00:00:26.559
of the curve with our comprehensive coverage

00:00:26.559 --> 00:00:29.589
of the ever -evolving world of Bitcoin. In today's

00:00:29.589 --> 00:00:32.210
episode, we'll cover Bitcoiner protests, ECB,

00:00:32.229 --> 00:00:34.530
McDonald's acceptance of Bitcoin in Switzerland,

00:00:35.289 --> 00:00:38.909
corporations stacking SATs, SEC's delay of ARK

00:00:38.909 --> 00:00:42.369
Invest ETF, the launch of Custodia Bank, Max

00:00:42.369 --> 00:00:45.170
Kaiser's ongoing hodling, incentives for green

00:00:45.170 --> 00:00:48.130
Bitcoin mining in Texas, revocation of SBF's

00:00:48.130 --> 00:00:51.009
bail, a Bitcoin billboard in Japan, an academic

00:00:51.009 --> 00:00:53.149
study on Bitcoin mining's impact on renewable

00:00:53.149 --> 00:00:57.229
energy, a UK barbershop accepting Bitcoin, Bittrex's

00:00:57.229 --> 00:01:00.109
fine by SEC, Stark's prediction of no Bitcoin

00:01:00.109 --> 00:01:02.990
ETF approval, People's preference for USD over

00:01:02.990 --> 00:01:05.750
Bitcoin, Noster's struggle to onboard users,

00:01:06.290 --> 00:01:08.829
Bitcoin's all -time high in Argentina, price

00:01:08.829 --> 00:01:11.950
updates on Bitcoin and Shiba Inu, Kraken surpassing

00:01:11.950 --> 00:01:14.530
Coinbase in liquidity, and Coinbase's base ranking

00:01:14.530 --> 00:01:17.689
fourth in daily TPS. We will also discuss topics

00:01:17.689 --> 00:01:20.409
such as the analysis of Worldcoin's data processing

00:01:20.409 --> 00:01:24.599
and risks, a crypto exchange fined by SEC, SEC's

00:01:24.599 --> 00:01:27.340
role in crypto vulnerabilities, Ethereum and

00:01:27.340 --> 00:01:30.859
XRP updates, Visa's testing of Ethereum payments,

00:01:31.480 --> 00:01:34.079
various AI -related discussions, cryptocurrency

00:01:34.079 --> 00:01:37.019
news, and the Nostr protocol for decentralized

00:01:37.019 --> 00:01:40.299
publishing, along with its features and implementations.

00:01:43.799 --> 00:01:45.719
Hey there, Bitcoiners. We've got some exciting

00:01:45.719 --> 00:01:47.739
news and updates in the world of cryptocurrency.

00:01:48.299 --> 00:01:51.819
Let's dive right in. First up, we have a Bitcoiner

00:01:51.819 --> 00:01:53.799
who has started a personal protest in front of

00:01:53.799 --> 00:01:57.060
the European Central Bank, ECB. Talk about taking

00:01:57.060 --> 00:01:59.879
a stand. It's great to see individuals advocating

00:01:59.879 --> 00:02:02.439
for their beliefs. And speaking of using Bitcoin

00:02:02.439 --> 00:02:05.159
in everyday life, did you know that you can now

00:02:05.159 --> 00:02:07.959
pay at McDonald's with Bitcoin in Lugano, Switzerland?

00:02:08.400 --> 00:02:10.919
It's amazing to see the adoption of cryptocurrencies

00:02:10.919 --> 00:02:13.979
by big corporations. But it's not just corporations

00:02:13.979 --> 00:02:16.900
getting involved. Investors like Paul Tudor Jones

00:02:16.900 --> 00:02:19.889
are also recognizing the value of Bitcoin. It's

00:02:19.889 --> 00:02:22.169
always interesting to see renowned figures embracing

00:02:22.169 --> 00:02:25.009
the world of cryptocurrency. Now let's talk about

00:02:25.009 --> 00:02:27.930
some regulatory news. The Securities and Exchange

00:02:27.930 --> 00:02:31.490
Commission, SEC, has once again delayed the application

00:02:31.490 --> 00:02:35.370
for ARK Invest's SpotBitcoin ETF. It seems like

00:02:35.370 --> 00:02:37.810
they can't buy time forever, but we'll have to

00:02:37.810 --> 00:02:40.090
wait and see what the future holds for this ETF.

00:02:40.610 --> 00:02:43.030
On the other hand, we have some positive news.

00:02:43.389 --> 00:02:45.750
After a long battle with regulators, Caitlin

00:02:45.750 --> 00:02:48.550
Long's Custodia Bank is finally live. It's a

00:02:48.550 --> 00:02:50.490
great step forward for the industry and shows

00:02:50.490 --> 00:02:54.270
that perseverance pays off. Max Kaiser, one of

00:02:54.270 --> 00:02:57.009
the early Bitcoin enthusiasts, called Bitcoin

00:02:57.009 --> 00:03:00.150
the currency of the resistance back in 2011.

00:03:00.650 --> 00:03:03.090
And over 12 years later, he's still holding strong.

00:03:04.250 --> 00:03:06.650
It's inspiring to see the belief and dedication

00:03:06.650 --> 00:03:09.610
that some individuals have for this digital currency.

00:03:10.110 --> 00:03:12.909
In terms of environmental impact, Texas is set

00:03:12.909 --> 00:03:15.310
to approve new incentives for cutting greenhouse

00:03:15.310 --> 00:03:18.379
gas emissions from flared and vented gas. This

00:03:18.379 --> 00:03:21.139
includes offering a tax exemption to energy producers

00:03:21.139 --> 00:03:23.639
using fugitive emissions to power Bitcoin mining.

00:03:24.240 --> 00:03:26.240
It's great to see efforts being made to reduce

00:03:26.240 --> 00:03:28.879
the carbon footprint of Bitcoin mining. But not

00:03:28.879 --> 00:03:31.800
all news is positive. SBF's bail has been revoked

00:03:31.800 --> 00:03:34.199
and he is headed to jail. It's a reminder that

00:03:34.199 --> 00:03:36.219
we should always stay informed and study the

00:03:36.219 --> 00:03:38.879
world of Bitcoin to make sound investment decisions.

00:03:39.719 --> 00:03:42.680
Now let's shift our focus to technology. A Bitcoin

00:03:42.680 --> 00:03:45.400
billboard has been spotted in Tokyo, Japan. It's

00:03:45.400 --> 00:03:47.300
always good to remember the networks that make

00:03:47.300 --> 00:03:50.919
Bitcoin grow. This leads us to a comparison between

00:03:50.919 --> 00:03:52.879
the Lightning Network and the Liquid Network.

00:03:53.419 --> 00:03:56.280
Both have their unique features and play a crucial

00:03:56.280 --> 00:03:59.680
role in the Bitcoin ecosystem. In the academic

00:03:59.680 --> 00:04:02.180
world, a new peer -reviewed study has found that

00:04:02.180 --> 00:04:04.740
Bitcoin's proof -of -work mining can contribute

00:04:04.740 --> 00:04:08.060
to renewable energy penetration and the decarbonization

00:04:08.060 --> 00:04:10.629
of the energy grid. This is an area that hasn't

00:04:10.629 --> 00:04:12.990
been comprehensively examined, so it's great

00:04:12.990 --> 00:04:14.870
to see research shedding light on this topic.

00:04:15.449 --> 00:04:17.509
Turning our attention back to regulatory matters,

00:04:18.069 --> 00:04:20.629
the SEC has delayed the decision on Cathie Wood's

00:04:20.629 --> 00:04:24.029
spot Bitcoin ETF. The next decision date is set

00:04:24.029 --> 00:04:26.709
for November 11th. We'll be eagerly awaiting

00:04:26.709 --> 00:04:29.089
the outcome of this decision. Now let's talk

00:04:29.089 --> 00:04:32.050
about adoption. A barbershop in the UK is now

00:04:32.050 --> 00:04:34.629
accepting Bitcoin. It's small steps like these

00:04:34.629 --> 00:04:36.410
that contribute to the mainstream acceptance

00:04:36.410 --> 00:04:39.129
and use of cryptocurrencies. In a throwback to

00:04:39.129 --> 00:04:41.850
the past, Andreas M Antonopoulos once talked

00:04:41.850 --> 00:04:44.689
about software owning money. He was truly ahead

00:04:44.689 --> 00:04:47.810
of his time, recognizing the revolutionary potential

00:04:47.810 --> 00:04:51.170
of decentralized currencies. And here's a thought

00:04:51.170 --> 00:04:53.850
-provoking point. People are waking up to the

00:04:53.850 --> 00:04:56.370
fact that Bitcoin is actually good for the environment.

00:04:56.889 --> 00:04:59.350
It's not just about profits. It's about making

00:04:59.350 --> 00:05:02.959
a positive impact on the world. Speaking of impact,

00:05:03.439 --> 00:05:06.120
Bitcoin miners have been selling 75 % of their

00:05:06.120 --> 00:05:10.120
reserves in June compared to 326 % in the same

00:05:10.120 --> 00:05:13.079
period last year. It's interesting to see different

00:05:13.079 --> 00:05:15.480
strategies among miners and who's holding on

00:05:15.480 --> 00:05:18.000
to their Bitcoin. Now, let's touch on a legal

00:05:18.000 --> 00:05:21.240
matter. Bittrex lost against the SEC, agreeing

00:05:21.240 --> 00:05:24.379
to pay a $24 million fine for offering US users

00:05:24.379 --> 00:05:27.319
access to unregistered securities. It's a reminder

00:05:27.319 --> 00:05:29.920
that regulations are an important factor to consider

00:05:29.920 --> 00:05:33.199
in the cryptocurrency space. If you've ever wondered

00:05:33.199 --> 00:05:35.540
why holding your wealth in Bitcoin is important,

00:05:36.019 --> 00:05:38.439
just take a look at the world around us. It provides

00:05:38.439 --> 00:05:41.579
a decentralized and secure alternative to traditional

00:05:41.579 --> 00:05:45.060
financial systems. Unfortunately, not everyone

00:05:45.060 --> 00:05:47.620
shares this viewpoint. According to John Reed

00:05:47.620 --> 00:05:50.660
Stark, a former SEC's Office of Internet Enforcement

00:05:50.660 --> 00:05:53.620
Chief, the SEC will not approve a spot Bitcoin

00:05:53.620 --> 00:05:57.180
ETF. But let's not lose hope. History has a habit

00:05:57.180 --> 00:06:00.500
of proving skeptics wrong. And here's an interesting

00:06:00.500 --> 00:06:04.019
observation. People would rather have $100 USD

00:06:04.019 --> 00:06:07.379
than one full Bitcoin. It just goes to show that

00:06:07.379 --> 00:06:09.779
we are still in the early stages of widespread

00:06:09.779 --> 00:06:12.439
Bitcoin adoption. Meanwhile, a decentralized

00:06:12.439 --> 00:06:14.879
social media protocol is struggling to onboard

00:06:14.879 --> 00:06:17.860
new users. It's a reminder that despite the growing

00:06:17.860 --> 00:06:20.560
popularity of cryptocurrencies, there are still

00:06:20.560 --> 00:06:23.449
challenges to overcome in various sectors. In

00:06:23.449 --> 00:06:25.589
international news, Bitcoin is setting a new

00:06:25.589 --> 00:06:28.550
all -time high against the Argentine peso. This

00:06:28.550 --> 00:06:30.750
comes at a time of primary elections in Argentina,

00:06:31.209 --> 00:06:33.350
highlighting the role of Bitcoin as a hedge against

00:06:33.350 --> 00:06:36.250
traditional currencies. Now let's shift gears

00:06:36.250 --> 00:06:38.189
and have a quick recap of the crypto market.

00:06:39.389 --> 00:06:42.410
Bitcoin had a slight dip, returning to $1 .29k

00:06:42.410 --> 00:06:45.529
after failing to break $1 .30k. On the other

00:06:45.529 --> 00:06:49.110
hand, Shiba Inu experienced a pump of 16 % in

00:06:49.110 --> 00:06:51.629
just seven days. The market is always full of

00:06:51.629 --> 00:06:55.050
surprises. In the altcoin space, RollBitcoin,

00:06:55.170 --> 00:06:59.449
RLB, has seen a massive 76 % weekly surge, securing

00:06:59.449 --> 00:07:02.990
a place among the top 100 altcoins. It's a reminder

00:07:02.990 --> 00:07:05.269
of the potential for growth and the ever -changing

00:07:05.269 --> 00:07:07.949
landscape of the cryptocurrency market. Moving

00:07:07.949 --> 00:07:10.750
on, we have Evernote's Evers AirDrop for XRP

00:07:10.750 --> 00:07:13.529
holders. The decentralized platform plans to

00:07:13.529 --> 00:07:19.449
distribute 5 ,160 ,960 Evers to eligible XRP

00:07:19.449 --> 00:07:22.500
holders. providing an opportunity for those involved

00:07:22.500 --> 00:07:26.720
in the XRP community. In July, Kraken dethroned

00:07:26.720 --> 00:07:29.680
Coinbase as the most liquid U .S. exchange for

00:07:29.680 --> 00:07:32.660
altcoins. This shift in market share could be

00:07:32.660 --> 00:07:34.959
attributed to Coinbase facing some regulatory

00:07:34.959 --> 00:07:37.879
challenges in recent months. And speaking of

00:07:37.879 --> 00:07:40.620
Coinbase, their base platform reached the fourth

00:07:40.620 --> 00:07:44.180
rank in daily TPS, transactions per second, among

00:07:44.180 --> 00:07:47.079
layer two solutions. It gained an impressive

00:07:47.079 --> 00:07:51.439
136 ,000 daily active users just two days after

00:07:51.439 --> 00:07:54.439
its public release. It's great to see the adoption

00:07:54.439 --> 00:07:56.819
and usage of new platforms in the crypto space.

00:07:57.300 --> 00:07:59.199
And that's it for this edition of our cryptocurrency

00:07:59.199 --> 00:08:01.800
news roundup. Stay tuned for more updates and

00:08:01.800 --> 00:08:03.620
remember to always stay informed and be part

00:08:03.620 --> 00:08:06.339
of this exciting world of cryptocurrencies. See

00:08:06.339 --> 00:08:16.170
you next time. Let's dive into some interesting

00:08:16.170 --> 00:08:18.750
news in the cryptocurrency world. First up, we

00:08:18.750 --> 00:08:21.110
have the AAIP, which stands for the Argentina

00:08:21.110 --> 00:08:24.290
Agency of Personal Information Protection. They

00:08:24.290 --> 00:08:26.189
recently announced that they will be closely

00:08:26.189 --> 00:08:28.629
examining how WorldCoin handles personal data

00:08:28.629 --> 00:08:31.149
and whether there are any potential risks for

00:08:31.149 --> 00:08:34.250
Argentines. It's great to see organizations taking

00:08:34.250 --> 00:08:37.090
data privacy seriously and ensuring the safety

00:08:37.090 --> 00:08:40.429
of individuals' information. In other news, A

00:08:40.429 --> 00:08:42.649
crypto exchange that has been facing numerous

00:08:42.649 --> 00:08:46.149
challenges recently has agreed to pay a hefty

00:08:46.149 --> 00:08:50.850
$24 million penalty to settle with the SEC. This

00:08:50.850 --> 00:08:53.289
exchange had actually filed for bankruptcy protection

00:08:53.289 --> 00:08:55.889
earlier this year, so this settlement is seen

00:08:55.889 --> 00:08:58.789
as a positive outcome for them. Co -founder William

00:08:58.789 --> 00:09:00.909
Shahara expressed his satisfaction with this

00:09:00.909 --> 00:09:05.269
resolution. Moving on, the SEC has delayed the

00:09:05.269 --> 00:09:08.559
approval of ARK's revised Bitcoin ETF. They want

00:09:08.559 --> 00:09:10.539
to hear the public's opinion on using Coinbase

00:09:10.539 --> 00:09:12.700
as a partner for surveillance and information

00:09:12.700 --> 00:09:15.919
sharing. This delay shows that regulatory bodies

00:09:15.919 --> 00:09:18.440
are being cautious and seeking input from various

00:09:18.440 --> 00:09:21.399
stakeholders before making significant decisions.

00:09:22.059 --> 00:09:24.220
Here's an interesting move by an e -gaming company

00:09:24.220 --> 00:09:27.659
called Boya. They have set aside $5 million to

00:09:27.659 --> 00:09:30.500
purchase Bitcoin and Ether. The company believes

00:09:30.500 --> 00:09:33.200
that investing in these cryptocurrencies aligns

00:09:33.200 --> 00:09:35.639
with their interests and the interests of their

00:09:35.639 --> 00:09:38.759
shareholders. It's clear that more and more companies

00:09:38.759 --> 00:09:41.440
are recognizing the potential of digital assets

00:09:41.440 --> 00:09:43.940
and incorporating them into their investment

00:09:43.940 --> 00:09:47.360
strategies. In unfortunate news, the founder

00:09:47.360 --> 00:09:51.039
of the popular crypto exchange FTX, Sam Bankman

00:09:51.039 --> 00:09:53.940
Freed, has been sent to jail for witness tampering.

00:09:54.539 --> 00:09:56.600
He could potentially spend at least two months

00:09:56.600 --> 00:09:59.679
behind bars before his trial. It's a reminder

00:09:59.679 --> 00:10:02.039
that engaging in illegal activities within the

00:10:02.039 --> 00:10:04.820
crypto industry can lead to serious consequences.

00:10:05.259 --> 00:10:07.460
Let's shift our attention to some recent market

00:10:07.460 --> 00:10:11.419
trends. Echeb, Ape, and Pepe have all experienced

00:10:11.419 --> 00:10:15.200
an impressive 8 % daily jump, while Bitcoin has

00:10:15.200 --> 00:10:18.600
managed to maintain a price of around $29 ,000.

00:10:19.440 --> 00:10:22.179
Moreover, SHIB's momentum seems to be on the

00:10:22.179 --> 00:10:25.460
rise, and another asset from the Shiba Inu ecosystem

00:10:25.460 --> 00:10:28.620
called BONE is also performing well. These market

00:10:28.620 --> 00:10:30.960
movements demonstrate the dynamic nature of the

00:10:30.960 --> 00:10:34.039
cryptocurrency space. In a recent investigation,

00:10:34.250 --> 00:10:36.370
Nansen looked into what whales are investing

00:10:36.370 --> 00:10:39.370
in on Coinbase's base network. It was discovered

00:10:39.370 --> 00:10:41.750
that early adopters of this network had a significant

00:10:41.750 --> 00:10:44.529
allocation to meme coins, which are cryptocurrencies

00:10:44.529 --> 00:10:47.870
known for their viral and fun nature. This finding

00:10:47.870 --> 00:10:50.269
showcases the diverse investment strategies within

00:10:50.269 --> 00:10:53.610
the crypto community. Visa, a major financial

00:10:53.610 --> 00:10:56.330
technology company, is piloting an innovative

00:10:56.330 --> 00:10:59.029
approach to paying on -chain gas fees with a

00:10:59.029 --> 00:11:02.350
Visa card. This solution aims to eliminate the

00:11:02.350 --> 00:11:04.769
need for individuals to hold Ether solely for

00:11:04.769 --> 00:11:07.570
the purpose of paying these fees. It's exciting

00:11:07.570 --> 00:11:10.029
to see traditional financial institutions exploring

00:11:10.029 --> 00:11:13.009
ways to leverage blockchain technology and improve

00:11:13.009 --> 00:11:16.090
user experiences. Now let's talk about Ethereum.

00:11:16.830 --> 00:11:19.110
The prices of this popular cryptocurrency have

00:11:19.110 --> 00:11:21.250
remained relatively stagnant for the past five

00:11:21.250 --> 00:11:24.149
months, with trading volume and volatility decreasing.

00:11:25.080 --> 00:11:27.919
However, there are 10 bullish fundamentals that

00:11:27.919 --> 00:11:30.720
could potentially have a positive impact on Ethereum's

00:11:30.720 --> 00:11:33.059
price in the future. It's worth keeping an eye

00:11:33.059 --> 00:11:35.679
on these factors to see how they ultimately influence

00:11:35.679 --> 00:11:38.899
the market. Bakit, a company specializing in

00:11:38.899 --> 00:11:42.200
digital asset custody solutions, has been experiencing

00:11:42.200 --> 00:11:45.759
a surge in client interest. They recently revealed

00:11:45.759 --> 00:11:48.740
that they've signed new custody clients and are

00:11:48.740 --> 00:11:51.639
in late -stage negotiations with several prospective

00:11:51.639 --> 00:11:54.639
clients across various industries. It's a clear

00:11:54.639 --> 00:11:57.519
sign that institutional adoption of cryptocurrencies

00:11:57.519 --> 00:12:01.100
is continuing to grow. In Russia, there seems

00:12:01.100 --> 00:12:03.299
to be some skepticism surrounding the digital

00:12:03.299 --> 00:12:06.320
ruble. A survey revealed that one -third of Russians

00:12:06.320 --> 00:12:08.899
perceive the digital ruble as some sort of fraud.

00:12:09.539 --> 00:12:11.919
Additionally, one in five participants stated

00:12:11.919 --> 00:12:14.279
that they have no interest in Russia's upcoming

00:12:14.279 --> 00:12:18.259
central bank digital currency, CBDC. This highlights

00:12:18.259 --> 00:12:21.019
the challenges that CBDCs face in gaining public

00:12:21.019 --> 00:12:24.070
trust and acceptance. let's move on to some notable

00:12:24.070 --> 00:12:26.970
price movements in the market. Thorchain's native

00:12:26.970 --> 00:12:30.210
token, Rune, has experienced a significant 20

00:12:30.210 --> 00:12:33.490
% surge in just one day, while Bitcoin has remained

00:12:33.490 --> 00:12:37.549
relatively stable around $29 ,000. Another altcoin,

00:12:37.809 --> 00:12:40.610
Toncoin, has also seen substantial gains among

00:12:40.610 --> 00:12:43.649
larger cap cryptocurrencies. These price movements

00:12:43.649 --> 00:12:46.250
indicate the dynamic nature of the crypto market,

00:12:46.690 --> 00:12:48.809
where opportunities for both short -term and

00:12:48.809 --> 00:12:51.799
long -term gains can arise. Interesting news

00:12:51.799 --> 00:12:54.279
comes from the former US President Donald Trump,

00:12:54.700 --> 00:12:58.440
who reportedly holds between $250 ,000 and $500

00:12:58.440 --> 00:13:02.100
,000 worth of Ethereum. However, despite his

00:13:02.100 --> 00:13:04.899
personal investment, Trump remains a vocal opponent

00:13:04.899 --> 00:13:07.600
of the crypto industry. It's intriguing to see

00:13:07.600 --> 00:13:09.940
such high -profile individuals involved in the

00:13:09.940 --> 00:13:12.500
crypto space despite their reservations about

00:13:12.500 --> 00:13:16.679
its overall impact. BitMEX, a popular cryptocurrency

00:13:16.679 --> 00:13:19.820
exchange, has released an analysis on the potential

00:13:19.820 --> 00:13:23.139
of drive chains for scaling Bitcoin. Drive chains

00:13:23.139 --> 00:13:25.740
could unlock new exciting applications for Bitcoin,

00:13:26.120 --> 00:13:28.820
but they also introduce added complexities and

00:13:28.820 --> 00:13:31.759
potential vulnerabilities. It's encouraging to

00:13:31.759 --> 00:13:34.740
see ongoing efforts to optimize Bitcoin's capabilities

00:13:34.740 --> 00:13:37.860
and scalability. In recent bankruptcy procedures,

00:13:38.379 --> 00:13:41.389
Voyager, a crypto trading platform, reportedly

00:13:41.389 --> 00:13:44.710
transferred $5 .5 million worth of Ethereum and

00:13:44.710 --> 00:13:48.230
SHIB to Coinbase. This move comes after Voyager

00:13:48.230 --> 00:13:50.870
set a deadline for its users to withdraw a specific

00:13:50.870 --> 00:13:52.990
portion of their tokens held on the platform.

00:13:53.570 --> 00:13:55.929
It's important for platforms to navigate bankruptcy

00:13:55.929 --> 00:13:59.090
procedures carefully to ensure the security and

00:13:59.090 --> 00:14:02.190
transparency of users' assets. Unfortunately,

00:14:02.429 --> 00:14:04.529
there have been instances of fraudulent activities

00:14:04.529 --> 00:14:07.909
in the crypto world for individuals, along with

00:14:07.909 --> 00:14:10.500
their unincorporated entity, have been charged

00:14:10.500 --> 00:14:12.799
with defrauding investors through a crypto and

00:14:12.799 --> 00:14:15.480
precious metal scam. They promised investors

00:14:15.480 --> 00:14:18.419
exceptionally high returns, highlighting the

00:14:18.419 --> 00:14:20.759
importance of conducting thorough research and

00:14:20.759 --> 00:14:23.740
due diligence before engaging in any investment

00:14:23.740 --> 00:14:26.720
opportunities. On a more positive note, the Singapore

00:14:26.720 --> 00:14:29.879
Red Cross has enabled crypto donations. Initially,

00:14:30.120 --> 00:14:32.120
they will be accepting digital assets such as

00:14:32.120 --> 00:14:37.029
Bitcoin, Ethereum, USDT, and USDC. It's great

00:14:37.029 --> 00:14:39.669
to see charitable organizations embracing cryptocurrencies

00:14:39.669 --> 00:14:41.990
as a means of receiving donations and supporting

00:14:41.990 --> 00:14:45.269
their initiatives. Let's talk about Riot, a company

00:14:45.269 --> 00:14:48.110
deeply involved in Bitcoin mining. In the second

00:14:48.110 --> 00:14:50.549
quarter, they successfully mined a substantial

00:14:50.549 --> 00:14:55.330
amount of BTC. Riot's CEO, Les, expressed his

00:14:55.330 --> 00:14:57.389
excitement about the company's role in transforming

00:14:57.389 --> 00:14:59.769
the energy and financial industries through Bitcoin

00:14:59.769 --> 00:15:02.529
mining. It's a testament to the growing influence

00:15:02.529 --> 00:15:05.960
of crypto mining operations. Coinbase, a leading

00:15:05.960 --> 00:15:08.360
crypto exchange, has acknowledged that there

00:15:08.360 --> 00:15:10.639
are problems with the user experience on its

00:15:10.639 --> 00:15:14.720
platform. The CEO, Brian Armstrong, has recognized

00:15:14.720 --> 00:15:17.299
the need for improvements and is working towards

00:15:17.299 --> 00:15:20.600
enhancing the user interface and overall functionality.

00:15:21.639 --> 00:15:24.259
It's essential for platforms to prioritize user

00:15:24.259 --> 00:15:27.379
-centric design to ensure seamless and satisfactory

00:15:27.379 --> 00:15:30.639
experiences for their customers. Unfortunately,

00:15:31.179 --> 00:15:33.460
there have been instances of protocol exploitation

00:15:33.460 --> 00:15:36.779
in the crypto space. Zunami Protocol recently

00:15:36.779 --> 00:15:39.299
fell victim to an attack, resulting in a loss

00:15:39.299 --> 00:15:42.600
of over $2 million. This attack specifically

00:15:42.600 --> 00:15:45.639
targeted the platform's lending pools. It highlights

00:15:45.639 --> 00:15:48.519
the importance of robust security measures and

00:15:48.519 --> 00:15:51.460
continuous monitoring to mitigate potential risks

00:15:51.460 --> 00:15:54.659
within the ecosystem. In terms of market trends,

00:15:55.059 --> 00:15:57.460
an indicator is suggesting a significant price

00:15:57.460 --> 00:16:00.110
movement ahead for Bitcoin. While many other

00:16:00.110 --> 00:16:02.769
cryptocurrencies remain relatively stable, a

00:16:02.769 --> 00:16:06.450
particular token called HBR has experienced substantial

00:16:06.450 --> 00:16:09.490
price surges in the double digits. This volatility

00:16:09.490 --> 00:16:12.429
and potential for major price movements are inherent

00:16:12.429 --> 00:16:15.070
to the crypto market, presenting opportunities

00:16:15.070 --> 00:16:19.409
for both traders and investors. Lastly, an opinion

00:16:19.409 --> 00:16:22.429
piece argues that the SEC's regulatory actions

00:16:22.429 --> 00:16:25.710
are contributing to the rising incidence of crypto

00:16:25.710 --> 00:16:28.480
-related cybercrime. The author highlights the

00:16:28.480 --> 00:16:31.639
idea of moral hazard and suggests that the stringent

00:16:31.639 --> 00:16:35.340
regulations put forth by the SEC may unintentionally

00:16:35.340 --> 00:16:38.259
encourage malicious actors to find alternative

00:16:38.259 --> 00:16:40.980
methods to exploit vulnerabilities within the

00:16:40.980 --> 00:16:43.679
crypto industry. It's crucial for regulatory

00:16:43.679 --> 00:16:45.860
bodies to strike a balance between protecting

00:16:45.860 --> 00:16:49.100
investors and fostering innovation. And that's

00:16:49.100 --> 00:16:52.139
a wrap for today's cryptocurrency news. Stay

00:16:52.139 --> 00:16:54.559
tuned for more updates on the exciting world

00:16:54.559 --> 00:17:01.009
of digital assets. Could the SEC unintentionally

00:17:01.009 --> 00:17:02.850
contribute to the increasing vulnerabilities

00:17:02.850 --> 00:17:05.450
faced by crypto companies? That's a question

00:17:05.450 --> 00:17:08.509
worth exploring. Let's start by analyzing the

00:17:08.509 --> 00:17:12.210
recent price action of Ripple, XRP. The cryptocurrency

00:17:12.210 --> 00:17:14.390
has been going through an extended correction

00:17:14.390 --> 00:17:17.369
phase, mainly because it encountered significant

00:17:17.369 --> 00:17:21.069
resistance at the 85 cents level. However, there

00:17:21.069 --> 00:17:23.529
might be a potential for a short -term interruption

00:17:23.529 --> 00:17:27.109
in the downtrend as the price approaches a robust

00:17:27.109 --> 00:17:30.299
support region. This analysis is provided by

00:17:30.299 --> 00:17:32.819
Cheyenne, who carefully examined the daily chart

00:17:32.819 --> 00:17:35.220
of Ripple. It's interesting to see how the price

00:17:35.220 --> 00:17:38.099
of XRP reacts to these resistance and support

00:17:38.099 --> 00:17:41.680
levels. Moving on to Ethereum, we observe that

00:17:41.680 --> 00:17:44.119
its price has been stuck in a state of indecision

00:17:44.119 --> 00:17:47.039
between buyers and sellers. This has resulted

00:17:47.039 --> 00:17:50.319
in shallow candle formations and a steady consolidation

00:17:50.319 --> 00:17:53.720
period over the past few months. However, Ethereum

00:17:53.720 --> 00:17:56.619
faces a crucial price region that could potentially

00:17:56.619 --> 00:17:59.220
determine its short -term trajectory, according

00:17:59.220 --> 00:18:02.059
to Cheyenne's technical analysis. It would be

00:18:02.059 --> 00:18:04.140
interesting to see how Ethereum breaks out of

00:18:04.140 --> 00:18:06.619
this consolidation phase and whether it will

00:18:06.619 --> 00:18:09.619
lead to an explosive move. Shifting our attention

00:18:09.619 --> 00:18:11.920
to specific factors to watch for the week in

00:18:11.920 --> 00:18:14.660
relation to Ripple's price, volatility seems

00:18:14.660 --> 00:18:18.240
to be on the horizon. Ripple's XRP might be gearing

00:18:18.240 --> 00:18:20.539
up for some action, and there are two important

00:18:20.539 --> 00:18:23.200
things worth keeping an eye on. It's always intriguing

00:18:23.200 --> 00:18:26.259
to see how these anticipated events unfold and

00:18:26.259 --> 00:18:28.279
their impact on the price of cryptocurrencies.

00:18:29.000 --> 00:18:31.079
Now let's shift our focus to Pepe, which has

00:18:31.079 --> 00:18:33.660
been breaking resistance levels one after another.

00:18:34.200 --> 00:18:36.680
This MimaCoins rally continued on Monday, and

00:18:36.680 --> 00:18:39.259
it surpassed the previous resistance level, turning

00:18:39.259 --> 00:18:42.400
it into a crucial support level. Such price movements

00:18:42.400 --> 00:18:44.460
can be bullish and might indicate a potential

00:18:44.460 --> 00:18:47.079
for further price increases. The support and

00:18:47.079 --> 00:18:49.539
resistance levels identified for Pepe provide

00:18:49.539 --> 00:18:52.000
a helpful framework for understanding its potential

00:18:52.000 --> 00:18:55.599
price movements. In other news, Visa, a global

00:18:55.599 --> 00:18:58.599
payment technology giant, has successfully conducted

00:18:58.599 --> 00:19:01.539
a test that allows users to pay Ethereum gas

00:19:01.539 --> 00:19:04.460
fees using credit or debit cards. This development

00:19:04.460 --> 00:19:07.500
could have significant implications for the usability

00:19:07.500 --> 00:19:10.480
and accessibility of Ethereum and its ecosystem.

00:19:11.380 --> 00:19:15.039
Crypto card games are also making waves. Parallel's

00:19:15.039 --> 00:19:17.299
closed beta has caught the attention of Decrypt's

00:19:17.299 --> 00:19:19.680
Kate Irwin, who went hands -on with the game

00:19:19.680 --> 00:19:21.920
to explore its features and what distinguishes

00:19:21.920 --> 00:19:24.380
it from other card battlers in the crypto space.

00:19:25.299 --> 00:19:27.500
It's always fascinating to see how blockchain

00:19:27.500 --> 00:19:30.380
technology and gaming intersect to create new

00:19:30.380 --> 00:19:33.779
and innovative experiences. Now let's turn to

00:19:33.779 --> 00:19:36.940
the SEC's role in the crypto space. The regulatory

00:19:36.940 --> 00:19:39.480
body has once again delayed its decision on the

00:19:39.480 --> 00:19:43.460
Rx21 shares Bitcoin ETF application. As more

00:19:43.460 --> 00:19:46.799
attention is focused on Bitcoin ETFs, the SEC's

00:19:46.799 --> 00:19:49.140
actions and decisions have a significant impact

00:19:49.140 --> 00:19:51.859
on the market. It's worth keeping an eye on how

00:19:51.859 --> 00:19:54.660
these regulatory developments unfold and their

00:19:54.660 --> 00:19:57.240
implications for the wider crypto ecosystem.

00:19:58.119 --> 00:20:00.779
Moving on to AI, musician Nick Cave has expressed

00:20:00.779 --> 00:20:03.420
his concerns about the use of artificial intelligence

00:20:03.420 --> 00:20:07.259
in the creative process. He argues that AI commodifies

00:20:07.259 --> 00:20:09.500
the human spirit and overlooks the struggles

00:20:09.500 --> 00:20:12.740
inherent in true creativity. It's an interesting

00:20:12.740 --> 00:20:15.259
perspective on the potential pitfalls of AI in

00:20:15.259 --> 00:20:18.359
the artistic realm. Staying on the topic of AI,

00:20:18.839 --> 00:20:22.240
ChatGPT, an AI chatbot created by OpenAI has

00:20:22.240 --> 00:20:25.359
elicited mixed responses. While it seems to excel

00:20:25.359 --> 00:20:27.839
in writing prescriptions, its ability to write

00:20:27.839 --> 00:20:30.829
code appears to be less accurate. Two research

00:20:30.829 --> 00:20:33.529
papers have evaluated chat GPT's accuracy in

00:20:33.529 --> 00:20:36.430
these domains, and their findings provide valuable

00:20:36.430 --> 00:20:38.730
insights into the strengths and limitations of

00:20:38.730 --> 00:20:42.710
AI chatbots. In the tech world, an exciting development

00:20:42.710 --> 00:20:45.470
is underway as Elon Musk and Mark Zuckerberg

00:20:45.470 --> 00:20:49.410
prepare for a clash. Musk suggests that the confrontation

00:20:49.410 --> 00:20:51.490
between the tech titans will be live -streamed

00:20:51.490 --> 00:20:54.329
via Twitter or Meta, promising an epic battle

00:20:54.329 --> 00:20:57.769
in an iconic location in Italy. The anticipation

00:20:57.769 --> 00:21:00.400
around this clash is high, and its outcome could

00:21:00.400 --> 00:21:02.500
potentially have wide -ranging implications.

00:21:03.380 --> 00:21:05.920
In gaming news, a new Grand Theft Auto V mod

00:21:05.920 --> 00:21:08.779
introduces AI -controlled NPCs that have their

00:21:08.779 --> 00:21:11.420
own minds, with some even hurling insults at

00:21:11.420 --> 00:21:14.119
players. This demonstrates the potential of AI

00:21:14.119 --> 00:21:16.880
to enhance gaming experiences and create more

00:21:16.880 --> 00:21:20.339
immersive virtual worlds. Finally, in the cryptocurrency

00:21:20.339 --> 00:21:24.920
industry, FTX CEO Sam Bankman Freed's bail has

00:21:24.920 --> 00:21:27.700
been revoked due to allegations of witness tampering.

00:21:28.029 --> 00:21:30.690
This development raises questions about the implications

00:21:30.690 --> 00:21:33.069
for the future of the prominent crypto exchange

00:21:33.069 --> 00:21:35.829
and the potential legal consequences for its

00:21:35.829 --> 00:21:39.789
founder. Overall, these recent developments and

00:21:39.789 --> 00:21:43.750
events in the crypto, AI, gaming, and regulatory

00:21:43.750 --> 00:21:47.029
landscapes shape the dynamic ecosystem we find

00:21:47.029 --> 00:21:49.970
ourselves in. As more milestones are reached

00:21:49.970 --> 00:21:52.549
and challenges arise, it's crucial to stay informed

00:21:52.549 --> 00:21:54.829
and engaged with these fascinating developments.

00:22:01.980 --> 00:22:04.539
Hey there! Let's dive into the latest news and

00:22:04.539 --> 00:22:06.900
hot topics in the world of technology, finance,

00:22:07.059 --> 00:22:09.559
and pop culture. Brace yourself for an exciting

00:22:09.559 --> 00:22:12.759
ride. First up, we have some juicy details about

00:22:12.759 --> 00:22:15.299
the highly anticipated release of Overwatch 2

00:22:15.299 --> 00:22:17.859
on Steam. Unfortunately, it seems like things

00:22:17.859 --> 00:22:21.059
haven't gone as smoothly as expected. Over 47

00:22:21.059 --> 00:22:24.099
,000 players have bombarded Blizzard with negative

00:22:24.099 --> 00:22:26.599
reviews, expressing their complaints about issues

00:22:26.599 --> 00:22:29.019
such as the free -to -play model and the absence

00:22:29.019 --> 00:22:31.940
of the PvE mode. Looks like this launch has turned

00:22:31.940 --> 00:22:34.359
into a scammy dumpster fire for some disappointed

00:22:34.359 --> 00:22:37.779
gamers. Yikes. In other news, the Securities

00:22:37.779 --> 00:22:40.720
and Exchange Commission, SEC, is making waves

00:22:40.720 --> 00:22:43.440
with its legal dispute against Coinbase. The

00:22:43.440 --> 00:22:45.799
Blockchain Association is claiming that the SEC

00:22:45.799 --> 00:22:47.920
is overstepping its boundaries and trying to

00:22:47.920 --> 00:22:50.339
take away Congress's authority. They argue that

00:22:50.339 --> 00:22:53.079
the SEC is attempting to fast -track the legislative

00:22:53.079 --> 00:22:55.539
process, which is causing quite a stir in the

00:22:55.539 --> 00:22:58.079
crypto world. It'll be interesting to see how

00:22:58.079 --> 00:23:01.559
this legal battle unfolds. Moving on, Custodia

00:23:01.559 --> 00:23:04.180
Bank is breaking new ground by accepting US dollar

00:23:04.180 --> 00:23:06.700
deposits and offering Bitcoin custody services.

00:23:07.279 --> 00:23:09.279
CEO Caitlin Long proudly shared that they've

00:23:09.279 --> 00:23:11.480
met all the regulatory requirements necessary

00:23:11.480 --> 00:23:14.180
for a bank to launch such services. It's clear

00:23:14.180 --> 00:23:16.920
that the bar is set high, but Custodia Bank has

00:23:16.920 --> 00:23:20.630
successfully cleared it. Kudos to them. Now let's

00:23:20.630 --> 00:23:23.269
talk about a bizarre incident involving Lil Tay,

00:23:23.430 --> 00:23:26.130
the teenage rapper. Initially, rumors swirled

00:23:26.130 --> 00:23:28.269
about the rapper's death, but later it was revealed

00:23:28.269 --> 00:23:31.029
to be a hoax. However, the confusion didn't end

00:23:31.029 --> 00:23:33.869
there. It seems that some opportunistic individuals

00:23:33.869 --> 00:23:35.829
took advantage of the situation by launching

00:23:35.829 --> 00:23:38.589
Lil Tay -themed tokens. The world of crypto can

00:23:38.589 --> 00:23:41.309
be quite puzzling at times. In a shocking turn

00:23:41.309 --> 00:23:44.390
of events, Sam Bankman -Fried, the founder and

00:23:44.390 --> 00:23:47.970
former CEO of FTX, had his bail revoked and was

00:23:47.970 --> 00:23:50.640
sent to jail for witness tampering. Crypto Twitter

00:23:50.640 --> 00:23:53.099
didn't hold back, with users reacting strongly

00:23:53.099 --> 00:23:55.720
to the news. Some even went as far as saying,

00:23:56.019 --> 00:23:58.859
hope you enjoy prison. It's a sobering reminder

00:23:58.859 --> 00:24:01.900
that actions have consequences, regardless of

00:24:01.900 --> 00:24:05.420
one's status in the crypto world. Shifting gears,

00:24:05.720 --> 00:24:08.160
let's explore the intersection of microfinancing,

00:24:08.700 --> 00:24:11.140
decentralized lending, and a motorbike company

00:24:11.140 --> 00:24:13.559
in Kenya. You might be wondering what happens

00:24:13.559 --> 00:24:16.339
when these elements come together. It spells

00:24:16.339 --> 00:24:20.240
lots of risk. This fusion of financial practices

00:24:20.240 --> 00:24:23.220
and technology serves as a fascinating case study,

00:24:23.599 --> 00:24:26.140
highlighting the challenges and potential rewards

00:24:26.140 --> 00:24:29.940
of decentralized finance. The SEC has been in

00:24:29.940 --> 00:24:32.700
the spotlight yet again. This time they played

00:24:32.700 --> 00:24:35.420
for time, but a recent note on stablecoins by

00:24:35.420 --> 00:24:38.180
the Federal Reserve suggests a possible softening

00:24:38.180 --> 00:24:40.500
of the regulatory stance on cryptocurrencies

00:24:40.500 --> 00:24:43.180
in Washington. It seems like the tide may be

00:24:43.180 --> 00:24:45.740
turning and the crypto community eagerly awaits

00:24:45.740 --> 00:24:48.589
further developments. Are chatbots promoting

00:24:48.589 --> 00:24:51.569
eating disorders? The Center for Countering Digital

00:24:51.569 --> 00:24:54.130
Hate conducted some testing on popular chatbots

00:24:54.130 --> 00:24:57.009
and discovered that many lack safety guardrails.

00:24:57.589 --> 00:25:00.190
This raises concerns about the influence of artificial

00:25:00.190 --> 00:25:02.490
intelligence in promoting unhealthy behaviors.

00:25:03.269 --> 00:25:05.210
It's a reminder that technology must be used

00:25:05.210 --> 00:25:07.529
responsibly to ensure the well -being and mental

00:25:07.529 --> 00:25:10.349
health of users. Now let's venture into the world

00:25:10.349 --> 00:25:13.480
of art and gaming. The Metropolitan Museum has

00:25:13.480 --> 00:25:15.880
embraced the metaverse by launching a quest -based

00:25:15.880 --> 00:25:18.180
app and creating a virtual doppelganger on the

00:25:18.180 --> 00:25:21.299
popular gaming platform Roblox. The aim is to

00:25:21.299 --> 00:25:23.059
engage with younger visitors in their digital

00:25:23.059 --> 00:25:26.000
playgrounds. It's an innovative approach that

00:25:26.000 --> 00:25:28.920
showcases the MET's willingness to adapt to new

00:25:28.920 --> 00:25:31.799
forms of interaction and reach a wider audience.

00:25:33.000 --> 00:25:35.839
Paris Hilton, the influential socialite and entrepreneur,

00:25:36.400 --> 00:25:39.140
never ceases to surprise us. She has recently

00:25:39.140 --> 00:25:42.230
released Sliving Land. a game on Roblox, inspired

00:25:42.230 --> 00:25:44.349
by a word she's been trying to popularize for

00:25:44.349 --> 00:25:47.329
almost four years. It's yet another example of

00:25:47.329 --> 00:25:49.970
how celebrities are tapping into the gaming industry's

00:25:49.970 --> 00:25:52.450
immense potential to connect with their fan base.

00:25:53.089 --> 00:25:55.309
Aragon is making waves with its recent launch

00:25:55.309 --> 00:25:58.589
of the Aragon app and OSX protocol on the Coinbase

00:25:58.589 --> 00:26:01.769
blockchain. This move aims to provide a platform

00:26:01.769 --> 00:26:04.990
for decentralized autonomous organizations, DAOs,

00:26:05.289 --> 00:26:07.650
to launch without requiring extensive developer

00:26:07.650 --> 00:26:10.339
expertise. It's an exciting development that

00:26:10.339 --> 00:26:12.740
empowers individuals and communities to participate

00:26:12.740 --> 00:26:16.279
in the DAO ecosystem. We're all aware of the

00:26:16.279 --> 00:26:17.960
increasing interest from Wall Street in the world

00:26:17.960 --> 00:26:21.359
of crypto. According to Talos CEO Anton Katz,

00:26:21.700 --> 00:26:23.619
one way to bridge the gap between traditional

00:26:23.619 --> 00:26:26.539
finance and crypto is by building better piping.

00:26:27.440 --> 00:26:29.359
He believes that Wall Street firms need tools

00:26:29.359 --> 00:26:31.799
that allow them to connect to trading opportunities

00:26:31.799 --> 00:26:34.240
similar to the ones they're accustomed to in

00:26:34.240 --> 00:26:37.000
traditional capital markets. It's an intriguing

00:26:37.000 --> 00:26:39.059
perspective that highlights the importance of

00:26:39.059 --> 00:26:41.420
creating user -friendly interfaces and platforms.

00:26:42.279 --> 00:26:44.339
Legal scholars have scrutinized the Securities

00:26:44.339 --> 00:26:46.720
and Exchange Commission's notion of an investment

00:26:46.720 --> 00:26:50.779
contract in the Coinbase lawsuit. Amicus briefs

00:26:50.779 --> 00:26:53.400
from top US law schools provide valuable insights

00:26:53.400 --> 00:26:56.980
into this complex legal dispute. It's a fascinating

00:26:56.980 --> 00:26:59.240
exploration of the legal implications surrounding

00:26:59.240 --> 00:27:01.670
cryptocurrencies. and it will be interesting

00:27:01.670 --> 00:27:03.910
to see how the court interprets these arguments.

00:27:04.509 --> 00:27:06.430
Let's talk about the latest happenings on crypto

00:27:06.430 --> 00:27:09.130
Twitter. PayPal has made a significant announcement

00:27:09.130 --> 00:27:12.269
about the introduction of a stablecoin. This

00:27:12.269 --> 00:27:14.849
news has sparked excitement among crypto enthusiasts,

00:27:15.470 --> 00:27:17.829
along with strong indications of Ethereum futures

00:27:17.829 --> 00:27:21.089
ETFs coming soon. These developments highlight

00:27:21.089 --> 00:27:23.670
the growing acceptance and integration of digital

00:27:23.670 --> 00:27:26.960
assets into mainstream financial systems. Former

00:27:26.960 --> 00:27:29.259
Securities and Exchange Commission attorney John

00:27:29.259 --> 00:27:32.359
Reed Stark believes that the SEC will not approve

00:27:32.359 --> 00:27:35.920
a Bitcoin spot ETF anytime soon. However, he

00:27:35.920 --> 00:27:38.099
speculates that a Republican administration after

00:27:38.099 --> 00:27:41.440
2024 could be more amenable to ETF applications

00:27:41.440 --> 00:27:43.240
and might even roll back certain enforcement

00:27:43.240 --> 00:27:46.500
actions. As with any prediction, only time will

00:27:46.500 --> 00:27:49.599
tell if his hypothesis comes to fruition. In

00:27:49.599 --> 00:27:52.880
an amusing twist, Martin Shkreli, known for his

00:27:52.880 --> 00:27:55.299
controversial actions in the pharmaceutical industry,

00:27:55.609 --> 00:27:59.369
took a jab at Sam Bankman Fried. The former FTX

00:27:59.369 --> 00:28:01.710
CEO was recently booked into a Brooklyn prison

00:28:01.710 --> 00:28:04.569
for witness tampering, and Shkreli couldn't resist

00:28:04.569 --> 00:28:06.769
commenting on the situation with a sardonic,

00:28:06.970 --> 00:28:09.970
sucks for Sam. It's a reminder that the crypto

00:28:09.970 --> 00:28:12.170
and financial worlds are not without their fair

00:28:12.170 --> 00:28:15.470
share of drama. Last but not least, it turns

00:28:15.470 --> 00:28:18.069
out that former President Donald Trump, who has

00:28:18.069 --> 00:28:20.269
been skeptical about the value of cryptocurrencies

00:28:20.269 --> 00:28:24.009
in the past, reportedly holds up to $500 million,

00:28:24.569 --> 00:28:27.930
in Ethereum. It's intriguing to see this shift

00:28:27.930 --> 00:28:30.170
in his perspective and demonstrates the growing

00:28:30.170 --> 00:28:32.950
influence of digital assets even among high -profile

00:28:32.950 --> 00:28:35.470
individuals. And that wraps up our whirlwind

00:28:35.470 --> 00:28:37.789
tour through the latest news and trends. Stay

00:28:37.789 --> 00:28:39.769
tuned for more exciting updates in the world

00:28:39.769 --> 00:28:45.890
of technology, finance, and beyond. Nostr is

00:28:45.890 --> 00:28:48.150
a revolutionary concept in the world of publishing

00:28:48.150 --> 00:28:51.210
on the web. It stands for notes and other stuff

00:28:51.210 --> 00:28:54.259
transmitted by relays. and is a simple, open

00:28:54.259 --> 00:28:57.019
protocol that allows for censorship -resistant

00:28:57.019 --> 00:29:00.599
and globally decentralized publishing. Unlike

00:29:00.599 --> 00:29:02.940
traditional apps or services that you sign up

00:29:02.940 --> 00:29:05.980
for, Noster is a protocol upon which anyone can

00:29:05.980 --> 00:29:09.119
build. It is designed with simplicity in mind,

00:29:09.339 --> 00:29:12.299
using plain JSON and standard public key cryptography

00:29:12.299 --> 00:29:15.240
for keys and signing. This makes it easy to run

00:29:15.240 --> 00:29:18.079
relays and build clients, ensuring that the protocol

00:29:18.079 --> 00:29:21.380
can be extended over time. One of the key features

00:29:21.380 --> 00:29:24.859
of Nostr is its resilience. Unlike other publishing

00:29:24.859 --> 00:29:27.180
platforms that rely on a small number of trusted

00:29:27.180 --> 00:29:30.440
servers, Nostr allows users to connect and publish

00:29:30.440 --> 00:29:33.140
to an arbitrary number of relays. This means

00:29:33.140 --> 00:29:35.859
that even if relays disappear, users can still

00:29:35.859 --> 00:29:38.819
access and publish their content. It gives users

00:29:38.819 --> 00:29:41.900
the freedom and control to change and adapt their

00:29:41.900 --> 00:29:45.000
relays over time. Another important aspect of

00:29:45.000 --> 00:29:48.450
Nostr is its verifiability. Because Nostr accounts

00:29:48.450 --> 00:29:50.849
are based on public key cryptography, it is easy

00:29:50.849 --> 00:29:53.250
to verify that messages were truly sent by the

00:29:53.250 --> 00:29:56.170
user in question. This adds an extra layer of

00:29:56.170 --> 00:29:59.049
security and trust to the platform. But why do

00:29:59.049 --> 00:30:01.630
we need Nostr? The current state of publishing

00:30:01.630 --> 00:30:04.529
on the web is deeply flawed. What initially was

00:30:04.529 --> 00:30:07.029
an open and democratic space has now become a

00:30:07.029 --> 00:30:09.210
centralized oligopoly controlled by a handful

00:30:09.210 --> 00:30:12.109
of powerful companies. These companies dictate

00:30:12.109 --> 00:30:15.109
what we read, who we talk to, and which ideas

00:30:15.109 --> 00:30:18.250
gain traction in our society. Their pursuit of

00:30:18.250 --> 00:30:20.710
engagement has led to negative consequences for

00:30:20.710 --> 00:30:24.009
society as a whole. It's time for a change. It's

00:30:24.009 --> 00:30:26.230
time to return to the open and decentralized

00:30:26.230 --> 00:30:29.690
roots of the web. Nostr provides us with an opportunity

00:30:29.690 --> 00:30:32.430
to reclaim control over the information we consume

00:30:32.430 --> 00:30:35.009
and how we consume it. It empowers us to build

00:30:35.009 --> 00:30:36.910
more open -minded and constructive communities

00:30:36.910 --> 00:30:40.440
on the internet. By embracing Nostr, We can challenge

00:30:40.440 --> 00:30:42.859
the dominance of these powerful companies and

00:30:42.859 --> 00:30:45.220
create a more democratic and inclusive online

00:30:45.220 --> 00:30:48.539
ecosystem. No longer will our access to information

00:30:48.539 --> 00:30:51.759
be dictated by a select few. No longer will our

00:30:51.759 --> 00:30:53.799
conversations be controlled and manipulated.

00:30:54.220 --> 00:30:57.299
With Noster, the power is in our hands. Imagine

00:30:57.299 --> 00:30:59.180
a world where anyone can publish their thoughts

00:30:59.180 --> 00:31:01.980
without fear of censorship or suppression. A

00:31:01.980 --> 00:31:04.039
world where ideas can freely flow and be shared

00:31:04.039 --> 00:31:07.440
among individuals, fostering creativity and collaboration.

00:31:07.849 --> 00:31:10.829
Noster makes this possible. But Noster is just

00:31:10.829 --> 00:31:13.190
the beginning. It is part of a broader movement

00:31:13.190 --> 00:31:16.230
to decentralize the internet and empower individuals.

00:31:16.970 --> 00:31:18.769
It's not just about creating another publishing

00:31:18.769 --> 00:31:22.049
protocol. It's about reshaping the entire landscape

00:31:22.049 --> 00:31:25.589
of the web. Decentralization is a powerful concept

00:31:25.589 --> 00:31:27.970
that challenges the status quo and promotes a

00:31:27.970 --> 00:31:30.569
more democratic and equitable online experience.

00:31:31.049 --> 00:31:33.769
It gives individuals the freedom to express themselves,

00:31:34.150 --> 00:31:36.710
connect with others, and shape their own online

00:31:36.710 --> 00:31:39.519
communities. So let's embrace Nostr and the broader

00:31:39.519 --> 00:31:42.500
idea of decentralizing the internet. Let's take

00:31:42.500 --> 00:31:44.720
back control over the information we consume

00:31:44.720 --> 00:31:47.640
and the conversations we engage in. Let's build

00:31:47.640 --> 00:31:50.079
a future where the web is open, inclusive, and

00:31:50.079 --> 00:31:59.380
owned by the people. So let's talk about what

00:31:59.380 --> 00:32:01.940
Nostr enables. It's a platform that offers a

00:32:01.940 --> 00:32:04.920
simple and flexible event format. allowing users

00:32:04.920 --> 00:32:07.039
to publish different types of content like social

00:32:07.039 --> 00:32:09.859
media posts, long -form articles, rich media,

00:32:09.960 --> 00:32:12.799
and even e -commerce. This means you have the

00:32:12.799 --> 00:32:14.940
freedom to express yourself in any way you like.

00:32:15.539 --> 00:32:17.960
One great feature of Noster is its verifiability.

00:32:18.500 --> 00:32:20.880
This means that notes and content are attributed

00:32:20.880 --> 00:32:23.819
to specific users, making it harder for spam

00:32:23.819 --> 00:32:26.440
and bots to infiltrate the platform. It adds

00:32:26.440 --> 00:32:28.660
a layer of authenticity and trust in the content

00:32:28.660 --> 00:32:31.319
you consume. Another important aspect of Noster

00:32:31.319 --> 00:32:34.640
is its decentralized nature. Users have the ability

00:32:34.640 --> 00:32:36.839
to connect to various relays and even run their

00:32:36.839 --> 00:32:39.420
own. This decentralization makes it challenging

00:32:39.420 --> 00:32:42.279
for any single entity to censor ideas or control

00:32:42.279 --> 00:32:45.019
who gets to participate. It's all about promoting

00:32:45.019 --> 00:32:47.220
freedom of expression and avoiding the control

00:32:47.220 --> 00:32:51.339
we often see in mainstream social media. Oh,

00:32:51.400 --> 00:32:53.519
and did I mention that Nostr is integrated with

00:32:53.519 --> 00:32:56.720
Lightning? This opens up new possibilities for

00:32:56.720 --> 00:33:00.000
value -for -value business models. Instead of

00:33:00.000 --> 00:33:03.289
relying solely on ads, Noster allows users to

00:33:03.289 --> 00:33:05.369
create fairer models where they can directly

00:33:05.369 --> 00:33:08.609
exchange value with their audience. It's an innovative

00:33:08.609 --> 00:33:11.829
approach to monetization. Now let's take a look

00:33:11.829 --> 00:33:14.170
at the current state of mainstream media and

00:33:14.170 --> 00:33:17.009
big tech social media platforms. Unfortunately,

00:33:17.230 --> 00:33:20.009
both of these have their downsides. Mainstream

00:33:20.009 --> 00:33:22.049
media often relies on grabbing your attention

00:33:22.049 --> 00:33:24.910
to sell ads, leading to sensational headlines

00:33:24.910 --> 00:33:27.890
and clickbait tactics. And let's not forget their

00:33:27.890 --> 00:33:30.069
tendency to focus on negativity and outrage.

00:33:30.630 --> 00:33:33.569
On the other hand, Big tech social media platforms

00:33:33.569 --> 00:33:37.009
also use your attention to sell ads. They employ

00:33:37.009 --> 00:33:39.349
bizarre techniques to keep you hooked, adding

00:33:39.349 --> 00:33:42.130
to the addictive nature of these platforms. Plus,

00:33:42.589 --> 00:33:44.670
the algorithms that determine the content you

00:33:44.670 --> 00:33:47.269
see are often kept secret, leaving you in the

00:33:47.269 --> 00:33:49.509
dark about how they work and unable to influence

00:33:49.509 --> 00:33:52.609
them. Additionally, these platforms have complete

00:33:52.609 --> 00:33:55.250
control over who can participate and often struggle

00:33:55.250 --> 00:33:58.420
with spam and bot issues. But wait, there's another

00:33:58.420 --> 00:34:01.099
alternative. Federated social media platforms

00:34:01.099 --> 00:34:04.680
like Mastodon. These platforms operate on a decentralized

00:34:04.680 --> 00:34:07.640
model where user identities are attached to domain

00:34:07.640 --> 00:34:10.400
names controlled by third parties. While this

00:34:10.400 --> 00:34:13.300
may initially seem like a solution, it also comes

00:34:13.300 --> 00:34:16.239
with its own set of challenges. For example,

00:34:16.659 --> 00:34:19.179
these third parties have the power to ban users,

00:34:19.559 --> 00:34:21.760
just like centralized social media platforms.

00:34:22.559 --> 00:34:25.539
Additionally, server owners can block other servers.

00:34:25.869 --> 00:34:29.010
limiting cross -server interactions. Migration

00:34:29.010 --> 00:34:31.150
between servers is also difficult and requires

00:34:31.150 --> 00:34:33.550
cooperation between servers, which isn't always

00:34:33.550 --> 00:34:36.530
easy to achieve. Moreover, running servers on

00:34:36.530 --> 00:34:39.889
federated platforms lacks clear incentives. As

00:34:39.889 --> 00:34:42.150
a result, servers are typically operated by enthusiasts

00:34:42.150 --> 00:34:44.050
or individuals seeking recognition through a

00:34:44.050 --> 00:34:46.909
cool domain name. Unfortunately, this often leads

00:34:46.909 --> 00:34:49.730
to the despotism of a single person, which can

00:34:49.730 --> 00:34:52.269
be worse than the control exerted by big companies

00:34:52.269 --> 00:34:55.340
like Twitter. Additionally, users often find

00:34:55.340 --> 00:34:57.659
themselves unable to migrate out of these servers

00:34:57.659 --> 00:35:00.699
effectively, rendering them stuck in unfavorable

00:35:00.699 --> 00:35:03.780
environments. Furthermore, amateur -run servers

00:35:03.780 --> 00:35:06.460
are prone to abandonment, effectively banning

00:35:06.460 --> 00:35:08.559
all users who signed up through that server.

00:35:09.199 --> 00:35:11.619
This creates issues with data duplication across

00:35:11.619 --> 00:35:14.519
different servers, making it challenging to maintain

00:35:14.519 --> 00:35:17.980
a coherent and seamless experience. In conclusion,

00:35:18.480 --> 00:35:20.760
while Nostr offers a promising solution to many

00:35:20.760 --> 00:35:23.489
of the issues faced by mainstream media, and

00:35:23.489 --> 00:35:26.250
existing social media platforms, there are still

00:35:26.250 --> 00:35:28.909
challenges to be addressed in decentralized systems.

00:35:29.429 --> 00:35:31.650
It's clear that finding the right balance between

00:35:31.650 --> 00:35:34.090
freedom of expression and avoiding centralized

00:35:34.090 --> 00:35:37.030
control is an ongoing process. However, with

00:35:37.030 --> 00:35:38.989
platforms like Nostr pushing the boundaries,

00:35:39.590 --> 00:35:41.769
there is hope for a future where users have more

00:35:41.769 --> 00:35:48.210
power and agency in the online world. So let's

00:35:48.210 --> 00:35:51.619
dive into what Zaps are all about. Think of them

00:35:51.619 --> 00:35:53.619
as helpful tips that are transmitted over the

00:35:53.619 --> 00:35:55.880
Lightning Network at lightning -fast speed with

00:35:55.880 --> 00:35:58.639
little to no transaction fees. It's like sending

00:35:58.639 --> 00:36:01.920
a message across the network in no time. Now,

00:36:01.960 --> 00:36:04.599
before we go further, let's understand how Zaps

00:36:04.599 --> 00:36:06.880
became an integral part of the Nostr protocol.

00:36:07.440 --> 00:36:10.360
In the early days, lightning invoices were often

00:36:10.360 --> 00:36:13.429
seen in notes. However, with the implementation

00:36:13.429 --> 00:36:17.289
of NIP -57, ZAPs took center stage as the primary

00:36:17.289 --> 00:36:20.349
way to transmit value in Noster notes. But what

00:36:20.349 --> 00:36:24.389
exactly is NIP -57 and how do ZAPs work? NIP

00:36:24.389 --> 00:36:28.210
-57, short for Noster Implementation Proposal

00:36:28.210 --> 00:36:31.170
57, is the document that lays out the guidelines

00:36:31.170 --> 00:36:34.429
for implementing ZAPs. It introduces two new

00:36:34.429 --> 00:36:39.280
types of notes. Kind 9735, which we call a ZAP,

00:36:39.659 --> 00:36:44.599
and Kind 9734, known as a ZAP request. These

00:36:44.599 --> 00:36:47.559
two notekinds work together seamlessly, enabling

00:36:47.559 --> 00:36:50.260
Nostr clients to easily request ZAP invoices

00:36:50.260 --> 00:36:53.440
from Eleneural servers and pay them. Essentially,

00:36:53.760 --> 00:36:56.860
NIPI 57 facilitates the smooth flow of ZAP payments

00:36:56.860 --> 00:36:59.420
within Lightning wallets and relays. Here's an

00:36:59.420 --> 00:37:01.960
interesting tidbit for you. The notekind chosen

00:37:01.960 --> 00:37:06.539
for ZAPs 9735, is actually the same port number

00:37:06.539 --> 00:37:09.320
that Lightning Network uses for networking. It's

00:37:09.320 --> 00:37:11.460
a fun little connection between the technology

00:37:11.460 --> 00:37:14.699
and its implementation. Now let's take a moment

00:37:14.699 --> 00:37:17.199
to explore the benefits of using Zaps in your

00:37:17.199 --> 00:37:20.699
Noster client. Firstly, Zaps offer incredible

00:37:20.699 --> 00:37:23.460
speed. Since they are transmitted over the Lightning

00:37:23.460 --> 00:37:26.619
Network, they travel at the speed of light, meaning

00:37:26.619 --> 00:37:29.820
your transactions happen in a flash. In a world

00:37:29.820 --> 00:37:32.809
where time is money, This is a significant advantage.

00:37:33.670 --> 00:37:36.070
Secondly, Zaps come with minimal transaction

00:37:36.070 --> 00:37:40.230
fees, if any at all. Traditionally, making transactions

00:37:40.230 --> 00:37:43.250
would require users to pay fees, often adding

00:37:43.250 --> 00:37:46.909
up to a significant amount. But with Zaps, these

00:37:46.909 --> 00:37:49.389
fees are drastically reduced, making it much

00:37:49.389 --> 00:37:52.010
more cost -effective to transmit value. It's

00:37:52.010 --> 00:37:54.349
a win -win situation for all parties involved.

00:37:54.829 --> 00:37:57.429
Another noteworthy aspect of Zaps is their versatility.

00:37:57.909 --> 00:38:00.840
You can use them for a variety of purposes. Need

00:38:00.840 --> 00:38:03.719
to tip someone for their services? Zap it! Want

00:38:03.719 --> 00:38:06.340
to reward an online content creator? Zap it!

00:38:06.639 --> 00:38:09.719
Sending money across the globe? Zap it! The possibilities

00:38:09.719 --> 00:38:11.920
are vast, and with Zaps, the process is simple

00:38:11.920 --> 00:38:14.380
and efficient. Now you might be wondering, how

00:38:14.380 --> 00:38:16.599
exactly do you use Zaps on your Nostr client?

00:38:16.980 --> 00:38:19.280
Well, it's quite straightforward. First, ensure

00:38:19.280 --> 00:38:21.239
that your Nostr client is updated to support

00:38:21.239 --> 00:38:25.000
Zaps and NIP57 implementation. Once that's taken

00:38:25.000 --> 00:38:27.519
care of, you can start requesting Zap invoices

00:38:27.519 --> 00:38:30.659
from LN neural servers. These servers will provide

00:38:30.659 --> 00:38:32.880
you with the necessary information to generate

00:38:32.880 --> 00:38:36.239
the invoice. Once you have the invoice, simply

00:38:36.239 --> 00:38:38.400
make the payment using your Lightning Wallet.

00:38:38.800 --> 00:38:41.599
It's as easy as that. Additionally, if you're

00:38:41.599 --> 00:38:44.420
on the receiving end of ZAP payments, your Lightning

00:38:44.420 --> 00:38:46.840
Wallet will automatically generate notes that

00:38:46.840 --> 00:38:49.800
need to be sent to relays. These notes ensure

00:38:49.800 --> 00:38:52.219
that the transactions are securely processed

00:38:52.219 --> 00:38:55.139
and settled. It's all part of the streamlined

00:38:55.139 --> 00:38:58.820
process created by the NIP -57 specification.

00:38:59.190 --> 00:39:02.329
So, whether you're a Noster client user or a

00:39:02.329 --> 00:39:05.289
Lightning Network enthusiast, Zaps bring a whole

00:39:05.289 --> 00:39:07.889
new level of efficiency and convenience to the

00:39:07.889 --> 00:39:10.889
table. With their lightning -fast speed, minimal

00:39:10.889 --> 00:39:13.110
transaction fees, and straightforward implementation,

00:39:13.690 --> 00:39:15.510
they're transforming the way transactions are

00:39:15.510 --> 00:39:18.710
done. So there you have it. A brief introduction

00:39:18.710 --> 00:39:21.650
to Zaps, their implementation through NIP57,

00:39:22.070 --> 00:39:25.079
and their impact on Noster clients. With Zaps,

00:39:25.119 --> 00:39:27.079
you can breeze through transactions with the

00:39:27.079 --> 00:39:29.079
speed of light while keeping your costs minimal.

00:39:29.599 --> 00:39:31.820
It's a game changer in the world of value transmission.

00:39:32.400 --> 00:39:34.940
Remember, Zaps are here to make your life easier.

00:39:35.360 --> 00:39:37.619
So why not embrace them and experience the future

00:39:37.619 --> 00:39:47.699
of hassle -free transactions? So, let's talk

00:39:47.699 --> 00:39:50.380
about how Zaps work. Now we're not going to dive

00:39:50.380 --> 00:39:52.940
deep into the technical details here, but for

00:39:52.940 --> 00:39:55.260
those of you who are curious, we'll give you

00:39:55.260 --> 00:39:57.760
a basic overview of how this whole Zap thing

00:39:57.760 --> 00:40:01.300
operates. So when you click or tap on that little

00:40:01.300 --> 00:40:04.599
lightning bolt icon in your client, whether it's

00:40:04.599 --> 00:40:07.619
Damus, Iris, Amethyst, or any other lightning

00:40:07.619 --> 00:40:10.079
wallet, something interesting starts happening

00:40:10.079 --> 00:40:13.000
behind the scenes. You see, the first thing your

00:40:13.000 --> 00:40:16.360
client does is communicate with the LNURL server

00:40:16.360 --> 00:40:18.099
that's sitting in front of the lightning wallet

00:40:18.099 --> 00:40:20.400
of the person you're trying to zap. It sends

00:40:20.400 --> 00:40:22.960
a message like, hey, I want to give Alice some

00:40:22.960 --> 00:40:27.699
SATs. Then the LNURL server responds. If Alice's

00:40:27.699 --> 00:40:30.099
wallet supports zaps, the server will let your

00:40:30.099 --> 00:40:32.460
client know and also provide Alice's public key.

00:40:32.960 --> 00:40:36.159
This is an essential piece of information. Now,

00:40:36.320 --> 00:40:38.500
armed with this knowledge, your client works

00:40:38.500 --> 00:40:41.449
on putting together a zap request. Think of it

00:40:41.449 --> 00:40:45.809
as a kind of note, more specifically, a 9734

00:40:45.809 --> 00:40:48.889
note, that contains data about the profile or

00:40:48.889 --> 00:40:51.650
note you want to zap, the amount, the relays

00:40:51.650 --> 00:40:53.570
where the note should be broadcasted, and a few

00:40:53.570 --> 00:40:57.369
other details. This zap request serves as a request

00:40:57.369 --> 00:41:00.590
for an invoice from the LNURL server. Once the

00:41:00.590 --> 00:41:03.110
server receives this request, it responds by

00:41:03.110 --> 00:41:05.889
providing the invoice you asked for. This invoice

00:41:05.889 --> 00:41:08.190
will include all the necessary payment details.

00:41:08.730 --> 00:41:11.320
Now, it's time for your client to pass this invoice

00:41:11.320 --> 00:41:13.679
to your lightning wallet so that you can pay

00:41:13.679 --> 00:41:16.519
it. If you're using a wallet like Albi in your

00:41:16.519 --> 00:41:19.699
browser and have already set a budget, this payment

00:41:19.699 --> 00:41:22.599
process can happen in a snap. Once you've paid

00:41:22.599 --> 00:41:24.679
the invoice directly to the wallet of the person

00:41:24.679 --> 00:41:27.480
you're zapping, their wallet will create a special

00:41:27.480 --> 00:41:32.039
note, a 9 ,735 note, and broadcast it to the

00:41:32.039 --> 00:41:34.300
relays that were specified in your initial zap

00:41:34.300 --> 00:41:37.840
request. Now, When these relays receive the note,

00:41:38.280 --> 00:41:40.820
they can notify connected clients about the zap.

00:41:41.420 --> 00:41:44.300
And clients, well, they can then show the zap

00:41:44.300 --> 00:41:47.400
to users in their user interface. It's a way

00:41:47.400 --> 00:41:49.800
for everyone to stay updated and informed about

00:41:49.800 --> 00:41:52.380
the zaps happening in the network. And perhaps

00:41:52.380 --> 00:41:54.320
the most fascinating part of all this is that

00:41:54.320 --> 00:41:56.360
it all takes place in just a matter of seconds.

00:41:56.820 --> 00:41:59.460
Fast, huh? And not only is it speedy, but it

00:41:59.460 --> 00:42:02.099
also costs just a tiny fraction of a penny. That's

00:42:02.099 --> 00:42:04.440
pretty incredible when you think about it. So.

00:42:04.599 --> 00:42:07.719
That's a brief overview of how zaps work. Remember,

00:42:08.159 --> 00:42:10.039
there's a lot more technical stuff going on in

00:42:10.039 --> 00:42:12.500
the background, but this gives you the basic

00:42:12.500 --> 00:42:18.760
mechanics of how it all comes together. So, you

00:42:18.760 --> 00:42:20.360
want to know how to send and receive zaps in

00:42:20.360 --> 00:42:23.400
Nostr? Well, it's actually quite simple. To zap

00:42:23.400 --> 00:42:26.079
other people, you just need two things, a zap

00:42:26.079 --> 00:42:28.159
-compatible lightning wallet and a client that

00:42:28.159 --> 00:42:30.920
has implemented zaps. Let's start with the lightning

00:42:30.920 --> 00:42:33.199
wallet. There are a few options you can choose

00:42:33.199 --> 00:42:36.039
from, such as Albi or Wallet of Satoshi. These

00:42:36.039 --> 00:42:38.179
wallets are designed to be compatible with Zaps,

00:42:38.539 --> 00:42:40.320
so make sure you have one of these installed.

00:42:40.860 --> 00:42:43.179
Next, you'll need a client that supports Zaps.

00:42:43.639 --> 00:42:45.500
Noster offers a variety of clients that have

00:42:45.500 --> 00:42:48.340
implemented Zaps, including Damus, Amethyst,

00:42:48.579 --> 00:42:51.800
Iris, and Snort. These clients allow you to interact

00:42:51.800 --> 00:42:54.840
with the Zap feature seamlessly. Now here comes

00:42:54.840 --> 00:42:57.280
the important part. You need to set your lightning

00:42:57.280 --> 00:42:59.960
address in your Noster profile. This address

00:42:59.960 --> 00:43:02.199
will be used to receive any ZAPs that come your

00:43:02.199 --> 00:43:05.280
way. So, make sure you have this address correctly

00:43:05.280 --> 00:43:08.179
set up in your profile. That way, when someone

00:43:08.179 --> 00:43:10.340
sends you a ZAP, it will go directly to your

00:43:10.340 --> 00:43:12.840
designated Lightning address. But here's something

00:43:12.840 --> 00:43:15.039
interesting to note. You have the flexibility

00:43:15.039 --> 00:43:17.519
to pay for ZAPs from a wallet or address other

00:43:17.519 --> 00:43:19.400
than the one you have set in your profile to

00:43:19.400 --> 00:43:21.920
receive ZAPs. Let's take a look at an example

00:43:21.920 --> 00:43:24.480
to better understand this. Imagine you have a

00:43:24.480 --> 00:43:26.780
Stacker News Lightning address set in your Nostra

00:43:26.780 --> 00:43:29.190
profile. This address is where you'll receive

00:43:29.190 --> 00:43:32.730
any zapped SATs. Now let's say you're using your

00:43:32.730 --> 00:43:35.849
web browser and have Iris as your client. When

00:43:35.849 --> 00:43:38.449
you want to pay for zaps, you can actually use

00:43:38.449 --> 00:43:40.929
your Albi wallet, which you access through their

00:43:40.929 --> 00:43:43.469
Chrome extension. This allows you to pay for

00:43:43.469 --> 00:43:45.949
zaps using a different wallet while still receiving

00:43:45.949 --> 00:43:48.510
them in your designated lightning address. It

00:43:48.510 --> 00:43:51.170
gives you that extra flexibility and convenience.

00:43:51.809 --> 00:43:54.429
And if you prefer to use a mobile client, you

00:43:54.429 --> 00:43:57.210
can opt for Damus. With Daymas as your client,

00:43:57.449 --> 00:43:59.829
you can pay for Zaps using the Wallet of Satoshi

00:43:59.829 --> 00:44:02.409
app. This allows you to have a different payment

00:44:02.409 --> 00:44:04.630
method while still using your Lightning address

00:44:04.630 --> 00:44:07.829
set in your Nostr profile to receive Zaps. So

00:44:07.829 --> 00:44:10.150
as you can see, sending and receiving Zaps in

00:44:10.150 --> 00:44:12.349
Nostr is pretty straightforward. All you need

00:44:12.349 --> 00:44:15.030
is a Zap -compatible Lightning wallet and a client

00:44:15.030 --> 00:44:17.889
that supports Zaps. And don't forget to set your

00:44:17.889 --> 00:44:20.590
lightning address in your Noster profile to receive

00:44:20.590 --> 00:44:23.010
Zaps. And remember you have the option to pay

00:44:23.010 --> 00:44:25.170
for Zaps from a different wallet or address if

00:44:25.170 --> 00:44:28.050
you prefer. It's all about giving you the flexibility

00:44:28.050 --> 00:44:31.510
to use Noster in a way that works best for you.

00:44:37.730 --> 00:44:40.889
So let's talk about Zaps. Have you heard of them

00:44:40.889 --> 00:44:43.840
before? If not, don't worry. I'll fill you in

00:44:43.840 --> 00:44:45.539
on what they are, how they work, and how you

00:44:45.539 --> 00:44:48.679
can use them on your Noster client. Basically,

00:44:49.139 --> 00:44:50.800
Zaps are like little tips that are sent over

00:44:50.800 --> 00:44:53.059
the Lightning Network at lightning -fast speed.

00:44:53.500 --> 00:44:56.280
And the best part? There are basically no transaction

00:44:56.280 --> 00:44:59.260
fees involved. It's a win -win situation, right?

00:44:59.940 --> 00:45:02.639
In the early days of the Noster protocol, Lightning

00:45:02.639 --> 00:45:05.550
invoices were commonly found in notes. But with

00:45:05.550 --> 00:45:09.210
the implementation of NIP -57, ZAPs have become

00:45:09.210 --> 00:45:11.849
the go -to method for transmitting value in Noster

00:45:11.849 --> 00:45:15.289
notes. So let's delve deeper into what NIP -57

00:45:15.289 --> 00:45:20.510
is all about and how ZAPs operate. NIP -57, otherwise

00:45:20.510 --> 00:45:23.349
known as the ZAP implementation document, lays

00:45:23.349 --> 00:45:25.969
out the guidelines for how ZAPs should be implemented.

00:45:26.510 --> 00:45:30.949
It introduces two new note kinds, kind 9735,

00:45:31.349 --> 00:45:35.909
which represents a ZAP, and KIND 9734, which

00:45:35.909 --> 00:45:39.349
represents a ZAP request. Together, these two

00:45:39.349 --> 00:45:42.170
note kinds enable Noster clients to request ZAP

00:45:42.170 --> 00:45:45.190
invoices from LNURL servers and make payments

00:45:45.190 --> 00:45:49.409
accordingly. Additionally, the NIP 57 specification

00:45:49.409 --> 00:45:51.849
outlines how Lightning wallets that receive ZAP

00:45:51.849 --> 00:45:54.429
payments should create notes to be sent to relays.

00:45:54.769 --> 00:45:57.050
It's a well -structured system that ensures smooth

00:45:57.050 --> 00:45:59.250
communication and hassle -free transactions.

00:45:59.829 --> 00:46:02.039
And here's a fun fact for you. The note kind

00:46:02.039 --> 00:46:07.039
chosen for zaps, 9735, is actually the same networking

00:46:07.039 --> 00:46:09.800
port that Lightning uses. It's a neat little

00:46:09.800 --> 00:46:12.519
detail that adds another layer of interconnectedness

00:46:12.519 --> 00:46:15.139
to the whole concept. Now that we've covered

00:46:15.139 --> 00:46:18.139
the basics and the technicalities, let's explore

00:46:18.139 --> 00:46:20.780
the benefits of using zaps on your Nostra client.

00:46:21.599 --> 00:46:24.139
One of the main advantages is the speed at which

00:46:24.139 --> 00:46:27.280
transactions occur. Since zaps are transmitted

00:46:27.280 --> 00:46:29.900
over the Lightning network, they travel at the

00:46:29.900 --> 00:46:32.000
speed of light. This means that your payments

00:46:32.000 --> 00:46:34.659
can be processed quickly and efficiently, saving

00:46:34.659 --> 00:46:37.860
you valuable time. Another great thing about

00:46:37.860 --> 00:46:41.000
Zaps is the negligible transaction fees. Traditional

00:46:41.000 --> 00:46:43.619
payment methods often come with hefty fees that

00:46:43.619 --> 00:46:46.820
eat into your funds. But with Zaps, you can enjoy

00:46:46.820 --> 00:46:49.260
the benefits of micro -transactions without worrying

00:46:49.260 --> 00:46:52.699
about substantial deductions. It's a cost -effective

00:46:52.699 --> 00:46:55.059
solution that makes financial transactions more

00:46:55.059 --> 00:46:58.019
accessible to everyone. Furthermore, ZAPs enhance

00:46:58.019 --> 00:47:00.579
the overall user experience by simplifying the

00:47:00.579 --> 00:47:03.500
payment process. With the implementation of NIP

00:47:03.500 --> 00:47:07.019
-57, requesting ZAP invoices has become much

00:47:07.019 --> 00:47:10.179
easier. Noster clients can effortlessly navigate

00:47:10.179 --> 00:47:13.719
LNURL servers to obtain the necessary invoices

00:47:13.719 --> 00:47:17.239
and pay them directly. This streamlines the transaction

00:47:17.239 --> 00:47:20.179
process, eliminating the need for complicated

00:47:20.179 --> 00:47:24.010
steps and reducing potential errors. Additionally,

00:47:24.389 --> 00:47:26.670
Zaps foster a sense of community and support

00:47:26.670 --> 00:47:29.750
between Noster users. By enabling people to send

00:47:29.750 --> 00:47:32.630
small tips, Zaps encourage collaboration and

00:47:32.630 --> 00:47:35.070
appreciation for valuable content or services.

00:47:35.690 --> 00:47:37.670
It's like spreading positivity through the lightning

00:47:37.670 --> 00:47:41.090
network and creating a supportive ecosystem within

00:47:41.090 --> 00:47:44.570
the Noster community. So, how can you start using

00:47:44.570 --> 00:47:47.210
Zaps on your Noster client? It's quite simple.

00:47:47.889 --> 00:47:50.190
Ensure that your client is updated to the latest

00:47:50.190 --> 00:47:53.519
version that supports NAP57. This will enable

00:47:53.519 --> 00:47:56.059
you to seamlessly request ZAP invoices and make

00:47:56.059 --> 00:47:59.360
payments. From there, you can explore various

00:47:59.360 --> 00:48:01.480
ele -neural servers that offer ZAPs and find

00:48:01.480 --> 00:48:04.079
exciting services or content creators to support.

00:48:04.800 --> 00:48:07.559
To sum it up, ZAPs are an innovative way to transmit

00:48:07.559 --> 00:48:10.860
value in the Nostra ecosystem. They offer speedy,

00:48:10.960 --> 00:48:13.639
low -cost transactions that enhance user experience

00:48:13.639 --> 00:48:17.130
and foster community support. With the implementation

00:48:17.130 --> 00:48:20.730
of NIP 57, requesting ZAP invoices has become

00:48:20.730 --> 00:48:23.710
incredibly convenient. So if you're ready to

00:48:23.710 --> 00:48:25.989
experience lightning -fast and fee -friendly

00:48:25.989 --> 00:48:29.070
transactions, embrace the power of ZAPs on your

00:48:29.070 --> 00:48:32.230
Nostr client. And there you have it, a comprehensive

00:48:32.230 --> 00:48:35.269
overview of what ZAPs are, how they work, and

00:48:35.269 --> 00:48:38.190
how you can use them on your Nostr client. So

00:48:38.190 --> 00:48:40.849
go ahead and explore the world of ZAPs. It's

00:48:40.849 --> 00:48:47.400
an exciting journey waiting to unfold. So, let's

00:48:47.400 --> 00:48:49.739
dive into the fascinating world of zaps and get

00:48:49.739 --> 00:48:52.139
a better understanding of how they actually work.

00:48:52.679 --> 00:48:54.619
Don't worry, we won't get too technical here,

00:48:54.820 --> 00:48:56.980
but we'll explore the basic mechanics behind

00:48:56.980 --> 00:48:59.880
them. You know that little icon you see in your

00:48:59.880 --> 00:49:02.900
client, whether it's Damus, Iris, Amethyst, or

00:49:02.900 --> 00:49:05.400
whichever lightning wallet you're using? Well,

00:49:05.440 --> 00:49:08.119
when you click or tap on that icon, something

00:49:08.119 --> 00:49:10.789
interesting happens. Your client sends a ping

00:49:10.789 --> 00:49:13.829
to the Eleneurl server, which is the server that

00:49:13.829 --> 00:49:15.989
sits in front of the lightning wallet of the

00:49:15.989 --> 00:49:18.289
person you're trying to zap. It's like saying,

00:49:18.449 --> 00:49:20.710
hey there, I would love to give Alice some saties.

00:49:21.230 --> 00:49:23.570
Now the Eleneurl server responds to your client.

00:49:24.050 --> 00:49:26.530
If Alice's wallet supports zaps, it lets your

00:49:26.530 --> 00:49:29.130
client know and also sends or confirms Alice's

00:49:29.130 --> 00:49:31.690
public key. This is where the magic starts to

00:49:31.690 --> 00:49:34.190
happen. Your client at this point puts together

00:49:34.190 --> 00:49:38.789
a zap request, also known as a kind 9 ,734 note.

00:49:38.989 --> 00:49:42.210
This request contains information about the profile

00:49:42.210 --> 00:49:45.590
or note that you want to zap, such as the amount,

00:49:46.250 --> 00:49:48.409
the relays it should broadcast the note to, and

00:49:48.409 --> 00:49:51.550
a few other details. Essentially, it's like asking

00:49:51.550 --> 00:49:54.630
the EleNeural server for an invoice. Once your

00:49:54.630 --> 00:49:57.010
client has sent the zap request, the EleNeural

00:49:57.010 --> 00:49:59.070
server responds with the invoice you requested.

00:49:59.690 --> 00:50:01.969
Now, this is where things get even more exciting.

00:50:02.550 --> 00:50:04.710
Your client takes that invoice and hands it off

00:50:04.710 --> 00:50:06.869
to your lightning wallet. And here's the crucial

00:50:06.869 --> 00:50:10.809
part. You... as the user, need to pay that invoice

00:50:10.809 --> 00:50:13.070
directly from your wallet to the recipient's

00:50:13.070 --> 00:50:15.349
wallet. If you're using a browser wallet like

00:50:15.349 --> 00:50:18.070
Albi and have set a budget, this whole process

00:50:18.070 --> 00:50:20.849
can happen lightning fast. Once you've paid the

00:50:20.849 --> 00:50:23.389
invoice, the recipient's wallet creates a kind

00:50:23.389 --> 00:50:27.309
9735 note, and this note is then broadcasted

00:50:27.309 --> 00:50:30.349
to the relays specified in the Zap request. It's

00:50:30.349 --> 00:50:32.269
like sending a message to the relays, telling

00:50:32.269 --> 00:50:35.400
them about the Zap. Now, the relays that receive

00:50:35.400 --> 00:50:37.619
this note can then inform connected clients about

00:50:37.619 --> 00:50:40.440
the zap, and then those clients can show the

00:50:40.440 --> 00:50:43.360
zap to users in their user interface. It's a

00:50:43.360 --> 00:50:45.599
seamless process that happens behind the scenes,

00:50:46.139 --> 00:50:48.440
keeping the user experience smooth and hassle

00:50:48.440 --> 00:50:51.860
-free. And here's the incredible part. All of

00:50:51.860 --> 00:50:53.739
this happens in just a matter of seconds and

00:50:53.739 --> 00:50:56.400
at a cost of only a tiny fraction of a penny.

00:50:56.960 --> 00:50:59.340
It's lightning fast and cost effective, making

00:50:59.340 --> 00:51:01.699
zaps an efficient and convenient way to transfer

00:51:01.699 --> 00:51:04.519
value on the lightning network. So next time

00:51:04.519 --> 00:51:07.340
you click or tap on that icon, know that there's

00:51:07.340 --> 00:51:09.760
a whole chain of events happening in the background.

00:51:10.400 --> 00:51:12.699
The client pings the Elnurl server, requests

00:51:12.699 --> 00:51:15.099
an invoice, you pay the invoice, and then the

00:51:15.099 --> 00:51:17.300
recipient's wallet broadcasts the note to the

00:51:17.300 --> 00:51:20.099
relays. It's a fascinating process that enables

00:51:20.099 --> 00:51:22.760
fast and secure transactions on the Lightning

00:51:22.760 --> 00:51:25.679
Network. And that, my friend, is how zaps work.

00:51:26.059 --> 00:51:28.420
Pretty incredible, right? Now you have a better

00:51:28.420 --> 00:51:31.119
understanding of the inner workings of zaps and

00:51:31.119 --> 00:51:33.099
can appreciate the convenience they bring to

00:51:33.099 --> 00:51:35.400
Lightning Network users. So go ahead and zap

00:51:35.400 --> 00:51:45.400
away. So you're wondering how to send and receive

00:51:45.400 --> 00:51:47.909
zaps on Nostr. Well, it's actually pretty simple.

00:51:48.389 --> 00:51:50.210
All you need are a few things to get started.

00:51:50.789 --> 00:51:53.170
First, you'll need a Zap -compatible lightning

00:51:53.170 --> 00:51:55.809
wallet. There are a couple of options available

00:51:55.809 --> 00:51:59.449
such as Albi or Wallet of Satoshi. You can choose

00:51:59.449 --> 00:52:02.090
the one that works best for you. Next, you'll

00:52:02.090 --> 00:52:05.269
need a client that has implemented Zaps. Nostr

00:52:05.269 --> 00:52:07.269
supports a few different clients that you can

00:52:07.269 --> 00:52:11.369
use like Damus, Amethyst, Iris, or Snort. These

00:52:11.369 --> 00:52:13.570
clients have integrated ZAP functionality, allowing

00:52:13.570 --> 00:52:15.829
you to easily send and receive ZAPs within the

00:52:15.829 --> 00:52:19.010
Nostra ecosystem. Once you have your ZAP -compatible

00:52:19.010 --> 00:52:21.130
lightning wallet and a supported client, there's

00:52:21.130 --> 00:52:24.150
just one more thing to do. Make sure you have

00:52:24.150 --> 00:52:26.550
your lightning address set in your Nostra profile.

00:52:27.230 --> 00:52:29.469
This is the address where you'll receive all

00:52:29.469 --> 00:52:32.389
your ZAPs. It's important to have this set up

00:52:32.389 --> 00:52:35.110
correctly, as it ensures that the ZAPs you receive

00:52:35.110 --> 00:52:38.329
go to the right place. Now, here's an interesting

00:52:38.329 --> 00:52:41.059
tidbit. You can actually pay for zaps from a

00:52:41.059 --> 00:52:43.059
wallet or address other than the one you have

00:52:43.059 --> 00:52:45.800
set in your profile. Let me explain with an example.

00:52:46.400 --> 00:52:48.619
Imagine you have a Stacker News lightning address

00:52:48.619 --> 00:52:51.300
set in your Nostr profile. This is the address

00:52:51.300 --> 00:52:54.460
where you'll receive any zapped SATs. Now, let's

00:52:54.460 --> 00:52:56.880
say you're using Iris as your web browser client.

00:52:57.500 --> 00:52:59.880
When it comes to paying for zaps, you can use

00:52:59.880 --> 00:53:02.380
your Albi wallet via their Chrome extension.

00:53:02.980 --> 00:53:05.559
This means you have the flexibility to use different

00:53:05.559 --> 00:53:08.269
wallets and addresses for zaps. even if they're

00:53:08.269 --> 00:53:10.369
not the same as the one in your Nostr profile.

00:53:10.909 --> 00:53:12.989
And if you're on the go and prefer to use your

00:53:12.989 --> 00:53:16.289
mobile device, you can still use Nostr. Just

00:53:16.289 --> 00:53:18.690
switch to your preferred client, like Damus,

00:53:19.070 --> 00:53:21.309
and pay for zaps using the Wallet of Satoshi

00:53:21.309 --> 00:53:24.289
app. This way you can easily manage your zaps,

00:53:24.389 --> 00:53:26.409
whether you're on your computer or out and about

00:53:26.409 --> 00:53:29.289
with your phone. So, as you can see, sending

00:53:29.289 --> 00:53:32.789
and receiving zaps on Nostr is a breeze. With

00:53:32.789 --> 00:53:35.130
a ZAP compatible lightning wallet, a supported

00:53:35.130 --> 00:53:36.909
client, and the correct lightning address set

00:53:36.909 --> 00:53:39.230
in your Nostr profile, you're all set to start

00:53:39.230 --> 00:53:42.170
zapping away. And don't forget, you have the

00:53:42.170 --> 00:53:45.409
flexibility to pay for ZAPs using different wallets

00:53:45.409 --> 00:53:48.869
or addresses if needed. So go ahead, explore

00:53:48.869 --> 00:53:51.889
the world of ZAPs on Nostr and enjoy the convenience

00:53:51.889 --> 00:53:54.190
and efficiency they bring to your lightning network

00:53:54.190 --> 00:54:00.969
transactions. Happy Zapping! So let's talk about

00:54:00.969 --> 00:54:04.739
NIPs. What are they exactly? Well, NIP stands

00:54:04.739 --> 00:54:07.420
for NOSTER implementation possibility. It's a

00:54:07.420 --> 00:54:10.539
way to document what must, what should, and what

00:54:10.539 --> 00:54:12.920
may be implemented by NOSTER compatible relay

00:54:12.920 --> 00:54:16.019
and client software. Basically, NIPs are the

00:54:16.019 --> 00:54:18.579
documents that outline how the NOSTER protocol

00:54:18.579 --> 00:54:21.239
works. Now, you might be wondering why you should

00:54:21.239 --> 00:54:25.519
care about NIPs. After all, NOSTER is decentralized

00:54:25.519 --> 00:54:28.300
and not owned by a centralized service like Twitter.

00:54:28.719 --> 00:54:30.920
This means that the direction of the protocol

00:54:30.920 --> 00:54:35.079
is up to all of us. Isn't that cool? We can suggest

00:54:35.079 --> 00:54:37.760
and advocate for changes and offer feedback on

00:54:37.760 --> 00:54:41.079
ideas suggested by others. By being an active

00:54:41.079 --> 00:54:43.519
part of the Noster community, you get a say in

00:54:43.519 --> 00:54:45.940
the direction of the network. And guess what?

00:54:46.280 --> 00:54:48.719
NIPs published in the main repository are already

00:54:48.719 --> 00:54:51.860
approved. So if you have some new and exciting

00:54:51.860 --> 00:54:54.960
ideas, you can add them via pull request on that

00:54:54.960 --> 00:54:57.900
repository. But where can you find these NIPs?

00:54:58.039 --> 00:55:00.599
Well, you're in luck. You can see all the current

00:55:00.599 --> 00:55:04.400
NIPs in the Noster NIP repository. It's a treasure

00:55:04.400 --> 00:55:07.199
trove of information about how Noster works and

00:55:07.199 --> 00:55:09.519
what features are being considered for implementation.

00:55:10.159 --> 00:55:12.960
So the NIP repository is the place to go if you

00:55:12.960 --> 00:55:15.320
want to stay up to date with the latest developments

00:55:15.320 --> 00:55:18.440
in the Noster protocol. It's where you can explore

00:55:18.440 --> 00:55:22.079
new ideas, contribute your own suggestions, and

00:55:22.079 --> 00:55:24.949
be a part of the decision -making process. Now

00:55:24.949 --> 00:55:27.269
you might be wondering how these NIPs are structured.

00:55:27.789 --> 00:55:30.590
Generally, each NIP has a unique number and a

00:55:30.590 --> 00:55:33.110
title. This helps to keep things organized and

00:55:33.110 --> 00:55:35.630
makes it easier to reference specific NIPs when

00:55:35.630 --> 00:55:39.250
discussing them. Each NIP also includes an abstract,

00:55:39.590 --> 00:55:41.769
which provides a brief summary of the proposal.

00:55:42.199 --> 00:55:45.659
The body of the NIP contains all the juicy details.

00:55:46.139 --> 00:55:48.780
It outlines the problem or goal that the proposal

00:55:48.780 --> 00:55:51.619
aims to address. It also provides a detailed

00:55:51.619 --> 00:55:54.360
explanation of the proposed solution and any

00:55:54.360 --> 00:55:56.599
potential trade -offs or considerations that

00:55:56.599 --> 00:56:00.079
need to be taken into account. NIPs also include

00:56:00.079 --> 00:56:02.760
a section on motivation, which explains why the

00:56:02.760 --> 00:56:05.380
proposal is important and why it should be considered.

00:56:05.860 --> 00:56:07.659
This is where you can really make a case for

00:56:07.659 --> 00:56:10.159
your ideas and convince others to support them.

00:56:10.489 --> 00:56:13.329
Of course, no proposal is perfect, and that's

00:56:13.329 --> 00:56:15.489
where the section on alternatives and rationale

00:56:15.489 --> 00:56:18.329
comes in. It explores alternative approaches

00:56:18.329 --> 00:56:20.829
to solving the problem and explains why the proposed

00:56:20.829 --> 00:56:24.030
solution is the best option. This helps to ensure

00:56:24.030 --> 00:56:26.230
that the decision -making process is thorough

00:56:26.230 --> 00:56:30.110
and well informed. Finally, NIPs conclude with

00:56:30.110 --> 00:56:33.389
a section on implementation details. This covers

00:56:33.389 --> 00:56:36.349
any technical specifications or requirements

00:56:36.349 --> 00:56:39.110
that need to be met in order to implement the

00:56:39.110 --> 00:56:41.480
proposal. It's like a roadmap for turning the

00:56:41.480 --> 00:56:45.639
idea into a reality. So as you can see, NIPs

00:56:45.639 --> 00:56:48.679
are a crucial part of the Noster ecosystem. They

00:56:48.679 --> 00:56:50.920
provide a platform for collaboration, innovation,

00:56:51.099 --> 00:56:53.940
and community involvement. By contributing to

00:56:53.940 --> 00:56:56.679
NIPs, you have the power to shape the future

00:56:56.679 --> 00:56:59.460
of the Noster protocol and make a real impact.

00:57:00.079 --> 00:57:03.559
So whether you're a developer, a user, or just

00:57:03.559 --> 00:57:05.880
a curious individual, I encourage you to check

00:57:05.880 --> 00:57:08.980
out the Noster NIP repository. Dive into the

00:57:08.980 --> 00:57:12.019
world of NIPs, explore the proposals, and get

00:57:12.019 --> 00:57:14.639
involved in the discussions. Your voice matters,

00:57:15.159 --> 00:57:18.159
and NIPs are the way to make it heard. Remember,

00:57:18.599 --> 00:57:22.199
the Noster community is all about openness, decentralization,

00:57:22.679 --> 00:57:25.440
and democratic decision -making. So don't miss

00:57:25.440 --> 00:57:27.579
out on this amazing opportunity to be a part

00:57:27.579 --> 00:57:30.500
of something big. Browse the NIPs, share your

00:57:30.500 --> 00:57:33.559
ideas, and let's shape the future of Noster together.

00:57:40.940 --> 00:57:43.239
So, you want to know what Noster clients are?

00:57:43.820 --> 00:57:45.920
Well, let me break it down for you in a conversational

00:57:45.920 --> 00:57:49.099
manner. In Noster, a client refers to the app

00:57:49.099 --> 00:57:51.480
or platform that you use to access and interact

00:57:51.480 --> 00:57:53.860
with the protocol. It's kind of like the Twitter

00:57:53.860 --> 00:57:56.340
iOS app or web app that you use to browse through

00:57:56.340 --> 00:57:59.079
Twitter's feed of tweets. Simple, right? Now,

00:57:59.079 --> 00:58:01.079
because the Noster protocol is quite flexible

00:58:01.079 --> 00:58:03.719
and straightforward, different clients have focused

00:58:03.719 --> 00:58:06.159
on implementing various aspects of the protocol

00:58:06.159 --> 00:58:09.789
in slightly different ways. For instance, Some

00:58:09.789 --> 00:58:12.230
clients prioritize having a beautiful and user

00:58:12.230 --> 00:58:15.329
-friendly interface, while others zero in on

00:58:15.329 --> 00:58:18.690
enabling lightning -fast payments. We even have

00:58:18.690 --> 00:58:21.369
clients that cater to creative use cases, like

00:58:21.369 --> 00:58:24.170
playing chess through the NOSTER protocol. Yep,

00:58:24.329 --> 00:58:27.389
you heard that right. Chess on NOSTER. Most of

00:58:27.389 --> 00:58:29.510
the clients that have been developed so far revolve

00:58:29.510 --> 00:58:32.889
around the social media use case. However, we're

00:58:32.889 --> 00:58:35.289
starting to witness more interesting and diverse

00:58:35.289 --> 00:58:37.750
use cases cropping up. Let me give you a few

00:58:37.750 --> 00:58:40.960
examples. First up, we have Jester, a client

00:58:40.960 --> 00:58:43.860
that allows you to play chess on Noster. Imagine

00:58:43.860 --> 00:58:45.960
challenging your friends or even strangers to

00:58:45.960 --> 00:58:48.340
a game of chess on this platform. Pretty cool,

00:58:48.460 --> 00:58:52.380
right? Next, we have Habla, a client that focuses

00:58:52.380 --> 00:58:55.840
on long -form content, much like Medium. So if

00:58:55.840 --> 00:58:58.300
you're into writing or reading lengthy articles,

00:58:58.840 --> 00:59:01.519
Habla might be the client for you. Then there's

00:59:01.519 --> 00:59:04.079
Nostogram, a client that is all about media.

00:59:04.619 --> 00:59:07.599
If you're into sharing and consuming various

00:59:07.599 --> 00:59:10.360
types of media content, Nostrogram is worth a

00:59:10.360 --> 00:59:12.940
look. Last but not least, we have ZapStream,

00:59:13.079 --> 00:59:15.139
a client that brings a Twitch -like streaming

00:59:15.139 --> 00:59:18.380
experience to Nostr. So if you enjoy watching

00:59:18.380 --> 00:59:20.300
live streams and interacting with streamers,

00:59:20.539 --> 00:59:23.199
you should definitely check out ZapStream. Now,

00:59:23.199 --> 00:59:25.019
you might be wondering if you can switch between

00:59:25.019 --> 00:59:28.679
these clients. The answer is yes. Since a client

00:59:28.679 --> 00:59:31.039
is just a way to access the underlying data held

00:59:31.039 --> 00:59:34.039
by relays, you can switch between different clients.

00:59:34.269 --> 00:59:36.730
or even sign into as many clients as you'd like.

00:59:37.130 --> 00:59:39.050
As long as each client is looking at the same

00:59:39.050 --> 00:59:41.269
set of relays for their data, you'll see the

00:59:41.269 --> 00:59:43.630
same messages across all the clients you use.

00:59:44.070 --> 00:59:46.090
But wait, should you enter your private key in

00:59:46.090 --> 00:59:49.309
the client? Generally, it's better not to. While

00:59:49.309 --> 00:59:51.389
most clients that ask for private keys make an

00:59:51.389 --> 00:59:53.949
effort to keep them secure, software is never

00:59:53.949 --> 00:59:57.590
100 % immune to breaches, exploits, or bugs.

00:59:58.110 --> 01:00:00.650
And if your private key gets compromised, it

01:00:00.650 --> 01:00:02.929
means starting from scratch and rebuilding your

01:00:02.929 --> 01:00:06.039
identity in Nostr. Plus, you'll lose your list

01:00:06.039 --> 01:00:08.840
of followers and all your private messages. Not

01:00:08.840 --> 01:00:11.420
something anyone wants to deal with. Now that

01:00:11.420 --> 01:00:13.860
we've covered the basics, let's talk about a

01:00:13.860 --> 01:00:15.539
few of our favorite clients across different

01:00:15.539 --> 01:00:18.280
platforms. If you're accessing Nostra on the

01:00:18.280 --> 01:00:21.840
web, we highly recommend giving Iris a try. It's

01:00:21.840 --> 01:00:24.599
our recommended client, especially for new users.

01:00:25.119 --> 01:00:27.199
And hey, we even have a handy guide that you

01:00:27.199 --> 01:00:30.119
can check out to get started with Iris. For desktop

01:00:30.119 --> 01:00:33.570
users, we have Gossip. a rather opinionated client

01:00:33.570 --> 01:00:35.550
that requires a bit more technical know -how

01:00:35.550 --> 01:00:38.429
to use. But the upside is that Gossip offers

01:00:38.429 --> 01:00:40.710
users more control over how they interact with

01:00:40.710 --> 01:00:43.630
Nostr. So if you're up for a challenge and want

01:00:43.630 --> 01:00:46.050
that extra control, Gossip might be the desktop

01:00:46.050 --> 01:00:49.329
client for you. Now let's move on to iOS. For

01:00:49.329 --> 01:00:52.389
all the iPhone users out there, we proudly present,

01:00:52.449 --> 01:00:55.329
Damus the first and best iOS client for Nostr.

01:00:55.610 --> 01:00:57.650
Trust us, it's worth a try. Just head over to

01:00:57.650 --> 01:01:00.269
our guide to get started with Damus. Last but

01:01:00.269 --> 01:01:03.849
not least, we have Amethyst, a beautiful client

01:01:03.849 --> 01:01:06.769
for Android users. If you're on an Android device,

01:01:06.829 --> 01:01:09.409
give Amethyst a go. We even have a guide available

01:01:09.409 --> 01:01:11.949
on our website to help you get started. And that,

01:01:11.949 --> 01:01:14.230
my friend, sums up what Nostr clients are. From

01:01:14.230 --> 01:01:17.030
web and desktop to iOS and Android, there's a

01:01:17.030 --> 01:01:19.329
client out there for everyone. So why not explore

01:01:19.329 --> 01:01:21.030
and find the one that best suits your needs?

01:01:21.409 --> 01:01:26.989
Happy Nostring. Nostr relays are an essential

01:01:26.989 --> 01:01:30.090
component of the Nostr platform. In this quick

01:01:30.090 --> 01:01:33.050
overview, will explain what relays are, why they

01:01:33.050 --> 01:01:36.530
are important, and how they work. So, what exactly

01:01:36.530 --> 01:01:39.170
are relays? Well, think of them as the backend

01:01:39.170 --> 01:01:42.210
servers for Nostr. They play a crucial role by

01:01:42.210 --> 01:01:44.869
allowing Nostr clients to send messages to them.

01:01:45.349 --> 01:01:48.090
These messages may or may not be stored, but

01:01:48.090 --> 01:01:51.010
they are broadcasted to all other connected clients.

01:01:51.349 --> 01:01:53.670
It's important to note that the world of relays

01:01:53.670 --> 01:01:56.730
is evolving rapidly, so we can expect many changes

01:01:56.730 --> 01:01:59.340
in the future. Due to Noster's decentralized

01:01:59.340 --> 01:02:02.380
nature, it heavily relies on relays to store

01:02:02.380 --> 01:02:04.880
and retrieve data. This means that if you find

01:02:04.880 --> 01:02:07.460
your Noster client running slow, chances are

01:02:07.460 --> 01:02:10.019
it's due to the relays you're using. In such

01:02:10.019 --> 01:02:12.400
cases, it might be worth considering adding or

01:02:12.400 --> 01:02:15.280
removing relays to optimize your client's performance.

01:02:16.059 --> 01:02:18.679
Currently, many relays are offered for free.

01:02:19.349 --> 01:02:22.130
However, with the costs associated with running

01:02:22.130 --> 01:02:24.889
a relay, such as compute, storage, and bandwidth,

01:02:25.349 --> 01:02:27.829
it is widely anticipated that paid relays will

01:02:27.829 --> 01:02:31.190
become the norm in the future. Using paid relays

01:02:31.190 --> 01:02:34.269
has its advantages, especially the higher signal

01:02:34.269 --> 01:02:37.489
quality of users and notes. The proof of work

01:02:37.489 --> 01:02:40.469
involved in paying for relay access helps prevent

01:02:40.469 --> 01:02:42.510
spam accounts from infiltrating the network.

01:02:43.010 --> 01:02:45.269
If you're interested in exploring paid relays,

01:02:45.630 --> 01:02:47.489
you can find an up -to -date list with details

01:02:47.489 --> 01:02:50.119
on Relay Exchange. Now, you might be wondering

01:02:50.119 --> 01:02:52.260
where you can find a comprehensive list of all

01:02:52.260 --> 01:02:55.000
relays. The best resource we have found for browsing

01:02:55.000 --> 01:02:57.400
and assessing the speed of known relays is the

01:02:57.400 --> 01:03:00.420
Noster Watch site. This site provides valuable

01:03:00.420 --> 01:03:03.000
information and insights on different relays,

01:03:03.239 --> 01:03:05.460
making it easier for you to choose the ones that

01:03:05.460 --> 01:03:08.239
suit your needs. But what happens if all the

01:03:08.239 --> 01:03:11.039
relays you use suddenly stop working? Unfortunately,

01:03:11.219 --> 01:03:13.960
in such a scenario, all your posts become unretrievable.

01:03:14.239 --> 01:03:16.460
That's why Noster allows users to connect to

01:03:16.460 --> 01:03:18.880
multiple relays, ensuring some degree of backup.

01:03:19.480 --> 01:03:22.539
However, if being uncensorable is a top priority

01:03:22.539 --> 01:03:25.380
for you, running your own personal relay is highly

01:03:25.380 --> 01:03:28.179
recommended. This way, you always have a copy

01:03:28.179 --> 01:03:30.800
of all your Noster posts and interactions for

01:03:30.800 --> 01:03:33.659
all time. It provides a greater level of control

01:03:33.659 --> 01:03:36.820
and security over your data. While running your

01:03:36.820 --> 01:03:39.119
own relay may not be worth the hassle for most

01:03:39.119 --> 01:03:42.139
people, It is an option for those who are technically

01:03:42.139 --> 01:03:44.559
inclined or want to establish a private relay

01:03:44.559 --> 01:03:48.300
for a small group. At the moment, we are working

01:03:48.300 --> 01:03:50.440
on a guide to help you set up your own Noster

01:03:50.440 --> 01:03:53.340
Relay. In the meantime, you can check out the

01:03:53.340 --> 01:03:55.860
guide by Andre Nevis, which provides step -by

01:03:55.860 --> 01:03:59.300
-step instructions on how to do it. In conclusion,

01:03:59.980 --> 01:04:02.039
Noster Relays are the backbone of the Noster

01:04:02.039 --> 01:04:05.099
platform. They enable communication between Noster

01:04:05.099 --> 01:04:08.039
clients, store messages, and broadcast them to

01:04:08.039 --> 01:04:10.940
other connected clients. As the landscape of

01:04:10.940 --> 01:04:14.179
relays continues to evolve, paid relays are expected

01:04:14.179 --> 01:04:17.119
to become more prevalent. While many relays can

01:04:17.119 --> 01:04:20.760
be accessed for free, utilizing paid relays offers

01:04:20.760 --> 01:04:23.619
benefits such as higher signal quality. If you

01:04:23.619 --> 01:04:25.860
want to explore relays or assess their speed,

01:04:26.400 --> 01:04:29.380
Nosterwatch is a valuable resource. And if you

01:04:29.380 --> 01:04:32.719
want to ensure your data's security and be uncensorable,

01:04:33.280 --> 01:04:35.099
setting up your own personal relay may be a wise

01:04:35.099 --> 01:04:44.579
choice. All right, let's dive into the world

01:04:44.579 --> 01:04:47.360
of relay implementations. Whether you're a curious

01:04:47.360 --> 01:04:49.960
developer or someone planning on running a relay

01:04:49.960 --> 01:04:52.860
yourself, this list of known implementations

01:04:52.860 --> 01:04:55.659
of the Nostr Relay Spec will surely pique your

01:04:55.659 --> 01:04:58.860
interest. And the best part? Relays are application

01:04:58.860 --> 01:05:01.059
agnostic, meaning you can run your own relay

01:05:01.059 --> 01:05:03.599
or utilize any of the public instances available.

01:05:04.059 --> 01:05:06.800
Let's start with Go. One notable implementation

01:05:06.800 --> 01:05:09.420
is the Relayer Basic, a simple reference relay.

01:05:09.800 --> 01:05:12.699
Built on top of the Relayer framework, this relay

01:05:12.699 --> 01:05:15.880
is backed by Postgres. It was created as a demo

01:05:15.880 --> 01:05:19.039
to showcase how to construct custom relays. It's

01:05:19.039 --> 01:05:21.159
a great starting point if you're new to relays

01:05:21.159 --> 01:05:24.239
or want to understand the inner workings. Moving

01:05:24.239 --> 01:05:27.619
on to C++, we have Stirfry, an intriguing relay

01:05:27.619 --> 01:05:30.039
implementation that dares to be database -less.

01:05:30.659 --> 01:05:33.539
With its C++ foundation, Stirfry takes a unique

01:05:33.539 --> 01:05:35.780
approach by eliminating the need for a database.

01:05:36.480 --> 01:05:38.619
Definitely an interesting choice for those who

01:05:38.619 --> 01:05:41.280
prefer a lightweight implementation. For the

01:05:41.280 --> 01:05:44.480
C -Hash enthusiasts out there, Anoster is a C

01:05:44.480 --> 01:05:47.260
-Hash relay that you might find appealing. With

01:05:47.260 --> 01:05:50.340
its implementation in C -Hash, Anoster provides

01:05:50.340 --> 01:05:52.940
a relay solution tailored specifically for the

01:05:52.940 --> 01:05:55.500
C -Hash community. It's worth exploring if you're

01:05:55.500 --> 01:05:58.099
comfortable working with C -Hash and want a relay

01:05:58.099 --> 01:06:00.059
that aligns with your programming language of

01:06:00.059 --> 01:06:02.360
choice. Now let's explore the world of Rust,

01:06:02.940 --> 01:06:05.699
if you're a Rustacean. you'll be delighted to

01:06:05.699 --> 01:06:08.239
know that there are a couple of relay implementations

01:06:08.239 --> 01:06:12.940
for you. First, we have NostrR's Relay, a minimalistic

01:06:12.940 --> 01:06:16.400
Rust Relay that uses Sqlite to store data. Its

01:06:16.400 --> 01:06:18.619
simplicity makes it an attractive option for

01:06:18.619 --> 01:06:20.719
those who prefer a lightweight and straightforward

01:06:20.719 --> 01:06:23.639
implementation. Another Rust implementation is

01:06:23.639 --> 01:06:26.340
Soster. This particular relay is private, meaning

01:06:26.340 --> 01:06:28.539
it's used to save all notes from one pub key

01:06:28.539 --> 01:06:30.599
and publish them to anyone who requests them.

01:06:31.280 --> 01:06:33.659
If privacy and data control are priorities for

01:06:33.659 --> 01:06:36.570
you, Soster might be the perfect fit. For those

01:06:36.570 --> 01:06:39.210
who embrace Node .js and TypeScript, Nostream

01:06:39.210 --> 01:06:41.570
is a Noster Relay implementation that you should

01:06:41.570 --> 01:06:44.150
definitely check out. Originally named Noster

01:06:44.150 --> 01:06:46.550
Tease Relay, it has been reborn as Nostream.

01:06:47.329 --> 01:06:49.809
Backed by PostgreSQL, this relay written in TypeScript

01:06:49.809 --> 01:06:52.150
provides a solid foundation for your relay needs.

01:06:52.730 --> 01:06:54.769
It's especially useful if you're already familiar

01:06:54.769 --> 01:06:57.630
with Node, DayJs, and TypeScript. If you're involved

01:06:57.630 --> 01:06:59.570
in the Mines community, you'll be thrilled to

01:06:59.570 --> 01:07:01.650
know that there is a Mines Noster Relay available.

01:07:02.119 --> 01:07:04.519
This particular relay is designed specifically

01:07:04.519 --> 01:07:07.400
for the open source social network Mines. It

01:07:07.400 --> 01:07:09.780
enables seamless relay functionality within the

01:07:09.780 --> 01:07:12.059
Mines platform, enhancing the user experience.

01:07:12.719 --> 01:07:15.059
And speaking of Mines, we have the Mines engine,

01:07:15.380 --> 01:07:18.400
Nostr. This is relevant Mines API code that allows

01:07:18.400 --> 01:07:21.059
you to read and write Mines posts using Nostr.

01:07:21.739 --> 01:07:23.559
It's an essential component for those looking

01:07:23.559 --> 01:07:26.500
to integrate Nostr into their Mines powered applications

01:07:26.500 --> 01:07:29.719
or projects. For Clojure enthusiasts, there's

01:07:29.719 --> 01:07:33.219
me .untether .nostrrelay, a relay implementation

01:07:33.219 --> 01:07:36.019
written in Clojure. With its Clojure foundation,

01:07:36.239 --> 01:07:38.539
this relay brings the expressive power of Clojure

01:07:38.539 --> 01:07:41.519
to the world of relays. If you're a fan of Clojure's

01:07:41.519 --> 01:07:44.039
elegance and functional programming, you'll likely

01:07:44.039 --> 01:07:46.639
appreciate this implementation. Next, we have

01:07:46.639 --> 01:07:49.780
Nostropy, a Python implementation that goes beyond

01:07:49.780 --> 01:07:52.699
just being a relay. It provides a comprehensive

01:07:52.699 --> 01:07:55.619
suite of tools, including a relay, client, and

01:07:55.619 --> 01:07:58.219
other useful tooling, all implemented in Python.

01:07:58.539 --> 01:08:00.860
If you're already working with Python and are

01:08:00.860 --> 01:08:02.880
looking for an all -in -one package for your

01:08:02.880 --> 01:08:05.980
Nostr needs, NostraPy is an excellent choice.

01:08:06.480 --> 01:08:09.139
Continuing with Python, we have Nostr underscore

01:08:09.139 --> 01:08:12.179
relay, another relay implementation written in

01:08:12.179 --> 01:08:15.179
Python. This time, it is backed by Sklite, making

01:08:15.179 --> 01:08:17.039
it a lightweight option for those who prefer

01:08:17.039 --> 01:08:20.260
simplicity. This implementation emphasizes efficiency

01:08:20.260 --> 01:08:23.020
and ease of use, which is perfect for those with

01:08:23.020 --> 01:08:25.819
minimal resource requirements. Last but not least,

01:08:25.880 --> 01:08:29.649
we come to Kotlin. Noster Poster Relay is a Kotlin

01:08:29.649 --> 01:08:31.829
-based relay implementation that offers support

01:08:31.829 --> 01:08:35.170
for both Sklite and Postgresql. If you're part

01:08:35.170 --> 01:08:37.350
of the Kotlin community and want a relay that

01:08:37.350 --> 01:08:39.350
seamlessly integrates with your preferred database

01:08:39.350 --> 01:08:42.210
solution, Noster Poster Relay has got you covered.

01:08:42.710 --> 01:08:45.989
And finally, we have Noster, a Noster relay implemented

01:08:45.989 --> 01:08:49.430
in Kotlin. What sets Noster apart is its support

01:08:49.430 --> 01:08:53.310
for Postgres and metrics via micrometer. If monitoring

01:08:53.310 --> 01:08:55.689
and comprehensive metrics are priorities for

01:08:55.689 --> 01:08:58.949
your relay implementation, Nostr is worth considering.

01:08:59.350 --> 01:09:01.010
Wow, that was quite a journey through various

01:09:01.010 --> 01:09:04.630
relay implementations. From Go to C++ to C -Hash

01:09:04.630 --> 01:09:07.609
to Rust, Node, JDesk, TypeScript, Clojure, Python,

01:09:07.810 --> 01:09:10.489
and Kotlin, there's truly a relay implementation

01:09:10.489 --> 01:09:13.010
for every developer out there. Whether you're

01:09:13.010 --> 01:09:15.770
a fan of simplicity, privacy, specific programming

01:09:15.770 --> 01:09:18.989
languages, or comprehensive tooling, this list

01:09:18.989 --> 01:09:21.729
has something for everyone. So go ahead, explore

01:09:21.729 --> 01:09:23.970
these implementations, and find the one that

01:09:23.970 --> 01:09:28.500
best suits your needs. Happy relaying. Happy.

01:09:31.760 --> 01:09:34.880
So let's talk about the Nostr repository. It's

01:09:34.880 --> 01:09:37.720
basically the central hub for all things Nostr.

01:09:37.960 --> 01:09:40.300
While it may not be the most jam -packed repository

01:09:40.300 --> 01:09:43.119
out there, it does house Ify at Jeff's original

01:09:43.119 --> 01:09:45.939
reasoning behind creating Nostr. So if you're

01:09:45.939 --> 01:09:48.560
interested in diving deeper into the why behind

01:09:48.560 --> 01:09:52.220
Nostr's existence, this is the place to go. Next

01:09:52.220 --> 01:09:54.939
up, we have Nostr relays. Now there are a few

01:09:54.939 --> 01:09:56.880
different types of relays in the Nostr realm.

01:09:57.229 --> 01:10:00.149
One of them is PurplePag .us, which is a special

01:10:00.149 --> 01:10:02.850
kind of relay. Then there's Noster .Watch, which

01:10:02.850 --> 01:10:05.170
is like the go -to source for all the info you

01:10:05.170 --> 01:10:07.829
need on all the known relays out there. And if

01:10:07.829 --> 01:10:09.710
you're curious about currently operating paid

01:10:09.710 --> 01:10:12.750
relays, Relay Exchange has got you covered. But

01:10:12.750 --> 01:10:15.149
here's where things get really interesting. There's

01:10:15.149 --> 01:10:17.770
this project called Noster .Wine's Filter Relay.

01:10:18.000 --> 01:10:20.960
And what it does is aggregates reading and writing

01:10:20.960 --> 01:10:24.060
from and to several other major relays. Its main

01:10:24.060 --> 01:10:26.039
goal is to bridge the gap between public and

01:10:26.039 --> 01:10:29.100
private relays. Pretty cool, right? If you want

01:10:29.100 --> 01:10:31.800
to learn more about this and other relay implementations,

01:10:32.140 --> 01:10:34.640
check out the page dedicated to relay implementations.

01:10:35.000 --> 01:10:37.500
Now let's talk about search and data. Gnoster

01:10:37.500 --> 01:10:39.920
.band is like the search engine for all things

01:10:39.920 --> 01:10:43.239
Gnoster. It can help you find new users to follow

01:10:43.239 --> 01:10:45.659
or even track down that note you saw floating

01:10:45.659 --> 01:10:48.079
around a while back. And if you're into high

01:10:48.079 --> 01:10:50.779
level data about the growth of the Nostr network,

01:10:51.399 --> 01:10:54.420
network stats, which is also run by Nostr .band,

01:10:54.880 --> 01:10:56.699
is where it's at. It gives you a pretty good

01:10:56.699 --> 01:10:58.699
overview of how things are looking in the Nostr

01:10:58.699 --> 01:11:01.840
world. Oh, and have you heard of ZapLife? It's

01:11:01.840 --> 01:11:04.560
an aggregation of all the Zaps across Nostr in

01:11:04.560 --> 01:11:07.319
the last several hours. It's basically the Zap

01:11:07.319 --> 01:11:09.899
leaderboard. So if you're curious about the most

01:11:09.899 --> 01:11:12.119
recent Zaps and who's making waves in the Nostr

01:11:12.119 --> 01:11:15.010
community, make sure to check it out. Now let's

01:11:15.010 --> 01:11:17.630
move on to long -form content. If you're in the

01:11:17.630 --> 01:11:19.949
mood for some deep conversations and discussions,

01:11:20.770 --> 01:11:23.210
you might want to check out Habla. It's a platform

01:11:23.210 --> 01:11:25.430
where you can engage in longer conversations

01:11:25.430 --> 01:11:28.189
and explore different topics. And if you're more

01:11:28.189 --> 01:11:30.689
into reading blogs, well, Blogstack is the place

01:11:30.689 --> 01:11:32.909
to be. It's a collection of interesting and thought

01:11:32.909 --> 01:11:35.510
-provoking blogs for all you avid readers out

01:11:35.510 --> 01:11:37.649
there. Switching gears for a moment, let's talk

01:11:37.649 --> 01:11:40.210
about badges. If you're into collecting badges

01:11:40.210 --> 01:11:43.260
or showing off your achievements, badges .page

01:11:43.260 --> 01:11:45.800
is where you'll find a variety of badges related

01:11:45.800 --> 01:11:48.680
to Nostr. It's a fun way to showcase your involvement

01:11:48.680 --> 01:11:51.239
in the Nostr community and your love for all

01:11:51.239 --> 01:11:54.100
things Nostr. And in case you're looking for

01:11:54.100 --> 01:11:56.539
more, there's Awesome Nostr. It's like a treasure

01:11:56.539 --> 01:11:59.340
trove of links related to Nostr clients, relay

01:11:59.340 --> 01:12:01.979
implementations and more. So if you want to explore

01:12:01.979 --> 01:12:04.479
further and discover even more Nostr related

01:12:04.479 --> 01:12:08.479
resources, Awesome Nostr is your one stop shop.

01:12:08.960 --> 01:12:10.880
Lastly, before we wrap things up, we want to

01:12:10.880 --> 01:12:13.579
ask for your support. We would greatly appreciate

01:12:13.579 --> 01:12:15.380
it if you could show us some love on Fountain

01:12:15.380 --> 01:12:20.319
.com, Noster .Build, Spotify, Amazon Music, RSS

01:12:20.319 --> 01:12:24.579
.com, Pandora, Samsung Podcasts, Apple iTunes,

01:12:25.039 --> 01:12:28.579
iHeartRadio, and many more platforms. You can

01:12:28.579 --> 01:12:30.800
do this by adding a like, sharing our podcast,

01:12:30.939 --> 01:12:32.939
or subscribing to the Bitcoin Street Journal.

01:12:33.460 --> 01:12:35.960
Your support means the world to us, and we thank

01:12:35.960 --> 01:12:37.939
you for taking the time to listen and support

01:12:37.939 --> 01:12:40.609
us. That's it for today's episode. We covered

01:12:40.609 --> 01:12:43.710
the Noster repository, relays, search and data,

01:12:44.189 --> 01:12:46.630
long -form content, badges, and some other cool

01:12:46.630 --> 01:12:49.609
Noster resources. We hope you found this information

01:12:49.609 --> 01:12:52.270
useful and that you're excited to dive into the

01:12:52.270 --> 01:12:54.930
world of Noster. Until next time, take care and

01:12:54.930 --> 01:13:10.789
keep exploring. On today's episode, we covered

01:13:10.789 --> 01:13:13.090
a range of topics including Bitcoin adoption

01:13:13.090 --> 01:13:17.390
by corporations, SEC delays, cryptocurrency fines,

01:13:17.970 --> 01:13:21.789
Ethereum updates, AI controversies, and the features

01:13:21.789 --> 01:13:24.689
of the Nostr protocol. Thanks for listening to

01:13:24.689 --> 01:13:26.789
today's episode. I'll see you guys at the next

01:13:26.789 --> 01:13:28.149
one and don't forget to subscribe.