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
Ed25519 curves [1] are used by Metamask, libp2p, IPFS, UCANs, Web3.storage and many many cryptocurrencies [2] for signing operations at high speed.
While the web has a cryptography API, it did not support Ed25519. This means that dapps must ship large JavaScript bundles that contain implementations which are not necessarily verified or audited. This is bad for user experience, as the sites load more slowly, and user safety.
Browser makers were generally positive on adding Ed25519 to the Web Cryptography API, but it was very low priority - no engines were actively working on implementing it.
Initiated while at Protocol Labs, the effort to implement this feature for the web was a contract with Igalia [3] for their browser engineering and standards expertise, which transitioned to a grant from the IPFS Foundation.
After more than 3yrs of effort, from engineering to negotiations at standards bodies to backchannel skullduggery, support for Ed25519 in the Web Cryptography API is now implemented in all major browser engines - Chromium [4], Webkit [5] and Gecko [6] 🎉
We overcame many hurdles over the years to get to this point - incompatibility on various parts of the each implementation, and being blocked by different browser vendors at different times for different reasons. We had to go back to the standards group at the W3C to hammer out a road forward for compatibility. Twice.
The primary functionality is complete. Nearly all compat issues are now ironed out, or have agreement from the vendors on a way forward. The remaining piece for web availability is for Chromium to enable the feature by default, which should happen in the next month or so.
Ed25519 curves [1] are used by Metamask, libp2p, IPFS, UCANs, Web3.storage and many many cryptocurrencies [2] for signing operations at high speed.
While the web has a cryptography API, it did not support Ed25519. This means that dapps must ship large JavaScript bundles that contain implementations which are not necessarily verified or audited. This is bad for user experience, as the sites load more slowly, and user safety.
Browser makers were generally positive on adding Ed25519 to the Web Cryptography API, but it was very low priority - no engines were actively working on implementing it.
Initiated while at Protocol Labs, the effort to implement this feature for the web was a contract with Igalia [3] for their browser engineering and standards expertise, which transitioned to a grant from the IPFS Foundation.
After more than 3yrs of effort, from engineering to negotiations at standards bodies to backchannel skullduggery, support for Ed25519 in the Web Cryptography API is now implemented in all major browser engines - Chromium [4], Webkit [5] and Gecko [6] 🎉
We overcame many hurdles over the years to get to this point - incompatibility on various parts of the each implementation, and being blocked by different browser vendors at different times for different reasons. We had to go back to the standards group at the W3C to hammer out a road forward for compatibility. Twice.
The primary functionality is complete. Nearly all compat issues are now ironed out, or have agreement from the vendors on a way forward. The remaining piece for web availability is for Chromium to enable the feature by default, which should happen in the next month or so.
The text was updated successfully, but these errors were encountered: