New answers tagged

0

I think the entrypoint is well written ("%transfer") because if you look the generated Michelson code, the entrypoint annotations start with a low-case letter. get_entrypoint_opt Ligo function is equivalent to CONTRACT %transfer {targeted_contract_entrypoints} in Michelson. And I reproduced this bug with a small michelson script like this one. ...


1

wallet.connect seems to indicate you are using the @temple-wallet/dapp package. If you are using TypeScript, there is the TempleDAppNetwork enum that you can import from the package with all the different network names. With the right settings on your editor, you should get a list of the network names when you type the parameter of wallet.connect :)


0

The operation hash is generated at the time of submission to the network. You submit the raw transaction bytes to any node which validates the operation, validates your signature, and then creates the opHash before putting the operation into the mempool. The opHash is immediately returned to you, so yes, you absolutely know the opHash before it is baked. ...


0

A few things.. Contacting Binance customer support won't help you since they no longer have access to those funds, since you withdrew it to your wallet. You aren't seeing those tokens on your balance via your wallet interface because they aren't ERC20 tokens. You did not do an ERC20 withdrawal, you did a BEP20 withdrawal. ERC20 tokens are on the Ethereum ...


0

So I figured out a solution, I don't know why this works but it does (or why it doesn't work without the solution). The contract I'm trying to trigger transfers from is an FA2 token contract. I need to define the transfer_action type before I import the fa2 type declarations type transfer_action is TransferAction of michelson_pair(address, "from", ...


1

Here is the detailed history of the multisig contract supported in tezos-client: Basic multisig, with replay attack Hash 475e37a6386d0b85890eb446db1faad67f85fc814724ad07473cac8c0a124b31. The first basic multisig supported by tezos-client. This version supports: single transfers updating the delegate updating keys and threshold All transfers of funds to the ...


2

After working with @taquito/rpc for a little while and having success there I also discovered in the main @taquito/taquito package there's some useful things you can subscribe to on the stream. A simple example to listen for new block hashes: const tezos = new TezosToolkit("http://localhost:8732"); const blockSub = tezos.stream.subscribe("...


Top 50 recent answers are included