Topic: [ANN][GRA] Graincoin - PoW/PoS coin | Fast, secure | Version 1.6.2 Release - page 10. (Read 58995 times)

Whoever running node at 24.95.55.64, would you mind to resync please. You are on fork 100k blocks behind.

Thank you.

Ah, I see. First, no legitimate node would accept the block that has time in advance of more that max clock drift. The max clock drift is currently 2 hours. It came from original bitcoin client and for bitcoin network it is not a problem at all. As I mentioned, I am going to change that parameter, but it requires a hard fork, so I would like to collect all such hard changes together. Also no legitimate node would accept the block that is in the past relative to the GetMedianTimePast().
You could of course (and it seems you did ) make a tweaked wallet that would persistently submit the blocks with time 2 hours in advance. This would influence the difficulty of course, but will not stop the network from generating new PoS blocks as I assume that even before your dump you were not in possession of 51% of all coins. So even if you managed to bring the network's PoW difficulty to some high value that 'stopped' the current network's hashing nodes from producing PoW blocks and you started to create your own fork to override main chain you most likely would fail as the cumulative trust score of your fork would be less than the network's one: the block trust score is a function of the block's difficulty and a history of last 12 blocks. So, to achieve the better result you should have more resources (both the hashing power and the supply) than the rest of the network.

Taking to account the currently low network hashing power it is of course possible to make successful doublespend, but as I already said I am not going to pump the situation with the thin air. As the coin presently has very low value I do not see any reason to care much about this: when and if the graincoin get well valued then miners come.

With "works" in mean that the blockchain accepts blocks with future timestamps.

Missed this initially. It's their business and their risks. If they see it affordable then let it be.

There is no need to send your wallet.

Works what? No PoW blocks for 2 hours? Or something else? If the former one, I already explained you: there were no miners active during that time. According to my observations we have only two or three people PoW mining it. And they do not mine it 24h a day. I have only 1 CPU miner running to collect the blocks when there is no power at all - just to give an opportunity to other people to mine.

I can send you my wallet with all Tx, if it helps you to analyze with issue.

I just wonder, if it works for 2h, would it also work for a day or a week or a month?

The main problem behind Grain is that there is no hash power behind it.

I understand your fears that grown on BCX related news.
Might be it worth to discuss such doubts with the community, dev,  other coins devs in the first turn than to just dump all that you have? Did you do any thorough study how that could be applied to graincoin particularly.

The case that you mentioned, when the PoS diff was stuck at 1.5 for several, was just due to no PoW miners with a notable hash power were active at the time. It took me a few minutes to solve that block with 3.6Mh rig to push it through.

Although the current set of the timing and other parameters that control the behavior of the blockchain is really not ideal and I am going to change some of them (the max clock drift among them) to improve the network security, ATM I have more important things to work on. Without these things implemented any other so called 'improvements' are just a dust. They will not make graincoin any different so it could get what it should deserve.

Edit:
the lack of my frequent postings here is not due to I am absent: you could easily see that I am online every day, so I am not gone. I just think that meaningless posts like "to da moon" does not create any value of the coin.

After reading stuff about BCX, I was curious how will the Grain blockchain deal with blocks that have a faked timestamp, so I have run a test.
I have changed the system clock time on my miner 2 hours into the future and started mining.

The network has accepted my blocks and I have also solved PoS blocks with a faked timestamp. I have tested this a second time without a PoS block being solved and the network has rejected my PoW blocks.
Normally I get 66-75% stales/invalids, but with the faked timestamp I have got only 40-50%. The PoW difficulty was also lowering!

After restoring the normal time I could still mine with a low difficulty for a short time, but then the difficutly has raised without PoW blocks being solved.
The difficulty was so high, that I could not solve any (or almost none, I cant remember) PoW blocks until 2 hours since my last block with a fake timestamp have passed.
My client also didnt solve any PoS blocks.

I cant tell how exacly the network did behave during this 2 hours, because I had only one client running, but I have noticed a very big interval between the blocks.
I can remember that the highest interval between block (according to my client) was over 10 minutes (maybe even 20).

