CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Spacecoin logo
Spacecoin
DeFi
Token
Binance Alpha
Max Payout
$30,000
Project Overview

The Spacecoin network is a DePIN (Decentralized Physical Infrastructure Network) built on Creditcoin, providing global, crypto-powered, permissionless internet and data services. It enables users and operators to access, deliver, and monetize connectivity through a decentralized, blockchain-coordinated infrastructure, while preserving user privacy and ensuring the integrity of transmitted data.

The bug bounty program covers both on-chain and off-chain components of the Spacecoin network:

Smart contract logic (e.g., state management, permissions, and value flows) Blockchain interactions and state transitions supporting internet and data service operations Off-chain systems (e.g., APIs, connectivity coordination services, key management, and operational infrastructure) Cryptographic mechanisms (e.g., signatures, identity, proof generation, privacy-preserving techniques, and data integrity guarantees) Economic and incentive models (e.g., rewards, payments, bandwidth/data usage accounting, reputation, and slashing mechanisms) Interactions between on-chain and off-chain components that enable delivery, verification, settlement, privacy, and integrity of internet/data services

Researchers should pay special attention to:

Trust boundaries between infrastructure providers, users, and protocol components State inconsistencies and race conditions affecting service availability, billing, privacy, or data integrity Authentication and authorization flows for secure and private network/data access Privacy vulnerabilities, including leakage of user identity, usage patterns, or transmitted data Data integrity risks, including tampering, replay, corruption, or unauthorized modification of transmitted or recorded data Economic exploits, including misuse of bandwidth, data accounting, or incentive mechanisms On-chain and off-chain interactions, especially those tied to service delivery, identity, coordination, privacy, and integrity guarantees.

Rewards by Severity
Smart Contract
Web Application
The bounty will be paid out in USD
Assets In-Scope
https://github.com/gluwa
Smart Contract
Smart contracts related to Spacecoin
https://spacecoin.org/
Web Application
Spacecoin related apps
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of project funds
other than unclaimed rewards.
Direct theft of user funds
other than unclaimed rewards.
Permanent freezing of funds.
Unauthorized mint/burn/transfer of crypto assets
Governance voting result manipulation.
Bugs which break core invariants: total supply
fund balances
accounting consistency
access rights
Major
Issues leading to temporary freezing of funds for a limited amount of time.
Theft or permanent freezing of unclaimed yield and rewards.
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration.
Griefing attacks that can damage users or the protocol without profiting the attacker
Limited impact on operation or user experience: bugs that require significant (but not prohibitive) unnecessary gas usage
minor accounting inconsistencies (non-critical)
inefficient logic causing excess fees or degraded UX
edge-case failures (rare inputs)
partial DoS (non-core functionality)
incorrect event emission/logging
Low
Important gas optimizations
Web Application
Critical
Remote code execution enabling attackers to compromise the entire system
Direct theft of user and project's assets(e.g. NFTs
tokens)
Unauthorized access allowing full control over user accounts or wallets
Access to sensitive internal data (private keys
database and server credentials)
Bugs which break core invariants: total supply
fund balances
accounting consistency
access rights
Major
Sensitive user data disclosed for a large amount of users (p.e. physical address
email
phone number)
Access sensitive data from the database through SQL injection
Bypass of essential authentication mechanisms granting administrative privileges
Unauthorized access to functions that modify sensitive user or application data
Server-Side Request Forgery (SSRF) vulnerabilities leading to unauthorized sensitive data access
or manipulation of internal systems
Major logic flaws but not immediate loss
oracle/pricing manipulation (if used)
funds can be locked/frozen (not stolen)
incorrect state transitions (inconsistent balances)
DoS on core functions (deposit
withdrawal
bridging)
weak validation that could become exploitable
incorrect fee/accounting logic
partial bypass of security checks
Medium
Security misconfigurations that could be exploited under certain conditions
Limited Cross-Site-Scripting (XSS)
Malicious redirection without interaction on domains with already-connected wallet
Limited impact on operation or user experience: bugs that require significant (but not prohibitive) unnecessary gas usage
minor accounting inconsistencies (non-critical)
inefficient logic causing excess fees or degraded UX
edge-case failures (rare inputs)
partial DoS (non-core functionality)
incorrect event emission/logging
Low
UI or UX bugs causing serious user confusion
Validation errors that lead to low-security risk
HTML and text injection in sensitive features with a low security risk
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Not following best practices
with no security risk.
Sybil attacks
Centralization risks
Issues with no security or financial impact.
Web Application
Best practice recommendations
Non-Sensitive Data Disclosure
Attacks requiring physical access to a user's device
Exposure of non-sensitive API keys
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Unconfirmed reports from automated vulnerability scanners
Issues that require unlikely user interaction
Previously known vulnerable libraries without a working Proof of Concept
Missing best practices in SSL/TLS configuration
Any activity that could lead to the disruption of our service (DoS)
Email Spoofing - SPF/DMARC Records Misconfiguration
Spam / Flooding
Tab nabbing
Social engineering
Presence of autocomplete attribute on web forms
CORS misconfiguration with no security impact
Self-XSS with no security impact
CSV/formula injection
Missing HTTP security headers or cookie flags without demonstrated impact
Clickjacking with no security impact.
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward., Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact., When duplicates occur we only award the first report that was received (provided that it can be fully reproduced)., Multiple vulnerabilities caused by one underlying issue will be awarded one bounty., Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder., Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services., Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Any testing with mainnet or public testnet contracts
  • all testing should be done on private testnets., Automated testing of services that generate significant amounts of traffic., Public disclosure of an unpatched vulnerability in an embargoed bounty., Social engineering (e.g. phishing
  • vishing
  • smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope2
Live SinceMay 3, 2026
Last Updated1d ago
Funds Reserved$50,000
Max Payout$30,000
Skynet Score
86.57
AA
KYC
Required
PoC
Required
View on Skynet