Transaction take very long to be confirmed
-
This post is deleted!
-
So in my case why the online wallet stop sync?
https://wallet.burst-team.us:8125/index.html
Last block: 282040
-
@Jumper That's exactly what is happening to me.
-
The only new thing that appears now to me is a unconfirmed income from the News Asset of @jervis . Man I really wanted to understand. I'll come back in a few hours, this last 2 I could'nt fix this.
-
Ok, please no panik ... missed the point that you all talk about online wallets.
Just go here http://util.burst-team.us:8888/ and click on a online-wallet, that is currently not stuck ... should be no problem?!
(@JotaJota sry i accident edited in your post above )
-
And what will happen to the transactions that are show in my wallet but is not confirmed, and I also cannot see this transaction using another wallet url.
-
@luxe When I enter from here, appears my deposit from poloniex, a income from the NewSilver asset, but not the income from the NEWS asset from @jervis that he sent 30 minutes ago.
-
@luxe do you have an idea when that wallet will be back? Cause, my transaction to BurstGames and my income from the NEWS Asset probably were using that wallet, so both are unconfirmed.
-
@Jumper @JotaJota Both of you maybe need to understand more, how this works.
It does not matter what wallet you use, data is on the blockchain ... all are in sync.
@JotaJota I can only check what happens to transactions, if you provide a transactionId, i do not know what could be the issue with jervis payout.
-
thanks. So the only thing to do for a transaction performed on the blocked wallet is to wait until issue is fixed.
-
@Jumper no just use another mirror of the online wallet:
-
@ luxe
I did provided TxID:
7585382108539246747 / 10/8/2016 19:55:35 Ordinary Payment 5'000 1 BURST-9DRH-PBKE-CGSB-3N53Q /
That is what I see under the blocked wallet history: 7585382108539246747
So what about that transaction?
-
I can not find a transaction with id: 7585382108539246747 so if that does not get confirmed by network, it will be refunded (after ~1500 blocks) ... and should have never happend if you use another mirror online wallet.
-
On the blocked wallet I see this:
image url)On the working wallet:
So wich balance is the correct?
-
Hi, I sent the payout 40 minutes ago and has still no confirmation yet. That's weird.
0
We offer a dynamic perspective on your investments
Pool: N.E.W.S. Mining Pool N.E.W.S. Website: https://news-asset.com
-
@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.
0We offer a dynamic perspective on your investments
Pool: N.E.W.S. Mining Pool N.E.W.S. Website: https://news-asset.com
-
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.
-
-
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:- New transactions are broadcast to all nodes.
- Each node collects new transactions into a block.
- Each node works on finding a difficult proof-of-work for its block.
- When a node finds a proof-of-work, it broadcasts the block to all nodes.
- Nodes accept the block only if all transactions in it are valid and not already spent.
- 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.
