1. Currently, invoke can be only used from migration scripts. We will add invoke and call commands in a future release.
https://github.com/software-mansion/protostar/issues/883
2. I couldn't replicate this problem. The migration script runner doesn't validate hints. I think the issue may be in the contract. Does this issue occur for the "main" contract generated by protostar init? Maybe the main.json is outdated. How do you run migration scripts?

You can check our integration tests for the invoke cheatcode in the version 0.4.2: https://github.com/software-mansion/protostar/blob/53cb5dc5cda1a74a1ffb862d84e7035e44a5c56b/tests/integration/migrator/migrator_invoke_cheatcode_test.py
(The deploy_contract cheatcode will be deprecated in the next release. Declare cheatcode should be used instead.)

Regarding best practices, migration scripts are intended to be used with Proxy pattern. Protostar's migrations are inspired by Truffle.
https://trufflesuite.com/docs/truffle/getting-started/running-migrations/

FYI: migrations needs polishing. In 0.4.3 for example, you should be able to deploy or declare contract by specifying a contract name (e.g. declare("main")) to avoid using outdated compiled contract by accident.

_This answer was originally posted on [StarkNet Discord](https://www.newton.so/view?tags=discord)_

Newton

Some questions that could be answered separately.

1. The only way to invoke a contract is using migrations (this applies for both devnet and testnet?)
2. When doing a migration file I receive the “Hint is not whitelisted. This may indicate that this library function cannot be used in StarkNet contracts.” error. For example for this code:

```
%lang starknet

@external
func up() {
    %{
        contract_address = deploy_contract(
             "./build/main.json",
             config={"wait_for_acceptance": True}
        ).contract_address

        invoke(
            contract_address,
            "initialize",
            {"new_authority": 123},
            config={
                "auto_estimate_fee": True,
                "wait_for_acceptance": True,
            }
        )
    %}

    return ();
}
```

_This question was originally posted on [StarkNet Discord](https://www.newton.so/view?tags=discord)_

The only way to invoke a contract is using migrations (this applies for both devnet and testnet?)

### *From Newton AI*
*OpenZeppelin is a collection of reusable, secure smart contract libraries for Ethereum. It provides a set of Solidity contracts that implement common contract patterns and functions, such as ERC20 token contracts and contracts for managing and securing user accounts. By using OpenZeppelin libraries in your contracts, you can benefit from the security and functionality provided by these pre-written contracts, without having to reimplement them yourself. When transpiling your contracts, the transpiler will include the code from any imported libraries, such as OpenZeppelin, in the final transpiled output.*

Is it possible to transpile contracts that use openzeppelin libraries?

I'm implementing the new version and had a couple Q's:

- Is `useStarknetExecute` now the only transaction method (for multi and single calls).
- Do we update the transaction manager on our end? I seem to remember `useStarknetInvoke` also update this automatically

_This question was originally posted on [StarkNet Discord](https://www.newton.so/view?tags=discord)_

Questions about useStarknetExecute. Do we update the transaction manager on our end? [StarkNet/Cairo]

Hey! I hope I'm at the right channel 🙂 I had a ques about contract creation gas fees. are there none? I can deploy to goreli starkent w/o any fees but couldnt find any doc

_This question was originally posted on [StarkNet Discord](https://www.newton.so/view?tags=discord)_

What are gas fees in StarkNet?

Another question I have is:

**What's easier, adapt the create2 trick in Solidity then transpile or transpile first then adapt in Cairo?**

---

### *From Newton AI:*

*"Create2" is a feature in Solidity, the programming language used to write smart contracts for the Ethereum blockchain. It allows the creation of new contract accounts using a deterministic algorithm, rather than having to send a transaction to create the contract like with the original "create" function. This can be useful in certain situations, such as when creating a contract that is intended to be deployed at a specific address.*

*Transpiling is the process of converting code written in one programming language into another language. This can be useful if a piece of code needs to be run on a platform that only supports a different language, or if it is desired to use a different language's features or syntax.*


Did you change the factory/create2 part (to compute pool addresses)?

When I try to transpile my contract using warp transpiler I get an error: `JavaScript heap out of memory`

![JavaScript heap out of memory error in Nethermind's warp transpiler](https://res.cloudinary.com/varga/image/upload/v1670423892/Screenshot_2022-11-30_at_7.32.34_PM_pazqli.png)

can anyone help?

update:
I ran this command 
```
export NODE_OPTIONS=--max-old-space-size=4096
```
before transpiling
still show the same error

- Node version is v16.16.0
- warp version  2.4.1
- I tried using node 18 but still same error occured
- I'm using an M1 Mac, 8gb RAM

I'm transpiling llampay contracts : [https://github.com/LlamaPay/llamapay/tree/master/contracts](https://github.com/LlamaPay/llamapay/tree/master/contracts)

The original LlamaPay has some unsupported features in Warp. And I fixed them:
- [LlamaPay.sol](https://pastebin.com/12pSdPBJ) 
- [LlamaPayFactory.sol](https://pastebin.com/DVeuvWKd)


Nethermind's warp error: JavaScript heap out of memory

Hey everyone!

I am trying to unpack nested tuples into felts t pass as calldata to a contract via a proxy call.

await signer.send_transaction(admin, proxy_contract.contract_address, 'createSyntheticAsset', [
       *test_synthetic_asset.to_tuple() 
    ])

But this fails with this error: TypeError: '<' not supported between instances of 'tuple' and 'int' 

does anyone have an Idea about this?

_This question was originally posted on [StarkNet Discord](https://www.newton.so/view?tags=discord)_

A TypeError while unpacking nested tuples into felts

I am trying to deploy my contract using this tutorial
[https://medium.com/starknet-edu/deploying-to-starknet-with-the-universal-deployer-contract-c6de07092bfb](https://medium.com/starknet-edu/deploying-to-starknet-with-the-universal-deployer-contract-c6de07092bfb)
But as I follow the steps, I got an error at the contract declaration step: `Unitialized Contract`

Popular tags

The only way to invoke a contract is using migrations (this applies for both devnet and testnet?)

1 answers

Your answer

Related

You may find useful