-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ord wallet not seeing full cardinal or runes balances #3632
Comments
I'm testing now in 0.18.3 and this does not appear to be an issue in this latest version. It's possible that users experiencing this issue are using 0.18.1 or earlier, and that the described behaviour has changed as of the wallet migration in 0.18.2 - still testing, just recording my notes here. |
I've seen the problem you are describing twice now, and the problem assists to be with bitcoin core, not ord. When I run "listunspent" in Bitcoin Core, some utxos that are in the wallet don't show up. There's a utxo I know exists, it isn't spent, it's at an address that I added some debugging to bitcoind to try to figure out why the utxo wasn't showing up, but the act of restarting bitcoind fixed the problem. That's good, in that now my balance shows up correctly, but bad in that I can't find the cause of the problem. Even switching back to the original version of Core without the debug now shows all the mixing utxos. So maybe just try restarting bitcoind (and ord server, if using cookie auth, because the cookie will change when you restart bitcoind. |
Same question, is there any way to transfer this rune to the original receive address? Only this address has a balance that allows me to spend gas on transfers or transactions |
In my current observation, on versions after 0.18.2, running But I haven't found a simple way to transfer it. If anyone has a way, please tell me. |
I etched a bunch of tokens at the halving. Some time in the last day, all the 10000 sat utxos containing the runes disappeared from the "bitcoin-cli listunspent" output. I restarted bitcoind and now they are back. This can't be an ord issue, because I'm not using ord, only bitcoin-cli. |
I found the problem:
Simply unlocking all utxos makes them show up again. Something is locking the outputs and leaving them locked. |
Huge thanks for your work on this Greg! I'll update the Ordicord post with the new instruction on how to unlock the utxos in core. |
Hi aboutmydreams - you can transfer runes using the If you need further assistance, please reach out to the #tech-support channel on our official Discord server, The Ordicord |
100:THE.RUNE.NAME.HERE replaces ? Will this command cost gas? Thank you. |
yes, sending a transaction will cost fees. |
UPDATE: I've had this advice from Greg work for multiple people with this issue. If your ord wallet is not seeing some of your utxos or their associated sats or runes, try this:
|
I think this happens when the tx is still in the mempool. The solution to this is adding mempool support to the wallet and explorer so pending txs can be incorporated into the output. |
Maybe, but for me it happened without anything being unconfirmed. The utxos were locked by ord, and then ignored because they were locked. |
when minting a rune from the ord wallet, by default, the rune and the change from the tx go to new receiving addresses. This is fine but the
ord wallet balance
command isn't showing the balances for these new utxos held by the wallet. It is being reported from many in the Ordicord that their displayed balances are incomplete.The is causing users to think that their outputs were sent to 'another wallet', because they're not familiar with the way the wallet dissuades address reuse and they also don't see their funds/runes. In these cases,
ord wallet outputs
shows all of the utxos with proper balances, but the runes and funds for some of them aren't being included with the balance results.I have a thread with a pinned explanation for more detail up on the Ordicord here: https://discord.com/channels/987504378242007100/1231226072385720440
I will be attempting to recreate this in 0.18.3 and will post more information here as I find it.
This is a high volume issue on the Ordicord. It has led me to believe that adding an
ord setting
that gives users a way to enable address reuse would be popular.edit: I edited the title and rewrote the problem with my new understanding of it.
The text was updated successfully, but these errors were encountered: