[ANN] [QRK] Quark | POW/POS | 0.10.8.0 - New Self Moderated Thread

[mix29k]

since devs supposed to clean the code - my 5 cents,
check if you can resync 0.10.7 from scratch using full-length bootstrap.dat,
i can't, it tends to break off and revert to network too soon

[ghzsymc2]

rpc-getblocktemplate calls CreateNewBlock()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/rpcmining.cpp#L517)

in CreateNewBlock() after MN-startblock it calls FillBlockPayee()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/miner.cpp#L360)

where FillTreasuryPayee() is called
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/masternode-payments.cpp#L304)

Two possibilities

Some people are using the new code to generate a lot of rewards for the foundation
(to create panic)

Unknown bugs have emerged as a result of mining along with the old chain during the upgrade

---------------------

We are working on a mandatory upgrade

It's going to start over at 70,700,00

--------------------
This address belongs to the foundation

We have decided to scrap the forks that currently allow the foundation to acquire large Numbers of COINS

A new version will be released soon

So far these extra COINS are in my hand

Please be assured that

We will soon abandon the chain

All exchanges have been notified to close deposits and withdrawals

----------------------
One thing is simple

If someone as smart as me were to steal a coin

I don't need to let everyone know at such an important moment

right ？

This is clearly a setup

But it doesn't work for me

I will organize to finish the upgrade work as soon as possible

No one can stop quark's advance

----------------------
Think back to when we released the upgrade

There were times when the network was unstable



The attacks have escalated recently

Even 10.6.3 of the mine pool hired force to mining
-
Our community consensus is what matters

As long as we stick together



No one can defeat the power of people

[Tpf0505]

rpc-getblocktemplate calls CreateNewBlock()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/rpcmining.cpp#L517)

in CreateNewBlock() after MN-startblock it calls FillBlockPayee()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/miner.cpp#L360)

where FillTreasuryPayee() is called
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/masternode-payments.cpp#L304)

Two possibilities

Some people are using the new code to generate a lot of rewards for the foundation
(to create panic)

Unknown bugs have emerged as a result of mining along with the old chain during the upgrade

it's a bug - happened during adaption of yiimp-base pool to new coinbase-layout.

getblocktemplate reports wrong scaled values and wallet doesn't check max value for treasury

[PromethiumX]

rpc-getblocktemplate calls CreateNewBlock()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/rpcmining.cpp#L517)

in CreateNewBlock() after MN-startblock it calls FillBlockPayee()
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/miner.cpp#L360)

