byte

users should never have to copy and paste addresses. web2 doesn't have this problem. just make cryptographically sane human-readable identifiers. most of this stuff is just such an old way of thinking (both in web2 and web3)

kinda funny seeing everyone on the timeline constantly amazed by ai coding, it's like watching myself from three years ago. back then, though, you had to pay more attention to syntax and library hallucinations, which probably is what taught me how to talk to LLMs from a young age

@0xTaylor_ @itsbirdo_ you should get a small allowance for statement store, I know there's an allowance faucet for bulletin on testnet since that's the rest route but this is already working afaik. someone can correct me if I'm wrong

@0xTaylor_ @itsbirdo_ it is built. if you download the devnet polkadot app and create an account, you are granted allowance

Few understand the gravity of what we have achieved over the last year. We have built the foundation for a new permissionless internet, true to the values of real Web3.

@0xTaylor_ @itsbirdo_ the authorization is granted automatically on the fulfillment of certain conditions, such as levels of personhood

IDK, this doesn't sound very permissionless. "Second, Levity requires explicit authorization to write. This is a deliberate design choice: not everyone can upload. Authorization is granted by a privileged origin, which keeps the network from becoming an open dump and ensures the content stored there has been sanctioned by someone accountable for it.`" Source: parity.io/blog/inside-le…

@KarimJDDA the problem is that anything that is widely regarded as tasteful becomes slop as soon as it is too widely adopted, so the taste window is always shifting, and it is shifting more quickly than ever before

We need a compiler for "taste".

business idea: free funds for rogue models

@cavemanloverboy it's not very far, it gets super slow if your phone can't make it out well because of error correction (our offline signer works like this)

wonder what the range is on this

@alice_und_bob @dotsumo_ and create forum threads if you want to discuss ideas or tech? anything is possible

@alice_und_bob @dotsumo_ you can do that too, the devnet issue tracker is just for the operated devnet (like rpcs are down) if there is an issue with the software itself feel free to open issues in the respective repos

I’m sorry but I find this statement super disrespectful towards the devs you want to try out your tech. It’s not: „hey let’s create a space together where we can talk about this“ It’s: „you can file a ticket here“ This is not how you build community. I know you need these legal disclaimers, but there still needs to be a venue (dare I say plaza) for the community to meet and discuss. Something like a forum… a Polkadot Forum

@aliceisplaying @Bewinxed 4.6 is the best

@Bewinxed hm. may be time to revisit good old 4.6

i can't trust opus 5 one bit so far it seems okay for a fable subagent

@llamaonthebrink you can always delegate to a different one or override your vote

@byteboro If the AI doesn’t vote on behalf of users based on the users preferences what’s the point

I kind of refuse to accept that onchain governance is dead. Actually, I personally think it’s on the verge of being reborn. Governance failed in the past because we lied. Uniswap lied. Curve lied. Aave lied. Maker lied. They were all liars. They told us “anyone can participate.” Except they never mentioned the massive elephant prerequisite in the room: You had to be capable of coding and intricately understand the ins and outs of each protocol. But that’s no longer the case. Today, with LLMs, none of that is needed. Anything you need to know about the protocol can be enumerated to you by AI. And any code that needs to be written can be written by AI. The argument against human-directed-AI-governance 2 years ago was that LLMs sucked at writing safe code. Fast forward to today, and ppl are scared to touch anything that’s human written because Fable will huff and puff and blow it all down. The excuse of the past are no longer valid. We can finally fulfil the original promise of onchain governance. Each and every token holder can now be mobilized with AI governance representation. Participation rates should be >90%. The ENS DAO debacle shouldn’t have been possible in this day and age. The Aavechan / Aave DAO conundrum could have been avoided, or at the very least represented the voice of all token holders. You say gov-tokens are dead. I say long live aiGov-tokens. We are not the same.

@llamaonthebrink we had ai agents in polkadot gov voting with hundreds of thousands of tokens at one point, still have ai summaries on all proposals, everything is legible. people don't vote

@byteboro It has never been practiced

@thewhiterabbitM lite personhood is available to anyone whi registers in the polkadot app, it grants you a smaller allowance than full personhood. but that's how chat and small bulletin uploads work, you do get free allocation out of the box

Honest caveats: it's an alpha devnet, rough edges everywhere, so we filed 12 findings for the devs (DEVFEEDBACK.md in the repo). And personhood is granted to a handful of accounts today, so every app (mine included) runs in demo mode. The killer feature isn't public yet.

Full disclosure: I'm not a developer. But with Claude Code, people like me can now actually build and ship to test a platform instead of just reading whitepapers. So take everything below with a grain of salt, it may be complete nonsense. 🧵

@alice_und_bob @thewhiterabbitM it's a known issue

@thewhiterabbitM I saw some button contracts deployed. ATM I think the biggest UX blocker is the many approvals

What is Polkadot Products? It was lovely finally trying it out last night and a lot clicked for me. It’s the first time something feels like true Web3 (a bit like the ChatGPT moment a few years ago made AI finally click) A thread to explain it 👇🧵

@zerokn0wledge_ @Ethanoshi @alice_und_bob @Polkadot still some rough edges as it's just gone up on the devnet, any feedback is welcome!

@Ethanoshi @alice_und_bob @Polkadot Unfortunately doubt it, but will report back when I got to give it a try

Looks like @alice_und_bob is making me revisit the @Polkadot ecosystem again for the first time in a long time. My Saturday night is a vibe-coding session anyhow, so might just fit Polkadot Products devnet into it as well. Ngl, the ecosystem is pretty much ded bc they literally never managed to make any app mobilize users at scale + a lot of the gud tech stayed a cool concept with no real traction. But when I entered crypto back in 2019/20 Polkadot's vision for a cohesive multichain network of app-specific chains, its vision for heterogenous sharding and cross-chain interoperability/composability was one of the things that rly got my nerdy mind hooked on web3. Also laid the foundation for my mental model to understand the rollup-centric roadmap, the modular thesis and generally blockchain scaling/architecture topics in the years after that. Not a believer or holder anymore tbh (too many things went very wrong over there), but will always have a soft spot for Polkadot. Should be fun anyhow and who knows, maybe they finally bring smth to market here that will matter to a real audience of users.

@IoTcryptochain here you can see him deploying a 100% polkadot-hosted decentralized website while messaging his agent on polkadot chat, through his polkadot id, on the polkadot app, which is also fully decentralized. sounds kinda cool to me

@byteboro What is cool about that?

super cool stuff happening on the polkadot product dev net already

@alice_und_bob it's possible you used it all, but you should just be able to overwrite the same cids or delete them to free it

@byteboro i think i am not allowed to do anything anymore today i get "Submit failed, no allowance set for account" everywhere all the time now :D

Friday Night Vibe Coding the new Polkadot Product Devnet 🤓🧑‍💻 x.com/i/broadcasts/1…