#**unclear rules in Shielded Expedition**

1 messages Β· Page 1 of 1 (latest)

potent bronze
#

.

dry flicker
#

Frustrated I am. but if the matter is officially settled, I'll 🀐 on this one πŸ˜„
And cheers for the lucky ones who registered on both sides and ranked on both (with some bittersweetness on my end)

fair patio
#

I do think those who land outside of top 100 due to people playing twice should be considered. I feel mostly for them.

#

No one seems to think of those people.

dry flicker
#

Would it be ok to EXTEND the leaderboard by the number of double ranked people, so that no-one is left behind if they would have ranked otherwise ?

frail nova
#

Great, this is what we were looking forward to

dry flicker
#

we're not talking about 30 people I think. That would add some rewards to the global pool, but given the absence of clarity, that would at least reward everyone who would have ranked

fair patio
#

Would kinda be a two birds one stone solution.

#

Poor birds.

#

But yes.

dry flicker
#

Dare I propose that would "take" a portion from the rewards of those who double ranked to reward the outsiders ? Robin hood style ? otherwise it's out of the pocket of the Anoma foundation (just throwing ideas)

fair patio
potent bronze
barren pulsar
#

many filled forms for both Pilots and Crews, but with same address and got filtered out.

the problem is why team didn't remove ones used two different addresses during registarion

could resolve all debates over this

pine agate
#

So what about the ease with which S5 passed? Some individuals merely made minor adjustments, sometimes even just modifying a single line of code, and they were able to pass the task "Building protocol and cryptography improvements."

Is there any grading criteria? I think the team has it.

spring glade
#

I registered as both a pilot and as crew using the same address. As a result, I can only participate as a pilot. In order to participate both as a pilot and as crew, would I have needed to register from different addresses, despite the fact that multi-accounting is prohibited?

sudden burrow
potent bronze
fair patio
fair patio
# potent bronze wdym?

I for instance also registered twice but used the same public key. Those got filtered out.

dry flicker
#

Same here

potent bronze
fair patio
#

So in a sense there was a 'prevention' for people signing double, but at the same time there wasn't. But yeah, it wasn't clearly set in stone.

dry flicker
#

If you put the same Namada address in both form, you'd get filtered out

pine agate
fair patio
#

It's oki hehe.

spring glade
eager ibex
#

