GRAFT - Universal Payment Processing Network

[Andre100]

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

[1715130172]

1715130172

[1715130172]

1715130172

[1715130172]

1715130172

[bitcoin.dbi]

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

Same problem. Can be trade on stocks.exchange.

[phonglouis]

I wish this wallet would show transactions.....as for the CLI setup is there a simple .exe file that unloads all the components like ETN has?

[Abies]

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

This is not the first time. Maybe, they will fix the sell-buy lists later.

[Abies]

To graft-project,

How can you resolve this timestamps problem in your blockchain?

Please, respond my question!  

I see many blocks have wrong timestamps, now.

height   age [h:m:s]   size [kB]   tx hash   fees   outputs   in(nonrct)/out   ring size   tx size [kB]
66155   01:31:15   13.30   7b77e644ababd155b99eb21fd5a0a00a34500986e3e8f641b108308eb43778d7   N/A   1705.842   0(0)/1   N/A   0.09
51285843b9bc781d07eef4b451fc4d92132017c512cac5138285f42970314d32   0.096   ?   2(0)/2   5   13.21
66154   00:26:53   0.12   d42c41ccc78b608f5ef4b68182b463a2770fea6f0edfa086dbadfdf59bc6f2e7   N/A   1705.750   0(0)/1   N/A   0.12
66153   00:26:44   22.61   feb88598b9f4eb58e2a532a81ccf52df2877b06f194b928d67dee0e7c97d7701   N/A   1706.381   0(0)/1   N/A   0.12
e4bebd2932ffceaf16fd472ed198ab4aeaa9e95ccd359f5ff4638cef44a100a9   0.628   ?   24(0)/2   5   22.49
66152   01:32:31   56.40   c660ee708e85c3e4394ffe57f310abd0c36ae37d88dd432dfc1fec9114e1d7ec   N/A   1706.145   0(0)/1   N/A   0.09

[Andre100]

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

Same problem. Can be trade on stocks.exchange.

stocks.exchange - trade some on this sh*t... to slow and laaaaaag

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

This is not the first time. Maybe, they will fix the sell-buy lists later.

not trade on tradeogre from today, and how long thay ofline? hrs or days ? ))

[NChink]

To graft-project,

How can you resolve this timestamps problem in your blockchain?

If you ignore this problem, there is no future for Graft.

Please, respond my question!  

I see many blocks have wrong timestamps, now.

height   age [h:m:s]   size [kB]   tx hash   fees   outputs   in(nonrct)/out   ring size   tx size [kB]
66155   01:31:15   13.30   7b77e644ababd155b99eb21fd5a0a00a34500986e3e8f641b108308eb43778d7   N/A   1705.842   0(0)/1   N/A   0.09
51285843b9bc781d07eef4b451fc4d92132017c512cac5138285f42970314d32   0.096   ?   2(0)/2   5   13.21
66154   00:26:53   0.12   d42c41ccc78b608f5ef4b68182b463a2770fea6f0edfa086dbadfdf59bc6f2e7   N/A   1705.750   0(0)/1   N/A   0.12
66153   00:26:44   22.61   feb88598b9f4eb58e2a532a81ccf52df2877b06f194b928d67dee0e7c97d7701   N/A   1706.381   0(0)/1   N/A   0.12
e4bebd2932ffceaf16fd472ed198ab4aeaa9e95ccd359f5ff4638cef44a100a9   0.628   ?   24(0)/2   5   22.49
66152   01:32:31   56.40   c660ee708e85c3e4394ffe57f310abd0c36ae37d88dd432dfc1fec9114e1d7ec   N/A   1706.145   0(0)/1   N/A   0.09

So, there is indeed an issue here - I looked at the timestamps and as you can see in block 66109, it does NOT fit into the median calc! Graft devs - how do you explain that??

Code:

