TerminalChain public testnet — looking for independent validator operators

I am building TerminalChain, an independent Cosmos SDK blockchain focused on fixed-supply TML payments and wallet integration. Current development status: • fixed maximum supply of 1,000,000 TML; • deterministic genesis allocations; • no post-launch minting permissions; • native TML transfers; • fixed-pool staking and unstaking; • verified airdrop module; • milestone reward module; • launch governance and economic safety protections; • successful four-validator local testnet; • transaction, restart, recovery and validator-offline resilience tests; • integration work with the TERMINAL wallet interface. Source code: https://github.com/Bimbobeat/terminalchain The next milestone is a public testnet operated by independent participants. I am looking for experienced Cosmos SDK node operators willing to help with: • running independent testnet validators; • reviewing validator onboarding documentation; • testing genesis coordination and restart recovery; • reporting network, RPC and consensus issues; • improving operational decentralization. This is a testnet only. TML has no guaranteed monetary value, there is no promised validator income, and this…

Excerpt (1197 of 1554 characters). Read the whole post on the forum ↗

Hi! I’m interested in participating as an independent validator. I have previous experience running Cosmos-based testnet validators, including Latanda, and currently operate several blockchain nodes on VPS infrastructure. I’d be happy to help test TerminalChain and provide feedback during the public testnet.

Hi! I’m interested in joining the TerminalChain public testnet as an independent validator.

I’m operating UTSA, a multi-network validator and infrastructure provider with extensive Cosmos SDK experience. We currently operate validators across multiple networks and also provide public RPC/API endpoints, snapshots, monitoring, guides and explorer infrastructure.

I tried the GitHub repository linked in your post, but it doesn’t seem to be accessible at the moment.

Could you please share the current repository and validator onboarding instructions? I’d be happy to join as an early testnet operator and help with testing and infrastructure.

Hi,

BonyNode would be interested in joining the TerminalChain public testnet as an independent validator operator.

We operate validator and node infrastructure across multiple Cosmos SDK / CometBFT networks, including mainnet and testnet environments, and maintain our own monitoring and operator infrastructure.

We can help with validator operation, genesis coordination, restart/recovery testing, RPC and consensus monitoring, and feedback on validator onboarding documentation.

Please let us know the next steps for joining the public testnet and whether validator onboarding/genesis coordination has already started.

Hi! I’m interested in participating as an independent validator.

Thank you for your interest in TerminalChain.

The public testnet is currently in the validator-coordination stage; genesis ceremony has not started yet. I am first confirming the public repository and preparing the final operator onboarding package.

Before I add anyone to the first operator cohort, please reply with:

• your organisation website and official contact channel;
• two public validator or RPC endpoints you currently operate;
• your preferred region and whether you can provide validator-only infrastructure or also public RPC/REST;
• confirmation that you will generate and retain your own validator keys.

No seed phrase, private key, server login or payment is required. This will be a no-value public testnet.

Once operator identities and the release package are verified, I will share the testnet timeline, signed binary checksum, genesis SHA-256 and onboarding process.

Thank you. I have confirmed that the repository is publicly accessible:

The public testnet is still in the validator-coordination stage, so genesis onboarding has not started yet. I will publish the final operator runbook, release checksum and genesis coordination process after verifying the initial operator cohort.

We are updating our website, but in the meantime, you can check out our services, guides, and explorer:
Services: 𝐔𝐓𝐒𝐀 | Services
Guides: lesnik13utsa — Teletype
Explorer: https://explorer.utsa.tech/
TG: @lesnik13utsa
Discord: lesnik_utsa

Hi, thanks for the update.

BonyNode confirms our interest in joining the first TerminalChain public testnet validator cohort.

Website: bonynode.online
Contact: support@bonynode.online
Explorer: explorer.bonynode.online

discord: bonynode

tg: @cryptobony

Preferred region: Europe.

We can operate the validator and provide services, explorer and public RPC / REST / gRPC infrastructure

Monitoring: monitor.bonynode.online

Public infrastructure examples:

• Provenance RPC: provenance-mainnet-rpc.bonynode.online

• AtomOne RPC: atomone-mainnet-rpc.bonynode.online

Ready for the next onboarding and genesis coordination steps.

Thank you for the clarification. I’m happy to provide the requested information.

• Organisation: Jackie Lương
• Website: jackieluong. com
• Official contact: X: @jackieluong / Discord: jackieluong
• Validator experience: I have been actively participating in blockchain validator and testnet programs for more than 2 years. Projects I have operated or participated in include Aptos, Celestia, Avail, Pactus, Gora, Pion, Massa, Tanssi, OG, NexaRail, KiiChain, BitBadges, Latanda, Dasi, and other early-stage testnets.
• Preferred region: Germany / EU (Hetzner)
• Infrastructure: I can provide validator-only infrastructure, and I can also operate public RPC/REST endpoints when required.
• Validator keys: Confirmed. I will generate, secure, and retain my own validator keys. No seed phrase or private key will be shared.

