DANIEL

Second IRL event this year. More to come! ❤️

Announcement. ↯

When you talk about regulated crypto futures in the U.S., you’re talking about a very small, very exclusive club. These are assets that have made it past compliance walls, institutional scrutiny, and regulatory requirements. The big names like: > Bitcoin > Ethereum > Solana A

Placed two bets with my bonus (0.5 $INJ each) and got liquidated. Thanks for playin. <3

Been invited to speak at “Web3 On Campus” hosted by the Student Union Government, University of Uyo. Tomorrow, 18th April. Plan to attend! ❤️

The X Cashtag is here for $INJ 🥷

After a few days of XION Analyst #14 being in the field, $XION experienced a sudden explosive pump to $0.19–$0.20 Immediately followed by a hard rejection + sell-off After the dump, price gradually trended downward and formed a base around $0.10–$0.11 And just recently another

“What do you do for fun?”

Looks like it's business as usual with the $INJ community buyback as April's round (228) ends with +21.32% ROI. Just claimed my rewards and it all amounts to about 42 $INJ profit. Massive skill issue if you miss next month's round.

Ignore this and you’re potentially delaying your project’s growth by months or even years. Apply now. ↯

OAuth2 primarily lets apps access data. XION takes it a step further by letting apps do things with that access. So asides just authorization. They’re using it as a gateway to: ➪ Payments ➪ Credentials ➪ Tamper-proof records All through the same flow. (7/10)

At Twitter, engineer Blaine Cook was trying to solve this. At the same time, another company (Ma.gnolia) had the same issue. They came together and realized there was no open standard for letting apps access user data safely (4/10)

The flow is simple. The user signs into your app using something familiar: Google, Apple etc. After login, your app receives an access token which your app uses to make requests. XION then goes on to execute actions behind the scenes. After which you will get a response

All of it is explained better in this video. (9/10)

Just when we thought we have seen it all with the Epstein File Clearance System. The XION Dev team shipped again. Learn more: (10/10)

So what did they do? They formed a small working group (2007) Included people from: ◦Google ◦AOL ◦Twitter This eventually led to the birth of OAuth 1.0 in 2007 Subsequently in 2012, OAuth 2.0 ce in to play See this for the differences between both: (5/10)

Fast forward to today… OAuth2 is now the default language of authorization on the internet. Every dev knows it. Every product stack depends on it. Which explains why XION decided to build on it. (6/10)

The trace of its existence goes as far back as 2006, where developers had problem like: - Apps needing access to user data - But the only way was collecting usernames & passwords Which was quite dangerous. (3/10)

OAuth ⇄ Open Authorization It’s an open standard that allows apps to access your data without seeing your password. So you don’t give your “password”, but rather what you give is “permission”. (2/10)