#**New requirements for RPC/Indexer
1 messages · Page 1 of 1 (latest)
Very good 👏
Excellent decision
Good work
@restive furnace will we have to resubmit if we used https but didn't submit in a format that is machine-parseable? will it show on sheet if we need to resubmit? thanks 🙂
can you give an example?
let's say I put "rpc.testnet.one (both http and https)"
which of course provides the info but I assume script wouldn't parse
so when will SE end
good news for us
https://cosmowiz.com/networks/NamadaNetwork
verify your rpc!
what is?
Certainly, applying for a TLS certificate is not a hassle, but I must point out that changing the rules at the end is definitely a foolish mistake. It's like an athlete participating in a 1000m race, and upon reaching the finish line, the judges say the committee has discussed changing the race to 3000m. As an athlete, I will abide by the committee's decision, but I definitely won't consider it to be the right decision.
The next change in the rules should be the acceptance of IBC with 500+ transactions, and finally, disqualify everyone and keep the tokens for yourself😆
In fact, let me be blunt, but this is horrible organization of the testnet. An example of how to ruin years of quality work in one month in the eyes of the community.
what are you talking about? there is no rule change. it's an adjustment of evaluation criteria for certain tasks due to blatant spam
An interesting perspective. Just because I haven't applied for an HTTPS certificate, does that make my RPC a spam? And now if I apply for one, then it's not spam anymore, haha.
I'm not sure where your logic is. Can't spam apply for an SSL/TLS certificate? What direct relationship does SSL/TLS have with whether it's spam or not?
that's not what I said. I didn't say yours was spam
it's an extra step to make mass submissions less feasible. it sorts out the people who don't want to put in the work. but regardless no reason to keep discussing this bro.
just had to address the claim of rule change, that's too big a term to use here
That is, a working RPC without a domain name is spam?
okay no more debating amongst one another, pls direct questions/concerns to Spork when discussing
and pls no answering one another if it becomes clear there is a conflict
some kind of nonsense - there can be no spam - the only difference is the https certificate (domain name with an ssl certificate) instead of http (regular server) .. instead of doing nonsense, it would be better to fix the leaderboard!!
I think its a good move. Since public endpoints need to be Https secured and should have an associated domain name for folks to easily use it
Ok, considering that I initially made rpc with SSL, thanks for removing the competitors.
There's not much to discuss, since you won't take our opinions into account anyway. It would be more practical to take some steps forward. Please review the development task I submitted as soon as possible.
@restive furnace One of my old endpoints were http, updated to https and sent you the https endpoints over dm. Can you check when you get a chance? Thanks
By the way, what should I do after installing the amazing SSL certificate, should I DM the mod or submit the task again?
@restive furnace I propose not to touch the http or https topic, at least for accepted works; in the original conditions this was not the case and all http were accepted. for example, I can’t add an ssl certificate to my domain, I’ll need to buy a new domain. I think there are a lot of them. Is this relevant to the essence of the task? It seems to me that reviewing past accepted assignments with normal alphabet domains brings confusion and negativity.
goood
lol, I have to buy a domain to publish RPC on the testnet, great idea, 0 comments
Just leave it if you don't want.
I have prepared a contribution, I hope they will reward me with a role) #contributions message
Good luck )
The funny thing is that the top 100 were determined from the genesis file (where 100 validators were selected) and oh gods, only the top 100 will receive rewards))) don’t you find this odd, humorist?)
just think about what you are saying! if, let’s say, initially at work you are told to sell 5 cars, the main thing is that they work, but when the time comes to sell and the client is ready to buy, then they tell you that these cars must be new from the showroom (and you already have 5 cars, but used ones with low mileage) then what will be your reaction???
@restive furnace What should I do if the indexer worked fine before the hardfork, but after it won't start with a constant error ```WARN namadexer::indexer: Failed to retreive block at height 1. Trying again in 10 seconds. (REASON : response error)````
and now how do I resubmit my solution with the domain added for this?
depends how far it's synced. there is some help in #1209046768910737448
I hope the official team can review the development tasks starting with 's' sooner. My tasks have been submitted for almost two weeks now, but they have yet to be reviewed.
I hope the official team can review the Class S development tasks sooner. I have submitted my tasks for almost two weeks now, but they still haven't been reviewed.
hi, my indexer task was rejected as the node is far behind chain. And I already fixed the node and it is working again, can you guys check it?
pubkey: tpknam1qrf4xm5zw9rlueslf4tugy8lr20tpvmv5rgwsdvwvtyd26xlxcha5080j4a
indexer: https://namada-indexer.decentrio.ventures/
https://namada-indexer.decentrio.ventures/block/last gets bad gateway
lol sorry wrong port, working now sirr thank you so much!
hmm can you check again (maybe cache remove helps)
okay confirmed, i've asked for submission check to be updated
@restive furnace @reef wedge I sent explorer in the 2340 post, but it was rejected because it was not https. Could you please check again, my domain also supports https.