Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] - Lovelace output needed when output address for native tokens is the same as change address #3057

Closed
mkoura opened this issue Aug 11, 2021 · 2 comments
Labels
alonzo-purple Relates to the Alonzo Purple Testnet API&CLI-Backlog comp: cardano-cli enhancement New feature or request era: alonzo type: enhancement An improvement on the existing functionality user type: internal Created by an IOG employee

Comments

@mkoura
Copy link
Contributor

mkoura commented Aug 11, 2021

Internal/External
Internal

Area
Native Tokens Related to Native Tokens (Mary).

Summary
I'm using transaction build command for minting native tokens. That command automatically creates output for Lovelace change. In my transaction, change was higher than minimum UTxO value. The output for minted tokens was the same address as was used for the change, i.e. the UTxO for that change address would have Lovelace amount greater than minimum UTxO value + the minted tokens. However the transaction failed with

$ cardano-cli transaction build --tx-in 2cb330d4125cfcd3a8bbffbd5f596e95e4abb58c957459cf810955da909b8b83#0 --tx-out addr_test1vqqt0x3ax6d5320eqtpykjf573ue00td834zcljhdyfd3useuevxa+2000000+1 d8e5fe41f76e817956a85dcb4751d86d0dd294f47e91ee0e01301817.couttscoingvzm --tx-out addr_test1vr0ukapgh8fxn2ywnvk2t8vr4p4dwt2lxam6x33gvdshcegkvpshl+19999999 d8e5fe41f76e817956a85dcb4751d86d0dd294f47e91ee0e01301817.couttscoingvzm --change-address addr_test1vr0ukapgh8fxn2ywnvk2t8vr4p4dwt2lxam6x33gvdshcegkvpshl --alonzo-era --testnet-magic 42 --out-file test_transfer_tokens_1_True_tx.body

Command failed: transaction build  Error: Minimum UTxO threshold not met for tx output: addr_test1vr0ukapgh8fxn2ywnvk2t8vr4p4dwt2lxam6x33gvdshcegkvpshl + 19999999 d8e5fe41f76e817956a85dcb4751d86d0dd294f47e91ee0e01301817.couttscoingvzm
Minimum required UTxO: Lovelace 1379280

System info (please complete the following information):

  • OS Name: Fedora 34
  • Node & CLI version:
cardano-cli 1.28.0 - linux-x86_64 - ghc-8.10
git rev 4ff39790a8f80e4b2617e641b2c6060b52525f10
@mkoura mkoura added the bug Something isn't working label Aug 11, 2021
@mkoura mkoura changed the title [BUG] - Lovelace output needed when minting output address is the same as change address [BUG] - Lovelace output needed when output address for native tokens is the same as change address Aug 11, 2021
@dorin100 dorin100 added the alonzo-purple Relates to the Alonzo Purple Testnet label Aug 11, 2021
@dcoutts
Copy link
Contributor

dcoutts commented Aug 16, 2021

This is a feature request, not a bug.

As designed, the change address feature is very simple: you provide a change address and we use that to create a single output with the ada/lovelace change. It doesn't matter if you also use the same address for other outputs. There is no feature to combine the change output with another output. If you want more precise control, use the build-raw command.

@mkoura mkoura added enhancement New feature or request and removed bug Something isn't working labels Aug 23, 2021
@mkoura mkoura changed the title [BUG] - Lovelace output needed when output address for native tokens is the same as change address [FR] - Lovelace output needed when output address for native tokens is the same as change address Aug 23, 2021
@Jimbo4350
Copy link
Contributor

Closing this as I agree with Duncan. Use the build-raw command.

@dorin100 dorin100 added type: enhancement An improvement on the existing functionality user type: internal Created by an IOG employee comp: cardano-cli era: alonzo labels Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alonzo-purple Relates to the Alonzo Purple Testnet API&CLI-Backlog comp: cardano-cli enhancement New feature or request era: alonzo type: enhancement An improvement on the existing functionality user type: internal Created by an IOG employee
Projects
None yet
Development

No branches or pull requests

5 participants