where FillTreasuryPayee() is called
(https://github.com/quark-project/quark/blob/f813e83ee229d9dce9f798051f96ca73f36d91f5/src/masternode-payments.cpp#L304)

Two possibilities

Some people are using the new code to generate a lot of rewards for the foundation
(to create panic)

Unknown bugs have emerged as a result of mining along with the old chain during the upgrade

it's a bug - happened during adaption of yiimp-base pool to new coinbase-layout.

getblocktemplate reports wrong scaled values and wallet doesn't check max value for treasury

Yeah! can we get a max value check? Better an error than a 27million coin overrun.
Any Idea where it's getting that magical number? (106,394.92616)

8 hours in seconds is 28800    times the MN reward 3.69416 is very close to the magical number 106391.808 Perhaps some rounding is involved.

    QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv
    106,391.232 QRK
    QirdV1H3Tikg12QefVkoFKrwkfHxT8EXia
    3.69416 QRK

[yiminh]

the developer of wallet 10.7.0 made a honest error and rewarded the treasury 1000 times the reward it should have get, everyone back to the old version of 10.6.3, we must abandon the 10.7.0 fork and upgrade using the correct wallet, maybe 10.8.0

[suoluosi]

Obviously, version 10.7.0 contains a plot to get a lot of rewards in the code. As an investor of QRK, to protect the credit of QRK COINS, it is safer to go back to the previous version of 10.6.3 and maintain the old blockchain!

[mix29k]

yeah, funny that 25% treasury "tax", coin will end up like ltcr, fame and all crap ..
i didn't realize how far down things gone for quarrrk until decided to sync up a good ole wallet lol

[suoluosi]

Just an hour ago, at the height of 7072682 position, block the browser https://chainz.cryptoid.info/qrk/# began to dig again.The 27 million QRK COINS that were created out of thin air yesterday belong to some thief!------------ -- can see very long time since, the upgrade of 10.7.0, itself is a scam!

[ghzsymc2]

Dear supporter
Quark has come to the critical moment of life and death
There is no point in going back to the old version
We spent six years verifying that this type of allocation scheme is not sustainable

All exchanges have temporarily closed deposits and withdrawals
The team has been very motivated to complete the solution as quickly as possible
Please do not make any transactions in the near future
Otherwise it is easy to suffer losses

We won't spend much time
It won't take months
Developers need to take a moment to analyze the cause of our problems
Then we will release a new version in a very short time （Maybe in a few days，I thought we could test it half a day ago, but the developer said it would take some time to review the code again）

But trust the team
Of course, if the team still can't solve this problem
So we have reason to go back to version 10.6.
But now, please give the team some time.

[titinet]

Dear supporter
Quark has come to the critical moment of life and death
There is no point in going back to the old version
We spent six years verifying that this type of allocation scheme is not sustainable

All exchanges have temporarily closed deposits and withdrawals
The team has been very motivated to complete the solution as quickly as possible
Please do not make any transactions in the near future
Otherwise it is easy to suffer losses

We won't spend much time
It won't take months
Developers need to take a moment to analyze the cause of our problems
Then we will release a new version in a very short time （Maybe in a few days，I thought we could test it half a day ago, but the developer said it would take some time to review the code again）

But trust the team
Of course, if the team still can't solve this problem
So we have reason to go back to version 10.6.
But now, please give the team some time.

Hi, I have installed quark 10.6 ( this version Revert "0.10.6.5" : https://github.com/quark-project/quark ) on my pool and I work with two miners with this version since 1 day.
My blocks are assured or not ?
block 7076959 actually
Address of my pool : QQsntQ4YaF...............

[ghzsymc2]

Dear supporter
Quark has come to the critical moment of life and death
There is no point in going back to the old version
We spent six years verifying that this type of allocation scheme is not sustainable

All exchanges have temporarily closed deposits and withdrawals
The team has been very motivated to complete the solution as quickly as possible
Please do not make any transactions in the near future
Otherwise it is easy to suffer losses

We won't spend much time
It won't take months
Developers need to take a moment to analyze the cause of our problems
Then we will release a new version in a very short time （Maybe in a few days，I thought we could test it half a day ago, but the developer said it would take some time to review the code again）

But trust the team
Of course, if the team still can't solve this problem
So we have reason to go back to version 10.6.
But now, please give the team some time.

Hi, I have installed quark 10.6 ( this version Revert "0.10.6.5" : https://github.com/quark-project/quark ) on my pool and I work with two miners with this version since 1 day.
My blocks are assured or not ?
block 7076959 actually
Address of my pool : QQsntQ4YaF...............

Suggestion for temporary suspension of mining
If we re-establish a healthy chain, it will start at 7070,000

[titinet]

ok thanks

[suoluosi]

The failure of the upgrade to 0.10.7 has caused a significant negative impact, and the entire currency circle is suspecting that the whole version is a conspiracy. If continue to go along the direction of the upgrade, it will inevitably make QRK currency lose the trust of investors.-------- -- so, suggest, in the shortest time, let QRK back to the previous 0.6.5 old chain, so, to maintain the popularity of the whole QRK community, -------- ---- otherwise, people will think that QRK currency, has become no difference with other new central currency pyramid selling money, this currency will not be trusted from now on!

[titinet]

The failure of the upgrade to 0.10.7 has caused a significant negative impact, and the entire currency circle is suspecting that the whole version is a conspiracy. If continue to go along the direction of the upgrade, it will inevitably make QRK currency lose the trust of investors.-------- -- so, suggest, in the shortest time, let QRK back to the previous 0.6.5 old chain, so, to maintain the popularity of the whole QRK community, -------- ---- otherwise, people will think that QRK currency, has become no difference with other new central currency pyramid selling money, this currency will not be trusted from now on!

i agree with this opinion. Why always change if that work.

[JFoxOne]

Explorer is down for about 5 days now - https://chainz.cryptoid.info/qrk/

[suoluosi]

Call "Quarkcoin max-guevare Pondi Cryptohunter", how many maintainers of the original QRK coin?

We sincerely hope that you can explain this wallet upgrade of 10.7.0. We suspect that there may be fraud of 27 million quarks in this upgrade.

The plan of upgrading to MN this time is different from that of upgrading to "POW+POS" in 2017. This time, 27 million QRK is remitted to the foundation account, which is a serious problem. According to theory, the organizer should deal with this problem in the shortest possible time.

I hope you several QRK leaders and maintainers can reply to the investors of this community as soon as possible, thank you!

[quarkcoin]

The 0.10.7.0 upgrade has been reverted.

Everybody is recommended to use the old 0.10.6.3 versions.

This might require re-syncing or re-indexing your wallet.

https://github.com/quark-project/quark/releases/tag/v0.10.6.3

[mix29k]

The 0.10.7.0 upgrade has been reverted.

Everybody is recommended to use the old 0.10.6.3 versions.

This might require re-syncing or re-indexing your wallet.

https://github.com/quark-project/quark/releases/tag/v0.10.6.3

checkpoint ? how do i know the correct chain while explorer is down ?

[PromethiumX]

The 0.10.7.0 upgrade has been reverted.

Everybody is recommended to use the old 0.10.6.3 versions.

This might require re-syncing or re-indexing your wallet.

https://github.com/quark-project/quark/releases/tag/v0.10.6.3

Just re-indexing  with 10.6.3 will not ensure you are on the correct chain. in your conf file set listen=0, remove all your addnode entries, then add connect entries to all peers that have a blockheight above 7091226
 ie:
connect=89.212.249.7:11973
connect=70.81.219.188:11973
connect=2a01:4f8:13b:7a3::901:11973
connect=123.243.123.106:11973
connect=101.187.42.235:11973
connect=58.96.77.27:11973

Once you have synced to 7091226 or above you can restart with listen=1 and replace addnode entries

[yiminh]

you need to create quarkcoin.conf file in you Quark folder(contain quark-qt.exe),

than copy and paste

listen=0
connect=89.212.249.7:11973
connect=70.81.219.188:11973
connect=2a01:4f8:13b:7a3::901:11973
connect=123.243.123.106:11973
connect=101.187.42.235:11973
connect=58.96.77.27:11973


into the file and save