#outstanding AMA questions/concerns

1 messages · Page 1 of 1 (latest)

leaden bramble
#

.

placid gorge
#

Not a Q but a consideration for Namada team:

Uptime issue has been beaten to death and i see team is trying to play fair. Only comment i would like to add is it's ok to remove uptime if not everyone can achieve it, however to keep it also fair to people who worked really hard to keep SE running by achieving high uptime, their efforts should be rewarded proportionately i.e. uptime reward should be inline with possible SE rewards. Just asking team to be fair to both sides.

plucky karma
# placid gorge Not a Q but a consideration for Namada team: Uptime issue has been beaten to de...

" their efforts should be rewarded proportionately i.e. uptime reward should be inline with possible SE rewards"

I agree with that! I'm not in the top 25 because of the uptime removal, and I think missing 200k $NAM because of this decision is unfair to me (and others who have been negatively impacted) and beneficial for the people who are in the top 25 and shouldn't have been there, as not everyone encountered problems...

leaden bramble
mortal locust
leaden bramble
#

let's stay on topic

#

If your question was missed, please use this thread to repost it. If you missed the AMA, please read through it carefully, and if you have a question/concern that was not already addressed, post in this thread. Please nothing else.

sonic sentinel
#

Hi Gavin!
I discovered the reason for the change in our rating.
"Finding Security vulnerabilities" was rejected with the comment “issue identified previously on Feb 13, this submission was Feb 25”.
May I ask if this vulnerability was published in detail before my application was submitted?
We discovered this problem while working on our explorer ( explorer75 ), independently of other people's work.
The task was to receive information from the node, in addition to the documented capabilities of CometBFT and I managed to stop my RPC node by a random request during debugging.
Then the situation was investigated and a report was made in NEBB, which has a link to the code with specific requests that cause the node to fail.
Yesterday I found another member's report dated 2/13/02. There was a comment, “ABCI query DoS issue.”
If this is all the published information about this vulnerability, then besides the fact that we didn't know about this report, it's not detailed enough.
Our report was detailed and had a sample code. We could not copy the information about this vulnerability and use it.
I believe that if there was no information about a specific vulnerability in the public domain, then our application should not be rejected because we found it independently.
I still can't tell if this is a single error or if there were several and they all fall under the description “DoS json-rpc issue”...
I was planning to develop our Explorer. This work is interesting, and gives the feeling that you can make some useful contribution, but the current situation with the results of the testnet, do not allow to do it. All results on which we spent a lot of effort have been canceled (uptime task, S-class Finding Security vulnerabilities).
I ask the team to take the time to look into this issue, I would like to see a fair assessment of our work.

undone birch
#

Is the team working hard preparing the mainnet or are you enjoying your vacation now?

mortal locust
#

@leaden bramble you mentioned 'not dealt with:
Governance proposal task completion concern with assymetries in NAAN distribution', why uptime is dealt with and governance not? There were very true assymetries issues also with governance, and numerous reports of people unable to vote because the faucet was not working? Why governance gets the green light despite concerns while uptime is quickly buried? Not cool

undone birch
leaden bramble
# mortal locust <@294676197823217674> you mentioned 'not dealt with: Governance proposal task co...

i marked the governance concern in the hackmd as 'not dealt with' so Christopher knew what to reply to

i agree that there were flaws with governance-related missions. idk what you're talking about here, but it seems like you're equivocating between two different issues.

and not sure what you're talking about re: green light and burying stuff, but i hope you understand that at some point i'll need to start ignoring your messages bc so often they have been long, numerous, and seemingly written in bad faith

(which is frustrating, because some of your criticism has been really helpful, but a lot of it seems to be misleading)

mortal locust
leaden bramble
mortal locust
# leaden bramble the flaws in the SE have been frustrating and we've seen the unwavering dedicati...

