Are you developing the application yourselves? Why don't you have a GitHub account? Also, are you planning to open a Discord channel? What are your next plans? Do you have a roadmap? I'm asking these questions because they're not mentioned in the topic or on your website.
There isn’t a “company” here to publish corporate promises.
There is software and a running network. The only authority is what code nodes and miners choose to run.
Why no GitHub account?GitHub is a hosting site, not a trust model.
A single “official repo” quickly becomes a single point of:
- account compromise
- takedown pressure
- social trust confusion (“official” vs “safe”)
- quiet history edits people don’t notice
Mirrors are healthy. If a GitHub/GitLab mirror is useful, make one:
- mirror the source
- publish hashes/signatures
- document reproducible builds
- keep multiple independent copies online
Discord / chat channel?Real‑time chat is fine for support, but
it should not be treated as governance.
If a Discord helps, start one and run it as a community channel.
Best practice:
- keep Bitcointalk / long‑form posts as the canonical record
- use community‑run Discord/Telegram for support
- pin links back to canonical docs and releases
- avoid treating chat as governance
Next plans / roadmap?A roadmap usually turns into promises and deadlines, then into disappointment.
A better approach is a public, living priority list that anyone can pick up:
Near‑term priorities (boring but important):- stability: syncing, peers, reorg handling, clear error messages
- mining/pool UX: fewer gotchas, better docs, known‑good configs for common miners
- wallet UX: balance clarity, send flow, auto‑shield / consolidation that “just works”
- reproducible builds + signed artifacts
- more independent pools / explorers / mirrors (fewer choke points)
Concrete ways to help right now:- run a full node and report real bugs with logs + exact versions
- mirror releases and publish checksums/signatures
- write a step‑by‑step guide for a specific OS/miner combo and keep it updated
- run a pool or a public endpoint and document the setup
- build a simple GUI wrapper/installer and ship binaries people can use
No promises needed. Progress is visible in code, releases, and uptime.
If a roadmap is required, the most honest roadmap is:
“ship what gets built, keep what stays stable.”If someone spins up a mirror / Discord / repo, post the link in this thread and it can be indexed in the OP.