In fact, I think we also need to clarify whether one S class can allow two people to score (I hope it's not an inappropriate interjection).

eager ibex
pine agate
# potent bronze wdym?

What I mean is, did they actually contribute? And the team doesn't have a criteria, in terms of fairness, I myself have changed nearly 20 files to pass that task, but others achieved it too easily.

potent bronze
fair patio
# dry flicker Dare I propose that would "take" a portion from the rewards of those who double ...

I find this quite fair though. Those who played double also knew their own intentions of playing twice and if they thought of the other players in the game they'd be aware of potentially taking the place of someone else.

Though it shouldn't be a crazy amount. Also perhaps only do it for those who surpass a certain threshold amount of NAM tokens as it should be fair for them as well? I dunno, also spitballing.

#

Dunno where I'll land, but I'm also willing to give to the ones outside of top 100 if there's a fierce rejection towards this idea.

#

But Anoma also had a reserve, I think Gav mentioned a couple times.

potent bronze
# eager ibex I noticed on the leaderboard that two people submitted the same S class and both...

i can only give my personal opinion on the matter, because i don't think that we have a proposal yet for this matter

my personal opinion is: it depends

  1. you have you collaborated --> points
  2. you are using someone else's (slightly modified) code that's already been submitted and pretending it's your own --> no-points or ban
  3. you clearly operating 20 accounts submitting the same code --> ban
potent bronze
hallow echo
potent bronze
potent bronze
#

we are currently auditing "security vulnerability" and "protocol improvement" subclasses

austere rose
#

I have participated both as a pilot and crew and I have submitted separate S tasks for both categories separate submissions for each S class task. So it’s not fair to disregard S class points, as I have hosted different nodes to ensure unique submissions.

potent bronze
#

there are problems that have arisen because we have no rules and no evaluation criteria

pine agate
austere rose
#

I will let the team decide, but wish to make it clear that lot of folks who participated as both, have played it fair. So it’s not fair to remove any points for us.

potent bronze
pine agate
fair patio
#

No worries!

austere rose
#

My apologies

eager ibex
errant junco
#

Does it mean an entity could register twice?

gaunt gull
potent bronze
eager ibex
austere rose
icy pond
#

You didn't have clear rules stating that one person could fill slots in two categories as both Crew and Pilot, and only realized this after the SE ended. This oversight is so ridiculous, especially given the small number of prize positions (100 in each category). Roughly speaking, 30 people participating as both Pilot and Crew could potentially occupy 60 spots in the top 100 (on both sides), which is absurd, lol 😱

eager ibex
potent bronze
potent bronze
gaunt gull
# potent bronze wdym?

I mean, if 2 players cooperate to complete a task, it should be counted as 1 passed submission
For example: build application (64B ROIDD) has 4 people completing A, B, C, D of which there are 3 submissions (1, 2, 3). the number 3 submission was completed with cooperation between C,D then the scoring formula should be
64B/3 ~ 21.6B , to be more fair, 21.3B should be divided equally by C and D that mean 21.6/2 ~= 10.3B

rigid crag
potent bronze
icy pond
icy pond
eager ibex
# potent bronze i totally get why you're saying this, but how to actually track/evaluate this?

Emmm, in fact, it's quite easy to implement. We just need to check if one account corresponds to one S class submission. I raised this issue because I saw in the spreadsheet that two people collaborated on the same task and both received points (see rows 3076 and 3077 at https
://docs.google.com/spreadsheets/d/1YgLo_nt-s_d-2UkrEPcluUnieeuLJtF6vSKsER9EEZU/edit#gid=1704705698). I am questioning this phenomenon.

potent bronze
#

like maybe maybe we can identify a cluster or two of accounts all submitting the same thing

eager ibex
potent bronze
#

so it's kind of like unscrambling an egg

eager ibex
potent bronze
potent bronze
eager ibex
fringe pawn
#

Thanks for addressing this. I want to just be clear that we asked several times (the messages are in general chat) and were told it was no problem to register for both crew and pilot. (before competition)

eager ibex
#

However, I think it seems even more inappropriate to submit the exact same task without any modifications.

potent bronze
dry heart
#

if we do not have the rule from the beginning, let's keep it running like it. I don't think it's appropriate to change the rules at this time

potent bronze
#

then we're just restricting people who are open/honest

potent bronze
#

@gaunt gull thoughts?

eager ibex
potent bronze
#

it's kinda like unscrambling an egg

the game setup had some pretty fundamental flaws

#

we're trying to do what we can to correct for this. we've got a few ideas in mind that we'll propose for discussion soon

gaunt gull
eager ibex
oak fox
#

Allowing ppl to register both for Pilot and Crews opened the door to a soft Sybil activity, so there's not too many feasible solutions atm, imo

potent bronze
# potent bronze we're trying to do what we can to correct for this. we've got a few ideas in min...

our priorities:

  1. integrity - we don't want to propose major deviations from the original game, only a last resort
  2. contributors - we want to ensure that strong contributors benefit from their participation and stay in our community
  3. cosmic justice - there's an intrinsic sense of justice, we kinda all know what's right/wrong, at least at the extremes of the spectrum.. like it's not cool to have a cluster of 20 Sybils on the leaderboard, and it's not cool if someone who makes an amazing app isn't recognized/rewarded
hallow echo
#

Hi sir, @potent bronze , currently there are many applications that only support IBC and do not support any shielded actions at all. Is there any auditing for shielded application. Because in my opinion, the application is called a shielded application when it support at least a shielded action.

magic gale
#

but you distributed test tokens only for 1 role, and if a user registered for 2 roles, he had to participate as a pilot, am i wrong?

rigid crag
#

Participants in both crew and pilot can choose which one they want to get prize after knowing their ranks. I think this is somehow fair.

vague nimbus
potent bronze
errant junco
#

As mentioned before that app submission acceptance will be very generous. That means a team of multiple individuals can submit similar apps with similar codes individually. Also the other S Class submissions can be done by sharing infrastructure.

I'm not complaining but it would definitely generate some tensions among the participants if there are competitors that can be considered as sybils.

fringe pawn
rare skiff
stiff adder
#

In general in the Shielded Expedition, we have been flying blind for most of the time with the Nebb broken for many weeks. It was decided not to fix the Nebb, then the preliminary results were not published before the end of the SE but it was mentioned that the preliminary results would be published within 2-5 days after the end of the SE, and this also didn't happen. Considering all this serious lack of transparency, the results in the 'WIP - results' excel tab should be immutable apart from some very minor details or changes

sudden burrow
sudden burrow
#

yeah, it really worth joining the server only today to ask that πŸ˜„
p.s. new type of those spammers? 🧐 just curious, no offense

#

so, you were typing that for 3 minutes? πŸ˜„

stiff adder
# potent bronze how so? if there's no way to stop forking and slightly modding

I think collaborations/joint submissions have been done mostly for difficult tasks. So if it is a joint submission of 2 pilots, and points of that task are X per pilot, each pilot here gets X/2 for the joint submission. If they submit two joint submissions in total for the same category then each gets X points ( (X/2) * 2). In the case of a joint submission of 3 pilots, each would get X/3 points. We were planning some joint submissions before, I asked Spork and he confirmed that this is how it works for joint submissions. Otherwise if for example 500 pilots collaborated to find a vulnerability and submit it as a joint submission, it would be like 500 new vulnerabilities approved? Like instead of each getting X/500 points, there would be suddenly like 500 new vulnerabilities approved if each of these pilots would get X points

fair patio
#

That's @sudden burrow

oak fox
#

Da Sybil detector

sudden burrow
#

Dani, just ban that crap πŸ˜„ anyway it will comeback
p.s. ⚽ time

trail magnet
potent bronze
stiff adder
# trail magnet Never heard of roid splitting in that case, if it was the case, we would have do...

@potent bronze going to reply here to you and lankou: We were planning a joint submission also and asked Spork about this, if it was possible only joint submission of 2 or 3 pilots could also be possible. He confirmed 3 was possible too, and explained in this case the points are just divided by 3. Of course in joint submissions the points are divided, otherwise what is the point of doing a joint submission? Like someone could do a task, then invite 10 other pilots and say 'joint submission' and points for 1 task are multiplied by x11? Right because this one task would give X ROIDS in total, so if 2 or 3 pilots or 10 pilots are sharing this X ROIDS for a joint task they each get X/2 or X/3 or X/10. It has to be like this, otherwise if each would get X ROIDS then X*11 means that one single task would give the same ROIDs as 11 tasks by labelling it as 'joint submission', obviously it cannot be like this and Spork clearly explained this to us weeks ago when we asked. Maybe @trail magnet if you never heard about this you could have verified and asked Spork as well like we did

stiff adder
# potent bronze wdym?

That it has been very opaque for weeks in terms of the ROIDs from A/B/C tasks in general given the Nebb was broken. Only the S class tasks were reviewed frequently and updated on the excel. So at least this shouldn't be modified a lot, because if already ROIDs from A/B/C categories are so opaque and now also after the end of the SE many changes will be done in the excel for S class tasks... In terms of transparency/integrity wouldn't be the best and any changes should be clearly explained and described I think

trail magnet
#

Regarding the crew + pilot,at the very beginning I registered for both with the same nam address, but anoma said then they registered me as a pilot, so I understood we cannot play pilot and crew, BUT if I had put 2 differents addresses I would had been subscribed for both, it think it was understandable from their communication in an email they send , I can look for it. It was not clear, but, as I look back to it, it was written: 2 diff addresses, crew.and pilot is ok, @potent bronze tell me if you want me to find the email

potent bronze
# stiff adder That it has been very opaque for weeks in terms of the ROIDs from A/B/C tasks in...

got it
we're auditing two categories, "security vulnerabilities" and "protocol improvements"

like security vulnerabilities need to be just that, not a ux bug. the problem is that there are lots of contributions that are valuable, like bug bounty valuable, but clearly don't qualify in these two categories

and probably nobody will qualify for protocol improvements, bc that's a pretty insanely hard bar to clear if you see the examples in the blog post pic

potent bronze
potent bronze
potent bronze
stiff adder
clear scarab
potent bronze
potent bronze
potent bronze
#

and the protocol improvements examples seem pretty clear what the intention was

#

another thing is that there are valuable contributions, like bug reports that deserve a bounty (but not security vulnerability ROID points) and docs contributions for a bounty (but not core protocol improvements ROID points)

i think evaluators wanted to recognize these contributions and so they fit them into these categories, but upon review it would mess with the integrity of the contest to leave them like this (as flawed as the contest is)

woven gull
errant junco
scenic sun
#

No competition can achieve absolute fairness. In cases where there's disagreement among community members, I believe it's sufficient to take care of most participants. I hope that the reward scope can be expanded.

#

If there are members who can rank both as a pilot and as a crew member, I think this is unfair to the community members who didn't succeed, as it takes up our ranking spots.

dry heart
cyan tusk
smoky sapphire
#

Why we're discussing this problem. Does anyone see a Pilot can be a Crew or a Crew operate the airship ? this is why we distinguish the role of Pilot and Crew.

frail nova
#

Because most of them work individually and do not have a team. If that had been allowed from the start, the outcome would have been very different.

fringe pawn
rigid crag
#

yes it's a great opportunity that you can choose between crew or pilot reward. and fairest solution as @eager ibex said. people with rank 25 to 70 in crew category could have possibly got doubled rewards if they participated in pilot category imo. people who participated in both now can use this opportunity and get double rewards.

scenic sun
#

If one can compete simultaneously as a pilot and a crew member, why are there two separate leaderboards for competition? I don't understand this practice. I noted yesterday's announcement explanation, but I reserve my opinion.

fringe pawn
#

I'm not here to discuss anything but I want to make the point that again, we asked before competition in the open channels and were told by moderation is was completely fine to register for both classes. I also don't think it would be fair at all to restrict rewards to one class only, ex post (after competition ended) when we have put in double work (and run double infra etc). However, I understand the decision lies with team and I'm cool with that. I do not like however, that the same arguments for changing the rules keep being reiterated again and again when it's already been stated a decision is pending, but that's just my opinion. Not here to discuss, will try and forget about this whole thing as honestly it makes me depressed regarding the nature of our community spirit.

eager ibex
eager ibex
fringe pawn
#

I'm not engaging. Will find the documentation as requested

narrow fable
#

@potent bronze , I know you, Spork, and the entire team have been dedicated to finding the best way to fairly reward everyone involved. However, I notice that we're still debating the same issues repeatedly, which leads to constant discussions.

It's disheartening to see that recent decisions may benefit some at the expense of others, especially when previously approved activities are now being questioned. If the team is considering tightening the rules for activities S5 and S6, why not apply the same rigor to all phase? After all, we know that the mainnet goes through five phases, so we still have time for a new analysis, considering that all activities have already been submitted. It's crucial to ensure that all activities are treated with equality and transparency, regardless of any personal interests that may interfere with the fairness of the process.

gaunt gull
narrow fable
gaunt gull
eager ibex
#

As one of the community members who raised questions yesterday, I would like to share my views again, hoping not to disturb everyone:

1.Regarding the situation where two people submit the same task for an S class, I believe this should not be allowed. In fact, each task submission is a proof of work, so when two people complete the same work, each should only receive half the points due for that category (or they could choose to allocate all the points to one person). If multiple people collaborate and submit multiple times, and receive the same score as a single submission by a group, this is extremely unfair to those who only submit once (especially for those S classes that are beautifully and complexly done by teams but submitted only once under the team's name). I strongly request that the official reopen the form to allow collaborators to submit again. I hope the officials can achieve the greatest fairness.

#

2.Regarding being registered both as a crew and as a pilot, I believe the official blog has already made it clear that this is not allowed (see https ://namada.net/blog/the-namada-shielded-expedition "you can join as a pilot (validator), or as a crew member (user)", the use of 'or' indicates that one cannot participate as both. If it were possible to join as both, it would probably be stated as "you can join as a pilot (validator), or as a crew member (user) or both"). In fact, I think this resembles a Sybil-like behavior (imagine if one person controls two accounts, one as a pilot and one as a crew, isn't that a form of Sybil?). Therefore, I think the fairest approach is to allow them to choose one identity to receive the reward. Indeed, such users already have a tremendous advantage as they can switch identities after the competition starts to achieve the best outcome. As someone who only registered as a crew member, I found the pilot role more interesting after the competition began but obviously, I could not switch, while those who registered both can easily do so. As for pretoro's claim of putting in double the effort by running two instances of RPC, doesn't a Sybil also put in double or more effort? Ultimately, this is a milder form of Sybil behavior (of course, this is just my personal opinion, and pretoro might disagree).

#

3.Regarding the issue of incorrect S class category submissions, I think the officials still need to be cautious in making corrections. I am not very familiar with whether IBC is a Shielded action or not, so I will not comment on that. However, I naively believe that a faucet cannot be categorized as a Shielded Application. If the officials think it is also a Shielded Application, then I earnestly request that everyone be allowed to change their S class submission category again. I noticed that several faucets in the table have been categorized under Building Namada Ecosystem Integrations and Tooling, but if they were categorized under Building Shielded Applications, the scores would increase significantly (because there are very few submissions under Building Shielded Applications, so the scores are higher). My estimate is that this could easily place one in the top fifty of the crew, and I think pilots would be similar.

austere rose
#

I am reiterating that the official blog and the team has confirmed that one can compete both as pilot and crew. Changing rules at the end of expedition after SE is over is not fair to anyone, who submitted tasks fairly in both category. And hence both submissions should be allowed.

eager ibex
austere rose
#

I have personally spent hours hunting for bugs and completing S class tasks in both categories, and I am really tired defending that once the rules were clear it’s confirmed it shouldn’t be changed

#

I don’t know how else to put it.

eager ibex
austere rose
#

We were pursuing this according to this confirmation and we also didn’t hide our identity, and it was public knowledge that folks were competing in both

eager ibex
austere rose
#

@fringe pawn has also shown evidences in chat where team confirmd multiple times that it is allowed

eager ibex
# austere rose The official announcement made by Gavin just exactly states that he checked with...

@eager ibex fyi #πŸ“£-se-announcements message

i also have not found the issue sufficiently clarified, regarding one playing as both Pilot and Crew. also i think it's pretty lame to find this out after registration ends. but my understanding is that one player can play as a Pilot while also playing as a Crew Member. we have also put it here to make extra sure with the Anoma Foundation: https://hackmd.io/@gaving/SkfYu80a6

eager ibex
austere rose
eager ibex
# austere rose Distort the truth?

" but continued unproductive, heated/frustrated/exasperated back-and-forths between one another--not cool 😎
this is the organizing team's responsibility (and fault), don't direct your frustration at each other"I think you can take a good look at this sentence.

austere rose
#

Independent Bug submissions, protocol improvements and protocols building has definitely made the protocol stronger. So it was helped the SE with fair submissions. This needs to be taken into consideration.

eager ibex
eager ibex
austere rose
#

It think it makes it clear. But anyway, it’s going in circles. I am not sure how else to put it. Anyway, I will let the team decide

potent bronze
# woven gull There are many accepted works that essentially have no *shielded action*. Exampl...

after speaking with Spork, this is my understanding

context
while we see no specific reference to "shielded actions" in the "building shielded applications" subclass in the blog post https://namada.net/blog/namada-shielded-expedition-wanted-asteroids-roids-point-system-and-rankings, it's probably reasonable to draw this conclusion from the examples provided.

there appeared to be no path for participants to create an application with shielded actions until the SDK was complete. this wasn't apparent until after participants had invested considerable time and effort and finally hit a wall. so the people developing their apps tried working around this limitation in various ways, which led to Spork establishing criteria (since we had no criteria provided to us at the outset)

Spork's criteria
the threshold for being considered a "shielded application" is that it either sends an asset over IBC to a znam address, or vice versa. then to qualify, it's case by case eg. work added to improve the UI, such as a web app or GUI or wallet features like key management

your question
does that mean I can ask spork to move my faucet from the Bulding namada ecosystem category to the Building Shielded Applications category? feel free to demo and share your code with Spork for consideration

potent bronze
potent bronze
potent bronze
gaunt gull
potent bronze
potent bronze
gaunt gull
#

we still can use the sdk via CLI

potent bronze
potent bronze
pine agate
#

The truth is we've already done it, and it's been operational, as that was Namada's requirement from the outset.

#

But in the final week, the requirements changed; the team lowered the mission criteria.

#

And if building an app without the need for the SDK is straightforward, then it would have been easier to accomplish, but prior to that, we spent over a month completing it.

potent bronze
#

were the requirements detailed somewhere before Spork provided clarification?

dry heart
potent bronze
potent bronze
willow ivy
potent bronze
pine agate
#

Okay! well done. Thank you

#

Thanks, @potent bronze , if you put it that way. Because we only researched and executed according to the project's documentation on the mission concept. If we had known beforehand that we could do it differently, we wouldn't have spent so much time on it.

#

Have a great weekend! everyone πŸ’ͺ

potent bronze
narrow fable
# potent bronze the other categories criteria already had a review, these are the final two prev...

Thank you for getting back to me. I understand the decision, although I don't fully agree, as I believe everyone worked with the information available at the time. If the information changes, strategies change as well. In my case, if we had known during the testnet phase that there would be new conditions to consider, we would have focused on finding something more complex that fit the new requirements. Unfortunately, that's no longer possible since the testnet has already been finalized. I hope the team can understand my point of view.

scenic sun
potent bronze
willow ivy
#

RPC endpoints is a good example. There was an announcement before SE ended about new approval criteria. And it gave time for participants to re-submit

potent bronze
potent bronze
hallow echo
#

I don't believe that an application that does not support any shielded action should be called a shielded application 🀣

potent bronze
potent bronze
#

and we didn't realize this until the contest ended, after the on-chain submissions had been completed

willow ivy
sudden burrow
#

to be honest, without offence to anyone, all "you didn't give us time" is the same as "let's allow ppl to submit till the mainnet", it will give some smart ppl the time to learn more and write smth from scratch

unfortunately, in any business there are deadlines, and if you missed them just because you understood the requirements wrongly it is only your fault that you didn't ask before to clarify them

and someone did it better, so an end customer selects your opponent πŸ€“

potent bronze
#

i'm trying to think about how to articulate this

willow ivy
potent bronze
#

this thread is for clarification on our decisions

sudden burrow
# willow ivy It's not about deadlines. We followed deadline - which is an ending of SE. It's ...

it is like you have a very uncertain customer πŸ˜„ and once you did smth he decided he wants a different thing, and you can't do anything, this is his right

just a suspicion from my side, once we all got a list of tasks almost no one clarified with the team what exactly should be done, most people just did something based on their understanding

for sure, if it was clarified and approved, then better to don't change related stuff

narrow fable
# potent bronze i totally understand we did consider this. this is bad, but it's the "less bad" ...

The team is considering a decision that may benefit some members, but I feel that this may not be the best decision for the group as a whole. I request that you consider the full impact of the decision on all involved, as I feel that some will be disadvantaged or unjustly treated.

Therefore, I believe the team should reflect more deeply on the potential effects of this decision and consider alternatives that promote equity.

sudden burrow
crisp tree
#

Please wrap it up my people. these disagreements wouldn't end even in two years. So please publish result already or update C and A class

potent bronze
potent bronze
gaunt gull
#

Hello Gavin, can we end the debate today? I just want to see the final result in next three days. We have a lot of works for mainnet stages. Please focus on the timeline. Too many people think we are not live 😦

fringe pawn
potent bronze
#

it still needs to be answered

fringe pawn
potent bronze
#

@willow ivy i need to get back to on this, i have a call

willow ivy
potent bronze
potent bronze
scenic sun
#

The team can't satisfy everyone, but they can choose to satisfy the majority.πŸ˜€

fair patio
#

I wasn't following along, but we're not changing already submitted and approved tasks right? Seems like we're having concerns about this now?

We already kinda discussed this many times during the competition and it was a big no-no then. Is it becoming a maybe-maybe/yes-yes now post-competition?
If so, I have to stand behind @willow ivy for this one. Back then we had the time to up the requirements for tasks, but now it leaves no room for anyone to adapt anymore.

For instance:

  • Some of us may have solved something fitting a category like 'protocol improvements', but didn't bother submitting it as an S-Class for already being eligible due to a previously submitted one.
  • Those who already had an approval stopped looking all too intensely for more fitting that category.
  • Even the submissions that were very clear to not fit the category can't be changed around now imo. Especially those who have been approved way back.
fringe pawn
#

maybe I shouldn't say more and I won't say much, but it's highly demotivating to be in a discussion where factual items posted (see above) that have been asked for by other participants, are pretty much ignored and the same assertions that have been put forward for days just keep being put forward (in all different channels and formats unrestricted). I hope my submissions of factual evidence above don't get lost in the stream, and hope anyone interested in the issue will take their time to go through it. (I also feel like there's a big portion of opportunism at play here and that really is dismaying)

willow ivy
fair patio
#

Ah, hmm, alright.

#

It's in the end in the hands of the team ofcourse.

willow ivy
#

Team is only considering now how to present it to the community. At least from my understanding

sudden burrow
fair patio
#

Though I do think it's important for people to express this.

#

Since I remember having heard many times that we can't just undo an already approved task.

fringe pawn
fair patio
#

Ah yes, I'll await the announcements we'll eventually get hehe

fair patio
stiff adder
#

Just curious Gavin about your comment 'we're auditing two categories, "security vulnerabilities" and "protocol improvements"', I understand that these two categories were being evaluated only by Heliax since the beginning of the SE. This new auditing mentioned is also being done by the same Heliax evaluators or do you mean some external auditing firm/evaluators?

austere rose
fair patio
austere rose
#

I think that was the point of this new entry column right

narrow fable
dry heart
#

I don't see Spork saying the last sheet is the final result. It says WIP, so that means the team can correct the bad things that they do not see during SE. Let's team work on it

left rover
#

I think we should change some of "already approved" submissions like copy-paste ones and low threshold ones.
On the one hand, even if the indexer, RPC, and IBC are removed, there are still over a thousand submissions. It is understandable that the team is understaffed and cannot complete them in a timely manner. On the other hand, I believe the team has the authority and should remove those submissions that are obviously plagiarized, cloned or of low quality.

eager ibex
woven gull
#

It looks like everything has already been decided:

  1. 2 categories will be revised ( not fair )
  2. Shielded applications are not subject to review if they have already been accepted
  3. It was possible to participate as a pilot and as a crew at the same time

Maybe we should end the debate, otherwise this can continue forever πŸ₯²

crisp tree
low token
potent bronze
# fair patio I wasn't following along, but we're not changing already submitted and approved ...

i agree with everything you've written, and we considered each of these before deciding to review and audit. we know that it's bad to do this, but i think we'll do it anyway, because the alternative is worse

the alternative: what are the implications of leaving the "protocol improvements" category as a catch-all bucket?

with the current evaluation, there's no defining characteristic, other than maybe "it seems to be helpful and doesn't fit in another category." i think this effectively makes the "protocol improvements" category unbounded, which calls into question all kinds of other submissions that should potentially qualify, and no way to qualify them

cc @willow ivy

fair patio
potent bronze
potent bronze
#

also i will review what's been written here and provide a summary for comment before announcing it

fair patio
#

I do still favor to rectify these things outside of SE (like adding it to the potential plan to reward those who did outstanding things).

potent bronze
#

yes, there's what we can do within the game, and what we can do outside of the game (that hopefully helps on the "prioritizing contributors" and also the "cosmic justice" front)
#1230547749603377273 message

gaunt gull
fair patio
#

But yes! Will await teams decision :)!

I will go go go off now!

#

Goood luck!

fair patio
fringe pawn
#

if I understand you correctly

fair patio
#

No, like:

What if we have someone who has the two tasks done that are being reviewed again. Person already has an approval for two months.

Now it appears one of his tasks didn't necessarily fit due to the criteria.

Give this person a NAM penalty instead of completely refusing his/her submission.

And I'm here talking bout a somewhat okay submission, not e.g. a single line fix.

@fringe pawn

#

Now we 1. don't punish super harsh/unfairly at the end of SE. 2. The person somewhat does pay the price. 3. We create a buffer to give to others.

fringe pawn
fair patio
fair patio
#

Perhaps ROIDs is possible as well, but then we get a kind of 'weighted' task approval approach.

fringe pawn
# fair patio No I actually mean NAM.

I don't think that's possible calculation-wise. It will trickle down and mess with all placings. If you mean roid it's doable though I lean towards it being a bad idea. but doing it with NAM I don't see how that would work at all

fair patio
fringe pawn
fair patio
#

I'm not talking bout placement btw. Eventually placement doesn't matter.

fringe pawn
#

rank is first, rank is what should be adjusted, NAM follows rank

#

if you want to impose penalties, freezing rank doesn't make any sense imo

#

ultimately I think such a scheme would be too complicated anyways, but it definitely needs to be roid-based if done

#

anyways I'm off for the weekend in a sec, but just wanted to get this in there. I think if you do some example-calculations, you will see how it becomes tricky..

fair patio
#

I bet it's far simpler and less hard of a punishment. Though I understand that this would make it less of an opportunity for those who didn't get these tasks.

fringe pawn
#

it would exactly be less of a punishment. to the point where it may be better to not change it at all. (and also would be a punishment to those ranking lower...)

#

but anyways I'm not strongly in favor of or opposed to the revision scheme , but I do feel strongly we should be careful making too complicated amendments or changing the entire structure of scoring, which is what this is suggesting I think

fair patio
#

This is exactly the same as the crew pilot debate btw.

You went with what you thought to be okay up till now right? That's the same for those who got something approved.

This is the exact same sensation we are now getting as an experience. It's funny that you're the one so against this now.

fringe pawn
#

btw Zen, I want you to have all roid in the world, I think your apps are absolutely stellar, so this is not about your contributions

fair patio
#

But okay, let's stop this. Cause I sense we have emotions boiling up lol.

#

We're big pals πŸ˜‚.

fringe pawn
crisp tree
#

Please let's move with the result we have . If at the end I don't receive NAM or enough nam I'll beg @fringe pawn @gaunt gull or @fair patio to give me small NAM

fringe pawn
fair patio
#

If I sent something in and I got an approval, my reality shifts towards one where I'm not obligated to send in this task anymore. Mine shifted even towards: I'm not going to spam or bug examinators with extra submissions I already got an approval for.

So in a sense, now hearing that there's a change for a rejection is like hearing: hey we said it was okay to play as pilot and crew, but meh now we are going to reconsider. It's similar in the sense of: you were given the idea that you are moving in alignment with the team, but now appears not so much.

#

Sorry had to clarify my comparison with the other "prob/issue"

fringe pawn
#

I'm available in dms if you want to discuss further

fair patio
#

Haha yes, just a sec. Need to read.

fair patio
rapid sparrow
#

Aware of all the discussion above,
But still most of the players have stop to submit / find solution as in (hard to find such potential solution) specially on building protocol and security vulnerability as it has been accepted (yes) .

But still align to what decision to be made further if it's to be made fair and on a good justice for everyone.

In my opinion this debate has been going on and it's not gonna end well if a proper direction is not made soon.

It's better to focus on the interim timelines, and get ready for several phase of mainnet.

I want to see the results and final settlement by the end of April at least!

Instead of taking issue and unclear rules bits by bits, it's better to take them as whole as one agenda and a proper direction to be taken as soon as possible.

#

It's like going on an on. Everytime I come here on chats it's all about unclear rules and regulations.

So clearly my sincere request to team and foundation handling the situation to make it fair and clean the messed up with fair justice and as soon as possible. We can't be debating all over this, and clearly it's not our decision that needs to taken beforehand, now it's clearly Going out of control.

When there's one head/ solution that can be addressed by who has control over this.

Thank you.

fringe pawn
#

100% agree with jojoraky. Off for weekend now.

rapid sparrow
#

Take care man! Same here. Have a good weekend

fringe pawn
#

you too!

fair patio
#

A good weekend to the both of you :)! ❀️

potent bronze
#

@here this is the criteria we intend to use for "Building protocol and cryptography improvements"
yes, it's bad to do this retroactively after end of competition, but otherwise pls let me know if there's anything particularly flawed

For a submission to be considered as "Building protocol and cryptography improvements," it should a) address something in the Namada specs (ie. core protocol), and to qualify b) it must be a reasonably useful improvement/solution that's been demonstrated practically or mathematically. The submission should be specific to Namada and a new, useful solution, not something already described somewhere like GitHub.

