Good proposal, and I think there’s a natural pairing here: flagging a neighbouring hub application ( Devcon 8 India: Sovereign Infrastructure Hub ) rather than a competing one.
I’m posting an intention this week for a “Sovereign Infrastructure” hub, reframed from the “Node Operators” hub of previous editions. Short version: self-custody answered “not your keys, not your coins.” We’re aimed at its quieter twin: “not your node, not your data.” Light clients, node tooling on hardware people already own, and wallets that verify chain data rather than trust a provider for it.
Which puts us squarely alongside two things already in your scope.
Transaction verification: an attendee who has learned to read a transaction carefully is still reading a screen populated by an RPC endpoint they don’t control. The provider chooses what they’re shown. Same for checking token approvals through a block explorer — the check is only as honest as whoever served the page. Drainers and phishing are the attacker in your face; a filtered or lying data source is the quiet one, and it defeats a well-trained user rather than a careless one.
I’d happily co-run a session on that if it appeals: “what your wallet shows you, and who told it that” — practical, and it lands better with an audience already thinking about verification than with one that isn’t. We’ll have light client maintainers in the room who can show the difference live.
Otherwise: we’d send anyone asking “how do I know what my wallet is telling me is true” to you, and you’d have somewhere to send people who want to fix the data path. Happy to coordinate scheduling so we’re not drawing on the same audience at the same hour.
Good luck with the proposal!