# IKP WG 2026 - Working Group Call Thread

**URL:** <https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887>\
**Category:** IAM, Key Management & Privacy (IKP)\
**Tags:** ikp\
**Created:** [January 12, 2026, 2:49pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887 "2026-01-12T14:49:47Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [January 12, 2026, 2:49pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/1 "2026-01-12T14:49:47Z")

</div>

Happy New Year IKP WG! 🎉

(starting a new thread)

Hope everyone’s had a great start to 2026!  
**First meeting of the year: JAN 15, Thursday, 12:00 UTC**

Topic: Proof of Personhood paper – comparing biometric standards and social proof of personhood systems, with a focus on AI implications.

We’ll be looking at examples including WorldID and agentprivacy fundamentals for proof of personhood approaches.

Call for contributors: We’re looking for additional contributors and identity protocols focused on personhood to help expand the paper and inform future standards pathways.

See you Thursday!

BGIN SR 0014\_Proof of Personhood: Biometrics, Systems + Agent Duality as Personhood Preservation Mechanism

add the calendar: [BGIN Working Groups](https://calendar.google.com/calendar/u/0/embed?src=c_d38853647205142770f21aebe1128f01c976bcb622145adf653f4f7dc3f12dfe@group.calendar.google.com&ctz=Asia/Tokyo)

> **[BGIN SR 0014\_Proof of Personhood: Biometrics, Systems + Agent Duality as...](https://docs.google.com/document/d/192To-2GhV_nEAh7JRQlgIUK2et0NDlSfqfH5JJIZHyY/edit)**
>
> BGIN BGIN IKP Working Group Proof of Personhood: Biometrics, Social Trust and Dual Agent Systems - BGIN is a multi-stakeholder discussion body / distributed think tank. © 2023 BGIN (Blockchain Governance Initiative Network) is registered...

> **[Join our Cloud HD Video Meeting](https://us06web.zoom.us/j/84260731068?pwd=evLSZGwggQPgyd0hWYKMi0vvCGDppX.1)**
>
> Zoom is the leader in modern enterprise cloud communications.

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [January 15, 2026, 2:11pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/2 "2026-01-15T14:11:15Z")

</div>

# **IKP Working Group Meeting Note**

**15 January 2026**

## **Block 14 Session Planning**

We kicked off with session planning for Block 14. IKP will lead or co-lead the following:

- **IKP** : _Post-Quantum Cryptography (PQC)_ — establishing a competition framework for PQC standards in blockchain, with ETH/BTC as critical contributors.

- **IKP** : _Privacy Enhanced Authentication and Key Management_

- **IKP** : _Accountable Wallet_

- **IKP** : _Proof of Personhood_ — discussed at depth today.

- **IKP + FASE** : _Forensics and Analysis — Toward a Common Lexicon for Harmful On-Chain Activities_

* * *

## **Proof of Personhood: Sharpening the Definitions**

The bulk of today’s session focused on tightening our conceptual foundations for the Proof of Personhood working group item. We’re conducting a case comparison study across Gitcoin Passport, zkPassport, human tech, first person project and World ID to understand where proof of personhood ends and identity systems begin.

### **The Core Triangle**

We explored whether proof of personhood requires three interdependent properties:

1. **Humanity** — the “bot or not” primitive

2. **Uniqueness** — preventing the same human from registering multiple times

3. **Identity** — the system-defined register of attributes

A key insight: systems that prove humanity _without_ uniqueness remain gameable. Uniqueness is a rate-limiting factor. This led us to propose the term **“proof of unique humanness”** as the stronger primitive.

### **Constraints as Definitions**

We found that attack vectors help sharpen definitions:

- **Uniqueness** is a _spatial_ question — are you registered once?

- **Liveness** is a _temporal_ question — are you present now?

- **Privacy** (via selective disclosure) is what prevents linkability and reconstruction attacks

A true proof of personhood should not reveal identifiers that are referenceable or useful for correlation — distinguishing it from proof of identity.

### **Identifiers vs Identity**

Identifiers are personal data. Composable, they _become_ identity. The governance of which identifiers anchor uniqueness is a design choice, not a technical inevitability.

We also touched on edge cases: What happens when states issue passports for people who don’t exist? (Espionage, error, fraud.) Biometrics become the control mechanism.

### **Agents, Reputation, and Duality**

A social media platform requiring World ID verification surfaced interesting questions:

- Users shouldn’t be limited to one account

- But reputation and rate-limiting across accounts should converge

- The human is the “gap in the middle”

This leads to **pairwise pseudonymous identifiers** — reputation accrues to the platform-specific identifier, not the root identity. Global reputation implies proof of _identity_, not personhood.

We discussed the **“oneness risk”** : if everything collapses to a single identifier, we enable censorship and total reconstruction. This risk extends to agents as well. Why duality matters — why it must be two (agentprivacy) to mitigate reconstruction of the personhood credential risk— for personhood-delegated agents, of which will be explored in further discussions.

While we raised reputation systems there was a consensus that this may be out of scope and expand /dilute the paper: ‘There are many different approaches and strategy with respect to reputation… And it is only “one” kind of application of PoP…’

* * *

## **Expanding the Case Studies**

We’re broadening our resource gathering to include additional proof of personhood approaches, and will open to contributors of others undiscovered or those already on this list.

- **WorldID**

- **Human.Tech** — Human Passport

- **Billions Network**

- **Web of Trust**

- **Kleros / Proof of Humanity**

- **BrightID**

- **First Person Project -** trust graph

- **Humanity Protocol** — palm scan biometrics

- […]

If you represent or have insight into these or have other approaches, we welcome your participation in the comparative analysis.

* * *

## **ACTIONS:**

- Continue case comparison analysis and invite additional approaches to contribute

- Draft definitions section with input from multiple disciplines / build the definitions, terms, and constraints before our next meeting for review

- Integrate agent duality framework into the working group item

- Coordinate with FASE on the forensics lexicon work and Cyber on related security considerations

- [BGIN SR 0014\_Proof of Personhood: Biometrics, Systems + Agent Duality as Personhood Preservation Mechanism - Google Docs](https://docs.google.com/document/d/192To-2GhV_nEAh7JRQlgIUK2et0NDlSfqfH5JJIZHyY/edit?usp=sharing)

* * *

_Contributions welcome. Reach out if you’d like to participate in the working group._

_-Mitchell, IKP co-chair @privacymage_

- 
- 

**Our next working group call will be in two weeks and the public workshop shared between IKP and FASE working groups (details to be linked soon)**

the topic is:  
**IKP + FASE** : Forensics and Analysis — Toward a Common Lexicon for Harmful On-Chain Activities

- any showcase or open AMA on the documents and progress on working items, such as the proof of personhood paper.  
+Block 14 workshop preparations.

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [January 29, 2026, 12:18pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/3 "2026-01-29T12:18:40Z")

</div>

Hi all,

no call today - sorry we messed up some of the scheduling this week, a touch distracted, we have been coordinating with block 14 participating organisations.

by way of update on IKP activities,

1. we’ve included human tech in the proof of personhood paper as a contributor. [https://human.tech/](https://human.tech/)
2. we’ve spoken with nyx foundation about forming a response and proposal to the ethereum RFP for privacy and trust/authentication ( [Invitation to Collaborate on Ethereum’s Trust Assurance Framework - #6 by JBringer](https://bgin.discourse.group/t/invitation-to-collaborate-on-ethereum-s-trust-assurance-framework/896/6) )
3. started to synchronise on ways the cyber incident response project can use IKP knowledge and participations to improve our agentic workflows. (via MyTerms [https://myterms.info/](https://myterms.info/) / [agentprivacy.ai](https://agentprivacy.ai/) dual agent governance)
4. spoken with World directly on block14 workshop details.

a quick note on the ikp past couple weeks.

Our next call will be 12th of Feb 12 UTC.

proposed agenda.

- block 14
- proof of personhood paper.
- taxonomy of harms and forensic vs analytics
- aob.

best,

mitchell

---

<div class="post-metadata">

**Author:** ![KigenFukuda](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/kigenfukuda/32/205_2.png) [@KigenFukuda](https://bgin.discourse.group/u/KigenFukuda)\
**Post date:** [February 1, 2026, 7:11am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/4 "2026-02-01T07:11:41Z")

</div>

Thanks for sharing the agenda.  
I would like to talk a little about Blockchain PQC migration item on 12th since I’m expecting some people involved in PQC blockchain may join the meeting

---

<div class="post-metadata">

**Author:** ![JBringer](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@JBringer](https://bgin.discourse.group/u/JBringer)\
**Post date:** [February 4, 2026, 9:43am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/5 "2026-02-04T09:43:15Z")

</div>

@Mitchell I cannot make it Thursday 12th ☹  
For the PoP paper

- any contact with Rarimo? I can try, in order to see if they would be ready to contribute.
- following our discussions at previous meeting. We should include use cases in the paper to illustrate the different expected properties (or requirements) vs the potential use cases.

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [February 4, 2026, 1:34pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/6 "2026-02-04T13:34:06Z")

</div>

sure lets discuss the PQC work items on the 12th.

@JBringer i agree and havn’t contacted yet, we focus in on writing the use cases and inviting other PoP ideas prior to block 14

---

<div class="post-metadata">

**Author:** ![JBringer](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@JBringer](https://bgin.discourse.group/u/JBringer)\
**Post date:** [February 4, 2026, 3:43pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/7 "2026-02-04T15:43:41Z")

</div>

ok. If you will discuss during the next meeting distribution of tasks in order to provide inputs for the document, feel free to assign one of the writing tasks to me if it can help.

---

<div class="post-metadata">

**Author:** ![nat](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/nat/32/12_2.png) [@nat](https://bgin.discourse.group/u/nat)\
**Post date:** [February 13, 2026, 7:19am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/8 "2026-02-13T07:19:27Z")

</div>

Sorry to miss the call yesterday. Have we come up with the final agenda and the descriptions? We should be filling in the session overview, agenda, and main contributors on the site.

---

<div class="post-metadata">

**Author:** ![nat](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/nat/32/12_2.png) [@nat](https://bgin.discourse.group/u/nat)\
**Post date:** [February 13, 2026, 7:59am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/9 "2026-02-13T07:59:14Z")

</div>

> [@Mitchell](#):
>
> - **Uniqueness** is a _spatial_ question — are you registered once?
> - **Liveness** is a _temporal_ question — are you present now?
> - **Privacy** (via selective disclosure) is what prevents linkability and reconstruction attacks

This is quite catchy and nice, but at the same time a little misleading. For example, when we talk about uniqueness, we have to define the universe. If the universe coverse period of time, then is it really purely spatial?

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [February 13, 2026, 12:22pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/10 "2026-02-13T12:22:41Z")

</div>

yea i see where you’re coming from here, time changes uniqueness from an object in space to a trajectory through space, so not purely spatial but also directional if from the first persons universe or in relation to, if from the observers universe. perhaps the word ‘registered’ needs updating? thank you, will keep this in mind.

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [February 13, 2026, 12:29pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/11 "2026-02-13T12:29:55Z")

</div>

yes we went through that process in the call. i’ll use the transcript to form that information for the website.

---

<div class="post-metadata">

**Author:** ![shinichiro.matsuo](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/shinichiro.matsuo/32/11_2.png) [@shinichiro.matsuo](https://bgin.discourse.group/u/shinichiro.matsuo)\
**Post date:** [March 12, 2026, 11:54am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/12 "2026-03-12T11:54:43Z")

</div>

@Mitchell Do we have a call today?

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [March 12, 2026, 2:05pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/13 "2026-03-12T14:05:34Z")

</div>

no call today

Hey all, quick heads up there won’t be a working group call this week as we hosted the layer 2 meetup in Sydney earlier this week and I’m travelling.

The next call will be on the 26th of March

We had a great discussion at the Layer 2 Meetup in Sydney, on the three graph one trajectory, PQC, privacy pools and the common lexicon

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [May 15, 2026, 1:44pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/14 "2026-05-15T13:44:48Z")

</div>

Hi All @nat @JBringer @KigenFukuda @shinichiro.matsuo

next week we have a very interesting guest into the working group call,

i have made a private event with BGIN admin on Luma to gather participants @Rola could you include the updated zoom link into this event when you get a chance.

I’ve sent initial invites to existing and relevant IKP WG participants (a short list) and will share with others, upon notifying the guests and gauging participation boundaries.

> **[Luma](https://luma.com/event/manage/evt-XMyGMsJTGlySL3v)**

---

<div class="post-metadata">

**Author:** ![KigenFukuda](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/kigenfukuda/32/205_2.png) [@KigenFukuda](https://bgin.discourse.group/u/KigenFukuda)\
**Post date:** [May 15, 2026, 6:28pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/15 "2026-05-15T18:28:55Z")

</div>

Is it the same time as the regular IKP call?

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [May 16, 2026, 11:55am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/16 "2026-05-16T11:55:05Z")

</div>

It is not, it is ~4 hours later than normal timing

---

<div class="post-metadata">

**Author:** ![shinichiro.matsuo](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/shinichiro.matsuo/32/11_2.png) [@shinichiro.matsuo](https://bgin.discourse.group/u/shinichiro.matsuo)\
**Post date:** [May 18, 2026, 10:41am UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/17 "2026-05-18T10:41:15Z")

</div>

As this is a big chance for us to gather new BGINres. Can we widely advertise this meeting? The Luma page could be public, but we should circulate the Zoom link privately.  
We need more and more engineers and blockchain stakeholders to discuss this work. I’m thinking of a few additional lectures on the PQC migration.

Anyway, can we make it a public Luma event? We can circulate the Zoom link one or two days before the call. @Rola, could you advertise this call over social media?  
@KigenFukuda, can you circulate this information to all the blockchain PQC migration-related persons?

Shin’ichiro Matsuo, Ph.D.  
Research Professor, Department of Computer Science, Georgetown University Cyber SMART Director, and Lead Researcher, Blockchain Eco-System

---

<div class="post-metadata">

**Author:** ![Mitchell](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/mitchell/32/78_2.png) [@Mitchell](https://bgin.discourse.group/u/Mitchell)\
**Post date:** [May 18, 2026, 12:03pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/18 "2026-05-18T12:03:13Z")

</div>

Agreed, ill update the event and share in a few places, we do need to have a process for sending a zoom link to all who have signed up at least 12/24 hours before.

---

<div class="post-metadata">

**Author:** ![Rola](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@Rola](https://bgin.discourse.group/u/Rola)\
**Post date:** [May 18, 2026, 1:13pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/19 "2026-05-18T13:13:06Z")

</div>

I have already shared is on LinkedIn, X and Discourse.

Please let me know if there’s something I missed

Regards

---

<div class="post-metadata">

**Author:** ![KigenFukuda](https://sea1.discourse-cdn.com/flex019/user_avatar/bgin.discourse.group/kigenfukuda/32/205_2.png) [@KigenFukuda](https://bgin.discourse.group/u/KigenFukuda)\
**Post date:** [May 18, 2026, 9:14pm UTC](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887/20 "2026-05-18T21:14:33Z")

</div>

Awesome, I will circulate the info to some communities and people I know.

[Next page](https://bgin.discourse.group/t/ikp-wg-2026-working-group-call-thread/887.md?page=2)