Protocol performance improvements, for example, should be more than just descriptive. They should either

  • mathematically prove a theoretical performance enhancement
  • demonstrate and measure an implemented performance enhancement
#

For "Finding security vulnerabilities" submissions to be considered, they must actually be reports of security vulnerabilities.

Security vulnerabilities specifically compromise the confidentiality, integrity, or availability of the system and its data (not a specific user), potentially leading to unauthorized access, data theft, or service disruption. They pose direct risks to the security posture of the system.

supple prawn
supple prawn
# potent bronze we have https://discord.com/channels/833618405537218590/1230547749603377273/1230...

The "Building protocol" category is also not explained in detail in the blog post, which means that any contribution can be considered in this category. The message you just shared consists of comments to increase the acceptance threshold and is completely not in the blog post

If there are people in this category who have made real cryptographic improvements, I fully support them getting the recognition they deserve. But if you can do this kind of retrospective re-evaluation for this category, you should be able to do it for the category of building shielded apps

stiff adder
#

Hey @supple prawn there have been ongoing discussions for a long time and the consensus is to respect what it has been decided by the team evaluating rather than continue repeating and insisting about topics extensively discussed before and already decided

spring glade
fair patio
#

It should never have said: "Examples" in the column next to the subclass names. This is probably where most confusion was to what is and isn't a decent entry.

