New answers tagged

0

As of GitHub commit: cc9b567f3acd813c81e105c074ebd783719c74364c88a78c3c22638322354f6d you can specify extended keys as required signers.


0

thank you so much for the link, it was exactly what i needed and yes, it is righ. used it, tested and worked cardano-cli transaction build-raw --fee 0 --tx-in ${tx_in} --tx-in ${my_tx_in} --tx-out ${in_addr}+${amountToSendUser}+"1 ${myToken}" --tx-out ${paymentAddr}+${amountToDonate}+"999 ${myToken}" --invalid-hereafter $FINALTIP --...


0

When the network is congested, your transaction can take some time before it gets processed within a block. Therefore, you need to make sure the --invalid-hereafter is sufficient. In my case I put up to 15 minutes after the submission. In the case where your transaction is minting, remember your policy script which could also have some time constraint. ...


3

The chain has been pretty congested since sundaeswap launched. It may take some time between transaction submission and inclusion into a block. If your TTL or --invalid-hereafter parameter is too short, the TX may be submitted to the mempool but be invalid by the time it is to be included in a block. Try setting the TTL to something like 10000+ and see if ...


2

The only difference between building a regular ADA-only transaction and one that contains ADA + asset(s) is in the cardano-cli transaction build-raw step that follows the multi-asset syntax as discussed in the official cardano documentation It would look something along the lines of: cardano-cli transaction build-raw \ --tx-in <TX_ID> \ --fee <FEE&...


1

The tx-out of the build-raw command is the only thing that is different for sending assets. Instead of address+1000000 it will be address+"1000000 + 5 <policy id><<asset name>"


3

This only works if it's an address embedding the payment and stake credential. You can use cardano-address address inspect locally. You could also use a tool like cardanoscan.io which when given an address to scan tells you the stake address associated as well. Note that some addresses don't have stake addresses and other ones can have only pointers to stake ...


2

The fact that you have a transaction ID does not mean it was successfully submitted. The moment you create locally a transaction file, you already have a transaction ID for it, no matter if you submit it or not (even before you sign it). You can see the transaction ID with the command: cardano-cli transaction txid --tx-body-file tx.raw Are you using the --...


3

For the above example, you would run: cardano-cli transaction txid --tx-file matx.signed If instead of inspecting a signed transaction you wish to inspect a transaction body / unsigned draft, it would look similar: cardano-cli transaction txid --tx-body-file tx.draft The Txid will be printed to stdout


0

Ok seems the problem was that i used an older cardano-cli with a newer cardano-node


0

You can't. WSL is a linux container on windows that expects a POSIX socket and Daedalus on windows uses named pipes. They aren't compatible. You may be able to symlink the state directory from Daedalus to WSL and stop daedalus and run a node in WSL, although I've never tested this and don't know if it would work.


1

Yoroi follows the same nomenclature that cardano-wallet does with change addresses. A number of other wallets (adalite, typhon and my python wrapper wallet https://github.com/input-output-hk/adawallet re-use the same address as the change address). The way it works is explained here in detail: https://github.com/cardano-foundation/CIPs/tree/master/CIP-1852 ...


3

Cardano utilizes a UTXO-style accounting model (similar to bitcoin, but with extra features), as opposed to an accounting model, like what Ehtereum uses. Here is a quick overview of the differences. In short, a UTXO is an output of a previous transaction that "sits and waits" at an address to be used as an input for a future transaction. It is ...


2

I am afraid that via the cardano-cli, you will not be able to do that. Indeed the cli evaluates the execution units before you get to sign the transaction. Signatories are however available in the script context from a Plutus standpoint. Right now, I don't know any other way than doing it "the Haskell way" and by pre-constructing the transaction ...


1

I'm trying to learn this too. I could not find any further documentation other than the cardano-cli command help. This is pretty extensive and useful. Every command argument seems to have built-in help. So, for instance, to get help with building a transaction, issue the command cardano-cli transaction build. The help for this includes some info on the --tx-...


0

You can ignore it. You do not need to account for TxOutDatumNone in your tx-out or anywhere else. See for yourself by manually sending a TX using cli before you script it.


0

Usually when you want to pass empty datum to the script you'd pass an empty list like so --tx-in-datum-value []


1

I'm afraid that presenting a "none" datum is not possible. This also means that this UtxO is lost (anybody, correct me if I'm wrong) I don't know the very reason why it is possible to send a UtxO at a script address without datum hash, while at the same time it will not be possible to get it back. Anyway, pay attention to always send a datum hash ...


