New answers tagged

1

As you can see in the explorer, the addLiquidity entrypoint accepts parameter of type (pair address (pair nat (pair nat timestamp)) But you pass (according to the original Dexter contract): (pair (pair address nat) (pair nat timestamp)) These are two different types, so you need to re-group your Pairs this way: Pair "...


3

Only admin can call mintOrBurn in that particular contract. As you can see in the contract storage, tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx is the admin, so you need a private key from this address. Fortunately, tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx is one of the bootstrap addresses with known private key edsk3gUfUPyBSfrS9CCgmCiQsTCHGkviBDusMxDJstFtojtc1zcpsh, ...


1

The contents of tickets is completely transparent and can't be used in this way. In general, you cannot assume that on-chain data is unreadable by users. You can add encrypted data on chain, but to to decrypt it you will have to supply the key -- effectively making the data public. You could use an off-chain oracle that feeds the hidden data to the contract. ...


1

It is for historical reason. Until the Babylon upgrade, smart contracts had the option to declare a manager at origination time and the manager could sign transactions whose source was the smart contract (so not only the amount of the transaction but also the fees were paid by the smart contract). When the feature was removed, the type of the SOURCE ...


Top 50 recent answers are included