Or a separate column describing the categories in detail.

#

"Building protocol improvements" and "Building cryptography improvements"

It's ambiguous.

potent bronze
dry flicker
# potent bronze @here this is the criteria we intend to use for "Building protocol and cryptogra...

There is nonetheless an unintended consequence of this :
Basically you are stripping a lot of ROIDs from most of the players who were the most hard at work and try to climb the ladder as best they could.
By doing that, it over weighs another bugged task : everything related to uptime.
On the current state, most shield-100 will get a lot of points from these tasks that other pilots couldn't achieve because of unjail and such.
By removing those S class, you're removing one of the few edges we had to compete with an initially skewed leaderboard

potent bronze
dry flicker
#

(sorry for being so blunt, long day, lost of frustrations)

potent bronze
potent bronze
potent bronze
fair patio
#

Why isn't there like a meet in the middle approach? Since it's not entirely our fault that we're here now.

Many of us would've adapted to the criteria if we knew of this mid competition. I personally would've shifted my focus for instance more on a github issue I made about optimizing MASP that wasn't good enough for lacking a bit more specific elaboration.

narrow fable
supple prawn
potent bronze
dry flicker
supple prawn
dry flicker
#

But I want the rewards to be paid in CHEESE, not NAM. that way, we get to eat our own winnings "cheese naan" 🀣

Ok... I'm officially losing it. Help me @fair patio

fair patio
# potent bronze wdym, meet in the middle?

Like for instance take a weighted or penalty approach, not entirely declining those who thought to have finished the task.

  • For instance those who match the criteria exactly get more of a weight in the pool, or
  • subtract an amount of ROIDs (or NAM) if you were in the category but didn't exactly match the criteria we are given now.

And perhaps only completely remove (still quite unfair imo) for those who truly didn't contribute anything valuable in the category.

supple prawn
supple prawn
fair patio
#

rm -rf, the person who first dropped that joke made me laugh so hard btw πŸ˜‚

#

Ah it was hades, the devil himself

dry flicker
fair patio
#

If it's not too much work ofcourse.

#

I dunno what's eventually best for all parties involved.

#

Just give all 100 winners equal amount of NAM, fuck it XD!

stark lodge
#

Please I thought everything is already settle. Close this thread do the final review. 22nd is here already I don't want to wait for final result beyond that

fair patio
#

These scenarios are kinda what are the most 'sucky':

  • You had more submissions you could have sent, but you didn't cause you didn't wanna spam examinators and you already had an approval.
  • You were on your way for a submission that could've been approved (for the current criteria), but worked on something else that did get approved (but doesn't meet the criteria now).
#

Apologies for talking too much. I'ma calm myself now πŸ˜‚.

#

πŸ§€

#

Random story: there was actually a mouse in my room a week ago. I'm on the second floor. I HAVE NO CLUE HOW. It was a baby mouse, like super tiny.

#

Actually cute, but his random fast movements were making me panicky af πŸ˜‚.

potent bronze
#

okay so there are two last things to deal with, regarding S Class evaluation updates

1. shielded app
can a jointly-created app be submitted by two different individuals, with each receiving full points? we think yes

There were two pairs of open collaborators. Each pair was advised by evaluators that they could submit their jointly-created app individually, which we will uphold.

Reasoning:

  1. the criteria was so uncertain that participants depended upon evaluators for guidance AND
  2. there's a credible reason to think that the two pair of collaborators would have submitted sufficiently different apps otherwise

Counterpoint:
if there's a credible reason to think that people would have done something different otherwise, why doesn't this reasoning apply to the "security vulnerability" and "building protocol.." audits?

Answer: #1230547749603377273 message

#

2. Sybils
Sybils won't be dealt with in this thread, but if we can collect some compelling evidence on the most egregious of Sybil clusters, we would like to propose banning them

this is dicey territory, because we want to be confident that we don't have a false positive

green fable
#

🀐

dry flicker
#

You forgot about uptime Gavin !

potent bronze
#

y'all too tired to throw rocks at me? πŸ™ˆ

potent bronze
fair patio
#

Stoneeeeeeeee

#

πŸͺ¨

dry flicker
#

Probably better to pick a helmet than hide behind your hands if we throw stones πŸ˜…

potent bronze
#

now i have to go through this entire thread and put it in a doc and post it, because people who missed this thread will (quite reasonably) have the same questions/concerns that we have discussed here

fair patio
#

πŸ˜‚...

#

No, but jokes aside. This feels like you don't have much control on the situation either and probably hurts you as well having to drop these types of news on us :(..

#

Or Gavin turned demon mode πŸ‘Ώ

#

The tough teacher!

#

Good luck Gav

stark lodge
fair patio
#

If you need help, though I may be too biased right now, just tell!

crisp tree
sudden burrow
austere rose
#

How much additional time are we looking at adding to re-review tasks?

#

Weeks/days or more?

potent bronze
potent bronze
fair patio
potent bronze
#

