Re: ██ 🌟🌟🌟 [SIL] 611 SIXELEVEN ◥◣ BLOCKCHAIN DOMAIN NAME SYSTEM ◥◣ 🌟🌟🌟██
WOW, thanks for your awesome summary on your debugging experience 
I just did start my wallet, but I see the message inside:
Wanted resynchronize wallet. Just deleted all files with old blockchain, and started the wallet again...
Synchronization was been stopped at block 171.
The same problem...
Start...
Synchronization was been stopped at block 171...
Again restart... Again, and again...
Finally! Synchronization is processing now... Why? I don't know...
Did you check the outputs in debug.log?
Meanwhile you can have a look at pyWallet for these kind of tasks.
Confirmed. I did try to send the raw transaction today and failed with the error that it has already been processed.
Had a similar issue a few month ago trying to renew a domain name with expiration > 10k blocks. A specific check function caused other clients to block this renew requests for quite some time (until client restart) but finally it did renew without any issues at a later date.
You are welcome to share your raw transaction or send me a priv. msg for debugging.
See my way...You are welcome to share your raw transaction or send me a priv. msg for debugging.
I just did start my wallet, but I see the message inside:
Quote
WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
Hm... Ok... Maybe something with blockchain?Wanted resynchronize wallet. Just deleted all files with old blockchain, and started the wallet again...
Synchronization was been stopped at block 171.
The same problem...
Quote
WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
Ok... Go to github, download latest wallet for windows x32 and x64.Start...
Synchronization was been stopped at block 171...
Again restart... Again, and again...
Finally! Synchronization is processing now... Why? I don't know...
Ok, will wait the end of sync... After full synchonization, I see incorrect transactions in wallet...
This was been updated not correctly...
I just tried to spend coins, but this says about coins already spent, and no any coins on that unspent output...
Ok... Maybe... Need... To... Delete wallet.dat, and start with new one?..
Did you run 611d with the "-rescan" option?This was been updated not correctly...
I just tried to spend coins, but this says about coins already spent, and no any coins on that unspent output...
Ok... Maybe... Need... To... Delete wallet.dat, and start with new one?..
But, no... Need to just dump private keys at first...
Ok! Go to console... Wanted to dumpwallet.
Ack: "add dumpwallet and importwallet" should be considered to be added with the upcoming releases.Ok! Go to console... Wanted to dumpwallet.
Code:
dumpwallet "file_path/filename.extension"
But...Quote
Method not found (-32601)
Ok... So you don't have dumpwallet option, to save all privkeys in human-readable file, like this have ReddByteCoin for exampleMeanwhile you can have a look at pyWallet for these kind of tasks.
Quote from: crypto_trader#43xzEXrP link=topic=1235629.msg52569320#msg52569320
Then... Go to list of addresses for receive... Copy this... Then...
[code
Then... Go to list of addresses for receive... Copy this... Then...
[code
dumpprivkey address1
-> privkey1
dumpprivkey address2
-> privkey2
etc...
[/code]
Then just add this to .txt-file.
And I think... Maybe... I can to delete this wallet.dat...
But... Stop. Just rename this.
Restart 611-qt.exe...
I see new wallet.dat created.
Then...
Dont' worry. You have to rescan the blockchain to add your balance using the "-rescan" option on 611d startup.-> privkey1
dumpprivkey address2
-> privkey2
etc...
[/code]
Then just add this to .txt-file.
And I think... Maybe... I can to delete this wallet.dat...
But... Stop. Just rename this.
Restart 611-qt.exe...
I see new wallet.dat created.
Then...
Code:
importprivkey privkey1
-> ok
importprivkey privkey2
-> ok
...
But... balance is ZERO.-> ok
importprivkey privkey2
-> ok
...
Quote from: crypto_trader#43xzEXrP link=topic=1235629.msg52569320#msg52569320
[...
[...
See my coins in the wallet. See only incoming transactions, because this is new wallet...
Then... Just want to register the name...
Do it... See another address generated as owner of this domain name. Maybe coins will go there?.. Hm...
Configure domain name, and send transaction.
Finally, I see my transaction... Just need to wait confirmations...
But... I see blockchain size is growing, synchronization is processed, but no one miner cann't include my transaction...
Maybe, this is not in rawmempool?
Go to console.
Hm... What happened?
Transaction hash is dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813
And... No any result...
Based on the foregoing, a number of important issues are brewing:
Can you broadcast this my signed RAW-transaction in the miners, from your working wallet, using this hexadecimal value?
Do you see this transaction in "getrawmempool" now?
Can you make the service to broadcast the signed raw-transactions online,
service, like this: https://www.blockchain.com/ru/btc/pushtx ?
Can you make "dumpwallet" option, to save ALL privkeys as human-readable file,
like in ReddByteCoin source-code?
Can you add EACH generated address in the list of address for receive coins, to dump privkey from this?
Can I disable randomly generation of the addresses, and use just one address for each operation?
Can I using my address as address of owner the domain, or set it,
because this is generated randomly, and changed after each operation,
and after wallet is generate this address, this address is available just for copy this, not to change this,
and coins are moved from address to address every time.
If wallet.dat will be damaged, or data will be corrupted, knowledge of my own privkey will not give nothing for me.
Can you make redirect to https://be.611.to/ from http://be.611.to/ within 3 seconds, with ability to cancel this redirect?
Just because transferring addresses and balances as open text over http is not secure, while working the sniffers of traffic.
Do you have online on your block-explorer, the list of unconfirmed transactions?
What version of 611-qt.exe is very-very stable?
Why sometimes, new 611-qt.exe just closing, without any warnings, after enter the command in console? Is there any log-file?
That's all questions from me, right now...
UPD: My transaction was been broadcasted by someone, and confirmed.
After this, I did open my wallet, and I see two more transaction was been generated.
This transactions have 0.00 amount, and this is "name_firstupdate", and "network fee".
Then, those two transactions was been sucessfully broadcasted from my wallet,
I saw it in "getrawmempool", and this already confirmed, now, and was been included immediately in the next block, generated by miners.
Then... Just want to register the name...
Do it... See another address generated as owner of this domain name. Maybe coins will go there?.. Hm...
Configure domain name, and send transaction.
Finally, I see my transaction... Just need to wait confirmations...
But... I see blockchain size is growing, synchronization is processed, but no one miner cann't include my transaction...
Maybe, this is not in rawmempool?
Go to console.
Code:
getrawmempool
And I see my transaction there...Hm... What happened?
Transaction hash is dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813
Code:
getrawtransaction dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813
63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000
63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000
Code:
signrawtransaction 63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000
{
"hex" : "63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b0000000048473044022011fc66657d4ce857524afc1812ad907dc4536fc07e484b3449255057643527cc022016d7e7346a28b29c512ffd0df3342d2294d73089d4a792d1f5ba7866abb5bfdf01ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000",
"complete" : true
}
{
"hex" : "63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b0000000048473044022011fc66657d4ce857524afc1812ad907dc4536fc07e484b3449255057643527cc022016d7e7346a28b29c512ffd0df3342d2294d73089d4a792d1f5ba7866abb5bfdf01ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000",
"complete" : true
}
Code:
sendrawtransaction 63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000
dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813
dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813
And... No any result...
Based on the foregoing, a number of important issues are brewing:
Can you broadcast this my signed RAW-transaction in the miners, from your working wallet, using this hexadecimal value?
Do you see this transaction in "getrawmempool" now?
Can you make the service to broadcast the signed raw-transactions online,
service, like this: https://www.blockchain.com/ru/btc/pushtx ?
Can you make "dumpwallet" option, to save ALL privkeys as human-readable file,
like in ReddByteCoin source-code?
Can you add EACH generated address in the list of address for receive coins, to dump privkey from this?
Can I disable randomly generation of the addresses, and use just one address for each operation?
Can I using my address as address of owner the domain, or set it,
because this is generated randomly, and changed after each operation,
and after wallet is generate this address, this address is available just for copy this, not to change this,
and coins are moved from address to address every time.
If wallet.dat will be damaged, or data will be corrupted, knowledge of my own privkey will not give nothing for me.
Can you make redirect to https://be.611.to/ from http://be.611.to/ within 3 seconds, with ability to cancel this redirect?
Just because transferring addresses and balances as open text over http is not secure, while working the sniffers of traffic.
Do you have online on your block-explorer, the list of unconfirmed transactions?
What version of 611-qt.exe is very-very stable?
Why sometimes, new 611-qt.exe just closing, without any warnings, after enter the command in console? Is there any log-file?
That's all questions from me, right now...
UPD: My transaction was been broadcasted by someone, and confirmed.
After this, I did open my wallet, and I see two more transaction was been generated.
This transactions have 0.00 amount, and this is "name_firstupdate", and "network fee".
Then, those two transactions was been sucessfully broadcasted from my wallet,
I saw it in "getrawmempool", and this already confirmed, now, and was been included immediately in the next block, generated by miners.
Confirmed. I did try to send the raw transaction today and failed with the error that it has already been processed.
Therefore, will be better to you add the option to broadcast signed RAW-transaction, as API method, here: https://be.611.to/q
Ok: it's on the TODO