Ryan Mehta

We used `requestSignTransactions` here: https://github.com/ref-finance/ref-ui/blob/main/src/services/near.ts#L78 and it worked pretty well! It may be nice to bring some of the logic we used int `near-api-js` so it is a bit easier...

It sounds like secp256k1 support in nearcore has been pushed until next quarter. We should take this time to audit the [elliptic](https://www.npmjs.com/package/elliptic) package. If it looks good we can replace...

@bowenwang1996 that is just what I heard when I asked about this. I've been messing around with adding a secp256k1 key with this code: ```js async function run() { const...

Created issue with borsh-js. https://github.com/near/borsh-js/issues/19 Waiting for feedback, then will implement a fix and implement this change

Can you expand on this? What inadequacies are you experiencing?

That function is for making JSON RPC requests to a NEAR node. It’s not really meant for general use. What is your use case?

@stunney any update on this? I'm still not sure what the use case for supporting more methods is.

We use the `fetch` function that is built into the browser in browser contexts and use `node-fetch` when in a node context. Are you importing the `near-api-js` `fetchJson` function into...

We should add ability to see delegated staking amount from `near-api-js` or provide some guide to show how to get this value using `near-api-js`.

This will be fixed by #557