I understand this is a no-value public testnet and that the genesis ceremony has not started yet. I’ll wait for the release package, signed binary checksum, genesis SHA-256, timeline, and onboarding instructions.

Looking forward to participating in the first operator cohort.

Hi Innowebstudio,

I came across your update about coordinating the first TerminalChain public testnet validator cohort and wanted to congratulate you on the same.

I noticed you are also looking for validator RPC infrastructure. We at Instanodes run managed validator and RPC infrastructure for 50+ chains and a guaranteed 99.95% uptime, including 24/7 monitoring and operational support.

We have the capability to support Terminal Chain on testnet. Should you prefer, we can provide a demo first, ahead of any commitment to scale

Best,
Ishan

Thank you — TerminalChain is now forming its first no-value public testnet cohort.

Before genesis coordination, please provide:

1. two currently operating public validator, RPC, or explorer endpoints that we can independently verify;
2. your preferred region and whether you will operate validator-only or also public infrastructure;
3. confirmation that your TerminalChain validator signing key will be generated and retained only by your team;
4. confirmation that you will operate only one TerminalChain validator identity for the initial cohort;
5. whether your participation is volunteer-based or requires an infrastructure-cost quote.

No seed phrase, private key, server login, payment, or genesis key is requested at this stage. After operator verification, we will publish the release package, binary checksum, genesis SHA-256, timeline, and onboarding instructions.

Hello TerminalChain team, Thank you for the update. Below are my answers: 1. Verifiable endpoints • Public explorer: https://jackieluong.com (multi-chain explorer I operate) • Public RPC: [ https://rpc.jackieluong.com – after setup finish] Both can be checked independently. I have been operating validators on several public testnets for over 2 years under the moniker `jackieluong`. 2. Region and role • Region: Europe (Germany, Hetzner Nuremberg) • Role: validator plus a public explorer/RPC endpoint 3. Key custody Confirmed. The TerminalChain validator signing key will be generated and retained only by my team. It will never be shared, and I understand no key is required at any stage. 4. Identity Confirmed. I will operate only one TerminalChain validator identity (moniker: `jackieluong`) for the initial cohort. 5. Cost model Volunteer-based. No infrastructure-cost quote is required. Before I prepare the servers, could you share your official website, GitHub repository and official community channel (Discord/Telegram/X) so I can verify them? Please also confirm that the testnet requires no bonded or purchased node rights and that there is no…

Excerpt (1193 of 1324 characters). Read the whole post on the forum ↗

Hello Jackie, Thank you for the detailed response and for confirming independent key custody, one validator identity, and volunteer participation. TerminalChain is currently in the validator-verification stage for a no-value public testnet. There is no TerminalChain mainnet yet. Official project repository: https://github.com/Bimbobeat/terminalchain For now, the official coordination channel is this Cosmos Forum topic and the GitHub repository/issues. We will publish an additional community channel before the genesis ceremony. To confirm the testnet model: • no validator must purchase node rights; • no real-value TML, treasury funds, or production keys will be used; • validator keys are generated and retained by each operator only; • testnet validator bonding, if required by the Cosmos genesis process, will use test-only genesis funds only; • no mainnet participation or future rewards are promised through this testnet. Your Germany / Hetzner location, validator-plus-public-infrastructure role, and volunteer model are noted. Before final selection, we will verify the public references and aim to avoid concentrating multiple validator identities…

Excerpt (1195 of 1455 characters). Read the whole post on the forum ↗

Hello TerminalChain team,

Thank you for confirming the testnet model. It matches the terms I am looking for: no purchased node rights, test-only funds, operator-held keys, and no promised rewards.

I could not open https://github.com/Bimbobeat/terminalchain (it returns a 404 on my side). Could you please:

1. share the direct link to the Cosmos Forum topic;
2. confirm whether the repository is currently private or provide the correct URL?

I will prepare my public RPC endpoint in the meantime and share it for verification. I will not run any binary until the repository or release package and its SHA-256 checksum are publicly available.

Best regards,
Jackie (jackieluong)

Hi,

Following up on our previous BonyNode submission:

1. Key custody: Confirmed. The TerminalChain validator signing key will be generated and retained only by the BonyNode team.
2. Validator identity: Confirmed. BonyNode will operate only one TerminalChain validator identity for the initial cohort.
3. Participation model: Volunteer-based. No infrastructure-cost quote is required.

Our previously provided public endpoints, Europe region, and validator + public infrastructure availability remain unchanged.

Ready for operator verification and the next genesis coordination steps.

BonyNode Team

Hello TerminalChain team I’d like to join the public testnet cohort as an independent validator operator.

Answers to your verification points:

1. Verifiable public endpoints: I operate a public multi-chain RPC relay serving 80+ networks at rpc[dot]hostdefi[dot]com (the /ethereum path responds to standard eth_chainId calls). I also run validator seats on several Cosmos SDK testnets and an SSV operator node happy to demonstrate any on-chain.

