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

What I did now was to rename my current grain folder to grain2, restart wallet and then close. Copy wallet.dat and grain.conf to the new grain folder and start wallet again and let it sync.
It seems now it working again without freezing...

Graincoin needs to be on http://www.worldcoinindex.com/ and http://www.coinwarz.com/

How does Grain's code look when you compare it to LKY, BUK, STR, MEM, COL, MPL ect ... ??

Orphans.. glitchy PoS/PoW .. .how many other similarities will be found ?

@mkimid

OK. You found a block. It got to the node that runs block explorer so you see the same picture there. At the same time (a few seconds or milliseconds later) block explorer receives a notification that some third node, to which you have no direct connection, found a block with the same height. The explorer's wallet retrieve that block but nothing changes as both blocks are of the same height. The explorer's wallet informs in turn that third node that it has alternate block. While all these things happened that third node found a new block based on it's previous block as it is continuously mining like you. It also send a notification to the block explorer's wallet. Then the longest chain wins. Explorer's wallet switches to it and informs you about the changes. Your wallet has nothing else than to drop it's own chain.

Yes, I want to think like that, how you can explian ?
[time stamp is an example; computer time / time in block explorer]

FIRST CASE :

   1. 00:00:40 // 00:00:30 #10000 PoW has listed, and it has been listed on Block Explorer (outside of network)
   2. 00:00:45 // 00:00:35 #10001 and the other blocks are connected on the block (I got 1 confirm) and shows on block explorer
   3. 00:00:55 // 00:00:20 #10000 has replaced with PoS in block explorer
   * PoS block has been found on 00:00:20, so, PoW blocks (00:00:30/00:00:35) are orphans : techinically no problem, and it is right
   
   You have mentioned about "Propagation", How long it will takes to progaration ? How will deicde what it the first [timestamp on packet] ?
   Most of time, within 1-2 seconds it has been updated as Orphans, but, some time, How can it makes 5-10 seconds delay ?
   
   Techinical issue
       this orphan block are connected in my local block chain because of it has confirmed [It means it has propagated to the other server also, NOT just in my local wallet, it is what difference from the general orphan]
       after while, QT detect, it is orphan block and fix the block chain again

   Yes, It can be happen, but, JUST VERY RARELY, NOT FREQUENTLY

   AND, it is in trouble of QT or ?


SECOND CASE :

    1. 00:00:30 // 00:00:05  #10000 PoW has found and listed in Block Explorer
    2. 00:00:35 // 00:00:04  #10000 PoW has replaced with PoS with 00:00:04 timestap
   
    It is happen on two computer under same network,
    (A) one is mining with 2.2MHs with clean/no-PoS QT, (B) the other is just running QT with PoS mining
    (A) cgminer shows a acceptance, and records are put into QT (PoW),
    After 5 seconds (At least)
    (B) QT shows a acceptance, and reocrds are put in to QT (PoS)
   
     I have running Safari BlockExplorer on iPad,
     When, I got notification from (A), I am keep refresh and chekcing
    - (A) records has listed on block explorer {AT Least ONE the other computer, Not Just in Local]
    after while
    - (A) records is gone, and (B) record is there

    Actually, it is too hard to understand with "Propagation",

    Just say, QT has reports PoS block(B), and it is going to every where EXCEPT computer (A) which in the same network, EXCEPT block explorer's comptuer
    and, Computer (A) reports PoW after 5 minuties, and ONLY (A) computer and Block Explorer's Computer are got this notice,
    and, Unknown (C) computer find a new PoW after 5 seconds and noticed to (A) computer, and Block Explorer's computer
    But, (A)/(B)/(C) QT aware the blocks are orphan, and they fix the block chain

    1. How (A)/(B)/(C) can decide ? base on the time stamps on the packet header ?
    2. Technically, it can be happen, I am not saying it is impossibe things,
        But, I want to ask, How frequently it can be happen ?

---------
@Bee7

I am not saying, this coin is making an impossible situation because of everything is possible technically,

Single orphan, it can be happen, It can be happen in low Diff coins, what is the possiblity when consider the network rate and diff of this coin ?
* 30~45% now

Multiple chained orphan with the other server, it can be happen also, what is the possibity when consider the network rate and diff of ths coin ?
* hard to say, but, I can find couple of case within a hour
* just refresh block explor, can find easily,
* actually, when I got notice from QT, immediately, I am check block explorer and keep refresh to check what it will happen.

This assumption is wrong. The block that propagated through the network faster wins. It even may have timestamp in the header 'younger' than yours (actually the header timestamp is not considered when wallet takes the decision on what is the best block), but if the miner that find that competing block is connected better than you, if his blocks propagated faster than yours then your blocks will be orphaned. In the PoW/PoS hybrid this decision is also affected by the actual PoW/PoS ratio in the recent past.

Most of miner got 20~45% orphans,

