This is the public queue for reporting issues, bugs, and ideas about Arkiv — the Web3 database, powered by $GLM.
If you've hit a bug, run into unexpected behaviour, or have an idea you'd like the team to consider, this is the place.
- Head to New issue.
- Pick the form that matches what you want to report:
- Bug or network issue — something is broken or behaving unexpectedly.
- Feature request or idea — you'd like Arkiv to do something it doesn't yet.
- Fill in the form. The more detail you give us up front, the faster we can help.
Before reporting, please:
- Check the documentation — your question may already be answered there.
- Search existing issues so we don't duplicate work.
- For general questions or quick chats, drop into the Arkiv Discord first.
Every issue lands on the team's triage queue. A maintainer will:
- Acknowledge the report and apply the right labels.
- Ask for more info if the form didn't capture enough to act on.
- Decide whether it's a real bug, a usage question, a known limitation, or a feature we'll consider.
- Link the issue to a tracking ticket if engineering is going to work on it, or close it with a clear explanation if not.
We aim to get to new reports within a few working days. If something is urgent (e.g. the network is down for you), please flag that in the report and we'll prioritise.
Do not open a public issue for security vulnerabilities. Please report them privately through GitHub Security Advisories.
This repository is for reports about Arkiv itself — the protocol, SDKs, tooling, docs, and website. For issues with applications built on Arkiv, please report them to the application's own team in the first instance.
Arkiv is in active development. Honest reports — even rough ones — make the product better. Thanks for taking the time.