2. Region and role: EU-based cloud infra; validator plus public infrastructure (RPC/API endpoints).

3. Key custody: Confirmed. The TerminalChain validator signing key will be generated and retained only by my team never shared with anyone.

4. Identity: Confirmed. I will operate only one TerminalChain validator identity for the initial cohort.

5. Cost model: Volunteer-based. No infrastructure-cost quote required.

Ready for operator verification and the genesis coordination steps.

Hello TerminalChain team - HostDeFi would like to join the public testnet cohort as an independent validator operator. A teammate posted an earlier expression of interest under @devin ; this is the same operation, so please treat this account as the operator contact going forward. About us: HostDeFi is an independent crypto infrastructure operation. We run a live public RPC relay across 80+ chains, a fleet of dedicated cloud boxes under 24/7 monitoring, an AIOZ Network DePIN node, and a Babylon finality provider with a live delegation. We also operate validator and node seats on other testnet and mainnet networks. Answers to your verification points: • Website and contact: `hostdefi.com` - reachable via this forum account. • Verifiable public endpoints: our multi-chain RPC relay at `rpc.hostdefi.com` (the `/ethereum` path answers a standard `eth_chainId` call; 80+ chains are served on the same pattern), and our AIOZ Network node `aioz1gw2w2499pncl25up9g5yr4gzeaav95xutauscm`. Our Babylon finality-provider registration is also visible on-chain and we are happy to share the FP public key for verification. • Region and role: cloud-hosted infrastructure, region flexible…

Excerpt (1192 of 1797 characters). Read the whole post on the forum ↗

Hello everyone, `@jackieluong @Yurii @nodesync @lesnikutsa @HostDeFi @olegshandra1970` `@devin` Thank you for the strong interest in the first TerminalChain public testnet cohort. We now have enough initial operator interest to begin verification and technical preparation. No validator has been selected yet, and the genesis ceremony has not started. Current status: • TerminalChain is a no-value public testnet only; • there is no mainnet; • no validator must buy node rights or provide any payment; • every operator generates and keeps its own validator signing keys; • no seed phrase, private key, SSH access, or server login will ever be requested; • each organization may operate only one validator identity in the initial cohort. We are reviewing public validator/RPC/explorer references, operator independence, region diversity, and infrastructure roles. We also need to keep the public RPC/REST infrastructure separate from validator consensus where possible. The official source repository is: https://github.com/Bimbobeat/terminalchain Once the first cohort is finalized, selected operators will receive the release package, binary SHA-256 checksum,…

Excerpt (1199 of 1517 characters). Read the whole post on the forum ↗

Hi! I’m interested in joining the TerminalChain public testnet validator cohort. I already have hands on experience running and participating in blockchain testnet infrastructure across multiple projects. 1-La Tanda Chain. I’m currently running a testnet node on my own Ubuntu VPS, with persistent peers, systemd service management, continuous syncing, and remote monitoring. 2-HashKinetics. I recently deployed a testnet validator/node on my VPS, including building the node from source, configuring the validator home and peers, syncing the chain, and running it as a persistent systemd service. 3-Retium. I have a validator seat and am actively participating in the Retium validator testing phase. 4-Asentum. I’m also running an Asentum testnet node and participating in its validator/operator testing. Through these projects, I’ve gained practical experience with Linux/Ubuntu, VPS administration, compiling blockchain nodes from source, peer configuration, chain synchronization, systemd, monitoring, and troubleshooting node issues. I’d be excited to contribute to TerminalChain from the early testnet stage and operate a reliable, continuously online validator. I’m ready to…

Excerpt (1198 of 1386 characters). Read the whole post on the forum ↗

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: • Two public validator, RPC, REST, or explorer endpoints you currently operate, with the related network names; • Your preferred operating region; • Whether you will run validator-only infrastructure or can also provide public RPC/REST; • Confirmation that your TerminalChain validator signing key will be generated and retained only by you; • Confirmation that you will operate only one TerminalChain validator identity; • 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,…

Excerpt (1192 of 1290 characters). Read the whole post on the forum ↗

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.

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)

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: • Services: Services | NodeSync - Trusted PoS Validator, Node Provider • 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…

Excerpt (1198 of 1376 characters). Read the whole post on the forum ↗

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.

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

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:…

Excerpt (1198 of 1249 characters). Read the whole post on the forum ↗

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

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

Regards,
zibraxter

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.

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

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)

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

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?

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

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

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

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

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.

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

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

Congrats and good on you for having the guts to move forward with so much FUD. Will you please share your website and any marketing plans you can, and how many people are on your team?

MekongLabs is interested in joining the TerminalChain public testnet as an independent validator operator. We have experience running Cosmos ecosystem nodes and validators, and would be happy to contribute to testing, network stability, and decentralization. Let’s connect! @innowebstudio