this is what's left to finalize S Class:

  • a bit of s class data to clean up
  • ~~ a few evals waiting to be checked by eng team~~
  • ~~ likely a bunch of security vulnerability emails backlogged (haven't had access to the emails for the last 10 days, but should get these Monday when person in charge returns)~~
  • ideally do what's needed to be confident banning a Sybil cluster or two

i think this is the rest:

  • final back-end scoring data (wen??) from eng team (seems like they are finally close)
  • check on up-time tracking (is it actually accurate?)
  • make proposal for dealing with up-time / NAAN asymmetry dilemma
  • make proposal to recognize high quality submissions, bounties, and others
  • finalize scores, announce & publish results

anything i'm missing?

edit: proposal to consider implications of expanding winner set

#

oh yeah and announce/publish summary of this thread

#

we've got some exciting Namada stuff we wanna focus on, haha
will be good to have the SE finished at last

eager ibex
#

Of course, I think that rewards should also be given to those who only set up IBC and RPC, even though their scores might not be very high, but they are still people who put in effort. Although they may not look excellent in terms of competition scores, they have indeed participated in community activities and have given their all.

prisma meteor
#

finally who's win? πŸ˜„

azure badger
#

@potent bronze Will be happy to share feedback on the Shielded Expedition structure and incentive model in one of the validator/community calls. There is opportunity to learn, and will keep it constructive. Look forward to speaking with team and suspect other validators will also have valuable input 🫑

left rover
#

Reward for people who will be affected by rules changing(but not low quality ones)? Agree. Reward for IBC and RPC or Indexer runners? Don't agree. They are not affected by anything. Unless Team would like to change the whole reward schema.

crisp tree
low token
eager ibex
crisp tree
dry heart
#

what? the team gonna change the reward schema?

crisp tree
stiff adder
# potent bronze this is what's left to finalize S Class: - a bit of s class data to clean up - ~...

Hey @potent bronze thanks for the overview, I think the timeline is missing? Also, people complaint a lot already about changing the rules of the game after the game has ended. And still some rules like uptime and others are still planned to be changed as well? Furthermore, the auditing of vulnerabilities and improvements tasks will have a huge impact in the SE. Basically if just around 5 tasks are approved in these two categories that will be the top 5, ie. the top 5 decided by changing the rules of the game after the game has ended, while we were competing for almost 2.5 monthsπŸ€¦β€β™‚οΈ Maybe we should have been informed that the rules of the SE were shielded and only unshielded after the end of the SE

dry heart
crisp tree
dry heart
crisp tree
frail nova
stiff adder
#

There is also another unclear category @potent bronze, the C V2 says 'Start your validator as quickly as possible after the upgrade height', if 'as quickly as possible' means the first block signed (block 237909 https://namada.valopers.com/blocks/237909) then the ROIDs should be given to the validators who signed that first block 237909, this should be clarified as well

prisma meteor
#

When end?

frail nova
covert garden
covert garden
stiff adder
covert garden
dry heart
#

We always miss deadlines πŸ˜‚

fair patio
# potent bronze @here this is the criteria we intend to use for "Building protocol and cryptogra...

Hey, a question cause I'm not sure if I have a complete image of the current situation:
Will we also take the ambiguity of the category name in account?

Like, "Building protocol and cryptography improvements" could be read as "Building protocol improvements" and "Building cryptography improvements".

For instance is it possible for a PR that has nothing to do with cryptography, but pointed out and fixed a flaw in the workings of a part of the namada protocol to remain accepted? Or are all of these non cryptographic submissions/bugfixes/optimizations, big and small, off the table?

stiff adder
# fair patio Hey, a question cause I'm not sure if I have a complete image of the current sit...

I heard from Gavin before here in the chat and in the last call that probably nobody will qualify for "protocol improvements" because 'that's a pretty insanely hard bar to clear if you see the examples in the blog post pic'. Regarding security vulnerabilities, I assume it would be similar because we didn't see any submission of a very serious vulnerability and much better than other previously approved submissions, hence no vulnerability submission will likely be approved, otherwise all vulnerability submissions of a similar level should be approved

rapid sparrow
# potent bronze i get what you're saying, and we're close to finishing this but it really affect...

I don't feel like it's competition anymore.

It's just feel like amending and fixing constitution

We need bold and responsible leader. And I'm not saying under your / team leadership there's flaw and not doing any part of it.

But please take bold decision and acceptable reasoning.

Sorry for being like this, but I have to say this and speak up.

Least thing that could be done as of now, is please come up with the finalize decision so we don't have to discuss about this.

No wonder I totally believe on transparency and justice that will be made.

rare skiff
#

Narrator: "Little did we know that the end of SE at epoch 91, wasn't really the end but a start of something far greater."

rapid sparrow
#

Also, there's limit and everything.

I don't understand why we need to expand winner set, just because some people say. I agree the sentiment and interest of general public. But if this keeps on going. I don't see where it will end.

What will they asked next? That's a very big question.

Sybil, duplicate submission, copying someone work that's something of better discussion than, bending new rules just because we want to make it fair,

#

If it's for the goodness and a valid reason still agree :))

Just don't want to see, complying every new rules that has been unclear since, maybe that's the biggest reason.

fair patio
# stiff adder I heard from Gavin before here in the chat and in the last call that probably no...

Makes no sense really to make a big deal out of it then, right?
If there's zero, then removing the categories in their entirety would be all the same.

Then I got a feeling this is being done to reward one or two who had exceptional entries, if that's the case. Also possibly to prep for post expedition media publishment and showcase some.

I just feel like, if these are the reasons, we're now placing the punishment in its entirety in our shoes...for something we are not to blame of. I remember asking right at the start of the competition how quality will be taken in account. Kept being said that eligibility is based on whether the person examining it is convinced. Now, instead of taking the bullet together, we're now having to take it.

But ah well, I just hope it's not a case where e.g. chat gpt entries have more chance of being accepted than actual implementations. Just try giving gpt a problem and some data on possible optimizations and it will bless ya with algorithms and so much more πŸ˜‚.

gaunt gull
#

The worst thing is that we went through a competition that had no specific criteria, now everything feels like starting over again.

rapid sparrow
#

Yeah,

fair patio
#

Really think awarding these separately outside of SE would keep everyone happy.

#

Think we are also at such a point where people who land high and see other people's work, would be willing to contribute a portion of their NAM to these people who made extraordinary things.

gaunt gull
#

If from the beginning we have specific criteria for each category, I submit the submission, and if it does not meet the requirements. I still have time to make it better or search in another direction. But now the SE has ended, we can only wait for the results without being able to fix it

fair patio
#

I dread the outcome where we lose key players from the community.

stiff adder
# fair patio Makes no sense really to make a big deal out of it then, right? If there's zero,...

So you think rather than approving zero protocol improvements and vulnerabilities, they will cherry pick one or two in each category and these will be the SE winners? But have you seen any exceptional entries in these 2 categories far better than all the rest? All the submissions are on the excel and I discussed with several people and nobody thinks there is some particularly exceptional submission. Unless there are some we still don't know about and only the evaluating team received the info by email (but I guess it would be on github anyway). It seems unlikely that in 2.5 months no exceptional submission and in the last minute a few of them that we don't know about

fair patio
#

I have to say though. This is all just speculation. It may not be this harsh. The mind tends to make things worse lol.

But if it gets upped big time, then the reason isn't just to filter out the few submissions that really didn't fit the category. That's for sure.

stiff adder
fair patio
#

Yeah...I just hope we're super wrong and overthinking took the best of me πŸ˜….

gaunt gull
#

πŸ™

fair patio
gaunt gull
narrow fable
# potent bronze this is what's left to finalize S Class: - a bit of s class data to clean up - ~...

Gavin, from the beginning, we've been working with the criteria we had, and I understand that over the course of almost 2.5 months, there have been several adjustments to the defined criteria. However, from the start, everyone without exception knew that only the top 100 for pilot and crew would qualify for rewards, and now we're simply ignoring the only criterion that has been clear since the beginning of the competition. Frankly, I don't understand.

Another concern is that by adding more slots for winners, how can we be sure we're not just allowing a single entity or individual to receive rewards for having more than a thousand accounts? I know it hasn't been easy to find a way to please everyone, but these changes after the end of the testnet have been regrettable.

Additionally, I noticed a lot of email activity about vulnerabilities and improvements that have not yet been evaluated. Ideally, it should be public so that everyone can know what it is about.

fair patio
waxen geode
low token
low token
gaunt gull
crisp tree
drowsy ember
narrow fable
# crisp tree I don't see any problem with expanding the winner set. We all worked with top 10...

The issue I see in this cycle of discussion is that we only express what suits us. It has been said so much that the rules were not clear, and the only one that is well explicit is simply torn apart. Just trying to understand...
Hard work alone doesn't guarantee anything. If everyone worked equally hard, but you still didn't reach that position, it might be a sign that something was missing.

crisp tree
# narrow fable The issue I see in this cycle of discussion is that we only express what suits u...

Somehow we all knew it consciously that some rules are just going to be amended or adjusted along the way. We did not just know the rules until the team saw it and deem it necessary. Somehow I'm confident in finishing top 100. But some rules were changed few days to SE end or after the end date. And it affected many people I'm not even in that category but if the team wants to accommodate them cool

fair patio
crisp tree
fair patio
#

I do try to give my opinion whenever I feel like something isn't conducted fairly though. But hard at times cause there are usually sacrifices to be made. But even then, the sacrifices should be kept at minimum if possible. Like what's the best outcome for most parties involved.

crisp tree
fair patio
#

Holy shit that scrolled a long ride up

crisp tree
narrow fable
#

The big problem I see is that there are already entities and institutions participating as Pilot and Crew. If we open more slots, won't we be creating room for more problems like these? Or is it not an issue because the rules allow it? I'm in favor of more opportunities, as long as they are for those who really didn't have the chance to be selected.

sudden burrow
#

Cmon, you started again…. πŸ₯΄

crisp tree
narrow fable
# sudden burrow Cmon, you started again…. πŸ₯΄

Sorry about that, I'll keep quiet now. I only expressed my opinion because I didn't agree with one of the topics Gavin suggested. But since people started ping me in the channel, I had to share my point of view. Anyway, I've said what I needed to say. I apologize if I offended anyone in any way. I wish everyone a great day.

fringe pawn
#

I see there is a lot to catch up on...

fringe pawn
fringe pawn
fringe pawn
fringe pawn
fringe pawn
fringe pawn
# stiff adder Hey <@294676197823217674> thanks for the overview, I think the timeline is missi...

uptime is a big issue because 1. currently it's not tracked at all for post genesis (uptime = zero) and 2. there was a persistent jailing bug that meant you couldn't unjail for many epochs if you got jailed for whatever reason... so something does need adjusting wrt both those points imo. that's not a matter of changing the rules after the fact, so much as adjusting to unforeseen circumstances during the testnet.

fringe pawn
fringe pawn
crisp tree
fringe pawn
fringe pawn
fringe pawn
fringe pawn
crisp tree
#

Yoooooooooooooooooooo I thought SE ended over 1 week now. Let's get this over with can we?.

crisp tree
fringe pawn
stiff adder
# fringe pawn uptime is a big issue because 1. currently it's not tracked at all for post gene...

Well, getting into the SE-100 was already part of the competition right? Everyone applied and 100 were selected based on the applications so it is normal and absolutely fair that there is some advantage/reward for having been selected amongst all the thousands of applications. Secondly, getting jailed or not is also part of the competition, maybe it wasn't possible to unjail for longer but this was because there was a jailing event in the first place, those who were not jailed didn't have that issue, so yes, it is normal that those who were never jailed and kept perfect uptime are rewarded for these efforts. The possibility of getting jailed or not being selected in the SE-100 are not 'unforeseen' circumstances during the testnet but obvious and clear parts of the SE

crisp tree
fringe pawn
fringe pawn
crisp tree
fringe pawn
crisp tree
dry flicker
stiff adder
# dry flicker Please just don't start diminishing others work or skills. Your message is so w...

Please don't suggest I said something which I didn't thanks. The selection of the SE-100 was done by the Namada team so if you have concerns about this you could have let them know, I just reminded about the applications and competitive selection process for the SE-100 to justify that those selected deserve of course some advantages over those not selected, I didn't mention anything about work or skills. No need to discuss in DM, you can present your arguments here to discuss. Validators who managed to never be jailed in the whole SE for almost 2.5 months and kept an almost 100% uptime despite the innumerable halts by working super hard, staying awake many nights for all the upgrades and so on, should be rewarded for this? Yes.

low token
livid niche
#

I don’t understand the debate about uptime. If a validator went to jail, he had already made a mistake, which means even with unjail work he had no chance of getting 99% uptime.

#

If, for example, only 1-2 people were to complete a task of class S, would it be cancelled? No. Then why should the uptime task be reconsidered? (By the way, a sufficient number of people have managed to maintain a high level of uptime.)

fringe pawn
fringe pawn
#

current state is almost all postgen have zero uptime because (I assume) team has been unable to establish a link between our participant pubkey and our validator. So atm (except for 1-2 edge cases we don't really know why) only genesis can get any uptime in scoring.

#

(also I assume this is because memo field is not properly preserved for the right tx types. again some of us are working to provide a map and are close to done. that will at least make it possible for team to calculate some rudimentary uptime based on signed blocks also for postgen.)

#

as for the jail issue, yes that does make a real difference but is less egregious than the issue sketched above..

fringe pawn
sudden burrow
fringe pawn
#

(jkjk)

sudden burrow
#

What about those shielded-100 who asks how to run the easiest command? Will not comment

#

So, all my three comments are just to show

Let’s end this discussion!!!

eager ibex
#

Indeed, increasing the number of award slots is a fair action. We shouldn't punish those who, due to unclear competition rules, didn't make it into the top 100. Many competition rules are not perfectly set, so there's a significant element of chance in who makes it into the top 100. For example, if I had known that creating a Shielded application only required an IBC transfer to a ZNAM address, I would have done so without hesitation. If I had known that one could register as both pilot and crew, I would have registered for both at the start. If I knew we could team up to complete S class and all receive the same score, I would definitely team up with friends to achieve more S class results (of course, these are all issues with the competition rules). Initially, rewarding only the top 100 was something everyone knew, but that was under the assumption of flawless rules. However, many people are currently missing out on the top 100 due to problems with the rules, and they too deserve to be rewarded.

dry flicker
# stiff adder Please don't suggest I said something which I didn't thanks. The selection of th...

You mean like :

  • having 10x more naan (or was it even 100x please confirm how much of a advantage/privilege this was) at the start of the competition
  • having specific C and B class that other pilots can't compete with
  • having a dedicated/privileged channel of discussion where you got the info about the restart early on, and that resulted in most of us being jailed (you forgot about this one @sudden burrow )
    There is "advantage" and there is "privilege", and in a competition, that do not result in a fair game.

I'm pretty sure that this has been mentioned before (by @potent bronze I think, but maybe I'm wrong) that being a shield-100 is more about "you have a responsibility to the network and the others" and less about "this gives you special rights".

Take a good look at pretoro screenshot...πŸ€“ Take a calculator and consider how much of an advantage, being a shield-100 has provided. In all the circles lined except the last maybe, being a shield-100 is either direct bonus points or bonus knowledge that leads to bonus points.
There you have some of my public arguments 🫑
I can understand a slight starter boost because you were "hand-picked by the team", but at that point, especially because S4 and S5 are being cancelled for everyone, these points mean an almost guaranteed spot in top 25. Is that fair? No

thin drum
dry heart
#

I feel like he is a sybil and most of his wallets are in the top 200 or 300 πŸ˜‚

eager ibex
#

Okay, quite interesting. Pointing out the issues with the competition rules and requesting to increase the reward range == sybil, pretty good. When there's no valid argument, personal attacks happen. In fact, you just don't want those of us affected by the competition rules to have a voice. Moreover, it's not just me who has pointed out the issues with the competition rules; in fact, Gavin also indicated that there are problems with the rules. Is he also a sybil then? Therefore, do not make baseless accusations. If there is any evidence to prove that I or someone else is a sybil, it can be directly submitted to the officials.

eager ibex
gaunt gull
eager ibex
#

In fact, I find that you seem to be avoiding the issue. The core point of the problems I mentioned above is not about begging for charity, but rather that due to the imperfections in the competition rules, some people who should have been in the top 100 did not make it, not because they weren't excellent. Therefore, expanding the award scope is not a form of charity, but a means to partially mitigate the consequences caused by the imperfect competition rules. I hope you do not intentionally misinterpret my meaning.

#

This is because these issues were not so apparent before the SE ended, and at that time, we were all busy completing various SE tasks. In fact, there were some debates at the time, just not as intense as they are now. You can check the chat logs in the other channels.

#

In fact, what's slowing down the progress now is not our debate, but because the database has become too large. Also, seeing the results, we all hope to see a fairer outcome.

rapid sparrow
#

Whatever not cool! Bye

dry heart
#

I don't think the database exceeds 1TB

scenic sun
#

Lol, everyone should stop making suggestions, because you never know if you will be accused of being a witch.

scenic sun
dry heart
#

dont see any position is opening to apply mate

stiff adder
# dry flicker You mean like : - having 10x more naan (or was it even 100x please confirm how ...

From the Namada blogspot (https://namada.net/blog/the-namada-shielded-expedition): '100 Pilots (validators) will be selected by the Anoma Foundation, Heliax, and Knowable as pre-genesis Pilots. The remaining validators who submitted a valid form will also receive NAAN at the Shielded ecosystem genesis block and can become validators post-genesis.'

-You question how many NAAN the Anoma Foundation/Heliax/Knowable gave to the selected 100 pilots compared to the not selected pilots. Well, they could have also decided to not allow not selected pilots and the competition only amongst the selected 100 pilots, so I guess feel lucky that they let everyone compete

-Again, if the Foundation/Heliax/Knowable created some tasks that only pre-genesis pilots can do this was their decision, again feel lucky that they created many other tasks that all non-selected pilots can do

-One more time, the Foundation/Heliax/Knowable created a dedicated SE-100 channel to coordinate the pre-launch and launch of the SE. But they also created other public and announcements channels, and sometimes information was shared earlier in the public announcements channel than in the SE-channel

-You might not like or agree about the decision of the Foundation/Heliax/Knowable but they created the SE and made the rules and decisions, it is not you who make the decisions. Their goal was not to make an β€˜equal’ game for all the pilots, it is clear they wanted to provide some advantages to the selected pilots, otherwise why make a selection right? And in fact they gave for the S category which all the pilots can do 375B roid the same as B + C categories together, and what will define the winners is the S category since for B and C each pool of points is shared amongst many pilots

-Also, you made a typo, the tasks that are being audited are s5 and s6. And no, I don’t think signing pre-genesis tx or similar guarantees a spot in the top 25, but it will be the hidden A tasks and S tasks mostly

livid niche
# fringe pawn let me draw you a map

Regarding your screenshot, many of the highlighted tasks could have been completed by everyone, including post-genesis validators. The tasks to "Initialize your validator post-genesis," "Become part of the validator set for at least one epoch," "Start your validator as quickly as possible after the upgrade height," "Keep average uptime of at least 95% across the Shielded Expedition" (there are post-genesis validators whose uptime exceeds 95%, and I believe the team will correct any display issues), and "Unidentified*" (which are also tasks for all) were all achievable.

quiet sluice
#

What is the team doing? It has been 10 days since the testnet was closed. Is it so difficult to make a decision?

dry flicker
#

OMG brilliant, thanks for your answer, now I don't even have to answer πŸ’ͺ
"Feel lucky that they let everyone compete and not just just the 100 pre genesis"
I'm just gonna ignore your message as this is so pretentious and condescending, I'm just gonna let it hang as is, instead of arguing with you as I wanted to do in my initial message

quiet sluice
#

You have so much discussion here, why not urge the team to make a final decision quickly?

dry flicker
#

@stiff adder with all my love 😘

quiet sluice
#

The final decision always lies with the team. This is not something that people involved in SE should worry about.

fringe pawn
#

regardless of actual uptime

livid niche
#

There is blockchain data from which you can get real validator uptime data. This is public

crisp tree
fringe pawn
fringe pawn
livid niche
fringe pawn
livid niche
# fringe pawn how?

By checking whether a validator signed a block, the blockchain contains this information, validator signed the block or not.

#

I also saw that some participants also checked uptime and posted the results.

fringe pawn
livid niche
#

Regarding the display issue, it's only a matter of time before the team corrects it. If it is not resolved, it can be contested with data from the blockchain if the validator was indeed signing blocks.

fringe pawn
dry heart
#

you are starting again 🀣

eager ibex
fringe pawn
fringe pawn
eager ibex
sudden burrow
#

unstoppable madness... πŸ‘»

green ember
#

I get the feeling some users insist on growing the number of winners may or may not have two or three more accounts between 100 and 200 ranking. based on the attitude they've been showing I dont really think they seek fair distribution, it seems more like self interest. If foundation want to increase the allocation for more winners (and it comes from treasury) then by all means would be happy to see that. I completely disagree with sharing top 100 useres to others. mostly because the amount of work,enery, cost of services . . . not really comparable

#

thats the only thing I would write regarding the situation and will wait for the resualt

eager ibex
# green ember I get the feeling some users insist on growing the number of winners may or may ...

Yes, of course I speak out for my own interests, but is there really a problem with that? And aren't you also speaking from your own interests when you stand there and say these things? There's no need to pretend to occupy the moral high ground to criticize others. Moreover, it is indeed due to issues with the competition rules that there is significant randomness among the top 100, unrelated to work, energy, or cost of services.

crisp tree
#

Just bring out result please

fringe pawn
low token
#

Maybe they're not giving it much attention or they don't have enough hands on it

fringe pawn
fringe pawn
dry heart
#

⏲️

low token
#

I don't think anybody persuaded them to do it. The team just decided to accommodate more people. That's not the first rule that was changed.

rapid sparrow
#

I don't see where that's coming from. But I have not seen a chat log that team propose for expanding winner set

low token
fair patio
#

Hey, actually ever since the beginning there were already potential plans to expand. Due to how many people were already not liking the small set allowed to win. They back then said they'd see how it would go and that they had like a reserve in place for this. This was in early validator circles.

So this idea of expanding is not even something new that came out of the blue post competition.

rapid sparrow
#

Well if that's the case it's okay.
Will it effect the existing prize pool or it will be allocated from elsewhere

fair patio
#

I know pros and cons to this. But every decision is having pros and cons.

And no, it shouldn't affect existing prize pool.

#

Atleast if they spoke of a reserve and are holding their word.

rapid sparrow
#

If that's it, I'm totally fine.

fair patio
#

Though mind you, this is also not sure. It was just back then an idea they gave.

#

Dunno if you remember how pissed everyone was πŸ˜‚. The community and all those bots raiding etc.

rapid sparrow
#

I know haha. It just pissed me off.

fair patio
#

They found the competition way too difficult + the set of winners way too low.

Response was to create the #πŸ«‚οΈ±se-community-support channel plus they said to us not to take the "only 100 or 200 will win" as the complete truth. Things could change.

But yes, that may just have been words to calm people down. So also take all this for a grain of salt.

In the end we'll have to agree to their decisions hehe. Just hope the decisions mitigate sacrifice as much as possible for all parties involved.

rapid sparrow
#

Yeah right. I'll just leave this with the team. No more comments.
Let the good things prevail.

fair patio
#

Have a good Sunday man!

rapid sparrow
#

You too :))

fair patio
gaunt gull
#

Have a nice Sunday guys. My popcorn is out. Come back later haha

gaunt gull
fair patio
cyan tusk
gaunt gull
fair patio
#

I am against...

#

War.

gaunt gull
#

turn off the screen

fair patio
#

❀️πŸ˜₯

gaunt gull
#

Hades was offline

fair patio
#

Bwhaha.

Hades is not here for the moment. He returned to the underworld to attend to his pet dog Cerberus.

#

But speak a message after this screaming soul and he'll get back to you momentarily.

prisma meteor
#

When remove all task S5 and S6. So i think we will have a lot of player get the same roids

fringe pawn
#

I am much in favor of this btw

#

as long as within the remits of an added pool

fair patio
fair patio
#

Or have I missed something here

fringe pawn
#

that was re the voices advocating a redistribution

#

I finished uptime!!!!

fringe pawn
fair patio
fringe pawn
fair patio
fringe pawn
fair patio
fringe pawn
#

but realized an obvious approach I missed while talking it over with him so all is good

fair patio
#

My day started, so don't need to sleep hehe.

fringe pawn
#

we are in complete agreement πŸ™‚

fair patio
#

I only see people speak of upping the slots, not about redistribution. Got a feeling this blank was getting filled without speaking directly bout it during the whole back and forth.

fringe pawn
#

all I am saying is I am in complete and enthusiastic favor of expanding the prize pool as long as it does not involve a redistribution (some in here have argued for the latter persistently). However I think if expanded it should be on an "active participants" basis only. (discord, not just chain)

fair patio
fair patio
#

Can't find a message either πŸ˜….

fringe pawn
fair patio
#

It overwhelms me

#

Now random friends asking me how it's going with the competition πŸ˜‚.

#

I DON'T KNOWWWW

#

Stop askinggg

#

Getting suspicious bout errthanggg

#

Nah I'm kidding. Tranquilo.

trim yarrow
fair patio
#

Thank you for having taken the time though dude

trim yarrow
#

It was a pleasure πŸ˜‰

frail nova
#

@potent bronze @slender wave In recent times, I've noticed proposals to eliminate tasks S5 and S6. In my opinion, let's stick to the rules and tasks of the competition as originally intended. Perhaps these proposals come from individuals who were unable to complete tasks S5 and S6, and they are trying to suggest their removal. In fact, some of us have contributed our source code PRs by completing task S5 and S6. It's effortful and takes a lot of time.

fair patio
# trim yarrow It was a pleasure πŸ˜‰

Really appreciated!

And for sure @fringe pawn base was already almost there if I understood it correctly. Just had this one problem with the tm addresses. Sometimes it just takes a bit of extra time, experimenting around and sharing thoughts.

I at times get epiphanies after just a single question someone asks lol.

woven gull
fringe pawn
fair patio
#

Or perhaps better to say. What's considered a right or wrong move is changed due to the opponent going back in time and changing their pieces around.

low token
fringe pawn
fathom hawk
#

@potent bronze is Uptime in Nebb still being calculated even after SE ends? I see my uptime dropped to 98.8% becuase After SE ends I did some tests which may effect my uptime ( not 99% ) Also I might stop my validator today .Can you please confirm this Thanks

fringe pawn
stiff adder
# fathom hawk <@294676197823217674> is Uptime in Nebb still being calculated even after SE end...

@sterile thorn released before the uptime file (https://github.com/nodiums/namada_se_uptime/tree/main), with the number of total blocks signed in the SE including for post-genesis pilots. The highest number of blocks signed is around 237k and this is close to 100% uptime, ourselves and others have around 100% uptime, but yes in the Nebb it now shows incorrect uptime for many that in that file have near 100% uptime

fringe pawn
#

blocks signed for 100% uptime for genesis validators should be closer to 355k

stiff adder
# fringe pawn lot of time passed since release of those files..

That file was released the 12th April, after the SE had ended, and of course uptime is only counted during the SE, not after SE had ended in epoch 91. I mean they even said keep validators and infra running a few more days just to help check some pending submissions and then they said validators/infra can be stopped, so obviously uptime is not counted after epoch 91πŸ˜…

fringe pawn
stiff adder
fringe pawn
#

also note tm address changes with change consensus key, so if anyone used that method they need to look at all tm addresses they had

fringe pawn
#

we ran into similar issues trying to create similar files off rpc calls

#

instead relying partly on indexer to create mine

stiff adder
fringe pawn
#

if you send me a dm I can show you my preliminary results, but i've only focused on post-gen for the time being

livid niche
#

About 50 validators have an uptime of more than 95%.
The impact of uptime on ratings is exaggerated; some S tasks have a greater impact than uptime.

barren pulsar
#

it should be 95% or 99.95% ?

fringe pawn
barren pulsar
fringe pawn
#

95
and 99

barren pulsar
fair patio
# fringe pawn what do you mean?

Hey don't really wanna start about the topic anymore 😭. I hope it made sense eventually, else I'll some time speak on it in DMs if you really want to. Though most info and perspectives on all this is above.

#

I saw your sheet btw. The mapping is super useful! Missing key component for linking public keys to validators!

Great job!

#

I was actually shocked seeing my uptime being around 96% :/! I never got jailed but I did have some epochs I missed. How was this calculated? It was minus first 2 epochs cause none of post genesis validators could run at those moments and remaining was calculated by counting all signed blocks?

#

For instance if I missed 3 epochs in total, that would correct to having missed 1 epoch divided by 91?

PS: I'm simplifying it atm by using epochs instead of block count ofcourse.

fringe pawn
#

ideally

#

or maybe idek what I'm doing πŸ™‚

#

also calculated govt percentage just now πŸ™‚

fair patio
#

Haha, if you checked the blocks signed, then it should be all good.

Would then be:
(total_blocks_signed + total_blocks_till_epoch_2) / (total_blocks_till_epoch_91)

austere rose
fair patio
fringe pawn
fringe pawn
fair patio
fringe pawn
#

wait lol

#

trying again haha

fair patio
#

πŸ˜‚

fringe pawn
#

ok so here goes

fair patio
#

Hehe. The formula I gave gives back the amount someone signed

#

And acts as if the person signed all first blocks in first two epochs

#

Basically nullifying that

fringe pawn
#

blocks_signed / 347517

fringe pawn
fair patio
#

You could rewrite the one I wrote as well.

#

It's perspective

fringe pawn
fringe pawn
#

it's not the formula I used though

fair patio
#

Hmm wait a sec.

#

Yours makes more sense than mine indeed.

Mine would still account for the first 2 epochs.

#

I just wonder how it becomes different percentages.

fringe pawn
#

I think they are equivalent

fair patio
#

I'm mindfucking myself over something as simple as this now.

fringe pawn
#

you are adding and I am subtracting

#

=

fair patio
#

Let's say we have

1000 signed, 200 in first two epochs and 2000 in total.

fringe pawn
#

but I think mine is more neat conceptually πŸ™‚

#

let's move this to dm shall we?

#

too much clutter

fair patio
#

0.55 is your formula
Mine gives 0.6.

#

Why lol, what am I missing here.

fringe pawn
#

hm

#

you're gonna make me do all these calculations aren't you πŸ™‚

fair patio
#

Yours bases percentage off a smaller set, mine bases it off all blocks but acts as if we signed all first blocks in those 2 epochs.

fringe pawn
#

could be my formula is off, it's definitely possible

fair patio
#

Not saying that though, think it's a perspective thing

#

Tho I really thought the answers would be the same.

#

πŸ˜‚ But percentages huh.

fringe pawn
#

I think they're equivalent tbh

fair patio
#

Filling out the calculation doesn't say this 😭 or I'm doing something noob.

#

Could you try with those simple numbers I just gave?

fringe pawn
#

you get my formula

#

it's mathematically equivalent

fair patio
#

Just do the calculation and you'll see it is different

fringe pawn
#

no but it's literally equivalent.

#

unless my math is too rusty

fair patio
#

I understand what you're trying to say, subtracting from denominator and the other word I don't know what it was called in English anymore.

fringe pawn
#

oh no lol. my math is rusty

#

I'm wrong

#

about the equivalency bit

fair patio
#

Badum tss

#

I think your approach is more so the perspective the team would have

fringe pawn
#

in any case my formula counts actually signed blocks as a fraction of possible window to sign, so I think it's pretty solid

fair patio
#

Mine is keeping the window as pre genesis

fringe pawn
#

but rn I'm just arguing the point because I really don't want to redo the queries

fair patio
#

It's actually unfair

#

Cause if we compare with pre genesis. They could have missed blocks in first two epochs

#

And we get away with having a perfect score in that region (up till epoch 2) if we take my approach

fringe pawn
fair patio
#

Hehe, forgive me, this was just a good exercise mathematically

fringe pawn
#

we also get perfect score in my formula

fair patio
fringe pawn
fringe pawn
#

in yours I think you would get slightly above 100%

fair patio
#

Ah well, team has to decide how they'll calculate it.

fair patio
fringe pawn
#

yeah yours give 102% πŸ™‚ (edit: this was incorrect)

fair patio
#

Or the boundaries are not correct.

#

Like the endpoints for epochs.

fringe pawn
#

just that your formula is off, sorry

fair patio
#

Lol that's not possible dude.

fringe pawn
#

or rather that it doesn't fit the problem being asked

fair patio
#

Nvm I'm not gonna argue over this

#

You keep doing this bullshit.

#

You didn't like how I was speaking facts up top and you felt butthurt back then, DM'ing me you didn't appreciate the way I spoke. But you keep doing this yourself.

#

Peace.

fringe pawn
#

dude we are discussing a formula here. this isn't even a discussion I wanted

fair patio
#

Ciao.

#

Don't ask me any more help, countless fucking times.

fringe pawn
#

sorry if I offended you. was not my intention at all

potent bronze
stiff adder
rigid crag
potent bronze
potent bronze
potent bronze
left rover
rapid sparrow
#

Gavin, are the scores. updated? Recently saw an update on nebb despite it 's being informed that nebb is broken!

potent bronze
narrow fable
potent bronze
#

pls keep accusations out of this thread

potent bronze
# left rover I mean if.

i think you mean evaluation criteria for S Class submissions, for which there wasn't any defined. they should be been defined sooner (like before the competition began)

potent bronze
sterile thorn
rigid crag
stiff adder
# potent bronze my understanding is that the scores still need S Class submissions before being ...

Thanks for the information, it is 100% sure that many approved S class tasks are still not added in the latest update of the Nebb today. What would be very useful to clarify is: 1) Are all the points for A tasks already on the current nebb? 2) The points for which C and B subcategories are already in the current nebb? Because certainly if the uptime and other things are still being clarified/calculated not all C and B points are already on the current nebb

