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

bug: Unable to create a reception address #3263

Closed
starker-xp opened this issue Mar 11, 2024 · 4 comments
Closed

bug: Unable to create a reception address #3263

starker-xp opened this issue Mar 11, 2024 · 4 comments

Comments

@starker-xp
Copy link

starker-xp commented Mar 11, 2024

versions :
windows 11 prox64
btc cli 25.0
ord 0.16.0-rc1

rpc.conf

##
## bitcoin.conf configuration file. Lines beginning with # are comments.
##
daemon=0
regtest=1

listen=1

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

#rpcport=8332

# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
server=1
#prune=5500
txindex=1
datadir=H:\btc\data

fallbackfee=0.000002
minrelaytxfee=0.000002

bitcoind -conf="H:\btc\rpc.conf"
bitcoin-cli -conf="H:\btc\rpc.conf" createwallet dev
bitcoin-cli -conf="H:\btc\rpc.conf" generatetoaddress 101 $(bitcoin-cli -conf="H:\test\rpc.conf" -rpcwallet=dev getnewaddress)

ord -r --cookie-file "H:\test\data\regtest.cookie" wallet --name=ord_dev create

ord -r --cookie-file "H:\test\data\regtest.cookie" wallet --name=ord_dev receive

thread 'main' panicked at src\wallet.rs:112:54:
called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@raphjaph
Copy link
Collaborator

Did you start the ord server?

The new wallet requires running it in parallel

@oxSaturn
Copy link
Contributor

Did you start the ord server?

The new wallet requires running it in parallel

And possible to show a warning asking users to run the server in this case? I'm afraid most users won't read the changelogs.

@starker-xp
Copy link
Author

I read the changelogs but missed this information. Indeed, adding a warning would be great.

@raphjaph
Copy link
Collaborator

Added a warning in #3272

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

No branches or pull requests

3 participants