Too many orphan makes the miner feel so uncomfortable even they got the reasonable number of blocks base on your target,
It can be allowed rarely, not much like the graincoin.
Even it is true or not, miner feel something steal their efforts,
Actually, that is true,
Orphans means they use their own hashing power for mining a useless block,
Technically, some kind of orphans can be happen with very small block time mostly within a second (so many finder within very short time),
     Typical delay of cgminer from GPU      15~25ms
     Network delay                                   10~250ms (mostly, < 100ms)
     Windows task scheduling delay           15~16ms
     QT notification and broadcast delay     < 5ms (estimated)
     **** even consider the overall delay, it is less than 0.5seconds
     **** ok, some body has experienced some abnormal delay, but, it can not be an answer, not only me has this issues,

but, in Graincoin, it is happen even after 5~10 seconds,
It makes a lot of lost hashing power,
And, IT makes miner's are leaving this mining of this coin,

I feel something wrong
     (1) delay of receving boardcast from the other network ?
     (2) wrong timestamping on PoS (using start of stake, instead of solved time), and it is applied on block chain lately
          --- Personally, I suspect it
          --- it can makes everybody waiting till he solve,

I want to say, many other pow/pos coins are having similar problem, BUT, NOT ALL
It means, It is a prblem and many PoS/PoW coins have,

Before you just counting the generated blocks, I wish you put more time to remove this problem,


(1) why PoS blocks are noticed and chained on the block chain with delay ?
(2) what is the most delay time ?

One of funny thing, I have testing with two computer

(1) A computer has some blocks and it is under PoS mining
(2) B computer has clean wallet, and just PoW ming
(3) I got a notification from B computer, it is found a block
(4) After couple of seconds (I am sure, longer than 5 seconds), I got a notification from A computer, it is found a PoS block
(5) Just guess
(6) Yes, on block chain has listed A computer's PoW block
(7) and, the block has replaced with B computer's PoS block

Two computer have same local time setup
Two computer are runing under same network
Two computers are running Grain-QT with Realtime mode and no other softwares are runing which can took network or others

Base on this test,
    (1) This coin is ignoring the basic rule of FIRST FINDER OF BLOCK RULE
    -OR-
    (2) my computer is under so mysterious states

I wish The other miner verify it,

I have the same Problem some days before, I have to take a scurecopy of my wallet.dat and all Blockchaindatas form Wallet 1.3 and than it works. I am using Linux so I copied the comlete hidden directory should be the same like user/Roaming/.... Im not sure if this will help on windows.

It will be nice, please go on

Had no problems with my wallet at any point. When I run the wallet it has some effect on gaming but once it has synced it runs smoothly. Using windows 8.1.

I think I will try to make a FAQ that could be added to OP as the same problems keep popping up on every 2nd page.

Changing priority does nothing.
It's really strange because before the cpu load was high only when started and then was minimal while stayed open. Now it's constantly high and "not responding" most of the time...

Problem with cron at this nignt

Problem with cron at this nignt
I think its deppend from orphans blocks.
I try to fix this problem.

Problem with same height of block. Pool found two block with same height. One good and one orphan. After cron stoped.


PS Dont worry, all statistic keeping and all payouts will be sent

Unfortunately I can't even test the issue as I have no Windows. However, Bosian said that he did not note anything similar. Also, there is a post regarding freezes:

Thank you very much!

I've noted since a few days ago that my wallet freezes constantly and uses more cpu than before...

I'm not the only one who was overpaid. lol

25k GRA SENT !

Status: 1/unconfirmed, broadcast through 2 nodes
Date: 30/01/2014 03:01
To: bee7 9D2yGsiqBzq2qmX58pCi9jgNPLubNwGGfV
Debit: -25000.00 GRA
Transaction fee: -0.08 GRA
Net amount: -25000.08 GRA
Transaction ID: 27d2834ea62c6c449565e5c7d88d75f4273eff588937451967153787aa9f0067

If you find this transfer in the posts 2330 and 2331 then please send it back to the address 9D2yGsiqBzq2qmX58pCi9jgNPLubNwGGfV (sure, you may deduct the tx fee).

Thanks

I just recieved a 2nd 25k GRA bonus even though I have not solo'd Grain since the first 25k payment. If this was a mistake, you are welcome to have it back.

I'm also seeing half my PoS blocks orphan after a few confirms.

At low diff it seems that it may have a lot orphans, but the block time is ok. When diff goes up the orphan seems goes down. Looks like the diff adjusting scheme is still not perfect. This situations also seen in many other pow/pos coins too.

The effect you did may be achieved by simply start the wallet with option '-rescan'. The final effect is the same - the blockchain is searched for all addresses in a wallet and the balance is recalculated. When you import a key then it is also scanned to find all transactions with the address being imported.

Sometimes when wallet was not shut down properly due to any reasons the inconsistency between the actual balance and the balance shown may happen.

Edit:

You can't lose any crypto coins (built with bitcoin's technology) unless you lost your keys as all transactions are kept in the blockchain. So backup your wallet.dat regularly. It is a must thing to do when you update the wallet app.