TerminalChain public testnet — looking for independent validator operators

[innowebstudio]

Hello zibraxter,

Thank you for your interest and for sharing your practical validator and VPS experience. Your experience with Ubuntu, systemd, persistent peers, monitoring, source builds, and testnet operations is relevant to the TerminalChain public testnet.

Please reply publicly in the TerminalChain Cosmos Forum topic with the following verification details before 3 October 2026:

1. Two public validator, RPC, REST, or explorer endpoints you currently operate, with the related network names;

2. Your preferred operating region;

3. Whether you will run validator-only infrastructure or can also provide public RPC/REST;

4. Confirmation that your TerminalChain validator signing key will be generated and retained only by you;

5. Confirmation that you will operate only one TerminalChain validator identity;

6. Whether you participate as a volunteer or require an infrastructure-cost quote.

TerminalChain is a no-value public testnet. There is no mainnet, no purchased node rights, no payment requirement, and no seed phrase, private key, SSH access, or server login will ever be requested.

After verification, selected operators will receive the release package, checksums, genesis SHA-256, timeline, and onboarding instructions.

Best regards,
TerminalChain

[innowebstudio]

Hello everyone,

Operator verification for the first TerminalChain public testnet cohort is now entering its final stage.

To be considered for the initial cohort, please provide the requested verification details by 3 October 2026:

• two public validator, RPC, REST, or explorer references that can be independently checked;

• operating region and intended role;

• confirmation of one validator identity only;

• confirmation that your team will generate and retain its own validator signing key;

• volunteer participation or a clear infrastructure-cost quote.

After the deadline, TerminalChain will select an initial group of four independent validator operators and one or more reserve operators. This is a no-value public testnet: no payment, purchased node rights, private keys, seed phrases, SSH access, or production assets are involved.

Selected operators will then receive a version-pinned release package, SHA-256 checksums, genesis ceremony timeline, chain ID, peer configuration, and onboarding instructions.

Please do not generate TerminalChain validator keys or start servers until selected operators receive the official package.

Thank you.

[jackieluong]

Subject: Re: TerminalChain – Operator verification (jackieluong)

Hello TerminalChain team,

Re-confirming for the final verification stage:

1. Public references: explorer https://jackieluong.com, plus RPC endpoint [điền link RPC nếu đã xong, hoặc “in progress — will share before the deadline”]
2. Region: Germany (Hetzner, Nuremberg); role: validator plus public infrastructure
3. One validator identity only (moniker jackieluong) — confirmed
4. Signing key generated and retained solely by my team — confirmed
5. Volunteer participation — no cost quote needed

