{"type": "project", "title": "WEB3SDR", "logoImg": "bafkreifpwlnpdn4elmg6lfo4x6bqkwjxxc4ove542rpm53xctokrk5ef3e", "website": "https://web3sdr.xyz/", "bannerImg": "bafkreibu6liogarsm4ct2dnpwowbk7s76l7eo2yzkte6fzjkfsbesphoiu", "createdAt": 1728733273370, "userGithub": "carzygod", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..iG523ymz2a4rbwXSSiku0GphZ7ymihhE-prrNIalJwSjyy4OnKqZ0WygFQWlbs5v5xdc83jm-fCTeoO8GOrlAA", "type": "Ed25519Signature2018", "created": "2024-10-12T11:40:33.921Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-12T11:40:33.921Z", "expirationDate": "2025-01-10T11:40:33.921Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xA773B474C0432E5E936C4580Ff3B514cb89b9dB9", "hash": "v0.0.0:N57kNEo2XAi26NvGQTF1Ba6jMmsFEEg6ftRfZ56EG3M=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#Web3sdr#32446081"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..5JpnaXXmY8xXdwT1sbmOLmhfwFHPsYel7U7KkRvCGKUM3Wg3UijvSDlm9Rw2U0xM20GuaV9cRsHl7KQieL8kAA", "type": "Ed25519Signature2018", "created": "2024-10-12T11:39:21.009Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-12T11:39:21.009Z", "expirationDate": "2025-01-10T11:39:21.009Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xA773B474C0432E5E936C4580Ff3B514cb89b9dB9", "hash": "v0.0.0:BT/5XebApqYKPrvIkmv4XadUBYQnqA7Euajz9VtxbHk=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#web3sdr"}}}, "description": "Web3SDR is a decentralized physical infrastructure network (DePIN) that integrates Software-Defined Radio (SDR) technology with the power of blockchain. Web3SDR transforms the traditional WebSDR platform into a decentralized, scalable, and tokenized system where SDR clients can contribute data from radio signals between 1 MHz and 160 MHz (AM/FM and more), while participating as nodes in a decentralized network. These SDR clients, connected via the TON proxy network, enable secure, censorship-resistant communication and incentivized participation through the WEB3SDR token.\n\nThis project aims to create a global, accessible SDR infrastructure for enthusiasts, researchers, and developers while ensuring data integrity, privacy, and decentralization.\n\nTokenomics\nWEB3SDR Token\nWEB3SDR is the native token of the Web3SDR network. It powers the ecosystem, serving multiple functions:\n\nFunctions:\n\nIncentivization: SDR clients earn WEB3SDR tokens by operating as a node on the network and providing radio signal data.\n\nPayments: Users who want to access SDR data through the API/SDK pay in WEB3SDR tokens.\n\nGovernance: Token holders participate in network governance, influencing the future development of Web3SDR.\n\nEarning Model\nNode Operators (SDR Clients):\n\nData Contribution: SDR clients earn tokens by contributing radio signal data to the network.\n\nMining Rewards: As part of the TON proxy network, they also participate in transaction processing and receive a portion of transaction fees in WEB3SDR tokens.\n\nData Consumers:\n\nUsers pay for accessing radio signal data on a pay-per-use basis. The cost depends on the bandwidth and duration of data usage.\n\nSecurity and Privacy\nDecentralization\nAll SDR clients operate as independent nodes on the TON proxy network, ensuring a decentralized architecture. No single point of failure exists, and data is distributed across various nodes.\n\nCensorship Resistance\nThe TON proxy network is used to ensure that Web3SDR is censorship-resistant. SDR clients cannot be easily blocked or restricted by authorities, ensuring free and open access to radio data.\n\nData Integrity\nThe integrity of SDR data is secured by the underlying blockchain network. Transactions, data contributions, and token payments are recorded immutably on the ledger, ensuring transparency and security.\n\nRoadmap\nPhase 1: Proof of Concept (POC)\nDevelop and test the first SDR client with Raspberry Pi and SDR hardware.\n\nBuild a basic version of the Web3SDR API.\n\nLaunch a testnet for SDR client connectivity.\n\nPhase 2: Token and Network Integration\nIntegrate WEB3SDR tokens and the TON proxy network.\n\nLaunch the mining node functionality on SDR clients.\n\nDeploy a full-featured API and SDK for developers.\n\nPhase 3: Mainnet Launch\nOpen the network to global users and developers.\n\nLaunch WEB3SDR token distribution through exchanges.\n\nExpand SDR client support to more hardware configurations.\n\nPhase 4: Ecosystem Growth\nPartner with developers and institutions to build use cases for Web3SDR data.\n\nExpand node participation through incentives and rewards.", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "Web3sdr", "projectTwitter": "web3sdr"}
WEB3SDR
Web3SDR is a decentralized physical infrastructure network (DePIN) that integrates Software-Defined Radio (SDR) technology with the power of blockchain. Web3SDR transforms the traditional WebSDR platform into a decentralized, scalable, and tokenized system where SDR clients can contribute data from radio signals between 1 MHz and 160 MHz (AM/FM and more), while participating as nodes in a decentralized network. These SDR clients, connected via the TON proxy network, enable secure, censorship-resistant communication and incentivized participation through the WEB3SDR token.

This project aims to create a global, accessible SDR infrastructure for enthusiasts, researchers, and developers while ensuring data integrity, privacy, and decentralization.

Tokenomics
WEB3SDR Token
WEB3SDR is the native token of the Web3SDR network. It powers the ecosystem, serving multiple functions:

Functions:

Incentivization: SDR clients earn WEB3SDR tokens by operating as a node on the network and providing radio signal data.

Payments: Users who want to access SDR data through the API/SDK pay in WEB3SDR tokens.

Governance: Token holders participate in network governance, influencing the future development of Web3SDR.

Earning Model
Node Operators (SDR Clients):

Data Contribution: SDR clients earn tokens by contributing radio signal data to the network.

Mining Rewards: As part of the TON proxy network, they also participate in transaction processing and receive a portion of transaction fees in WEB3SDR tokens.

Data Consumers:

Users pay for accessing radio signal data on a pay-per-use basis. The cost depends on the bandwidth and duration of data usage.

Security and Privacy
Decentralization
All SDR clients operate as independent nodes on the TON proxy network, ensuring a decentralized architecture. No single point of failure exists, and data is distributed across various nodes.

Censorship Resistance
The TON proxy network is used to ensure that Web3SDR is censorship-resistant. SDR clients cannot be easily blocked or restricted by authorities, ensuring free and open access to radio data.

Data Integrity
The integrity of SDR data is secured by the underlying blockchain network. Transactions, data contributions, and token payments are recorded immutably on the ledger, ensuring transparency and security.

Roadmap
Phase 1: Proof of Concept (POC)
Develop and test the first SDR client with Raspberry Pi and SDR hardware.

Build a basic version of the Web3SDR API.

Launch a testnet for SDR client connectivity.

Phase 2: Token and Network Integration
Integrate WEB3SDR tokens and the TON proxy network.

Launch the mining node functionality on SDR clients.

Deploy a full-featured API and SDK for developers.

Phase 3: Mainnet Launch
Open the network to global users and developers.

Launch WEB3SDR token distribution through exchanges.

Expand SDR client support to more hardware configurations.

Phase 4: Ecosystem Growth
Partner with developers and institutions to build use cases for Web3SDR data.

Expand node participation through incentives and rewards.
WEB3SDR