Topic: [ANN][GRA] Graincoin - New PoW/PoS coin | Fast, secure | Version 1.5 Released! - page 120. (Read 177059 times)

So around same time as me and Jollyburner

My time zone is GMT+8

we need to figure out if we got them at the same time, see my post.

im not sure what could cause this, if they aren't part of the blockchain they should just disappear I think...

anyways, if anyone else has some unconfirmed tx, plz post the local timezone you are in, or convert to UTC

http://www.worldtimebuddy.com/ - time converter super easy to use, pick the mini calendar if you need to change to yesterday.

thanks

*edit* ty Illus, i think we can expect then that all this problems occurred around the same time, approximately 10 hours ago. this may help bosian figure it out.

it appears that everything is still working ok, so just keep mining and if anymore tx get stuck like this plz update the thread immediately so devs know its a recurring problem.

Seems I also have 2 unconfirmed transactions from today. Both from solo mining.
This it what it shows in transaction details:

Status: 0/unconfirmed, broadcast through 11 node(s)
Date: 27.12.2013 08:10
Source: Generated
Credit: (not accepted)
Net amount: 0.00 GRA
Transaction ID: 9a5a23fb4234e91a1792002b6e15d1c884032c4afa4735c8836acc48ad023d6a
(In wallet it shows Amount 2045.00 GRA, but unconfirmed)

Status: 0/unconfirmed, broadcast through 10 node(s)
Date: 27.12.2013 07:26
Source: Generated
Credit: (not accepted)
Net amount: 0.00 GRA
Transaction ID: cbce55bad1c919561e00e5f7ea92497ef82e24463f47d7bd349231f8e3dc974a
(In wallet it shows Amount 1566.00 GRA, but unconfirmed)

Edit: GMT/UTC +2 here. So about same time as Jollyburner

I have an unconfirmed tx aswell, from forkpool:

Status: 0/unconfirmed
Date: 12/26/2013 21:36
From: unknown
To: --*I remove my forkpool address*-- (own address, label: fork)
Credit: 11706.318287 GRA
Net amount: +11706.318287 GRA
Transaction ID: c82304440eae47ffea1e557d49baa389e5fb39b843b72815bf6888b1d8ffefc0

I wonder why?

seems to be the only one, its around 9-9:30 pm pacific time dec 26th, 5-5:30am UTC/GMT dec 27th.

@esteeming, can you confirm the timezone you are in, or the GMT/UTC time/date of the transactions? im jw if they are at the same time, it may help identify the problem.

bosian, I am pool mining with forkpool.com and I did not have any problem before when receiving coins from this pool.

However, I find 3 of transactions from forkpool today are still NOT be confirmed after received more than 8 hours, can you please how to deal with these transactions?

Cheers, Esteeming.

PS. There is no sync issue of my wallet found so far - I had already tried to close the wallet and restart it, but above mention transaction problem still exist.

Status: 0/unconfirmed
Date: 12/27/2013 14:09
From: unknown
To: 9DiuNh5P98ZU977uTwe3udYmrbJoVf87GT (own address, label: Receiving Coin from Forkpool)
Credit: 1300.709806 GRA
Net amount: +1300.709806 GRA
Transaction ID: 81556b58b5b4445aefbcfbb58d55dbb35b6a018a2b22c24434517a8108ae0c23

Status: 0/unconfirmed
Date: 12/27/2013 14:05
From: unknown
To: 9DiuNh5P98ZU977uTwe3udYmrbJoVf87GT (own address, label: Receiving Coin from Forkpool)
Credit: 69.326034 GRA
Net amount: +69.326034 GRA
Transaction ID: 2ab0cf6901a60e95a740fe56e96be7c9f91f7aaf4c7bde3cf0fb1a6a2cf10db3

Status: 0/unconfirmed
Date: 12/27/2013 13:57
From: unknown
To: 9DiuNh5P98ZU977uTwe3udYmrbJoVf87GT (own address, label: Receiving Coin from Forkpool)
Credit: 259.181089 GRA
Net amount: +259.181089 GRA
Transaction ID: 909f89aca00a27cb285979068362927c11726d85688285a3450676e650b5806d

Edited: I am at GMT+8

I confirm this with my wallet aswell, much activity on internet and I/O Read & Write bytes.

after I close and reopen wallet there is less total activity and server mode seems to increase it a bit. so for now closing the wallet and reopen it seems to reduce it, for how long I don't know.

I have plenty of internet so its ok, but I think JL0z is right, its using too many internets for some people.

I wonder what it is doing that it needs to talk so much?

9AkuipbZfXaEjHmAaw3YA3ho9ZDWZC6TqG

Thank you!

bosian,

Hi.  I set my Wireshark to capture my network traffic for a period of 15 minutes.

74467 packets were captured and saved to a file size of 59,391KB.

When I filter these packets for those to/from tcp port 11054, I get 70342 packets and saved these to a file - size 58,659KB.  This is in .cap format so these are generally the raw capture data with just a small header.

Here in Australia, we are generally on metered internet connections, so running my Grain wallet for a day would use up possibly 5.6GB a day - and this is just having the wallet open on a computer.  I think this is something we need to look at, since this would use up 86% of my monthly allowance - that explains why things have been going so slowly in the past few days.

-John

[Edit] Just had a look at my firewall traffic graph - shows average outbound traffic of 56.5 KBps during the time everyone here was sleeping.  I took a snapshot but can't work out how to insert the jpg.

[Edit2] I closed my wallet, then waited for the firewall to refresh its traffic graphs.  Outbound traffic on my internet connection dropped from 64.397KBps to 2.960KBps.

bosian,

Hi - my concern is that this debug shows that the client maybe is causing a lot of network traffic, if it does this each time a new block is received.  My internet connection isn't great at best and lately with all my miners and my son's bitcoin miners - our internet is a bit slower than usual.  I will have a look and see what network traffic is being generated.

The following list of people, please send me your wallet address, or post in this thread, to claim your supporter's bounty!

Don't worry about debug.log, it's mostly useless. If it bothers you, you can stop qt-client, delete debug.log, and start qt-cleitn again. Everything will be fine.

tx42, you are on the supporter bounty list, please post you wallet address or PM me. Thanks.

yes that is correct number, it is in 47200s right now

What is your current block number? We should be at block 47268 now.

tx42, a fork is done because the PoW is jammed. This is a typical process to fix the issue. Other coins did the same thing for fixing similar problems.

                   ((  )
                     (( )
                      ( )
  ________      ∏
  [║_║_║_║----""--,.
  \,_( G. R. A. )---(0)
^-(O)O)O)O)---oo-\\

One thing, has anyone else noticed that the debug.log file is growing very large?  As of this morning it was over 110MB so I stopped my wallet, renamed it to start a new one, and restarted my wallet.

What it is showing are lots of these.

trying connection 184.78.158.84:11054 lastseen=9.0hrs
getblocks 37083 to 00000000000000000000 limit 500
  getblocks stopping at limit 37582 000000001f656535fd6f
received getdata (3 invsz)
getblocks 37083 to 00000000000000000000 limit 500
  getblocks stopping at limit 37582 000000001f656535fd6f
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e

etc, etc - it seems to be going through each peer and checking what block it is up to - and does this every time it receives a new block.  Currently it is 1MB and has been running only 40 minutes or so.

In grain we trust.

Right now it is 47186