fringe pawn
potent bronze
#

i've asked for the code that's used to track and calculate uptime

stiff adder
stiff adder
fringe pawn
stiff adder
potent bronze
stiff adder
potent bronze
#

is this a productive exchange? if not, pls just wait for the code

pine agate
stiff adder
# potent bronze i think we'll know this when we see the code for uptime

Hmmm I don't follow Gavin, in the blogpost it says for C V2: 'Start your validator as quickly as possible after the upgrade height', we know the upgrade height and those who signed the first block, what's ambiguous is the meaning of 'as quickly as possible', the Namada team needs to clarify what they meant by that, if first block signed or if something else, but definitely 'as quickly as possible' implies the first block signed, since there is not quicker than this possible

potent bronze
barren pulsar
potent bronze
pine agate
# potent bronze can you pls be more specific?

I'm Junkio ranked at position 55 and there's another person at the same rank. I've completed most of the tasks, but The Nebb has updated 2-3 times and my score hasn't changed. I keep getting stuck at the same ranking position. I've checked the basic tasks of most of the top-ranked individuals, but my score still falls far behind. (Especially basic tasks and hidden basic tasks).

My question is: What will happen if my score is still not updated correctly at the last minute? Is there any accurate data to cross-reference?

potent bronze
fringe pawn
stiff adder
# potent bronze ostensibly everything but S Class is in the Nebb, but we have identified two ite...

