<<  >> (p.34)
    Author Topic: 🌟🌟🌟 [SIL] 611 SIXELEVEN ◥◣ BLOCKCHAIN DOMAIN NAME SYSTEM 🌟🌟🌟  (Read 80294 times)
    crypto_trader#43xzEXrP
    Full Member
    ***
    Offline Offline

    Activity: 1588
    Merit: 214


    View Profile
    October 02, 2019, 01:23:19 PM
    Last edit: October 02, 2019, 01:40:15 PM by crypto_trader#43xzEXrP
     #661

    Now that I have to withdraw my currency exchange coins.
    In which wallet can I store them?
    You can using piWallet-based web-wallet: https://wallet.611.to/
    This no need to download blockchain, and available online.
    Also, you can download https://github.com/611project/sixeleven/releases
    Generate the address, dumprivkey from this, and send coins there.
    In this case, if you will not move your coins and will not pay anything, and just hold this,
    you can sign the transaction by privkey at anytime,
    and you can do "importprivkey" to another wallet, if this privkey will be saved.
    Also, you can just generate your address, then, dumpprivkey, then delete wallet.dat,
    and accept your coins to address.
    You can see balance on https://be.611.to/address/ADDRESS
    and while only you have your privkey, no one cann't spend your coins,
    and you can do "importprivkey" for this key at any time.
    But... If you will pay for someone or pay for name, then the rest of your coins inside qt-wallet
    will be moved to new addresses every time for each transfer,
    and in this case you need to do "dumpprivkey" for each address,
    because this is saved in "wallet.dat", and this file can be damaged, or data inside can be corrupted.  Grin
    So if this moving cannt' be disabled, will be better to using that piWallet-based web-wallet, IMHO.



    WOW, thanks for your awesome summary on your debugging experience Cool
    Hi, PatrickMacH! You can using preview button, before send your post.

    Did you check the outputs in debug.log?
    No, but now I saw this.
    I see long logs, in this old debug.log, and I just did search keyword "error" there.
    I see some errors:
    Code:
    ...
    dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
    ...
    ERROR: CheckProofOfWork() : hash doesn't match nBits
    ERROR: CheckProofOfWork() : proof of work failed
    ERROR: CBlock::ReadFromDisk() : errors in block header
    ...
    Warning: AddSupportingTransactions() : unsupported transaction
    CreateTransactionWithInputTx succeeded:
    CTransaction(hash=797007ac08, ver=611, vin.size=2, vout.size=3, nLockTime=0)
        CTxIn(COutPoint(0dadfa6ecf, 1), scriptSig=3046022100b8519a10d50ab7)
        CTxIn(COutPoint(7beec3fae5, 0), scriptSig=3045022100a603368498e2ed)
        CTxOut(nValue=663.63150000, scriptPubKey=04ef2be110d2a9f3ce158c13a0df3d)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    ...
    Warning: AddSupportingTransactions() : unsupported transaction
    CreateTransactionWithInputTx succeeded:
    CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    Automatic name_firstupdate created for name d/node (initial, with empty value), created tx: 1af560e2f8a0d7392ef2b4131c95ab3558fabe0112c46d09965133aa1e8cb0bf:
    CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    CommitTransaction:
    CTransaction(hash=dfcf12d47c, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(7beec3fae5, 0), scriptSig=30450220080139a5f4543e46)
        CTxOut(nValue=663.56040000, scriptPubKey=0407d3c66822825922820a249e3f6a)
        CTxOut(nValue=0.10110000, scriptPubKey=1 ff311d1b913c82d569fe20dc0526)
    ...
    CreateTransactionWithInputTx: total value = 10110000
    CreateTransactionWithInputTx: SelectCoins(0.00), nTotalValue = 0.1011, nWtxinCredit = 0.1011
    CreateTransactionWithInputTx: selected 0 tx outs, nValueIn = 0.00
    CreateTransactionWithInputTx succeeded:
    CTransaction(hash=8117e90750, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=304502205a1877dc70fbc028)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    Automatic name_firstupdate created for name d/node, created tx: 8117e9075088dd4fcb9ac7e7f15471775129f923aec2c9922424db0b3e5bcf65:
    CTransaction(hash=8117e90750, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=304502205a1877dc70fbc028)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    Warning: NameTablePriv::updateEntry: Got CT_UPDATED, but entry is not in model
    09/27/19 05:28:57 Flushing wallet.dat
    Flushed wallet.dat 74ms
    ...
    Exit program.

    Again start...
    ...
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (10841 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11646 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11267 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11699 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8658 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11653 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8477 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8932 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8481 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8940 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (9040 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11446 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (10531 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8041 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8945 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11438 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (11444 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8611 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: tx (8556 bytes)
    ERROR: AcceptToMemoryPool() : not enough fees
    received: inv (1765 bytes)
      got inventory: tx de2f4aca064ed6d8b0f1  new
    askfor tx de2f4aca064ed6d8b0f1   0
      got inventory: tx b8750d3a2969d3829239  new
    askfor tx b8750d3a2969d3829239   0
      got inventory: tx 474cb65e4ed2bde7ccc3  new
    askfor tx 474cb65e4ed2bde7ccc3   0
      got inventory: tx 52cb79f49be4a3bda41c  new
    askfor tx 52cb79f49be4a3bda41c   0
      got inventory: tx 95b12e661e4de3d08bbc  new
    askfor tx 95b12e661e4de3d08bbc   0
      got inventory: tx 2566113d34d701261b52  new
    askfor tx 2566113d34d701261b52   0
    ...
    Warning: AddSupportingTransactions() : unsupported transaction
    CreateTransactionWithInputTx succeeded:
    CTransaction(hash=797007ac08, ver=611, vin.size=2, vout.size=3, nLockTime=0)
        CTxIn(COutPoint(0dadfa6ecf, 1), scriptSig=3046022100b8519a10d50ab7)
        CTxIn(COutPoint(7beec3fae5, 0), scriptSig=3045022100a603368498e2ed)
        CTxOut(nValue=663.63150000, scriptPubKey=04ef2be110d2a9f3ce158c13a0df3d)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    ...
    CreateTransactionWithInputTx: total value = 10110000
    CreateTransactionWithInputTx: SelectCoins(0.00), nTotalValue = 0.1011, nWtxinCredit = 0.1011
    CreateTransactionWithInputTx: selected 0 tx outs, nValueIn = 0.00
    Warning: AddSupportingTransactions() : unsupported transaction
    CreateTransactionWithInputTx succeeded:
    CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    Automatic name_firstupdate created for name d/node (initial, with empty value), created tx: 1af560e2f8a0d7392ef2b4131c95ab3558fabe0112c46d09965133aa1e8cb0bf:
    CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
        CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
        CTxOut(error)
    CommitTransaction:
    CTransaction(hash=dfcf12d47c, ver=611, vin.size=1, vout.size=2, nLockTime=0)
        CTxIn(COutPoint(7beec3fae5, 0), scriptSig=30450220080139a5f4543e46)
        CTxOut(nValue=663.56040000, scriptPubKey=0407d3c66822825922820a249e3f6a)
        CTxOut(nValue=0.10110000, scriptPubKey=1 ff311d1b913c82d569fe20dc0526)
    keypool keep 3
    ...

    Another copy of old debug.log have lesser errors, only few:
    Code:
    ...
    ERROR: CheckProofOfWork() : hash doesn't match nBits
    ERROR: CheckProofOfWork() : proof of work failed
    ERROR: CBlock::ReadFromDisk() : errors in block header
    ...
    ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
    ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
    ...
    ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
    ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
    ...
    This is long debug.log, but there is no any more errors.







    Did you run 611d with the "-rescan" option?
    No, because after importing privkeys into the new wallet.dat,
    this was been rescanned automatically,
    and just need to wait some time to update balance, after privkey imported.
    But sometimes program was been closed, and also, I saw the some error of importing the key, in console.

    Now I did just restart 611-qr.exe with -rescan options, and old wallet.dat.
    Process:

    I did backup my files:
    1. log.lock
    2. addr.dat
    3. db.log
    4. wallet.dat
    5. nameindex.dat
    rename debug.log to debug1.log
    and new my wallet.dat to good_wallet.dat.
    Then I did just copy old wallet.dat to "data"-folder, and...

    Code:
    Try to run -rescan with synchronized blockchain, old wallet.dat and debug.log:

    folder_where_611-qt.exe>611-qt.exe -datadir="data" -rescan
    Long time loading...
    Done.
    But, I see old balance, and old unconfirmed transactions.
    So, This was been updated good, after "-rescan".
    Exit from the wallet.

    See debug.log.
    There is many info, but I did find keyword "error":
    ________________________
    dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
    ...
    LoadBlockIndex(): hashBestChain=0000000000000044ce97  height=369350
     block index           82244ms
    Loading wallet...
    nFileVersion = 61100
     wallet                  119ms
    Rescanning last 369350 blocks (from block 0)...
    ERROR: CheckProofOfWork() : hash doesn't match nBits
    ERROR: CheckProofOfWork() : proof of work failed
    ERROR: CBlock::ReadFromDisk() : errors in block header
    ...
    ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
    ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
    ...
    And... No any more message with errors, there.

    After this, I did rename debug.log to debug2.log, wallet.dat to old_wallet.dat, and good_wallet.dat to wallet.dat
    Try to run -rescan with synchronized blockchain, my currnet wallet.dat and new debug.log:
    Code:
    folder_where_611-qt.exe>611-qt.exe -datadir="data" -rescan
    ...
    new debug.log was been generated.
    long time loading...
    Done...
    All transactions are confirmed. Actual balance I see.
    Exit from wallet.

    Try to search keyword error in new debug.log:

    Code:
    dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
    ERROR: CheckProofOfWork() : hash doesn't match nBits
    ERROR: CheckProofOfWork() : proof of work failed
    ERROR: CBlock::ReadFromDisk() : errors in block header

    That's all...

    Maybe this all info can help you to find the reason of this errors, fix this, and repair something, maybe not, but I hope it.  Grin







    Ack: "add dumpwallet and importwallet" should be considered to be added with the upcoming releases.
    Meanwhile you can have a look at pyWallet for these kind of tasks.
    Ok.

    Don't worry. You have to rescan the blockchain to add your balance using the "-rescan" option on 611d startup.
    Ok. I already did run this, and I see... Result you can see in this post...

    Confirmed. I did try to send the raw transaction today and failed with the error that it has already been processed.
    Maybe, someone another did send this, as RAW-transaction, and then this was been broadcasted.

    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
    Ok.

    P.S.: I'm using win64 version in "611-qt_win32" folder.
    win32 version just was been renamed to old_611-qt.exe, and this was lagging too.
    I did start win32 version with Roaming folder, but win64 with "data"-folder, as portable wallet.

    STOP RUSSIAN INVASION OF UKRAINE - SUPPORT UKRAINIAN DEMOS
    Contact me in TOX: 653D6C2D13B6DF22C4CB93432586398858A608EE5457624A9A728BE1A9252C5DA12B894C54DB, or just crypto-trader@toxme.io.
    Also, WAVES - SCAM! ;(
Page 33
Viewing Page: 34