#'User is not a Shielded Expedition participant.'
1 messages · Page 1 of 1 (latest)
👋
@fluid wyvern 🫂
'User is not a Shielded Expedition participant.'
hello!
this thread is for two purposes:
- if you keep getting
User is not a Shielded Expedition participant.we have some things to check - if it remains a mystery, you can be one of the unlucky few that has to submit S Class manually here to @shadow hedge
do not submit S Class here unless we have done #1 first! and agreed that you must proceed to #2
@red fjord @ancient cedar 🫂
@prisma mason @plush hamlet pls tag anyone that is experiencing User is not a Shielded Expedition participant. despite extension being up-to-date, submission under 500 chars, and API indicating that they've registered
@dusty cedar 🫂
@obtuse crypt 🫂
i verified that your tpknam is registered
have you tried these?
Yes, I tried, but the error always prevents me from sending
welcome to group #2! pls work w @shadow hedge to submit each of your S Class missions here
wait sir, i’ll give your address in arround 6hours, i’m still busy irl
Ah nice! Will refer those here going forward! Thanks @mighty timber!
OK, thank you
Have same problem Wallet address - tnam1qr3c9kzm7wvkp09yxvvxzkdx4uz4tau8my8ad5yr
Validator address: tnam1q89auh8xszqxmmr34jnvzvnc8vmkyxgpfsuy0fg5
@low zenith 🫂
what's your tpknam?
need your tpknam pls
tpknam1qz8pshnuusgugkemwn7cv733vhhmtusju5x70fyw6dzd69g5fzkk547svw0
checked ✅ address is registered
you have seen the orignal post, and you've checked these?
Yes
Reason: Posted a link
The bot will not allow you to insert a link to the evidence for the task
@shadow hedge
Hi!
S Class Asteroid Category
Operating Namada infrastructure as a service
Please submit a summary of the S Class Asteroid you’ve found
Providing Public RPC Endpoints as a service
my Public Key
tpknam1qzv22jjsrhycv6leqc8335shvwnp4aatp6ugc2y0me6ahd59y09rjpurxr8
Evidence
h__p://91.107.221.196:26657/
tpknam1qpmfpse3acelyrkvzvptt9506f0qqkfe0valq3h6msuhc3rz74a45sdhr3r
verified ✅
have you reviewed these?
Yes
In extension
tnam1qz8xye0t99yk8r4ktu7k2uspc8c564m7svvegex2
tpknam1qpmfpse3acelyrkvzvptt9506f0qqkfe0valq3h6msuhc3rz74a45sdhr3r
submission 55/500
thanks! okay welcome to Group 2 🫂
pls submit each S Class manually here to @shadow hedge
hey guys
We are also having the same issue
Keys are verified
tpknam1qzj2yu5ya3rg44qpz9473m594cdacumgldgul7ed0qp98sh5kcw2v9p8e76
@wheat citrus
@mighty timber
hey!! 👋 been a while 🙂
yup, key looks good
pls submit S Class tasks directly to @shadow hedge
hi everyone! in future pls tag @shadow hedge with your tpknam to be checked
@shadow hedge
S Class Asteroid Category:
Operating Namada infrastructure as a service
Summary:
Operate a Namada indexer as a service
Public Key:
tpknam1qpk2wnktchjslajzgs6ve5y67tmgdev6dkhw775kpl5hally455zjmdu6uz
Evidence:
h__p://116.203.240.47:26657/block?height=1
Submitting here as I am getting not a shielded expedition participant error. Thanks.
hey all:
we'll go through submissions here, submitting them manually if need be... but it probably be tomorrow before i get to them as i've already accrued quite a backlog! i'll put 👀 on your post once i've looked at it. thanks!
@shadow hedge S Class Asteroid Category:
Operating Namada infrastructure as a service
Summary:
Operate a Namada indexer as a service
Public Key:
tpknam1qzwq6ev9atajfap87ndjl2ymqy2n2um70u7m6qg3lwjmygxj9dhaurma9da
Evidence:
h__p://namada-api.sproutstake.space/block/last
S Class Asteroid Category:
Operating Namada infrastructure as a service
Summary:
Providing Public RPC Endpoints as a service
Public Key
tpknam1qzwq6ev9atajfap87ndjl2ymqy2n2um70u7m6qg3lwjmygxj9dhaurma9da
Evidence
h__p://namada-rpc.sproutstake.space
We play as a team. So, i think we can update the address when we win the prize
So even though it says User is not a Shielded Expedition participant
the data is still sent to the API, right?
If so, I sent it several times because I thought it couldn't be sent. I'm very sorry about this problem
@shadow hedge
S Class Asteroid Category:
Operating Namada infrastructure as a service
Summary:
Providing Public RPC Endpoints as a service
Public Key:
tpknam1qzaqvxm6g4h7z34pgdqyzh3y4xevx072ednsfcujfza02knwrfkwqrgywah
transparent addy:
tnam1qzqgs9jdn76vtphjye6ntcgjv8rvm5c5wvsrq4zy
Evidence:
h__p://139.59.255.37:26657/
h__ps://github.com/anoma/namada-shielded-expedition/commit/00196bd3239d237e4de2b24c0cacd2e1842aaff5
i hope this can be fixed
Hello @shadow hedge ! It doesn't work for me too
Public Key
tpknam1qzlftk9273ccq0xn65s8masg93h6a2e43y5lj8fd9frjdp62nvcrqqenmrk
hello guys, my submit cannot be done because the site say "u are not a se participiant" i've done the step #1 so now i will give all infos to submit my class S manually, thanks
@shadow hedge
S Class Asteroid Category : Operating Namada infrastructure as a service
Providing public RPC Endpoints as a Service :
h..p://161.97.103.23:26657/
h..ps://github.com/anoma/namada-shielded-expedition/pull/328/commits/548eb0b3085ac0c4ce7fc762ba22ae1c5507aa96
Evidence: h..p://161.97.103.23:26657/
PK: tpknam1qq7xm3q96j4m5uqzqnm79zmvfw2dpjd785a3acgq44ps0ys2ulaugx6p25e
TP add: tnam1qpuxts7mr76rtqc7vlnyc7fglmanjunfvuddlupl
hey devs, i can't submit my S Class submission. imma submit here. @shadow hedge
S Class Asteroid Category : Operating Namada infrastructure as a service
Summary : Providing public RPC Endpoints as a Service
h...ps://github.com/anoma/namada-shielded-expedition/pull/331
Evidence: h...p://167.172.69.47:26657/
Public Key: tpknam1qqfd0z5t98u78xyztynrucp8cgwzep4ahm0hyh34uscdvd8ppq6rxc4yn0q
Transparent add: tnam1qpmqqpxavzlut0f4jr736pr5zmt8z7hxwcdyd33v
indexer : kv (on)
hey devs, i can't submit my S Class submission. imma submit here. @shadow hedge
S Class Asteroid Category: Operating Namada infrastructure as a service
Summary: Providing public RPC Endpoints as a Service
h...p://135.181.106.73:26657/
Evidence: h...p://135.181.106.73:26657/
**Public Key: ** tpknam1qr9hj77acpdntx63k2wql4053cslxwt8d9ruwtap8qzcp6c6wrl8xm3k6cy
**Transparent add: ** tnam1qzkqup3f33wa3wgzx6fq5st0zfzagjgff5rwlcuk
Hi, i can't submit my S Class submission. imma submit here. @shadow hedge
S Class Asteroid Category: Operating Namada infrastructure as a service
Summary: Providing public RPC Endpoints as a Service
h..p://157.90.151.227:26657
Evidence: h..p://157.90.151.227:26657
Public Key: tpknam1qzp9vtaaufeyq4sshtm0wk9t6axnvul93m0tur4qpcfp27uqt6xmzfpafdh
Transparent add: tnam1qze0xd7c3jrqlc665eplz9y20khstqfzdsznldrk
I'm trying to send now and it gives me an error User is not a Shielded Expedition participant. how i can fix it?
S Class Asteroid Category: Operating Namada infrastructure as a service
Summary: Providing public RPC Endpoints as a Service
my RPC htp://65.109.72.13:26657/
Public Key: tpknam1qqnsu3l53nh77ufr46t9xgy7npad86hwal3j9u3y4k2d92qh98ht5xv4yxt
Transparent : tnam1qrw6q5xyapewe0j0sqwgj52d5g6ygpwz3yy3xxza
Thanks @mighty timber
Hey @shadow hedge Ali, @wheat citrus will be submitting the tasks later on to here 🙏
Hello, i can't submit my S Class submission. imma submit here. @shadow hedge
S Class Asteroid Category: Operating Namada infrastructure as a service
Summary: Providing public RPC Endpoints as a Service
h..p://128.140.108.202:26657
Evidence: h..p://128.140.108.202:26657
Public Key: tpknam1qzv40fcrpt4ctz6wpz7kkj7n5g0pgk6k7ttjyvglvhk7k278e8dzx4jk638
Transparent add: tnam1qpf9l25k76ltrh9k888wsq5kggmdgefu3s3etva4
Im trying submit Operating Namada infrastructure as a service
My public RPC open http://51.89.115.168:26657/
transp: tnam1qppd9wuurdz0ezy2epw0lnqftageklykugd66rjy
Pubkey: tpknam1qr20k485p0h8mds9820he6zjrv2luf9nrhuwecdr9xrmva83ky7p6fmhww5
Reason: Posted a link
- Task 1:
- Category : Operating Namada infrastructure as a service
- Description :
Task : Providing public RPC endpoint as service
I am running a Namada full-node and open it's RPC as a service.
My server IP is : 155.133.7.250
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://155.133.7.250:26657/status
My Namada address : tnam1qzqlf0v5h6flykuz6u6vdhdvx0n2xwjzvufz63wv
MONIKER: zzzztthzzzz - Evidence :
h..p://155.133.7.250:26657/status
@shadow hedge
Hello, i can't submit my S Class submission. imma submit here. @shadow hedge
S Class Asteroid Category: Providing public RPC endpoint as service
Summary: Providing public RPC Endpoints as a Service
h..p://154.26.134.30:26657/status
Public Key: tpknam1qqfzpd8zm982x3pk4kd0s9pmksyeqdqdm68w07nmkx9g70c4htxkwgcwh26
Transparent add: tnam1qzescs3yhdg5tm4uqz0c5k7snsem3xn7lvhe3zuf
Task 1:
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
I am running a Namada full-node and open it's RPC as a service.
My server IP is : 128.140.94.169
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://128.140.94.169:26657/status
My Public Key : tpknam1qz5dx9ht4ad2j50avpsaut9ht2z9unmerahspvq4gek5dqff8400qtl3qaf
My Transparent Address : tnam1qzsdhrcfxlxcp42k20dhs2cm0vlnrhdztvxemtk5
MONIKER: freeman
Evidence : h..p://128.140.94.169:26657/status
@shadow hedge
Task 1:
- Category : Operating Namada infrastructure as a service
- Description :
- Task : Providing public RPC endpoint as service
I am running a Namada full-node and open it's RPC as a service.
My server IP is : 78.46.150.83
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://78.46.150.83:26657/status
My Public Key :tpknam1qrfe4v8urhnjjd04ghs8dkzenrwk46s03gxkz9h8jp4jh7a3cypsct9h402
My Transparent Address :tnam1qzw5ke2whpxj763sz60aqe5yayd6c5c2qcpmzg3d
MONIKER:yarik - Evidence :
h..p://78.46.150.83:26657/status
@shadow hedge
Task 1:
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 95.216.152.23
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://95.216.152.23:26657/status
My Public Key : tpknam1qqkqr7unz5np0cllj8asfxsdnphplnmyvh6swrytjyse4ya36qav6xykyz4
My Transparent Address : tnam1qzwrqjma22ghxxjc46vd4ncr0een63c3zq7vnsvw
MONIKER: dmitry
- Evidence :
h..p://95.216.152.23:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.76.77
RPC port is : 26657
You can check the status of node by send curl request to :
h...p://5.78.76.77:26657/status
My Public Key : tpknam1qpj2p4ghvthanr8fwrhcmdkkfwvahw9qc4ktrgv47r0w92rkwwegyjjv22p
My Transparent Address : tnam1qrc9nc7x3fudxe3kvut99ppjdy3gm4s7tu3339cl
MONIKER: butcher
- Evidence :
h...p://5.78.76.77:26657/status
@shadow hedge
Reason: Posted a link
@spork | Knowable
@mighty timber
Hi!
S Class Asteroid Category
Operating Namada infrastructure as a service
Please submit a summary of the S Class Asteroid you’ve found
Providing Public RPC Endpoints as a service
my Public Key
tpknam1qqhfg494tw2r3k64jdv3gdqyjztn4vu545f29nzdlg450zxeht0vgpheljp
Evidence
I add PR in github with my peer and RPC h..ps://github.com/anoma/namada-shielded-expedition/pull/281
h..p://173.212.245.122:26657/
@mighty timber I think there should be a repo on github where participants should add their requests, because some of bad actors can spam here not their RPC and how to identificate who use his own))))
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 95.217.181.230
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://95.217.181.230:26657/status
My Public Key : tpknam1qr37sg40qxehmlkkr9hffhltcxt7wclaqvv5xx7wnevzhxwtrav6cmrt5r5
My Transparent Address : tnam1qzallj7kglr3qrghlh0dklwfnk0gawjzz582xxaz
MONIKER: chilly
- Evidence :
h..p://95.217.181.230:26657/status
@shadow hedge
That's interesting, but what's stopping you from posting someone else's RPC on GitHub ? ))
There is one, https ://github.com/anoma/namada-shielded-expedition, you can submit a PR here
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 159.69.87.87
RPC port is : 26657
You can check the status of node by send curl request to :
h...p://159.69.87.87:26657/status
My Public Key : tpknam1qzh8dvas0pyty92w08nsjkg95vpcetnmn6vl7vej3l0x8ljuffxhzwnkdev
My Transparent Address : tnam1qzpjqy4kx9gmntztejpga6g8g7cx2ux0puh8hwe2
MONIKER: Konstantin
Evidence :
h...p://159.69.87.87:26657/status
@shadow hedge
Reason: Posted a link
you can take rpc and check validator_info = Tendermint key at validator
example my rpc #1210649213499871243 message
My Tendermint key: B8882772838501162D7FD935BDAEF7A87C704382
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.71.104
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.71.104:26657/status
My Public Key : tpknam1qpuxt797upkmu28vzlg5n6ml9vjtxzf480vtu4lk0yrdj2wsf8jmyrenjud
My Transparent Address : tnam1qz9kvddsvej8u859dnjlczepq8pydgk9s5ajthmk
MONIKER: talisman
Evidence :
h..p://5.78.71.104:26657/status
@shadow hedge
rpc and validator node should be different for security reasons
but who care)))
I agree, but this is a test network
it was just a question to think how to avoid bad actors
we can to sign gntx or something else
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 95.217.20.109
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://95.217.20.109:26657/status
My Public Key : tpknam1qqmjy86v3cnlmzys0apwgmpum3djh95un8q04qw0we3m783vnyk9ke6mg3p
My Transparent Address : tnam1qqm3kgr37k4pclwms88lamnerayaq9axr5zm96ed
MONIKER: clasik
Evidence :
h..p://95.217.20.109:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 65.21.62.212
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://65.21.62.212:26657/status
My Public Key : tpknam1qpdm2c4w2wfalnqku3xegrtmjj6ftt7vk509d4gwzd9z3k0sa8zvkqwh90s
My Transparent Address : tnam1qz5umcpt2m84s2dngf0pcpc5wj4s8hy97gjkkqhz
MONIKER: rock | star
Evidence :
h..p://65.21.62.212:26657/status
@shadow hedge
@shadow hedge new S Class submission plz.
S Class Asteroid Category:
Operating IBC / interoperability infrastructure
Summary:
Operate a Shielded Expredition-compatible Osmosis testnet relayer
Public Key:
tpknam1qzaqvxm6g4h7z34pgdqyzh3y4xevx072ednsfcujfza02knwrfkwqrgywah
moniker :
Grand Valley
transparent addy:
tnam1qzqgs9jdn76vtphjye6ntcgjv8rvm5c5wvsrq4zy
my osmosis relayer address :
osmo14qv635g3jxk3jqqz3m7v42gde0srlkutzxjntx
Evidence:
shielded-expedition.88f17d1d14 (channel-432) <> osmo-test-5 (channel-5893)
channel creation tx : h ttps://www.mintscan.io/osmosis-testnet/tx/F5AFE9BFFD8605BBAB4D8362FC3BEE4D208327B30D0129582126B7C5B3F56EAA?height=5622283
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 95.217.179.235
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://95.217.179.235:26657/status
My Public Key : tpknam1qztxzq8vs4vghfwpyk83v0ge7rwsgzxpctf5gwmfeea2tvv4xzv8qh5q8fa
My Transparent Address : tnam1qph0q69ey5yg3thy3v29ev8jvjjk0apt2cft6vap
MONIKER: irina || yummii
Evidence :
h..p://95.217.179.235:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.161.46.35
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.161.46.35:26657/status
My Public Key : tpknam1qpsj8lcjf3k9zjzxrpljykl0d6e9zzsn52ghllpat8elmyss7svmvetw7wa
My Transparent Address : tnam1qq5nhy7z6dmmusmexl8euj69vecwmch48vxa4zjw
MONIKER: akula
Evidence :
h..p://5.161.46.35:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.112.122
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.112.122:26657/status
My Public Key : tpknam1qpd9rkh2fh8wfx4fynae3j35mwk6eurctjgslzvx0w6zkcag7tukydpgha7
My Transparent Address : tnam1qrqmgvjwhm65ee9df0aa5vm4t24ru6kpgu2csz5t
MONIKER: poker_face
Evidence :
h..p://5.78.112.122:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 116.203.73.252
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://116.203.73.252:26657/status
My Public Key : tpknam1qzufnjd2q46jx95qw8katcudztdf477qfx70tmgd08rre58ka4g87gnvyar
My Transparent Address : tnam1qp44ktx05ss6spja7ka4sxr29xuwal2agy356f03
MONIKER: iron man
Evidence :
h..p://116.203.73.252:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.111.147
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.111.147:26657/status
My Public Key : tpknam1qr02erw99p4j7e6a4mc89ua0m9mgfs3kaulf6944m9nrr8z0q8al2y23a3e
My Transparent Address : tnam1qzfzt87565jue7ha3v0yp2sugp6tjrkeqyzw5rll
MONIKER: irina888
Evidence :
h..p://5.78.111.147:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.161.214.181
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.161.214.181:26657/status
My Public Key : tpknam1qpzw0j05xlz850uftyvwettdmspdhxcqgcccxy0p8dw5neptj9g3xe0jzd8
My Transparent Address : tnam1qq930hvunl7lxnak3a6zklulmk0whxux9qz92hyj
MONIKER: Rustem | gaz
Evidence :
h..p://5.161.214.181:26657/status
@shadow hedge
@shadow hedge i've created an ibc channel (osmosis <> namada), please check!
task : S class
subclass : Operating IBC / interoperability infrastructure
summary : Operate a Shielded Expredition-compatible Osmosis testnet relayer
moniker : D.Santos
namada pk :
tpknam1qqfd0z5t98u78xyztynrucp8cgwzep4ahm0hyh34uscdvd8ppq6rxc4yn0q
namada tp address :
tnam1qpmqqpxavzlut0f4jr736pr5zmt8z7hxwcdyd33v
osmosis relayer address (newly generated, aka seperate mnemonic from my primary namada keys) :
osmo137wq2ln0lkyugdj08yvenqdjfnvkln3r4jt3g6
Evidences :
shielded-expedition.88f17d1d14 (channel-433) <> osmo-test-5 (channel-5894)
channel creation evidence : h__ps://www.mintscan.io/osmosis-testnet/tx/A2716C344FAACD5A01C8B853FE78579C4268DB1B568FC135BC73B076E1F74CF7?height=5622477
ibc-transfer evidence (namada --> osmosis) :
OSMOSIS = h__ps://www.mintscan.io/osmosis-testnet/tx/4722A603CE64F0278777EDB884D510DE8D84C1234DB69D211B23A9A1C0216466?height=5622705```
relay evidence : ```h__ps://testnet.ping.pub/osmosis/tx/B748D2054398333DBC91B25491D45AB83073DB7DD9E52EEC7CB46969E7A2BCD2```
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 116.202.9.96
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://116.202.9.96:26657/status
My Public Key : tpknam1qqqdzclcs5gd320ldg4ufu9dhtk66y6km668x7c8umevx6tekmwyzscz30n
My Transparent Address : tnam1qzym7czl7wvewuegl067gfgz3546a6af4qf3fl6m
MONIKER: Tatiana || gg
Evidence :
h..p://116.202.9.96:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.46.16
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.46.16:26657/status
My Public Key : tpknam1qrt04r77jpfld0k52lpl305d9ttsg9cvzhv6zz634fsjjfu6ztldgfm7jdh
My Transparent Address : tnam1qqngjxhy6eh3cd05pew2rnffk57ccj8lpcs2qnj7
MONIKER: nuari
Evidence :
h..p://5.78.46.16:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.161.197.121
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.161.197.121:26657/status
My Public Key : tpknam1qpjwc99tach8004j7ktrc680ll84ukm5uq53rjqdat3yqjns83l673q3pl3
My Transparent Address : tnam1qrnevwuvezderhkv5m2vxeultvkxad9g4s5h3wwr
MONIKER: mr.nobody
Evidence :
h..p://5.161.197.121:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 159.69.46.238
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://159.69.46.238:26657/status
My Public Key : tpknam1qq0hp2ranxrq09gsz967h4cly7fnmhajlkynku8uynh9kny6l7a5clhf53r
My Transparent Address : tnam1qpp7q3pzxsjcqe2k3tvdjasx6vr8sfeexymvfs4w
MONIKER: The brain
Evidence :
h..p://159.69.46.238:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.46.36
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.46.36:26657/status
My Public Key : tpknam1qqcx8dg8r6zsp0k5cvt0hl8qe9vpfku3hhlnzvtpxwt4eg3znm28um7kd74
My Transparent Address : tnam1qppwklnwz0klgfdrdupshtl7ssqp9syauvr3nu2n
MONIKER: Goldenshade
Evidence :
h..p://5.78.46.36:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.95.122
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.95.122:26657/status
My Public Key : tpknam1qrxu2tlh5lc0ul8dgu0d9542caz765qdz25kq9g0tnv2qpl6ynsl22cpvmq
My Transparent Address : tnam1qz3t2sx4tnkptkw0hsv450y086ay07x5sv9su65s
MONIKER: Pavlik
Evidence :
h..p://5.78.95.122:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 138.201.172.194
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://138.201.172.194:26657/status
My Public Key : tpknam1qq3hyrqhjmfhqlhqllxt30vhek5x9ewhj8z7qjq346p7gdgvvc5tcfpcag4
My Transparent Address : tnam1qpwvnzasdp3uc0kgfad7lm07hs79tscway9azsqj
MONIKER: hellworker
Evidence :
h..p://138.201.172.194:26657/status
@shadow hedge
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
My server IP is : 5.78.40.113
RPC port is : 26657
You can check the status of node by send curl request to :
h..p://5.78.40.113:26657/status
My Public Key : tpknam1qrpshqhnc59nnaq9fp2rmv7twwa5jrj2cqf3jescam5qk8z56tk47acz3dz
My Transparent Address : tnam1qp77fgr2evyqqt4uznme9haeleqyjdf8hg89ux9c
MONIKER: dreamer
Evidence :
h..p://5.78.40.113:26657/status
@shadow hedge
i stil cant submit rpc task with error, how to fix it? ERROR
User is not a Shielded Expedition participant. pubk tpknam1qr20k485p0h8mds9820he6zjrv2luf9nrhuwecdr9xrmva83ky7p6fmhww5
i updated some things, i hope you recheck it if you have checked it before @shadow hedge
check please @shadow hedge
new submission @shadow hedge
new S Class submission plz.
S Class Asteroid Category:
Operating IBC / interoperability infrastructure
Summary:
Operate a Shielded Expredition-compatible Cosmos testnet relayer
Public Key:
tpknam1qzaqvxm6g4h7z34pgdqyzh3y4xevx072ednsfcujfza02knwrfkwqrgywah
moniker :
Grand Valley
transparent addy:
tnam1qzqgs9jdn76vtphjye6ntcgjv8rvm5c5wvsrq4zy
my cosmos relayer address :
cosmos14qv635g3jxk3jqqz3m7v42gde0srlkut2apra5
Evidence:
- channels : shielded-expedition.88f17d1d14 (channel-434) <> theta-testnet-001 (channel-3873)
- channel creation tx :
h ttps://www.mintscan.io/cosmoshub-testnet/tx/17EEF99708ACB5A2E46990DCE39A1094F16775C8AD34AA13A7F1C9197989561E?height=20457494 - ibc (namada -> cosmos) =
Wrapper transaction hash:F10BE0F1C2D069BF7B192C3B219C9B222FA4893CBC56F34DD28DA6768CB8043E
Inner transaction hash:80774F5FA993B6F619BDF3EAC73BCDE602A6A8C07F85C68BE4633C270A7E61BD
@shadow hedge i've created another ibc channel (cosmos <> namada), please check!
task : S class
subclass : Operating IBC / interoperability infrastructure
summary : Operate a Shielded Expredition-compatible Cosmos testnet relayer
moniker : D.Santos
namada pk :
tpknam1qqfd0z5t98u78xyztynrucp8cgwzep4ahm0hyh34uscdvd8ppq6rxc4yn0q
namada tp address :
tnam1qpmqqpxavzlut0f4jr736pr5zmt8z7hxwcdyd33v
cosmos relayer address (newly generated, aka seperate mnemonic from my primary namada keys) :
cosmos137wq2ln0lkyugdj08yvenqdjfnvkln3rafcp7g
Evidences :
shielded-expedition.88f17d1d14 (channel-436) <> theta-testnet-001 (channel-3875)
channel creation evidence :
h__ps://www.mintscan.io/cosmoshub-testnet/tx/A80F9D376E3BA310DFB88D38B8984315BDE51AF49A70293E068F80117ED16E4B?height=20458436
ibc-transfer using the channel evidence (namada --> cosmos) :
COSMOS = h__ps://www.mintscan.io/cosmoshub-testnet/tx/ED04E0F796D89DD10E2543261C5C1DF2C2E81AA8C19CAA615A662A4DE04591BF?height=20458529```
tnam1qpmghghlyhxm7qvml4uzy2mm0j4r0d78yu47usnt
S Class Asteroid Category: Operating Namada Infrastructure as a service
Please submit a summary of the S Class Asteroid you’ve found: we are providing namada se public rpc node as service
Evidence: h ttp://37.120.173.44:26657
ERROR
User is not a Shielded Expedition participant.
TASK:
Category: Operating Namada
infrastructure.
Description:
providing public Rpc endpoint as service.
Evidence:
Below is the evidence of our Rpc url that's has been used and still in synch with the network.
http:// 104.251.222.134:26657/
Our Pubkey :
tpknam1qrvsyrczhgm2v6k0pkwawuy8049shsvz2l5xde7gpcpnyuzeg9znxv2xtcu
MONIKER: Jaytechent
@shadow hedge
My Public Key : tpknam1qrklx46xussyvvgu3gjsge0kueasvrdarrc5tgxelw8na6ve9as2y4jz5uv
My Transparent Address : tnam1qz3z0qt93e3gdfm2lcjd5hygf28w5fhvxqwfmjcw
My server IP is : 135.181.227.157
MONIKER: MapleSyrup
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Providing public RPC endpoint as service
RPC port is : 27357
You can check the status of node by
Evidence :
h..p://135.181.227.157:27357
=============
Task :
Category : Operating Namada infrastructure as a service
Description :
Task : Operate a Namada indexer as a service
Evidence :
h..p://135.181.227.157:27357/status
=============
@shadow hedge
Reason: Posted a link
TASK:
Category: Operating Namada
infrastructure.
Description:
** providing public Rpc endpoint as service.**
Evidence:
Below is the evidence of our Rpc url that's has been used and still in synch with the network.
65.108.106.168:34657/
Our Pubkey :
tpknam1qqvzcv6c4wwl8rkqu8dxmxh25td0g4c249hfqag6uqrskl9ztuv8wgv2rmz
MONIKER: infinity
@shadow hedge
Reason: Posted a link
ERROR
User is not a Shielded Expedition participant.
S Class Asteroid Category
RPC service
Please submit a summary of the S Class Asteroid you’ve found:
My RPC Service
h..p://65.108.197.84:26657/
Evidence
h..p://65.108.197.84:26657/
My Public Key:
tpknam1qzw6knx7z3dtk68w558ghdetq75wtmh8efqq6dj3s0my9g4u0ajlysych0a
Moniker:
subtlelight
@shadow hedge
TASK:
Category: Operating Namda infrastructure as a service
Description:
** INDEXER **
Evidence:
Setup postgres/namadexer-server/namadexer-indexer.
You can check using any block. (for some reason it doesn’t work with "last", but I’ll try to fix it)
65.108.106.168:30303/block/height/71644
Our Pubkey :
tpknam1qqvzcv6c4wwl8rkqu8dxmxh25td0g4c249hfqag6uqrskl9ztuv8wgv2rmz
MONIKER: infinity
@shadow hedge
@signal parrot
@mighty timber pls check DM
S Class Asteroid Category:
Operating Namada infrastructure as a service
Description:
Providing public RPC endpoint as service.
Evidence:
http://namada-se.ptzruslan.org:26657
Description:
Operate a Namada indexer sa a service
Evidence:
http://namada-se.ptzruslan.org:30303/block/last
Our Pubkey:
tpknam1qzsd9r6dklslndzmjffz2qe7xmvwnfc8ha5vhktpqk989wpquum5kw3xkga
MONIKER: ptzruslan
@shadow hedge
Hello! I found that I can submit S-class without an error when i deleted "http://" and last "/" symbol from "Evidence " . Maybe it will help you in debug @shadow hedge
Yes, actually I was only able to submit after removing the slashes.
@shadow hedge
S Class Asteroid Category:
Operating Namada infrastructure as a service
Summary:
Providing Public RPC Endpoint as a service
Public Key:
tpknam1qzj2yu5ya3rg44qpz9473m594cdacumgldgul7ed0qp98sh5kcw2v9p8e76
Evidence:
http://195.201.197.246:30657/
@here can you pls try your failed submissions again? and tell me what error you get
in DM
i've only this account...
i've submitted manually but idk i need to re-submit my class S
it still error
ERROR
User is not a Shielded Expedition participant. You've tried to submit an S Class Asteroid with the following public key: tpknam1qqhfg494tw2r3k64jdv3gdqyjztn4vu545f29nzdlg450zxeht0vgpheljp. Please double check if the correct default account is selected in the extension.
tnam1qzfn6ecqy56hxd7cxtd9re659v0sd7mrqs62d6es
S Class Asteroid Category: Operating Namada Infrastructure as a service
Please submit a summary of the S Class Asteroid you’ve found: we are providing namada se public rpc node as service
Evidence: http:/ /37.120.173.44:26657
ERROR
User is not a Shielded Expedition participant. You've tried to submit an S Class Asteroid with the following public key: tpknam1qr8nueltsfp66hly947ww67rcknkmd3zrjkvqlcjxehvgy4p0ceus5ytnx2. Please double check if the correct default account is selected in the extension.
ERROR
User is not a Shielded Expedition participant. You've tried to submit an S Class Asteroid with the following public key: tpknam1qzv22jjsrhycv6leqc8335shvwnp4aatp6ugc2y0me6ahd59y09rjpurxr8. Please double check if the correct default account is selected in the extension.
for now i can submit my submissions through the website, is that alright?
i mean what about my discord submissions?
please don't categorize my submissions as spams, just check my submissions through the namada website
@mighty timber sorry for tagging, but this is important
It didn't go through. The error persist, it just diplay our public key ... someone suggest we submit our evidence without http, should we do this??
Yes, it work :))
I have submitted 2 S-class tasks 👍🏼
To sign my S class submission, I enter my password and extension window stays for about 5 minutes: Decrypting keys and signing with tnam1...
After that it gives the following error: Error: Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received Try again
When resending, endlessly repeating error: Error: Error: no resolvers found for tab ID 1182873580 Try again
I reinstalled the extension, installed the extension on another browser - all this did not help. This tip for a similar problem didn't help: #🫂︱se-community-support message
Did you include http in your url
Evidence:
http://namada-se.ptzruslan.org:26657
i use this promt (without slash in the end)
Ok. I did use my ip with the port without the slash but still didn't wrk
It worked for me too!
@here many of the errors should be fixed now! pls check?
special thanks to @undone widget 🙌
there's probably still more stuff that's getting blocked--please experiment let us know the things that are preventing your submissions
if Spork confirmed with you, then it should be in the sheet. he highlighted the entries in light green at bottom of sheet: https://docs.google.com/spreadsheets/d/1YgLo_nt-s_d-2UkrEPcluUnieeuLJtF6vSKsER9EEZU/edit#gid=0
Batch A
#,Received,Time (CET),From,Category,Description,Evidence,Eligible for ROIDS?,S Class Subclass,Comments
1,02.02.2024,16:38,tpknam1qqqu2hwp6wqkuz84arxg4mqhaa46t9pdcq7mmcdcgw5tckkeq0tgudple6q,Providing Public RPC as a service,Public RPC as a service for Shielded Expedition network.,
it haven't fortunately
can you resubmit it? or are you getting the error
please just review my via-website submissions @shadow hedge
now i can normally submit my S Class submissions through the website
@jovial cloak core devs asking if you happen to be using antivirus software, and also to try this:
1- Go to chrome://extension, search for Namada Extension, click on Details, then make sure to have “Allow in Private” or “Allow in Incognito” option enabled.
2- Open an anonymous tab (control + shift + N, or cmd + shift = N) and try to repeat the operation in an anonymous tab.
@scenic wadi what error are you seeing?
I was able to send it that way, thank you.
- please don't consider it spam, I posted it here earlier. #1210649213499871243 message
@jovial cloak lmk if it works?
I also posted here earlier on how to do it better:
- send if it works as here #1210649213499871243 message
- or leave it in discord #1210649213499871243 message
we're trying to move away from leaving them in Discord and get all the bugs squashed 🐛
Okay 🫡 , I'll try the submission as described here #1210649213499871243 message.
What fixed it? Do confirm so others can use the same process to submit their tasks too
Yeah, I sent it.
It worked for me, too.
@mighty timber, if I submitted the S class task yesterday, should it already be displayed in the google sheet? if not, when should it appear so that I know if my submission has been received at all?
Haven’t been updated yet, check the sheet only tasks until Feb 20 have been populated in sheet
it should be there. you'll see the spreadsheet updated in a few hours (i'll announce) and you can verify that it's there
fyi @plush hamlet @prisma mason, pls spread the word if people struggle with S Class submissions (and lmk if people are still unable)
i'm going to close this thread and announce that S Class submissions should be working for everyone now