Question for all Ethereum enthusiasts around here: Say you have a smart contract to which users can submit transactions for which they have to pay gas fees. You'd like to offer them the service of paying these gas fees on their behalf so they don't have to go go through the trouble of having to get their own ETH. But it's also important that msg.sender always be the address of the privkey with which the user signed the underlying transaction (rather than say the address of the payor). Is there an (easy?) way to do this? #ethereum

You don't need key signing parties to bind pubkeys to their owners. What you need are pubkeys that have an association with their owners which remains stable over the long term. That's because, given enough time, you'll always have plenty of opportunity to observe all kinds of cues and signals that will tell you who is behind a pubkey, at least to the extent to which the owner wants to reveal that information to you. For example, over time you'll be able to tell whether the owner is a bot or a human, what their interests are, their writing style, what communities they are part of etc. And if they want you to know their name or other "personally identifiable information," there will be almost always be easy mechanisms by which they can convince you that they are who they say they are. It seems very unlilely that AI's ability to impersonate will change this, either now or in the future.

The pubkey @npub10ukg...x0x9 has never ever signed a single Nostr event. Yet that pubkey has recently gained its first real-life follower. I admittedly don't know whether they'll decide to stick around or not. But it's a small milestone in the (very early) history of Inkan.