►
From YouTube: April 28, 2022 - Ortelius Architecture Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
today
is
the
april
28th
architecture
meeting
and
we
just
got
off
a
a
board
meeting
call
and
one
of
the
ideas
that
we
came
up
with
is
every
basically
every
meeting
start
looking
through
the
issues
and
seeing
prioritizing
them
and
and
kind
of
giving
doling
out
the
issues
for
folks
to
work
on.
I'm
not
prepared
to
do
that
today,
but
that's
gonna
be
the
game
plan.
I
will
get
that
sorted
out.
A
We
may
do
that
coming
up
on
monday
on
tuesday,
monday
or
tuesday,
for
the
general
meeting
to
let
folks
know
that
there
will
go
through
a
few
minutes
and
see
who's
interested
in
what
on
the
issues
side.
So
we
keep
things
moving
along,
but
today
we're
focusing
on
our
start
at
akash
and
his
blockchain
just
want
to
get
a
get
caught
up,
ukrs,
where
you're
at
and
what
we
can
help
you
with.
B
Okay,
so,
as
you
know,
we
have
like
two
standalone
application:
one
is
for
nfp
and
the
other
one
is
for
leisure,
so
currently
they
are
working
as
a
like
a
standalone
application.
The
objective
that
I
that
I'm
working
currently
on
is
to
create
one
application
that
you
use.
You
know
the
dependent
methods
or
calls
from
those
modules.
A
Cool-
and
I
can't
remember,
was
the
nft
code
in
node.
B
A
And
for
this
stuff
feel
free
we're
not
real,
strict
on
merges
and
stuff
like
that,
and
so,
if
you
want
to
go
ahead
and
merge
things
yourself.
A
Go
ahead
and
just
create
a
pull
request
and
merge.
It
yourself.
B
A
Just
to
let
you
know,
I'm
not
that
type
of
person
that's
going
to
freak
out.
If
you
do
a
a
pr
and
you
break
something
because
the
way
github
works,
we
it's
really
hard
to
get
rid
of
history
and
it's
even
harder,
since
we
all
have
a
copy
of
the
of
the
repo.
At
some
point,
so
you
know
some
other
projects
are
really
strict
about.
Who
can
do
prs
and
things
like
that,
but
my
viewpoint
is
more.
We
can
move
things
along
the
better
than
being
bottlenecked.
A
He's
the
only
person
that
we
we've
excluded
permissions
for
going
directly
against
the
re,
the
main
repo
car
shirt,
your
pr
has
been
merged,
so.
A
D
A
B
A
Perfect
yeah,
so
just
to
recap
for
folks
that
weren't
here
last
time
I
initially
threw
out
the
the
requirement
to
try
to
use
python
for
the
xrpl
and
what
we
kind
of
found
joseph
ran
into
this
initially
for
the
nfts
was
there
was
a
python,
and
so
the
nfts
live
inside
of
ipfs,
which
is
an
interplanetary
file
system
which
is
a
distributed
file
system.
A
That
gives
us
a
way
to
have
an
immutable
object
on
a
file
system
and
that
immutable
object
in
our
world
is
our
json
definition
of
a
of
an
application
version
or
component
version.
So
we're
going
to
take
the
out
of
our
database
when
we
go
and
create
a
new
version,
we'll
go
ahead
and
create
that
mirror
that
into
an
nft.
A
So
the
nft
is
just
going
to
be
a
json
file
that
is
stored
in
the
ipfs,
which
makes
it
immutable
and
then
and
and
what
we
found
was
joseph
couldn't
get
the
python
piece
to
work.
So
he
ended
up
going
over
to
node
and
that
made
things
a
lot
easier.
Now
utkar.
She
started
with
python
first
yeah
and
now
you're
moving
over
to
node.
To
get
everything
consistent.
Is
that
correct?
D
He
knocked
and
yeah
he's
yeah
like
a
real
impulsive
steve.
Please.
A
He
scratches
on
the
door,
so
he
knows
time
for
him
to
come
in
all
right.
So
now,
you're
moving
over
to
to
node
on
your
side
on
the
larger
side,
correct
and
how's
that
going.
B
Yeah,
the
code
for
leisure
is
all
already
completed,
but
the
problem
is
the
nft
code
and
leisure
code
they're
working
as
a
standalone.
So
we
need
to
merge
that
code
into
into
a
application
that
works
for.
A
And
have
we
found
any
examples
to
that
kind
of
tie
it
all
together
yet
or
is
that
something
that
we
need
help
on.
B
A
All
right
perfect,
so
if
we
need
help
on
pulling
together
the
ledger
side
with
the
nft
side,
if
we,
if
we
can't
get
any
of
the,
what
we
think
is
the
path
to
merge
it.
Let
me
know-
and
I
will
make
sure
that
we
can
get
somebody
from
ripple
who's.
The
the
creators
of
the
xrpl
group
to
give
us
some
help
on
that
front.
So
brian
dawson
works
for
ripple
and
they
are
the
core
contributors
to
the
xrpl.
A
So
he
can
get
us
some
resources
if
we
need
to
so,
if,
if
you're,
if
you're
having
a
hard
time,
just
speak
up
sooner
than
later,
so
we
can
get
that
scheduled.
B
A
A
I've
seen
other
projects
that
tried
to
use
a
language
that
doesn't
really
that
isn't
mature
yet
around
certain
technologies.
So
I
know
like
rust
and
blockchain.
They
exist.
You
know
their
support
in
in
blockchain
for
for
the
rust
language,
but
it
isn't
mature
enough.
So
you
spend
all
this
time
trying
to
fix
bugs
instead
of
coding,
a
solution
and
I'm
glad
we're
moving
to
nodes
to
keep
things
moving
along
cool.
So
what
do
you
think?
A
What
do
you
think
your
kind
of
your
your
time
frame
not
trying
to
hold
you
to
a
certain
date?
But
what
do
you?
What
do
you
think
you're
shooting
for.
A
Cool
excellent,
well
sergio's
volunteering.
I
can
hear
him
trying
to
speak
up.
E
D
A
All
right
awesome,
so
some
other
things
anything
else
on
the
the
ledger
and
the
nfts.
Oh
just
the
one
thing
brian
did
say
that
they
are
going
through
the
grant
process
and
starting
the
reviews.
A
I
told
them
that
we've
been
working
on
getting
a
sample
code
in
our
repo,
and
he
was
excited
about
that.
So
even
if
we
have,
in
other
words,
commit
stuff
to
the
repo
and
just
go
ahead
and
merge
it
yourself
to
keep
that
process
moving
along,
even
if
it's
not
a
complete
working
solution.
As
long
as
we
have
commits
going
showing
that
we're
we're
doing
work,
that'll
help
with
that
that
grant
yep
sure,
cool
and
we'll
we'll
let
sasha
merge
all
the
prs
and
be
responsible
for
like
the
code
reviews.
A
All
right
cool,
so
anything
else
on
the
blockchain
and
nfts.
B
Yeah
so
one
thing
we
did
discuss
with
josef
and
all
so
there
are
like
two
types
of
like:
there
are
two
ways
we
can
use.
Ipfs
storages.
One
of
them
is
what
joseph
was
using.
So
he
was
using
the
third
party,
ipfs
storage.
B
So
when
you
use
that
service,
whatever
you
know
the
what
you
call
cids
that
crds
that
are
created,
they
are
immediately
available
to
the
outside
world.
So
that
becomes
public
right.
But
there
are,
there
is
another
way
of
you
know
using
ipfs
storages,
that
is
in
repo
ipfs
storage.
So
you
can
do
all
those
processes,
but
that
will
be
at
the
repository
level
and
later,
when
you
want
to,
you
know,
make
make
those
cids
as
a
public.
Then
you
can,
you
know,
use
either
pinata
or
other
third
party
like
services
that
are
there.
A
Okay,
yeah,
I'm
I'm
okay
with
having
the
information
public
it
actually
in
the
long
run.
So
if
I
let
me
kind
of
give
you
guys,
my
vision
here
is
the
concept
of
an
application
and
the
components
at
the
microservices
world
is
going
to
become
more
public,
so
we're
going
to
have
services
that
exist
outside
of
the
outside
of
a
company
that
need
to
be
managed.
A
So,
for
example,
like
wordpress
wordpress
is
made
up
about,
I
think
like
six
different
components,
including
like
or
postgres,
is
one
of
the
database
components
and
when
that
wordpress
version
gets
created
for
a
company,
you
know
what.
What
does
that
look
like
you
know,
what's
the
components
that
are
making
up
the
application,
that
information
should
be
applied
to
the
ledger
that
we
have
a
history
of
of
this
is
what
the
config
looked
like
at
this
point
in
time.
A
So
the
ledger
is
just
the
immutable
transaction
log
that
we
get
to
keep
track
of.
What
went
where
and
basically
snapshot
things
as
we
go
so
that
information
being
public,
I'm
I'm
okay
with,
because
there's
nothing
like
really.
A
You
know
like
there's
no
secrets
in
there,
there's
not
like
any
classified
information
at
that
level.
Now,
there's
another
concept.
So
to
answer
your
question,
of
course,
using
the
public
or
the
the
internal
one,
I
can
go
either
way.
A
Whichever
is
easier,
I
think
we
go
with
the
nft.storage
for
what
we're
doing,
for,
like
the
proof
of
concept,
isn't
going
to
cost
us
anything
so
we're
okay,
sticking
with
that
front,
which
is
what
joseph
did
now,
one
of
the
other
things
that,
in
the
grant
proposal
that
we
put
together
is
they
have
a
concept
in
in
xrpl.
A
So
what
I
kind
of
foresee
is
that
we're
going
to
end
up
having
our
main
blockchain
of
like
the
components
and
stuff
like
that,
as
they're
coming
out
of
the
build
process,
we're
snapshotting
those
in
the
ledger
and
then
when
somebody
goes
to
pull
together
components
into
an
application,
that's
internal
to
a
company
that
would
go
that
configuration
definition
would
go
into
their
internal
side
chain.
So
what
ends
up
happening?
A
Is
you
have
this
public
blockchain
of
component
versions
and
then
you
have
internal
company
definitions
of
what
how
an
application
is
putting
being
put
together,
and
this
reason
why
this
is
going
to
happen?
Is
companies
don't
want
to
expose
all
the
the
technology
they're
using
because
they
see
software
as
a
competitive
advantage,
so
exposing
what
they're
doing
versus
you
know?
One
bank,
you
know
bank
america
versus
wells
fargo.
They
want
to
make
sure
that
bank
of
america
is
not
showing
up.
A
A
Now,
when
we
talk
about
like
at
the
wallet,
if
we
do
have
a
public
application
like
wordpress,
and
we
want
to
know
that
wordpress
is
deployed
to
these
one
million
customers,
this
version,
that's
where
the
wallet
will
come
into
play
and
we'll
have
transactions
at
that
level,
where
you
actually
buy
wordpress
for
zero
dollar
amounts
from
our
blockchain,
and
you
put
it
into
your
wallet
when
we
when
we
finally
get
to
that
level.
A
That
person
that's
doing
the
buying
of
that
wordpress
version.
We
will
want
to
make
sure
that
it's
only
an
id
and
not
necessarily
like
you
know,
wells,
fargo
or
bank
of
america
as
the
identifier
and
that
that's
kind
of
like,
like
your
your
bitcoin
blockchain,
it's
pretty
anonymous,
you
don't
know
who
who
you're
buying
or
selling
from
you
just
have
these
ids.
There
are
some
ways
you
can
kind
of
eventually
groom
and
work.
Your
way
to
the
original
you
know
to
the
owner
of
that
that
transaction.
A
But
it's
really
hard,
and
I
I
foresee
that
in
the
case
of
like
wordpress
being
purchased
for
zero
dollar
amounts
by
these
million
customers,
that,
if
there's
a
fix
to
php
and
wordpress,
that
we
can
then
contact
those
you
know
send
out.
I
don't
know
how
we
would
do
it
exactly,
but
we
know
the
ids
of
the
consumers
and
then
we
could.
A
We
can
do
a
notification
through
the
id
process
that
they
need
to
update
their
version
of
of
wordpress,
because
we've,
we
know,
there's
a
vulnerability
in
their
version
that
they're
using
and
that's
where
the
side
chains
will
come
in
into
play
as
well
at
a
federated
level.
So
we'll
have
our
main
block
chain
and
we'll
know
that
these
side
chains
are
consuming
what's
off
of
the
public
blockchain
and
that
we
can
notify
the
side
chain
owner
in
some
way
that
they
have
to
go
and
update.
A
So
we'll
know
we'll
be
able
to
look
in
from
the
public
blockchain
into
not
necessarily
into
the
side
chains,
but
we'll
be
able
to
reference
the
side
chains.
Now,
if
you're
in
the
side,
the
side
chain
and
looking
back
out,
you
can
see
everything
from
from
your
organization
all
the
way
up
into
the
public
one.
But
you
won't
be
able
to
see
across
organizations
from
one
side
chain
to
another
side
chain.
A
So
we'll
have
some
work
to
do,
but
that's
kind
of
the
the
vision
I
have
and
if
we
start
looking
at
pulling
this
into
with
what
the
open
ssf's
doing
at
the
package
level
we'll
be
up
into
the
millions
of
of
records.
Pretty
quick
keeping
track
of
stuff
so
it'll
be
it'll,
be
fun,
it'll,
be
a
journey
and
we'll
do
we'll
do
a
lot
of
learning
along
the
way
to
to
make
sure
we
can
get
this
structured
and
figured
out
correctly.
D
Yeah,
I'm
I'm
good.
I
just
think
that
I'm
well
first,
I
I
feel
bad
to
not
be
actively
working
on
this,
but
from
the
other
side,
I
think
we
need
maybe
to
clone
wood
cars
or
find
someone
with
the
same
compromise.
A
We
have
joseph
joseph
cranked
out
that
nft
pretty
quick,
so
so
we
do
have
somebody
that
we're
we're
in
the
process
of
cloning.
We've
got
one
arm
done.
D
D
A
And
oh,
and
as
just
a
topic
in
general
that
we
need
to
kind
of
figure
out,
like
I
said
at
the
beginning
of
how
we
can
get
folks
working
on
issues
and
maybe
getting
the
issues
out
of
my
head
and
a
little
more
clearer,
more
concise
for
folks
to
work
on
it
and,
as
sergio
has
his
his
project
board
that
he's
working
on
to
kind
of
help.
Categorize
things
so
we're
getting
there
we're
trying
to
take
some
steps,
but
it's
definitely
going
to
be
a
learning
process
to
make
this
work.
A
A
All
right
cool,
so
I've
been
working
on
the
pulling
in
information
from
the
s-bomb
perspective.
A
So
one
of
the
things
that
I've
been,
I
can't
remember
who
did
the
coding
change,
but
you
know
we
have
a
way
as
part
of
the
cicd
process
to
grab
the
s-bomb.
That's
been
generated
from
the
different
tools,
the
one
that
seems
the
to
work.
A
The
best
is
sift
from
encore,
so
sift
the
look
at
any
container
and
dive
into
the
container
and
pull
out
the
os
level
packages
like
the
debs
and
rpms
if
it's
a
node
application
or
if
it's
a
mixing,
node
and
and
maybe
some
goaling
it'll
go
through
and
pull
out
the
dependencies
and
put
them
into
an
sbdx
or
cyclone
formatted,
json
file
that
we
then
upload
over
to
the
back
end
side,
which
we
associate
those
packages
to
the
component
version.
So
all
that's
working,
really
cool
and
working
really.
A
Well,
I
have
figured
out
that
there
is
a
new
cve
database.
That's
been
kind
of
groomed
over
the
last
couple
years.
Let
me
find
it
here.
A
A
So
it's
actually
been
groomed
together
out
of
a
different
set
of
databases.
So
it's
it's
one
of
the
more
comprehensive
ones.
A
And
one
of
the
things
this
is
allowing
us
to
do
is
to
basically
in
real
time,
associate
together
the
package.
So
where
is
it.
A
We
we
could
pull
up
all
this
this
this
information
and
to
make
that
query.
It's
super
simple.
Basically,
you
pass
in,
like
I
just
did
log
for
j,
and
I
can
put
in
like
2.16.0.
A
No,
I
forgot
the
format
anyways,
there's
a
an
api
endpoint
that
we
get
to
hit
as
part
of
this
information.
So
what
I'm
doing
is
cross-referencing.
The
s-bomb
with
these
cves
and
one
of
the
things
that
we're
going
to
need
is
this
database.
A
Even
though
we
can
hit
the
end
point,
that's
available,
it's
just
too
slow.
So
we
need
to
kind
of
offload
all
this
data
locally
and
I
haven't
created
an
issue
yet,
but
I
think
we
can.
I
started
playing
around
around
with
a
rango
db
as
a
document
store
to
load
in
the
json
and
then
query
it
using
it's
called
aql,
which
is
a
graphing
type
of
query
language,
and
it's
super
fast.
A
So
some
of
the
things
that
we
need
to
do
is
we
need
to
to
stand
up
in
a
rango
container
in
our
kubernetes
cluster
and
then
also
have
a
nightly
process
to
go
or
hourly
process
to
go
download
the
latest
cbes
from
this
website.
So
what
ends
up
happening?
Is
they
come
down?
They
have
just.
These
are
just
backed
by
json
files,
so
the
json
files
can
be
pushed
into
the
rangodb
real,
easy,
just
a
simple
command
line
and
then
we'll
be
able
to
query
it
from
our
side
of
things.
Pretty
quick.
A
So
that's
kind
of
the
the
next
thing
on
the
horizon
that
we
need
to
kind
of
get
sorted
out.
Also
with
the
libyar
stuff
that
aisha
aisha's
been
working
on.
It
looks
like
those
databases,
are
json
formatted
as
well,
so
I
think
we're
getting
to
the
point
we're
going
to
start
moving
towards
a
more
of
a
a
document
store.
A
You
know
a
graph,
a
graph
database
instead
of
the
the
postgres
database
here
and
I
kind
of
foresee
that
we'll
have
a
little
bit
of
both
in
in
the
interim.
I
I'm
not
in
that
in
the
long
term,
I
don't
think
we'll
be
able
to
move
away
from
the
the
postgres
database
very
quickly,
but
I
think
we
can
start
chipping
away
at
it
at
that
level.
A
So
looks
like
I
have
to
tracy
just
told
me:
I
had
to
jump
on
to
another
meeting,
so
I'm
going
to
open
a
couple
issues
on
that
curse,
reach
out.
If
you
need
any
help
on
pulling
that
together
on
the
ledger
side
with
the
nfts
and
then
we'll
touch
base
on
the
at
the
general
meeting.
A
However,
early
next
week
and
we'll
we'll
see
where
things
are
going
to
make
sure
we
have
everybody,
all
the
resources
happening
and
I'm
gonna
go
create
a
couple
issues
around
the
rangodb
and
the
cbes
database.
So
if
anybody's
interested
in
some
helm,
charts
and
learning
orango,
let
me
know
all
right:
sasha
I'll
get
you
on
the
list.