►
From YouTube: May 26, 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
All
right,
utkarsh,
everybody
welcome
to
the
may
26th
architecture,
meeting
for
artelias
we're
just
gonna,
be
going
over
what
we've
been
doing
for
the
xrpl
grant
and
kind
of
do.
A
quick
walkthrough
of
what
we've
kind
of
come
up
with
is
a
plan
of
attack
for
persisting
the
json
information
about
application
versions,
component
versions
into
the
blockchain
as
nfts.
A
Looks
like
utkarsh
who's
been
driving.
The
coding
is
getting
reconnected
here.
So
we'll
wait
for
him
to
who
kirsh?
Can
you
hear
us
hello,
yeah,
sorry.
A
So
it's
we're
gonna
take
off.
If
you
don't
mind,
we'd
like
to
just
do
a
quick
walk
through
of
what
you've
come
up
with
from
the
blockchain
perspective,
with
pulling
together
the
nfts
and
the
blockchain
transactions.
B
Okay,
so
let's
start
with
code
itself
and
before
code,
let's
run
this
code
once
and
see
like
go,
let's
go
through
the
logs
once
and
that
will
give
us
more
idea
about
like
what
is
the
code
and
what
the
code
is
doing.
B
Yes
correct,
so
we
would
like
I
spent
some
time
between,
like
two
libraries
like
python
libraries
and
node.js
libraries,
but
at
the
latest
step
we
found
that
like
a
lot
of
application,
examples
that
are
already
there
on
web-
and
that
could
you
know,
be
useful
to
us.
So
that
is
where
we
decided
to
go
with
node.js.
B
Correct
correct:
we
can
invest
that
time
to
create
something
new
right.
B
Okay,
so
let's
start
with
the:
what
are
the
packages
like
architecture
of
the
project?
So
basically,
as
you
can
see,
there
are
two
main
folders
here
present.
So
there
is
one
folder
called
nft
and
there
is
another
folder
that
is
s
bomb
leisure.
B
A
A
quick
question
on
the
the
ipf
storage,
which
one
are
we
using
at
this
point?
Is
it
nft.storage
as
the
storage,
okay,.
B
Okay,
so
the
second
one
which
is,
which
is
swam
leisure.
So
it
has
all
the
methods
that
we
need
to
interact
with
leisure
like
creating
a
transaction
uploading,
some
metadata,
and
there
are
a
couple
of
more
methods
that
we
need.
While
we
go.
B
So
we
have
only
included
methods
that
we
are
using,
that
we
are
like
that
that
were
relevant
from
the
user
historic
point
of
view,
so
there
could
be
multiple
methods
that
are
that
might
be
related
for
other
products,
but
what
we
needed
we
we
needed
like
creating
a
connection
to
a
ledger,
making
a
transaction
uploading
some
metadata
to
a
wallet.
So
therefore,
we
have
only
included
those
methods
here.
B
Apart
from
that
here,
we
are
instantiating
the
x
api
for
ripple
api,
basically,
so
that
we
could,
we
could
leverage
ripple
apis
in
our
application,
just
a
method
to
handle
our
error
messages
and
from
here
our
main
method
starts.
So
I'll
escape
few
like
few
things
that
we
have
done
just
to
beautify
the
logs
or
something
so
here,
I'm
using
piglet
for
artelia's
that
is
not
relevant
to
this
demo.
B
We
are
creating
one
wrapper,
which
is
a
build
setting
that
will
have
all
those
all
this
information,
like
all
the
meta
information,
and
since
this
was
a
poc,
so
I
was
also
writing
all
those
information
to
an
output
file.
So
the
path
to
this
input,
file
and
output
file,
and
just
to
mention
what
we
have
done
so-
and
this
is
this-
is
the
json
that
that
that
has
been
generated
by
ortelius.
So
this
is
this
has
been.
B
B
Here
we
are
doing
some
of
the
validations
before
writing
to
the
file
since
when
when
we
will
use
this
poc
to
the
actual
implementation,
a
lot
of
the
code
will
will
get
removed
because
the
source
and
sync
will
be
different.
Like
from
where
we
read
read.
Some
data
would
be
an
api
endpoint
or
some
other
feed
endpoints.
B
We
are
generating
hashes
for
the
file
and
again
we
are
leveraging
a
method
that
is
written
in
our
ledger,
so
this
will
generate
a
hash
for
the
hash
for
the
the
file
that
we
have
in
the
input.
Folder.
A
And
is
that
is
that
hash
prior
to
ipfs,
or
is
that
a
ipfs
hash
itself.
B
B
Okay,
here
is
ipfs
right,
yes,
correct
ipfs
is
afterwards
so
here
we
are
fetching
some
of
the
information
that
we'll
need
like
what
is
our
wallet
address,
so
this
will
give
us
like
what
is
what
is
the
address
that
we
want
to
make
transaction
to
and
again
we
are
storing
everything,
everything
every
information
in
a
in
a
wrapper
class
that
is
build
settings
so
so
that
everything
is
present
in
a
object
in
a
consolidated
way,
and
I'm
also
writing
that
object
in
a
file
so
that
I
can,
since
that
was
a
pc.
So
I
can.
B
B
A
So
a
quick
question
on
that:
the
shouldn't
the
hash
be
calculated,
but
right
before
you
do
the
upload
since
you've
added
data
to.
B
B
And
after
that,
I'm
just
doing
some
logs
and
okay.
This
is
this
is
something
important,
so
I
don't
know
like.
I
looked
at
few
of
the
examples,
so
there
they're
they
were
creating
some.
So
let's
look
at
this
method.
Upload
xrpl
wallet
data,
so
why
this
is
important,
because
this
is
what
is
creating
a
transaction.
B
So
if
you
see
like
what
is
the
method
signature
for
this
api,
it
takes
a
wallet
data
which
is
of
any
type
and
wallet
address
and
x,
api,
the
api
connection
or
xrp.
So
it's
a
good
practice
that
we
store
our
metadata.
So
so,
whenever
we
see
one
transaction,
we
could
see
some
metadata
that
is
associated
with
that.
B
So
this
is
because,
because
of
that
methods,
because
we
are
wrapping
all
this
information
in
that
object,
and
that
is
why
we
are
able
to
see
a
lot
more
metadata
information
because,
as
we
know,
all
like,
our
actual
data
resides
in
nft
right.
But
what
goes
in
the
transaction
in
the
leisure
is
some
metadata
and
which
is
there
so
all
right,
yeah.
So
that
is
there
and
we
can
see
like
the
transaction
was
successful
or
not.
You
can
see
every
data
here,
but
let
me
go
back.
B
B
Yeah,
so
that
is
all
the
code
walkthrough.
C
A
And
can
you
can
you
see
the,
can
you
browse
the
ipfs
with
the
cid
and
and
see
the
data
from
that
side
or
yes,
we
can
do
that.
A
And
how
long
does
it
take
to
do
a
transaction?
Is
it
pretty
fast
or
is
it
like.
B
Several,
no,
no,
it's
pretty
fast!
So
so,
as
you
saw
now
like
when
I
triggered
this
index.js,
so
it
was
executing
all
these
steps
in
the
sequential
manner.
So
it
was
like
less
than
one
minute
perfect.
It's
like
a
couple
seconds.
Yeah.
B
B
B
A
C
Yeah,
so
you
have
you
guys,
considered
stephen,
I'm
sort
of
withholding
some
number
of
comments
and
questions,
because
I
don't
you
know,
necessarily
have
a
certain
level
of
background.
That
makes
me
confident,
but
but
I
am
curious,
so
it
looks
like
so.
This
object
that
we're
storing
on
ips
is
is
the
is
the
s
bomb
right
again.
A
Yeah
in
this,
in
this
poc
example,
we
needed
just
a
a
json
file
to
store
over
an
ipfs,
and
the
s-bomb
is
one
of
the
json
files
that
we
can
utilize.
So
in
ortilius
we
actually
have
a
json
representation
of
application
version
and
we
have
a
json
representation
of
a
component
version
and
those
will
be.
Those
also
have
like
the
component
will
have
a
relationship
to
an
bomb
as
well.
So
we
have
these
nested
json
files
and
that's
one
of
the
things
we
have
to
look
at
from
a
an
architecture.
A
C
A
We
we
did
look
at
that,
but
I
think
you
know
when
we're
looking
at
a
couple
hundred
k
of
of
data
yeah
yeah,
you
know
the
we
could
do
it
it.
You
know.
Blockchain
will
support
it,
but
it's
not
like
a
best
practice
to
load
up.
C
Yeah-
and
one
of
the
reasons
I
ask
is
it
would
be
great
to
have
a
well
not
great.
It
would
be
nice
to
have
a
a
a
standards-based
rend,
renderable
representation
of
of
what's
stored
on
ipfs,
because,
of
course,
when
you're
issuing
say
an
nft
around
an
image
right,
you
can
use
pinata,
also
various
marketplaces
to
render
that.
C
So,
where
I
was
kind
of
going
is,
is
is,
is
you
know,
can
we
store
the
ortilius
specific
s
bomb
and
data
elsewhere
so
that
it's
only
read
through
sort
of
an
ortillious
reader?
But
then
is
there
a
way
to
allow
anybody
to
kind
of
get
it
get
it
get
it
get
it
get
a
standards
based
representation
of
nft?
If
that
makes
sense,.
A
As
what
we're
going
to
put
into
ipfs-
and
that
is
where
we
just
need
to
make
sure
that
the
that
there's
a
way
to
render
json
from
ipfs,
we
may
have
to
create
our
own
browser,
like
you
said,
of
the
of
a
json
renderer
for
for
the
nft.
But
one
of
the
problems
that
we
have
with
ipfs
is
and
putting
everything
over
there
is
that
it's
not
searchable.
A
So
one
of
the
things
that
we'll
need
to
do
is
to
do
a
secondary
process,
and
this
is
kind
of
where
the
grant
comes
into
play
being
able
to
build
out
a
way
to
search
the
json
data
over
an
ipfs
right.
Okay,
and
that's
why
I
keep
on
asking
you
about
the
like
a
implementation
or
another
one.
B
A
C
Right,
okay,
that
helps
me
understand
better
what
we
were
talking
about
earlier
in
the
week.
I
don't
know
offhand
either,
but
of
course,
in
the
course
of
this
engagement
you
know
I
I
can.
I
can
work
to
figure
that
out.
Actually
you
know
one
one
of
our
our
our
data
team,
guys
I'll
be
meeting
with
tomorrow
morning
and
I'll.
Ask
him
about
this
see
if
he
has
any
points.
A
Yeah,
so
what
we
really
need,
and
the
reason
why
we
we
chose
ipfs
for
the
this
poc
was
it
ipfs,
gives
you
an
immutable
file.
Basically,
and
that's
one
of
the
the
things
that
we
want
to
be
able
to
do
with
the
the
blockchain
and
the
nft
is
create
an
immutable
ledger.
A
Now
we
could
skip
the
ipfs,
ipfs
and
just
load,
it
load
the
stuff
into
a
database,
but
we
lose
the
immutability
of
it
at
that
point,
and
I
think
the
immutability
is
more
important
than
the
database.
A
A
company
I
saw
that
has
done
that
before
so
I've
seen
their
their
model
around
that
being
able
to
do
a
secondary
index
on
ipfs.
C
Side
was
the
name
of
that
company.
My,
for
instance,
I
see
lens
just
on
a
gross
google
ipfs
search
engine
with
lensed.
A
And
there's
there's
things
like,
I
think
we
can
point
elastic,
search
at
it
as
as
a
possibility,
but
elasticsearch
kind
of
runs
into
a
few
issues
with
licensing
on
that
level.
So
they're
not
quite
quite
100,
open,
there's
a
certain
input
interpretations
of
like
the
elastic
storage.
A
Okay,
oh
here
it
is,
let
me
drop
it
in
there.
I
think
this
is
the
one.
If
I
remember
correctly,
it's
called
the
graph.
C
And
then
steve,
it
sounds
like
until,
unless
you
find
out
performance
becomes
an
issue.
This
is
probably
the
preferred
sort
of
decentralized
solution
to
making
the
the
json
content
searchable
right.
So
I'm
assuming
that
theoretically,
oh
did
I
lose
everybody.
Oh
we
lost
steve
the
hotel
room
wi-fi.
C
There
was
something
else
so
ooh
carter's.
By
the
way,
I'm
looking
it's
funny.
I
tweeted
it.
This
afternoon
we
have
our
devrel
team
is,
is
holding
a
a
series
of
talks
around
nfts
and
other
contents.
I
don't
know
garcia.
Have
you
been
participating
in
the
discord
channel.
B
C
Yes,
there's
an
xrpl
discord
channel.
If
you
go
to
xrpl.org,
you
can
access
it
from
there
and
and
I'm
gonna
I'll,
pull
specific
details
and
look
to
send
them
to
you
before
we
wrap.
But
there
they've
posted
the
agenda
and
timing
for
for
a
series
of
presentations
around
xrpl
development
and
then
specifically,
xls20
or
nft,
and
the
sad
thing.
B
C
A
C
A
Want
our
internet
connection
out
of
the
hotel,
but
I
was
seeing
brian
on
the
the
graph
link
that
I
sent
you
their
model
is
something
that
we
could
implement
and
like
load
things
based
on
that
model,
doing
the
indexing
into
a
a
or
an
orango
db,
a
docustore
that
we
can
then
search
at
that
level.
So
it's
it's
not.
A
I
don't
think
we're
too
far
off
on
that
front.
Just
was
out
of
scope
for.
C
Yeah
now
makes
sense
that
makes
that
makes
sense,
and
then
I
was
just
explaining
why
you
were
gone
steve,
for
I
am
in
the
chat
here.
If
I
can
find
it,
I'm
going
to
give
you
the
link
to.
Unfortunately
it's
a
tweet
from
one
of
the
ledger
developers
yolk,
but
in
that
tweet
you'll,
see
the
link
to
the
discord
channel
and
the
information
about
the
session
that
they
are
running
at
12
p.m.
Pacific,
today.
A
C
And,
of
course,
and
for
steve,
they,
I
think,
based
on
what
I
understand
of
the
content,
I
was
kind
of
involved
with
initial
planning
of
the
content.
There
was
likely
useful
information
there
for,
for
both
of
you.
A
Well,
yeah,
I'm
going
to
be
doing
my
presentation
at
that
time,
so
hopefully
they
record
it
and
I
can
watch
it
later.
C
All
right,
hopefully,
I
didn't
slow
down
your
guys
review
too
much,
I'm
going
to
jump
over
to
a
another
meeting.
You
know
both
from
the
artillia
side
and
the
ripple
side.
You
know
the
two
hats
I'm
wearing
this
is
I'm
excited
to
see.
I'm
excited
to
see
where
this
goes.
Thanks,
yeah
awesome,
job
lukas.
B
Thanks,
actually,
what
we
saw
is
like
a
smaller
section
of
what
we
learned.
So
during
the
time
of
learning,
we
explored
a
lot
of
other
terms
and
methods
as
well,
so
yeah
yeah.
A
Yeah,
it's
a
it's
a
huge
landscape
to
learn
around
blockchain.
A
And
I
think
you,
you
nailed
in
exactly
what
we
needed
to
focus
on
for
what
we're
going
to
be
doing
with
ortillius
and
the
nfts
and
the
blockchain.
So
nice
job.
A
And
would
one
of
you
guys
be
able
to
jump
on
that
xrpl
meeting
or
not
that's
happening.
B
I
need
to
have,
I
need
to
have
a
twitter
account.
I
don't
have
a
twitter
account.
A
All
right,
everybody,
I
think
that's-
should
do
it
for
day
awesome
job
and
who
cares?
Were
you
able
to
figure
out
why
you
weren't
able
to
see
the
ipfs
the
object
in
ipfs,
or
is
it
just
not
a
renderer
over
there.
B
No,
no
actually,
actually
the
path
was
wrong
that
actually,
I
was
passing
the
whole
object.
Basically,
that
should
contain
only
the
path
for
the
file,
so
that
was
the
error.
Okay,
cool.
A
All
right,
because
that
was
one
of
brian's
question-
was,
if
you
could
see
the
through
a
browsing
mechanism,
if
you
could
see
the
json
without
writing
a
special
browser.
A
Yeah
yeah
and
if
you
could
just
do
a
quick,
screenshot
and
drop
it
in
the
discord,
okay,
yeah
job,
I
love
it.
Nice
going
all
right,
guys,
okay,
cool!
Thank
you.
Everybody.