This repository provides static data and assets related to Qubic blockchain. It serves as a single, reliable source of structured data for developers, explorers, wallets, dashboards, and analysis tools.
Available at: https://static.qubic.org/v1/general/data/
- Smart contracts — names, indexes, procedures, GitHub source links, and addresses
- Exchanges — known trading platforms and their Qubic addresses
- Tokens — additional token information
- Address labels — relevant Qubic addresses
Available at: https://static.qubic.org/v1/wallet-app/
- DApp Explorer - Curated list of DApps with multilingual support (7 languages: EN, DE, ES, FR, RU, TR, ZH)
- Mobile wallet configuration files
⚠️ IMPORTANT WARNINGThe
wallet-appdata is NOT intended for public consumption or third-party use. This data is maintained exclusively for the official Qubic Wallet application.
- ❌ No stability guarantee - Breaking changes may occur at any time without notice
- ❌ No support - We do not provide support for third-party usage
- ❌ No responsibility - We are NOT responsible for issues arising from third-party use
- ❌ No API contract - Structure and content may change without warning
If you need this data: Fork the repository and maintain your own copy. You assume all risks.
See products/wallet-app/README.md for full details.
Note: Currently, wallet-app is the only product-specific data. Additional products may be added in the future as the ecosystem grows.
Base URL: https://static.qubic.org/v1/general/data/
-
Smart Contracts
-
Exchanges
-
Tokens
-
Address Labels
-
Bundle (All files combined)
-
Version Tracking
- version.json - Contains file hashes and sizes for cache invalidation
Base URL: https://static.qubic.org/v1/wallet-app/
- DApp Explorer
- dapps/dapps.json - Curated DApp catalog
- Locales:
dapps/locales/{lang}.json(en, de, es, fr, ru, tr, zh) - Want to add your DApp? See How to Contribute section below
This repository supports three deployment environments:
- Production:
https://static.qubic.org/v1/- Stable releases (e.g., v1.2.3) - Staging:
https://static.qubic.org/staging/v1/- Release candidates (e.g., v1.2.3-rc.1) - Dev:
https://static.qubic.org/dev/v1/- Development testing
Production: https://static.qubic.org/v1/{product}/{path-to-file}
Staging: https://static.qubic.org/staging/v1/{product}/{path-to-file}
Dev: https://static.qubic.org/dev/v1/{product}/{path-to-file}
General Data:
https://static.qubic.org/v1/general/data/smart_contracts.json
https://static.qubic.org/staging/v1/general/data/smart_contracts.json
Wallet App:
https://static.qubic.org/v1/wallet-app/dapps/dapps.json
https://static.qubic.org/v1/wallet-app/dapps/locales/en.json
Each product includes a version.json file for efficient cache management:
// Fetch version metadata
const versionData = await fetch('https://static.qubic.org/v1/wallet-app/version.json')
.then(r => r.json());
// Compare file hashes with cached versions
for (const [filename, metadata] of Object.entries(versionData.files)) {
if (cachedHashes[filename] !== metadata.hash) {
// Hash changed → download new file
await downloadFile(filename);
}
}The version.json contains SHA-256 hashes and file sizes for all files, enabling apps to:
- Only download changed files
- Properly invalidate caches
- Verify file integrity
data/ # General/shared source data
├── smart_contracts.json
├── exchanges.json
├── tokens.json
└── address_labels.json
products/ # Product-specific source data
└── wallet-app/
└── dapps/
├── dapps.json
└── locales/
scripts/ # Build and update utilities
├── build_dist.py # Build distribution files
└── update_smart_contracts.py # Update SC data from GitHub
.github/workflows/ # CI/CD automation
├── commitlint.yml # Commit message validation
├── lint-pr.yml # PR title validation
└── deploy.yml # Automated deployments
This repository uses GitHub Actions with semantic-release for automated versioning and deployments.
Follow Conventional Commits:
feat:- New features (triggers MINOR version bump)fix:- Bug fixes (triggers PATCH version bump)docs:- Documentation changes (no version bump)chore:- Maintenance tasks (no version bump)
Examples:
feat: add proposalUrl field to smart contracts
fix: correct address calculation for contract index 166
docs: update README with new structure
- Dev - Push to
devbranch → deploys to dev environment (no versioning) - Staging - Push to
stagingbranch → creates RC tag & GitHub pre-release → deploys to staging - Production - Push to
mainbranch → creates version tag & GitHub release → deploys to production
- Development - Make changes in feature branches using conventional commit messages
- Dev Testing - Merge to
devbranch → auto-deploys to dev environment - Staging - Merge to
stagingbranch → semantic-release creates RC tag & deploys - Testing - Test on staging environment
- Production - Merge
stagingtomain→ creates release & deploys to production
Semantic-release automatically:
- Analyzes commit messages
- Determines version numbers
- Creates GitHub releases
- Generates changelogs
- Triggers deployments
Contributions are welcome! Here's how you can help:
DApps for Wallet Explorer
- Add your DApp to the curated explorer list in
products/wallet-app/dapps/dapps.json - Include title and description translations in all 7 languages:
products/wallet-app/dapps/locales/*.json(en, de, es, fr, ru, tr, zh) - Provide app URL, icon (set "" when not available)
- An example can be seen here #24
Exchange Addresses
- Add new exchange addresses to
data/exchanges.json - Include exchange name and Qubic address
Token Information
- Add complementary token data to
data/tokens.json - Reference tokens by name (not all tokens need to be listed, only those with additional metadata)
Address Labels
- Add relevant Qubic addresses to
data/address_labels.json - Include descriptive labels for known addresses
Smart Contract Custom Data
- Add custom fields or metadata to existing smart contracts in
data/smart_contracts.json - Note: Core fields (name, contractIndex, address, procedures) are auto-generated. Open an Issue for corrections to these fields rather than submitting PRs
- Fork the repository
- Create a feature branch with conventional commit format (e.g.,
feat: add new exchange address) - Submit a Pull Request to the
devbranch - Changes will be tested in dev → staging → production environments by the Fronted Apps Team