DavidM-D

@firatNEAR Just a heads up that this is a blocker for multichain relayers, which we're hoping to get out by EoY

@frol > If business sponsoring a new account does not need to deploy a smart contract they should be fine with Meta-transactions to further compensate the costs, and users cannot...

I approve this NEP

Thanks for writing up this proposal Bowen, it appears to me to be very sensible and solve our problem. I've got a few suggestions of how I think we can...

Do we have to have an opaque reference type. Is it not possible to do it all on the application level? Surely if the contract has to verify the response...

Will storage deposits be denominated in gas or NEAR? NEAR storage deposits make for complex interactions with relayers.

I'll clean this up tomorrow

@ilblackdragon > async sign(payload: Bytes) -> Signature Is mainly for brevity, practically it'd likely be more like: ```rust async sign(payload: Bytes, derivation_path: [u8; 32], ecdsa_Curve: Curve) -> Signature ``` The...

I'd like to propose instead of this being a protocol feature we prototype this using a capabilities contract and only move over to protocol when we have discovered clear limits...

The capability contract would be one per user. Multisig + NETH would be one per network/shard depending on usage If we did compose them all into a single contract, people...