Deploying to gh-pages from @ 6007596 🚀

print.html

@@ -360,15 +360,14 @@ <h2 id="acknowledgements"><a class="header" href="#acknowledgements">Acknowledge
 <p>Special thanks to <a href="https://github.com/btchip">btchip</a> for developing the reference implementation
 <a href="https://github.com/btchip/Webauthn.sol">here</a> and for the invaluable guidance through the WebAuthn specification.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="iwebauthn256r1"><a class="header" href="#iwebauthn256r1">IWebAuthn256r1</a></h1>
-<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/786aa3f50855be04284a783ca4f4eb44ed06c972/src/IWebAuthn256r1.sol">Git Source</a></p>
+<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/6007596147c262322506bf828cc1b9b118177c68/src/IWebAuthn256r1.sol">Git Source</a></p>
 <h2 id="functions"><a class="header" href="#functions">Functions</a></h2>
 <h3 id="verify"><a class="header" href="#verify">verify</a></h3>
 <pre><code class="language-solidity">function verify(
     bytes1 authenticatorDataFlagMask,
     bytes calldata authenticatorData,
     bytes calldata clientData,
     bytes calldata clientChallenge,
-    uint256 clientChallengeOffset,
     uint256 r,
     uint256 s,
     uint256 qx,
@@ -378,8 +377,12 @@ <h3 id="verify"><a class="header" href="#verify">verify</a></h3>
     returns (bool);
 </code></pre>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="webauthn256r1"><a class="header" href="#webauthn256r1">WebAuthn256r1</a></h1>
-<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/786aa3f50855be04284a783ca4f4eb44ed06c972/src/WebAuthn256r1.sol">Git Source</a></p>
+<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/6007596147c262322506bf828cc1b9b118177c68/src/WebAuthn256r1.sol">Git Source</a></p>
 <p>A library to verify ECDSA signature though WebAuthn on the secp256r1 curve</p>
+<h2 id="state-variables"><a class="header" href="#state-variables">State Variables</a></h2>
+<h3 id="client_challenge_offset"><a class="header" href="#client_challenge_offset">CLIENT_CHALLENGE_OFFSET</a></h3>
+<pre><code class="language-solidity">uint256 private constant CLIENT_CHALLENGE_OFFSET = 0x24;
+</code></pre>
 <h2 id="functions-1"><a class="header" href="#functions-1">Functions</a></h2>
 <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessage</a></h3>
 <p>Validate the webauthn data and generate the signature message needed to recover</p>
@@ -412,8 +415,7 @@ <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessa
     bytes1 authenticatorDataFlagMask,
     bytes calldata authenticatorData,
     bytes calldata clientData,
-    bytes calldata clientChallenge,
-    uint256 clientChallengeOffset
+    bytes calldata clientChallenge
 )
     internal
     pure
@@ -425,7 +427,6 @@ <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessa
 <tr><td><code>authenticatorData</code></td><td><code>bytes</code></td><td>The authenticator data structure encodes contextual bindings made by the authenticator. Described here: https://www.w3.org/TR/webauthn-2/#authenticator-data</td></tr>
 <tr><td><code>clientData</code></td><td><code>bytes</code></td><td>This is the client data that was signed. The client data represents the contextual bindings of both the WebAuthn Relying Party and the client. Described here: https://www.w3.org/TR/webauthn-2/#client-data</td></tr>
 <tr><td><code>clientChallenge</code></td><td><code>bytes</code></td><td>This is the challenge that was sent to the client to sign. It is part of the client data. In a classic non-EVM flow, this challenge is generated by the server and sent to the client to avoid replay attack. In our context, as we already have the nonce for this purpose we use this field to pass the arbitrary execution order. This value is expected to not be encoded in Base64, the encoding is done during the verification.</td></tr>
-<tr><td><code>clientChallengeOffset</code></td><td><code>uint256</code></td><td>The offset of the client challenge in the client data</td></tr>
 </tbody></table>
 </div>
 <p><strong>Returns</strong></p>
