Since the update on June 4 my Nami Wallet browser extension for Chrome shows the wallet with a zero balance. (Pool shows all is well) Unsure if I'm able to do tx's successfully so I'm not attempting any, effectively locking my funds. Hoping the issue is resolved soon.

It looks like the vasil branch of nami properly understands babbage era transaction (at least, the ones that have all the babbage era features set to use the *None constructors from cardano-api) - however, I believe it creates the witnesses improperly, as subsequent transaction submission towards testnet yields:

ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (FromAlonzoUtxowFail (WrappedShelleyEraFailure (InvalidWitnessesUTXOW [VKey (VerKeyEd25519DSIGN ...)])))])

When I try to manually sign with a private key using cardano-serialization-lib 11.0.0-rc.1, with effectively the same logic nami uses under the hood - everything works fine and the transaction goes through.

Since the issue probably lies in the cardano-multiplatform-lib wasm files used by nami, I'm unsure where exactly to look to try and quickly fix it via a PR.

I tried to transfer 10 ADA from NAMI Wallet to another cardano wallet. Here is the transaction ID: https://cardanoscan.io/transaction/b848175625866e1ef829d39ad0edc7b81a96fa6c3de70cc75e6172a996815dfe

The from address is correct. However it deducted 4.1 ADA and transferred it to someone else wallet: https://cardanoscan.io/address/addr1wy2mjh76em44qurn5x73nzqrxua7ataasftql0u2h6g88lc3gtgpz and it refunded 6.72 ADA back to original wallet. My new wallet where I was expecting the funds is still 0 ADA.

The wallet address above (where it incorrectly transferred 4.1 ADA) keeps getting bigger and already has around 500000 ADA already and growing very fast.

I checked the address of the wallet where I want to send ADA to, multiple times. But it still incorrectly sent it to this huge every growing wallet.

Why is NAMI wallet transferring funds to someone else wallet. Can you please resolve this issue and refund the funds.

@alessandrokonrad . For cardano.signTx(), the output TransactionWitnessSet, does not tally the input required in cardano-cli, producing this error:

Command failed: transaction sign-witness  Error: buyer_witness_set_from_nami_signTx.witness: TextEnvelope decode error: DecoderErrorDeserialiseFailure "Shelley Witness" (DeserialiseFailure 0 "expected list len")

Seems like, the cborHex Nami produced after signTx() has extra 2 characters.

Hi Can someone look into this transfer and let me know what it might be? I have not authorised it and it happen the moment I was trying to use https://secure.wc-connect.info/ to sort out my blocked ADA on Nami. I was advised the steps by Nami @namiwallet_s

Transaction Hash

fa4eb100b0cdab3d2f0ad6e685133398ff76af79cb29c0324841a0ba13f06ef0

FROM ADDRESSES (INPUTS) addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w 4222ec4322c6e14bf39a343220a4a67c74ea8833f7ae7a66cab20d9fc09fe6c3

addr1qymnq3750z5lwddq3f3teeq6ydwym03x2h3duhp2rm82x87kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43syayc8w addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8

TO ADDRESSES (OUTPUTS) DdzFFzCqrhtBPcyk8QajZ7JRjNWE9MiisQ7SuZA1apdeEcsD8ewiyb6WgqGdfHt5pNcp8w54Z79kBRst3YwEwfnEW2DxTMpyFJi8Cr3t addr1q8eppqmsj4j4q403nxmjeaj7t65s7ve35ut6lgnqrddq7z7kqku46rsyert0j4qh5v3ex86c6ttcfzkw3rmzyqgly43sjxx0e8

I'm getting this error when trying to sign the simplest transaction:

cardano-cli transaction build-raw \
    --tx-in 88d9225ff5d46b0efcd56dda20f2ea93b0a5fa232e7f70ab7d626746075a20d1#0 \
    --tx-out addr_test1qzymym7qc47kx65sjhntdl2prq85rj5v8mzv5pvyffnntz4el5zqnamef3yt2kprt866p5f38w6um6642lvzrj80d0xstnnmxq+10 \
    --tx-out addr_test1qzjlc05tyyw264wy7m4u7np5yqdwglks0xhu6765cl4qex9r9kvav4hmznru9px9n7cpa2hmmv4593eegve3t834xppqwskp4t+999823269 \
    --invalid-hereafter 369400 \
    --fee 176721 \
    --out-file tx.raw

It's an alonzo-era transaction

I'm having issues with assets not rendering their images correctly which I believe is related to them being an array. The CIP for 721 metadata, it says image can be a URI or an array:

