Video summary
The Credible Weekly Community Call focused primarily on technical updates regarding service architecture and code contributions. A key agenda item was the ongoing effort to decouple various platform services so they can run independently, allowing users to utilize specific services like issue tracking without needing to deploy the entire suite. Ankita and Ajay are leading this initiative by identifying candidate services for segregation, with a particular focus on merging the webhook service into the organization module. The team aims to submit a draft pull request (PR) for this work by the next meeting, while also planning to address extensibility features in parallel once the core decoupling is stabilized to minimize merge conflicts.
In addition to architectural changes, significant progress was made on security enhancements and external integrations driven by Mark from the Sign Foundation. Several PRs related to authentication hardening and agent provisioning are currently undergoing rigorous local testing after code reviews were completed by Ajay and Rinkle. Notably, a new feature allowing the integration of an external Key Management System (KMS) was successfully merged for the mobile SDK, enabling developers to use secure enclaves or separate KMS instances for key management during initialization. The team confirmed that while the code changes look correct, thorough testing across different machines is essential before final approval, and a pluggable KMS solution for the Credo backend is also being evaluated with external systems.
Beyond technical developments, the call highlighted Credible's success in the Global Digital Trust Awards, where the project has been selected as a finalist in the collaboration category. The evaluation process heavily relies on community voting, which accounts for fifty percent of the criteria, and the team urged all attendees to cast their votes before the September 2nd deadline. Voting is conducted directly on the award website, and the organization encouraged participants to propagate this request within their networks to support Credible's chances. With the technical PRs scheduled for review later in the week and the voting campaign underway, the meeting concluded with a positive outlook on the project's momentum and community engagement.
Read the full video transcript
Hi Topan, sir. Good morning.
Good evening.
>> Call everybody.
Have you called?
>> Uh
>> Hi Simran, good evening.
>> Hi, good evening, Shobha.
Hi Topan.
>> Hi Simran.
>> So, So be joining via this link.
Like
Pawan, Tapan, if anyone can tell.
>> No idea, Sandeep.
>> Okay.
>> Already I'm waiting.
>> Mhm.
>> Yeah, hi. Good morning all. Sorry for
the delay.
Okay.
Uh so, let me share my screen and like
It's
Okay.
Uh I hope you are able to see my screen.
>> Yes, we are able to see.
>> Yes, yes, we are.
>> So, welcome all to Credible Community
Call.
Just do
>> Uh hello Amit.
We are not able to hear you. If you are
please
>> Okay.
So like
I was on mute from starting itself.
>> Yes.
>> Okay.
So I was just sharing the
agenda.
Uh so last week we had a discussion
regarding the decoupling of the
services. So like incredible there are
so many services are there.
And uh
So, have decided to like decouple those
services and
those can run independently. Like uh if
someone wants to only use the issue on
service, so they do not need to like run
other services as well. So, that can uh
reduce. So, the we are working on that
part. So, initially we are doing some
planning and how we can segregate those
services and all. So, Ankita and Ajay is
looking into that part.
Apart from like extensibility, like
Teeku is actively working on that. I
guess Teeku is not on the call.
Otherwise, uh we can share the Ankita is
there. Ankita, do you want to share
anything related to the
decoupling part?
>> Yes. So, as per uh
as we discussed in the last call, we
created an issue for uh coupling for
this decoupling and merger of the
services.
And uh we identify like myself and
Teeku, we are assigned
uh
uh in as of now for this task. If
someone wants to take that up, that is
also fine.
So, we have identified few services uh
to which we can
uh decouple and merge
uh to align the microservices.
Uh in each we started with webhook
merging webhook service into
organization and there are I think 1722
is the issue
that we created.
1722.
So, maybe we'll have
uh
some a draft PR
uh by next
call
uh for this.
>> So, yeah, in the
platform itself, correct?
>> Yes, yes. Uh platform services.
And this platform services.
And uh for
um
for extensibility part, uh as we
discussed in the last call, we will uh
merge and decouple the services first,
and then we will uh resume extensibility
part.
Uh so,
what we can do is we can divide
different services and work parallelly
as well.
Uh but, I think we have to um
it we we have to assign ourselves um
independent services, so that there can
there will and actively merge merge into
each other's fork.
So, that uh there will not be much merge
conflict.
So, uh first, we'll complete this part,
and then we'll
um
then I think it will be better to
uh do the
extensibility part.
Like packaging one.
>> Okay.
Yeah.
There are a couple of more PRs are
there. You want to talk into that
regarding this like
header JDO utility shutters
>> Uh yeah, I think um
my
Just one minute.
Uh Mark from Sign Foundation uh has
has raised few PRs regarding um
authentication and hardening of the
uh services.
So, we are
uh working on testing them locally. Like
there were some review comments on them
and Ajay and
Rinkle also reviewed it.
So all the issues in the code are fixed,
but we are working on
testing them
thoroughly.
>> [clears throat]
>> Because I think
in the agent provisioning service also
it is
there are changes, so we will test it
on different machines and then
we'll
approve for comment on the PR.
So code wise it
it looks good, but we have to test it.
So we are in a process of testing those
PRs.
Similarly, like there are couple of PRs,
1706,
1708
and 1727.
All the three services and
And there was one service to redirect
swagger issue that is uh
that is approved, so we will merge it.
Yes, that's it from
on platform side.
>> Yeah.
Then the controller also like sign like
Mark from sign has a clear one more PR.
It's related to like open bow for credo
KMS backend.
>> Okay.
>> It's I think it's a pluggable KMS,
right?
>> Yeah, pluggable KMS.
>> That's an interesting PR.
>> Mhm.
I think that we have to test this one
with the external KMS and
So, in the mobile SDK side as well, uh
like there are one PR was there from the
same person. So, it is like a same like
KMS related stuff.
In the morning itself, we have just
merged that PR.
So, like uh in the SDK like earlier, we
have not
uh uh support that external KMS. So,
like the
in the PR itself, they they have
mentioned that uh
how we can integrate the external KMS in
the system.
So, there is a separate interface that
has been written. So, while initializing
the SDK,
uh you can you can use any external KMS.
So, in the read me example, it's a
secure enclave that generally there in
the
like mobile. So, you can have a
uh like separate KMS uh to manage those
uh
create and manage those keys. So, that
interface and all of stuff are written.
So, that PR is uh merged to the itself.
>> Mhm.
>> There are no no any changes on the
mobile wallet side.
>> Mhm.
Yeah.
I think that's it. Do we have to discuss
anything like
apart from this?
>> I think I'm going to Tuesday I have
something.
>> Mhm.
From communication
and marketing perspective.
I think the
we participated in
fights global digital trust
awards. We were there, so
credible is
now in finals.
Is selected for as a finalist for
the
collaboration category. Is it? Can you
scroll down?
There are different categories
in this award. So, in the collaboration
award,
credible is chosen as one of the
project.
So,
like 50% of the evaluation criteria is
the community vote.
So,
it would be great
if you all can vote for credible.
And propagate in the network and
community as well.
>> Yes. So, you just have to log in into
this website, and we just have to select
the credible and vote it like I have
already done it.
People who are
like
not yet vote, they can just log in and
vote here.
Apart from there are different
categories as well.
So,
>> There are other projects as well.
Impact wallet.
There are four categories.
>> Yeah.
Voting deadline is at 2 September, 2nd
September.
>> Mhm.
>> Well, yeah, I think that's it for
today's call.
If ever anyone have any question or any
discussion, please feel free to ask. We
can discuss those.
Otherwise, we can conclude the call.
>> I think I'm good from my side.
>> Good, nothing specific from my side as
well. There are few PRs that
I'm already working on as Ankita
mentioned.
And
will be
looked at and addressed in this week,
mostly. Yeah.
>> Yes.
>> Okay, then we can conclude the
>> Thank you, everyone.
>> Thank you.
>> Bye.