search

gridcoin-community / Gridcoin-Tasks

Gridcoin community tasks repository
https://gridcoin.us
MIT License
24 stars 5 forks source link

[CLOSED] 7000 GRC bounty: solving superblock situation (6850 GRC) + creating superblock (150 GRC) #141

Closed skcin closed 6 years ago

skcin commented 6 years ago

Issue by Erkan-Yilmaz Sunday Jun 25, 2017 at 20:28 GMT Originally opened as https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/136

situation:

Why is this important?

A "regular block" processes the transactions that have occurred in the network during the block's time frame

some investigation results:

@barton2526: 250 GRC pledged to whoever (or multiple if team effort) can solve the current superblock situation @barton2526: and 50 GRC to the wallet that stakes the superblock

skcin commented 6 years ago

Comment by XaqFields Sunday Jun 25, 2017 at 20:36 GMT

xaqfields: 250 GRC pledged (additional to @Barton26) to whoever (or multiple if team effort) can solve the current superblock situation

xaqfields: 50 GRC pledged to the wallet that stakes the SB

So total should be 500 GRC pledged to solve the current SB situation & 100 GRC to the wallet staking the SB

skcin commented 6 years ago

Comment by elspru Sunday Jun 25, 2017 at 22:30 GMT

How would someone go about fixing it? i heard a theory that it is because people aren't staking their wallets. my idea is that it is because of lots of new users. the new user idea can be tested by if someone can see difference in number of cpids of previous superblocks and this one.

If there is a big difference in this one it could be the issue. in which case team gridcoin could temporarily stop new members till the sb finishes synchronizing. Then reopen on the new block.

skcin commented 6 years ago

Comment by jericomanapsal Monday Jun 26, 2017 at 01:27 GMT

I pledge 100 GRC to whoever (or a set of people) solves this situation 😺

skcin commented 6 years ago

Comment by Bouowmx Monday Jun 26, 2017 at 03:48 GMT

I pledge 250 GRC to the person(s) who resolve, and 50 to the address that stakes the next superblock.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Monday Jun 26, 2017 at 07:29 GMT

see also comments here

skcin commented 6 years ago

Comment by Editorial-Meat Monday Jun 26, 2017 at 08:30 GMT

We have been trying to get our NN hashes to sync up in the developer's Slack. Even when we execute a NN sync through syncdpor2, and compare the hash after, we don't get the same hash. It could be due to the number of CPIDs changing, as we are not all returning the same number of CPIDs present in the network. We had numbers between 2199 and 2210.

Maybe it would be an option to buffer beacons near an expected superblock so the network come come to a consensus on the hash? The network is currently split about evenly on consensus between 3 different hashes, which is why no SB is forming (?). What is the consensus threshold?

In the meantime, if the network growth is the problem, we may be able to force a superblock by having everyone manually sync their wallets to the neural net? It seems the 45 minute timer to sync the network is too long.

skcin commented 6 years ago

Comment by Editorial-Meat Monday Jun 26, 2017 at 08:48 GMT

As another note, we currently have consensus on the hash:

"Neural Hash" : "Popularity,Percent %", "213472e4b11ea3170e1a01323f309576" : "29; 99.97%",

But only 29 participants of the quorum trying to stake...? The chance of that is very small unless there just so happens to be a whale included. Imagine if these are all wallets with a tiny balance and a tiny mag. Out of interest, how many whales are actually using Windows? If most Windows users are new, small wallets, this will keep happening.

skcin commented 6 years ago

Comment by Editorial-Meat Monday Jun 26, 2017 at 09:25 GMT

I think we need to set the quorum to have an entry criteria based on DPOR, so that we do not end up with a situation where once consensus IS FINALLY REACHED the chance to stake is about zero.

skcin commented 6 years ago

Comment by dc7dgrid Monday Jun 26, 2017 at 13:41 GMT

I want to raise the bounty: I pledge 1000 GRC to the person or team who will solve this issue.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Monday Jun 26, 2017 at 14:35 GMT

thanks @dc7dgrid

I'll ask @barton2526 to set up a GRC address so people can send it to there

skcin commented 6 years ago

Comment by AbuApellius Tuesday Jun 27, 2017 at 03:22 GMT

Sorry for any lack of understanding; I'm new to gridcoin. Is the problem that there are not enough CPU cycles going to validate/generate the superblock? If that's the case, why not turn that task into a BOINC project?

skcin commented 6 years ago

Comment by Vortac2 Tuesday Jun 27, 2017 at 13:04 GMT

I pledge 5000 GRC to the person(s) who resolve this

skcin commented 6 years ago

Comment by Erkan-Yilmaz Tuesday Jun 27, 2017 at 13:20 GMT

@Vortac2 thank you

skcin commented 6 years ago

Comment by barton2526 Tuesday Jun 27, 2017 at 16:16 GMT

I have now set up an independent isolated INVESTOR wallet to hold the bounty funds and distribute them once the issue has been resolved. This address is SD8bHkNcZeQqZFta4Us7EfMmperAbBeqAe

