Community
hashspan is built in the open by its maintainer and contributors. The most useful contribution right now is feedback from people who trace agents that send transactions.
Ways to contribute
Review the span names
The semantic conventions are a draft. Tell us what is missing or named wrong for the transactions your agents send.
Semconv feedback →Pick a good first issue
Small, scoped tasks with the files to touch and how to test them.
Good first issues →Request an adapter
Sending with something hashspan does not trace yet, such as ethers or a smart account? Say which.
Ideas →Show your traces
Running hashspan with your agent? Share a screenshot of the trace and what it helped you find.
Show and tell →Improve the docs
Backend guides, examples and fixes to anything that was unclear when you set it up.
Docs issue #35 →Good first issues
Open now, pulled from GitHub at build time.
GitHub Discussions
Questions and ideas go to Discussions, so the answers stay public and searchable. Bugs go to Issues.
From clone to pull request
The short version of the contributing guide. macOS or Linux (WSL on Windows).
- 1
Set up
nvm use corepack enable pnpm pnpm installNode.js from .nvmrc, pnpm through corepack.
- 2
Run the tests
make tools pnpm test pnpm test:integrationIntegration tests run against a local Anvil chain, never a public network.
- 3
See it in a trace
make lab-up make demoJaeger on localhost:16686. make lab-nuke removes everything again.
- 4
Open a pull request
pnpm lint pnpm typecheck pnpm changesetA changeset is needed for user-visible changes only.
AI-assisted contributions
You may use AI coding tools, but you are responsible for what you submit: you understand every change, have run the checks, and can explain and adjust it in review. Pull requests that look generated without that care may be closed.
Contributors
Your name here: start with a good first issue.