Topic: [ANN] [QRK] Quark | POW/POS | 0.10.6.3 - New Self Moderated Thread - page 23. (Read 64220 times)

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

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

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

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

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

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)

Excellent reveal.
Pardon my ignorance, where does this get (strTreasuryPaymentAddress = "QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv" assigned?

Search "getblocktemplate" (37 hits in 13 files)
  C:\Users\administrator.STARWING\Quark-Master\doc\build-unix.md (1 hit)
   Line 239: Mining is also possible in disable-wallet mode, but only using the `getblocktemplate` RPC
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes\release-notes-0.10.0.md (5 hits)
   Line 283: software relying on its `getblocktemplate` must be updated in parallel to use
   Line 288: If you are mining with the getblocktemplate protocol to a pool: this will affect
   Line 299: `getblocktemplate` method. This enables miners to check the basic validity of
   Line 357: - `ff6a7af` getblocktemplate: longpolling support
   Line 580: - `b45a6e8` Add test for getblocktemplate longpolling
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes\release-notes-0.7.0.md (2 hits)
   Line 44: * Replaced the 'getmemorypool' RPC command with 'getblocktemplate/submitblock'
   Line 50: BIP 22 - 'getblocktemplate', 'submitblock' RPCs
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes\release-notes-0.8.2.md (2 hits)
   Line 76: * fixed a getblocktemplate bug that caused excessive CPU creating blocks.
   Line 100: * Entering the 'getblocktemplate' or 'getwork' RPC commands into the Bitcoin-Qt debug
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes\release-notes-0.9.0.md (1 hit)
   Line 237: - 'getblocktemplate' does not require a key to create a block template
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes\release-notes-0.9.5.md (2 hits)
   Line 28: software relying on its `getblocktemplate` must be updated in parallel to use
   Line 33: If you are mining with the getblocktemplate protocol to a pool: this will affect
  C:\Users\administrator.STARWING\Quark-Master\doc\release-notes.md (2 hits)
   Line 84: getblocktemplate must be updated in parallel to use libblkmaker either
   Line 94: - If you are mining with the getblocktemplate protocol to a pool: this
  C:\Users\administrator.STARWING\Quark-Master\qa\rpc-tests\getblocktemplate_longpoll.py (7 hits)
   Line 38:         templat = node.getblocktemplate()
   Line 45:         self.node.getblocktemplate({'longpollid':self.longpollid})
   Line 47: class GetBlockTemplateLPTest(BitcoinTestFramework):
   Line 49:     Test longpolling with getblocktemplate.
   Line 55:         templat = self.nodes[0].getblocktemplate()
   Line 58:         templat2 = self.nodes[0].getblocktemplate()
   Line 91:     GetBlockTemplateLPTest().main()
  C:\Users\administrator.STARWING\Quark-Master\qa\rpc-tests\getblocktemplate_proposals.py (6 hits)
   Line 87:     rsp = node.getblocktemplate({'data':template_to_hex(tmpl, txlist),'mode':'proposal'})
   Line 91: class GetBlockTemplateProposalTest(BitcoinTestFramework):
   Line 93:     Test block proposals with getblocktemplate.
   Line 98:         tmpl = node.getblocktemplate()
   Line 162:         rsp = node.getblocktemplate({'data':b2x(rawtmpl),'mode':'proposal'})
   Line 182:     GetBlockTemplateProposalTest().main()
  C:\Users\administrator.STARWING\Quark-Master\src\rpcclient.cpp (1 hit)
   Line 57:     { "getblocktemplate", 0 },
  C:\Users\administrator.STARWING\Quark-Master\src\rpcmining.cpp (4 hits)
   Line 321: Value getblocktemplate(const Array& params, bool fHelp)
   Line 325:             "getblocktemplate ( \"jsonrequestobject\" )\n"
   Line 379:             + HelpExampleCli("getblocktemplate", "")
   Line 380:             + HelpExampleRpc("getblocktemplate", "")
  C:\Users\administrator.STARWING\Quark-Master\src\rpcserver.cpp (3 hits)
   Line 276:     { "mining",             "getblocktemplate",       &getblocktemplate,       true,      false,      false },
   Line 276:     { "mining",             "getblocktemplate",       &getblocktemplate,       true,      false,      false },
   Line 835:     if (strMethod != "getblocktemplate")
  C:\Users\administrator.STARWING\Quark-Master\src\rpcserver.h (1 hit)
   Line 160: extern json_spirit::Value getblocktemplate(const json_spirit::Array& params, bool fHelp);

it's not an attack - it's the result of broken values from getblocktemplate

 "payee": "QVvYypXoiRXcJpJpRVkftKEjMkXbd6UKJv",
 "payee_amount": 10639123200,
 "masternode_payments": true,

Our network was attacked

We're going to recalibrate the blockchain

Please do not trade in the near future

It may take some time （May be a week）

Inform the exchanges you know to close quark deposits and withdrawals

Woo Hoo

Don't worry

The pool is adjusting its code to the quark's master node

This may take 1-2 days

Once they can properly support the master node payment

Our network will be up and running again

chain's sick again

Yes, that's why they were rejected

-102.697 QRK

That's because quark is 5 decimal places, not 8
They need to adjust the code
Otherwise, master node rewards cannot be allocated correctly



Here's a reference from the developer
The cause of the error

Nominal output 106387.53784          actual output 106.38753784



See reference here
https://twitter.com/Quark_revive/status/1148258165378568197

Indicates a solved block in about 4 minutes
Mining on a single wallet at 18.4 Gh/s, 2 miners
   Quark (quark)   -102.697 QRK   1.166 k   7 072 567   4 mins   18.4 Gh/s   -0.00191


Looks like they went back to the drawing board.

This pool - orphan blocks

Maybe they still can't allocate the masternode correctly
Developers have figured out why

Quarks are 5 decimal places (important)
Some pools default to 8 decimal places, so the quark's trading output is negative
This will cause the pool to reject itself

Looks like cryptonova has upgraded and is currently re-indexing

We have identified the reason why the pool failed to allocate the master node correctly
Now waiting for pool adjustment code

————————————————————
In addition, we have officially upgraded successfully

That ineffective pool no longer affects us

If your pool mining with https://cryptonova.eu please point your miners elsewhere while we wait for them to upgrade.

You can check the Quark version being used here: https://cryptonova.eu/explorer

so cryptoid it is, thanks.
keep in mind that a 0.10.7 peer can get caught by a wrong chain,
which happened to me, i had to "squeeze thru" to the right one )
more practice after the kumacoin forking lol