[Passed] Reduce the total displayed supply of NSR by 10,000

[jooize]

I don’t see how there’d be any difference in such metrics. Can you play with some numbers to demonstrate?

[assistant]

Hi @tomjoad

Here are the details for the Motion Vote on e0b3f80e5d9f58d3c3df27e346b61233b9cd5153:

---

##e0b3f80e5d9f58d3c3df27e346b61233b9cd5153
Blocks: 4636 (46.360000%)
Share Days: 1674828011 (50.713730%)

---

[Nagalim]

Is the blockchain explorer not working properly?
http://blockexplorer.nu/motions

[assistant]

Hi @tomjoad

Here are the details for the Motion Vote on e0b3f80e5d9f58d3c3df27e346b61233b9cd5153:

---

##e0b3f80e5d9f58d3c3df27e346b61233b9cd5153
Blocks: 4643 (46.430000%)
Share Days: 1677662868 (50.788705%)

---

[tomjoad]

Is the blockchain explorer not working properly?

It’s been frozen for about a day. Our block explorer guy is aware of it so it should hopefully be fixed soon.

It looks like this motion may pass if current voting trends continue.

[JordanLee]

I had indicated this change will be a little messy, meaning there are some temporary problems that will be created at the time of the switch. They don’t have neat automated solutions, but they will be limited in scope and duration. The problems you mentioned are valid reasons for shareholders to be concerned about this proposal. Opposing the change on the basis of the problems identified is reasonable. I think the change brings us a net gain, but not by a lot. The change is permanent, but the problems will be transitory.

what about the other users that do use these configs? When should they update them?

At the time of the switch.

The NSR custodian and fee votes. Internally the votes values are stored in satoshis so it’s not a problem, but the data feeds provide amounts in NSR. So the data feeds would have to update at the exact same time too. If the data feed providers use the votenotify config then we may trigger it at switch time to make sure they update.

But even so, if the clocks of the data feed provider and the node using it are not in sync, the amounts could be interpreted incorrectly.

But I guess data feed providers could just stop voting for NSR grants and fee a few hours before the switch.

@Cybnate and @cryptog can you confirm you understand this issue and be careful to remedy it at the switch time?

[tomjoad]

@assistant motion vote e0b3f80e5d9f58d3c3df27e346b61233b9cd5153

[assistant]

Hi @tomjoad

Here are the details for the Motion Vote on e0b3f80e5d9f58d3c3df27e346b61233b9cd5153:

---

##e0b3f80e5d9f58d3c3df27e346b61233b9cd5153
Blocks: 5004 (50.040000%)
Share Days: 1810040176 (54.118211%)

---

[tomjoad]

The motion has passed! I will wait for further comment from @JordanLee, @sigmike and others on what technical direction they would like to take before drafting up our 60-day implementation plan.

This denomination change should help us market our network much easier and I am happy that shareholders agreed.

[sigmike]

At the time of the switch.

These values are not very important, but I think having to change the config at upgrade time is better than having to restart the client at a precise time.

I will wait for further comment from @JordanLee, @sigmike

I think we’re mostly waiting for exchange comments.

Still, about #1:

The recommended course of action for exchanges would be to not upgrade until the switch time.

Exchanges are intensive users of the client and the most likely to find bugs in the large internal changes. So recommending them to make this important upgrade at a specific time without a possible way back adds the risk of a temporary delisting if something goes wrong, until the problem is fixed.

I think it’s less risky to have 2 distinct upgrades. Note that 2.2 could also have an automatic switch time if we want. It’s just mixing the important internal changes and the time constrained upgrade that concerns me.

[cryptog]

But I guess data feed providers could just stop voting for NSR grants and fee a few hours before the switch.

I will certainly comply with above. So count me in.

[cryptog]

Issue with the official block explorer. It mentions:
e0b3f80e5d9f58d3c3df27e346b61233b9cd5153 50 votes just now 535,044 3,340 (33.40%) 1,162,269,035/3,145,721,565 (36.95%)

[tomjoad]

Issue with the official block explorer. It mentions:e0b3f80e5d9f58d3c3df27e346b61233b9cd5153 50 votes just now 535,044 3,340 (33.40%) 1,162,269,035/3,145,721,565 (36.95%)

It's been frozen for about a day. Our block explorer guy is aware of it so it should hopefully be fixed soon. It looks like this motion may pass if current voting trends continue.

[JordanLee]

I think it’s less risky to have 2 distinct upgrades. Note that 2.2 could also have an automatic switch time if we want. It’s just mixing the important internal changes and the time constrained upgrade that concerns me.

I’m willing to proceed toward two releases with 2.2 having a switch date.

I think we’re mostly waiting for exchange comments.

That is the way I see it too. We have a release plan now, but we ought to get some input from exchanges before we commit to a course of action.

[Cybnate]

Happy to comply and clear the datafeed for a few hours before the switch and turn it back on when required. Not sure if I fully understand the why but I believe I don’t need to. As long as the time is clearly communicated in advance. Depending on the time of the day I might have to turn it off for longer especially if it happens outside of the weekends.

Another risk is that others are using private datafeeds. e.g. I have a testfeed. We might need to clearly communicate that they also need to be turned off.

[tomjoad]

It doesn’t appear that exchanges are going to comment here. Are we able to commit to a denomination switch date yet, or will it depend on developer availability for v 2.2? Once that final date is established I can begin preparing a schedule for activities (notifying exchanges, posting in social media, etc.) we need to complete as shareholders prior to the change occurring.

[ttutdxh]

Were are we on this?

[ppitonak]

Any updates on this?

[tomjoad]

Implementation of the denomination switch could take awhile longer, as B&C Exchange needs to finish its initial development first.