AeroNyx Nodeboard operator konsolu rehberi

Nodeboard, AeroNyx merkeziyetsiz gizlilik dugumlerinin operasyon konsoludur. Kayit, toplu saglik, kapasite, protokol kaniti, bakim ve incident closure islerini kullanici trafigini veya sifreli icerigi gostermeden tekrarlanabilir workflow'lara donusturur. app.aeronyx.network adresini acin. Her panel yalnizca guncel kaynaginin bildirdigini kanitlar; configuration, runtime readiness ve observed evidence ayri durumlardir.

Kapsam ve isletim modeli

Uc seviye kullanin. Dashboard fleet'in dikkat isteyip istemedigini, Services size ait dugumlerde bir service/capacity domain karsilastirmasini, Node detail ise tek dugumun evidence, control ve audit history'sini sunar. Saglikli dugumler sessiz kalir; raw proof history ve command timeline detayda bulunur. Nodeboard kimligi dogrulanmis operatorun dugumlerini yonetir, herkese acik traffic explorer degildir.

Dugum kaydetme

Registration Codes icinde kisa omurlu kod olusturun, uretilen command veya resmi installer'i kullanin. Planning, install, registration, service start, heartbeat ve admission adimlarini ayri izleyin. Dugum gorunurse region, public visibility, runtime version, source commit, capacity ve health'i dogrulayin. Kod tek onboarding'i baglar; tekrar kullanilan API key degildir ve tuketilmis secret yeniden gosterilmez.

Fleet attention ile baslama

Oncelik: offline/stale heartbeat; failed/timeout/stale command; active sessions varken maintenance; packet drops veya IP pool, conntrack, fd, disk baskisi; policy drift; discovery/relay mismatch; sonra eski recovery/proof evidence. Stale, not reported ve disabled, zero ya da healthy demek degildir. En yuksek etkili ogeyi acin, user impact ve dogrulanabilir closure condition belirleyin.

Services ve dugum detayi

Services; Privacy Network, Discovery & Relay, MemChain & Storage ve Runtime sinyallerini toplar. Karsilastirmadan sonra node detail'da source timestamp, policy sync, risk, command state ve recovery evidence inceleyin. Her incident icin signal, impact, action, closure gerekir. Exit code zero tek basina closure degildir; fresh heartbeat, service health, protocol endpoint ve etkilenen capacity geri gelmelidir.

Kapasite ve placement karari

Capacity admission karari icindir, gosteris score'u degildir. IP pool used/free, max_connections, policy max_sessions, active sessions, conntrack, fd, packet drops, pps/bps, bandwidth policy, disk, memory ve CPU'yu izleyin. Hard runtime limit ile commercial policy'yi ayirin; zero backend semantics'e gore unlimited olabilir. Nedeniyle birlikte Accepting, Limited, Drain veya Maintenance gosterin; aggregate rate'ten bireysel davranis cikarmayin.

Discovery ve sifreli relay kaniti

Configured capability, signed advertisement, endpoint reachability, recent probe stability, real encrypted relay observation, terminal client receipt ve restart continuity'yi ayirin. Synthetic probe test path kanitidir, user traffic degildir. OnionMiddle no-exit encrypted relay roludur; reachable peer API, ready ChatRelay, signed descriptor, routeable peers ve fresh path evidence ister. Route hop, social graph, payload veya client identity aciga cikmaz.

MemChain ve commitment kaniti

MemChain paneli sealed storage, commitment follower, witness, quota, cleanup ve recovery'nin configuration/freshness durumunu gosterebilir. Ozellikler config-gated'dir; empty/disabled ariza kaniti degildir. Witness/checkpoint sayilari rollback/fork evidence'dir, public-chain consensus veya payload possession proof degildir. Yalniz aggregate state; owner key, record ID, project, vector, edge, checkpoint material ve ciphertext yoktur.

Guvenli bakim, restart ve upgrade

Remote restart_service backend-gated privileged command'dir. Permission, active-session warning, maintenance/drain guidance, acik confirmation, immutable audit ve pending -> sent -> executing -> completed | failed | timeout lifecycle gerekir; yalniz izin verildiginde cancel edilir. Sonra maintenance bitmeden runtime, heartbeat, healthcheck, policy sync ve ilgili evidence dogrulanir. Upgrade paneli version drift, staged state, blocker ve cutover safety gosterir; evrensel one-click remote upgrade vaadi degildir. Onayli upgrade ve rollback workflow'unu kullanin.

Erisim kimliklerini ayirma

Registration code node enrollment, private access code restricted node'a onayli client admission, anonymous voucher ise operator credential olmadan service eligibility icindir. Birbirlerinin yerine gecmez. Least privilege, short expiry, one-time reveal, revocation ve audit uygulayin. Secret, private key, raw bearer veya recovery material'i event, URL, screenshot ve support ticket'a koymayin.

Event, freshness ve audit

Her panel provenance ve freshness gostermelidir: signed Rust heartbeat, local health endpoint, discovery status, systemd/upgrade report, backend policy veya command audit. Event ne zaman, hangi node/service, hangi izinli actor ve closure evidence gelip gelmedigini yanitlar. Timestamp ve coarse reason code kalabilir; payload, destination, message ID, client IP activity, memory content ve social graph dislanir.

Yetkiler ve gizlilik siniri

Registration, policy, maintenance, command, code ve audit role-based authorization ile korunur. Nodeboard aggregate sessions, bytes, packets, capacity pressure, routeability, proof outcomes, recovery ve command lifecycle gosterebilir. DNS, destination, browsing history, packet/message/MemChain plaintext, client public-IP activity, wallet traffic, private key veya voucher secret gostermez. Operator user behavior bilmeden altyapiyi isletebilmelidir.

Operator rutini ve referanslar

Gunluk: Attention, offline/stale, placement, drops, resource pressure, discovery freshness ve command SLA. Bakimdan once: sessions, drain/maintenance, target version/commit ve rollback. Sonra: service active/enabled, fresh heartbeat, healthcheck, policy sync ve configured discovery/relay admission; ardindan incident closure.