►
Description
Timecodes:
00:00 - Praise time!
15:50 - Agenda
18:33 - Stewards
22:35 - Legal
23:30 - Gravity
25:17 - Hatcher outreach
27:23 - Soft Gov
30:28 - Transparency
32:41 - 0mega
33:50 - Labs
35:13 - Comms
36:24 - Params
37:07 - Common Swarm
40:17 - An introduction to SPICE and TokenSPICE
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/uM4ZWDjNfK
or say hello on Telegram https://t.me/tecommons
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: https://twitter.com/tecmns
Learn more http://tecommons.org/
A
Santi
for
reaching
out
during
the
week
after
laser
escarim
mitch
and
katie
for
their
contributions,
good
to
comes
adria
for
a
look
at
his
guidance
in
the
common
swarm,
juanka
griff
inception
for
a
front
prey
session,
invite
by
viv
and
octopus
for
being
the
closest
to
superheroes
in
the
tc.
I
passed
it
to
nagin.
B
Yeah
hi,
I
wanna,
I
wanna
praise
mitch
for
the
amazing
work
on
this
deck
and
also
the
rest
of
the
team
lauren
griff,
marco
vitor
inceptivist,
with
with
the
forum
posts.
I
want
to
praise
sam
for
reviewing
my
pull
request
and
I
want
to
praise
octopus
for
the
craziness
video
he
uploaded
to
youtube
and
yeah.
I
want
to
please
myself
for
the
forum
posts
I
wrote
and
for
in
other
pull
requests
for
the
easy
convert
and
I'll
pass
it
to
sam.
C
I
would
like
to
praise
fable,
rodrigo
fabi,
fiore,
paul,
paulo
ana
pereira.
Pacha
will
grieve
luke
and
myself
for
the
gardens,
which
is
the
corner
store
at
the
cornerstone
of
the
common
tahoe
that
we
are
designing
and
I
will
also
price
mitch
for
grief,
loren
and
the
rest
of
the
params
working
group
for
the
specification
of
the
of
the
common
password.
C
D
C
Okay,
I
also
would
like
to
praise
myself
for
the
giving
all
the
help
all
the
help
I
can
with
the
mathematical
formulas,
because
I
I
really
love
it
and
I
try
to
add
them
solve
anything
with
with
math
with
maths,
for
example,
the
impact
our
formulas
or
I
like
to
put
maths
everywhere.
F
F
I
would
like
to
praise
gabby
fabry,
rodria
and
everyone
else
on
the
gardens
team
for
doing
an
amazing
work
on
the
onboarding
on
the
garden
supporting
project
and
of
course
I
will
have
to
praise
pablo
and
sam
for
an
amazing
week
here
on
the
gibbot
house,
hacking
and
an
extra
praise
to
sam
for
helping
me
and
on
designing
and
specifying
the
requirement
for
an
amazing
library
that
we're
building
and
yeah
I'll
pass
it
to
ygg.
G
Hey
everyone.
I
went
I'll
pass
it
over
to
tamara.
G
Tim
went
too
how
about
david.
H
Hey
good
morning,
everybody
at
least
it's
morning
here
in
bc,
I'd
like
to
praise
myself
for
diving
on
into
this
community
heads
first
and
just
seeing
what
comes
of
it
and
also
praise
myself
for
picking
up
so
much
tech
education
in
the
last
two
months.
It's
it
seems
like
every
day,
there's
a
new
app
to
learn
how
to
use
and
then,
as
soon
as
I
learn
how
to
use
it,
productivity
exponentially
grows
in
a
great
way.
Also
praise
myself
for
making
any
progress
in
this
messy
room.
H
Excuse
that
no
virtual
backgrounds
on
this
thing
yeah.
I
want
to
praise
suga
for
inviting
me
here.
It
was
her
warm
and
friendly
invitation
that
made
me
feel
able
to
to
knock
on
the
door
and
join
the
community
a
few
months
ago,
and
I
want
to
praise
chewie
for
being
so
patient
with
my
question
after
question
about
where
to
go,
what
to
do
and
how
to
contribute.
H
Thank
you
and
I
want
to
praise
griff
for
his
seemingly
infinite
energy
and
optimism.
Seeing
you
bouncing
around
and
smiling
in
these
meetings
makes
me
feel
optimistic
too,
and
that's
it
I'll
pass
it
to
vvv.
Is
that
pronounced.
H
H
Oh
yeah,
I
want
to
praise
ygg
anderson
too,
because
I
see
his
name
pop
up
or
sorry,
their
name
pop
up
in
the
most
random
of
places
on
the
internet,
communities
and
I'm
like
hey.
I
know
that
person
future
thinkers
community,
especially
thanks.
J
Thanks
wow,
yes,
so
david,
I'm
stugga
so,
and
I'm
also
katie.
Thank
you
for
that.
So
praise
to
david
for
his
praise.
J
So
I'm
going
to
praise
myself
for
being
a
single
mom
and
managing
a
headache
since
I've
had
since
monday
and
two
little
kids
in
the
bath
while
we're
having
this
call
and
daily
life
is
like
that.
Last
night
there
was
like
squirting
baby
tomatoes
all
around
the
dinner
table.
J
While
I
was
trying
to
do
some
work
with
ygg
I'd
like
to
praise
myself
for
orientation
stuff
and
I'd
like
to
phrase
myself
a
third
time
for
the
blog
so
and
on
that
note
I
would
like
to
praise
the
folks
who
have
really
helped
me
a
lot
this
week
on
that
so
heater
and
actually
heater
peter.
That's
that's
the
blog
you're
hoping
with
not
the
weekly
update.
J
So
let
me
just
get
that
in
and
of
course,
octopus
magali
ygg
super
grateful
help
mitch
and
then
just
extra
contributions
from
craig
and
marco
and
last
praise
for
jess
and
jeff,
just
also
for
the
blog
and
jeff
just
for
one-on-one
fabulous
insight.
And
let
me
look
now
with
my
giant
headache.
Oh,
I
want
to
praise
trent
sorry,
because
I
want
to
try
praise
I've.
Never
I
want
to
praise
somebody.
I've
never
praised
before
and
also
a
token
engineer,
so
I'm
going
to
send
it
back
to
griff
because
I
don't
know
who's
left.
K
No
thank
you
griff.
I
wanna
praise
myself
for
diving
into
tokyo
engineering.
I
had
zero
knowledge
about
it
before
getting
into
this
project.
So
for
me
it
has
been
a
journey,
and
I
thank
everyone
for
that.
I
wanna
displace
myself
for
and
ham
for,
the
impact
hours
campaign
where
we
reach
everyone
up
to
four
impact
hours.
K
I
wanna
displays
to
levy,
for
I
don't
know
how
she
did.
She
managed
to
her
time
into
creating
all
these
things
and
make
it
up
and
be
always
so
kind
to
everyone
that
joins
our
calls
and
so
on.
I
want
to
dish
praise
to
ygg
for
his
immense
knowledge
that
he's
willingly
helping
and
contributing
to
the
community.
I
want
this
place
to
to
angela.
L
L
So
I
think
yeah,
that's
something
I
praise
myself,
because
sometimes
we
we
all
work
all
the
time
and
we
forget
to
do
other
things
and
life
is
so
wonderful
that
each
experience
has
to
be
lived
profoundly,
and
I
would
praise
myself
also
for
being
here
with
you
guys,
because
years
ago
this
was
like
a
dream.
L
I
wanted
to
work
in
in
in
in
dallas
and
doing
what
I'm
doing
now
and
like
standing
for
my
belief
and
living
with
my
worry,
but
I
I
am
going
to
take
some
more
seconds
to
praise
other
people
and
I
am
going
to
praise
jess
and
jeff
for
leading
and
opening
the
impact.
Our
discussion
analysis
grief
for
this
idea
of
praising
ourselves.
L
Same
for
for
proposing
and
grievances
for
proposing
the
for
the
impact
hour,
analysis,
durga,
das
and
dan
for
helping
me
these
two
weeks
with
gravity,
sep
and
chewy
for
praise
quanting
leavey
for
leading
the
soft
gob
working
group
and
all
the
initiatives
that
are
in
there,
santi
tam
for
being
great
stewards,
ygg
and
octopus,
and
and
angela
for
jumping
into
the
phrase,
analysis
and
bye,
bye
b
for
the
discord,
wizardry
and
ib
for
typing.
All
these
praise
and
I
will
pass
to
who
hasn't
gone
acid.
Laser
definitely.
D
M
N
Hey
everyone
it's
my
first
time
here,
so
this
won't
be
too
crazy.
Long,
I'll
praise.
Whoever
came
up
with
this
idea.
Wonderful
and
great
vibes,
I'll
praise,
angela
and
peter
for
roping
me
into
this
tea
services
project
and
that's
been
a
lot
of
fun
and
I'll
praise
myself
for
coming
around
more
than
I
have
the
last
few
months,
so
yeah,
good
fun
and
I'll
pass
to
chris.
I
think.
N
Awesome,
I
will
praise
I'd
like
to
praise
rdfbx
and
5iv
for
doing
all
the
work,
sorting
out
praise
the
praise,
bot
and
missed
praise,
and
that
kind
of
thing.
So
thank
you.
Praise
to
those
two
for
all
their
work.
Sorting
that
stuff
out
I'll
pass
back
to
griff.
O
Okay,
I'll
do
the
self
praise
two
self
phrases,
case
studies
and
my
progress
in
learning
salinity,
and
then
I
will
do
my
praise
in
the
community
ivy
for
twitter
and
the
praise,
aggregation
mitch
and
lauren
for
all
the
forum
posts
that
you're
doing
chewing
on
the
unbelievably
unbelievable
amount
of
comms
initiatives
that
are
going
on
within
this
community
eduardo
and
zepty
for
the
hatchery
guidebook
work
that
you're
doing
tam
for
all
the
guidance
and
advice
you
provide
us
olivia
for
all
the
perspectives
on
governance
and
informing
ways
for
the
intervention,
proposals,
octopus
and
ygg
for
the
praise
and
impact
hour,
analysis
ygg
for
te
labs
and
the
te
services
groups
great
for
just
pulling
this
all
together
into
a
cohesive
mission,
canadian
for
the
blog
and
external
comps
that
you
do
on
a
daily
basis,
which
is
really
awesome.
O
Five
iv
for
all
the
platform
work
that
you
do,
keeping
us
on
track
and
everything
accountable,
and
I
also
wanted
to
add
that
david
praise
you
for
being
new.
We
were
all
on
your
shoes
at
one
point,
so
congratulations
and
welcome
to
the
community
and
I
will
pass
it
to
the
next
person.
P
Let's
see
all
right,
I
guess
this
is.
Why
can
you
hear
me
yeah,
we'll
hear
you
yeah
cool
yeah?
This
is,
I
guess,.
F
P
First
call
on
this,
though,
praise
to
the
people
who
set
this
up.
It
is
a
really
good
vibe,
like
someone
else
pointed
out
and
raised
to
the
invite
to
come
to
this
and
talk
a
little
bit
about
token
spice
and
share
with
you
guys.
You
know
some
of
the
learnings
that
I've
had
there
praise
to
the
people
who
praised
me
for
for
being
here.
Thank
you
and
yeah.
I
mean
overall
praise
to
just
you
know.
P
I
know
so
many
of
you
have
put
in
a
lot
of
hard
work
to
really
get
token
engineering
commons
off
the
ground
and
took
an
engineering
too.
Obviously
so
this
is
I.
I
fear
that
if
I
start
listing
names,
it's
I'm
going
to
miss
many
people,
but
I
know
that
griff
and
jeff,
and
and
angela
and
others
have
done
so
much
work
so
so
praise
at
least
you
three
and
many
more
I'm
sure
so
yeah.
I
apologize
that
I
can't
be
at
more
of
these
meetings.
Q
R
In
the
game
with
house
going
to
barcelona
and
learning
a
lot
and
I'd
like
to
get
praised
this
prize
to
sam
for
all
his
work
in
in
the
params
and
and
in
the
modeling
thing,
and
to
paulo
for
scripture,
a
library
which
we'll
use
and
also
I'd
like
to
displace
to
to
gabi
and
poppy
for
doing
my
pull,
requests
on
the
garden
boarding
and
that's
pretty
much
it
I'll
pass
it
to
griff.
D
Thank
you
so
much
pablo
a
man.
D
D
F
F
I
Okay:
okay:
here
we
go
so
we're
really
tight
on
time
and
we
have
so
much
to
go
over,
but
there's
also
all
the
working
group
updates
that
are
gonna
be
great,
so
I'll
pass
it
straight
to
community
stewards
and
tam
to
kick
us
off.
T
T
We
had
a
conversation
in
our
retrospective
around
sharing,
thanks
for
adding
that
grandpa's
excellent.
We
just
had
a
conversation
in
our
retrospective
around
his
decision
space
and
what
to
make
decisions
on
and
how
to
make
decisions
and
balancing
advice
process
with
community
decisions.
So
I
know
that
griff
added
this
here
very
quickly
and
we'll
start
talking
about
it
more
in
our
in
each
of
our
weekly
calls.
T
Okay,
so,
let's
get
down
to
business
at
the
end
of
spring
12,
believe
it
or
not.
We
have
12
sprints
together.
I
think
that
my
my
screen
is
sharing
well,
and
this
is
what
our
sprint
our
retrospective
board,
looks
like
at
the
end
of
every
sprint.
We
take
some
time
to
be
introspective
and
ask
ourselves
what
did
we
do
really?
T
T
So
you
are
welcome
to
jump
into
the
board
and
see
the
inner
workings
of
our
minds,
but
what
we
decided
to
do
as
an
action
to
improve
is
to
to
go
deeper
than
we
have
on
this
patch
readiness
checklist,
but
to
really
identify
every
single
critical
to
hatch
task
and
make
sure
that
there's
a
github
issue
for
each
of
each
one
of
those.
T
So
we
could
easily
see
it
on
the
zen
hub
report
as
well,
and
what
we
decided
to
do
is
add
these
issues
which
we
will
do
on
here
on
the
zenho
board
and
our
sprint
planning
happens
tomorrow
at
6
p.m.
Everyone
is
welcome
to
join
or
watch
it
on
youtube
if
you're
curious
about
how
we
plan
our
our
two-week
sprints.
And
what
else
do
I
want
to
say
about
that?
Yes,
there's
still
time
for
us
to
update
and
close
issues
before
our
sprint
planning
tomorrow.
T
So
the
hatch,
readiness
checklist
each
of
the
working
groups
are
slowly
signing
off
to
to
say,
hey
if
we
needed
to
hatch
tomorrow,
we'd
be
ready
to
hatch.
Tomorrow
we
are
pretty
close
now,
so
there's
going
to
be
more
discussion
from
olivia
and
softgov
on
where
we
need
to
make
decisions
in
order
on
the
impact
hour
and
data
analysis
in
order
to
be
ready
for
the
hatch
from
the
soft
and
cultural
bills
perspective.
T
We
have
this
list.
In
our
last
blog
post,
the
working
group
stewards
have
come
together
and
said:
these
are
the
kinds
of
skill
sets
we're
looking
for.
So
if
you
match
one
of
these
skill
sets
or
interested
in
participating,
please
do
come,
find
either
suga,
who
is
the
orientation
coordinator
or
or
any
of
the
stewards?
T
What
else
do
I
have
yeah?
Oh
some
stats,
so
I
made
a
mistake
last
time
and
I
only
had
15
stewards,
so
I
added
the
missing
steward
that
I
missed
last
time,
but
it's
also
nice
to
to
share
this.
T
Actually
in
this
call,
there
are
15
stewards
now
in
the
tdc
and
there
are
11
working
groups
and
we
have
now
over
400
people
who
have
contributed
and
earned
praise
in
the
tec
alone,
and
the
last
thing
I
want
to
share
is
this,
which
we
started
just
last
week:
it's
the
working
groups,
weekly
update,
it's
on
the
forum.
T
So
if
you
don't
have
time
to
be
really
deep
in
our
community
on
all
of
our
calls
or
on
our
discord,
you
should
probably
get
an
update
by
email
with
all
the
different
things
that
are
going
on
in
each
individual
working
group.
So
that's
very
cool.
All
the
great
stuff
happens
inside
the
working
groups
themselves.
So
without
any
further
ado,
I'm
going
to
pass
to
santiago.
U
Thank
you,
tom
all
right
here,
legal,
we
are
started
working
meeting
bi-weekly,
so
we
didn't
have
a
meeting.
Last
week
we
made
sure
all
the
documents
have
included.
The
final
forms
that
we
voted
together.
We
have
to
go
a
couple
of
smile,
minor
minor
changes
that
we
we
still
checking,
but
all
of
that
all
of
those
documents
are
finished
and
have
integrated
all
the
arms.
U
Besides
that
we've
started
last
last
meeting,
we
started
working
on
the
covenant
and
the
constitution
for
the
daw,
and
hopefully
we
might
be
able
to
jump
into
that
tomorrow
in
our
meeting.
So
we
welcome
you
to
come
and
join
us.
We
meet
on
on
at
4
p.m.
Central
european
time,
you're
welcome
and
I
hope
to
see
you
all
there
and
that
being
said,
I'm
all
finished
and
I'll
pass
it
to
juan
carlos
for
the
next.
Thank
you.
L
Thanks
auntie:
well,
we
have
a
gravity
survey
that
that
is
open
for
everyone
to
to
fill
out,
and
the
idea
of
this
survey
is
to
identify
what
are
the
key
needs
of
of
of
dao's
related
to
conflict
management
and
also
to
see
how
can
we
polish
and
improve
our
our
processes,
because
we
have
a
step-by-step
process.
L
L
So
if
you
need
any
support
from
us,
you
can
fill
this
type
form
and
we'll
contact
you,
and
we
are
professionally
responsible
for
for
trying
to
be
impartial
and
for
trying
to
facilitate
a
dialogue
between
between
between
people
and
we
are
trying
to
design
the
second
graviton
training
that
is
after
july,
and
today
we
have.
Our
working
group
called
that
durgadas
will
lead
and
he
will
give
us
a
decolonization
talk.
K
Thank
you,
honka,
hello,
everyone,
so,
in
hatch
outreach
we
are
basically,
as
you
were
in
this
call.
You
have
received
praise.
Therefore,
you
have
impact
hours
so
for
everyone
to
know,
impact
hours
will
be
lost
forever
if
they
are
not.
If
your
trusted
state
membership
is
not
activated.
So
if
you
need
help,
if
you
don't
know
how
to
do
it,
just
reach
me
out
or
time,
and
we
can
help
you
with
that.
K
Also
and,
as
we
mentioned
before,
everyone
will
than
four
impact
up
with
up
to
four
impact.
Hours
has
been
contacted
individually
and
we
will
launch
this
campaign
to
do
so,
and
it
has
been
proven
quite
successful.
75
of
those
with
up
to
10
impact
towers
already
trusted
member.
Also,
we
have
sort
of
change.
We
have
an
ama
for
hatcher's
that
used
to
be
4
pm.
Today
we
cancel
it,
and
basically
the
idea
of
this
is
we'll
probably
wait
until
the
hatch
to
relaunch
this
space.
K
But
if
any
of
you
have
any
question-
or
you
want
to
just
ask
a
question
or
make
a
suggestion-
just
go
to
hash
irish
channel
here
in
discord
and
we'll
be
there
for
you
also,
we
are
doing
two
main
documents.
One
document,
it's
a
hatch
handbook,
which
is
a
document
design
for
how
the
params,
once
you
get
into
the
hatch,
will
affect
you
and
these
documents
should
be
ready
by
this
spring
or
the
beginning
of
the
next
spring.
And
then
we
have
a
closing
working
document,
because
the
name
of
our
group
is
hajj
outreach.
K
So
once
the
hatch
is
launched,
the
outreach
our
mission
is
done.
So
we
are
preparing
a
document
that
serves
as
a
guideline
for
other
working
groups
to
closure
and
what
kind
of
things
do
we
need
to
have
or
know
or
pass
on
to
other
working
groups?
In
case
we
have
so
that
will
be
pretty
much
all
in
case.
Anyone
here
in
the
school
have
a
project
or
something
that
you
would
like
to
propose
as
a
proposal
for
the
tec
you're.
More
than
welcome
to
send
me
a
message,
so
we
can
walk
you
through.
I
Thanks
ado
yeah
in
softgov,
we
had
a
very
exciting
week
to
show
all
the
praise
analysis
results
that
came
from
ygg
and
octopus
and
muhammad
and
angela
and
all
of
the
labs
crews
that
did
so
much
work
and
everyone
that
helped
clustering.
The
praise
and
categorizing
the
praise
and
helping
us
to
arrive
to
the
point
we
are
now
that
we
can
start
making
decisions.
I
So
we
had
a
call
last
tuesday
and
we
gathered
a
lot
of
inputs
from
everyone.
What
is
everyone
thinking
about?
What
is
the
best
proposal
to
make,
and
we
have
a
token
log
instance
that
it's
been
taking
a
really
long
time
for
me
for
this
to
load
today.
I
So
I
hopefully
hope
there
is
no
problem
with
it
I'll
check
with
wesley,
but
you
should
oh
here
it
is
I
just
needed
to
refresh
so
sam
and
griff
submitted
proposals
already
and
we're
hoping
to
have
many
more
that
will.
That
will
have
a
a
great
perspective
of
what
are
all
the
thoughts
from
the
community
in
the
direction
we're
we're
taking
with
the
impact,
our
intervention.
I
So
I
hope
everyone
can
participate
and
the
timeline
we
have
chosen
is
we
extended
a
little
bit
from
last
time.
We
talked
because
we
heard
from
some
people
that
making
proposals
until
this
week.
It
would
be
very
tight
on
time,
so
we're
going
to
close
the
primaries
on
next
thursday,
that's
july
1st.
So
that
gives
a
little
more
time
to
make
proposals,
and
hopefully
we
have
some
days
just
for
voting.
I
So
if
proposals
can
be
submitted
until
the
weekend
or
until
monday,
that
would
be
really
really
great
and
we
have
three
or
four
days
just
for
voting,
and
then
the
runoff
proposals
will
be
created
on
july,
2nd
and
the
vote
of
the
runoff.
Since
it's
a
reduced
number
of
proposals
will
run
just
from
the
second
to
the
sixth
and
then
we're
hoping
to
hatch
between
the
ninth
and
the
eleventh,
and
this
is
really
exciting.
I
This
is
the
last
piece
for
the
hatch,
so
we're
really
hoping
to
have
the
max
participation
possible,
and
all
of
you
guys
in
this
call
are
stakeholders
that
can
vote.
E
Thank
you,
libby
yeah.
First
of
all,
I
want
to
say
sorry
because
I
I
well,
I
miss
recording
the
price,
so
it
would
be
super
cool
if
you
guys
could
write
it
on
the
channel
and
especially
like
don't
not
forget
to
press
yourself
and
yeah.
It
would
be
super
nice
and
I'm
so
sorry
again
for
missing
that
and
then
for
the
updates.
E
And
can
you
go
on
the
next
slide?
Lately
yeah
we
yeah.
We,
we
meet
bi-weekly
on
monday,
three
pm
ct
and
yeah.
We
have
two
little
projects
on
what
that
are
going
on.
That
is
the
credential
discussion
management
that
it's
yeah.
It
would
be
super
cool
to
have
more
engagement,
but
we
also
yeah
we're
working
on
like
who
should
have
like
the,
and
we
also
registered
topic
on
omega.
E
So
yeah
omega
is
also
thinking
on
it
and
well
yeah,
and
then
well
also
working
on
rules
for
different
platforms,
but
for
the
people
who
have
admin
powers
right
now,
we're
missing
a
hotspot,
medium.
E
Yeah,
if
yeah
yeah-
and
we
decided
just
to
put
like
the
the
audience
we
have
and
just
announce
them,
announce
them
every
once
in
a
month,
so
yeah
people
know
what's
going
on
with
the
outage
and
yeah
and
yeah.
I
wanted
to
make
sure,
like
normally
like
the
working
groups
that
have
a
yellow-
it's
not
because
like
they
are
not
being
transparent,
but
it's
mostly
because
of
the
of
the
business
plan
after
heights
that
yeah
some
there
are
some
blank
spaces
and
yeah.
E
It's
mostly
that
and
the
working
groups
who
do
not
have
aldi
is
because
they
are
mostly
new
working
groups
that
yeah
they
are
engaging
with
the
tc
and
with
that
I'll
pass
it
to
america.
I
So
lady
couldn't
enter
because
the
room
was
full,
so
she
asked
me
to
give
some
updates
for
omega,
so
we're
we're
working
on
refreshing,
our
system,
thinking
with
integral
frameworks
like
cinephone,
integral
theory
and
the
t
proposals,
and
and
formulating
a
t
proposal
of
who
owns
ethics
and
t
consilience.
I
So
this
is
being
sketched
and
will
be
shared
soon
and
also
we
were
working
with.
Let's
see
if
I
can
paste
it
here,
this
mirror
board
that
has
the
updates
from
the
type
form.
So
we
had
21
answers,
and
I
put
them
all
here,
so
we
can
play
with
them
and
see
yeah.
What
are
what
are
some
of
the
answers
for
this
first
tea
ethos
type
form
research
that
went
out
so
feel
free
to
look
around
too
and
I'll
pass
to
ygg
with
labs.
G
Livi,
that's
so
cool
that
you're
able
to
import
the
survey
results
into
notes
like
that
in
miro
and
zeptimus.
That's
so
sad,
you
missed
the
recording
of
the
praise.
I
think
this
just
shows
how
valuable
zeptimus
is
and
that
he's
at
the
top
of
the
charts.
For
a
reason,
luckily,
you
guys,
I
got
you,
I
recorded
the
praise,
but
I
did
miss
some
of
it.
G
I
think
I
got
about
half
of
it,
but
I
think
it'd
be
really
cool
if
every
single
person
in
this
call
jumps
into
the
praise,
channel
and
dishes
the
praise
that
they
said
that'd
be
a
cool
decentralized
solution
to
this,
so
tech
labs,
whoever's
on
the
slides,
maybe
go
to
the
next
one:
who's
every
screen
sharing
I'll,
be.
V
G
Because
we're
a
bit
over
time
so
praise
analysis,
dashboards
are
up,
so
I
have
the
links
here
and
go
ahead
and
make
proposals.
There's
two
proposals
so
far,
so
jump
in
and
make
proposals.
I
want
to
redirect
some
praise
to
heater
because
I've
been
getting
praised
for
this
te
services
initiative,
but
that's
all
peter
or
heater.
G
It's
his
tag
so
go
ahead
and
dish
praise
the
heater
for
that.
It's
super
cool
initiative,
awesome
stuff
coming
out
of
that
and
that's
most
yeah
tech
coordination
labs
on
fridays
a.m,
pst
6
p.m,
cet
and
hack
sessions
on
sundays.
So
I'll
see
you
guys
there
and
I'll
pass
over
to
griff
for
params
or,
let's
see
com's
actually
chewy.
A
Thanks
ryggy,
okay,
super
quick:
we
meet
on
tuesdays
at
9,
00
a.m,
pst
and
6
p.m.
Cet,
and
do
you
have
any
content
requests?
Do
you
need
like
anything,
to
facilitate
communicating
something?
That's
going
on
in
your
working
group?
Please
feel
free
to
reach
us
out.
We
have
a
content
and
distribution
repo.
You
can
go
in
there.
We
also
have
a
twitter
spreadsheet.
You
can
go
in
there.
You
don't
have
to
write
the
whole
tweet.
A
You
just
have
to
write
the
objective,
we'll
be
hacking
into
this
list
many
times
per
week
and
we
can
draft
whatever
you
need.
So
please
feel
free
to
jump
in
and
make
sure
you
also
check
our
common
swarm,
weekly
updates
and
remember.
A
We
do
have
a
content
workshops
where
we
can
hack
around,
like
anything
that
you
have
purpose
for
for
publishing
or
for
whatever
needs
that
you
have
in
in
your
in
your
working
group
and
that's
it
I'll,
keep
it
short
I'll,
pass
it
to
griff
in
params
or
mitch.
I'm.
W
Gonna
take
it
from
because
he's
having
some
crazy
issues
so
just
brands
working
group
we
meet
twice
a
week.
We've
got
the
tuesday
meeting
and
then
we've
got
the
wednesday
hack
session.
So
that's
coming
up
pretty
quick.
What
we've
been
working
on
is
the
commons
configuration
dashboard,
that's
coming
along
pretty
good,
and
so
the
first
draft
specs
are
almost
finished
for
the
design,
validation
and
then,
on
the
back
end,
we've
got
a
couple:
all-stars
working
and
building
the
python
modules
to
get
that
going
so
come
to
the
hack
session
on
sunday.
W
C
I'm
sorry
thank
you
so
well,
we
have
a
a
new
heights
of
rehearsal,
since
we
did
a
mistake
with
the
with
the
last
one.
It
was
not
a
critical
mistake,
but
we
just
decided
that
it
is
better
to
start
from
the
beginning,
and
this
time
we
have
the
new
community
video.
C
C
Paolo
is
working
on
an
evm
scripted
library,
which
is
a
library
that
will
allow
any
dow
to
be
able
to
install,
modify
any
parameter
or
any
permission
or
anything
actually
or
need
new
tokens
or
water
tokens
in
just
one
boat,
and
it
has
been
something
that
has
been
very
painful
for
the
space.
During
always,
I
guess
it
was.
It
was
possible,
but
it
was
not
easy.
C
So
we
thought
that,
in
order
to
create
the
once
upright
script,
it
was
time
for
something
like
that.
So
we
are
overextending
a
little
bit
in
order
to
have
a
tool
that
is
useful
for
not
only
the
command
to
break
but
for
any
kind
of
upgrade
of
allow,
and
also
for
the
whole
one
height
ecosystem,
and
also
we
have
some
front-end
improvements
at
compared
to
commerce.org
made
by
noogan,
and
also
peter
has
been
working
on
on
adapting
the
the
front-end
for
the
new
type
of
contract
that
it's
still
not
working.
C
O
We
have
a
tre
kana,
hey
from
the
ocean
protocol
and
he's
going
gonna
go
over
token
spice
and
kind
of
some
agent-based
modeling
that
he's
working
on.
I
know
it's
at
the
top
of
the
hour
we're
kind
of
running
over
late,
but
if
you
have
a
chance
to
stay,
please
stay
and
listen
to
this
presentation,
because
it's
really
awesome
so
I'll
pass
it
over
to.
I
Youtube
or
if,
before
passing
to
trent,
I
just
want
to
make
a
quick,
quick
announcement
that
we
have
a
hatch
dress
rehearsal.
So
please
everyone
click
in
here
and
go
test.
The
hatch,
it's
gonna,
be
very
important
for
us
to
have
feedback
on
that
and
with
that
I
passed
to
you
trent
with
tokens
fights.
P
P
Let's
see
here
thanks
for
your
patience
and
thanks
for
sticking
around,
I
will
try
to
keep
this
presentation
to
about
10-15
minutes
and
yeah.
Let's
go
and
I'll
share
my
screen
here.
J
P
P
P
So
with
that
I
will
get
started,
so
this
is
an
introduction
to
spice
and
token
spice
short
version.
There
are
long
versions
too.
I've
already
put
the
link
for
my.
P
The
token
space
page,
if
you
want
to
look
later,
that
I'll
get
going,
so
the
outline
of
this
talk
is
I'm
going
to
talk
about
some
flows
from
analog
circuit
electrical
engineering.
I
am
an
electric
engineer,
myself
brief,
loose
pure
manual,
a
basic
spice
flow
and
a
spice
in
the
lip
flow.
Then
I'm
going
to
talk
about
similar
flows
that
are
possible
for
token
engineering,
pure
manual
basic
token,
spice
and
token
spice
in
the
loop
and
finally,
I'm
going
to
zoom
into
some
details
of
token
space
electrical
engineering
flows.
P
So
one
of
the
people
that's
called
earlier
mentioned,
they
love
math,
so
here's
some
math
for
the
lovers
of
math.
If
you
are
an
analog
circuit
designer,
this
is
basically
sort
of
where
you
spend
a
lot
of
your
time
doing
in
the
initial
design.
J
P
You
are
looking
at
some
sort
of
topology
on
the
left
and
you're,
basically
coming
up
with
equations
to
try
to
model
that
in
this
case,
it's
about
trying
to
model
the
game
bandwidth.
It's
just
a
performance
parameter
as
a
function
of
gm1.
That's
a
a
design,
variable
trans,
conductance
of
transistor
one
and
a
load
capacitance,
and
then
you
know
with
skill
and
experience.
It
usually
actually
takes
a
lot
of
skill
and
experience
many
years,
typically
a
phd's
worth.
P
P
Lot
of
analog
designers
spend
time
at
day-to-day
today.
They've
been
doing
this
since
the
60s
and
the
flows
have
got
more
refined
over
time.
Then
in
the
70s
along
came
spikes.
It
was
there's
a
lot
of
people
trying
to
do
circuit
simulators
and
the
first
good
one
that
came
out
was
something
called
spice
in
1973
and
ever
since
then
it's
been
refined,
refined,
refined,
and
so,
when
you
say
spice
to
an
electrical
engineer
or
an
analog
designer,
they
think
circuit
simulation
so
including
myself.
I'm
a
bit.
P
But
I've
spent
enough
time
in
in
the
world
of
analog
design
that
yeah
that's
how
it
is
and
building
tools
for
them
as
you'll
see.
So
this
is
the
overall
flow
for
a
circuit
designer
who
wants
to
use
a
simulator.
They
basically
do
their
initial
manual
design,
where
they've
probably
taken
the
topology
from
somewhere
else,
and
then
they
they
size
the
design
they
figure
out.
P
You
know
what,
in
this
picture,
on
the
right,
it's
like
what
resistance
for
the
resistor,
what
parameters
for
the
diode
and
the
capacitor
et
cetera,
and
they
have
different
formulas
too
from
that
manual
design,
where
they've
got
the
schematic
and
the
parameters,
then
they
say:
okay,
I
want
to
simulate
this
thing
and
they
enter
a
net
list,
and
this
the
netlist
is
a
bunch
of
text
like
the
tiny
little
text
you
see
in
the
middle
here,
the
next
screen
will
show
more.
P
I
think
I
have
it
yes
and-
and
they
can
enter
that
manually
or
they
can
have
a.
P
Around
and
so
on,
and
it
generates
an
address
for
them
automatically
and
finally,
they
run
spice
the
circuit,
simulator
and
the
output
of
running
spice.
It
comes
out
its
own
csv
file,
but
there's
always
waveforms
and
so
on
to
help,
and
that's
what
we
see
on
the
bottom
here.
So
this
is
the
the
standard
flow
that
analog
engineers
have
have
used
since
the
since
the
70s.
P
P
The
very
top
line
of
this
it's
got
a
section
for
basically
specifying
the
voltage
source,
which
is
well
apart,
voltage
one
going
from
node
one
and
node
zero
and
then
it
talks.
It
has
a
few
different
parameters
in
this
case.
It's
specifying
that
it's
a
transient
square
wave
with
going
from
minus
10,
volts
to
plus
20
volts
and
more
and
then
there's
a
capacitor
there's
a
diode,
a
resistor
and
more
and
basically
specifies
you
know
which,
which
different
nodes
they
connect
to
and
and
then.
P
An
ac
and
a
transient
analysis
transient
is
time
series
dc
is,
I
won't
get
into
it,
doesn't
matter,
but
basically
you're
specifying
different
ways
that
you
want
the
thing
to
sort
of
flex
the
circuit
and
not
showing
here,
there's
also
dot
measure
commands,
which
might
say
I
want
to
know
what
the
the
current
was
over
time
at
this
particular
node
here
and
so
on.
P
So
the
summary
is
you're
specifying
how
these
inside
a
net
list,
you
specify
how
the
different
parts
are
connected
and
you
specify
how
you
how
you
want
to
sort
of
perturb
the
circuit
and
what
analysis
you
won't
want
to
have
transient
and
so
on,
and
what
we
want
to
measure.
So
that's
the
spicenet
list
once
again
a
standard
staple,
and
you
know
the
standard
format
for
specifying
it
goes
back
to
1973,
and
you
know
people
have
used
it
ever
since
it's
part
of.
P
Chips
to
this
day,
but,
interestingly,
what
happened
was
by
the
mid-90s.
Circuits
computers
had
got
fast
enough
that
you
could
run
spice
not
just
once,
but
you
could
run
a
bunch
of
times
in
a
row,
because
you
know
a
small
circuit
like
this
on
the
top
right
that
might
take
five
minutes
or
20
minutes
in
1973,
but
in
by
1995.
P
It
would
take
like
one
second,
so
you
could
say:
okay!
Well,
you
know
why
not
just
simulate,
you
know
say:
10
simulations
in
a
row
for
10
different
values
of
the
voltage,
the
power
supply
voltage,
for
example,
et
cetera,
et
cetera,
and
that's
what
people
started
doing
a
little
bit
in
the
80s,
but
with
more
advanced
tools
in
the
90s,
and
it
was
in
the
90s
that
I
started
getting
into
circuit
design
a
lot
and
the
cad
tools
for
circuit
design,
especially
what
is
called
spice
in
the
loop.
P
So
this
is
the
idea
simply
that,
rather
than
just
doing
a
single
simulation
kicked
off
by
the
analog
designer,
they
have
a
tool
that
runs
a
lot
of
simulations.
They
might
run
10
simulations
or
100
or
10
000
right.
So
the
general
flow
is,
there
is
a
manual
initial
design
where
the
designer
has
that
initial.
You
know
topology
the
structure
and
the
parameters,
and
then
the
next
parts
is
actually
all
managed
by
sort
of
design
or
verification
tool.
It
can
be
doing
design,
it
can
be
doing
verification
or.
P
Then
you
know
it
uses
the
next
sim
and
simulates
that
and
loops
and
loops
and
loops,
and
the
result
on
the
as
an
example
in
the
bottom
right.
I'll
give
many
more
examples
in
following
slides.
This
is
basically
there's
you
know
not
just
a
single
waveform
from
a
single
set
of
from
a
single
simulation,
but
a
bunch
of
them.
So
this
is.
P
In
circuit
land,
what
does
some
of
these
tools
actually
look
like?
Here?
Are
some
examples:
here's
one
called
fast
design
sweep
and
it's
basically
what
it
does
is
it
does
a
bunch
of
samples
across
all
the
different
design
variables.
Let's
say
you
have
10
different
design,
variables,
widths
and
lengths
transistors,
resistances
capacitances.
P
It
samples
uniform
randomly
across
the
whole
space
and
with
each
point
in
that
space
it
does
a
simulation,
so
maybe
it
does
100
samples
and
then
with
each
sample
it
simulates
that
and
then
from
those
simulations
it
builds
a
model
or
a
regression
model
that
maps
the
design
variables
that
it
sampled
from
this
10
dimensional
vector
to
a
single
output
vector
such
as
gain
or
power
consumption
or
something,
and
then
it
has
pretty
plots
like
you
see,
and
this
basically
makes
it
really
nice
and
easy
for
designers
to
sort
of
move
around.
P
Different
design
spaces
and
see
the
effects
of
different
variables.
These
effects
can
be
quite
non-linear.
For
example,
if
you
look
at
the
plot
in
the
bottom
right,
you'll
see
that
it's
you
know
very
curvy
and
stuff
right,
and
that
means
that
you
know,
as
you
change
one
variable,
it
interacts
with
other
variables
towards
the
output
here,
one
picture
above
the
very
middle
plot
on
the
right.
You
see
that
it's
sort
of
straight
lines
in
one
direction,
so
that
means
that
only
one
variable
is
making
a
difference.
P
The
the
y
variable
and
the
the
x
variable
isn't
making
any
difference
at
all
right
and
the
z
variable
the
colors
is
is
actually
the
the.
P
This
gives
you
a
feel
of
a
tool.
There's
many
other
tools.
This
one
here
is
simply
for
fast
design.
Space
exploration,
there's
another
one
for
worst
case
analysis.
You
know,
if
you
say:
okay,
I've
got
a
temperature
range
from
minus
40
degrees
to
plus
40,
and
I've
got
you
know
a
load
from
you
know:
10
ohms,
resistance
to
10
kilo,
ohms
resistance-
and
maybe
you
know
three,
four
or
five
other
parameters
say:
okay,
tell
me
now
what
combination
of
these
things
of
temperature
of
load,
et
cetera,
gives
me
the
worst
case
power.
P
You
know
that
has
the
highest
power
and
has
the
worst
gain
etcetera,
etcetera,
etcetera
and
that's
a
tool
that
I've
also
had
and
helping
to
build
and
it
under
the
hood.
What
it's
doing
to
do
this
efficiently,
rather
than
looking
at
all
the
combinations,
because
there
could
be
like
a
million
combinations,
it
runs
an
optimization,
a
global,
optimization
and
finds
that
worst
case
thing
and
it
basically,
then
you
can
say
hey.
P
P
P
Another
another
tool
that
helps
with
design
it
takes
a
net
list
on
the
left
and
it
perturbs
a
bunch
of
different
variables.
It
can
be
the
design
variables
or
the
random
variables
whatever
it
takes
a
bunch
of
points
in
the
space
and
then
from
that
it
simulates
them
with
spice,
and
now
it
has
100
points
or
a
thousand
points.
P
One
that
you
can
actually
see
the
formula
itself
and
you
can
call
this
symbolic,
modeling
or
white
box,
modeling
or
symbolic
regression.
However,
you
want
to
call
it,
and
so
examples
of
the
results
are
on
the
bottom,
where
it's,
the
very
top
row
is
for
gain
and
basically
you
can
see,
there's
a
closed
form
expression
for
gain
as
a
function
of
design
and
variables,
id1,
vsg3,
etc,
and
you
can
see
they're
pretty
complicated,
we've
got
lawn
in
there,
we've
got
different
ratios
and
so
on
and
other
ones
to
get
the
same.
P
That
people
can
use
to
get
insight
into
you
know
in
a
close
form
way
of
what
things
look
like
and
yeah
it's
drawing
from
the
simulation
results
itself.
Another
one
is,
you
can
even
go
full
on
synthesis.
You
can
say
you
know
what
I'm
going
back
to
here.
P
What
if,
instead
of
doing
that
manual
initial
design,
you
don't
actually
specify
a
structure
like
the
topology
or
parameters.
You
just
say:
here's
my
space
of
all
the
possible
topologies
and
parameters,
go
nuts,
mr
mr
ai
algorithm,
and
go
find
the
results
for
me
and
that's
what
it's
doing
here,
and
so
you
can
see
here.
Basically
what
it's
done
is
it
doesn't
just
spit
out.
One
result:
one
good
result
this
one:
it
actually
spits
out
a
whole
bunch
of
results,
a
whole
trade
off
in
this
case
it's
for
three
different
settings
abc.
P
Let's
look
at
the
setting
on
the
right.
The
blue
curve-
and
that
is
every
single
point
on
that
curve-
is
a
different
design.
There's
two
different
topologies
and
each
topology
has
you
know
a
bunch
of
different
sizings,
10
or
15
different
sizings
and
together
they
form
this
trade-off
of
gain
bandwidth
and
power.
So
if,
if
you
want
higher
and
higher
gain
bandwidth,
then
it's
going
to
cost
you
more
and
more
power
right.
P
So
it's
a
tradeoff
and
pretty
interestingly
right
at
some
point
and
gain
bandwidth
at
about
1.8
gigahertz
or
so
it
does
a
switch
from
one
topology
to
another,
and
this
is
actually
going
from
a
single
stage
circuit
to
a
two-stage
circuit,
a
folded
version
of
it.
So
an
analog
engineer
will
look
at
this
and
be
like
oh
wow.
So
this
is
another
example
of
a
tool
that
uses
spice
in
the
loop.
P
In
this
case
it's
actually
using
splice
in
the
loop
to
automatically
come
up
with
the
the
structure
and
the
parameters
itself
and
there's
a
whole
bunch
of
space
in
the
loop
tools.
There's-
and
you
know
we
can
break
them
roughly
into
two
categories,
one
for
verification.
P
You
know
nominal
verification,
corner
extraction
worst
case
analysis,
monte,
carlo,
nor
and
for
design
itself.
So,
where
you're
exploring
the
design
space,
you
can
do
things
more
manual
exploration,
things
like
design,
sweep
sensitivity,
analysis
and
then
you
can
get
more
and
more
automated.
You
can
do
local
optimization,
then
go
global
or
synthesis
where
you're
actually
changing
the
structure
itself
and
then
even
variation
where
synthesis,
we're
changing
the
structure
itself,
but
also
accounting
for
all
the
different
variations.
You
know
random
variations
worst
case
et
cetera.
P
So
so
that's
basically
a
bunch
of
tools
that
can
get
built
and
in
fact
these
are
all
out
there
for
circuit
land.
So
this
is
circuit
land.
This
is
where
I
spent
almost
two
decades
of
my
career,
basically
building
cad
tools
for
people
with
ai
under
the
hood,
and
it
was
always
the
ai
part
that
I
loved,
so
that
was
you
know,
really
fun,
I'm
trained
as
an
electrical
engineer,
but
ai
was
sort
of
my
first
love
in
tech
yeah.
P
So
then
token
spice
and
token
engineering,
so
I
started
with
spice
and
electrical
engineering.
Now,
let's
take
this
to
token
engineering
land
and
as
a
talk
right,
I've
talked
about
ee
and
the
three
flows
for
ee,
especially
analog
circuits.
Now,
let's
yeah
look
at
those
three
flows
for
tokenland
so
similar
to
the
flow
you
saw
before
that
we
can
have
a
flow
that
starts
with
manual
design.
P
That
then
goes
to
entering
a
netlist
and
finally
simulating
with
a
simulator
for
tokens
token
space
and
on
the
top
of
manual
design.
What
do
those
schematics
look
like?
I
have
a
couple
examples
for
my
work.
One
is
the
the
web
3
system,
that's
the
diagram
in
the
grey
and
another
one
is
a
model
of
ocean,
a
high
fidelity
model
of
ocean
markets,
and
that's
the
one
on
the
right
there's
a
lot
more
details
than
this.
P
In
the
token
supplies
github
by
the
way,
but
just
to
give
you
a
feel
at
this
highest
highest
level
and
then
to
enter
the
net
list
so
token
spice
is
an
agent-based
simulator
where
you
can
and
have
agents
that
are
pure
python.
If
you
want,
but
also
critically,
you
can
have
agents
that
are
wrapping
solidity
code
and
that
solidity
is
simulated
directly
on
evm
in
ganache
you
could
actually
use
robson
and
whatever
else
too,
but
it's
just
more
convenient
than
ganache.
Of
course.
So
basically,
your
net
list
is
python
and
solidity
together.
P
Right-
and
this
is
all
you
know
token
spice
itself
is,
you
know
all
written
in
solidity
and
then
it
imports
the
smart
contracts
from
elsewhere,
but
you
can
use
you
know
you
can
evolve
that.
However,
you
want,
of
course.
So
that's
that's
the
heart.
You
know
good
spice.
Is
this
agent-based
evm
simulator
and
then
once
you,
you
know
you
enter
that
list
and
then
you
run
the
thing
and
it
gives
you
simulation
results
in
this
case.
P
I
worked
on
this
initially
started
about
a
year
ago
on
this
just
over
a
year
ago
and
it
wasn't
evm
based
then,
but
then,
as
I
was
starting
to
do,
the
the
balance
rm
simulations
and
stuff,
I
realized
that
I
really
wanted
to
have
evm,
because
I
found
myself
copying
and
pasting
solidity
code
trying
to
convert
it
to
python
and
realizing
it
was
super
air
prone,
and
I
mean
why
not
just
run
the
solidity
code.
Ganache
is
sitting
right
there.
P
So
that's
what
I
did
basically
so
to
zoom
in
on
the
netlist
right.
What
does
the
token
spice
netlist
look
like?
You
know
the
thing
that
you're
simulating
well
there's
the
python
on
the
left.
So
in
this
case
you
can
see.
There's
you
basically
have
a
bunch
of
agents
to
find
each
agent
is
defined
as
a
class,
and
it's
purely
open-ended
right.
You
can
get
it
to
do
whatever
you
want
and
then
you
add
them
together.
As
a
set,
you
know
new
agents,
one
two
and
so
on.
P
So
we've
got
a
marketplace's
agent,
a
router
agent
and
a
burner
agent
and
so
on
and
each
agent.
Basically,
you
specify
what
else
it
connects
to
what
other
you
know
just
like
in
spice
you,
you
connect
the
different
nodes
to
each
other
same
thing
here
and
they
have
their
own
parameters.
You
know
you
can.
This
marketplace
agent,
for
example,
starts
with
zero
us
dollars
and
zero
ocean,
but
later
on
you
know
some
of
the
other
agents.
P
Have
you
know
a
bunch
of
us
dollars
for
ocean
and
then
under
the
hood,
some
agents
are
evm
based.
So,
for
example,
the
the
pool
agent
under
the
hood
wraps
oceans
be
pooled
up
by
library,
which
is
simply
a
driver
for
balance
or
pool,
be
pool.
That's
all
and
that's
what
we're
looking
at
on
the
right,
just
a
snippet
of
bpool.sol
on
one
of
the
different
swaps.
So
you
know
none
of
this
needs
to
get
implemented.
P
It's
just
basically,
you
know
these
contracts
are
deployed
to
ganache,
and
you
know
the
address
is
deployed
to
you
know
the
apis
and
everything
else
connects
together.
So
this
was
spice
in
the
loop
right.
Sorry,
this
is
the
the
basic
one
step
tokens
by
simulation,
but
what's
pretty
cool
now
is
you
can
say?
Let's
have
spikes
in
the
loop
principles
in
the
loop,
so
just
like
the
analog
circuit
version,
you
start
with
the
manual
initial
design
with
these
net
lists,
and
then
you
can
say:
okay,
I
want
to
do
a
verification.
P
P
The
flow
is
the
same,
chooses
the
next
sim
or
simulations
like
one
or
many,
and
with
each
simulation
it
generates
a
net
list,
combination
of
python
and
solidity
and
runs
token
spice
and
gets
the
results,
measures
the
results
and
then
loops
loops
loops
as
it
needs.
So
that's
token
splice
in
the
loop
and
what
sort
of
tools
can
we
do
with
this
general
flow
everything
you
saw
for
circuit
land?
We
can
have
very
a
bunch
of
verification
tools.
We
can
have
a
bunch
of
design
tools
for
verification.
P
You
know
nominal
corner
extraction,
worst
case
analysis,
monogram
simulation
and
more
same
thing
for
design.
We
can
have
design,
sweep
local,
optimization,
global,
optimization
synthesis
and
variation
or
synthesis,
and
it
gets
pretty
interesting
when
we
get
to
synthesis
us,
because
if
you
are
saying
I
want
to
do
synthesis
on
the
solidity-based
agent
say
like
an
amm,
then
you're.
P
Actually,
what
you're
doing
is
searching
through
the
space
of
solidity
code
or
evm
bytecode
itself
and
what's
cool
is
there's
actually
a
fair
bit
of
research
on
evolution
and
search
in
general
through
program
spaces,
and
I
personally
actually
did
a
lot
of
work
in
evolution
through
a
grammar
constraint
space.
So
you
could
say:
okay,
my
grammar
is
this
subset
of
solidity,
a
bunch
of
building
blocks,
how
they
connect
and
I'm
going
to
search
through
that
space,
and
so
I've
got.
P
Code
online
that
I
referenced
here
called
mojito.
That
right
now
is
tuned
for
circuits,
but
you
could
swap
with
spice
for
token
spice,
so
I'll
put
the
circuit
building
blocks
with
solidity
building
blocks
and
then
you're
good
to
go,
and
you
can
be
evolving
evm,
byte
code
or
evolving
solidity
code
itself
with
token
splice.
So
I'm
pretty
excited
about
that
as
a
direction
to
go.
This
also
points
to
doing
things
like
you
know:
a
live,
automated
trading
system,
that's
you
know
evolving
our
robots
or
whatever.
P
You
want
right
and
there's
some
interesting
implications
for
maybe
as
well
so
keeping
going
almost
done
token
splice
details.
So
the
main
thing
is,
if
you're
interested
to
learn
more,
it's
all
open
source,
apache2
licensed
on
github.com
oceanprotocol,
slash
token
spice
talks
about
what
it
is
right.
It's
an
evm,
agent-based
token
simulator,
the
agents
are
classes
et
cetera.
Each
agent
has
its
own
wallet
and,
like
I
mentioned,
they
can
also
be
wrapping
solidity
and
be
right.
P
That
part
is
running
on
ganache
yeah
it
and
it's
still
pretty
young
a
software.
I've
tested
it
well
and
so
on.
So
everything
that
all
the
functionality
and
features
that
it
has
are
well
tested,
but
it
still
has
some
features
that
I
need
to
get
in
most
notably
right
now,
if
you
want
to
have
a
new
netlist
you'll
have
to
fork
it
and
put
that
in
sort
of
in
a
hardwired
way.
So
that's
that's
one
thing
that
that's
my
next
thing
up
to
do.
P
Also,
though,
of
course,
I
encourage
all
of
you
if
you're
interested
come
and
help
me,
you
know,
build
and
extend
this
over
time.
My
time
and
stretch
is
pretty
thin,
so
I
can
only
spend
a
bit
of
time
with
this,
but
you
know
there
seems
to
be
an
asset
community
interested
in
helping
to
extend
this,
and
that's
wonderful.
P
So
you
know
inside
here.
How
do
you
get
going
with
it?
Well,
so
so
right
below
the
top
description,
it
talks
about
the
initial
setup.
So
the
first
thing
is
I'll:
just
get
to
it,
you
get
ganache
running
and
then
you
deploy
some
more
contracts
to
ganache
here,
I'm
giving
an
example
with
ocean
contracts-
and
you
know
from
the
ocean
repo,
but
you
can
have
whatever
small
contracts
you
want,
of
course,
and
you
you
keep
going.
P
Just
to
give
you
a
feel
of
some
of
the
similar
sim
results.
This
is
the
line
of
vm
results
shown
because
the
evm
part
with
the
end
to
end
is
still
a
work
of
progress.
P
Here's
an
example
of
monthly
r
d
span
from
you
know:
web3
sustainability,
loop
models,
left
side
is
linear.
Right
side
is
log
and
kind
of
gives
you
a
feel
over
time,
and
there
are
actual
numbers
for
this.
But
we
don't
like
to
make
this
public
because
we
don't
want
speculators
to
basically
kind
of
run,
a
mock
with
just
numbers
that
our
simulators
give.
P
So
so
we
hesitate
to
make
this
public,
but
there's
also,
you
know,
what's
the
market
rate
places
sales
and
growth
rate
over
time
and
then
what
is
the
ocean
token
count
over
time
and
then,
of
course,
what
we
did
when
we
designed
you
know
ocean
token
was
things
like
do
we
want
to
have
you
know
five
percent
of
token
revenue,
burning
or
95,
or
what
sorry
question?
P
Okay
and
yeah
there's
more
simulations
yet
monthly
ocean
minted
and
burned.
Dow
income
so
for
ocean
has
a
dow
a
grand
style.
So
what
does
that
income
look
like
over
time
and
we
tuned
parameters
such
that
for
the
first,
eight
or
so
years?
It's
pretty
steady
and
after
that,
as
the
ocean's
fundamental.
P
Overtakes,
the
speculation
valuation
based
on
our
models,
then
the
the
revenue
will
go
exponential.
Actually,
maybe
that
will
happen
sooner
maybe
later,
but
we
basically
tuned
such
that
you
know:
there's
there's
steady
income
for
dao
ocean
dow
for
the
first
10
years
and
after
that
yeah
goes
up.
So
all
this
is
really
important
right.
We
answered
we
asked
and
answered
a
lot
of
what,
if
questions
right,
what's
the
effect
of
burning,
how
do
we
have
a
smooth
distribution
of
tokens
over
atomic
center?
P
So,
to
conclude,
just
very
quick
summary:
I
started
with
talking
about
analog
circuit
design
flows
focusing
on
pure
manual
and
pulling
in
basic
spice
and
then
pulling
in
spice
in
the
loop
and
the
amazing
tools
that
can
get
built
from
that
and
where
I've
had
a
lot
of
experience
in
that
and
then
how
we
can
pull
that
into
token
engineering
land
with
pure
manual
design,
which
is
a
lot
of
the
practice
now
and
there's
some
nasa
simulators,
which
are
great,
I'm
a
big
fan
of
cad
cad,
for
example,
and
then
token
spice,
which
pulls
in
the
evm
side
of
things.
P
So
we
can
do
it
in
a
very
basic.
You
know
nominal
flow,
but
if
we
start
to
put
it
with
token
spice
in
the
loop
we
can
start
to
have
just
wicked
amazing
results.
Everything
from
like
really
great
variation,
where
analysis
to
account
for
uncertainties
in
a
big
way
to
optimization,
sweep
and
full
on
structural
synthesis,
searching
across
solidity
code,
etc.
P
And
then
you
know
token
spice,
like
I
mentioned
it's,
it's
pretty
young,
but
what
is
there
works
quite
well
and
where
it
has
a
lot
of
promise
and
yeah,
I
encourage
everyone,
you
know
come
and
kick
the
tires
of
it
play
with
it
contribute
to
it
yeah.
So
I
will
stop
there
and
see
what
questions
everyone
has.
I
Thank
you
so
much
trent.
That
was
a
very
valuable,
in-depth
explanation.
It's
so
incredible
to
have
this
in
our
community.
We
are
a
little
bit
over
time
and
thank
you
so
much
for
everyone
who
who
stayed
over
and
we
can
still
have
the
space
for
questions.
I
just
wanna
be
aware
that
there
is
also
a
gravity
call
that
it's
going
to
be
starting
in
the
gravity.
Channel
and
durga.
I
Das
is
going
to
be
talking
about
decolonization
to
us
and
all
of
the
things
we
need
to
think
to
keep
the
harmony
in
our
community
and
yes
for
everyone
who
needs
to
go
to
gravity.
I
really
recommend
and
also
if
we
want
to
stay
and
here
have
questions
to
trent.
That
is
also
a
very
valuable
moment
to
have
him
here
so
I'll,
open
the.
O
G
Hey
trent,
I
have
one
question:
okay,
have
you
ever
considered
the
idea
of
like
a
plug-in
architecture
with
token
spice,
so
is
it
possible,
maybe
that
you
could
have
like
a
standard
way
that
someone
could
package
an
agent
and,
and
then
that
could
just
be
like
a
standalone
repo
on
github
and
then
token
spice
could
essentially
have
like
a
like.
A
netlist
would
be
a
very
distributed
netlist,
so
it
could
just
basically
name
a
github
repository
to
pull
in
a
particular
agent.
G
Do
you
think
this
is
possible,
or
have
you
seen
anything
like
this
with
like
standard
packaging
for
spice
simulator
components
like
this.
P
So
spice
doesn't
do
it,
but
I
think
there's
a
straightforward
way
to
do
in
token
token
spice
and
it's
the
following.
So
the
net
list
that
I
see
is,
it
is
simply
going
to
be
python
code.
P
Where
it,
you
know
it's
adding
these
agents
one
at
a
time
right,
but
at
the
imagine
at
the
top
of
that
net
list,
it
just
does
import
reacts
and
library
x
just
happens
to
be
repo
on
pi
pi,
and
if
you
build
new
models,
you
know
maybe
there's
a
very
nice
simple
flow
to
publish
to
pi
pi
right,
make
it
even
thicker
than
it
is
right.
P
So
that's
one
way
we
could
probably
do
other
ways
too
to
make
it
you
know,
rather
than
relying
on
the
infrastructure
of
pi
pi,
because
maybe
that's
a
bit
too
heavy
for
here.
There's
probably
other
ways
too
right,
and
I
think
it's
a
great
question.
So
I
guess
also
in
circuit
land
there's
this
idea
of
ip
sharing
for
different
building
blocks
and
stuff,
and
a
company
made
like
there's
a
big
startup
that
did
quite
well
on
it
called
trenta
love.
P
P
Okay,
yeah,
I
guess
any
of
you
are
interested
to
learn
more
actually
I'll.
Put
this
link
to
the
slides
here,
for
you
guys
make
it
convenient,
and
if
you
know
you
want
to,
you
know,
explore
more
feel
free
to
you
know,
give
it
a
try.
Of
course
I
need
to
find
the
chat
here.
P
Okay,
slides
from
my
presentation
there
we
go.
I
just
heard
the
clients
cool.
Thank
you
very
much,
and,
and
also
if
you
go
to
token
spice
itself,
like
the
the
on
github
links
to
the
slides
as
well
now
so
and
encourage
each
of
you.
If
you're
interested,
you
know,
go
and
give
it
a
whirl
right,
go
through
the
the
quick
start
and
yeah.
I
think
it
has
a
lot
of
promise
right.
P
It's
I
see
it
as
quite
complimentary
to
cad
cad
cad
cat
is
really
tuned
for
early
stage
design,
where
you're
more.
You
know,
iterating
with
the
symbolic
models
and
the
equations
and
stuff
and
token
spice
is
more,
for
you
know
a
little
later
in
the
design
and
for
design
iterations
and
that
sort
of
thing.