You must remember to declare your contract to publish them to the chain before deploying your contract. You only need to declare your contract once but you can deploy the contract multiple times afterwards. 

Why am I having trouble deploying my Cairo contract?

# Is Kakarot zkEVM a blockchain?

Does Kakarot have its own consensus, finality, commitment to L1, blocks, etc.?

Is Kakarot zkEVM a blockchain?

Hey, I'm curious if uint256 variables are safe to use? They are using 2x128 bits, while a native felt uses only 252 bits. 

Can anyone explain?

Is uint256 math operators like uint256_le safe? Why do I need to use uint256_check?

Hey, is there anyway to debug Cairo contracts in hardhat environment? Something like hardhat console in Solidity?

Hey, is there anyway to debug Cairo contracts in hardhat environment? Something like hardhat console in solidity

Hi people. I can't seem to be able to update to 0.3.3.

I am using docker, and when and successfully pull with

*docker pull eqlabs/pathfinder*

but then

*docker run \
  --rm \
  -p 9545:9545 \
  --user "$(id -u):$(id -g)" \
  -e RUST_LOG=info \
  -e PATHFINDER_ETHEREUM_API_URL="https://goerli.infura.io/v3/<project-id>" \
  -v $HOME/pathfinder:/usr/share/pathfinder/data \
  eqlabs/pathfinder*

makes the node run with 0.3.0-alpha

Anyone encountering the same issue ?

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

An issue while updating to 0.3.3 node StarkNet

I have the following code:


`@external`


`func updateCurrNum{syscall_ptr : felt*, pedersen_ptr : HashBuiltin*, range_check_ptr}(updatedNum : felt):`


 `let (isOwner) = isOwner()`


 `assert isOwner = 1`


`...`


And I am getting this error: 


Unexpected '.' after '__main__.updateCurrNum.isOwner' which is future.


 let (isOwner) = isOwner()


 ^*****^


What am I doing wrong?


ㅤ
_This question was originally posted on [Triality](https://triality.org/question/806)_

Cairo error for Unexpected '.' after ... which is future

Can I transpile any solidity version?

Say I am calling the following function test. Why can I call with either of these function signatures and get the same result?


`func test{syscall_ptr : felt*}():`


or


`func test{syscall_ptr : felt*, range_check_ptr}():`


ㅤ
_This question was originally posted on [Triality](https://triality.org/question/413)_

Popular tags

Why am I having trouble deploying my Cairo contract?

1 answers

Your answer

Related

You may find useful