https://blockexplorer.graft.network/block/66110 1524216658 (2018-04-20 05:30AM)
https://blockexplorer.graft.network/block/66109 1524223476 (2018-04-20 07:24AM)
https://blockexplorer.graft.network/block/66108 1524216287 (2018-04-20 05:24AM)
https://blockexplorer.graft.network/block/66107 1524216172 (2018-04-20 05:22AM)
https://blockexplorer.graft.network/block/66106 1524216076 (2018-04-20 05:21AM)
https://blockexplorer.graft.network/block/66105 1524215997 (2018-04-20 05:19AM)
https://blockexplorer.graft.network/block/66104 1524215606 (2018-04-20 05:13AM)
https://blockexplorer.graft.network/block/66103 1524215231 (2018-04-20 05:07AM)
https://blockexplorer.graft.network/block/66102 1524215127 (2018-04-20 05:05AM)
https://blockexplorer.graft.network/block/66101 1524214997 (2018-04-20 05:03AM)
https://blockexplorer.graft.network/block/66100 1524214770 (2018-04-20 04:59AM)

[Abies]

Ok.

Nobody answered my question.

so, I researched the block timestamps in Bitcoinwiki.

They say it may not exactly accurate.(Block times are accurate only to within an hour or two)

https://en.bitcoin.it/wiki/Block_timestamp

Timestamp order is not important.

My problem solved.

[Abies]

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

Same problem. Can be trade on stocks.exchange.

stocks.exchange - trade some on this sh*t... to slow and laaaaaag

https://tradeogre.com/exchange/BTC-GRFT
no trade activity only at me?

This is not the first time. Maybe, they will fix the sell-buy lists later.

not trade on tradeogre from today, and how long thay ofline? hrs or days ? ))

Last time, it took 5-6 hours to fix the problem in my memory.

[NChink]

Ok.

Nobody answered my question.

so, I researched the block timestamps in Bitcoinwiki.

They say it may not exactly accurate.(Block times are accurate only to within an hour or two)

https://en.bitcoin.it/wiki/Block_timestamp

Timestamp order is not important.

My problem solved.

It's what I posted in my first response to you (clock drift) - it is working as intended. However, I don't recall seeing a 2 hour difference between specific blocks within the last 11 entries which is why I asked as well.

[Abies]

Ok.

Nobody answered my question.

so, I researched the block timestamps in Bitcoinwiki.

They say it may not exactly accurate.(Block times are accurate only to within an hour or two)

https://en.bitcoin.it/wiki/Block_timestamp

Timestamp order is not important.

My problem solved.

It's what I posted in my first response to you (clock drift) - it is working as intended. However, I don't recall seeing a 2 hour difference between specific blocks within the last 11 entries which is why I asked as well.

New diff algorithm gives different timestamps(not real time).

I noticed the block timestamp was modified when diff went up.

[maxvan1]

I posted(and quickly removed) the issue with timestamps and orphaned blocks to reddit yesteday.

Easyhash.io orphaned 20+ blocks in a row--it definitely seems like there is some sort of issue.

[Abies]

Ok.

Nobody answered my question.

so, I researched the block timestamps in Bitcoinwiki.

They say it may not exactly accurate.(Block times are accurate only to within an hour or two)

https://en.bitcoin.it/wiki/Block_timestamp

Timestamp order is not important.

My problem solved.

It's what I posted in my first response to you (clock drift) - it is working as intended. However, I don't recall seeing a 2 hour difference between specific blocks within the last 11 entries which is why I asked as well.

https://www.reddit.com/r/Graft/comments/8dscv1/timestamps_for_recent_blocks_are_counting_down_we/
In the Reddit, imperdin said "Attackers are using a nefarious pool that injects malicious time-stamps into blocks to forcefully reduce the difficulty to mine blocks at a faster rate at the expense of others."

