►
From YouTube: Aries-vcx Meeting
Description
Aries-vcx Meeting
A
C
A
A
good
good
afternoon
good
evening.
A
All
right,
so
we
are
all
collected
here
as
from
the
usual
call
member.
A
All
right,
so
it's
September,
28th
2023.
This
is
rsv6
community
call.
Hypoge
Anti-Trust
policy
is
in
effect
and
let's
dive
into
our
agenda
so
well
before
we
get
any
further.
This
is
this
is
something
I
I
prepared
to
it
looks
quite
long
I,
don't
think
it's
you
longer
than
usual.
It
just
has
a
more
bullet
points
in
it,
but
nevertheless,
do
you
guys
have
anything
you
would
like
to
add
here
and.
B
A
Okay,
then,
probably
not
so
we
can
go
ahead
with
our
starting
discussion
points
here.
A
So
commentary
updates
I
have
attended
the
last
Monday
I
pleasure
and
on
crits
2.0
call
so
just
kind
of
put
it
out
there.
There
was
there
is
a
nice
nice
notes
on
the
on
the
link
here
from
the
call,
and
it
was
Mike
loader
there
talking
about
talking
about
hyperledger
Labs
Agora
project,
which
should
be
kind
of
like
I
guess
closest
comparison
will
be
to
Ursa,
but
Ursa
was
I,
know
a
Michael,
explain
the
difference
between
the
two.
A
Obviously
there's
like
different
crypto
here
different
stuff,
with
different
kind
of
philosophy.
Ursa
was
originally
supposed
to
be
a
project
for
all
of
the
high
Pledger
projects.
This
is
specifically
for
Aries
and
add-on
credits.
A
So
there's
going
to
be
a
number
of
libraries
he
donated
he
worked
on
over
the
years
and
is
now
donating
as
a
part
of
the
Agora
project
and
then
in
critics,
library
or
I,
guess,
I,
guess
more
accurately
the
Anon
credits
Library
and
that
will
be
then
kind
of
all
glued
together
and
it
will
be
also
the
layer
where
the
revocation
model
would
be
implemented
or
put
together
with
the
crypto
crypto
components
underneath.
A
So
that's
where
I've
been
this
week,
I
didn't
make
it
to
the
yesterday's
Aries
for
group
call
so
I,
don't
know
what
was
happening.
There
didn't
have
time
to
review
the
recording.
Yet
have
you
guys
attended
any
any
of
the
meetings
by
chance
or
anything
community
community
happening
you're,
aware
of.
A
Well,
maybe
to
review
back
here,
I
think
there
was
no
discussion
here
on
this
point,
so
I
I,
don't
know
it
was
supposed
to
be
discussed
in
yesterday's
Aries
War
group
called
unfortunately
I.
Wasn't
there
so
I'm,
not
sure
they
touched
on
it
or
not,
and
I'll
go
ahead
and
review
the
recording
quick
check
on
the
dependency
loosening.
If
there's
any
news
looks
like
not
yet
at
least
not
in
the
issue
thread.
Okay,
so
then
mentorship
before
we
get
to
any
updates.
A
I
would
just
like
to
point
out
that
I'm
I'm
working
on
deploying
media
for
well
planning
to
deploy
mediator
the
simple
relay
project
and
vcx
agency
on
on
some
public
URL,
where
all
these
Services
would
be.
You
know
considered
a
very
short-lived
the
data
in
them
with
some
daily
cleanups
or
something
like
that,
so
some
relatively
short
frequencies,
so
people
wouldn't
rely
on
it,
but
it
should
be
helpful
for
development.
A
So
that'll
be
these
three
services.
I'll
just
needs
to
I,
guess
from
from
the
inside.
If
you
could
well
once
the
things
are
ready
whenever
you're
ready
and
are
able
to
build
a
Docker
container,
you
can
just
point
me
to
that
Docker
repository
and
I'll
deploy
that
realize
something
we
need
to
build
in
rcbcx.
A
But
it's
pretty
simple,
it's
very
simple
service,
so
it
should
be
easy
to
contact
containerize
and
we
do
have
container
for
the
Legacy
agency,
so
they'll
be
that
is
being
deployed
right
now
back
to
the
status
updates.
So
again
we
have
a
nine
you're
on
a
call.
So
if
you
have
any
updates
you'd
like
to
share.
B
Yes,
I
have
a
small
update
from
last
time,
but
it's
in
a
good
state,
so
I
have
something
here.
Can
I
share
my
screen,
sure.
B
B
Right
now
so
previously,
before
the
past
month,
we
had
been
working
on
the
protocols
side
and
the
message
passing
side
of
the
mediated
protocols
that
we're
interested
in
that
is
forward
message,
protocol,
pickup
protocol
and
the
mediator
coordination
protocol.
So
everything
above
the
half
of
the
diagram
was
being
done
previously
so
yeah.
These
are
the
tick
marks,
so
this
were
being
done
previously
and
they
exist
in
a
separate
repo
called
some
server
something
yeah.
B
So
over
the
past
month,
a
few
weeks
what
I've
been
doing
is
to
work
on
the
main
cracks
of
the
project.
That
is,
since
we
are
going
to
be
talking
with
Aries
agents.
The
mediator
needs
to
speak
Aries,
so
this
here,
the
media
Aries
agent,
is
what
I've
been
working
on.
So
I've
been
doing
it
modularly,
because
each
of
them
deals
with
some
different
aspect
of
the
whole.
B
So
as
part
of
this
sub
project,
I
have
completed,
presenting
an
OB
invitation
and
making
a
request
from
the
Alice
agent.
That
is
the
mediation
request,
and
the
mediator
does
respond
properly
to
that
and
we
have
a
complete
connection
so
now.
The
next
step
is
to
actually
merge
these
two.
These
aren't
meant
to
be
separate.
It's
supposed
to
be
one
mediator
agent,
so
this
week,
what
I've
been
working
on
is
to
actually
merge
these.
B
B
There
were
some
dependency
conflicts,
live
Indie,
for
example,
requires
0.5.8
version
of
SQL,
X
and
I
was
using
a
more
recent
version,
so
that
involved
having
me
reduce
the
required
version
on
the
some
server
side.
But
even
after
that
there
were
some
workarounds
required
because
SQL
x,
previous
to
version
6,
does
not
support
macros
without
importing
another
Library.
So
it's
in
the
code
about
why
the
workaround
is
required
answers
we
need
to
add
another
build
dependencies
on
now.
What
is
the
current
functionality
that
you
can
expect
right
now?
So?
B
Currently,
we
are
able
to
complete
an
aries.com
connection,
that
is
the
OB
invite
and
the
mediation
request,
the
connection
request
and
the
connection
response,
so
that
is
completed
and
to
test
the
integration
that
is
to
test
whether
we
are
probably
depending
on
the
previous
code.
I
have
tried
to
create
an
account
for
the
client
when
the
mediator
sees
a
connection
request.
B
B
Yes,
so
that
means
that
the
indication
of
this
Aries
agent
and
the
previous
code
is
successful
yeah.
So
this
is
the
current
state
now
what
to
do
forward
so
right
now,
this
creation
of
an
account
is
happening
using
the
previous
database
Fields
itself,
and
in
that
we
didn't
have
a
field
for
the
mediator
side
of
the
connection
key.
That
is,
we
are
saving
the
authentication
key
or
the
very
key
of
the
client
inside
the
account,
but
we
aren't
saving
the
key
that
the
mediator
server
uses
to
authenticate
to
the
client.
B
So
the
next
part
is
going
to
be
to
add
that
field
inside
the
database
of
the
sum
server
and
then
to
implement
explicit
UI
in
the
client
side
so
that
it
can
make
requests
of
the
forward
message.
Type
and
media
request
types,
yes
and
then
do
other
protocols
yeah!
That's
it
for
me.
A
Nice,
nice,
that's
that's
looking
good!
It's
a
good
way
happy
to
see
the
connection
establishing
your
let's
it's
important,
most
indeed
so.
A
Yeah
I
guess
Perhaps
Perhaps
next
week,
given
the
progress
you
have
made
I
I
think
maybe
next
week
we
would
see
the
other
protocols
integrated
with
with
the
server
the
mediator
right
all
over
them.
B
Yes,
hopefully,
the
mediator
coordination
protocol
is
the
first
one
I'll
be
targeting,
so
that
is
the
well
creation
of
an
account
is
partially
done
now.
I
still
need
to
add
the
fields
for
saving
the
own.
Signing
key
of
the
mediator.
Server
then
like
there
are
other
messages
in
the
mediator
coordination
protocol,
like
adding
keys,
for
which
you
would
like
to
receive
forward
messages
and
to
list
them
out
in
all
of
those,
so
that
is
the
first
one
I'll
be
targeting,
and
after
that
I'll
be
trying
the
forward
message.
A
A
Good
sounds
great,
thank
you
for
the
demo
and
we
can
move
ahead
with
our
agenda.
D
Heyo
that
the
client
implementation
that
you're
planning
on
doing
will
that
be
its
own
crate
in
the
Aries
vcx
repair.
B
Currently,
it's
so
technically
I
mean:
let's
have
these
weird
terms
about
crates
and
projects
and
workspaces
and
packages.
So
it
is
a
separate
binary.
Yes,
it's
not
a
separate
package,
but
it
is
a
separate
binary.
D
Okay,
are
you
guys
thinking
about
turning
the
client
into
a
library
instead
of
a
binary.
B
Right
now,
it's
the
same
code
base
so
right
now,
I'm
using
the
client
only
to
test
the
mediator
server.
So
it's
not
like
a
full
I
mean
having
it
as
an
independent
entity.
Isn't
a
prime
goal
right
now,
so
that's
a
secondary
consideration
right
now.
The
main
goal
is
to
make
the
server
functional.
So
the
client
is
just
like
a
sibling
project
that
goes
along
with
it
right
now,
at
least.
D
Okay,
okay,
cool
cool
was
that
in
the
scope
of
the
project
plan,
for
you
guys,
I
I
can't
remember
actually.
A
A
Yeah
I
think
it.
It
wasn't.
A
Yeah
cool
all
right.
What
happened
what's
happening?
Where
did
I
get?
Okay,
George
I
saw
lots
of
PRS
being
merged
on.
B
D
Yeah,
so
there
was
three
pending
PRS
last
week
and
they
didn't
need
much
more,
just
a
few
more
back
and
forth
with
swapnil
and
myself
and
yeah
those
three
all
got
merged,
so
that
was
a
refactor
sort
of
a
refactor
of
the
app
to
hide
away
some
of
the
complexity
and
just
make
it
more
clean
and
and
also
just
PR's
for
finishing
up
the
connection
within
the
app
and
another
one
for
just
cleaning
up
the
scripts.
D
So
most
refactoring
work
and
finishing
up
the
connection
stuff
and
yeah
swapnil
and
I
haven't
had
a
meeting
this
week
he's
been
busy.
He
said,
he's
traveling,
which
is
fine
but
yeah.
He
said
that
he's
currently
reading
up
on
the
holder
side
of
the
issue,
credential
protocol
and
yeah
that
that's
what
our
next
meeting
will
be
about
sort
of
seeing
how
we
can
apply
his
knowledge
and
start
working
on
the
holder,
stuff.
A
Also,
now
a
holder
so
right
so
so
now
there's
a
connection
protocol
and
next
next
up
will
be
the.
If
you
can
like
hold
your
side
of
the
issuance
vertical
right.
A
A
We'll
do
that
all
right
so
overview.
Recent
work
done
so
we
had
contributions
from
Nyan.
A
Those
two
one
was
to
something
we
discussed
last
week
to
changing
the
return
tabs
of
the
unpacked
message,
wallet,
interface
and
the
other
one
was
kind
of
linking
to
that
as
kind
of
just
additional
Improvement,
deleting
some
code,
an
uncluttering
it
here
a
little
bit.
So
thank
you.
Thank
you
Nan
for
this
one.
Next
we
have
completed
a
book
that
has
completed
the
clean
fixes
across
the
code
base.
I
think
that's
in
terms
of
lint
fixing,
that's
I,
think
covered
everywhere,
and
then
we
had
just
merge.
A
Freshly's
warning
the
issue.
Credential
D2
and
I
saw
update
from
you
George
that
just
this
morning
as
well,
that
you
reported
interrupt
with
occupy
is
that
right.
A
Cool
cool,
so
I
yeah,
I
I
did
it
kind
of
high
level
overview
since
it
works
with
acapan
and
and
and
Bogdan
had
like
good
good.
A
It's
probably
most
qualified
here
to
review
this
as
a
author,
I
kind
of
trust
it
but
yeah
I
gave
it
overview
and
looked
good
to
me.
So
I
got
it
merged
and
I.
Guess
that's
what
has
been
done.
There
is
still
a
number
of
stuff
in
progress
and
in
review
so
linking
to
that
D2
still,
the
the
the
protocol
implementation
itself,
that's
still
pending
and
I
would
like
to
have
a
a
good
look
on
that
myself
and
I
see
it's
failing
right
now.
C
A
This
all
the
stuff
you
want
to
get
addressed
in
this
PR.
D
Yeah,
so
there's
yeah
I
want
to
get
them
done
in
this
PR.
But
probably
after
your
reviews,
you
know,
like
you
know,
testing
I,
don't
really
want
to
flesh
them
out
too
much.
If.
B
A
D
A
I
see
all
right
all
right.
Well,
I'll,
yeah,
I'll,
try
to
I'll
prioritize
this
there's
lots
of
things
to
do.
I'd
like
to
do
the
the
UNIF
fighter
mode,
but
I
think
this
should
get
a
higher
priority.
Quite
important
and
valuable.
D
A
Right,
cool
cool,
so
a
bit
cleaner;
okay,
any
other
comments
here
from
from
New
York
or
anyone
else.
D
A
Let's
make
this
so
in
terms
of
like
priorities
and
kind
of
epics
ongoing.
A
The
main
one
right
now
we
are
busy
with
is
the
completing
the
credit
stuff
just
making
sure
we
can
get
safely
rid
of
it.
So
it's
some
internal
testing
but
I'm
getting
ahead
of
myself
in
agenda,
but
yeah
as
some
were
mentioned
here,
so
so
right
now
prioritizing
this
this
piece
of
work,
so
we
could
hopefully
get
rid
of
video
tools
and
on
credits
early
next
week
and
then
after
that,
I
think
we
can
make
this
another
top
priority.
A
Get
this
reviewed
and
and
yeah
I'll
just
make
some
progress
here.
This
is
super
cool.
A
Okay,
where
did
we
left
collection
protocol
in
a
review?
There's
a
small
PR
from
myself
pending
for
review?
A
It's
not
big,
it's
mostly
removing
stuff,
so
the
that
kind
of
PR
removing
I,
basically
mainly
removing
automatic
problem
report
sending
from
connection
protocol,
which
is
something
which
is
now
not
happening
happening
in
any
of
the
protocols
and
I,
think
it's
Justified
to
remove
it
from
connection
protocol
as
well,
and
instead
this
this
PR
is
doing
one
function
incurred
message,
which
kind
of
will
simply
increase
message
for
the
connection.
A
A
So
if
you
guys
can
have
a
look
at
this
one,
it's
not
big,
that's
pending
and
then
in
progress.
Few
things
well
wait.
A
A
review
this
is
in
progress,
so
release
0.59
I'm
expecting
today
tomorrow.
A
In
the
meantime,
I
suppose
some
smaller
PRS
can
be
still
merged
in
even
the
connection
protocol,
I
think,
but
but
I
would
like
to
avoid
any
like
bigger
changes
into
059,
and
then
we
have
started
the
discussions
about
report.
We
we
we
mentioned
last
week,
so
Bogdan
has
proposed
some
ideas:
how
to
go
about
it
and
we
discussed
here
so
I
guess
this
is
kind
of
final
proposition
State.
We
we
came,
we
found
out
our
consensus.
A
I
know
George.
If
you
had
a
chance
to
take
a
look
at
this.
If,
if
not,
we
can
kind
of
go
through
it
quickly
now
and
just
see
what
you
think
about
it.
A
Main
idea
is,
like
you
know,
make
the
the
main
page
of
the
repo
a
lot
simpler,
so
put
everything
under
the
under
a
single
credits
directory
you're.
A
fan
of
this
idea.
Bogan
was
not
so
happy,
but
we
are
over
voted
him.
So
you
can
cast
your
road
as
well
here.
What
do
you
think
about
this?
But
the
the
rationale
was
to
make
the
main
page
a
bit
simpler,
but
then,
even
with
within
the
credits
directory,
there
is
some
restructuring.
A
So,
for
example,
I
mean
this
is
pretty
much
the
same:
I
guess,
but
but
right
now,
uni
F
of
Pi
would
be
under
wrappers.
So
so,
but
but
I
noticed
under
the
uni
F5
area.
V6.
Currently,
there's
two
directories:
there's
the
wrapper
itself
and
the
demo.
So
perhaps
the
demo
could
actually
go
under
the
agents,
because
it's
it's
essentially
a
mobile
agent
right
and
similar
way.
I
would
see
the
the
the
nions
mediator
and.
B
A
The
mediator
agent,
it
could
also
end
up
under
the
agents
directories
with
the
old
agents,
and
then
some
of
these
are
pretty
much
the
same
rz6
cores
without
change
for
now.
But
then
all
these
did
related
crates
goes
under
you
know,
Common
directory
same
with,
did
Doc
and
putting
the
Legacy
stuff
also
grouping
it
together.
A
D
You
guys
might
have
already
talked
about
this,
but
does
this
mean
that
there's
some
there's
a
bit
of
non-rust
code
within
the
crates
directory?
You
know
the
node
stuff
and
potentially
the
unify
Android
stuff?
Oh.
C
It
does
yeah
I
initially
wanted
to
put
the
wrappers
outside,
but.
C
But
it
is
a
very
good
point,
though,
and
I
mean
another
thing
worth
considering.
Is
that
and
I
I
mentioned
that
to
Patrick
and
Mira
was
crates,
might
not
be
the
best
name
for
that
root
directory
like
if
you
change
that
to
something
else,
then
the
problem
with
intermingling
node.js
and
rust
code
is
not
there
anymore.
D
Does
it
seem
wrong
as
well
to
like
call
some
of
those
binaries
a
crate?
Like
you
know,
the
simple
message
relay
is
a
binary
yeah.
That's
my
only
thoughts.
C
Yeah
I
mean
that's
what
I.
That's
what
I
didn't
really
like
about
this
directory
thing?
We
have
a
lot
of
stuff
and
it's
pretty
hard
to
classify
everything.
C
Into
into
one
common
thing-
and
it
doesn't
really,
in
my
opinion,
serve
any
real
purpose
like
okay,
it's
gonna
make
the
landing
page
a
bit
smaller
and
I
mean
considerably
considerably
smaller,
but
we're
not
like
we're
having
some
business
website.
It
is
a
coding
repository
right,
so
the
the
main,
in
my
opinion,
the
main
goal
behind
this-
was
to
kind
of
fact
some
things
together,
that
sort
of
Belong
Together
just
to
make
it
easier
to
navigate
through
the
directory
structure,
because
the
list
was
becoming
very
long.
So.
D
C
To
keep
them
at
the
base
level,
pretty
much
with
the
structure,
that's
in
there
now
within
the
crates
directory,
but
just
keeping
them
at
the
base
level.
C
It
I
don't
know
it
kind
of
makes
sense
to
me
and
it's
not
like.
We
have
a
lot
of
other
stuff
at
the
base
level
that
you
know,
people
would
get
confused
about.
C
There's
some
minor
files,
of
course,
but
maybe
that
docs
directory,
but
apart
from
that,
it's
fairly
intuitive
and
yeah
this
way.
Okay,
so
you
can
see
the
agents
which
again
should
pretty
much
be
self-explanatory.
We
have
a
separation
between
tools,
Legacy
code,
the
wrappers
that
we
have
to
me
so
perfectly
fine
repository
organization.
D
Yeah
I
think
I
agree
was
the
crates
directory.
Was
that
inspired
from
eighth
that
that
Reaper.
A
A
I
I,
don't
think
they're,
multiple
languages,
no
and
but
I,
don't
know
about
binaries.
It's
it's.
A
very
modular
kind
of
project
is.
C
The
thing
is
that
from
what
I've
seen
they
they
have
additional
things
at
the
top
level.
You
know,
besides
that
this
creates
a
library
or
whatever
they're
building
so
for
them
it
makes
more
sense
to
kind
of
compartmentalize
things
like
that,
like
the
coding
or
the
the
actual
rust
libraries
are
in
one
crates
directory,
but
then
they
have
different
things.
I
don't
know,
I
can
find
the
link
anymore.
Maybe
Patrick
can
bring
it
up,
but
because
I
wanted
to
have
another
look.
A
Yeah
they
have,
they
have
a
yeah,
they
have
been
been
read
apparently,
which
is
I,
guess
that's
the
main
binary.
They
have
crates
announce
Etc.
This
looks
like
some
other
stuff.
For
example,
I
have
dogs
testing.
They.
B
A
Code
is
here,
but
I
I
don't
know
what
what
it
encapsulate,
but
anyway
I
mean
we
don't
have
to
I
I,
just
it
was
in
kind
of
it
looked
it
looked
clean,
so
I
kind
of
a
good
inspiration
from
there
suggesting
this.
But
honestly,
you
guys
are
bringing
some
good
points
here
and
yeah.
We
are
not
like
building
a
Business
website,
so
it's
a
cool
report
story,
so
I'm
kind
of
I'm
kind
of
leaning
back
like
perhaps
you
guys
at
some
point.
A
Perhaps
we
can
bring
some
of
it
up,
or
at
least
at
the
minimum
on
this
at
minimum.
This
this
name
seem
to
not
really
serve
the
purpose
variable
in
our
case
but
I
guess.
Given
the
points
you
guys
made,
I
guess
I'll
be
Keen
to
King
to
move
it's
a
level
up
as
well
back
to
the
roots.
D
Okay,
cool
yeah
with
this
PR
for
the
the
unify
stuff.
D
A
Yeah
also,
like
you
know,
don't
feel
any
Rush
about
it.
Even
this
change.
You
know
what
we
are
kind
of
discussing
here.
It's
more
of
a
discussion
phase,
yet
I'm
trying
to
find
the
overall
concept
consensus,
how
to
go
about
it,
but
implementation
wise
it.
Just
whenever
happens
to
be
good
opportunity,
then
we'll
do
this.
We
wouldn't
break
many
PRS
and
I.
Guess
right
now
the
main
thing
like
a
bunch
of
stuff
has
been
merged.
A
Oh
that's
just
Edition.
That
might
be
easy
to
fix,
I
guess
for
a
mirror.
So
now
we
don't
have
to
worry
about
it
too
much
the
credential
issues.
V2!
That's
also
addition
mostly.
So
that
should
be
also
easy
to
sync
up
if
we
do
any
re-arc
and
other
than
that
as
well.
A
Those
changes
are
modifying
or
deleting
I
think
those
should
be
merged
before
so
yeah
I
have
this
another
PR
I
didn't
mention
some
some
test
refactoring
this
kind
of
PRS
I,
guess
the
the
ones
which
are
modifying
the
existing
code
base.
Let's
get
merge
those
and
then,
unless
there's
anything
else,
any
modification
kind
of
PR
pops
out
and
we
can
actually
Implement
and
reorganize,
reshuffle
everything
Whenever.
C
Yeah
yeah
I
just
pushed
the
pr
now
I
gotta
rebase
it,
and
let
me
warn
you,
this
thing
will
be
painful
and,
and
it's
not
even
it's
barely
even
scratching
the
surface.
So
anyway,.
A
All
right
yeah
so
that
actually
bringing
us
to
I
don't
have
it
here.
Do
I
I,
planned
I,
guess
the
the
the
the
work
you
are,
the
the
generification.
If
you
will
you
started
working
on
so
I
guess
I
can
get
given
what
you
said
now.
I
guess
I
can
move
it
too
in
progress
now,
but
maybe
to
to
share
with
your
I'm,
not
sure
we
talked
about
this
with
George.
Can
you
kind
of
talk
a
bit
about
the
changes
you're
doing.
C
Yeah
so
well,
the
changes
I
wanted
to
do
were
pretty
much
just
replace
some
like
some
of
these
trade
objects
with
generics,
because
there's
really
no
point
in
having
them,
because
generally
agents
will
just
just
you
will
you
pass
an
instance
of
a
wallet
you
don't
necessarily
swap
hot
swap
wallets
like
that
or
I
know
I,
don't
create
implementations
or
ledgers,
or
things
like
that.
C
C
It's
like
the
problem
is
deeply
rooted
in
many
corners
of
the
crates
that
we
have
in
the
sense
that
we
essentially
have
no
design
for
these
things
like
with
the
with
the
arc
trade
objects.
Thing
that's
been
in
in
the
entire
workspace.
C
You
know
like,
for
instance,
in
some
Auto
credits,
implementations
there
are
like
the
wallet
is
being
used
where
the
wallet
and
it's
being
used
in
the
sense
that
it's
encapsulated
within
the
structure
where
it
could
just
be
passed
in
ideally,
but
intermixing
components
like
this
is
allowed
now
and
pretty
much
used
everywhere,
because
well,
we
we've
just
been
using
like
the
code
base.
C
Only
has
these
Arc
trade
objects
and
you
can
get
away
with
pretty
much
everything,
but
there's
no
real
flow
between
how
things
are
supposed
to
work,
because
everything
references,
everything
yeah,
so
I
can't
even
begin
to
rub
my
mind
around
how
much
of
a
change
it
will
require
to
actually
fix
this.
C
But
for
now
the
pr
essentially
just
replaces
or
attempts
to
valiantly
attempts
to
replace
a
huge
part
of
these
trade
objects
with
either
concrete
implementations
of
certain
certain
types,
implementing
a
trait
or
just
some
generics
yeah.
So
that's
pretty
much
it
I'm
gonna
have
to
right.
Now.
I
still
have
some
rebases
to
do.
Apparently,
hopefully,
that's
not
going
to
be
too
painful.
C
C
Although
I
did
kind
of
work
around
live
the
CX,
because
Olivia
CX
is
not
the
first
class
citizen,
so
I
kind
of
worked
around
that
by
re-implementing
the
traits
over
the
arced
trade
objects
to
kind
of
get
around
with
just
passing
those,
because
there
is
just
it
becomes
even
more
painful
and
even
with
the
mocking
stuff
in
those
I
don't
know
it's
just
Madness
yeah.
C
Again,
I'm
not
even
sure
where,
like
how
necessarily
to
go
about
this
in,
like
in
iterative
steps,
I
obviously
have
one
great
idea
and
that's
rewriting
everything,
but
we
we
don't
really
do
that
here.
Yeah.
The
second
idea,
I
guess,
would
spawn
across
multiple
multiple
steps
of
adapting
code
and
rewriting
trades
and
then
rewriting
the
rewrites
to
kind
of
make
them
better
and
then
rewriting
tests.
C
I,
don't
know
we're
pretty
much.
Gonna
have
to
to
see
right
now.
The
intentional
is
like
I,
said
to
kind
of
set
the
groundwork
for
the
generics
thing
and
because
that's
going
to
allow
the
like
further
work
to
be
done
and
yeah.
A
C
Yeah
one
one
other
thing,
honestly:
I,
don't
even
know
if
we
can
actually
pull
this
off
like
this
I
mean
like
I,
said
everything
is
so
intertwined
and
the
problems
are
so
deeply
rooted
that
I
I
don't
know
it's.
It's
gonna
be
difficult.
I'm.
A
C
Mean
removing
the
arcs
is
really
not
like
in
some
places,
I
had
to
leave
the
arcs
again
because
of
no
ownership,
we're
no
clear
ownership
between
components,
but
where
I
could
remove
them
and
get
away
with
it.
I
did
because
why
not,
but
yeah.
C
A
Okay,
let's
see
next
week.
A
The
better,
the
sooner
the
working
on
the
the
peer
4
implementation,
which
is
similar
to
did
period
two
and
three
allegedly
so,
probably
not
too
much
of
of
challenge.
A
I
I
expect
to
implement
that,
given
we
have
already
the
two
and
three
and
and
one
studies
in
I
think
we
can
also
complete
the
get
that
did
the
exchange,
completed
and
I
assume
I,
as
I
mentioned,
I
haven't
been
on
the
list
for
the
Aries
board
group
call,
but
assume
things
are
moving
with
the
Deep
before
and
did
Exchange
kind
of
community
update,
aath
testing
for
the
exchange
we
did
before.
So
then
we
can
get
some
interrupt
results.
A
Hopefully,
with
this
thing
and
yeah,
that's
bring
us
to
the
end.
D
I'll
probably
start
the
presentation,
V2
messages
work
in
the
next
week,
it'll
be
very
similar
to
the
issue
credential
and
then
yeah
as
soon
as
we're
happy
with
or
arrive
at
some
consensus
on
how
to
implement
the
issue
of
V2
stuff
that
PR
I
have
up
for
review.
Then
I'll
start
on
the
presentation.
V2
protocol
as
well,
but
yeah
I'll,
do
the
same
thing.
One
PR
for
messages,
one
for
the
actual
implementation.
D
B
A
Reuse
to
land
on
because
Monday
Tuesday,
Monday
Tuesday
Wednesday
time
next
week
for
the
foreign.
A
More
time
from
all
the
reviewers
and
we
want
to
yeah,
we
want
to
get
the
DDX
critics
stuff
completed
and
video
tools
removed
and
and
I
suppose
that
once
we
do,
that,
it'll
be
a
lot
easier
to
contribute,
or
is
it
to
contribute
the
Aries
ascar
I'm,
not
sure
how
sure
I'm
not
sure
exactly
how
the
dependency
tree
is
going
to
change.
But
it's
really
going
to
be
a
lot
thinner.
So
I,
don't
know,
there's
gonna
be
a
still
some
challenges.
Some.
A
I
guess,
if
you
I
guess
it
depends
if,
if
the,
if
the
ask
car
implementation
is
in
the
repo,
it
doesn't
matter,
whether
stuff
is
feature
flagged
or
not,
right
yeah,
it
just
matter
of
whether
those
two
have
any
conflicts
and
I'm
not
sure
about
that.
But
do
you
know
if
removing
vdr
tools,
gonna
help
with
Oscar
I
know
we
touched
on
this
before
I.
Don't
remember
our
past
conclusions.
D
Yeah
I
think
it'd
be
pretty
much
ready.
The
only
other
thing
that
it
need
changing
is
I'm
not
sure
if
they
have
released
a
newer
version
of
Indie
video,
but
Indie
vdr
depends
on
Indie,
shared
RS
and
the
previous
version,
or
maybe
current
version
of
Indie
shared
RS.
That's
released,
has
a
dependency
conflict
with
Aries
ASCA,
so
you
need
yeah
I
sort
of
have
my
own
chain
of
of
forks
to
get
around
that
before
and
you
shared
RS
and
that
Forks
being
used
by
my
Fork
of
indie
vdr,
Etc.
A
Okay,
that's
hence
the
hence
the
issue
you
are
creating
two
weeks
ago
or
so
right,
yeah.
A
340.
we
should
check
on
that
how
how
it's
going
all
right,
if
it's,
if
it's
moving
forward
it
would
help
this.
It
would
be
great
to
have
Oscar
in
the
in
the
code
base
and
perhaps
then
we
could
even
use
it
on
a
mediator
or
stuff
like
that,
maybe
with
the
UNIF
fight
too
right
like.
Why
not,
why
not
to
run
the
new
components
with
NASCAR?
If
we
can.
A
A
Yeah,
that's
a
great
point
and
again
it's
this
dependency
stuff.
Yes,
I
think
it
will
be
the
reason
why
it's
so
currently
in
the
wallet
with
your
tools,
wallet
implementation
is
using
old
version
of
SQL
X,
which
is
even
a
forked.
A
It's
even
Fork
version,
but
and
it's
difficult
to
upgrade
it
because
the
upgraded,
the
the
latter
versions
of
SQL,
X
I
think
have
conflicts
with
the
bdr
tools,
kind
of
video
tools
and
on
credit
dependencies,
I
believe
and
but
once
we
get
rid
of
vdr2
summon
crates
which
should
be
in
a
few
days.
Hopefully,
then,
upgrading
SQL
X
should
be
easier
and
yeah
similar
with
askar.
That
might
also
be
easier.
B
A
No,
just
you
know
just
making
just
making
a
complete
circle
just
in
case
all
right,
then
I
think
we
are
done
here.
So
thank
you
and
have
a
good
week.
Cool.