Well, let's point out another major flaw: we are 11th with 8.1 billion roids and achieved 99% uptime, shielding app and protocol improvement with a PR even fixing the issues we found, we get 233k NAM (encipher 8.3 billion roids and gets 500K NAM more). Some ranked around 25th, with no uptime, no shielding app, no vulnerability or protocol improvement, just spam proposal voting, also get 233k NAM. This tiers idea was absolutely terrible, there is over 4 billion roids point difference between us 11th and the 25th ranked🤦‍♂️ From the 100th to 26th there is around 2 billon roids difference, but from the 25th to 11th over 4 billion roids difference, more than double. I propose something better so you can land the plane a bit better: there is 15x233K NAM for the tier 2, instead of giving the same to all, share it proportional to the amount of roids -> ((15x233k)/(total roids in tier 2))x(roids of each pilot in tier 2) to get the NAM prize for each pilot

mortal locust
# leaden bramble i marked the governance concern in the hackmd as 'not dealt with' so Christopher...

@leaden bramble There were issues with gov voting also voting duration is 2 epochs but we were able to vote on 1 epoch only next epoch we got vp issues. We got this issue while voting with non-validator account. I think we got this issue during entire SE, you can check the issue related messages on discord se-100 group during the first week. Why if there were also bugs related with governance and not all participants could compete for the governance tasks, governance is kept unchanged? There are many reports also of people unable to vote when the faucet was not working for an extended period of time. Is it ethical to ignore all these issues for governance while addressing them for uptime?

  1. The faucet did not work, so the validator could not vote on the proposal with a voting period of epoch3 to epoch4.
  2. @wind sapphire then manually send to tokens.
  3. In epoch 4, some validators received token and tried bonding as a non-validator account.
  4. Bonding takes place in the next epoch, so can vote starting from epoch5. In the end, neither validators nor non-validator account could vote on proposals whose voting deadline was epoch 4.
    So these validators could vote on 90%+ of proposals, but 99%+ was not achievable. Full details and evidence on the forum, please review at the earliest, thanks: https://forum.namada.net/t/concerns-about-uptime-mission-removals/665/16 Honestly these are much better reasons to remove governance, since for uptime there were ways to avoid getting jailed while for governance there was no way to get tokens to vote for many proposals
bronze iron
#

@lilac ginkgo You have Anoma and you have Namada. Major public investments were made in Anoma. Does this mean that this investment is made in Namada? Can we consider these to be the same project? If not, it turns out that Anom will also have a token in the future; if so, then what might it be needed for?

lilac ginkgo
#

@bronze iron in response to your question:

I work on a project called Anoma and a project called Namada - I wouldn't say that I have or own them, though, I'm just a contributor (same goes for Heliax). Backers who have SAFTs (contracts) with the Anoma Foundation have contracts which only state an obligation for us to propose an Anoma genesis block that includes allocations to those backers, the contracts do not mention Namada, which started a bit after at least the first backers joined anyways. For further context on this history, I recommend Awa's blog post - https://mirror.xyz/awasunyin.eth/crGJ-CLwYKvDHDY24yIAra-f2eZHdpT_myBzPrvXAPY.