@@ -437,10 +438,9 @@ <h3 id="verify-1"><a class="header" href="#verify-1">verify</a></h3>
 <p>Verify ECDSA signature though WebAuthn on the secp256r1 curve</p>
 <pre><code class="language-solidity">function verify(
     bytes1 authenticatorDataFlagMask,
-    bytes calldata authenticatorData,
+    bytes calldata authData,
     bytes calldata clientData,
     bytes calldata clientChallenge,
-    uint256 clientChallengeOffset,
     uint256 r,
     uint256 s,
     uint256 qx,

src/IWebAuthn256r1.sol/interface.IWebAuthn256r1.html

@@ -178,15 +178,14 @@ <h1 class="menu-title"></h1>
                 <div id="content" class="content">
                     <main>
                         <h1 id="iwebauthn256r1"><a class="header" href="#iwebauthn256r1">IWebAuthn256r1</a></h1>
-<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/786aa3f50855be04284a783ca4f4eb44ed06c972/src/IWebAuthn256r1.sol">Git Source</a></p>
+<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/6007596147c262322506bf828cc1b9b118177c68/src/IWebAuthn256r1.sol">Git Source</a></p>
 <h2 id="functions"><a class="header" href="#functions">Functions</a></h2>
 <h3 id="verify"><a class="header" href="#verify">verify</a></h3>
 <pre><code class="language-solidity">function verify(
     bytes1 authenticatorDataFlagMask,
     bytes calldata authenticatorData,
     bytes calldata clientData,
     bytes calldata clientChallenge,
-    uint256 clientChallengeOffset,
     uint256 r,
     uint256 s,
     uint256 qx,

src/WebAuthn256r1.sol/library.WebAuthn256r1.html

@@ -178,8 +178,12 @@ <h1 class="menu-title"></h1>
                 <div id="content" class="content">
                     <main>
                         <h1 id="webauthn256r1"><a class="header" href="#webauthn256r1">WebAuthn256r1</a></h1>
-<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/786aa3f50855be04284a783ca4f4eb44ed06c972/src/WebAuthn256r1.sol">Git Source</a></p>
+<p><a href="https://github.com/0x90d2b2b7fb7599eebb6e7a32980857d8/webauthn/blob/6007596147c262322506bf828cc1b9b118177c68/src/WebAuthn256r1.sol">Git Source</a></p>
 <p>A library to verify ECDSA signature though WebAuthn on the secp256r1 curve</p>
+<h2 id="state-variables"><a class="header" href="#state-variables">State Variables</a></h2>
+<h3 id="client_challenge_offset"><a class="header" href="#client_challenge_offset">CLIENT_CHALLENGE_OFFSET</a></h3>
+<pre><code class="language-solidity">uint256 private constant CLIENT_CHALLENGE_OFFSET = 0x24;
+</code></pre>
 <h2 id="functions"><a class="header" href="#functions">Functions</a></h2>
 <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessage</a></h3>
 <p>Validate the webauthn data and generate the signature message needed to recover</p>
@@ -212,8 +216,7 @@ <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessa
     bytes1 authenticatorDataFlagMask,
     bytes calldata authenticatorData,
     bytes calldata clientData,
-    bytes calldata clientChallenge,
-    uint256 clientChallengeOffset
+    bytes calldata clientChallenge
 )
     internal
     pure
@@ -225,7 +228,6 @@ <h3 id="generatemessage"><a class="header" href="#generatemessage">generateMessa
 <tr><td><code>authenticatorData</code></td><td><code>bytes</code></td><td>The authenticator data structure encodes contextual bindings made by the authenticator. Described here: https://www.w3.org/TR/webauthn-2/#authenticator-data</td></tr>
 <tr><td><code>clientData</code></td><td><code>bytes</code></td><td>This is the client data that was signed. The client data represents the contextual bindings of both the WebAuthn Relying Party and the client. Described here: https://www.w3.org/TR/webauthn-2/#client-data</td></tr>
 <tr><td><code>clientChallenge</code></td><td><code>bytes</code></td><td>This is the challenge that was sent to the client to sign. It is part of the client data. In a classic non-EVM flow, this challenge is generated by the server and sent to the client to avoid replay attack. In our context, as we already have the nonce for this purpose we use this field to pass the arbitrary execution order. This value is expected to not be encoded in Base64, the encoding is done during the verification.</td></tr>
-<tr><td><code>clientChallengeOffset</code></td><td><code>uint256</code></td><td>The offset of the client challenge in the client data</td></tr>
 </tbody></table>
 </div>
 <p><strong>Returns</strong></p>
@@ -237,10 +239,9 @@ <h3 id="verify"><a class="header" href="#verify">verify</a></h3>
 <p>Verify ECDSA signature though WebAuthn on the secp256r1 curve</p>
 <pre><code class="language-solidity">function verify(
     bytes1 authenticatorDataFlagMask,
-    bytes calldata authenticatorData,
+    bytes calldata authData,
     bytes calldata clientData,
     bytes calldata clientChallenge,
-    uint256 clientChallengeOffset,
     uint256 r,
     uint256 s,
     uint256 qx,