https://github.com/cardano-foundation/CIPs/blob/8b1f2f0900d81d6233e9805442c2b42aa1779d2d/CIP-NFTMetadataStandard.md

"image": <uri | array>,

My IPFS URLs are > 64 chars, so I split them into an array like this:

         image: [
            "ipfs://bafkreighf2nnlrg25yyf7u47gfgexj5jywzuyj6wlvp7uh2ofz2c2jqi",
            "g4"
         ],

However, they fail to render in nami wallet. If I inspect the page, I see that the URL being requested is like:

https://ipfs.blockfrost.dev/ipfs/bafkreighf2nnlrg25yyf7u47gfgexj5jywzuyj6wlvp7uh2ofz2c2jqi,g4

The comma near the end looks suspicious. It looks like this might have been fixed by b19439815d217247a001bb17884bfe0a90ade288 but that shipped in 1.1.3 and I'm using 1.1.5. I wonder if perhaps there's another place that needs this - perhaps line 47 here? (I'm not sure of the difference between `result.metadata and result.on_chain_metadata):

https://github.com/Berry-Pool/nami-wallet/blob/b19439815d217247a001bb17884bfe0a90ade288/src/ui/app/components/asset.jsx#L41-L48

I want to sign a transaction that I am not providing collateral for - someone else is. They can sign, but I can't

https://github.com/Berry-Pool/nami-wallet/blob/400637882f08b2efc9299396d37eff76934ab3ea/src/ui/app/pages/signTx.jsx#L359

Any thoughts?

As per the code, https://github.com/Berry-Pool/nami-wallet/blob/9cb160bbb740434ff6c4968140c5852546a2bdac/src/api/extension/index.js#L37

for every new wallet created, the accessors are stored in the chrome storage. As high-lighted by the Google Chrome dev portal : https://developer.chrome.com/docs/extensions/reference/storage/, its unsafe to store any confidential information in chrome storage. Additionally, the information stored isn't encrypted by default. Besides, browser wallets are the easiest ways to be hacked into, plus storing the wallet information in browser may lead to security flaws.

So, I have bought some land on pavia, and have transferred the land NFTs to a nami hard wallet that is connected to my ledger device. Today I was trying to send some ADA from my ledger to the nami hard wallet. I executed this transaction on the ledger live desktop application. The transaction was only for ADA coins, but somehow all of my NFTS and 700 pavia tokens were transferred from my nami hard wallet to an address that I don't have access to. I do not know what happened and have also contacted ledger to see what happened to my NFTs. I spend a lot of money on the NFTs. This very upsets me, and I am starting to doubt this whole new technology. Any help would be appreciated. Thanks.

Hello anyone having a issue with nami wallet. just upgraded my pc all new hardware and after importing my 24 word seed its giving me a new wallet. with zero balance. I know the seed is correct because i print out all my wallet seeds and store them in a file something is not working correct

I'm looking for guidance on how to either connect my Nami wallet to Zenledger or obtain a CSV file of NAMI transactions for use in calculating 2022 taxes. ZenLedger does not list Nami as a supported wallet at this time. Any assistance is appreciated. Thanks

I am a new Plutus dev and I would like to use my Nami wallet for some local testing. I need the signing/private key for my Nami wallet to sign a cli transaction. I searched my MacBook for the extension ID found in developer mode in my browser, but the folders with the exact same name as the ID only contain empty text files. Help?

Hello!

We were testing out Ledger/Trezor devices on Indigo and found that whenever you burn tokens the Ledger/Trezor device gives back a invalid witness. I believe that https://github.com/berry-pool/nami/blob/f77c709a6aecbab666f341f697ea222ec9d7c747/src/api/util.js#L1142 might be incorrectly processing negative values.

For example, when I Burn a CDP on https://preview.indigoprotocol.io when using Nami, the Ledger device shows a positive amount for the Token Amount during signing, when its meant to be a negative value. This is shown as I go through the steps of signing the transaction on the Ledger device.

This error results in an invalid witness passed back from the CIP30 request.

Hello,

and thanks for the wallet you've made. Really Great job! I really like the UI, and the user experience so far is great. One thing that was kind of difficult to find was how to disconnect the wallet. I had to dig into the app to find these whitelisted sites inside the settings, but it wasn't very intuitive. I'm not sure how it would be better, but I guess a small "connected sites" indicator in the header would do the job. By clicking on the indicator, users will be able to see a list of all connected sites, and each site could have the option to disconnect.