{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibfw6ul3q62gwpxe65r2smcaesmc4b5ycg2dl2ebd77ich24ibmey",
    "uri": "at://did:plc:ep3fxt5imrl3vy62u2j2i4vl/app.bsky.feed.post/3mhvqjgwinin2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiexdh7rnmcpm56qu6gtcj3pp3qbwxidj3qbmg6gype33yrwl4gqja"
    },
    "mimeType": "image/png",
    "size": 1539616
  },
  "description": "In the last piece, we talked about what the chain can show today, and what it still cannot show directly.\n\nThat leads to a very normal question:\n\nIf the paper already explains PoBU, what does it still want to improve?\n\nThe paper answers that in its future work section. And in plain language, it is saying this:\n\nPoBU is not “finished.” The paper gives the base model, shows what it can measure now, and then lists the next things that would make the system clearer and stronger.\n\n\n1) Make the rulebo",
  "path": "/how-pobu-gets-stronger-from-here/",
  "publishedAt": "2026-03-25T18:41:44.000Z",
  "site": "https://blog.humanode.io",
  "tags": [
    "hat the chain can show today",
    "paper already explains the flow",
    "here"
  ],
  "textContent": "In the last piece, we talked about what the chain can show today, and what it still cannot show directly.\n\nThat leads to a very normal question:\n\nIf the paper already explains PoBU, what does it still want to improve?\n\nThe paper answers that in its future work section. And in plain language, it is saying this:\n\nPoBU is not “finished.”**** The paper gives the base model, shows what it can measure now, and then lists the next things that would make the system clearer and stronger.\n\n## 1) Make the rulebook clearer\n\nThe next step is to publish a more precise protocol interface. It lists parts like:\n\n  * prove-uniqueness\n  * on-chain notification\n  * eligibility checks\n  * wipe/refresh\n  * renewal/revocation\n\n\n\nWhat does that mean in simple terms?\n\nIt means the rulebook will become even clearer. Right now, the paper already explains the flow:\n\nA person proves uniqueness, the chain gets notified, and eligibility can later expire, be refreshed, or be removed.\n\nThe next step is to write those rules in an even more exact way, so anyone reading the protocol can clearly see:\n\n  * what each step is\n  * when it happens\n  * and what the chain is supposed to do\n\n\n\nSo this part is really about making the system easier to understand and harder to misread.\n\n## 2) Publish safer summaries from the human side\n\nAnother thing is that the evaluation would be stronger if it could publish safe identity-layer aggregates.\n\nIt gives examples like:\n\n  * enrollment / renewal success rates\n  * PAD summaries\n  * duplicate-attempt handling\n\n\n\nThat can sound abstract, so let’s slow it down.\n\n### Enrollment / renewal success rates\n\nThis means simple summary numbers like:\n\n  * how often new people successfully get in\n  * how often existing participants successfully renew their eligibility\n\n\n\nWhy does that matter?\n\nBecause if a system works in theory but lots of real people struggle to enroll or renew, that tells you something important about how usable it really is.\n\nSo this part is about showing how the human side of the system performs in practice.\n\n### Presentation Attack Definition (PAD) summaries\n\nThe paper uses PAD when talking about fake or misleading attempts during biometric checking.\n\nIn simple words:\n\nthis is about summary information on how well the system handles attempts to fool the check. So this part is about showing how strong the “real human vs fake attempt” side of the system is.\n\n### Duplicate-attempt handling\n\nThis means summaries about what happens when someone tries to get counted more than once.\n\nThat matters because PoBU is built around a simple rule:\n\none eligible account per human.\n\nSo readers naturally want to know: what happens when that rule gets pushed?\n\nThis part is about showing how the system responds when repeated attempts happen.\n\nPut simply, the paper is saying:\n\nThe chain already shows the key-level side. The next step is to safely publish more evidence from the human side, too.\n\n## 3) Reduce dependence on one gatekeeper\n\nThe paper also says PoBU should explore multi-issuer decentralization.\n\nIt specifically talks about governance for adding and removing issuers and verifier operators, without creating unilateral control or regional censorship.\n\nThat can sound technical, but the idea is simple. If too much power sits with one issuer or one operator, that becomes a weak point.\n\nSo the future system should have better ways to:\n\n  * spread out that power\n  * decide who can be added\n  * decide who can be removed\n  * and avoid one side becoming too dominant\n\n\n\nIn plain language:\n\nThe system should depend less on one gatekeeper.\n\n## 4) Prove eligibility while revealing less\n\nThe future work should strengthen privacy-preserving eligibility proofs.\n\nIt gives examples like:\n\n  * selective disclosure\n  * anonymous credentials\n\n\n\nHere’s the plain version.\n\n### Selective disclosure\n\nThis means revealing only the part that matters.\n\nFor example, instead of revealing extra information, the system would try to reveal only:this person is eligible.\n\nSo this part is about sharing less extra data while still proving what needs to be proved.\n\n### Anonymous credentials\n\nThis means a way for someone to prove they qualify without turning that proof into an easy personal label every time. In simple words: prove the right to take part, while making it harder to connect that proof back to the person.\n\nThe paper also says this still has to preserve revocation and audit needs.\n\nThat means the system still needs a way to:\n\n  * remove access when needed\n  * and support checking when something goes wrong\n\n\n\nSo this future step is about improving privacy without losing accountability.\n\n## 5) Make the measurements stronger\n\nThe empirical side can improve.\n\nIt gives three directions:\n\n  * regime-aware analysis\n  * randomized sampling\n  * full-census author extraction where possible\n\n\n\nAgain, let’s make that normal.\n\n### Regime-aware analysis\n\nThe paper already notes that long windows can mix together different phases of the chain’s history. So regime-aware analysis means: don’t treat every part of the chain’s history as if it were the same.\n\nBreak the history into meaningful phases.\n\n### Randomized sampling\n\nThe paper also says sampled block-author data can have bias. So randomized sampling means: choose samples in a way that reduces the chance that the sampling method itself distorts the result.\n\n### Full-census author extraction\n\nThis means: instead of checking only some blocks, measure all relevant blocks where possible.\n\nSo this future step is about making the evidence stronger and more complete.\n\nSo what is it really saying?\n\nIt is saying five simple things:\n\n  * make the rules clearer\n  * publish safer summary data from the human side\n  * reduce dependence on one issuer or operator\n  * improve privacy\n  * improve the measurements\n\n\n\nThat is what “next steps” means for PoBU.\n\nWhat comes next\n\nAt this point, we’ve covered the main themes of the PoBU paper one by one. So the next article can zoom out and do one final job:\n\n**What the PoBU paper is really trying to contribute overall, in one clear picture.**\n\nTill we lay that down for you, if you are interested in a more thorough reading, you can check out the original PDF here. And to get the summarised version of the themes in POBU paper, read this article here.",
  "title": "How PoBU gets stronger from here",
  "updatedAt": "2026-03-25T18:41:44.591Z"
}