Nu 3.0.1 release with new currencies

Phoenix 2016-11-01 02:06:51 UTC #4

I’m very pleased to see this. @woolly_sammoth what remains to be done to adapt NuBot to 3.0?

The next step will be finding exchanges that will list CN-NBT. After the protocol change occurs, I will request the first grant of CN-NBT. Once we have this grant and the NuBot changes, we will be prepared to support trading pairs on exchanges.

Who wants to step up to lead this important marketing task?

I think we should really push exchanges to place CN-NBT as the denominator, not the numerator as is the case with US-NBT on Poloniex. This improves the readability of our price.

Finally, with the OP @sigmike has met the requirements for receiving a rapid deployment bonus. Having met the requirement on the the 30th, that qualifies as a 14 million NSR bonus as I recall. Is that what you were expecting @sigmike?

Cybnate 2016-11-01 08:07:18 UTC #5

I’m having intermittent issues with the Linux 3.0.0 client. The first time it appeared to be stuck at:

“blocks” : 1120769,

Had to restart the client and it now appears to work.
Might be a coincidence but blockexplorers are also not working. Is it just me?

V2.01 client still works, although I noticed that there are unusual large gaps between the blocks at times (e.g. 7 minutes) or large reorgs, meshing issue, not sure. Haven’t seen that before with this blockexplorer. You can see it here: https://svr1.nubitsexplorer.nu/chain/Nubits. Maybe it is not v3 related, it seems to be going on longer than that.

Anyway, will start minting with the new v3.0.0 client.

sigmike 2016-11-01 08:17:15 UTC #6

Should I add it to the nubits.com download page?

That’s how I understand the bonus rules yes.

I didn’t change anything related to the download in this version, so I think it’s not but it’s still possible.

Cybnate 2016-11-01 08:44:10 UTC #7

Something is not right. V3.0.0 reports up to date while it is multiple blocks behind. It doesn’t seem to catch-up. It is now 25 minutes behind. When I start V2, it catches up. Restarting v3.0.0 recognises the updates but won’t progress by itself.
Curious to hear whether others have better results.
Edit BTW, the test env also seems to have stalled at block 612665 even though I still have a v2.1.1 client running with 2 peers. Can you confirm that? @sigmike

sigmike 2016-11-01 09:07:59 UTC #8

I’ll check that.

Indeed my client was not minting anymore. It is now, and it has already found some blocks. It’s still on 2.1 though. I’ll start a 3.0 client.

Cybnate 2016-11-01 09:10:11 UTC #9

Thanks

That works!

sigmike 2016-11-01 10:03:47 UTC #10

Indeed there’s a problem with the park rate calculation. I will certainly have to make another release. Do not upgrade yet.

sigmike 2016-11-01 12:09:48 UTC #11

I’ve made a fix: https://bitbucket.org/JordanLeePeershares/nubit/pull-requests/270/30-park-rates-fix/diff

I’m testing a full chain download and when it’s done I’ll release version 3.0.1.

sigmike 2016-11-02 11:57:23 UTC #12

The full download test was successful. I found another problem that I fixed though. The changes between 3.0.0 and 3.0.1 are here: https://bitbucket.org/JordanLeePeershares/nubit/branches/compare/v3.0.1 v3.0.0

I updated the first post and nubits.com.

backpacker 2016-11-02 19:03:04 UTC #13

https://rbfi.io/dl.php?key=/WH1y/Nu-Qt.dmg

sha256: d721889cc1988c8058e150ab9730333a54687db27ba4a9d69c388d8234799205

cryptog 2016-11-12 11:39:56 UTC #14

What is the current rate of adoption of Nu 3.0.1?

Cybnate 2016-11-13 07:13:26 UTC #15

When I look at the number of nodes I’m connected to, I see 4 out of 13 nodes on v3.01. Just over 30%. For the protocol change it is about the % of minters and their stake though. I don’t know how to obtain those figures.

sigmike 2016-11-13 10:59:52 UTC #16

Right now: 41.55% of the last 2000 blocks.

Testnet will switch at 2016-11-25 14:00:00 UTC.

When I imported the protocol switch code from B&C I also imported the getprotocolvotes RPC that will give you these numbers.

sigmike 2016-11-15 08:08:40 UTC #17

The protocol vote passed. The new protocol will be activated at 2016-11-28 14:00:00 UTC.

I made a mistake though. The protocol switch was triggered when 55% of the blocks were generated by this version whereas I proposed 60%. I guess when I imported the B&C code I planned to change the percentage after my proposal has been discussed, but when the final release came and there was no discussion about it I probably assumed I already had put the proposed percentage so I didn’t update it.

Given this percentage did not raise any discussion, that the numbers are not very different and that the absolute requirement to switch is 50%, I think it’s better to keep it that way. All the other options would probably result in a fork between shareholders wanting to switch and the others anyway.

Cybnate 2016-11-15 08:33:42 UTC #18

Well, I suppose it won’t hurt to advance the date a bit. We just have to make sure that more than 55% of the block continue to be on v3.01 to prevent a fork I believe. Is that correct?

sigmike 2016-11-15 08:48:32 UTC #19

No, a fork would happen only if some minters decided to reject some block from the other side (by running a different client). Since only those who don’t want to switch may want to do that, and given they are a minority (although this is fluctuating) they would just fork themselves out. Now that the switch has been triggered it will happen at the planned time. The only way to prevent it would be that a new majority build a higher chain starting before the vote passed, or that the majority decides to run a client with different protocol rules (but if they happen to not be the majority they will just be forked out).

So that means more than 50% of the minters must be running on 3.0 for the network to stay healthy. So 55% is actually a good target.

cryptog 2016-11-15 11:13:14 UTC #20

I suppose it is now secure the do the upgrade. I ll do tmr.

sigmike 2016-11-16 07:47:00 UTC #21

Since shareholders funded these builds I guess they should be put on nubits.com. I did it.

Phoenix 2016-11-16 19:01:48 UTC #22

The network is now at 68% adoption of the new protocol. That is good enough for the fork, although it would be better to have everyone switch before the fork on the 28th.

Sabreiib 2016-11-23 12:20:22 UTC #23

Has this version solved the problem of high CPU occupation?