Newton talks a big game about non technical users delegating agents, but try explaining a zkPermission to your mom and watch her eyes glaze over.
I tested this logic on myself first, could I actually set up scoped autonomy for an agent without reading three docs pages and guessing at what a session key even means for my funds. The concept is genuinely user protective, funding limits and operational conditions that stop an agent from going rogue, but explaining zero knowledge circuits to someone who just wants automated recurring buys is a UX problem nobody's solved yet. Magic's embedded wallet background should help here since they've onboarded non crypto users before, but permission granularity and simplicity usually fight each other, more control almost always means more decisions the average user doesn't want to make. If claiming, staking, and setting an agent's boundaries all still feel like separate technical hurdles, adoption stalls right at the door.
$NEWT
Good security means nothing if regular people bounce off the setup screen.
@NewtonProtocol $NEWT #Newt
I tested this logic on myself first, could I actually set up scoped autonomy for an agent without reading three docs pages and guessing at what a session key even means for my funds. The concept is genuinely user protective, funding limits and operational conditions that stop an agent from going rogue, but explaining zero knowledge circuits to someone who just wants automated recurring buys is a UX problem nobody's solved yet. Magic's embedded wallet background should help here since they've onboarded non crypto users before, but permission granularity and simplicity usually fight each other, more control almost always means more decisions the average user doesn't want to make. If claiming, staking, and setting an agent's boundaries all still feel like separate technical hurdles, adoption stalls right at the door.
$NEWT
Good security means nothing if regular people bounce off the setup screen.
@NewtonProtocol $NEWT #Newt