Wallet secrets
Tenzarch should never require a private key or recovery phrase.
Use consistent terminology across the website, product, documentation, and developer surfaces, and keep privileged credentials inside the correct trust boundary.
Tenzarch should never require a private key or recovery phrase.
Store programmatic credentials server-side and scope them narrowly.
Database connection strings and privileged service credentials belong only in backend environment configuration.
Do not place privileged secrets in browser-exposed environment variables.
The coordination system connecting workload demand, execution state, orchestration, routing, distributed capacity, observability, and results.
A user-facing AI experience that submits workloads.
A reusable developer-facing execution capability.
The trackable record of an individual workload.
The orchestration record coordinating execution lifecycle around a Job.
Distributed processing infrastructure eligible for assignment under network conditions.
The wallet-associated participation entry point.
Usage accounting for workload execution.
A separate program for qualifying node participation.
The accounting unit used by the Node Rewards program.