is Vyper compatible with BEP networks by default?
@Tumble17 you mean Binance Chain? Yes, there are several things deployed there and working just fine.
hi, I have been trying to deploy an ERC721 contract on Ropsten, but the token transfers do not show up in the transfers tab and it seems to be displayed as an ERC20 token: https://ropsten.etherscan.io/token/0xcBAcCb66dADa684B36Bea31F84615B66a3cc0234
is this an issue with the code, or with Etherscan? the code is available on Etherscan
adghsrgnsfgbs(bytes)for a function signature
def adghsrgnsfgbs(data: bytes) -> ...further
Thanks @fubuloubu so basically we can't support standards like https://eips.ethereum.org/EIPS/eip-1155 who extensively use dynamic array like : function safeBatchTransferFrom(address _from, address _to, uint256 calldata _ids, uint256 calldata _values, bytes calldata _data) external; and if @scherrey workaround works, we couldnt even work with function balanceOfBatch(address calldata _owners, uint256 calldata _ids) external view returns (uint256 memory); which also return a dynamic array which we couldnt construct with the right size
Not yet, no. Not until vyperlang/vyper#1440 is implemented, which is high priority for us but has a number of issues that needs to be resolved first to be able to be added safely.
Just jumping in to ask because google is being completely unhelpful, do we have any current method for dealing with the incompatibility of vyper with dynamic array inputs for solidity contracts?
Trying to spec out a uniswap v2 interface for a contract (because I have yet to find an open source one for vyper) and the return values for amounts and the path inputs straight up aren't possible with the current feature set (given no workaround exists)
Do i just have to subject myself to the torture that is solidity or wait for v0.3?