Provider integration
Applications use the in-page provider to request a connection or signature. The extension bridge carries that request to the wallet’s approval interface.
A signing boundary for the web
Bring your identity to the tab.
The Sigil extension connects web applications to a wallet provider. Review a connection, inspect a signing request, and keep approval in a dedicated wallet surface.
Chrome ExtensionIllustrated study
Defined scope / checked / bounded
A permission is a condition, not a blank cheque.
Chrome Extension
01 / Built for a purpose
A request from a site deserves context.
A browser application requests access through the wallet provider. The extension is responsible for showing the origin and the requested operation, then returning the approved result. Connecting to a site and authorizing a transaction are distinct decisions.
Wallet-controlled signing
The application should receive the approved response, not the underlying private key. The wallet’s encrypted vault and unlock lifecycle form the signing boundary.
Protocol-compatible messages
Canonical message encoding and signing fixtures give wallet implementations a common reference for the data they sign.
An explicit selected network
A request must identify the network it targets. Test SIG, BITS, and MINT should remain distinguishable before an approval is granted.
Keep exploringOne capability.