You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not knowledgeable about this area usecase. What type of user is going to be impacted, and what "thing" will the be trying to do and why that is impacted? I'm asking so we can gage priority.
Background here: we use secp256k1 everywhere, including in the registry, because that's the native Ethereum curve. But, unfortunately, WebAuthn, that lets you generate and securely store and use private keys in a browser environment, don't support k1, so we can't have nice, safe session keys generated by a browser. Instead, we have to do it purely in software, without the use of a secure enclave to house the private key. The session key private material is exposed to JavaScript and potentially browser extensions/malware, whereas secure enclave storage keeps the key material isolated from the application layer.
On the flip side, our EVM doesn't support efficient secp256r1 operations, so we can't make use of WebAuthn as it is unless we do one of two things:
Leverage an existing library and do it all in Solidity, which is not super efficient, but possible
Add a precompile to FEVM to make it efficient, this would require a FIP, but has been requested and wouldn't be too hard to do, it's just more work
And, the other important point here is that the API is more complex since we can't just use ecrecover on an address, you have to pass in an additional public key unless we get a library or a precompile that gives us an ecrecover we can use. The problem is that if we have to also pass the public key then that hits everything because extraData needs to be extended from the SDK through to FWSS, which is a bit too annoying.
This might be nice to have for GA if we could get over the ecrecover hurdle, but also it seems like it might have to be a stretch goal, and more than likely it'll end up being a v2 thing.
Great explanation - thank you! Unless we have already heard clear customer demand for this, I think we'll need to punt to post GA given we already have a lot to do for GA. (I realize that comes with having to swallow doing the extra work later of a filecoin-pay contract migration...). As a result, I'm leaving this with the MX milestone.
Activity
BigLep commentedon Dec 3, 2025
I'm not knowledgeable about this area usecase. What type of user is going to be impacted, and what "thing" will the be trying to do and why that is impacted? I'm asking so we can gage priority.
rvagg commentedon Dec 4, 2025
Background here: we use secp256k1 everywhere, including in the registry, because that's the native Ethereum curve. But, unfortunately, WebAuthn, that lets you generate and securely store and use private keys in a browser environment, don't support k1, so we can't have nice, safe session keys generated by a browser. Instead, we have to do it purely in software, without the use of a secure enclave to house the private key. The session key private material is exposed to JavaScript and potentially browser extensions/malware, whereas secure enclave storage keeps the key material isolated from the application layer.
On the flip side, our EVM doesn't support efficient secp256r1 operations, so we can't make use of WebAuthn as it is unless we do one of two things:
And, the other important point here is that the API is more complex since we can't just use
ecrecoveron an address, you have to pass in an additional public key unless we get a library or a precompile that gives us anecrecoverwe can use. The problem is that if we have to also pass the public key then that hits everything becauseextraDataneeds to be extended from the SDK through to FWSS, which is a bit too annoying.This might be nice to have for GA if we could get over the
ecrecoverhurdle, but also it seems like it might have to be a stretch goal, and more than likely it'll end up being a v2 thing.BigLep commentedon Dec 4, 2025
Great explanation - thank you! Unless we have already heard clear customer demand for this, I think we'll need to punt to post GA given we already have a lot to do for GA. (I realize that comes with having to swallow doing the extra work later of a filecoin-pay contract migration...). As a result, I'm leaving this with the MX milestone.
rvagg commentedon Dec 8, 2025
This is the EIP we want to track for this to get a precompile into Filecoin: EIP-7951