2

The flag --tx-out-datum-embed-file FILE allows you to embed the datum data on the transaction, not the datum hash like using that flag --tx-out-datum-hash-file FILE. cardano-cli transaction build --tx-out-datum-embed-file DATUM.json According to this web page, the definition is vague: The script datum to embed in the tx for this output, in the given JSON ...


0

The problem was that I was trying to use the cardano-cli command for address to a stake-address. The command for payment credential (PubKeyHash) is correct in the question: cardano-cli address key-hash --payment-verification-key-file payment.vkey The correct command for staking credential should be like this: cardano-cli stake-address key-hash --stake-...


1

A single transaction in Cardano can contain many inputs and outputs. As long as the transaction is signed by all the private keys associated with each address, it will be valid. In other words, the number of inputs doesn't effect the number of signatures needed, only the number of unique addresses does, where each unique address requires a signature. For ...


0

Here's an example of a signing command - just add/remove --signing-key-file parameters as necessary! cardano-cli transaction sign --signing-key-file payment.skey --signing-key-file policy.skey --mainnet --tx-body-file matx.raw --out-file matx.signed


0

If you want to send everything in a wallet the new way that calculates the fee and adds ttl you can query for all the utxo's in the wallet. cardano-cli query utxo \ --address $(cat payment.addr) \ --mainnet grab all the utxo's and add them as tx-in as you normally would. You can have multiple in and out. If it is all going to one place use --change-address. ...


0

Fees are variable - You cannot depend on them being the same for every transaction. Things such as changing the number of signing witnesses, or number of receivers, can make fees adjust. To determine the correct fee, first create a draft TX and just use a dummy ada amount for the txout and txin parameters, such as 0, and then run: cardano-cli transaction ...


-1

The build command will differ from the amount when submitted from the signatures. So the problem is that the cost goes up with each signature. You can include this estimate by using the "--witness-override 2" if you know you will be signing it with 2 signatures and it will give an accurate fee.


1

You should be able to create a transaction draft where you should specify a fee of 200000 lovelace (to have the same transaction size as the final transaction), then estimate the fees, and create the final transaction. You can also use "cardano-cli transaction build" command and you don't need to calculate the transaction fees or build the ...


0

I made a post on this, maybe this can help you. Basically you'd need to first sign transaction with cli, load transaction to cardano-serialization-lib, clear vkeys from witness-set, sign transaction on the frontend and add vkeys from signature witness-set. Here's a link to my blogpost: https://srdjanstankovic.com/2021/12/24/how-to-sign-and-submit-cardano-cli-...


2

This is a known issue: https://github.com/input-output-hk/cardano-node/issues/3360 Out of curiosity, how many NFT's do you have per --tx-in? I've seen this increase memory usage dramatically with users on jpg.store who store a lot of NFT's in there wallet. I have a few suggestions, knowing practically nothing about how this stuff works :P I'll share these in ...


3

By default cardano-wallet listens on loopback ip only - 127.0.0.1, to listen on server external ip, you need to add --listen-address parameter So at the end command should be: cardano-wallet serve \ --listen-address 0.0.0.0 \ --mainnet \ --node-socket ~/cardano/db/node.socket \ --database ~/cardano/db --port 8090 Or put dropleat real ip instead of ...


0

I'm no networking wiz (working on it) - but I just played around with the above: I got the same error when I used my public IP address. However, when I use the loopback address (127.0.0.1) it seems to work for me. Try running: http://127.0.0.1:8090/v2/network/information in chrome and see if that works. If anyone knows why the public IP doesn't work but the ...


Top 50 recent answers are included