Show Posts
|
Pages: [1] 2 »
|
Yes exactly!
Yes indeed I can create users to allow people to play with but more risky.
My idea is that I rented recently a quite good server and I can run bitcoin with good configs like coinstats, txindex and I can add other indexes, and I think it can be good to share it with the community. In the idea to provide a pretty good endpoint RPC with good features and understand how to provide such kind of services. Like a first node providing experimentation for the community. But I know that it's dangerous and need to fill some requirements.
|
|
|
Ok thank you! Just to be sure to understand, as I put rpcbind=0.0.0.0:8332 127.0.0.1:8332 address will not be accessible anymore right? Or yes it's still working as usually because 0.0.0.0 maps 127.0.0.1. Sorry it's more a general network question than bitcoin focused...
|
|
|
Do you know if I can find somewhere a nginx config example dedicated to Bitcoin RPC which is locking wallets access but allow rest and some basics rpc call everything in https?
I'm still figuring out, but I have a port with https TLS certificate for the server. Such that it can be authenticated regarding TLS but I still don't know how to activate it ^^'
|
|
|
Hello,
Thanks for your answer. Nginx acts as a reverse proxy? Cool, so I just have to configure nginx about 8332 port communication?
|
|
|
Any thoughts about Runes protocol in this topic? rodarmor.com/blog/runesHalving is arriving in ~2k blocks and fees can be way higher than any brc20 previous wave. Do we have the same angry people?
|
|
|
Hey, How long are we staying with newbie status Is it after a certain time, or number of posts or reply?
|
|
|
Hello,
I recently take a quite big server where I'm running Bitcoind with txindex=1 and I think it can be interesting for people to have access to this.
In order to make it accessible I activated rpcbindaddress=0.0.0.0. For now I whitelisted two IPs but my idea is to put accessible to everyone. But it seems to be very dangerous according to every documentations and help.
I put here my conf and I'm very interested to understand how to give endpoints accessible by anyone to have Bitcoin info. I removed some unused options. I own the server and can modify everything.
Hope to understand all of this and don't make too many mistakes in order to do this.
## ## bitcoin.conf configuration file. ## Generated by contrib/devtools/gen-bitcoin-conf.sh. ## ## Lines beginning with # are comments. ## All possible configuration options are provided. To use, copy this file ## to your data directory (default or specified by -datadir), uncomment ## options you would like to change, and save the file. ##
### Options
# Execute command when an alert is raised (%s in cmd is replaced by # message) #alertnotify=<cmd>
# For backwards compatibility, treat an unused bitcoin.conf file in the # datadir as a warning, not an error. #allowignoredconf=1
# If this block is in the chain assume that it and its ancestors are valid # and potentially skip their script verification (0 to verify all, # default: # 000000000000000000026811d149d4d261995ec5b3f64f439a0a10e1a464af9a, # testnet: # 000000000001323071f38f21ea5aae529ece491eadaccce506a59bcc2d968917, # signet: # 0000000870f15246ba23c16e370a7ffb1fc8a3dcf8cb4492882ed4b0e3d4cd26) #assumevalid=<hex>
# Maintain an index of compact filters by block (default: 0, values: # basic). If <type> is not supplied or if <type> = 1, indexes for # all known types are enabled. #blockfilterindex=<type>
# Execute command when the best block changes (%s in cmd is replaced by # block hash) #blocknotify=<cmd>
# Extra transactions to keep in memory for compact block reconstructions # (default: 100) #blockreconstructionextratxn=<n>
# Specify directory to hold blocks subdirectory for *.dat files (default: # <datadir>) #blocksdir=<dir>
# Whether to reject transactions from network peers. Disables automatic # broadcast and rebroadcast of transactions, unless the source peer # has the 'forcerelay' permission. RPC transactions are not # affected. (default: 0) #blocksonly=1
# Maintain coinstats index used by the gettxoutsetinfo RPC (default: 0) coinstatsindex=1
# Maintain a full transaction index, used by the getrawtransaction rpc # call (default: 0) txindex=1
# Print version and exit #version=1
### Connection options
# Add a node to connect to and attempt to keep the connection open (see # the addnode RPC help for more info). This option can be specified # multiple times to add multiple nodes; connections are limited to # 8 at a time and are counted separately from the -maxconnections # limit. #addnode=<ip>
# Specify asn mapping used for bucketing of the peers (default: # ip_asn.map). Relative paths will be prefixed by the net-specific # datadir location. #asmap=<file>
# Default duration (in seconds) of manually configured bans (default: # 86400) #bantime=<n>
# Bind to given address and always listen on it (default: 0.0.0.0). Use # [host]:port notation for IPv6. Append =onion to tag any incoming # connections to that address and port as incoming Tor connections # (default: 127.0.0.1:8334=onion, testnet: 127.0.0.1:18334=onion, # signet: 127.0.0.1:38334=onion, regtest: 127.0.0.1:18445=onion) #bind=<addr>[:<port>][=onion]
# If set, then this host is configured for CJDNS (connecting to fc00::/8 # addresses would lead us to the CJDNS network, see doc/cjdns.md) # (default: 0) #cjdnsreachable=1
# Connect only to the specified node; -noconnect disables automatic # connections (the rules for this peer are the same as for # -addnode). This option can be specified multiple times to connect # to multiple nodes. #connect=<ip>
# Discover own IP addresses (default: 1 when listening and no -externalip # or -proxy) #discover=1
# Allow DNS lookups for -addnode, -seednode and -connect (default: 1) #dns=1
# Query for peer addresses via DNS lookup, if low on addresses (default: 1 # unless -connect used or -maxconnections=0) #dnsseed=1
# Specify your own public address externalip=94.16.123.98
# Allow fixed seeds if DNS seeds don't provide peers (default: 1) #fixedseeds=1
# Always query for peer addresses via DNS lookup (default: 0) #forcednsseed=1
# Whether to accept inbound I2P connections (default: 1). Ignored if # -i2psam is not set. Listening for inbound I2P connections is done # through the SAM proxy, not by binding to a local address and # port. #i2pacceptincoming=1
# I2P SAM proxy to reach I2P peers and accept I2P connections (default: # none) #i2psam=<ip:port>
# Accept connections from outside (default: 1 if no -proxy, -connect or # -maxconnections=0) listen=1
# Automatically create Tor onion service (default: 1) #listenonion=1
# Maintain at most <n> automatic connections to peers (default: 125). This # limit does not apply to connections manually added via -addnode # or the addnode RPC, which have a separate limit of 8. #maxconnections=<n>
# Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000) #maxreceivebuffer=<n>
# Maximum per-connection memory usage for the send buffer, <n>*1000 bytes # (default: 1000) #maxsendbuffer=<n>
# Maximum allowed median peer time offset adjustment. Local perspective of # time may be influenced by outbound peers forward or backward by # this amount (default: 4200 seconds). #maxtimeadjustment=1
# Tries to keep outbound traffic under the given target per 24h. Limit # does not apply to peers with 'download' permission or blocks # created within past week. 0 = no limit (default: 0M). Optional # suffix units [k|K|m|M|g|G|t|T] (default: M). Lowercase is 1000 # base while uppercase is 1024 base #maxuploadtarget=<n>
# Use NAT-PMP to map the listening port (default: 0) #natpmp=1
# Enable all P2P network activity (default: 1). Can be changed by the # setnetworkactive RPC command networkactive=1
# Use separate SOCKS5 proxy to reach peers via Tor onion services, set # -noonion to disable (default: -proxy). May be a local file path # prefixed with 'unix:'. #onion=<ip:port|path>
# Make automatic outbound connections only to network <net> (ipv4, ipv6, # onion, i2p, cjdns). Inbound and manual connections are not # affected by this option. It can be specified multiple times to # allow multiple networks. #onlynet=<net>
# Serve compact block filters to peers per BIP 157 (default: 0) #peerblockfilters=1
# Support filtering of blocks and transaction with bloom filters (default: # 0) #peerbloomfilters=1
# Listen for connections on <port>. Nodes not using the default ports # (default: 8333, testnet: 18333, signet: 38333, regtest: 18444) # are unlikely to get incoming connections. Not relevant for I2P # (see doc/i2p.md). #port=<port>
# Connect through SOCKS5 proxy, set -noproxy to disable (default: # disabled). May be a local file path prefixed with 'unix:' if the # proxy supports it. #proxy=<ip:port|path>
# Randomize credentials for every proxy connection. This enables Tor # stream isolation (default: 1) #proxyrandomize=1
# Connect to a node to retrieve peer addresses, and disconnect. This # option can be specified multiple times to connect to multiple # nodes. #seednode=<ip>
# Specify socket connection timeout in milliseconds. If an initial attempt # to connect is unsuccessful after this amount of time, drop it # (minimum: 1, default: 5000) #timeout=<n>
# Tor control host and port to use if onion listening enabled (default: # 127.0.0.1:9051). If no port is specified, the default port of # 9051 will be used. #torcontrol=<ip>:<port>
# Tor control port password (default: empty) #torpassword=<pass>
# Use UPnP to map the listening port (default: 1 when listening and no # -proxy) #upnp=1
# Support v2 transport (default: 1) #v2transport=1
# Bind to the given address and add permission flags to the peers # connecting to it. Use [host]:port notation for IPv6. Allowed # permissions: bloomfilter (allow requesting BIP37 filtered blocks # and transactions), noban (do not ban for misbehavior; implies # download), forcerelay (relay transactions that are already in the # mempool; implies relay), relay (relay even in -blocksonly mode, # and unlimited transaction announcements), mempool (allow # requesting BIP35 mempool contents), download (allow getheaders # during IBD, no disconnect after maxuploadtarget limit), addr # (responses to GETADDR avoid hitting the cache and contain random # records with the most up-to-date info). Specify multiple # permissions separated by commas (default: # download,noban,mempool,relay). Can be specified multiple times. #whitebind=<[permissions@]addr>
# Add permission flags to the peers using the given IP address (e.g. # 1.2.3.4) or CIDR-notated network (e.g. 1.2.3.0/24). Uses the same # permissions as -whitebind. Additional flags "in" and "out" # control whether permissions apply to incoming connections and/or # manual (default: incoming only). Can be specified multiple times. #whitelist=<[permissions@]IP address or network>
### Wallet options
# What type of addresses to use ("legacy", "p2sh-segwit", "bech32", or # "bech32m", default: "bech32") #addresstype=1
# Group outputs by address, selecting many (possibly all) or none, instead # of selecting on a per-output basis. Privacy is improved as # addresses are mostly swept with fewer transactions and outputs # are aggregated in clean change addresses. It may result in higher # fees due to less optimal coin selection caused by this added # limitation and possibly a larger-than-necessary number of inputs # being used. Always enabled for wallets with "avoid_reuse" # enabled, otherwise default: 0. #avoidpartialspends=1
# What type of change to use ("legacy", "p2sh-segwit", "bech32", or # "bech32m"). Default is "legacy" when -addresstype=legacy, else it # is an implementation detail. #changetype=1
# The maximum feerate (in BTC/kvB) at which transaction building may use # more inputs than strictly necessary so that the wallet's UTXO # pool can be reduced (default: 0.0001). #consolidatefeerate=<amt>
# Do not load the wallet and disable wallet RPC calls #disablewallet=1
# The fee rate (in BTC/kvB) that indicates your tolerance for discarding # change by adding it to the fee (default: 0.0001). Note: An output # is discarded if it is dust at this rate, but we will always # discard up to the dust relay fee and a discard fee above that is # limited by the fee estimate for the longest target #discardfee=<amt>
# A fee rate (in BTC/kvB) that will be used when fee estimation has # insufficient data. 0 to entirely disable the fallbackfee feature. # (default: 0.00) #fallbackfee=<amt>
# Set key pool size to <n> (default: 1000). Warning: Smaller sizes may # increase the risk of losing funds when restoring from an old # backup, if none of the addresses in the original keypool have # been used. #keypool=<n>
# Spend up to this amount in additional (absolute) fees (in BTC) if it # allows the use of partial spend avoidance (default: 0.00) #maxapsfee=<n>
# Fee rates (in BTC/kvB) smaller than this are considered zero fee for # transaction creation (default: 0.00001) #mintxfee=<amt>
# Fee rate (in BTC/kvB) to add to transactions you send (default: 0.00) #paytxfee=<amt>
# External signing tool, see doc/external-signer.md #signer=<cmd>
# Spend unconfirmed change when sending transactions (default: 1) #spendzeroconfchange=1
# If paytxfee is not set, include enough fee so transactions begin # confirmation on average within n blocks (default: 6) #txconfirmtarget=<n>
# Specify wallet path to load at startup. Can be used multiple times to # load multiple wallets. Path is to a directory containing wallet # data and log files. If the path is not absolute, it is # interpreted relative to <walletdir>. This only loads existing # wallets and does not create new ones. For backwards compatibility # this also accepts names of existing top-level data files in # <walletdir>. #wallet=<path>
# Make the wallet broadcast transactions (default: 1) #walletbroadcast=1
# Specify directory to hold wallets (default: <datadir>/wallets if it # exists, otherwise <datadir>) #walletdir=<dir>
# Execute command when a wallet transaction changes. %s in cmd is replaced # by TxID, %w is replaced by wallet name, %b is replaced by the # hash of the block including the transaction (set to 'unconfirmed' # if the transaction is not included) and %h is replaced by the # block height (-1 if not included). %w is not currently # implemented on windows. On systems where %w is supported, it # should NOT be quoted because this would break shell escaping used # to invoke the command. #walletnotify=<cmd>
# Send transactions with full-RBF opt-in enabled (RPC only, default: 1) walletrbf=1
### Node relay options
# Equivalent bytes per sigop in transactions for relay and mining # (default: 20) #bytespersigop=1
# Relay and mine data carrier transactions (default: 1) #datacarrier=1
# Relay and mine transactions whose data-carrying raw scriptPubKey is of # this size or less (default: 83) #datacarriersize=1
# Accept transaction replace-by-fee without requiring replaceability # signaling (default: 0) mempoolfullrbf=1
# Fees (in BTC/kvB) smaller than this are considered zero fee for # relaying, mining and transaction creation (default: 0.00001) #minrelaytxfee=<amt>
# Relay non-P2SH multisig (default: 1) #permitbaremultisig=1
# Add 'forcerelay' permission to whitelisted peers with default # permissions. This will relay transactions even if the # transactions were already in the mempool. (default: 0) #whitelistforcerelay=1
# Add 'relay' permission to whitelisted peers with default permissions. # This will accept relayed transactions even when not relaying # transactions (default: 1) #whitelistrelay=1
### Block creation options
# Set maximum BIP141 block weight (default: 3996000) #blockmaxweight=<n>
# Set lowest fee rate (in BTC/kvB) for transactions to be included in # block creation. (default: 0.00001) #blockmintxfee=<amt>
### RPC server options
# Accept public REST requests (default: 0) rest=1
# Allow JSON-RPC connections from specified source. Valid values for <ip> # are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. # 1.2.3.4/255.255.255.0), a network/CIDR (e.g. 1.2.3.4/24), all # ipv4 (0.0.0.0/0), or all ipv6 (::/0). This option can be # specified multiple times rpcallowip=MY_IP_1 rpcallowip=MY_IP_2
# Username and HMAC-SHA-256 hashed password for JSON-RPC connections. The # field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A # canonical python script is included in share/rpcauth. The client # then connects normally using the # rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This # option can be specified multiple times rpcauth=USER:0949c0b552d208e24608d4896e706422$15b778b47156bc76545a262452a6475db8d78a8a3639c2d044ee2a6a73675ea7
# Bind to given address to listen for JSON-RPC connections. Do not expose # the RPC server to untrusted networks such as the public internet! # This option is ignored unless -rpcallowip is also passed. Port is # optional and overrides -rpcport. Use [host]:port notation for # IPv6. This option can be specified multiple times (default: # 127.0.0.1 and ::1 i.e., localhost) rpcbind=0.0.0.0:8332
# Location of the auth cookie. Relative paths will be prefixed by a # net-specific datadir location. (default: data dir) #rpccookiefile=<loc>
# Password for JSON-RPC connections #rpcpassword=<pw>
# Listen for JSON-RPC connections on <port> (default: 8332, testnet: # 18332, signet: 38332, regtest: 18443) #rpcport=<port>
# Set the number of threads to service RPC calls (default: 4) rpcthreads=1000
# Username for JSON-RPC connections #rpcuser=<user>
# Set a whitelist to filter incoming RPC calls for a specific user. The # field <whitelist> comes in the format: <USERNAME>:<rpc 1>,<rpc # 2>,...,<rpc n>. If multiple whitelists are set for a given user, # they are set-intersected. See -rpcwhitelistdefault documentation # for information on default whitelist behavior. #rpcwhitelist=<whitelist>
# Sets default behavior for rpc whitelisting. Unless rpcwhitelistdefault # is set to 0, if any -rpcwhitelist is set, the rpc server acts as # if all rpc users are subject to empty-unless-otherwise-specified # whitelists. If rpcwhitelistdefault is set to 1 and no # -rpcwhitelist is set, rpc server acts as if all rpc users are # subject to empty whitelists. #rpcwhitelistdefault=1
# Accept command line and JSON-RPC commands server=1
|
|
|
Thank you for all your answers. What I did is come back to the original path and modify the config file to make it working. Now wallets are loaded with the flag -walletdir=.../testnet3/wallets.
I still don't know why it doesn't work before but now it works. I'm still strugling with bitcoin-cli because he doesn't want to read config file in PATH. Rather than bitcoind is running correctly into this path...
I hope to find the problem soon. Thanks again everyone for your answer.
|
|
|
Yes there are. Each wallet.dat are into its folder: wallets/FirstTestWallet: wallet.dat
wallets/FirstTestnetWallet: wallet.dat
wallets/TestOPReturnWallet: wallet.dat
wallets/ord: wallet.dat
wallets/test_cli: wallet.dat wallet.dat-journal
And there are into testnet3/wallets and testnet3/tesnet3/wallets
My point is really this. The structure seems to be the same as on the mainnet where I can load them (mainnet wallets not testnet ones)
|
|
|
The file settings.json is replicated into /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3 and /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3.
The settings.json file contains:
{ "_warning_": "This file is automatically generated and updated by Bitcoin Core. Please do not edit this file while the node is running, as any changes might be ignored or overwritten." }
I reproduce the last log above.
Let me know if you need anything else to have more info.
2024-03-21T12:25:10Z Bitcoin Core version v27.99.0-015ac13dcc96 (release build) 2024-03-21T12:25:10Z Script verification uses 7 additional threads 2024-03-21T12:25:10Z Using the 'x86_shani(1way,2way)' SHA256 implementation 2024-03-21T12:25:10Z Using RdSeed as an additional entropy source 2024-03-21T12:25:10Z Using RdRand as an additional entropy source 2024-03-21T12:25:10Z Default data directory /Users/galois/Library/Application Support/Bitcoin 2024-03-21T12:25:10Z Using data directory /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3 2024-03-21T12:25:10Z Config file: /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/bitcoin.conf 2024-03-21T12:25:10Z Config file arg: [test] printtoconsole="1" 2024-03-21T12:25:10Z Config file arg: [test] rpcallowip="127.0.0.1" 2024-03-21T12:25:10Z Config file arg: [test] rpcbind="127.0.0.1" 2024-03-21T12:25:10Z Config file arg: [test] rpcport="18332" 2024-03-21T12:25:10Z Config file arg: [test] testnet="1" 2024-03-21T12:25:10Z Command-line arg: datadir="/Volumes/Crucial X8/bitcoin/Bitcoin/testnet3" 2024-03-21T12:25:10Z Command-line arg: testnet="" 2024-03-21T12:25:10Z Command-line arg: txindex="1" 2024-03-21T12:25:10Z Using at most 125 automatic connections (285 file descriptors available) 2024-03-21T12:25:10Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements 2024-03-21T12:25:10Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements 2024-03-21T12:25:10Z scheduler thread start 2024-03-21T12:25:10Z Binding RPC on address 127.0.0.1 port 18332 2024-03-21T12:25:10Z Using random cookie authentication. 2024-03-21T12:25:10Z Generated RPC authentication cookie /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/.cookie 2024-03-21T12:25:10Z Starting HTTP server with 4 worker threads 2024-03-21T12:25:10Z Using wallet directory /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/wallets 2024-03-21T12:25:10Z init message: Verifying wallet(s)… 2024-03-21T12:25:10Z Using /16 prefix for IP bucketing 2024-03-21T12:25:10Z init message: Loading P2P addresses… 2024-03-21T12:25:10Z Loaded 22415 addresses from peers.dat 71ms 2024-03-21T12:25:10Z init message: Loading banlist… 2024-03-21T12:25:10Z SetNetworkActive: true 2024-03-21T12:25:10Z Script verification uses 7 additional threads 2024-03-21T12:25:10Z Cache configuration: 2024-03-21T12:25:10Z * Using 2.0 MiB for block index database 2024-03-21T12:25:10Z * Using 56.0 MiB for transaction index database 2024-03-21T12:25:10Z * Using 8.0 MiB for chain state database 2024-03-21T12:25:10Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2024-03-21T12:25:10Z init message: Loading block index… 2024-03-21T12:25:10Z Assuming ancestors of block 000000000001323071f38f21ea5aae529ece491eadaccce506a59bcc2d968917 have valid signatures. 2024-03-21T12:25:10Z Setting nMinimumChainWork=000000000000000000000000000000000000000000000c59b14e264ba6c15db9 2024-03-21T12:25:10Z Opening LevelDB in /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/blocks/index 2024-03-21T12:25:10Z Opened LevelDB successfully 2024-03-21T12:25:10Z Using obfuscation key for /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/blocks/index: 0000000000000000 2024-03-21T12:25:18Z LoadBlockIndexDB: last block file = 243 2024-03-21T12:25:18Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=377, size=77285114, heights=2582462...2582883, time=2024-03-18...2024-03-21) 2024-03-21T12:25:18Z Checking all blk files are present... 2024-03-21T12:25:23Z Initializing chainstate Chainstate [ibd] @ height -1 (null) 2024-03-21T12:25:23Z Opening LevelDB in /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/chainstate 2024-03-21T12:25:23Z Opened LevelDB successfully 2024-03-21T12:25:23Z Using obfuscation key for /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/chainstate: 15c231132368eddf 2024-03-21T12:25:24Z Loaded best chain: hashBestChain=0000000001413dd752ecefeb8cd5d84fe3fb2fc8b5f9f6fc5ee3e927d63ee3e3 height=2582883 date=2024-03-21T09:53:33Z progress=0.999821 2024-03-21T12:25:24Z Opening LevelDB in /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/chainstate 2024-03-21T12:25:24Z Opened LevelDB successfully 2024-03-21T12:25:24Z Using obfuscation key for /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/chainstate: 15c231132368eddf 2024-03-21T12:25:24Z [Chainstate [ibd] @ height 2582883 (0000000001413dd752ecefeb8cd5d84fe3fb2fc8b5f9f6fc5ee3e927d63ee3e3)] resized coinsdb cache to 8.0 MiB 2024-03-21T12:25:24Z [Chainstate [ibd] @ height 2582883 (0000000001413dd752ecefeb8cd5d84fe3fb2fc8b5f9f6fc5ee3e927d63ee3e3)] resized coinstip cache to 384.0 MiB 2024-03-21T12:25:24Z init message: Verifying blocks… 2024-03-21T12:25:24Z Verifying last 6 blocks at level 3 2024-03-21T12:25:24Z Verification progress: 0% 2024-03-21T12:25:24Z Verification progress: 16% 2024-03-21T12:25:24Z Verification progress: 33% 2024-03-21T12:25:24Z Verification progress: 50% 2024-03-21T12:25:24Z Verification progress: 66% 2024-03-21T12:25:24Z Verification progress: 83% 2024-03-21T12:25:24Z Verification progress: 99% 2024-03-21T12:25:24Z Verification: No coin database inconsistencies in last 6 blocks (3224 transactions) 2024-03-21T12:25:24Z block index 14582ms 2024-03-21T12:25:24Z Opening LevelDB in /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/indexes/txindex 2024-03-21T12:25:24Z Opened LevelDB successfully 2024-03-21T12:25:24Z Using obfuscation key for /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/indexes/txindex: 0000000000000000 2024-03-21T12:25:24Z Setting NODE_NETWORK on non-prune mode 2024-03-21T12:25:24Z block tree size = 2582900 2024-03-21T12:25:24Z nBestHeight = 2582883 2024-03-21T12:25:24Z initload thread start 2024-03-21T12:25:24Z txindex thread start 2024-03-21T12:25:24Z torcontrol thread start 2024-03-21T12:25:24Z txindex is enabled at height 2582883 2024-03-21T12:25:24Z txindex thread exit 2024-03-21T12:25:24Z Loading 0 mempool transactions from disk... 2024-03-21T12:25:24Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast 2024-03-21T12:25:24Z AddLocal([2a02:a03f:65fc:3900:d3:ed27:d3be:fce4]:18333,1) 2024-03-21T12:25:24Z initload thread exit 2024-03-21T12:25:24Z Discover: IPv6 en0: 2a02:a03f:65fc:3900:d3:ed27:d3be:fce4 2024-03-21T12:25:24Z AddLocal([2a02:a03f:65fc:3900:3128:fcaf:af7e:67bf]:18333,1) 2024-03-21T12:25:24Z Discover: IPv6 en0: 2a02:a03f:65fc:3900:3128:fcaf:af7e:67bf 2024-03-21T12:25:24Z Bound to 127.0.0.1:18334 2024-03-21T12:25:24Z Bound to [::]:18333 2024-03-21T12:25:24Z Bound to 0.0.0.0:18333 2024-03-21T12:25:24Z Loaded 2 addresses from "anchors.dat" 2024-03-21T12:25:24Z 2 block-relay-only anchors will be tried for connections. 2024-03-21T12:25:24Z init message: Starting network threads… 2024-03-21T12:25:24Z net thread start 2024-03-21T12:25:24Z msghand thread start 2024-03-21T12:25:24Z init message: Done loading 2024-03-21T12:25:24Z dnsseed thread start 2024-03-21T12:25:24Z addcon thread start 2024-03-21T12:25:24Z opencon thread start 2024-03-21T12:25:24Z Waiting 300 seconds before querying DNS seeds. 2024-03-21T12:25:26Z New block-relay-only v1 peer connected: version: 70016, blocks=2582896, peer=0 2024-03-21T12:25:26Z New block-relay-only v1 peer connected: version: 70015, blocks=2582896, peer=1 2024-03-21T12:25:26Z Leaving InitialBlockDownload (latching to false) 2024-03-21T12:25:27Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=2 2024-03-21T12:25:41Z UpdateTip: new best=0000000000001d479ec743b442d19ca113a8bb515657375e5bc73bb427589b58 height=2582884 version=0x24000000 log2_work=75.721318 tx=74493222 date='2024-03-21T10:13:35Z' progress=0.999844 cache=1.4MiB(10376txo) 2024-03-21T12:25:41Z UpdateTip: new best=000000000005f611289a6a6b9c25e48a88c6345971a66f93597b021e6c02305a height=2582885 version=0x20006000 log2_work=75.721318 tx=74494054 date='2024-03-21T10:33:36Z' progress=0.999868 cache=1.7MiB(12475txo) 2024-03-21T12:25:41Z UpdateTip: new best=0000000000000014aa6098952b4f6305d22f403ffe1c367f1aced9595049ba87 height=2582886 version=0x20006000 log2_work=75.721327 tx=74494316 date='2024-03-21T10:34:33Z' progress=0.999869 cache=1.7MiB(12646txo) 2024-03-21T12:25:42Z UpdateTip: new best=00000000000000281c1641f68b6c2434b5e82b31a910e76f99f5d95d9b136e91 height=2582887 version=0x27000000 log2_work=75.721337 tx=74494894 date='2024-03-21T10:45:18Z' progress=0.999882 cache=1.8MiB(13913txo) 2024-03-21T12:25:42Z UpdateTip: new best=000000000000000794b75c5810e374fd09dd9a4a57c9acabd448906ad8af05eb height=2582888 version=0x2d108000 log2_work=75.721347 tx=74495471 date='2024-03-21T10:53:25Z' progress=0.999891 cache=2.1MiB(14848txo) 2024-03-21T12:25:42Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=3 2024-03-21T12:25:42Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=4 2024-03-21T12:25:42Z UpdateTip: new best=00000000000000188c9c97985ec2f55f5f6bec62d64c6398c8f5febdddc48ac3 height=2582889 version=0x20400000 log2_work=75.721356 tx=74495570 date='2024-03-21T11:08:55Z' progress=0.999909 cache=2.1MiB(14996txo) 2024-03-21T12:25:42Z UpdateTip: new best=0000000000000001fca621083c80470ee09dafbd8c004d3ac6c2137a04d0e14e height=2582890 version=0x20800000 log2_work=75.721366 tx=74495576 date='2024-03-21T11:09:41Z' progress=0.999910 cache=2.1MiB(15003txo) 2024-03-21T12:25:43Z UpdateTip: new best=000000000015113b2f8571b60a0083f78cb63dfb58a8a97ed7fb2b01f21a6d56 height=2582891 version=0x20000000 log2_work=75.721366 tx=74497178 date='2024-03-21T11:29:42Z' progress=0.999934 cache=2.4MiB(18049txo) 2024-03-21T12:25:43Z UpdateTip: new best=000000000000000a32bf07228860ccfbbc151604895d80b0c6421fd8c80d5aed height=2582892 version=0x20600000 log2_work=75.721376 tx=74497691 date='2024-03-21T11:36:27Z' progress=0.999942 cache=2.6MiB(19052txo) 2024-03-21T12:25:44Z UpdateTip: new best=0000000022c6cf5f7d952fcef00187b65f602f7dd19437addbb0be705329b5f5 height=2582893 version=0x20000000 log2_work=75.721376 tx=74498416 date='2024-03-21T11:56:29Z' progress=0.999966 cache=2.7MiB(20552txo) 2024-03-21T12:25:44Z UpdateTip: new best=00000000000000245745b0c766f31eefb68659815497e00b7e9b1cd055b68800 height=2582894 version=0x20200000 log2_work=75.721385 tx=74498439 date='2024-03-21T11:58:16Z' progress=0.999968 cache=2.7MiB(20576txo) 2024-03-21T12:25:44Z UpdateTip: new best=000000000000000ecac067910bd15815af4eec6c548104da35e3ceade9c5427c height=2582895 version=0x264a8000 log2_work=75.721395 tx=74498931 date='2024-03-21T12:03:26Z' progress=0.999974 cache=2.9MiB(21240txo) 2024-03-21T12:25:44Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=5 2024-03-21T12:25:44Z UpdateTip: new best=000000000000001938c3292b75d0135886a215b123ee409e80bde56e13e50e5c height=2582896 version=0x20800000 log2_work=75.721404 tx=74499797 date='2024-03-21T12:17:47Z' progress=0.999991 cache=3.0MiB(23166txo) 2024-03-21T12:25:46Z P2P peers available. Skipped DNS seeding. 2024-03-21T12:25:46Z dnsseed thread exit 2024-03-21T12:26:00Z New outbound-full-relay v1 peer connected: version: 70015, blocks=2582896, peer=6 2024-03-21T12:26:01Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=7 2024-03-21T12:26:02Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=8 2024-03-21T12:26:02Z New outbound-full-relay v1 peer connected: version: 70016, blocks=2582896, peer=9 2024-03-21T12:29:27Z New block-relay-only v2 peer connected: version: 70016, blocks=2582896, peer=10
|
|
|
It seems like the problem is the settings.json file. It is automatically generated by Bitcoin Core and in testnet no wallets are produced but in mainnet I have all wallets.
|
|
|
Ok, thanks for the first flag!
But for the loadwallets why? I never used it and everything worked well testnet as well as mainnet. Is it only the dual dash you think?
|
|
|
Ok thanks for your answer. It works for the RPC command.
But I still don't see my wallets loaded I don't understand why:
2024-03-20T14:20:00Z Using wallet directory /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/wallets 2024-03-20T14:20:00Z init message: Verifying wallet(s)… 2024-03-20T14:20:00Z Using /16 prefix for IP bucketing 2024-03-20T14:20:00Z init message: Loading P2P addresses… 2024-03-20T14:20:00Z Loaded 6497 addresses from peers.dat 19ms
$ bitcoin-cli -testnet -datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3 listwallets [ ]
Don't have any ideas about why.
|
|
|
Hello everyone,
I post a message here cause I'm bothering to struggle too much with my bitcoind testnet and need some help to understand what's happening.
Before everything was working good. I updated the last version Bitcoin Core version v27.99.0-015ac13dcc96 and now a lot of issues with my testnet node...
So where to begin?
I'm on MacOS (LTS) and I'm using an external hard disk to store everything.
PATH=/Volumes/Crucial\ X8/bitcoin/Bitcoin
I first struggled with config cause my `bitcoind` can't apply [test] section I don't know why. So, I'm using ./testnet3/bitcoin.conf.
# Testnet bitcoin.conf printtoconsole=1 rpcallowip=127.0.0.1 testnet=1 [test] rpcport=18332 rpcbind=127.0.0.1
I'm running the node with: bitcoind -datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3 -txindex=1 -testnet
I copied blocks and indexes into ./testnet3/testnet3 ^^' cause apparently if ./testnet3 is the datadir it will create a testnet3 nested folder.
The cookie file is into ./testnet3, but when I launch bitcoin-cli it told me:
$ bitcoin-cli -testnet -conf=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/bitcoin.conf help error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set. See -rpcpassword and -stdinrpcpass. Configuration file: (/Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/bitcoin.conf)
This is the first problem quite important.
BUT a second problem: my wallets stored into ./testnet3/wallets AND ./testnet3/testnet3/wallets are not opened by the node:
2024-03-20T11:55:06Z Using wallet directory /Volumes/Crucial X8/bitcoin/Bitcoin/testnet3/testnet3/wallets 2024-03-20T11:55:06Z init message: Verifying wallet(s)… 2024-03-20T11:55:06Z Using /16 prefix for IP bucketing
It verifies wallets but nothing after...
If I launch the node in mainnet, from PATH (./) wallets are well opened. I don't uderstand why, what happen and no idea about how to solve it.
I can give any additional required details about this to try to solve it ^^'
Thank you in advance for your consideration
|
|
|
Hello,
As the first message on this post, I need some tBTC for a project. We can buy for some sats but we need something like 3-4 tBTC.
If you know anyone interested feel free to comment here and we can chat about it.
Thanks,
GaloisField
|
|
|
Ok ! With command line args it works.
But it could be cooler to just have the config file to setup and not re write a long cli args to put each time.
So, it's not necessary but cool for the next ^^
|
|
|
The absolute path doesn't work with error : ./bin/bitcoind -conf=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/bitcoin.conf -walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/wallets -txindex=1 -testnet
Assertion failed: (base.is_absolute()), function AbsPathJoin, file fs.cpp, line 37. [1] 28624 abort ./bin/bitcoind -txindex=1 -testnet
A problem is also that in my main config we can see that I set /Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets/main as walletdir path but when I run bitcoind, it's still set with walletdir : /Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets and so it doesn't find any wallet.
|
|
|
Hello,
I have a weird issue with my configuration. I tried many things and nothing really works well.
For now if the following can works it could be good.
Context : I've got MacOS last version and my hard drive 1Tb connected. I'm running everything from the path '/Volumes/Crucial X8/bitcoin/Bitcoin'.
Objectives : Run my node is testnet and in mainnet with different configs properly with `bitcoind`. Everything related to the node should be into the hard drive (obviously, I don't have enough space on my computer haha).
Config file : # Listen for connections on this port (default: 8333): port=8332
# Network-related settings: # Bind to given address and whitelist peers connecting to it: bind=127.0.0.1
# JSON-RPC options: # Server for JSON-RPC connections (default: 127.0.0.1) #rpcbind=127.0.0.1 # Username for JSON-RPC connections #rpcuser=rpc_bitcoin # Password for JSON-RPC connections #rpcpassword=rpc_bitcoin
# Miscellaneous options: # Size of the "memory pool" for transactions awaiting confirmation (default: 300MB) #maxmempool=300
# File containing masternodes IPs and rewards private key #masternode=
# Reduce storage requirements by only storing most recent N blocks (default: 288) #prune=550
[main] datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin blocksdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/blocks walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets/main conf=bitcoin.conf spendzeroconfchange=1 txindex=1 rpcworkqueue=128 settings=/Volumes/Crucial\ X8/bitcoin/Bitcoin/settings.json
[test] testnet=1 datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3 blocksdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/blocks walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets/test addnode=testnet.blixtwallet.com settings=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/settings.json
Folder structure : | - bitcoin.conf | | bin -- bitcoind | | blocks -- | blocks -- | index -- | tesnet3 -- blocks | | indexes -- | txindex | | wallets -- | main -- MyMainWallets -- | test -- MyTestsWallets | | testnet3 -- bitcoin.conf (for some tests but bitcoind couldn't read it. I don't know why cause all rights are openned) -- | bin -- bitcoind and others -- | blocks -- *.dat -- | index -- *.log -- | wallets -- MyTestsWallets -- | indexes -- | txindex
Command run : - For mainnet : ./bin/bitcoind -conf=bitcoin.conf -txindex=1. With this command the problem now is : Using wallet directory /Volumes/Crucial X8/bitcoin/Bitcoin/wallets which should be with wallets/main for mainnet. - For testnet : The same with the flag -testnet. And here I got the error : Error: Config setting for -walletdir only applied on test network when in [test] section. But as we can see in config file it's well setup for each network. And the fact that mainnet doesn't read properly the wallet dir path seems to show a problem.
I don't know how can I solve this misleading configuration. I tried to do everything in testnet3 folder, but I already built a part of the testnet in the main folder. So I'm wondering if it's possible to make work my configuration.
Maybe you can have some ideas. I don't know.
I can move it if it's not in the right place ^^
Also, when I'm trying to run bitcoind from the fodler testnet3 with : ./bin/bitcoind -conf=bitcoin.conf -walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/wallets -txindex=1 -testnet I have this in the launch : 2023-12-21T16:07:06Z Config file: /Volumes/Crucial X8/bitcoin/Bitcoin/bitcoin.conf 2023-12-21T16:07:06Z Config file arg: blocksdir="/Volumes/Crucial X8/bitcoin/Bitcoin/blocks" 2023-12-21T16:07:06Z Config file arg: conf="/Volumes/Crucial X8/bitcoin/Bitcoin/bitcoin.conf" 2023-12-21T16:07:06Z Config file arg: datadir="/Volumes/Crucial X8/bitcoin/Bitcoin" 2023-12-21T16:07:06Z Config file arg: settings="/Volumes/Crucial X8/bitcoin/Bitcoin/settings.json" 2023-12-21T16:07:06Z Config file arg: walletdir="/Volumes/Crucial X8/bitcoin/Bitcoin/wallets" Which is not what is specified in the bitcoin.conf file into testnet3 : [test] conf=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/bitcoin.conf datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3 blocksdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/blocks walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/wallets addnode=testnet.blixtwallet.com settings=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/settings.json I don't understand why the node is not syncing on the right conf file...
|
|
|
Hello,
I have a weird issue with my configuration. I tried many things and nothing really works well.
For now if the following can works it could be good.
Context : I've got MacOS last version and my hard drive 1Tb connected. I'm running everything from the path '/Volumes/Crucial X8/bitcoin/Bitcoin'.
Objectives : Run my node is testnet and in mainnet with different configs properly with `bitcoind`. Everything related to the node should be into the hard drive (obviously, I don't have enough space on my computer haha).
Config file : # Listen for connections on this port (default: 8333): port=8332
# Network-related settings: # Bind to given address and whitelist peers connecting to it: bind=127.0.0.1
# JSON-RPC options: # Server for JSON-RPC connections (default: 127.0.0.1) #rpcbind=127.0.0.1 # Username for JSON-RPC connections #rpcuser=rpc_bitcoin # Password for JSON-RPC connections #rpcpassword=rpc_bitcoin
# Miscellaneous options: # Size of the "memory pool" for transactions awaiting confirmation (default: 300MB) #maxmempool=300
# File containing masternodes IPs and rewards private key #masternode=
# Reduce storage requirements by only storing most recent N blocks (default: 288) #prune=550
[main] datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin blocksdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/blocks walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets/main conf=bitcoin.conf spendzeroconfchange=1 txindex=1 rpcworkqueue=128 settings=/Volumes/Crucial\ X8/bitcoin/Bitcoin/settings.json
[test] testnet=1 datadir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3 blocksdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/blocks walletdir=/Volumes/Crucial\ X8/bitcoin/Bitcoin/wallets/test addnode=testnet.blixtwallet.com settings=/Volumes/Crucial\ X8/bitcoin/Bitcoin/testnet3/settings.json
Folder structure : | - bitcoin.conf | | bin -- bitcoind | | blocks -- | blocks -- | index -- | tesnet3 -- blocks | | indexes -- | txindex | | wallets -- | main -- MyMainWallets -- | test -- MyTestsWallets | | testnet3 -- bitcoin.conf (for some tests but bitcoind couldn't read it. I don't know why cause all rights are openned) -- | bin -- bitcoind and others -- | blocks -- *.dat -- | index -- *.log -- | wallets -- MyTestsWallets -- | indexes -- | txindex
Command run : - For mainnet : ./bin/bitcoind -conf=bitcoin.conf -txindex=1. With this command the problem now is : Using wallet directory /Volumes/Crucial X8/bitcoin/Bitcoin/wallets which should be with wallets/main for mainnet. - For testnet : The same with the flag -testnet. And here I got the error : Error: Config setting for -walletdir only applied on test network when in [test] section. But as we can see in config file it's well setup for each network. And the fact that mainnet doesn't read properly the wallet dir path seems to show a problem.
I don't know how can I solve this misleading configuration. I tried to do everything in testnet3 folder, but I already built a part of the testnet in the main folder. So I'm wondering if it's possible to make work my configuration.
Maybe you can have some ideas. I don't know.
I can move it if it's not in the right place ^^
|
|
|
Ok ! Yes totally you're right !
Thanks a lot for all your help !!!🙏🙏🙏
|
|
|
|