One open item from my earlier message: I was unable to access the repository link previously shared (https://github.com/Bimbobeat/terminalchain, 404). Could you confirm the correct repository URL or the forum topic link before the deadline?

Understood — no keys generated and no servers started until the official package is sent.

Best regards,
Jackie (jackieluong)

[lthuan2011]

Posting on behalf of NODESYNC — our NODESYNC forum account is currently unable to reply, so I’m using my personal account temporarily.

Operator: NODESYNC
Handle: @nodesync_top
Website: https://nodesync.top

Public validator references:

1. Services: Services | NodeSync - Trusted PoS Validator, Node Provider
2. Explorer / Validator: https://explorer.nodesync.top

Operating region: Germany (Nuremberg region and nearby regions), with additional infrastructure in the United States and other regions as needed.

Intended role: Independent validator operator for the TerminalChain public testnet, providing reliable validator infrastructure, monitoring, maintenance, and incident response. NODESYNC has also participated in multiple networks from their early testnet and genesis stages, supporting initial network setup and validator operations.

Validator identity: NODESYNC — one validator identity only.

Signing key: NODESYNC will generate and retain its own validator signing key. The key will be securely managed by our team and will not be provided to third parties.

Participation: Volunteer participation. Infrastructure and operational costs will be covered by NODESYNC for the testnet period.

We will not generate TerminalChain validator keys or deploy servers until the official version-pinned package and onboarding instructions are provided.

[nodesync]

I confirm the information above for NODESYNC. It seems the previous user account was restricted because it could not post links. I recreated the account and it is working now. Thank you for understanding.

[Yurii]

Hi TerminalChain team,

BonyNode confirms that our previously submitted verification details remain valid and unchanged for the final operator verification stage.

All requested verification points have been provided in our previous replies.

We remain available for the initial cohort and are ready for the next onboarding and genesis coordination steps.

BonyNode Team

[cryptogemfunds]

Hi! I’m interested in joining the TerminalChain public testnet as an independent validator
NodeSafe is an independent validator and blockchain infrastructure operator focused on validator operations, monitoring, automation, and long-term network participation.

Networks

Prior Validator Experience (list chains)

Cosmos, Polcadots, Solana, Sui, EVM, Cardano: Dymension, Og AI, Pipe, Pallanom, Nulla, Dwall, Sei, Subspace, Chainbase, Aligned Layer AVS..

Active Mainnet (Validator):
Tellor, OG AI Alignment, Jay Network, Lumen, Epix, Safrochain, NexaRail

Active Testnets (Validator-Minner):
Gnoland, Logos, QuipNetwork, Republic AI, Safrochain, Sunima, Push Chain, Latanda, Emperria, Paraloom, Structs, Fortytwo, Netrum…

Previous Testnets:
OG AI, Dymension, Nillion, Entangle, Tanssi, Side Protocol, Chainbase, Story, Aligned Layer, Galactica, Union, Avail, Nullion, Taiko, Subspace, NuLink, Dusk… and other blockchain ecosystems…

Digital Presence:

Explorer: https://explorer.nodesafe-app.xyz

X (Twitter): NodeSafe (Ø,G)|| 🍚 ⛓ (@CryptoGemFunds) / X

GitHub: cryptogemfunds (NodeSafe) · GitHub

Contact Details:

Email: cryptogemfunds@gmail.com

Telegram: Telegram: Contact @cryptogemfunds

Discord: cryptogemfunds

[zibraxter]

Hello TerminalChain team,

Thank you for the verification request.

1. Currently operated public infrastructure

La Tanda Chain testnet

RPC: 213.199.43.108:26657

P2P: 213.199.43.108:26656

HashKinetics

Public node endpoint: 213.199.43.108:27000

2. Preferred operating region: EU
3. Validator only or public RPC/REST: I can operate as a validator only operator and can provide public RPC/REST infrastructure if required.
4. Validator signing key: I confirm that the TerminalChain validator signing key will be generated and retained only by me and will not be shared.
5. Validator identity: I confirm that I will operate only one TerminalChain validator identity.
6. Infrastructure: Volunteer operator, I am not requesting an infrastructure cost quote at this stage.

Regards,
zibraxter

[innowebstudio]

Hello @Yurii @HostDeFi @jackieluong @zibraxter,

You have been provisionally selected for the first TerminalChain public testnet validator cohort.

Please reply by 6 October 2026 confirming that you are still available to participate as one independent validator operator.

This is not genesis activation yet. Do not generate or share any TerminalChain seed phrase, private key, keyring, runtime file, node ID, or consensus key at this stage.

After availability is confirmed, TerminalChain will begin the final release and genesis-ceremony preparation. Selected operators will later receive a tagged release package and will be asked only for public technical data required for genesis coordination.

The testnet remains no-value and volunteer-based. No payment, purchased node rights, production assets, or promised rewards are involved.

@Yurii and @HostDeFi: please also state whether either organization can volunteer to operate a separate non-validator public RPC/REST node or seed/sentry node. This is optional and does not affect validator selection.

Thank you.

[HostDeFi]

Hello TerminalChain team,

Confirming that HostDeFi is still available to participate as one independent validator operator in the first public testnet cohort.

1. Currently operated public infrastructure
2. Solana testnet validator (voting at tip, credits above cluster average), Celestia mocha-5 validator (active, signing), Charon/Obol DVT cluster. Public TerminalChain RPC/REST endpoints will be exposed once the tagged release ships.
3. Preferred operating region: US.
4. Validator only or public RPC/REST: We can volunteer a separate non-validator public RPC/REST (or seed/sentry) node in addition to the validator.
5. Validator signing key: The TerminalChain validator signing key will be generated and retained only by HostDeFi and will not be shared.
6. Validator identity: We will operate only one TerminalChain validator identity.
7. Infrastructure: Volunteer operator; not requesting an infrastructure cost quote at this stage.
   Regards,
   HostDeFi

[jackieluong]

Hello TerminalChain team,

Thank you for the update. Confirming: I (jackieluong) remain available to participate as one independent validator operator in the first cohort.

I understand this is not genesis activation yet, and I will not generate or share any TerminalChain seed phrase, private key, keyring, runtime file, node ID, or consensus key until the official package and instructions are sent.

Looking forward to the release package and genesis-ceremony timeline.

Best regards,
Jackie (jackieluong)

[zibraxter]

Hello,

Thank you for the update. I confirm that I am still available and willing to participate as an independent validator operator in the first TerminalChain public testnet validator cohort.

I understand that this is not genesis activation yet and that I should not generate or share any seed phrase, private key, keyring, runtime file, node ID, or consensus key at this stage.

I look forward to the next instructions for the release and genesis ceremony preparation.

Best regards,
zib

[HostDeFi]

Hey — saw your validator-coordination post. We run bare-metal validators: live Solana mainnet, testnet voter, plus Cosmos-side ops through an SSV operator and two DVT clusters, a Babylon finality provider and EigenDA ops. We keep our own keys, run our own RPC endpoints, and have an org site behind the operation. Happy to stand up a node on your public testnet and be part of the first independent set — what do you need from applicants?

[Yurii]

Hello,

BonyNode confirms that we are available to participate as one independent validator operator in the first TerminalChain public testnet cohort.

We can also volunteer to operate a separate non-validator public RPC/REST node for the testnet.

We understand that this is not genesis activation yet and will not generate or share any TerminalChain keys or runtime data until the official release package and genesis coordination instructions are published.

Ready for the next release and genesis-ceremony preparation steps.

BonyNode Team

[innowebstudio]

Hello HostDeFi,

Thank you. HostDeFi has been provisionally selected for one validator position in the first TerminalChain public-testnet cohort.

Please reply to confirm that your organization remains available to operate exactly one independent validator identity in this cohort and will not generate or share any TerminalChain key, node ID, or consensus key until the official package and ceremony instructions are published.

The immediate next step after confirmation will be final release and genesis-ceremony preparation. No payment, purchased node rights, production assets, or validator rewards are involved.

Best regards,
TerminalChain

[HostDeFi]

Hello TerminalChain team,

Confirming: HostDeFi remains available to operate exactly one independent validator identity in the first TerminalChain public-testnet cohort.

We will not generate or share any TerminalChain key, node ID, or consensus key until the official package and ceremony instructions are published.

Ready for the final release and genesis-ceremony preparation.

Best regards,
HostDeFi

[innowebstudio]

Hello HostDeFi,

Thank you for the confirmation. The first TerminalChain public-testnet validator cohort is now complete.

The next stage is final release and genesis-ceremony preparation. We will publish the tagged release package, verification instructions, ceremony timeline, and the exact public technical-data request before any operator generates TerminalChain keys or starts a node.

Best regards,
TerminalChain

[innowebstudio]

The first TerminalChain public-testnet validator cohort is now moving into the pre-genesis verification stage.

Selected operators should join the private coordination group here:

TerminalChain Public Testnet

The verification package is tied to v0.1.0-public-testnet.1 for terminalchain-public-testnet-1.

Before submitting any operator information, please independently verify the distributed Linux binary against this SHA-256:

0e96c70271679cef7aabd8ce77772ee51d0ce4d0a9b083b4932f81bc64ab13f6

At this stage we request only public operational data: operator name, contact, region, consensus public key, node ID and planned P2P address.

Do not publish or send any mnemonic, private validator key, node key, keyring or validator runtime files. Genesis construction and node startup are not part of this stage.

[jackieluong]

Operator name: jackieluong
Contact: tuanlga@gmail.com , telegram : @jackieluong
Region: Germany (Hetzner, Nuremberg)
Consensus public key: {"@type":"/cosmos.crypto.ed25519.PubKey","key":"9TWaCXmKsA4+SSaxBVVKnkiy4Ch4oy3ruVMjNqqI8QY="}
Node ID: 7063ad1dca0aed5a5d3560bfdde351fa35818b2f
Planned P2P address: 116.203.238.65:36656

[innowebstudio]

Hello zibraxter,

We are collecting the final public ceremony inputs for the selected public-testnet cohort.
Join to the telegram group. We are waiting only for you..

Please send only:

Operator name:
Contact:
Region:
Consensus public key:
Node ID:
Planned P2P address:

Do not send a seed phrase, private key, keyring, validator state file, or any runtime data.

Thank you,
TerminalChain