正在加载视频...

视频加载失败

Introducing Bittensor Auth Gateway. Sign in with Bittensor. It's a standard OAuth2/OIDC login with a key difference - identity is backed by the chain. Your wallet is your identity and your on-chain state is your permissions. Open source - or use the Taostats hosted version Works with any OAuth2...

52,408 次观看 • 6 个月前 •via X (Twitter)

19 条评论

taostats τ 的头像
taostats τ6 个月前

Bittensor has rich on-chain identity — miners, validators, subnet owners, stake levels. But every tool you build has to reinvent auth from scratch. Traditional login tools have no concept of wallets or on-chain roles. Result: we're all building custom auth with manual allowlists - access that doesn't follow chain state.

taostats τ 的头像
taostats τ6 个月前

Bittensor Auth Gateway bridges the two worlds. 1/ Your Customer requests login 2/ Redirect to Bittensor Auth 3/ User signs with wallet 4/ On-chain state verified 5/ JWT issued — hotkey, coldkey, scope, subnet, stake 6/ App grants access

taostats τ 的头像
taostats τ6 个月前

Real things you can build with this: 🔧 Headless miner auth — CLI login via Device Code Flow. No browser. 📊 Validator dashboards — access auto-revokes on deregistration. 🎯 Token-gated content — different content at different stake thresholds. 🏠 Subnet owner portals — verify ownership automatically. No allowlist.

taostats τ 的头像
taostats τ6 个月前

The chain IS the database. * Register → you get access. * Deregister → access lapses at next epoch. No user table. No allowlist. No manual offboarding. Chain state is truth.

taostats τ 的头像
taostats τ6 个月前

Everything you need to get started: → Docs + hosted version: → Self-host: MIT licensed. No SDK. Works with any OAuth2 library. Ship it.

NameTensor 的头像
NameTensor6 个月前

👏 👏 👏

brian combs 的头像
brian combs5 个月前

I can't access the app or my wallet. Please tell me what's going on.

Miki 的头像
Miki6 个月前

🫡 ahead of the game

Akin Aguda 的头像
Akin Aguda6 个月前

Incredibly fire video 🔥🔥🔥

Jemmy (τ) 的头像
Jemmy (τ)6 个月前

clever

Not sure yet 的头像
Not sure yet4 个月前

Why isn’t their a slippage setting on your app to prevent sandwich attacks. I am a small holder and have been done 4 times in the past 24 hours losing 2 of what was my remaining 12tao. This is Criminal and ridiculous. Don’t go ANYWHERE NEAR TAOSTATS APP!!!!!!

Bittensor Digger 🇦🇺 的头像
Bittensor Digger 🇦🇺3 个月前

Will the purchases made on @krakenfx run through the alpha charts? Atm I don’t see anything that is corresponding back over to taostats. I guess question is — are the purchases in the same pool?

Lucky 的头像
Lucky6 个月前

keep building 👍

Dogelayer 的头像
Dogelayer6 个月前

I'm here to show some support for our friend

Not sure yet 的头像
Not sure yet4 个月前

No transaction or chart update has happened in over 3 hours now on taostats. Any ideas? @taostats This happens like clockwork every weekend. However, never for this length of time.

Drip 的头像
Drip5 个月前

Next integrate @nametensor !!!

Not sure yet 的头像
Not sure yet4 个月前

@taostats server is still down, all up, it’s probably been down half the day. No charts will update, no transaction show up. Luckily this time we are able to see our funds.

hgabe796 的头像
hgabe7964 个月前

yo, your dms are closed, dm me pls

SubScreener (τ) 的头像
SubScreener (τ)6 个月前

You guys are killing it at Taostats! ⚡

相关视频

You can't pretend you care about security if you are still sharing API tokens in .env files or sharing SSH keys. This might be good enough to provide simple access to a resource, but it's a horrible way to do security when it really matters. Look into "Identity-Based Access". The state of the art today is Identity-Based Access. With traditional security, you have to present a key to get access to the resource (an API key, a password, or an SSH key). These are long-lived keys you need to keep secret somehow. If somebody steals your key, they become you and get the same access you had. With Identity-Based Access, you need to prove who you are instead. If you are a human, you can prove this with a passkey, SSO with Google or GitHub, or Multi-Factor Authentication. If you are a computer, you can use AWS IAM, Kubernetes, a cloud service account, or any other trusted environment. Once the system verifies your identity, it checks your permissions and gives you a short-lived credential. Prove identity → Permissions → Short-lived credential → Access The difference here is huge, because those credentials are: • Short-lived • Tied to a specific identity • Scoped to specific permissions • Automatically expired • Much easier to audit In practice, implementing this is as simple as integrating with Teleport, which will handle everything for you. Here is a full explanation of how Teleport works and how you can start using it: Thanks to the Teleport team for partnering with me on this post.

Santiago

20,971 次观看 • 2 个月前