Transaction take very long to be confirmed



  • On the blocked wallet I see this:

    0_1475964895343_Screen Shot 2016-10-08 at 23.14.04.png image url)

    On the working wallet:

    0_1475964967851_Screen Shot 2016-10-08 at 23.14.26.png

    So wich balance is the correct?



  • Hi, I sent the payout 40 minutes ago and has still no confirmation yet. That's weird. 0_1475964993384_Screenshot_3.png


  • admin

    @Jumper 8125 is stuck (not up-to-date), so i guess the 2nd.
    @jervis check your account in another wallet that online 8125, if the transactions never reached the network, just do them again ... maybe.



  • @luxe I'll wait it out. It's saturday night. Maybe the wallet is drunk or something. XD. It'll resync. I hope there is a timeout feature for the wallet if the request dont go through after how many cycles.


  • admin

    Burstcoin is a peer-to-peer network with a lot of nodes communicating, if a node is 'disconnected' from network, it is stuck ... and will have problems talking to the others ... understand?!

    If a transaction is done, it is ofcause in the data of the wallet, it was done with ... but if it does not get confirmed/send to the network ... no other node knows about that transaction and that means it never happend.



  • @luxe

    Yeap. Lets wait ;)

    i need to sleep. Bye now


  • admin

    I suggest reading this https://bitcoin.org/bitcoin.pdf to understand the basics of a crypto currency ... it explains very well how all works.

    Network
    The steps to run the network are as follows:

    1. New transactions are broadcast to all nodes.
    2. Each node collects new transactions into a block.
    3. Each node works on finding a difficult proof-of-work for its block.
    4. When a node finds a proof-of-work, it broadcasts the block to all nodes.
    5. Nodes accept the block only if all transactions in it are valid and not already spent.
    6. Nodes express their acceptance of the block by working on creating the next block in the
      chain, using the hash of the accepted block as the previous hash.

    Nodes always consider the longest chain to be the correct one and will keep working on
    extending it. If two nodes broadcast different versions of the next block simultaneously, some
    nodes may receive one or the other first. In that case, they work on the first one they received,
    but save the other branch in case it becomes longer. The tie will be broken when the next proof-
    of-work is found and one branch becomes longer; the nodes that were working on the other
    branch will then switch to the longer one.


  • admin

    @all The 8125 wallet was stuck, it's now caught up and working fine.



  • @luxemy wallet is good now.... all coins are in ....thks everyone...!!!


  • admin

    The online wallet was simply stuck. If the local wallet instance works for you and is up to date it is always recommend to use it.

    Online wallet is like a secure ATM in the streets. It can be out of order sometimes. If it breaks you need to wait until it gets fixed by someone else.

    The so called local wallet is like an ATM in your own house. If it breaks you can fix it yourself.

    Both give you the same access to the network.



  • @daWallet My AIO online wallet really is broken. It's not synching at all. I uninstalled it and reinstalled but still the same. Broken. I deleted the db folders and everything but still the wallet is broken when I installed again. When I use the same online AIO wallet on a different computer, it's okay. But in my computer it's broken. What to do?


  • admin

    @jervis There are many other threads about this topic. I made a run_safe_mode.bat you cases like yours. You can post what the command line tells you and we can figure out what is wrong.

    Another way would be to run the original wallet and tell us what error it throws at you: https://github.com/burst-team/burstcoin/releases



  • @daWallet i run the safe bat but the cmd just exits without giving any reports. :(



  • @daWallet
    C:\Users\JerViS\AppData\Roaming\BurstWallet>echo Checking Path only
    Checking Path only

    C:\Users\JerViS\AppData\Roaming\BurstWallet>for %f in (java.exe) do if exist %~$path:f (
    echo Java found at: %~$path:f
    set launch="BURST" %~$path:f -cp burst.jar;lib*;conf nxt.Nxt
    goto startup
    ) else (
    echo Not found in Path, Searching full C drive
    for /F "tokens=*" %f in ('C:\Windows\system32\where /F /R C:\ java.exe') do (
    echo Java found at: %f
    set launch="BURST" %f -cp burst.jar;lib*;conf nxt.Nxt
    goto startup
    )
    )

    C:\Users\JerViS\AppData\Roaming\BurstWallet>if exist C:\ProgramData\Oracle\Java\javapath\java.exe (
    echo Java found at: C:\ProgramData\Oracle\Java\javapath\java.exe
    set launch="BURST" C:\ProgramData\Oracle\Java\javapath\java.exe -cp burst.jar;lib*;conf nxt.Nxt
    goto startup
    ) else (
    echo Not found in Path, Searching full C drive
    for /F "tokens=*" %f in ('C:\Windows\system32\where /F /R C:\ java.exe') do (
    echo Java found at: java.exe
    set launch="BURST" java.exe -cp burst.jar;lib*;conf nxt.Nxt
    goto startup
    )
    )
    Java found at: C:\ProgramData\Oracle\Java\javapath\java.exe

    C:\Users\JerViS\AppData\Roaming\BurstWallet>REM Check for Burst jar

    C:\Users\JerViS\AppData\Roaming\BurstWallet>if exist burst.jar (start /wait "BURST" C:\ProgramData\Oracle\Java\javapath\java.exe -cp burst.jar;lib*;conf nxt.Nxt ) else (for /F "tokens=*" %f in ('C:\Windows\system32\where /F /R C:\ burst.jar') do (
    echo Burst.Jar found at: %f
    cd %~pf
    start /wait "BURST" C:\ProgramData\Oracle\Java\javapath\java.exe -cp burst.jar;lib*;conf nxt.Nxt
    ) )

    C:\Users\JerViS\AppData\Roaming\BurstWallet>pause
    Press any key to continue . . .



  • @daWallet I just run the original wallet. Thanks for this. I never knew that Burst Local wallet can run in Maxthon. Thank god I dont have to use IE for the local wallet :D



  • This post is deleted!

Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.