Conversation
aefhm
force-pushed
the
xz/add-viem-snippet
branch
from
5bb22f0 to
12a1ba2
Compare
| window.ethereum = sapphire.wrap(window.ethereum); // If you're feeling bold. | ||
| ``` | ||
|
|
||
| ### Viem |
There was a problem hiding this comment.
Should we keep or replicate these snippets to https://github.com/oasisprotocol/docs? Or is this okay for now? cc @matevz
There was a problem hiding this comment.
Or I have my answer in oasisprotocol/docs#585
There was a problem hiding this comment.
@CedarMist we probably want BOTH our npm user facing documentation as well as official documentation snippets right?
There was a problem hiding this comment.
In addition to the npm readme, the WAGMI part should go into https://docs.oasis.io/dapp/sapphire/browser and the Viem part into https://docs.oasis.io/dapp/sapphire/quickstart or perhaps https://docs.oasis.io/dapp/sapphire/guide.
btw. Does Viem support encrypted transactions using our wrapper? I thought we only integrate with ethers hooks?
There was a problem hiding this comment.
In addition to the npm readme, the WAGMI part should go into https://docs.oasis.io/dapp/sapphire/browser and the Viem part into https://docs.oasis.io/dapp/sapphire/quickstart or perhaps https://docs.oasis.io/dapp/sapphire/guide.
This sure is more convenient to reference on a PR now. 😉
Does Viem support encrypted transactions using our wrapper? I thought we only integrate with ethers hooks?
I'm able to get this through as opposed to unwrapped transaction, and I sampled these demo examples as working.
It is all EIP-1193 the way down with custom providers the way they wrap it.
aefhm
force-pushed
the
xz/add-viem-snippet
branch
5 times, most recently
from
8a251c8 to
fe30a74
Compare
aefhm
force-pushed
the
xz/add-viem-snippet
branch
from
fe30a74 to
9695ab4
Compare
|
This is now fairly stale and provides less support #303. |
3 participants
Description
Viem has changed a bit since when we opened #164. This snippet works with Viem examples.
TODO
Vigil.sol