Skip to content

Gateway allowlist request #1824

Open @samuelonn1993 opened 2026-09-23 12:01 UTC 6 comments Updated 2026-09-23 20:38 UTC

Gateway allowlist request

Operator

  • Name: Samuel Onn
  • GitHub: @samuelonn1993

Creator address

gonka1u54tux4u26vy9s207088v607a0kkjr9tgxsqdl

Please consider adding this address to:

devshard_escrow_params.allowed_creator_addresses

Intended models

  • MiniMaxAI/MiniMax-M2.7
  • deepseek-ai/DeepSeek-V4-Flash-0731
  • zai-org/GLM-5.3-Flash

Use case

Personal, private, single-user self-hosted gateway for my own AI-assisted software development.

The gateway will initially run locally on my own Windows PC and will be used on demand. It is not intended to operate as a public inference service or broker.

I will fund the creator address only after allowlist membership has been confirmed on-chain.

💬 Comments (6)

@tcharchian commented 2026-09-23 18:20 UTC

Hi @samuelonn1993!

Allowlisting is an on-chain governance decision, so this registers intent but timing/inclusion aren't guaranteed. Before waiting on that, one question, since it changes the fastest path: for personal, on-demand coding use, do you actually need to self-host?

If what you need is just a private OpenAI-compatible endpoint for your own AI-assisted development, that exists today via OpenBroker (https://github.com/gonka-ai/gonka/discussions/1363, https://openbroker.gonka.gg): GNK-native, no markup (1-to-1 with escrow cost), streaming + tool calls, no enrollment or governance wait — you'd be pointing your coding tools at it within minutes, and it fits on-demand use well since you only spend against actual usage.

If you try it and something doesn't fit, say so here.

@samuelonn1993 commented 2026-09-23 18:56 UTC

Hi @tcharchian

Thanks for the clarification.

Yes, I specifically want to self-host my own gateway. My goal is to run a private, single-user gateway for my own AI-assisted development, initially on my own Windows PC and potentially move it to my existing Linux VPS later.

The gateway would be used on demand for my own development and is not intended to operate as a public inference service or broker.

I understand that allowlisting is an on-chain governance decision and that timing and inclusion are not guaranteed. I am willing to wait for the governance process rather than use OpenBroker.

If my creator address is eventually added to the allowlist, is there any way I would be notified or informed that the request has been processed?

Thank you for registering the request.

@tcharchian commented 2026-09-23 19:53 UTC

To be clear, though: this issue isn't a promise or a queue with a guaranteed outcome — it just records your intent. Allowlisting is an on-chain governance decision, so inclusion and timing aren't guaranteed. Worth knowing that, since it's governance, submitting a param-change proposal for devshard_escrow_params.allowed_creator_addresses is itself an option open to anyone — just so you're aware of the path, not something you have to do.

No automated notice when/if it lands (it's decentralized), so to track it: watch on-chain governance / upgrade release notes, or query devshard_escrow_params.allowed_creator_addresses directly any time.

@samuelonn1993 commented 2026-09-23 20:14 UTC

Thanks for clarifying.

Just to make sure I understand the process correctly: is my current Issue #1824 request sufficient for my creator address to be considered for inclusion in the allowlist, or would I need to submit a formal governance proposal myself?

I understand that neither route guarantees inclusion; I just want to make sure I am using the right process.

@tcharchian commented 2026-09-23 20:25 UTC

Short answer: this issue is a valid way to register intent. But it's not the only route: since allowlisting is on-chain governance, you can always pursue it yourself directly — submitting a param-change proposal and building support for it in the community is an option open to anyone at any time. So you're not limited to waiting on a batch; you can drive the outcome through governance yourself if you prefer.

What helps your odds either way: visibility and contribution in the community, a track record/reputation, and more detail about your project and why the creator address matters for it. Concrete context — what you're building, how you'll use the gateway, and your engagement in Gonka Discord and other community chats makes an address much easier to include. None of that guarantees inclusion or timing, but it meaningfully strengthens the case.

@samuelonn1993 commented 2026-09-23 20:38 UTC

Thanks for clarifying. That makes sense.

I’ll keep my request on Issue #1824 for now and wait for the governance process. I’ll also monitor the on-chain allowlist for my creator address.

I appreciate the explanation.

🔄 Auto-synced from Issue #1824 every hour.