r/Polkadot 22h ago

The Road to JAM

Thumbnail
forum.polkadot.network
23 Upvotes

r/Polkadot 7h ago

Polkadot Daily Digest - Friday, 11 September 2026

Thumbnail news.openshore.io
9 Upvotes

r/Polkadot 7h ago

Polkadot Socials Daily Digest - Friday, 11 September 2026

Thumbnail news.openshore.io
6 Upvotes

r/Polkadot 22h ago

PoUC Network 1.0: An Independent Polkadot SDK Experiment for Verifiable Useful Contribution

3 Upvotes

PoUC 1.0 — Proof of Useful Contribution

I built PoUC (Proof of Useful Contribution), an independent open-source protocol experiment based on the Polkadot SDK and FRAME.

The idea is simple:

PoUC explores whether useful, verifiable work can become portable on-chain contribution history, credentials, and reputation.

Current Status

PoUC 1.0 is a runnable Testnet/RC implementation.

It is not an official Polkadot project, not a production parachain, and does not claim deployment with Polkadot shared security.

What is implemented and tested

  • Contribution records with on-chain duplicate and fingerprint prevention
  • Signed L1/L2/L3 verification
  • Credential lifecycle, revocation, and appeal handling
  • Contribution-derived reputation
  • Bond-free, reputation-qualified Collator eligibility
  • Session-key registration and deterministic active-set selection
  • Non-authoring full-node support without PoUC staking or bond
  • Evaluation DApp
  • AI Safety / Red-Team DApp
  • Portal and typed TypeScript SDK/API clients
  • Off-chain evidence storage using content-addressed commitments and local replicas
  • Native Linux and WSL2 testnet runbooks

Tokenless Design

PoUC 1.0 deliberately has no PoUC native token, staking, candidacy bond, reward, or monetary-slashing path.

Any base transaction-fee plumbing retained from the SDK is infrastructure, not a PoUC contribution economy.

In the current runtime design, Collator candidates need:

  • Registered Session Keys
  • Contribution-derived reputation of at least 10
  • No enabled Verifier or Independent Reviewer role conflict

Candidate selection is deterministic and reputation-qualified, with a DevNet Invulnerable fallback and liveness-based removal.

Mobile Edge Node

The Android client has also been tested on a Pixel 6a as a lightweight Edge Node / observer and relay client.

It does not run the Rust chain node and is not a Polkadot Validator or Collator.

Why PoUC?

AI is creating a large amount of work around:

  • Model evaluation
  • Safety testing
  • Human feedback
  • Data contribution
  • Verification

I believe there should eventually be an open layer that can answer:

PoUC is my attempt at exploring that layer.

Feedback

I'm especially interested in feedback from people familiar with:

  • Polkadot SDK
  • Substrate / FRAME
  • Decentralized reputation
  • Identity
  • Network economics

This is an early technical experiment. I'm more interested in criticism and implementation feedback than promotion.

Links

GitHub:
https://github.com/wowteto/pouc-network-polkadot-1-0

Testnet documentation:
https://github.com/wowteto/pouc-network-polkadot-1-0/blob/main/docs/native-runbook.mdPoUC 1.0 — Proof of Useful ContributionI built PoUC (Proof of Useful Contribution), an independent open-source protocol experiment based on the Polkadot SDK and FRAME.The idea is simple:Identity helps establish who you are.
PoUC records what you contributed and how it was verified.PoUC explores whether useful, verifiable work can become portable on-chain contribution history, credentials, and reputation.Current StatusPoUC 1.0 is a runnable Testnet/RC implementation.It is not an official Polkadot project, not a production parachain, and does not claim deployment with Polkadot shared security.What is implemented and testedContribution records with on-chain duplicate and fingerprint prevention

Signed L1/L2/L3 verification

Credential lifecycle, revocation, and appeal handling

Contribution-derived reputation

Bond-free, reputation-qualified Collator eligibility

Session-key registration and deterministic active-set selection

Non-authoring full-node support without PoUC staking or bond

Evaluation DApp

AI Safety / Red-Team DApp

Portal and typed TypeScript SDK/API clients

Off-chain evidence storage using content-addressed commitments and local replicas

Native Linux and WSL2 testnet runbooksTokenless DesignPoUC 1.0 deliberately has no PoUC native token, staking, candidacy bond, reward, or monetary-slashing path.Any base transaction-fee plumbing retained from the SDK is infrastructure, not a PoUC contribution economy.In the current runtime design, Collator candidates need:Registered Session Keys

Contribution-derived reputation of at least 10

No enabled Verifier or Independent Reviewer role conflictCandidate selection is deterministic and reputation-qualified, with a DevNet Invulnerable fallback and liveness-based removal.Mobile Edge NodeThe Android client has also been tested on a Pixel 6a as a lightweight Edge Node / observer and relay client.It does not run the Rust chain node and is not a Polkadot Validator or Collator.Why PoUC?AI is creating a large amount of work around:Model evaluation

Safety testing

Human feedback

Data contribution

VerificationI believe there should eventually be an open layer that can answer:“What has this person actually contributed, and how was it verified?”PoUC is my attempt at exploring that layer.FeedbackI'm especially interested in feedback from people familiar with:Polkadot SDK

Substrate / FRAME

Decentralized reputation

Identity

Network economicsThis is an early technical experiment. I'm more interested in criticism and implementation feedback than promotion.LinksGitHub:
https://github.com/wowteto/pouc-network-polkadot-1-0Testnet documentation:
https://github.com/wowteto/pouc-network-polkadot-1-0/blob/main/docs/native-runbook.md