The deliverables for some of the Snap Builders are not Snaps themselves, but instead 3rd Party Tools and SDKs that can be used by other Snap Builders.
Here is a list of Builders who are interested in developing 3rd Party tools and SDK for the ecosystem.
| Builder | Description | Stage |
|---|---|---|
| Push | Idea | |
| XMTP | Idea | |
| Biconomy | Idea | |
| Cubist | Here’s what I was thinking for mentioning our Snap in the developer docs. My suggestion is to create a new section between “Responsible key management” and “Derive keys” at https://docs.metamask.io/snaps/how-to/manage-keys/ | |
| Key management options | ||
| When building a Snap, you are responsible for deriving your users’ MetaMask keys and handling them responsibly. | ||
| For those who prefer a more seamless key management solution, the security experts from Cubist built a Snap that allows you to safely manage both EVM and non-EVM keys on behalf of your MetaMask end users. The Snap provides an interface to a simple API for programmatically requesting signatures, and your users’ keys sign server-side from within secure hardware enclaves. This means that your MetaMask users' keys are never exposed in memory to attackers, and there's no risk that you could accidentally leak the keys, either. Get started with the CubeSigner Snap here. | ||
| Hopefully that blurb should work for passing along the value prop to your technical team, too. Here is our launch announcement for our CubeSigner Snap: https://cubist.dev/blog/cubesigner-snap-hardware-backed-signing-for-metamask-developers. This post includes more detail about how the Snap works and has a video of a cross-chain demo powered by MetaMask and the CubeSigner Snap. | ||
| In order to use the Snap, developers will need to set up a CubeSigner account with us (not currently self-service, but onboarding is fast)—so, it’s probably the best fit for companies that are building dapps or Snaps. We have a TypeScript SDK, and our Snap provides an interface to CubeSigner's remote signing services via the MetaMask JSON-RPC Snap API. | ||
| Our pricing is usage-based, billed monthly, and depends on the number of keys and the number of transaction requests. We tier the rates based on volume. We have customers who have millions of users and consider it cost-effective. | ||
| Would it make sense for us to have a quick technical call with Mario and anyone else who regularly interfaces with builders? I’d be happy to pull in engineers from our side to give an engineering-level overview and answer any questions. | ||
| We hope our Snap will make it a lot faster for developers to build secure Snaps or dapps of their own! | Idea | |
| Xtreamly | Can we showcase Xtreamly as a third-party Snap Developer? We can describe the functionality available as APIs that other Snap Developers can use. |