okay... so is this normal? i just did a internal wallet to wallet xfer and seems like everything went okay ... but then when i loaded the following time i saw the accounting entry..
The key is present and all otherwise it wouldn't of approved he push... it seems stuck to me as it has not reflected yet and i see it want 4.7db citing a mismatch on 4.8
Im out of my element on this, how can i have it complete what is in a accepted paused state ... i dont have the slightest idea and cannot find 4.7 anywhere
so if someone knows how to resolve it please let me know..... Here is some of the outputs censored.
data was written to the wallet.. accepted was indicated... did a subtract but then froze after that citing an mismatch or hell if i know..
Can someone help me and ill tip them ...
Move '2nd wallet' 200000000000 (other: '1st wallet, time: Wed Feb 23 18:33:10 2022, entry 2) ☺️☺️n☺️8
Move '1st wallet' -200000000000 (other: '2ndwallet', time: Wed Feb 23 18:33:10 2022, entry 1) ☺️☺️n☺️7
account" : "1st intenral wallet",
"category" : "move",
"time" : 1645669990,
"amount" : -2000.00000000,
"otheraccount" : "2nd internal wallet",
"comment" : ""
},
{
"account" : "2nd internal wallet",
"category" : "move",
"time" : 1645669990,
"amount" : 2000.00000,
"otheraccount" : "1st internal wallett",
"comment" : ""
}
NotifyAddressBookChanged 2nd internal wallett isMine=0 status=0
Flushing wallet.dat
Flushed wallet.dat 76ms
AddToWallet 8645b5eb1f
NotifyTransactionChanged 8645b5eb1f8fda4c803d463ea4657a90b549b03d3274dd24e86dd459d91efe73 status=1
received block 0000000000000d33038f
SetBestChain: new best=0000000000000d33038f height=155626 work=178118820252315657527 date=12/01/11 23:26:19
ProcessBlock: ACCEPTED
received block 0000000000000e14c5da
updateWallet 8645b5eb1f8fda4c803d463ea4657a90b549b03d3274dd24e86dd459d91efe73 1
inWallet=1 inModel=1 Index=3-4 showTransaction=1 derivedStatus=1
Then i pulled it again and saw this
"acentry": [
"1st internal wallet",
-200000000000,
"2nd internal wallet",
"Wed Feb 23 18:33:10 2022",
1,
"\u0000\u0001\u0001n\u00017"
],
"bestblock": "00000000000000480ad86800491315535a4a71bbe51b5d595b7e7e1cd6851987",
Did i do something wrong? ..
The Bitcoin-qt/bitcoind wallet.dat file is a
BerkeleyDB database. It contains several different data stores. Here's a dump of a new wallet (with just two reserve addresses for future use)
{
"acc": "",
"bestblock": "000000000000036011761a18097da44837e45d2997473cdbb5073900e7e6e7ac",
"defaultkey": "1ynUnWB9JJ9nDzS8sWDA2Dm3oDuMW2zHp",
"keys": [
{
"addr": "1H5YWGN4wxSMQVkxeNvt7143Tb2sx5btcF",
"hexsec": "5f73b6e3433d3dcc0ff581a972e675c6b90b2400a5172fe2e41d38b7cdb741a0",
"reserve": 1,
"sec": "5JYKmuHP165m8aRbkuQbtotV4rzfbNTSSVmoNqjBqPJgkvzaSxd"
},
{
"addr": "18pXbTAXH8yQ3G7YJtebgDjcMBP6ecmuJK",
"hexsec": "df8b1541844beace15abc9c60dac6ecbb55e2119e7f134abe4e5d2da862d0fa0",
"reserve": 1,
"sec": "5KWjhFuqmtn5YGvErQ9prWcjCKGixZXeskQtR8WTnyTkAS8LdjM"
},
{
"addr": "1ynUnWB9JJ9nDzS8sWDA2Dm3oDuMW2zHp",
"hexsec": "f60a32974e7dc594ec5fa68b8e240e379e1cb2e3df251ddc57d85c4489f846a0",
"label": "",
"sec": "5KgeLcBKufAUium7DGtbbe1mXYFQsvXE2GAuweRjQ7QMwxhqxiU"
}
],
"minversion": "unsupported",
"names": {
"1ynUnWB9JJ9nDzS8sWDA2Dm3oDuMW2zHp": ""
},
"orderposnext": "unsupported",
"pool": [
{
"addr": "18pXbTAXH8yQ3G7YJtebgDjcMBP6ecmuJK",
"n": 2,
"nTime": 1364628317
},
{
"addr": "1H5YWGN4wxSMQVkxeNvt7143Tb2sx5btcF",
"n": 3,
"nTime": 1364628317
}
],
"settings": {
"addrIncoming": "0.0.0.0:0"
},
"tx": [],
"version": 80000
}An analysis of some of the things in the wallet - we see that every time a new block is received, data is written to the wallet:
"acc": "",Assign account name to address - rarely used
"bestblock": "000000000000036011761a18097da44837e45d2997473cdbb5073900e7e6e7ac",
The last block hash seen on the network, so wallet knows where to start scanning for new payments
"defaultkey": "1ynUnWB9JJ9nDzS8sWDA2Dm3oDuMW2zHp",
The key that is offered as "your receiving address" (used to automatically change in Bitcoin < 0.4)
"keys": [ ...The store of public/private keys. "reserve": 1 means the address is a reserve key
"minversion": "unsupported", Option if future wallets are backwards-incompatible
"names": { ...Labels applied to addresses/address book
"orderposnext": "unsupported", Database position counter
"pool": [ ...List of reserve pool addresses in order they should be used
"settings": {Most user settings have been moved to the registry on Windows.
"tx": [], ...A list of all transactions sent and received/seen on the network relating to wallet addresses
"version": 80000Bitcoin version that created wallet/current version (if upgraded by software)
Also from
http://bitcoin.stackexchange.com/questions/3173/what-information-does-a-wallet-contain name - an address book name
tx - a transaction
acentry - an accounting entry
key - a pair of public and private keys
mkey - a master key
ckey - an encrypted key
defaultkey - the default receiving address' key
pool - a keypool entry
version - the version of the software that wrote this wallet
minversion - the earliest version of the software that can read this wallet
cscript - a script
bestblock - a pointer to the end of the best blockchain seen
wkey - a private key (no longer used)
setting - used to store user interface settings (no longer used, except to hold an invalid setting to stop pre-0.4.0 versions of the client which don't understand minversion from loading wallets that are too new for them)