I would actually rephrase this Gavin as 'ostensibly everything but S Class tasks since the last S class db update is in the Nebb', because in the current nebb the top 5 are there because of early s5 and s6 tasks approved currently being audited. Ideally, all the approved S tasks in the WIP tab on the excel should be added to the nebb to get the proper estimate of the ranking, and then if there are a few pending tasks or some s5 or s6 to remove this could be done later. Because there are some pilots for example in current nebb below 25th that should be in top 10 or top 5 with all the tasks added to the nebb

tawny furnace
#

Will the final rankings be in nebb or outside somewhere?

stiff adder
stiff adder
frail nova
frail nova
fair patio
# potent bronze dude

Yep, guess I officially had it. What just happened was for me a summary of what has been going on in here post competition and why it bothered me to the point where I just snapped.

This behavior of "No, this is right, you're wrong." that keeps circling around and around. We can't seem to come to terms or see how 9 out of 10 times multiple perspectives hold truth. To the point where we deny even trying to understand the other person. It has to be this or that.

I will apologize @fringe pawn, for my outburst was misdirected. I also exaggerated big time with saying how often you ask for help.

I'm just tired (in general) of there not being an understanding or consideration for alternatives without or the least amount of impact dealt to everyone involved.

I will go away for a while, cause in my current state I'll won't be any good. Apologies for making this so personal now, Gavin. I'm also just human in the end, there'd be something terribly off if I always tried to be Mr. Nice Guy.

#

Or I was high 24/7 and on cloud 9...

crisp tree
sudden burrow
rapid sparrow
#