I think this is right because I could not find which pool found from block 66311 through block 66369 in the graft pool list.(http://grftplst.zarub.org/)

Therefore, In the spacepools, a Nicehash buyer spent a lot of money for one block.(effort 9431% for one block 66375)
66375   34 / 60    933201974   16d2307190616728ec8fec0e8472dd04d91c0cb79fefc6392ee8181a00b4bdf0   TBA   4/20/2018, 9:17:14 PM   9431%

https://graft.spacepools.org/#pool_blocks

[wudafuxup]

Ok.

Nobody answered my question.

so, I researched the block timestamps in Bitcoinwiki.

They say it may not exactly accurate.(Block times are accurate only to within an hour or two)

https://en.bitcoin.it/wiki/Block_timestamp

Timestamp order is not important.

My problem solved.

It's what I posted in my first response to you (clock drift) - it is working as intended. However, I don't recall seeing a 2 hour difference between specific blocks within the last 11 entries which is why I asked as well.

https://www.reddit.com/r/Graft/comments/8dscv1/timestamps_for_recent_blocks_are_counting_down_we/
In the Reddit, imperdin said "Attackers are using a nefarious pool that injects malicious time-stamps into blocks to forcefully reduce the difficulty to mine blocks at a faster rate at the expense of others."

I think this is right because I could not find which pool found from block 66311 through block 66369 in the graft pool list.(http://grftplst.zarub.org/)

Therefore, In the spacepools, a Nicehash buyer spent a lot of money for one block.(effort 9431% for one block 66375)
66375   34 / 60    933201974   16d2307190616728ec8fec0e8472dd04d91c0cb79fefc6392ee8181a00b4bdf0   TBA   4/20/2018, 9:17:14 PM   9431%

https://graft.spacepools.org/#pool_blocks

Yea there's definitely an asshole attacking the network currently. There was a point where I was put in 65Kh/s for about 3 hours just to test it. Didn't receive a single coin. Rejected blocks from pool 

[Andre100]

Last time, it took 5-6 hours to fix the problem in my memory.

yes, already fix Thx, but for now not 20\20 confirm.. now 40\40 need

[PainKiller1986]

Today my wallet can't open, just show a blank window and close

[serhanni]

I have just saw a note on cryptunit.com.

"april 21 Looks like the something is happening on graft network. We've reviewed some Graft pools and they all have a problem. Graft is temporarily removed from Cryptunit."
There is no information on the site about the issue.

[Abies]

I have just saw a note on cryptunit.com.

"april 21 Looks like the something is happening on graft network. We've reviewed some Graft pools and they all have a problem. Graft is temporarily removed from Cryptunit."
There is no information on the site about the issue.

Yes, timestamp attack is happening now.

https://www.reddit.com/r/Graft/comments/8dveem/graftteam_please_solve_the_timestamp_attack/

[wudafuxup]

It seems like the timestamp attacks have been addressed. The fork will happen at block 68000. I like the quick response time! https://www.graft.network/2018/04/22/graft-major-network-update-1-2-1-at-block-68000/

[graft-project]

GRAFT MAJOR NETWORK UPDATE 1.2.1 AT BLOCK 68000

https://www.graft.network/2018/04/22/graft-major-network-update-1-2-1-at-block-68000/


We just released a major network update 1.2.1. This update is intended to mitigate recent attacks on GRAFT blockchain and improve the stability of the block intervals. There are two major changes included in this release: timestamp manipulation prevention and improved difficulty adjustment algorithm. The major network update will be triggered at block 68000.
The block timestamp manipulation allows a miner with significant hashrate power to generate an alternative chain of several blocks and add it to the main chain. The corresponding code fix will disable this possibility.

The original LWMA-based difficulty adjustment algorithm used the same adjustment rate to increase and decrease difficulty. As the result, it was taking significant time to restore after a peak, leaving users suffering from a higher difficulty. In our novel approach, we introduce an adaptive adjustment rate, making return to a normal difficulty level faster. The mechanism detects a failing edge of the difficulty curve and change the rate accordingly, using the following formula:

The major network update is scheduled for block height 68000. Each GRAFT network node must be updated to the new software version before that block, otherwise, the node that wasn’t updated is going to be on the wrong version of the blockchain. Major network update means that if you are running the GRAFT network node (graftnoded daemon), you must upgrade it to the current software release as soon as possible. If you do not install the updated node before the block 68000, your node will be blocked by other nodes. Note that the users of GRAFT mobile and desktop wallets (GUI wallets) are not affected by the upcoming network update and don’t need to do anything – as long as they are still connected to the default proxy supernodes (if you are connected to your own supernode, however, do not forget to upgrade the underlying network node).

The source code of the version 1.2.1 is now released and available for download from master. In order to check whether you are running the right version of GRAFT network node, launch graftnoded daemon in terminal window (in interactive mode) and type help command. If you are running the right version you should see Graft ‘Beta Lyrae’ (v1.2.1-release) in the first line of the help result.