signet.js 0.0.7 → 0.0.9-retry

package/docs/dist/assets/index-DTr0DlO0.js

@@ -1,36 +0,0 @@
-import{u as t,j as e}from"./index-D8xhaiVb.js";const r=void 0;function i(s){const n={a:"a",code:"code",div:"div",h2:"h2",h3:"h3",li:"li",p:"p",pre:"pre",span:"span",strong:"strong",ul:"ul",...t(),...s.components};return e.jsxs(e.Fragment,{children:[e.jsxs(n.h2,{id:"introduction",children:["Introduction",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#introduction",children:e.jsx(n.div,{"data-autolink-icon":!0})})]}),`
-`,e.jsx(n.p,{children:"Managing multiple accounts across different blockchains is a headache. Every chain has its own wallets, private keys, and authentication systems, making cross-chain interactions complex and fragmented. But what if a single abstract account could seamlessly control multiple accounts across different chains—without compromising security? That's now possible through Chain Signatures."}),`
-`,e.jsxs(n.h3,{id:"what-are-chain-signatures",children:["What Are Chain Signatures?",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#what-are-chain-signatures",children:e.jsx(n.div,{"data-autolink-icon":!0})})]}),`
-`,e.jsx(n.p,{children:`Chain Signatures are programmable digital signatures that enable cross-chain control, allowing one account on one blockchain to securely manage accounts and assets on entirely different chains.
-The system:`}),`
-`,e.jsxs(n.ul,{children:[`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"Derives keys"})," from a single base key."]}),`
-`,e.jsxs(n.li,{children:["Allows third parties (e.g., dApps, wallets, or protocols) to ",e.jsx(n.strong,{children:"request signatures"})," on-chain."]}),`
-`,e.jsxs(n.li,{children:["Introduces ",e.jsx(n.strong,{children:"flexible usage controls"}),", such as daily spending limits or rate limits, by combining these keys with custom on-chain logic."]}),`
-`]}),`
-`,e.jsxs(n.h3,{id:"benefits--use-cases",children:["Benefits & Use Cases:",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#benefits--use-cases",children:e.jsx(n.div,{"data-autolink-icon":!0})})]}),`
-`,e.jsxs(n.ul,{children:[`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"One Identity, Many Chains"}),": Instead of juggling multiple wallets, a single signature from your Ethereum account could authorize actions on any other supported EVM or non-EVM chain, without needing to manage separate private keys."]}),`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"Seamless Cross-Chain Transactions"}),": Move assets or execute smart contract functions across different chains, without relying on third-party bridges or centralized custodians."]}),`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"Usage Controls"}),': rate or time-based restrictions can be enforced by the on-chain contract that manages key usage (e.g., "this key can only send up to 1 ETH per day").']}),`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"Recovery or Fallback Conditions"}),": Instead of storing private keys in a single hardware device, you can use a multi-party computation (MPC) setup that offers user-friendly ways to recover accounts."]}),`
-`,e.jsxs(n.li,{children:[e.jsx(n.strong,{children:"Signs the Arbitrary State of a Foreign Chain"}),": Gives your smart contract awareness of whether a transaction it signed went through so that it can perform actions accordingly. For example, it allows for a smart contract to keep track of local chain assets based on the foreign chain's state."]}),`
-`]}),`
-`,e.jsxs(n.h2,{id:"how-it-works",children:["How It Works?",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#how-it-works",children:e.jsx(n.div,{"data-autolink-icon":!0})})]}),`
-`,e.jsxs(n.h3,{id:"contract-background",children:["Contract Background",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#contract-background",children:e.jsx(n.div,{"data-autolink-icon":!0})})]}),`
-`,e.jsxs(n.p,{children:["The ",e.jsx(n.strong,{children:"ChainSignatures"})," contract:"]}),`
-`,e.jsxs(n.ul,{children:[`
-`,e.jsxs(n.li,{children:[`
-`,e.jsxs(n.p,{children:["Holds a base public key (",e.jsx(n.code,{children:"publicKey"}),"), expressed in affine coordinates on the secp256k1 curve."]}),`
-`]}),`
-`,e.jsxs(n.li,{children:[`
-`,e.jsxs(n.p,{children:["Derives new public keys for each ",e.jsx(n.code,{children:"(user, path)"})," combination by computing an integer ",e.jsx(n.code,{children:"epsilon"})," (based on a ",e.jsx(n.code,{children:"path"})," string and user’s address) and performing an EC point addition:"]}),`
-`,e.jsx(e.Fragment,{children:e.jsx(n.pre,{className:"shiki shiki-themes github-light github-dark-dimmed",style:{backgroundColor:"#fff","--shiki-dark-bg":"#22272e",color:"#24292e","--shiki-dark":"#adbac7"},tabIndex:"0",children:e.jsx(n.code,{children:e.jsx(n.span,{className:"line",children:e.jsx(n.span,{style:{color:"#24292E","--shiki-dark":"#ADBAC7"},children:"DerivedPubKey = BasePubKey + (epsilon × G)"})})})})}),`
-`]}),`
-`,e.jsxs(n.li,{children:[`
-`,e.jsxs(n.p,{children:["Allows a user to request a signature on a 32-byte payload by calling ",e.jsx(n.code,{children:"sign(...)"}),". A minimal deposit may be required to discourage spam; any unused deposit is refunded once the request is completed."]}),`
-`]}),`
-`,e.jsxs(n.li,{children:[`
-`,e.jsxs(n.p,{children:["Awaits the ",e.jsx(n.strong,{children:"MPC network"})," to compute the actual ECDSA signature offline, then call ",e.jsx(n.code,{children:"respond(...)"})," with that signature. The contract then emits an event with the signature, and refunds the deposit."]}),`
-`]}),`
-`]})]})}function o(s={}){const{wrapper:n}={...t(),...s.components};return n?e.jsx(n,{...s,children:e.jsx(i,{...s})}):i(s)}export{o as default,r as frontmatter};