Video summary
The Identus Community Call from August 11, 2026, began with a casual check-in among team members before transitioning into technical discussions regarding recent progress on the identity portal project. The primary focus was on resolving Phase Two of development, which involved finalizing necessary pull requests and addressing feedback on multi-tenancy for SDKs. It was clarified that while long-term goals include supporting multiple tenants, the immediate strategy is to proceed with a single-tenant architecture using TypeScript. This approach allows the team to build a robust authentication layer first, making it easier to integrate multi-tenancy later without treating current limitations as blockers. The group also discussed automating peer reviews and testing new AI agents on specific repositories to streamline workflows before moving forward with Phase Three, which is nearing completion pending final approvals.
A significant portion of the meeting was dedicated to architectural decisions regarding schema management within the Midnight network. Drawing from discussions held several years ago about full CRUD operations for schemas, the team agreed that schemas should be treated as immutable objects once created. Instead of allowing updates or deletions, the proposed solution involves versioning; developers can create a new versioned schema when changes are needed and fetch existing versions without modifying them directly. This strategy ensures stability in the long term while providing flexibility through version control, particularly for entities managed by Microsoft or related to verifiable credentials where immutability is crucial. The conversation highlighted that this method prevents accidental data loss and maintains integrity across different models and projects within the ecosystem.
The call concluded with official announcements regarding the release of Midnight DID 0.50, which marks a step forward despite ongoing internal security reviews and W3C registration processes required for full compliance. Alongside the digital identity project, updates were shared on Lace ID, an upcoming initiative designed to function as a decentralized identity portal where anyone can issue credentials. The team confirmed that repositories related to verifiable credentials are becoming public, allowing external contributors to build upon existing examples or integrate these technologies into their own projects like the Lace wallet. Additionally, John provided an update on his book project, noting it is in final editing and will be available for community review soon, before wrapping up with a friendly reminder of upcoming meetings and a thank you to all participants for their engagement during this efficient session.
Read the full video transcript
That's us.
Hello Yuri.
>> Hi Si.
How are you?
>> I'm good. Thanks.
>> Nice. Nice to hear us.
Okay. Where is my
Okay. I'm trying on the desktop. Do you
see it?
>> Uhhuh.
>> Yes. Excellent.
Um, as far as I know, have you reviewed
a couple of your PRs? Uh, so
do you have any blockers or any other
questions?
>> Uh, no. No, we finished the phase two
and uh we uh discussed we agreed that we
need some pair sessioning. So I need a
pair session from
>> waiting tomorrow after tomorrow he's
going to have a time.
>> Yeah. Yeah. I understand. Yeah.
>> Cool. And uh I saw some comments about
uh multi-tenency for SDKs. Uh it's uh
not really required to deliver identity
portal because uh by default this uh SDK
TS is single tenant. So if it's do you
hear me?
>> Yeah. Yeah. You you said single tenant.
>> Yeah. We can start with single tenant
and then uh when we add the proper um
authentication and authorization layer
with key lock it will be not hard to add
multi-tenency as well.
>> Oh
>> so don't make it some kind of blocker
for you. You can proceed with a single
tenant for SDKS and uh later with
powerful AI agent it will be possible to
turn it into multi.
>> Hi but
>> hello
guys.
>> Hello.
>> Don't be shy. Turn on video.
Oh,
you don't have such beautiful moak as
me, but you still pretty handsome.
>> Cool. Let's wait one more minute.
probably today it's going to be a small
group of people
and but uh we need to review from time
to time uh say these uh PRs
or we can try to
uh automate other agents uh to reuse
these PRs automatically.
Okay. Okay. Yeah,
I can re I [clears throat] can reapply
the workflow, the same workflow we use
to this
repos.
>> Recently I released a new version of
this agent peer review but uh it should
be tested so we can test it on some
repositories to burn some tokens. By the
way, Si, do you have access to Cloud
Codics or any other AI tools?
>> Yeah. Yeah, I have a cloud code.
>> Cloud code. Uh, okay. I just have
another question. What What model is
your favorite?
>> Uh,
I use a fable, but it has a very limits,
but I use
Opus the last version.
>> Yeah, I want to try Kiwi. Uh some uh
quen
what is a famous Chinese model?
>> Both. [laughter]
>> Yeah, both. Yeah.
>> And I wonder how it can uh be better or
worse than Codex cloud because I use
both.
Anyway, 5 minutes left. Uh let's uh do
this quickly. Uh welcome to a dentist
community call weekly meeting and as you
usually know we follow antitrust policy
notice defined by Linux foundation and
the code of conduct. If you forgot about
code of conduct there are clear
statements about this. The main one is
treat each other with respect and never
harass or bully me. That's the main
rules. Everything else we will share
next meeting. I mean from third one to
11th or you can do this anytime. Hi
John. Uh secondly our agenda for today I
wanted uh si to uh share a progress and
uh if there are any obstacles questions
to discuss about uh uh not mentorship
program it's one type of
identity
portal
uh then I will share some updates about
midnight and uh our progress with it. It
was a special request from uh our
company to uh add cells identity layer
to the midnight network and this is a
piece of our work and uh I guess uh but
already did this. Yep. Third and fourth.
So it's published and upgraded to
skeleton.
>> Yeah. Yeah. That's that that they were
both done.
>> It's actually done. Uh so Si Loris if
you have anything to tell us share
you're welcome. Uh yeah I uh
unfortunately I don't have any uh a lot
of progress but uh like I said uh the uh
phase two is resolve it we did a great
uh resolve and publish uh all all
necessary my PRs and uh I have uh two
blog things you if you if you would like
open it 8 uh 8 x 87 and 88
Yeah. Yeah. I requested
review. So the only two things is
working on this the
also asked to do something. Yes.
>> Yes. Yes. And uh I'm still waiting uh by
session from him. So
um
okay J how can I join today? Uh we will
figure out what he's looking for.
>> Okay.
>> And then we
>> uh also uh also uh phase three is almost
done. Just waiting approval from him.
>> Okay. Phase three is defined here for
us.
>> Yeah.
schemas are done local uh endpoints.
>> Mhm.
>> But uh as as you
said about multi- tenants and single
tenants I will
I will try.
>> Okay. As a wrote in comment or one
comment to share about schema
management. It was uh probably three or
four years ago when we had a discussion
about full CRT operations for schema
management but uh uh after discussions I
don't remember but we accepted some uh
decision or probably ADR about schema
management so we decided
do I have problem with internet because
everything is throttle
or it's only s
but I you move
probably said you got frozen a little
bit and uh the decision was that it's
better to create the versioning so the
same schema uh might should have uh the
must I would say must have version
according to the model and we need to
apply only create and uh uh
not only delete only create operation
usually. So two operation create and
fetch. Create to create the schema with
version and fetch to fetch the schema.
Uh it looks slightly
um how to say unusual
if you have some resource but you don't
allow to update or delete this resource.
But uh this is uh the right way to go in
a long-term perspective. So if you uh
define it the schema you can run it you
can even use 0.1
version if you are not sure about this
version and as soon as it's stabilized
you can uh create your schema and um I
remember there is site schema or
yeah and um probably it's not related to
this. It's a schemas for u a lot of
entities as far as I know managed by uh
probably Microsoft or some guys from
Microsoft and um some guys also created
u
schemas for verifiable credentials as a
site
and uh all these schemas are not
deletable. So if you have the schema you
can uh expect that it's immutable
object. It's like a remark about uh is
schema immutability question. Uh cool
any other questions uh discussions for
identity portal city.
Okay. Uh we don't hear you. Something is
wrong with your uh sound but it's okay.
I can read
what did you say? Cool. Uh short
announcement of uh midnight uh did
uh probably uh I uh sent some links on
our previous meetings but now we
officially release at uh midnight uh did
050.
Uh this is not uh one 0 release because
we still need to conduct internal
security review, external security
review and do some uh bureaucracy action
with uh W3C
um working group to properly register
this D. uh but uh we started using this
D in uh midnight uh projects and
together with midnight there are
midnight verifiable credential uh
project where this did is actively used
it and uh uh we also work on lace ID
which is going to be identity portal
where anyone can uh issue credentials.
Currently it supports midnight
verifiable credential uh digital
passport and uh part of this
repositories will be public. So if you
want to uh look at example or try to
build something similar or contribute to
it, it will be possible. Uh midnight
repositories are currently public as
well but we still actively working on
particular stuff. So verifiable
credential
it is this requested I will share this
links if you are interested in
something uh or have any questions or
feedback we would really appreciate this
packages are published to npmgs
and
in theory
me and pot successfully integrated this
did in has a couple of projects and here
it's going to integrate it into the lace
wallet and as I wrote here we going to
consider at midn to the identus platform
as well so ident is maintained by
engineers from organization it's not
that secret and uh it's uh pretty cool
to support all the methods
that
um it can be used to build self identity
layer on top of midnight and blockable
shades.
Cool. Any questions so far? Uh because
yep I just made announcement and yes I
forgot we have
uh midnight
we have midnight resolver uh repository
and currently uh yeah it's pretty
obvious that we have uh resolver uh
service uh for midnight here and
together with resolver we have uh uh
manager service. Uh this is a web
application that can help you to create
and uh manage your at verification
method verification method relations and
everything related to G. So these two
services this one is example application
and the mid9 resolver is going to be
registered as official reserver resolver
for the method.
Uh, cool. We are done with the second
bullet. Uh, Q&A section. Uh, John, how
is your book?
It's your time to ask something.
Uh, book is good. Um, we're in the final
beedit right now. So, um, see what date
it is. Maybe I don't know if it'll be
next Tuesday, but maybe the Tuesday
after that. Um there'll be something
that I would love to get uh people's uh
um review of. Uh so
there might be parts of it that are
ready for that review uh by Tuesday,
probably the Tuesday after. But um at
that point maybe I'll come to this
meeting and sort of just show everyone
where things are and I would love to get
um uh reviews on some chapters that
would be really helpful.
>> Yep. Don't hesitate to share links in
Discord channel. We will take a look.
>> Great.
>> Thanks.
>> Cool. Any other questions, topics to
discuss guys?
Great. We were really fast today. So
just 16 minutes and covered all topics.
Uh cool. Then thank you for your time
and um
your feedback for our work and see you
in one week.
We will read some interesting books.
Thank you guys. See you around. Bye-bye.
>> Thank you.
>> Thank you. Bye-bye.