Richard Moore
Richard Moore
(and am adding support along with the other change to accept the API function names you use)
The Transaction object will accept any of `[email protected]`, `[email protected]` and `micro-ecc-signer` KZG libraries. ```javascript // kzg-wasm (either v0.4 or v0.5) import { loadKZG } from "kzg-wasm-4"; tx.kzg = loadKSG(); //...
(quick aside, I've heard the pure-JS version provided by micro-ecc-signer is faster than the WASM version; any benchmarks are welcome on this issue ;))
Oh! Is it finally deployed on a testnet? I’ve been waiting for that, as that is a good indication the spec of likely done changing. Plus it enables trying it...
Thanks! Yes, I have a local implementation (in BaseWallet and Transaction) ready to release on the 24th once I can test it out. :)
Almost. I have a PR I'll be pushing up later. I'm just waiting for it to go live on Sepolia so I can make sure my tests work. :)
Does anyone know of a JSON-RPC endpoint for Sepolia that this works on? It should have definitely activated by now. I've tried Infura, but I get the error: ``` //...
I've added a branch with initial support. I'm going to test it a bit more and then publish it as an alpha release on npm.
To use it: ```javascript // You may optionally specify a nonce and chainId; if omitted the current provider is used // to get the chain ID and nonce. A chainID...
Yes, the above code (converted to ethers syntax) would work just fine on the new branch. But if that is a common pattern, I think it also makes sense to...