accountless.eth pfp
accountless.eth
@accountless.eth
"Many users end up with separate smart accounts for each application due to inadequate rediscovery mechanisms. Smart accounts created with one provider may not be compatible with those generated using another." "7715 resembles a JWT token. Users sign off on what an application can do with their account, all offchain, then the app co-signs every action against the JWT which is enforced onchain." web 3 is powered by jwt https://blog.getpara.com/the-10000-account-problem/
1 reply
0 recast
2 reactions

James pfp
James
@theref
Do you think there's benefit in having a decentralized JWT issuer?
1 reply
0 recast
0 reaction

accountless.eth pfp
accountless.eth
@accountless.eth
devil 😈 is in the details
1 reply
0 recast
0 reaction

James pfp
James
@theref
Yeah for sure. But is it worth figuring those details out?
1 reply
0 recast
0 reaction

accountless.eth pfp
accountless.eth
@accountless.eth
i dunno how to answer that question - but here is a neat metaphor https://docs.zerodev.app/blog/session-keys-are-the-jwts-of-web3
1 reply
0 recast
1 reaction

James pfp
James
@theref
Thanks, that's a really great article
2 replies
0 recast
1 reaction

accountless.eth pfp
accountless.eth
@accountless.eth
yea. check out their blog and or docs. great builders. major contributions to the industry.
1 reply
0 recast
0 reaction

accountless.eth pfp
accountless.eth
@accountless.eth
name chain from ens could play a neat role there. w the records fields for ens if they developed those the goal should be zero trust imo, and constantly striving towards that end
1 reply
0 recast
0 reaction

James pfp
James
@theref
I feel like Ethereum Attestation Service probably has a role to play too.
0 reply
0 recast
1 reaction