►
From YouTube: Aug 4, 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
Alrighty
welcome
everybody
to
the
august
4th
or
to
this
architecture
meeting.
Let
me
drop
the
link
again
in
case
you
came
in
a
little
bit
later.
A
There
is
the
link
to
the
docs
so
go
ahead
and
sign
in,
and
today's
probably
gonna
be
a
relatively
quick
meeting,
because
we're
kind
of
like
on
a
taking
a
little
bit
of
time
off
in
august
for
everybody
taking
vacations,
but
in
in
general
we
officially
got
the
xrpl
grant
and
what
we
will
be
doing
is
september
after
labor
day
in
the
states
will
start
kicking
off
the
architecture
piece
on
creating
what
we
need
to
do
around
the
blockchain
and
persisting
our
json
information
into
an
nft
ipfs
storage.
A
A
A
Last
time
I
think
I
mentioned
there
was
a
an
ipfs
storage
or
an
nft
storage
called.
I
think
file
coin
that
was
supposed
to
be
relatively
cheap
compared
to
using
like
a
s3
bucket
or
one
of
the
other
storage
mechanisms
out
there.
The
amount
of
data
that
we're
gonna
have
initially
is
gonna,
be
pretty
low.
We're
not
storing,
like
you
know,
videos
or
anything
like
that,
so
our
our
nfts
are
gonna,
be
pretty
pretty
small,
but
I
think
we're
gonna
have
a
good
number
of
them.
A
So
anytime
we
make
a
change
to
an
application
or
component
or
we
do
a
build.
We're
gonna
end
up
pushing
that
over
to
the
blockchain
and
into
the
storage
process.
So
that's
where
we'll
have
a
good
deal
of
transactions
that
we'll
have
to
manage
at
that
level.
B
Quick
question:
yep,
quick
question,
so
the
storage,
how
important
is
the
storage
decision
straight
up?
Does
it
need
to
be
immutable?
So
if
we
decided,
maybe
you
know,
let's
say
we
start
industry
and
then
we
move
do
we
obviously
have
to
transfer
that
and
then
hook
it
back
up
right.
A
Yeah,
so
it
would
be,
we
do
want
immutable
storage
and
that's
one
of
the
things
that
when
we,
when
you
use
the
nft,
that
nft
ends
up
being
immutable
now
the
the
tricky
part
with
nfts
is
you
want
to
put
them
into
a
distributed
network,
so
they
can't
really
be
manipulated.
You
know
you
can
manipulate
them,
but
you
won't
as
soon
as
you
go
and
touch
and
start
messing
around
the
data.
You
invalidate
the
the
key
for
it.
A
B
And
it's
a
series
of
files
in
the
storage
or
I'd
like
to
understand.
I
can
read
up
on
it,
but.
A
Yeah,
so
what
we're
gonna
do
is
I
at
this
point,
we'll
have
two
two
levels
of
storage
that
we'll
need
so
we'll
have
a
storage
at
the
component
level.
So
when
a
component
is
a
version
of
a
component
is
created,
we
would
take
that
information
as
json
and
push
it
into
the
storage.
So
everything
about
the
component,
you
know
the
the
name
of
it.
You
know
who
created
it.
You
know
the
basic
service
catalog
stuff
around
the
component
and
then
also
the
component
s-bombs
now.
A
You
know
like
a
python,
flask
application,
we're
going
to
have
some
s-bomb
related
to
python
and
we're
going
to
have
s-bomb
related
to
the
container
that
the
flask
application
is
running
on,
so
that
that
that
s-bomb
information
plus
the
component
service
catalog
information
would
be
basically
a
snapshot
of
json
that
we'd
push
into
storage.
A
Now
the
next
level
of
storage
is
at
the
application
level,
so
the
application
versions
are
going
to
reference
component
versions
and
that's
where
we
do
a
second
storage
of
json
with
little
relationships.
C
B
A
Yeah,
let
me
I
will
get.
I
will
drop
the
link
to
the
proposal
and
all
that
stuff,
so
you
can
read
up
on
it
and
in
there's
a
repo
out
there.
I
believe
it's,
let
me
see
if
it
has
everything
out
there.
B
Sorry,
you
crashed.
We
spoke
at
the
same
time.
A
D
So
see
what
I
was
wondering,
so
we
are
showing
this
data
and
this
data
is
taking
mutable
data.
So
whenever
a
new
version
of
a
data
is
persisted,
there
will
be
a
new
set
of
data
right.
So
so,
during
the
time
there
will
be
like
before,
storage
will
have
a
lot
of
data
because
so
like
for
my
first
question
is
like:
do
we
have
it,
like
instance,
of
that
database,
or
that
is
like
global
instance
that
can
be
accessible
like
for
anyone.
A
So
let's
say
we,
we
are
like
ortillius
when
ortelius,
because
it's
an
open
source
project
when
we
go
and
build
ortilius
and
we
publish
you,
know
the
home
chart
and
stuff
like
that
that
from
the
artillious,
basically
dashboard
or
website,
you
know
the
the
application,
not
the
web,
that
you
can
go
and
look
at
the
version
of
ortillius
that
was
published
and
see
the
dependencies
and
the
s-bombs
that
are
associated
with
over
to
this
open
source
project.
A
A
If
we're
going
to
have
that
company
stand
up
their
own
blockchain
process
or
if
we're
just
going
to
do
it
more
anonymously
kind
of
like
bitcoin.
Does
you
know
where
it's
more
of
anonymous
transactions
that
you
can
you
know
who
you
are
yourself?
But
nobody
knows
who
you
know
you?
Could
you
could
identify
your
transactions
and
stuff,
but
somebody
else
can't
go
and
find
out
who
you
are
and
then
there's
another
process.
A
They
call
them
side
chains,
it's
kind
of
like
a
federated
blockchain
model
and
I
think
we're
gonna
run
into
this
a
lot
with
ortilius,
because
they're
gonna
be
other
blockchain
and
ledgers
that
we're
gonna
need
to
reference.
So,
like
sig
store,
is
going
to
be
another,
it's
not
necessarily
a
blockchain,
but
it's
another
ledger
that
we're
going
to
need
to
be
able
to
reference
and
validate
against.
A
Persia
is
another
open
source
project,
they're,
building
open
source
packages
and
signing
them
in
and
like
doing
immutable
builds
around
those
there.
They
have
a
blockchain,
then
there's
gonna
be
a
couple.
Other
notary
2
is
going
to
be
coming
out
around
signing
and
identification.
A
So
I
think
that's
where
we're
going
to
have,
from
the
artillia's
point
of
view
we're
going
to
be
kind
of
like
snapshotting,
all
this
together
and
being
able
to
track
those
relationships
across
multiple
ledgers
is
what
we're
going
to
have
to
keep
in
the
back
of
our
mind.
D
A
Right
and
that's
where
the
the
xrpl
calls
them
side
chains,
so
that
organization
could
stand
up
their
own
ledger
that
they
would
be
controlling
the
access
to
so
artelias
would
be
able
to
read
and
write
to
that
ledger
internally,
but
somebody
from
the
outside
world
couldn't
come
into
that
ledger
and
you
know
exploit
it.
D
A
And
that's
going
to
be.
The
challenge
for,
for
us
is
being
able
to
look
at
this
information
across
these
dispersed
locations.
A
So
we
are
going
to
be
doing
a
lot
of
federating
and
that's
going
to
be
one
of
the
the
things
that
we
have
to
figure
out.
You
know:
do
we
federate
on
the
fly,
or
do
we
have
like
a
batch
bosses
or
cron
job
that
does
the
federating?
A
You
know
where's
that
data
persisted
when
we
federate
it,
those
type
of
things
and
that's
why
I
keep
on
pushing
to
look
at
like
the
orango
db
and
some
of
the
other
graph
databases,
because
we're
going
to
have
a
large
number
of
trans
relationships
in
the
transactions
that
we
kind
of
have
to
navigate
through.
E
So,
if
we're
at
a
good
spot
for
it,
I
have
a
few
questions
yeah,
so
things
when
I
look
at
an
architecture
and
I
I
certainly
read
through
it
and
I
have
it
open
now,
I
would
expect
to
see
that
I
don't
find
is.
First
of
all,
I
don't
see
a
data
model
for,
for
example,
what's
held
in
the
repo
in
the
service
catalog.
A
Right
and
that's
one
of
the
things
that
we
are
in
the
process
of
figuring
out.
A
What
the
requirements
are
and
like
ukrs
is
saying
when
we
get
into
this,
what
is
where
type
of
a
type
of
world
who
has
access
to
what
that's,
where
we'll
be,
building
out
that
that
data
model?
I.
E
A
Do
have
a
database
tables
today
that
julius
is
running
on
top
of
postgres,
but
the
I
think
what
we're
going
to
need
to
do
is
move
that
more
into
a
document
based
database,
so
that
I
think
it's
going
to
change
the
data
model.
A
little
bit.
E
For
you
know,
for
people
to
call
into
the
catalog-
and
you
know,
for
example,
search
services
use
services
they
have
to
format
in
some
fashion.
Similarly,
I'd
expect
to
see
a
few
other
things,
some
form
of
overview
diagram
that
shows
how
things
fit
together
and
what
the
notional
flows
are
is
something
I
would
expect.
A
Yeah,
I
think
that's
in
the
artillious
documentation.
We
have
that
diagram
and
it
may
not
be
in
this
in
the
xrpl
diagram,
documentation.
A
Oh
okay
and
I
think
it
I
think
it
got
moved
over
to
the
documentation
site
so
I'll
have
to
update
that
that
invite
and
get
that
to
you
all.
E
C
A
And
if,
if
it's
not,
if
what
we
have
isn't
answering
your
question,
we'll
make
sure
that
we'll
get
an
issue
open
and
get
that
updated.
Well,.
E
A
Okay,
that
works
yeah.
If
you
go
to
docs.ortilius.io,
that
will
be
the
you'll,
see
a
user
guide
and
a
contributor
guide
underneath
that
the
user
guide
will,
I
should
have,
if
I
remember
correctly,
some
of
the
architecture.
Information
in
the
introduction.
C
E
So
anyway,
I'll
I'll
just
like
I
said
I'll
drop,
you
a
quick
note,
and
you
know
you
can.
Let
me
know
what
I
should
be
thinking
and
so
on.
A
So
that's
kind
of
what
we
have
going
on
with
the
xrpl
in
the
grant.
Like
I
said
we'll
be
starting
in
september,
we
may
bring
on
a
person
that
has
been
doing
blockchain
work
for
the
last,
like
10
years,
has
done
extensive
stuff
with
bitcoin
with
ibm
and
a
couple
other
well-known
blockchain
implementations
also
we'll
be
able
to
get
support
from
the
xrpl
developers
through
the
discord,
their
their
discord
channel.
A
So
we're
not
gonna
be
out
there
alone
on
this,
which
is
gonna,
mean
we
have
some
decent
support.
It
looks
like
so
with
that.
That's
what
I
have
brad
do
you
want
to
do
an
update
from
your
side
on
the
what
you
have
going
on
with
captain
and
and
the
get
ops
pieces
and
stuff.
B
Yeah
sorry
get
captains
they've
improved
their
web
hook,
integration,
so
we're
originally
gonna
write
a
golang
plug-in
for
kept
in
the
the
talk
so
italia.
So
now
we
don't
really
need
to
so
we
can
actually
leverage
the
the
webhook
service.
B
So
we
have
an
environment
ready
to
go.
We
just
need
to
have
some
sort
of
a
flow
diagram
with
api
calls
of
what
we
actually
want
to
achieve
and
then
we're
ready
to
go
straight
away.
So
I
think
we're
going
to
have
a
session
next
week
on
that.
B
A
Well,
you
may
want
to
do
something
with
mermaid
and
kind
of
do
like
a
state
diagram.
So
it's
easier
to
follow.
You
know
with
the
columns
and
the
the
transactions
going
back
and
forth.
A
Yeah,
because
I
think
I
think
this-
the
state
diagram
kind
of
you
know,
from
top
to
bottom
will
be
easier
to
follow,
will
be
another
layer
for
people
to
follow
other
than
the
one
sasha
did
with
with
the
transactions
going
from
one
tool
to
the
next
tool.
I
think
we
need
both
of
them,
so
I
think
the
state
diagram
should
be
what
we
try
to
tackle
next.
B
A
To
do
it
yeah
exactly,
I
I
think
in
that
state
diagram
we
should,
you
know,
lay
out
the
transactions
lay
out
the
payloads,
so
we
all
are
on
the
same
page.
B
Yeah,
so
I
guess
in
a
way
I'm
blocked
by
that,
so
other
things
I've
been
looking
at
as
well
is
integrating
testing
into
this
workflow,
because
what
I've
found
is
when
we're
doing
things
like,
if
folks
want
to
do
like
canary
deployments,
for
example,
you
can
do
with
the
canary
deployment
at
2
a.m,
and
you
can
generally
canary
deployment.
Will
just
poll
like
prometheus
and
say
you
know:
did
you
have
500
errors?
B
While
we
were
progressing
the
application
and
then
what
I've
found
is,
if
you
don't
have
any
real
traffic,
then
you're
not
really
going
to
get
those
errors.
So
adding
testing
to
that
is
very
important.
So
I've
been
working
a
little
bit
with
cubeshop,
so
there
are
open
source
incubator
and
they
have
they're
sort
of
in
my
eyes,
they're
sort
of
leading
the
testing
a
little
bit
yeah.
B
It's
a
bit
of
a
a
gap,
in
my
opinion,
in
in
the
cloud
native
space,
so
they've
got
tools
like
trace
test
test
cube
test
cube
would
be
an
easy
one
for
us
to
adopt,
because
you
can
just
upload
postman
collections
and
then
you
can
sort
of
automate
it
into
the
pipeline.
Pretty
easy.
So
I've
been
sort
of
spiking
that
a
little
bit
to
see
how
we
can
fit
that
in
cool
and
yeah
yeah
pretty
much
just
just
really
ready
to
go.
B
We
thought
you
know
it's
just
we
just
have
to
have
that
meeting
to
to
get
started
really.
A
Yeah,
since
I
got
both
you
and
kershaw
on
the
line
now
does
tuesday
work.
C
B
I
I
I
don't
know
what
your
time
is
now,
but
even
after
this
meeting
I
would
be
free.
But
if
you're
not
this
one
too.
A
No,
I
have
another
meeting
here
in
five
minutes.
So
yeah
can
we
do
tuesday
same
time,
yep
yep,
that
does
that
works
for
both
of
you
all
right
cool.
I
will
send
out
an
invite
and
make
sure
everybody
has
the
right
information
there.
So
I'll
get
that
sent
out
here
in
a
little
bit
the
invite
for
tuesday
same
time
as
this
meeting.
B
Yeah
and
I
want
to
talk
to
tracy-
maybe
soon
as
well,
about
keeping
new
contributors
sticky.
So
we
have
a
lot
of
new
contributors
coming
through,
but
I
feel
like.
We
need
to
work
a
little
bit
more
on
the
program
about
how
we
can
actually
get
them
involved
and
staying
because
they
join
and
then
maybe
they
get
a
little
bit
lost
and
they
just
sort
of
go
away.
C
B
A
And
then
I
know
the
the
one
thing
that
we
struggle
with
it
and
the
in
general
in
the
community
is
just
like
project
management.
A
You
know
so,
if
that'd
be
like
one
role,
that
we
really
kind
of
need
is
somebody
to
help
with
the
the
project
management
and,
like
you
said,
get
when
the
new
folks
come
in
getting
them
working
on
something,
even
if
it's
small
yeah
those
those
type
of
things
I
just
get
get
way
behind
on,
and
I
just
can't
keep
up
on.
B
Yeah
we
could
con
instead
of
making
it
like
a
community
role,
an
extent
you
know
like.
I
think
we
have
like
science
ambassador.
We
have
a
few
other
roles,
but
maybe
that's
another
role
we
could
have,
which
would
be
quite
effective.
A
Even
yeah,
and
even
if
it's
just
like,
if
somebody
comes
in
new,
we
kind
of
do
like
I
kind
of
on
discord.
Do
a
quick,
like
I
don't
know
like
interview
to
find
out
what
they're
interested
their
skill
set
and
then
being
able
to
point
them
to
a
starting
issue
to
work
on.
B
Yeah,
I
think
the
I
really
love
the
the
you
know,
the
badges
you
get
for
a
contributor,
it's
once
every
microservice
visionary
but
yeah
the
new,
especially
younger
folks.
They
love
like
you,
know
it's
probably
their
first
open
source
contribution.
They
love
to
put
it
on
twitter
and
that
so
bringing
a
lower.
You
know.
Maybe
congratulations
on
your
first
contribution
to
whatever's
would
would
really
help
them
stay
as
well
and
get
them
really
interested
to
do
more.
A
Oh
yeah
and
those
badges
are
easy
to
do
exactly.
I
can't
remember
the
platform
if
it's
badger.
A
Yeah,
so
the
creating
those
is,
is
it's
pretty
easy
to
do
it's
more
of
just
the
you
know
the
logistic
side,
making
sure
that
that
we
get
it
created
in
a
timely
fashion,
things
just
things
just
get
dropped,
sometimes.
B
Yeah,
but
I
feel
like
yeah,
I
can
get
a
lot
of
people
to
join,
but
to
stay
is
a
different
story,
so
yeah
we
need
to
work
a
little
bit
around
that.
A
All
righty
anything
else.
C
A
Yeah-
and
I
think
that
will
be
is
part
of
the
when
we
get
into
the
the
architecture
around
the
xrpl
that
will
start
creating
some
issues
with
you
know,
like
brad,
was
saying:
go
off
and
spike
a
particular
tool
that
we
need
to
investigate.
A
You
know
those
types
of
things
that
we'll
need
if
the
flush
out
so
folks
could
come
back
and
and
let
us
know
what
they
found
around
those
different
tools.
So
we
can
choose
a
the
right
implementation.
D
A
Well,
the
have
you
used
mermaid
before
in
markdown
sasha.
A
It's
pretty
cool
yeah,
it's.
It
makes
the
doing
diagrams
pretty
easy,
because
you
just
literally
do
certain
patterns
in
your
markdown
in
a
mermaid
block,
and
then
you
get
this
nice
graph
showing
up.
So
if
you
want
to
change
something
on
the
fly
you
just
go
in
and
edit
the
the
markdown
and
then
you
know
you
save
it
and
you
got
it
rendered.
So
it's
it's
really
works
nice
for
that
fashion.
A
Yeah,
so
it
will,
it
will
be
the
they
have
like
a
state
diagram
in
mermaid,
where
it
has
like
the
different
columns
showing
the
arrows
going
between
the
different
kind
of
like
a
transaction
flow
at
that
level.
A
C
A
A
Yeah,
it's
mermaid
js
is,
I
think,
the
plug-in
name
and
then
in
your
markdown
code.
You
do
you
like
your
three
backticks,
then
mermaid
js
and
then
your
block,
and
then
you
put
your
mermaid
code
in
there
and
then
it
will
render
it
for
free.
A
All
right
guys,
I
have
to
drop
for
another
meeting
thanks
everybody
and
I
will
get
that
invite
sent
out
for
next
tuesday.