►
From YouTube: TokenScript Weekly Meeting 20200109
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
A
A
Didn't
participate
but
weekend
the
first
sorry
toka
script,
weekly
meeting
during
Christmas.
Good
news
is
most
we
didn't
make
any
much
progress
and
this
is
a
Christmas
once
we
basically
review
and
consolidate
what
we
already
know
so
you're
not
missing.
Much
have
a
look
at
community
thought,
focus
cook
talk
and
there
is
a
weekly
design,
making
seven
weekly
design
meeting
link
and
if
anyone
found
that
link,
can
you
please
share
the
link
because
I'm
on
my
computer
and
I'm
sticking
to
my
tablet
and
yeah
so
be
great?
B
A
Is
yeah
so
this?
This
is
a
bit
of
a
review
of
what
we
have
discussed
in
the
previous
meetings
and
which
themselves
are
review
of
what
we
have
discussed
in
the
meetings
in
2000
and
I.
Think,
and
so
today's
and
agenda
is
more
about
a
data
object,
continuing
from
the
data
object
being
used
in
attestation
and
extending
the
use
of
object
in
other
parts
of
token
script
and
the
actual
code
is
here
and
opens.
A
Yes,
okay,
oh
cool,
so
let's
open
the
first
one
attestation,
dot
XML.
It
picks
up
from
the
data
object
with
the
we
previously
defined
before
a
test
station
and
examine
how
how
the
the
pitaka
script
uses
it
so
and
I
explained
from
the
beginning
to
the
end
of
the
file.
The
file
is
very
small.
It's
only
39
lines
long.
So
it
starts
with
the
definition
and
contract
stuff
which
contract
is
relevant
to
the
token.
And
then
it
starts
by
defining
object
class,
the
idea
of
it
it
is
ticket.
A
A
A
A
A
If
the
user
is
a
mobile
phone
user,
then
the
user
had
the
test
asian
stored
in
the
before
memory.
Note
that
the
technician
doesn't
have
to
be
owned
by
the
current
user,
for
example,
you
might
have
someone
else's
attestation
in
order
to
do
a
transaction
and,
for
example,
if
you
are
buying
a
kitty
from
someone
and
that
person
is
selling
you
a
certain
price
that
signed
offered
to
sell
the
Qt
is
itself
a
attestation
that
is
not
owned
back
user.
A
So
basically,
and
the
token
script
assumes
you
have
the
test
station
and
the
test
it
doesn't
have
to
be
yours,
and
then
there
is
an
next
line,
is
the
is
the
attribute
type
which
is
no
battle
notice
that
this
actually
type
and
being
defined
here?
It
was
actually
first
used
in
that
hesitation
as
the
first
element
on
line
five.
A
So
when
you
deform,
we
define
a
test
ation,
we
don't
define
the
attribute
types,
for
example
where
it
is
originated,
and
how?
How
does
the
user
see
this
display
the
name
of
the
particular
type?
These
are?
These
are
separate
from
the
test
itself,
so
from
line
19
to
line
26.
These
are
the
definition
of
attribute
type.
A
So
basically,
this
by
saying
attribute
of
the
token
I
mean
this
is
a
attribute.
You
can
access
through
token
bad
app
in
JavaScript.
It's
part
of
a
token
data,
and
then
you
observed
that
there
is
a
token
name
and
the
name.
The
translation
in
this
case
there's
only
one
language
version,
because
no
matter
is
a
symbol
on
line
21
and
then
we
ended
the
definition
of
the
name,
and
then
we
start
with
origins.
A
A
A
A
In
the
line,
seven
data
object
has
is
defined
inside
that
contract
notice
that
previously
object
class
was
defined
outside
contract.
Here
it
is
defined
inside
contract
and
then
it
followed
the
object
class
and
has
the
following
the
how
this
is
a
object
classes.
That
is
the
definition
of
an
object.
So
inside
there's
a
sequence
and
they're,
followed
by
element
element
lots
of
different
elements,
each
with
a
firm
type
and.
A
9:18,
where
a
ENS
name
is
defined
again,
this
is
identifier,
meaning
identifier
has
two
minions
here
and
most
prominently.
Identifier
is
the
count
of
number
of
tokens.
So
if
you
have
a
three
unique
identifiers,
they
have
33
tokens
if
there
are
threatened
if
unique
identifiers.
If
there
are
three
tokens
with
you
with
the
unique
identifiers,
then
you
have
the
same.
You
have
and
there
exist
three
tokens
and
then
the
token
name
is
in
s
name
by
line
20,
that
we
have
the
origins
and,
unlike
other
attributes,
this
actually
type
originates.
A
This
attribute
originates
from
from
an
event
and
you
can
see
in
the
line
25th.
It
refers
to
event
name
registered,
which
is
defined
in
line
7,
so
notice
that
when
you
do,
we
define
line
7.
We
simply
defining
that
object,
the
definition
of
the
how
objectives
of
the
class-
and
we
don't
define
it-
is
a
event
if
you
simply
use
as
event,
so
that
object
is
always
like
a
standalone
and
there
it
can
be
yeah
exist
in
the
form
of
the
event.
A
It
can
exist
in
the
form
Africa
station
or
even
the
day
since
rain
returned
by
a
trusted
source
and
so
continue
from
line
20.
If
and
you
get
this
contract
Lacoste
register
and
the
future
equals
to
owner
equals
to
own
address,
which
means
a
token
script.
Engine
at
this
point
will
scan
through
all
the
events
that
is
named
registered
the
events.
B
A
B
A
So
this
is
about
how
to
source
and
attribute
from
events
and
the
that
could
be
a
and
what
you
say
says
will
be
a
notification
or
events
the
engine
delete
no
token.
So
yes,
this
one.
This
would
not
cover
that.
You
are
right:
yeah,
okay,
yeah,
that
that
still
has
to
be
dealt
with
because
token
script
at
this
point
is
decorative.
A
B
A
We
still
only
implementation
still
need
to
deal
with
it.
So
it's
a
question:
if
not
we'll
put
that
logic
into
a
token
script,
and
it's
you
can
see
that
if
we
don't
declare
such
thing,
if
we
don't
declare
what
happens
if
the
token
changes
ownership
token
script,
engine
probably
is
still
continuing
such
event,
because
this
piece
of
XML
has
provided
it
enough
data
for
the
engine
to
no
such
thing
happened.
A
B
A
A
I
actually
just
finished
so
and
I
have
an
example
of
how
and
that
object
is
used
for
future
and
events
and
how
that
object
is
used
for
making
it
has
stations
and
how
that
object
is
used
for
getting
return.
Value
from
smart
contracts
function
course
so
yeah.
This
is
just
something
that
time
this
is.
This
is
a
playground
asking
for
comment.
A
B
Go
over
explicitly
what
sequence
represents,
what
how
does
that
make?
How
does
that
affect
the
engine
declaring.
A
B
A
B
A
Probably
not
consequence
but
code
and
like
Union
Union
in
knowledge
and
in
in
attestation
and
there's
a
similar
convention.
For
example,
in
certificates,
looks
like
an
x.509
or
any
ASM
dot.
One
encoded
data
and
D
are
encoded,
I
mean,
and
usually
this
kind
of
stuff
I
put
in
the
sequence
as
well.
So
I
simply
replicate
this.
This
is
this
structure,
because
I
notice
similarity
how
ABI
handles
data
and
how
he
has
endured
one
handles
data
and
they
both
use.
Something
like
that.
A
C
A
A
C
C
A
Yeah
you
mean
that
the
the
the
creation,
the
name
token,
can
be
done
through
one
of
the
two
events.
Yes,
two
or
more
yeah
yeah.
That's
that's
an
interesting
thing.
If
we
do
this,
can
we
have
multiple
events
and
origins
and
because
original
initially
supposed
to
provide,
let's
say
another
attribute
type,
it
has
actually
good
whose
value
can
can
originate
from
from
a
theorem.
Smart
contract
function
call
or
from
event.
But
if
you
say
true
is
the
relationship
or.
C
C
C
Is
if
for
for
the
owner
wallet
for
the
owners
interim
address,
if
it
receives
the
detects
to
naming
register
events,
if
you
have
two
ENS
names,
this
this
part
feels
to
be
considered
again
using
the
events
in
origins
to
represent
the
layout
of
the
attribute
based
on
object.
Class
tag
sounds
good,
but
when
we
use
the
detection
of
the
event
to
represent
instances
of
the
ENS
name
within
the
users
in
Theorem
addressed
this,
this
second
part
sounds,
and
it
feels
a
bit
strange.
C
A
A
C
A
A
A
A
Now,
I'm
not
even
sure,
if
I'm
answering
the
question
but
I'm
thinking,
thinking
thinking,
maybe
where
I
think
I've
seen
same
problem
right,
yes,
kind
of
yeah,
good,
scream,
horn,
yes,
and
some
it's
certainly
not
for
a
few
reasons,
not
only
this.
So
traditionally
you
should
be
able,
if
you
think
about
traditional
Directory
objects,
for
example,
which
is.
A
Quite
heavily
used
in
X
for
a
quite
heavily
used
in
a
station
as
well.
Ad
Archer
object
is
identified
by
a
attribute
key
value
pair
or
by
multiple
of
them,
so
you
can
identify
a
directory
object
by
name
name
equal
to
something
plus
eight
equals
to
something.
For
example,
you
can
uniquely
identify
a
object
through
attribute
types
and
in
the
current
schema
it
seems
not
not
able
to
do
so.
So
one
idea
is
to
simply
remove
the
identifier
equals
to
true,
which
is
on
line.
B
A
C
A
And
then
so,
if
you
open
event
dot
XML
and
the
test
issue
dot
XML
side-by-side,
then
you
will
notice
in
event
of
XML,
like
nine,
nine,
nine
10,
11
and
12
in
this
lines
that
object
elements,
the
element,
types,
I,
didn't
I'm.
Sorry
theorem,
a
film
string
different
by
32
theorem
address
and
in
the
test
session
case,
look
at
the
test
agent
of
XML
line.
Five
and
six.
A
Like
a
cross
like
hey,
that
object
is
used
as
the
event
or
as
a
bi
or
as
attestation
or
as
Jason
strain
returned
by
the
server.
Then
the
type
will
change,
and
so
you
imagine
you
have
an
object
that
can
be
used
in
all
three
scenarios.
Then
you
might
have
something
like
line
6f
attestation,
but
XML
where
you
have
two
types
or
maybe
three
or
four
of
them,
to
show
how
each
item
n
should
be
encoded
and
in
different
context.
We
used
as
different
thing.
A
A
A
All
you
can
get
so
you
can
say
sorry
or
you
can
say
that
a
ticket
is
a
ticket,
no
matter
if
you
obtained
it
through
a
gas
station
by
buying
with
a
credit
card
or
you
and
purchase
it
through
ether
and
obtained
it
for
event
and
it's
the
same
ticket
with
the
same
that
object
same
structure.
If
a
ticket
have
an
additional
value,
let's
say
you
have
normal
ticket
gift
ticket
VIP
ticket.
Then
you
have
the
VIP
ticket
very,
very
important
person
ticket.
A
C
A
So
so
so
you
say
that:
can
we
can
we
simply
define
one
type
and
I
internally
transferred
internally
change
them
so
that
the
user
don't
have
to
be
confused
with
different
types?
Yes,
that
probably
will
do.
We
need
to
think
about
how
to
do
that,
though,
for
example,
a
theorem
address
is
more
specific
than
a
s,
an
octet
string,
which
is
good,
because
then
we
can
use
the
theorem
address
and
we
know
it
must
be
encoded
in
optics
string.
C
We
can
invent
something
yeah,
okay,
but
but
this
these
tights
might
be
easier.
Why
might
be
difficult
might
be
things
like
integer
of
floating
numbers,
floating
point
numbers
because
of
precision?
Oh.
A
A
A
A
A
Example,
the
hope
is
not
necessary,
but
the
bad
programmers
are
everywhere,
so
they
probably
define
object,
class
and
later
used
in
some
code
and
then
define
new
one,
which
is
very
similar.
Just
look
at
how
many
different
versions
of
a
free
particle
contract
that
we
have
deployed
deployed
on
theorem,
even.