That is not happening. We’ll keep you updated.
8 Likes
thanks i update myself
Ok, but then please describe what the situation is and what is on the table.
1 Like
Ok, could you please inform us where we should be looking to make sure we don’t miss any of such updates. Thanks in advance.
1 Like
So, please keep us updated ASAP. To be honest, it is hard to see still some labour pains and never ending changes in NEM/Symbol after so many years. I know, that we are in rapid growth enviroment but still…
3 Likes
long story short: we’re still negotiating
3 Likes
What’s the latest update here?
This thread started off with a clear update but then went through confusion into reversing back. In case there was (transparent) discussions happening over in Discord, you could perhaps share the link to the respective threads/messages.
Greetings from LuxTag
2 Likes
Could someone share an update for the situation?
2 Likes
Info would be nice…
1 Like
The new active NEM&SYMBOL leaders are probably more active at Discord. I have asked over there to please proceed and respond in this forum thread.
and just starting this week … there is a hardfork ? 
I am seeing many red flags in project management since Kristie joined xD But this is only my opinion, right 
“La roue tourne” 
There was a hardfork to fix a bug: September 14th - Post Mortem - HackMD Not sure how this is Kristie’s fault…?
Also I would disagree, seems to me that we have some leadership (finally) and a team that are focussed on delivering a product.
First, it’s only my opinion. Great if you or others found a leader in Kristie.
Second, I am referring to the 32-hours hard fork with 0 preparation for operators. Who forgot to tell the community that their keys expire? Or who forgot that this is going to happen? (1 week pre-expiry of more than 30% voting stake is a bit sharp don’t you think? But offtopic here and could be responsibility of operators themselves.)
3 Likes
Where is the discussion about what happened with voting / the “bug”? I see no discussion about it in client-cpp on Discord. Things I saw discussed lately include ZKP and rollups but I haven’t seen a discussion about Symbol’s finalization gadget or any other features in Symbol already that may or may not need changes [e.g. “multisig bug / feature”]. But then, out of the blue operators do have to accept a hard fork to-happen-in-32-hours.
The community is fragmented, realize it or not ; development with Symbol is near 0 outside of Japan [“core agreed” projects xD] ; Partnerships stalled ; Social dead ; I guess it’s now only supernodes who need to be up to date with decisions, not the community anymore, that’s what is sad.
I hope I will be proven wrong - when I see there is “negotiation” that are taking very long time and then in the mean time a hard fork. Guess what, I get skeptical and I hope for #NEM that SNs do take the necessary time to do their due diligence with regards to actions that are being executed.
3 Likes
I don’t think that anyone wanted it to be such short notice but if finalisation was stalled then it needed an urgent fix hence the timeline. To be fair nearly 90% of node owners have updated: Symbol node list and a reasonable percentage of those that didn’t haven’t bothered to update since v1.0.0 (including several supernodes).
Not saying it was an ideal situation, far from it and lessons hopefully will be learned but if it is an urgent problem then it requires urgent action.
I don’t really want to get into discussing pros and cons of different personalities of NEM past and present but in my opinion I think focussing on the technology and bringing in some new ideas is a good thing.
From trawling Twitter every day when writing http://symbolblog.com I generally see support for the new direction from the Japanese community. I think everyone wants to see NEM/Symbol being successful so I guess let’s give it a chance and judge based on results. Symbol has only been live for 6 months it will take a while…
2 Likes
For the completeness of this thread, I am pasting the reply from Gimre here. He responded in Discord on 16/Sep/2021 that there’s not update yet.
Remark from my side:
Perhaps the community should involve here? Or is it only the core developers (+Kristy?) who “own” decision-making for NEM & SYMBOL at the moment?
Presumably the negotiation is confidential, not sure how the community would be able to resolve the situation. I don’t know any of the details of what is happening but I am just not sure why if a new non-profit is being set up by the team, the Trust still needs to exist and control the funds.
With one member leaving, that leaves four other Trust members who presumably “own” all decision making from NEM and Symbol? Also I am not really sure who those four members are or what technical qualifications they have which would make them the most appropriate people to decide what the best interests are for NEM/Symbol going forward. One seems to be a member of the now defunct NEM Group but I can’t find much info on the others.
Guess I would rather have the technical experts that are building the technology and know what needs to be done decide how the funds should be spent than the other four guys we don’t know much about.
3 Likes
That’s exactly what I mean, for me this sounds more like a hostile takeover rather than anything positive for the ecosystem.
And to @SJM211: how you frame trustees is a real shame - considering that the Trust was created to protect exactly from those hostile magic tricks -) but who am I to even bring up these problems, eh…
1 Like
I don’t mean to frame trust members in a certain light, just replying as a counter argument to this:
And I certainly didn’t single anyone out (as has been done above).
I am just saying that I don’t know anything about them (apart from Jeff who is leaving) and I am not sure that many in the community do.
Anyway, we can agree to disagree. I don’t think it is a bad thing that the team who have developed NEM and Symbol from nothing should be able to have control over the budget.
I, like you hope that it is resolved soon too.
2 Likes