Jackson Mills

If you omit the `LastLedgerSequence` from the Transaction definition, `submitAndWait` with `autofill = true` will automatically populate that field for you before sending the transaction. Let me know if that...

My guess would be that it's the line `const result = await client.submitAndWait(trust_set { wallet:'' })` - It looks like you're passing in a string when you need to pass...

I'm not quite able to reproduce the issue locally unfortunately. This code works for me: ```js xrpl = require("xrpl"); async function main() { const client = new xrpl.Client("wss://s.altnet.rippletest.net:51233"); await client.connect();...

@jinho Unfortunately I'm still unable to reproduce with electron JS (I cloned their quickstart they display on their [homepage here](https://www.electronjs.org/) and added the xrpl code I shared before for signing...

@dependabot rebase

> @intelliot I believe the better path is to use the same parameter name, `WalletLocator`, that's on the docs to avoid confusion. AFAIK, we've been consistent with our models containing...

As far as I understand it, Wallet was just intended to make it easier to use private keys in whatever format you have them. `Wallet.verifyTransaction` is simply there to make...

I see the value in the publicKey "Validation Wallet" which just makes it easy to keep track of the `classicAddress` and `publicKey` and do validations. For the Reference Wallet case...

Good catch! - If you remove the `SignerList` import in `accountRoot.ts` it should resolve the unit test error you're running into.

@barmola Could you share what version of xrpl.js you are using? (And a code snippet that reproduces the issue?) I'm not able to see that issue locally.