Possibility no one's fault here .
Just directing each other debate and throwing tantrums on ourselves because of all these unclear rules and conditions.

Like said blame no one, but

Just blame the organizing team. Don't let your frustration be between each other. Lately I have changed and not into debate and neither much I care now.

I'm like let them do whatever they want.

Cause this thing doesnt excite me anymore. Has gone too far. But still have spend some time and energy worth a while to come by check if I did win something.

potent bronze
potent bronze
potent bronze
# stiff adder I would actually rephrase this Gavin as 'ostensibly everything but S Class tasks...

ah, gotcha

  1. ~~we are awaiting feedback from eng team about four submissions in particular ⏳ ~~
  2. we need the rest of the security emails (shouldn't be too many; we're told that none are actual vulnerabilities, but we need to verify / be accountable) ⏳
  3. Spork needs to consolidate security emailed submissions with the S Class sheet (many were only submitted as emails, without tpknam) ⬅️

Spork's plan is to update everything at once, so that there isn't a lot of volatility with repeated changes

dry flicker
potent bronze
dry flicker
#

Actually not even burn, coz space, so, no oxygen. So it would be an insignificant "pop", except from inside the spaceship

#

Anyways, I'm off playing cross the ages and gods unchained in the meantime.
Jojoraky self preservation strategy seems to be the valid one, if even Zen loses his marbles.

fair patio
fringe pawn
dry flicker
fringe pawn
#

is it just me or are there 113 genesis signatures btw?

young hearth
crisp tree
#

I wish yall safe landing brothers

#

If I don't get a parachute I turn to parasite and turn everybody in space zombies.

fringe pawn
tulip lion
stiff adder
eager ibex
#

In fact, the timing of the point and the initial bond are closely related.

#

It seems that the earlier the bond, the higher the score, I guess the score from the bond is probably not evenly distributed.

#

Of course, according to the rules, it should be evenly distributed, but it seems that it isn't actually divided evenly (of course, this is just a guess based on my observations)

icy pond
#

@potent bronze How soon will the results of shielded expedition be published?

#

It's been 12 days 😯

eager ibex
icy pond
nova flint
sterile thorn
#

Would be interesting to see all hidden asteroids
Will be surprised if steward task mandatory assuming all validators voted mainly for their friends only

woven gull
sterile thorn
rigid crag
green ember
#

approving a normal proposal was impossible let alone becoming a steward :))
whatever you wrote in proposal was a straight "Nay"
I guess we dont forget network upgrade and hard fork proposal were also rejected :)))

woven gull
green ember
stiff adder
# potent bronze ah, gotcha 1. ~~we are awaiting feedback from eng team about four submissions i...

Hey Gavin for some S task categories some pilots have the same S category approved several times on the excel, it was mentioned before that even several S tasks in the same category are approved in the excel for the same pilot it is only counted once in the nebb but has this been 100% checked and verified? Because there are some concerns that some pilots in the current nebb are getting points several times for the same S class category

fringe pawn
dry flicker
fair patio
fair patio
fair patio
fair patio
potent bronze
fringe pawn
icy pond
fair patio
potent bronze
# icy pond It's been 12 days 😯

depends

i'd like to give people what's needed to independently verify. we're awaiting the raw scoring data and the code used to compile the scoring data ⏳

potent bronze
pine agate
potent bronze
potent bronze
pine agate
stiff adder
fair patio
#

I kissed pretoro, all is good now.

#

πŸ˜‚

fringe pawn
#

so I was going to post this but zen beat me to it: for everyone wondering, me and zen made friends again. I could have admittedly been a bit less brief if I had not been as exhausted from doing queries all day. and a bunch of other stuff we resolved in private

fair patio
#

And I shouldn't have been a dick. Inconsiderate to someone who spend so long trying to solve this.

fringe pawn
#

so in summary, all is good

#

all is zen lol

fair patio
#

Yes, I need to step away from that name

#

πŸ˜‚, I uh. Did take that name as a reminder though. What I aspire to be. Not what I am.

#

Cause it's arrogant. But yes enough bout us!

Project.

pine agate
#

🫑

green ember
#

Shielded Bromance

#

guys, just dont forget to sign a prenup

pine agate
#

I hope that Namada will announce the final results before the wedding of @fringe pawn and @fair patio takes place, or preferably before the first child is born. (As both matters are in great need of money)

#

❀️ πŸ™ NAM

fair patio
#

πŸ˜‚ Damn, apologies @fringe pawn, seems like we're gonna need to endure a period of bromance jokes. I wonder what Rigorous is gonna say cause that dude notorious for his jokes πŸ˜‚πŸ˜­. Do not tag him!!!

pine agate
fair patio
pine agate
#

lol

pine agate
fair patio
trail magnet
#

Is there any way we can see the current status of (un)validated class S ?

fringe pawn
#

or wip tab in the sheet rather

trail magnet
# potent bronze @here this is the criteria we intend to use for "Building protocol and cryptogra...

I have a ||(insert adjective)|| question, is it possible to submit a new task for this category? With the original specs enforced, leave us 1 month, and it will definitely solve the who's first problem. We would need, a person from the team answering to us, because I asked many times, but got almost no answers, I even asked you @potent bronze to relay my messages. And I stopped my efforts when I had my class S validated by another mean... I was really going to try it. I think it may be beneficial for everyone, the team and the person improving the code, it's a bit sad otherwise, because I think it will stay a blank category with no valid submission. To me it's an interesting proposition that is in the philosophy of the original blog post.. (that nobody did get) Or propose another solution because people had work on this, had they S validated, and stay in the top 10 for 2 months, and then may even not be rewarded at all. I was really shy to post S class at the beggining because, it was written, "you will get ban, if you post garbage", but no one did get ban, as I know of, and then validations as flooded from everywhere, so the competitor adjusted themselves to the difficulty. I don't understand what "error" they did. I don't want to steal ROID and I understood that the team really did want help on this(masp/note slowlish) and didn't get what they wanted, at the end everyone is loosing. Maybe we could end it another way, I'm sure people are tired, but I'm sure people are skillfull, and still a bit motivated, with a big knowledge of Namada now. I was thinking, if only I could go back, so I ask, ok, can we go back for another round ? I (and surely others) will really try to do it, if you let us, I'm all ears.

stiff adder
rigid crag
trail magnet
fair patio
# trail magnet I'll just do one reply because debating is a waste of time to me, the team doesn...

Very true. It's indeed a problem if the main "selling" point of a chain isn't performing as well as it should.

I'm not sure what the current state is, cause I heard fraccaman speak about big changes that were going to be made. Where they'd focus on how ZCash does it. But this is something I heard in a validator circle before the end of SE.

I do believe that in every creative process there has to be a time for hardcore in house testing and experimenting with different approaches. We might get in the way if it's not coordinated well.

SE was like a separate development track, which made it easier to keep potential ideas or implementations set apart from mainnet. So there's somewhat an order to be maintained and it does require some organizing/coordinating to not let us either do unnecessary work, conflict with code etc.

Perhaps Housefire could be meaningful in this aspect, cause this is planned to return.

young hearth
stiff adder
potent bronze
#

@trail magnet if you've followed the devs github activities and are not seeing progress on something that you think would be helpful, probably Housefire 🏚️πŸ”₯ will be the place to do it

potent bronze
stiff adder
dry heart
#

any news guys?

icy pond
potent bronze
#

update:

S Class not released yet because we're removing a few clusters of scaled Sybil accounts

feeling good that we'll have this done by tomorrow. putting in long hours, since this seems the best way to have the same kind of outcome as expanding the set of Crew winners

astral fern
#

πŸ‘†

crisp tree
covert garden
#

Good Luck for that ! πŸ˜…
Final results should take some more time.

mild badge
#

adv congratulations πŸ₯³

tired moss
#

Eat sleep check announcement repeat

rigid crag
tired moss
#

4-19.?

rigid crag
#

Some points changed yesterday I think

tired moss
#

Lol lost some roids πŸ₯²

fringe pawn
tired moss
#

I see on real nebb

gilded dome
#

@rigid crag I don't see any changes in crew leaderboard. Did it change too?

low token
low token
regal quartz
#

New Year's Eve is approaching

woven gull
crisp tree
icy pond
#

Not today again

potent bronze
#

i think we can probably release S Class list before removing the sybils

i want to remove sybils after the weekend so we're online, in case fires break out

icy pond
rigid crag
low token
knotty lion
#

πŸ™Œ

dry flicker
#

That way people can start speculating on the leaderboard (minus the Sybils)

rigid crag
astral fern
rigid crag
#

@slender wave what does recommend bounty mean?

#

Do we have a new category?

#

What does other mean in this category?

oak fox
#

@potent bronze Excuse me, but this is a high severe security vulnerability capabale to heavily harm the project in case of being in production.

https://github.com/anoma/namada/issues/2985

"A way to lock/freeze assets by freezing an IBC client - which makes them unusable until the related code is fixed (i.e. ibc-rs) and chain upgraded in order to be able to avoid freeze behaviour (0.51 ibc-rs) as well as updating frozen/expired IBC clients for new ones (0.52 ibc-rs) to finally unlock/unfreeze those assets"

Also, how come a core protocol improvement like adding the validator alias to be part of the validator metadata isn't considered a protocol improvement?

GitHub

I have already reported a similar (or perhaps related) behavior internally one month ago or so. It looks like something is broken with IBC clients statuses on Namada's side. Frozen height isn&#...

oak fox
fathom hawk
#

@potent bronze πŸ”… I worked on my security finding ALONE for DAYS without checking with any one and without checking any other submission . and tested the security issue ( DoS ) and verified it and sent PoC to the team . But in the xls sheet i got this
DoS issue but already reported
. .. All security finding was hidden and sent to the team and NO One would know which finding had been identified . IF i know that it had been finded by someone elese I would NOT work on it and tried to find another 1 .. ..So To make it fair all Security finding ( if proven ) should be approved for rewards because submission and results was hidden all the time . again IF team hint that for example ( DoS found in IBC ) had been identified that would make all other ppl who try to exploit IBC transferer would stop and try something else . But with this way . it not fair . And we are not talking about block explorer which can be cloned and had been cloned . we are talking about something few ppl can work on it

gaunt gull
#

πŸ€”

narrow fable
fathom hawk
#

Also the xls sheet didnot show if that DoS ( For others ) had been approved or not . So still legit to submit mine

gaunt gull
#

can we public all s6 already approved? I want to see it

rigid crag
fathom hawk
gaunt gull
supple prawn
gaunt gull
#

cool bro @supple prawn you got it

fathom hawk
supple prawn
fathom hawk
#

no need to say more

supple prawn
#

what is s6

gaunt gull
supple prawn
#

ah got it

#

even having an approved vulnerability submission will not be able to absorb the damage of C and B class missions. what a tragedy

gaunt gull
supple prawn
#

but it was probably an error that the core software could trigger itself at any time

gaunt gull
sudden burrow
gaunt gull
#

but someone reported before me so it was rejected