The genesis block that the Anoma Foundation plans to propose for Namada will include some allocations to backers, in addition to allocations to RPGF drop recipients, RPGF recipients, and various contributors. The entire Namada genesis block proposal is just of our own volition, we have no contracts which constrain us to propose a genesis block with particular contents (but, obviously, anyone could choose to run a different genesis block if they don't like the one we propose).

Does that help answer your question?

bronze iron
# lilac ginkgo <@369201124550508547> in response to your question: I work on a project called ...

I'm not sure I understand what you mean. I’ll describe what I saw and why I had these questions - in the community they write like this Anoma (Namada) or another variant Namada (Anoma) attracted so much money in such and such rounds of financing... That is, in essence, Anoma’s investments are equated to investments in Namada, which is very confusing. Therefore, I wanted to clarify whether the investment in Namadu was separate, or whether the NAM token will be bundled with the Anoma token for investors. Are there any investments for Namad separately from Anom? If this is not confidential information, I will be glad if you explain this point. In any case, I'll be looking forward to the blog on tokenomics.

lilac ginkgo
#

I see. I think it depends on what you mean by "investment". No one has given money to the Anoma Foundation in exchange for contracts promising NAM token allocations, so in that sense no one has invested in Namada separately. It's possible that people who gave us money expected token allocations even though there were no contracts, I can't say. Many folks may have committed their time (e.g. in the Shielded Expedition) in hopes and expectations of token allocations in a genesis block proposal. I would consider that an investment of sorts, although not one of fiat money.

The Anoma Foundation plans to make two distinct genesis block proposals - one, very soon, for Namada, and one, much later, for Anoma - and those proposals will have different allocations, so in that sense there are two distinct tokens. In the future, it's possible that the tokens could converge, create mutual credit, or do other interesting cryptoeconomic things, but those decisions are up to the community and governance over time, not specifically up to us.

Does that help?

bronze iron
brisk bolt
jagged shadow
#

@lilac ginkgo I just read your answer here
#shielded-expedition message

But Gavin said there is no plan for collecting passports. Hope there is a plan considering participants privacy.

brisk bolt
mortal locust
#

@lilac ginkgo @leaden bramble According to the Shielded Expedition T&Cs (https://anoma.foundation/shielded-expedition-terms-and-conditions) US persons are not allowed to participate and VPN are not allowed to circumvent this. We are still gathering more evidence but believe some pilots in the Top 10 broke this rule of the Shielded Expedition and therefore should be disqualified?

#

'Participant is a non-U.S. person as defined in Rule 902 (k)(2) of Regulation S under the U.S. Securities Act of 1933. No directed selling efforts (as defined in Rule 902(c) of Regulation S) were made in the United States, and the Participant is not receiving any tokens hereunder for the account or benefit of any U.S. Person(s);'

#

'Participant will not use a VPN or other tool to circumvent any geoblock or other restrictions that the Foundation may have implemented for participants in the Testnet Program. Any circumvention or violation will permanently disqualify the respective Participant from participation in the Testnet Program;'

bronze iron
brisk bolt
pastel sonnet
#

this is crazy

mortal locust
mortal locust
pastel sonnet
ashen sable
#

👀

jagged shadow
bronze iron
mortal locust
mortal locust
bronze iron
jagged shadow
mortal locust
# bronze iron I’m just sure that you wouldn’t do all this if you were in the top 10. You’re ju...

There is no honor in removing uptime in last minute and changing all rules after SE ended, with correct rules we are in top 10 100%, we had s5 approved with PR fixing issues, s4 and uptime. And for governance check the forum, many couldn't vote in plenty of proposals because faucet was not working and were waiting for Adrian to send tokens. For uptime some managed to solved issues and get uptime, for governance for some was really impossible to vote in many proposals, so governance should be removed with much more reason than uptime

bronze iron
# mortal locust There is no honor in removing uptime in last minute and changing all rules after...

Well look. I managed to complete tasks related to shielded transactions between shielded addresses. But this task was deleted because this function broke and someone didn’t have time to do it, but I did and I was credited with roids for it (I’m 100% sure of this, because I followed the change in roids. But I don’t argue with this decision because I understand , that the team has the final decision. This is their competition and we play by their rules. And if my memory serves me correctly, the rules you refer to state that they can change anything and whenever they want, they can even cancel it. awards and we can't do anything about it.

mortal locust
bronze iron
#

@leaden bramble Sorry for the discussion in this thread, I just noticed that this thread is for questions. forgot about it

brisk bolt
mortal locust
lucid cliff
#

Hector being Hector again

lyric thistle
#

holy crap... why do we have all that discussion here... one person is trying to do whatever he can to defame others and get higher, what a shame...

brisk bolt
#

just leaving as a note here, gavin, that the indexer you linked in response to the remark that it would be nice to have access to the in-house indexer on SE, is not the version they used for SE, as per remarks by fraccaman on git when I asked (and can't be used for SE as I understand it). I understand why it's impractical to give us access to indexer, but wanted to just be precise that it hasn't been provided.

leaden bramble
leaden bramble
leaden bramble
bronze iron
leaden bramble
leaden bramble
brisk bolt
lucid cliff
brisk bolt
#

"initialize your validator post-genesis" (maybe)
"become part of the validator set for at least one epoch" (probably)
"start your validator as quickly as possible after upgrade height" (very likely)

leaden bramble
# brisk bolt

i think if signed blocks aren't counted, it would mean that player would not be credited for:

  1. initialize your validator post-genesis for post-genesis validators | start your validator within 5 mins for genesis validators
  2. become part of validator set for at least one epoch
  3. start your validator as quickly as possible after hard fork
brisk bolt
zealous oracle
brisk bolt