@XaqFields @jericomanapsal @Bouowmx @dc7dgrid @Vortac2 @Erkan-Yilmaz

https://www.gridcoinstats.eu/address/SD8bHkNcZeQqZFta4Us7EfMmperAbBeqAe

skcin commented 6 years ago

Comment by Erkan-Yilmaz Tuesday Jun 27, 2017 at 22:33 GMT

we have a NEW superblock !

getblockhash 942327 => b0354a55b11c02f2768c2a0368b0eff5ab2d8e7a1a5a4fb06dbada5826368d23

an investor seems to have staked it:

skcin commented 6 years ago

Comment by barton2526 Wednesday Jun 28, 2017 at 00:16 GMT

Are we fully in agreement that 150 GRC should be sent to the staker and the remaining bounty (6850, of which I hold 5750) should be held until a solution to the problem is developed or at least understood? If so, I will pay out 50 GRC (myself) + 50 GRC (from @XaqFields) + 50 GRC (from @Bouowmx). I also hold @Vortac2's bounty but he did not specify to pay to the staker.

Please confirm on irc with me.

skcin commented 6 years ago

Comment by barton2526 Wednesday Jun 28, 2017 at 01:21 GMT

150 GRC sent to staker of the superblock. See here for tx:

https://www.gridcoinstats.eu/tx/33556f17ba480bc3763b9e93553ba64e7bd130849e9851a411081baf761a1843

Escrow still holds 5600 GRC for dev solution.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Wednesday Jun 28, 2017 at 10:03 GMT

likely causes of the delayed superblock + new Gridcoin version:

https://steemit.com/gridcoin/@ravonn/gridcoin-superblock-we-forgive-you

skcin commented 6 years ago

Comment by barton2526 Wednesday Jun 28, 2017 at 17:31 GMT

Additional 500 GRC sent to staker (250 from @Vortac2 and 250 from myself). Bounty wallet is now at 6350 GRC for dev solution (pending leisure update(?))

skcin commented 6 years ago

Comment by Quezacoatl1 Wednesday Jun 28, 2017 at 18:24 GMT

Thanks guys, I seem to be the lucky staker :)

skcin commented 6 years ago

Comment by XaqFields Wednesday Jun 28, 2017 at 18:32 GMT

Thanks @Quezacoatl1 for staking! That's the main thing we needed during this SuperBlock struggle was people to stake their coins. Enjoy your winnings :-)

skcin commented 6 years ago

Comment by barton2526 Tuesday Jul 04, 2017 at 07:32 GMT

Regarding the 6750 GRC bounty still active: As holder of the escrow it's not ultimately my call, but I do not consider this leisure update to have satisfied the terms of "fixing the NN problem". I would not feel comfortable paying out the bounty until a more stable and tested solution is put in place. I would also prefer to wait several days to ensure said solution "holds" and we do not payout prematurely. @bullshark @vortac @xaqfields @dc7dgrid @Bouowmx are free to disagree.

If any bounty payer wishes me to send their bounty out at any time, just let me know.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Friday Jul 07, 2017 at 04:51 GMT

no new superblock for more than 54h since the last superblock #951984

skcin commented 6 years ago

Comment by denravonska Friday Jul 07, 2017 at 05:29 GMT

A lot of people are still running old nodes, still making it hard to reach consensus. On my wallet, only 37% (10/24) of the NN-capable connections are running 3.5.9.2.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Friday Jul 07, 2017 at 05:49 GMT

"We had now 5 superblocks after this 148h-MEGA-long superblock #942327, and the average and median times were about 33h (or in block terms: 1931 blocks and 2051 blocks)." (We are waiting for you, oh SUPER-block... again)

skcin commented 6 years ago

Comment by Vortac Friday Jul 07, 2017 at 07:02 GMT

Man I was so confused by the few emails that I got tagged in. Don't forget to add that 2 onto Vortac. Best of luck to whatever this is.

skcin commented 6 years ago

Comment by Erkan-Yilmaz Friday Jul 07, 2017 at 13:17 GMT

after 62h there it is:

skcin commented 6 years ago

Comment by vega40k Thursday Jul 27, 2017 at 09:59 GMT

i was the creater of this on. superblock: #956235 (2017-07-07 13:00:00) i was so glad :-)

skcin commented 6 years ago

Comment by barton2526 Monday Aug 28, 2017 at 17:22 GMT

As the current holder of this bounty, I think all of us should come to an agreement on what to do regarding these funds. I can continue to hold them, they can be paid if you think the bounty has been met, or I can return the bounty to the donators. Thoughts? @XaqFields @jericomanapsal @Bouowmx @dc7dgrid @Erkan-Yilmaz @Vortac2

skcin commented 6 years ago

Comment by tomasbrod Monday Aug 28, 2017 at 17:35 GMT

The superblock situation definitely got better. But from a "Critical" to "Not so good". When considering bounty, don't forget PR 522 (it takes effect at v8, if it helps, we don't know).