After the 2 hours, my client have solved a shitload of PoS blocks instantly and the difficulty was back to normal.

I could made a copy of the chain and do the above and mine faster than the network.
I could also play with the timestamps on my private copy of the chain and I would definitely solve the blocks faster than PoW and PoS of the network combined.


It is also a bad idea of swisscex to accept Grain deposits after only 6 confirmations.

Really? Could you elaborate, please, the complete scenario.

This is why I have dumped everything.
I was just testing some stuff, but you could time warp the shit out off this chain if you wanted (I didnt, I have only mined 2h in the future without forking the chain).
This 2h time change has fucked up the diffculty for 2 hours. You could time warp and double spend as much as you wanted (which I didnt).

PoW should be removed, its only a weak point with this low block rewards.

I have only mined with ~250 Khash/s.


This is probably someone else doing the same shit.

Great job.
Thanks.

Thank you. Apparently, there are still some issues with ABE code - I am fixing it now.

Nice work. 

Hi,

It seems my attempt to negotiate the block explorer outsourcing has failed.
First I doubled the requested 0.05 BTC lifetime fee as I was aware that ABE scripts are incorrectly calculating coindays destroyed, fees, etc. for blocks containing superblock reward transactions and I wanted this to be fixed by the explorer op. Then I doubled this amount again as he was impressed by the blockchain size... to no avail. So I did what I said him: I rented a VPS for that amount, fixed and deployed the blockchain explorer myself. Here you are:

http://explorer.graincoin.net/

It is an official one. The OP is updated.

"netmhashps" : 127.60631041

Hold on ...  It's still breathing and has a weak pulse ...

I am all out.

"netmhashps" : 77.80505571

nice

Edit:
now its all gone 

A bit of movement on swisscex.

Thanks.
Getting 5 active connections right now.

I'm showing 12 active connections.  just in-case anyone needs it ... peer info below.



[
{
"addr" : "54.196.227.51:11054",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124835,
"conntime" : 1409594215,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1036273,
"banscore" : 0
},
{
"addr" : "192.99.15.174:11054",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124841,
"conntime" : 1409594232,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1036273,
"banscore" : 0
},
{
"addr" : "84.51.215.123:50770",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124834,
"conntime" : 1409594328,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1036279,
"banscore" : 0
},
{
"addr" : "99.63.193.158:57059",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124842,
"conntime" : 1409594489,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1036286,
"banscore" : 0
},
{
"addr" : "213.21.33.12:41654",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124834,
"conntime" : 1409594899,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1036310,
"banscore" : 0
},
{
"addr" : "24.107.155.164:51761",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124841,
"conntime" : 1409885019,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 95010,
"banscore" : 0
},
{
"addr" : "95.27.79.233:11054",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124836,
"conntime" : 1409949702,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1051433,
"banscore" : 0
},
{
"addr" : "87.98.190.199:54194",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124834,
"conntime" : 1410057246,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1055431,
"banscore" : 0
},
{
"addr" : "176.195.213.159:64968",
"services" : "00000001",
"lastsend" : 1410124842,
"lastrecv" : 1410124841,
"conntime" : 1410075427,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1056501,
"banscore" : 0
},
{
"addr" : "92.31.145.180:60604",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124816,
"conntime" : 1410081590,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 130464,
"banscore" : 0
},
{
"addr" : "78.53.55.135:63715",
"services" : "00000001",
"lastsend" : 1410124840,
"lastrecv" : 1410124841,
"conntime" : 1410118932,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1058391,
"banscore" : 0
},
{
"addr" : "192.227.144.2:52449",
"services" : "00000001",
"lastsend" : 1410124841,
"lastrecv" : 1410124830,
"conntime" : 1410121105,
"version" : 60007,
"subver" : "/Grain:1.6.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 750169,
"banscore" : 0
}
]

Nice to see you, Nullu

btw. could you please respond to the PM I sent you while ago , thank you