btcd in simnet mode showing bad cerficiate.

[zydjohnHotmail]

btcd in simnet mode showing bad cerficiate.

[guggero]

You don't need to generate a certificate, btcd will do that for you. Then you have to specify that in btcwallet when connecting.

Can't listen on [::1]:18556: listen tcp6 [::1]:18556: bind: cannot assign requested address

This probably just means you don't have ipv6 networking enabled within the container but are trying to listen on an ipv6 address.

[zydjohnHotmail]

Hi,
I don't quite understand. If I don't need generate certificate, then just using the config file:
[Application Options]
rpcuser=yourusername
rpcpass=yourpassword
simnet=1
And run btcd --configfile=/path/to/config/file?
Then what I should do? I want to create an account for user Alice (or any default account), and create another account for Bob(or any none-default account), generate some blocks (I think 101 blocks will be enough to get some reward BTC tokens, right); then try to send 1BTC token from Alice's wallet address to Bob's wallet address. I think I can use btcctl to get new address, and use btcctl to transfer some tokens. But how to create wallet, I don't know if btcctl can do this or not.
Do I have to use btcwallet package? And which version of btcwallet I have to install?
Please advise,
Thanks,

[guggero]

Yes, just start btcd and it will generate its own (self-signed) certificate.
btcd itself doesn't have a wallet (and hence no accounts), you'll need to use an additional software for that. There is btcwallet which does work as a standalone binary (though it is designed and maintained more as a library for other software, such as lnd), see https://github.com/btcsuite/btcwallet#getting-started.

You can also use lnd as an on-chain wallet (ignoring all the Lightning features), as it might have more wallet features out of the box than the standalone btcwallet binary. See https://github.com/lightningnetwork/lnd/tree/master/docker for a docker based tutorial with btcd on simnet.

Going to convert this to a discussion as this sounds like troubleshooting and not an issue with btcd itself.