Philippe ROSTAN

I think that we can have : ```typescript const content:AllowArray=await myContract.getStorage(varName,nbFeltToRead); ``` `nbFeltToRead` is optional. Then the user has to deserialize the output. I think it will be difficult to...

> Hi, is there anyone working on this? Hello, I have started to work on it, but it has not been yet decided the exact scope of this job.

Hello, For short term, you can do the same thing than Lava project : use manually the Starknet.js test suite, not to test Starknet.js, but to test their nodes. For...

Hello, ByteArray is already supported in Starknet.js, both for encoding and decoding : https://www.starknetjs.com/docs/next/guides/define_call_message#longstring-or-bytearray https://www.starknetjs.com/docs/next/guides/define_call_message#receive-data-from-a-cairo-contract Conversion functions are available here : https://www.starknetjs.com/docs/next/API/namespaces/byteArray

Well, The guide is explaining all possible needs, including the complicated ones. Seems clear that in a normal case `You can send to Starknet.js methods: string.` . So just send...

Hello, You are right. That's why the PR https://github.com/starknet-io/starknet.js/pull/985 has been proposed, to have a full compatibility with the new OpenZeppelin Ethereum account. This PR is waiting a review from...

Do you mean the code in my tuto?

This commit is rather old. Please checkout latest commit and re-test.

> I wanted to test a refactoring suggestion and I noticed that some of the tests don't fully check the code. > > On this [branch](https://github.com/starknet-io/starknet.js/commit/38e21a22a54cc7fb60df30186919aeca08c82225#diff-f7dca081cb62e38c337dcdf23e048124e55164c90ca6212d0a920bceb9a347d7) you can see that...

Some tests have been performed (with success) with various types of accounts, outside of the test suite :