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

ord env not allowing inscriptions #4164

Open
duckingwhimsical opened this issue Jan 4, 2025 · 3 comments
Open

ord env not allowing inscriptions #4164

duckingwhimsical opened this issue Jan 4, 2025 · 3 comments
Labels

Comments

@duckingwhimsical
Copy link

I'm on windows 11, just trying to get started running this stuff myself. I'll try on linux tomorrow. Here's my process:

  1. Install bitcoin core to d:\bitcoin
  2. Install ord in d:\bitcoin\ord\ord-0.22.1
  3. Put d:\bitcoin\daemon in my PATH
  4. Ran d:\bitcoin\ord\ord-0.22.1\ord env
  5. Ran d:\bitcoin\ord\ord-0.22.1\ord --datadir env --regtest wallet inscribe --fee-rate 1 --file README.md

here's the output from ord env (looks normal to me): ord_env.txt
here's the output when I try to inscribe:

D:\bitcoin\ord\ord-0.22.1>ord --datadir env --regtest wallet inscribe --fee-rate 1 --file README.md
error: JSON-RPC error: RPC error response: RpcError { code: -4, message: "Wallet is currently rescanning. Abort existing rescan or wait.", data: None }

says that even after an hour. Any ideas?

@cryptoni9n
Copy link
Collaborator

cryptoni9n commented Jan 4, 2025

hi @duckingwhimsical - I'm pretty sure this is a bug with ord env and Windows. I actually ran into this and had an issue opened a couple of months ago for it (#4057). I wasn't able to find anyone who could replicate it then, though.

I just retried in 0.22.1 and am able to recreate the issue. Here's the full dump that I get:

F:\0.22.1\release>ord.exe --datadir env wallet inscribe --file "F:\Bitcoin\art projects\ANDRE.webp" --fee-rate 5
error: JSON-RPC error: RPC error response: RpcError { code: -4, message: "Wallet is currently rescanning. Abort existing rescan or wait.", data: None }
   0: std::backtrace_rs::backtrace::dbghelp64::trace
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\..\..\backtrace\src\backtrace\dbghelp64.rs:91
   1: std::backtrace_rs::backtrace::trace_unsynchronized
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\..\..\backtrace\src\backtrace\mod.rs:66
   2: std::backtrace::Backtrace::create
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\backtrace.rs:331
   3: std::backtrace::Backtrace::capture
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\backtrace.rs:296
   4: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   5: <T as ord::subcommand::Output>::print
   6: <T as ord::subcommand::Output>::print
   7: ord::subcommand::runes::run
   8: ord::subcommand::wallet::WalletCommand::run
   9: ord::subcommand::Subcommand::run
  10: ord::arguments::Arguments::run
  11: ord::main
  12: __ImageBase
  13: __ImageBase
  14: std::rt::lang_start_internal::closure$2
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\rt.rs:143
  15: std::panicking::try::do_call
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:554
  16: std::panicking::try
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:518
  17: std::panic::catch_unwind
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panic.rs:345
  18: std::rt::lang_start_internal
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\rt.rs:143
  19: main
  20: invoke_main
             at D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
  21: __scrt_common_main_seh
             at D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
  22: BaseThreadInitThunk
  23: RtlUserThreadStart

@raphjaph @casey here is the full RUST tracelog:
ord_v0.22.1_RUST_LOG_trace.txt

I know Windows isn't a platform that is available for you to test on so please let me know if I can provide any other logging or backtraces to help identify this issue.

@raphjaph
Copy link
Collaborator

raphjaph commented Jan 7, 2025

Hmm yeah I don't have a Windows machine to play around with.

What happens when you do wallet balance?

@raphjaph raphjaph added the bug label Jan 7, 2025
@cryptoni9n
Copy link
Collaborator

Hmm yeah I don't have a Windows machine to play around with.

What happens when you do wallet balance?

it's the same as #4057 for me - at first, it reports correctly:

{
  "cardinal": 500000000000,
  "ordinal": 0,
  "runes": {},
  "runic": 0,
  "total": 500000000000
}

then, if I ctrl-c the env server, I get two unexpected kill errors:

F:\master_202501\release\ord.exe --datadir env wallet balance
Shutting down gracefully. Press <CTRL-C> again to shutdown immediately.
Shutting down gracefully. Press <CTRL-C> again to shutdown immediately.
kill: 86128: No such process
kill: 86796: No such process

then, if I restart the env server and check the balance again:

{
  "cardinal": 0,
  "ordinal": 0,
  "runes": {},
  "runic": 0,
  "total": 0
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants