►
From YouTube: W16 TEC Lab!: Hatch contracts testing and documenting 2
Description
🙏 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
A
B
Hey
barge
hey,
hi,
okay,
so
I
think
we
should
get
to
testing.
I'm
not
very.
I've
had
a
lot
on
the
go
the
last
few
days
and
I
injured
my
shoulder
too.
So
I'm
I'm
a
little
bit
less
prepared
today.
In
fact,
I'm
not
prepared
at
all,
but
I
figure
we
can
just
get
started:
anyways,
okay!
So,
let's
first
of
all
remind
everyone.
So
in
the
tec
labs
channel,
there
is
a
pinned
message
that
links
to
the
notion
workspace.
B
And
you'll
now
see
at
the
top
there's
a
link
to
the
workshop.
The
workspace
for
the
cad
cad
study
group-
that's
starting
next
week
and
so
you'll
see
the
attendance
sheet
here
in
the
work
in
the
workspace
so
for
everyone
here
go
ahead
and
open
up
the
attendance
sheet
and
we'll
fill
in
some
emojis
for
the.
B
A
A
Hey,
why
did
she
I've
been
a
very
like
not
catching
up
with
the
lab
for
a
while
and
I
feel
always
lost
when
I
come
to
the
calls?
Do
you
have
like
one
thing
I
could
watch
that
would
put
me
up
to
date,
like
one
or
another
session
to
advice.
B
Yeah
good
question:
the
labs
are
pretty
what
I
would
call
non-serial,
so
they
don't.
I
don't.
Usually
one
lab
doesn't
really
depend
on
a
previous
other
than
we've
done.
A
few
series,
of
course,
like
the
chess
thing
and
the
params
modeling
at
the
beginning
and
now
we're
doing
testing
contracts,
but
I
think
most
people
feel
lost.
B
So
you
don't
have
to
you
know
it's
good
you.
You
say
this
because
you're
definitely
not
the
only
one,
but
I
definitely
the
only
mandatory
part
of
the
labs
is
at
the
beginning
to
get
it
find
your
way
to
the
attendance
sheet
and
plug
in
an
emoji.
Just
because
I
think
that
sparks
a
little
bit
of
participation,
it
gets
people
to
feel
that
yeah
they
can
open
up
the
materials
on
the
fly
as
we're
going
and
start
to
edit
stuff
as
well.
So
let
me
know
if
you
can
find
the
attendance
sheet.
B
Yeah
and
so
yeah,
because
it
it
also
makes
sure
that
everyone
can
find
the
workspace
that
has
all
the
materials
and
that
workspace
is
pinned
from
the
labs.
B
Channel
and
the
attendance
is,
did
you
find
it.
B
B
B
So
let's
jump
in
so
I
I
don't.
I
don't
have
too
much
plan
for
testing
the
labs.
In
fact,
chewie
might
want
to
kind
of
jump
in
and
give
us
an
update
or
kind
of
help
drive.
But
what
I
was
planning
on
doing
is
just
going
back
opening
up
what
we
have
and
let's
let's
see
if
this
is
like
documented,
okay,
so
lab
15.
B
This
blog
post
is
kind
of
a
map
of,
what's
involved
with
the
hatch,
the
different
contracts
needed
for
the
freeze,
the
migration
tools,
which
need
documentation
and
tests,
which
I
know
the
commons
swarm
team
has
been
like
really
working
hard
on
and
then
the
hatch
template
tests
and
the
commons
upgrade.
But
that
comes
later
this
week,
we're
in
fact
I
think
this
weekend,
there's
a
push
to
really
get
the
the
hatch
contracts
and
the
migration
tools
ready
for
a
freeze.
B
Yeah,
so
we
have
the
migration
tools
and
the
hatch
template
and
just
to
make
sure
everyone
is
able
to
follow
along
what
I've
done
here.
Is
I've
opened
up
this
blog
post
and
additionally,
in
the
notion,
workspace
there's
the
calendar,
so
I
always
try
to
open
up
a
page,
so
you
can
go
to
the
calendar
and
find
today's
date
and
today
is
lab
16.
So
this
is
a
hatch
oops
edit.
B
So
this
is
hatch
testing,
part
2
and
from
there
I'll
make
sure
there's
this
link
to
the
state
of
the
hatch
blog
post
and
from
there.
You
can
find
all
the
components
of
the
hatch
and
check
them
out.
So
I've
just
opened
up
the
first
two,
which
are
the
migration
tools
and
the
hatch
template,
and
so
our
job
is,
I
think
we
should
add
some
information
to
the
readmes.
B
Last
week
we
got
some
help
on
how
to
actually
run
these
contracts
and
run
the
tests,
and
but
we
didn't
finish
our
job,
which
would
be
like
documenting
that
in
the
readme.
So
that's
what
I
want
to
accomplish
for
today
and
first
of
all,
just
to
double
check
to
make
sure
we
remember
how
to
run
the
contracts
and
run
the
tests.
So
I
think
that's
what
we'll
do
first,
but
I
think
I'll
pause
there
and
check
in
and
see.
B
Maybe
chewie,
I'm
wondering
do
you
have
any
information
or
do
you
want
to
give
us
a
kind
of
summary
of
what
is
how
everything's
going
what
you
guys
are
working
on
and
if
there's
anything
else,
we
should
be
aware
of.
C
Actually,
I'm
I'm
here
because
I'm
I'm
trying.
A
A
Wanted
to
you
know
to
just
like
observe,
maybe
and
and
oh.
B
B
Yeah
welcome
chewie,
so
the
labs
are
usually
more
of
a
like
a
data
science,
token
engineering
flavor
like
usually
we're
opening
up,
jupiter,
notebooks
and
working
in
python
and
doing
some
modeling,
but
just
I
know
the
it's.
It's
the
last
push
before
the
hatch
freezes.
B
So
I
wanted
to
use
the
labs
as
a
space
to
help
out
the
common
swarm
team
as
much
as
possible
and
educate
the
community
on
what
is
involved
because
we're
at
a
stage
where
what's
needed
is
documentation
and
testing
and
that's
kind
of
what
a
lot
a
lot
of
people
can
help
out
with
that.
Even
if
they're,
not
like
master
solidity
developers
like
myself,
so
I
just
wanted
to
sort
of
capture
and
broadcast
the
process
of
actually
running
these
contracts
and
poking
around
with
the
tests
and
then
making
some
contributions
to
the
documentation.
B
B
So
I
have
all
sorts
of
repos
here
I'll
just
make
a
clean.
B
Directory
so
we
have
this
empty
and
just
in
case
anyone's
like
new,
you
probably
can't
see
stuff
on
my
screen
too.
Well,
sorry
about
the
dark
theme
everywhere,
but
all
I've
done
is
you
know,
I'm
navigating
the
terminal
here
and
the
terminal
is
just
a
reflection
of
the
file
system
on
the
computer.
So
I'm
going
through
all
my
files,
I'm
in
my
workspace,
slash
tec
and
I
just
created
this
directory
called
clean.
So
there's
nothing
in
it.
It's
just
an
empty
folder.
B
B
B
B
So
it
takes
the
redeemable
reserve
and
the
non-redeemable
reserves
and
that's
in
the
hatch,
those
are
held
by
the
hatch
dow
and
in
the
commons
dow
we'll
have
a
griff.
You
might
be
able
to
help
me
out.
What
would
these
vaults
be
called
in
the
in
the
commons
dow?
Would
they
be
the
same
things
they
wouldn't
be
like
redeemable
and
non-renewable.
A
They're
they're
called
funding,
pool
and
reserve
and
they're
all
technically
agents.
So.
A
Yeah
I
mean
at
vaults
evolved
is
a
specific
type
of
aragon,
application
that
usually
is
connected
to
the
finance
app
and
then
there's
these
agents,
which
have
a
lot
more
there.
They
have
a
lot
more
surface
area,
they
can
do
what
is
was
generally
like.
A
B
A
A
B
Okay,
so
let's
let's
grab
one
of
these:
let's,
let's
take
this
hatch
template
so
on
github,
I'm
going
to
copy
the
link
and
in
my
terminal
I'm
going
to
go,
get
clone
and
paste
that
in
so
we're
grabbing
the
hatch
template
okay,
so
we
got
it
there.
So
I'm
going
to
go
into
the
hatch
template.
B
B
B
In
getting
all
the
dependencies,
so
if
for
anyone
who
doesn't
know
yarn,
is
a
package
manager
for
javascript
programs.
So
I'm
just
gonna
split
my
screen
here
and
we
can
open
up
the
actual
code.
B
Let's
see
yeah
so
we
have
docker
packages.
B
Okay
and
then
package.json
yarn.lock,
so
we
could
explore
these
right
on
github
and
if
you
see
package.json,
this
is
what
we
include
with
every
javascript
program
like
or
repository
that
you
might
find
on
github
and.
B
Solidity
projects,
smart
contracts,
maybe
I'll,
give
a
little
bit
of
background
here.
It's
the
concept
of
web3.
So
what
is
web3
3
is
a
hybrid
between
solidity
and
the
ethereum
world
and
javascript
and
the
web
world,
and
what
it
how
it
works.
Is
you
take
your
smart
contracts
and
they
get
compiled
using
a
program
called
solidity,
and
the
solidity
program
takes
a
smart
contract
and
compiles
it
down
into
a
byte
code
or
in
ethereum.
B
It's
called
the
application,
binary
interface
or
the
abi,
so
you
can
think
of
an
abi
as
a
compiled
smart
contract
and
it's
literally
like
a
punch
card.
So
you
might
remember-
or
you
might
know
about
like
the
history
of
computing
before
people
had
these
actual,
like
teleterminals,
like
a
like
a
television
screen-
that
they
could
interact
with
the
computers
with
they
would
actually
use
paper
punch
cards.
So
they
would.
B
And
so
it's
a
very
slow
developer
loop.
And
so
we
should
be
very
grateful
for
the
tools
that
we
have
available
today.
But
now
things
always
come
full
circle
because
basically
ethereum
or
what
you
call
the
ethereum
virtual
machine,
which
is
what
runs
on
any
ethereum
node.
It's
running
the
ethereum
virtual
machine.
You
can
think
of
that,
as
literally
a
little
machine,
a
little
computer
machine
that
you
have
to
insert
a
punch
card
into
to
get
it
to
execute.
B
What
you
want
it
to
do,
and
so
that
punch
card
is,
is
the
abi,
the
application,
binary
interface
and
it's
what
gets
fed
into
an
evm.
You
know
whether
you're
running
a
node
locally
or
maybe
you're,
using
infuria,
which
is
like
a
cloud-hosted
ethereum
nodes.
But
if
you
want
to
deploy
smart
contracts,
you
have
to
compile
them
into
the
abi,
and
then
you
have
to
get
that
abi
to
a
node
somewhere
and
maybe
run
it
locally.
B
B
So
if
you're
running
on
mainnet
then
and
you
deploy
a
smart
contract
and
and
run
it,
then
you're
making
that
punch
card
you're,
inserting
it
into
an
evm
somewhere
and
then
that
evm
is
broadcasting
it
so
that
every
other
evm
in
the
world
also
runs
that
program.
And
this
is
why
gas
is
so
expensive
because
when
you
do
something
on
ethereum
you're
doing
it
on
every
ethereum
node,
so
it's
a
super
inefficient
process,
but
it
achieves
this
goal
of,
like
globally
maintained
state
of
a
computing
system.
So
it's
super
cool.
B
So
what
is
web
3?
That's
the
whole
point
of
this
web
3.
Is
we
compile
our
solidity
contracts
into
these
like
punch
cards
and
then
we
take
these
punch
cards
and
we
embed
them
in
a
javascript
application
and
a
javascript
application
is
just
like
a
web
app
right.
So
we
now
have
web
apps
that
have
compiled
smart
contracts
inside
of
them,
and
so
they
can
send
those
around.
You
know
you
could
request.
B
B
Web
and
ethereum,
which
is
super
cool,
and
I'm
wondering
in
here,
if
we
have
sometimes
when
this
stuff
gets
compiled,
we
can
probably
actually
find
the
abis.
I
can
show
you
what
they
look
like,
but
right
now
so
remember,
we
ran
yarn
and
this
installed
all
of
our
dependencies,
which
we
would
see
in
this
new
directory
called
node
modules,
and
so
these
are
all
of
our
javascript
dependencies
and
also
like
solidity.
B
You
know,
I
think
solidity
package
managers
use
the
same
approach.
We
install
things
with
this
as
a
node
module,
so
these
are
all
of
our
dependencies
that
the
we
just
grabbed
by
running
this
yarn
command.
So
I'm
gonna
add
that
to
the
readme
everything
in
the
readme
so
far
that
we
see
here
is
just
a
default
from
scaffold
eath.
B
So,
let's
start
adding
our
own
tec
documentation
here,
so
oops
go
full
screen.
B
So
this
is
like
token
engineering,
commons,
hatch
template.
B
Swarm
common
swarm,
hatch
template
and
then
we
can
say
how
to
run
locally.
B
Okay,
so
first
clone
this.
B
B
B
Chain,
so
this
is
using
the
hard
hat
framework,
which
is
an
ethereum
development
environment
and
it's
going
to
run
a
local
chain,
a
local
ethereum
chain,
and
then
it
actually
compiles
all
the
contracts
and
deploys
them
to
the
local
chain,
and
so
now
we're
hosting
an
ethereum
blockchain.
At
this
address,.
B
So
for
anyone
who
doesn't
know
or
doesn't
recognize
this
ip
address,
this
is
a
super
special
unique
ip
address.
It's
called
the
loopback
address
and
it's
the
same
on
every
computer
and
it's
it
means
if
you
try
to
access
this
ip
address
on
the
internet.
It
takes
your
request
and
it
loops
it
back
to
your
own
computer.
B
So,
and
you
can
also
substitute
this
for
a
word,
the
keyword
is
localhost.
All
one
word
localhost,
so
this
is
this
is
when
you
run
like
web
services
on
your
own
computer
this.
So
this
ip
address
allows
you
to
access
them.
So
right
now
on
our
own
computer,
we're
running
our
ethereum
node
at
this
port
port
8545.
B
So
any
system
or
program
now
that
we
run
locally
can
make
ethereum
like
this
is
an
ethereum
node
running.
So,
however,
we
typically
interface
with
an
ethereum
node
and
the
way
we
do
that
is
through
the
json
rpc.
That's
like
a
protocol.
B
We
can
now
hit
this
and
like
deploy
contracts
to
it
or
make
transactions
all
sorts
of
stuff.
So
we
have
a
test
chain
running
and
the
contracts
are
deployed.
Now
it
looks
like
a
bunch
of
like
warnings
here.
You
know,
I'm
not
sure
what
all
this
is.
B
Let's
see
where
it
starts,
so
it
says
compiling
80
files
and
then
it
has
warning
defining
constructors
as
functions
with
the
same
name
as
the
contract
is
deprecated
use
a
constructor
instead.
So
it
looks
like
in
all
of
these
aragon
contracts
that
we're
importing-
probably
they
were
written
a
few
years
ago
and
they
use
some
outdated
standards,
particularly
this
one
is
naming.
Oh,
this
is
mini
me
token.
We
should
blame
griff.
B
A
B
Yeah
mini
me
token
was
a
great
invention.
It
allows
it's
essentially
the
snapshot.
I
think
nowadays,
there's
snapshot,
which
is
kind
of
a
newer
thing,
but
mini
me
token
allows
like
the
double
the
duplication
of
a
token
so
that
we
can
track
exactly
which
wallets
have
what
accounts
at
a
certain
moment
in
time
and
then
from
there.
It
enables
things
like
governance.
We
can
do
voting
or
just
general
snapshotting,
and
how
is
it
being?
Is
that
right,
griff
or
do
you
want
to
comment
on
that?
A
little
bit.
A
Yeah
I
mean
the
main
thing
is
that
it's
an
upgradable
token
a
really
easily
upgradable
token,
and
it
was
from
the
dao
experience
like
it
was
made
specifically
for
dallas,
so
that
you
could
do
voting
like
where
you
can
easily
snapshot,
and
then
the
people
who
had
tokens
at
the
time
of
the
vote
could
vote,
but
not
people
who
get
tokens
later
and
it
doesn't
lock
your
tokens.
There
was
just
a
lot
of
from
the
first
dow.
A
There
was
a
lot
of
lessons
learned
and
we
integrated
them
into
the
mini
me
token
contract
and
it
ended
up
being
used
by
aragon,
status,
storm
city
and
a
bloom
and
a
whole
bunch
of
other
groups,
and
it's
still
in
use
today
with
one
hive.
Honey
is
a
mini
me.
Anything
that
interacts
with
the
aragon.
Dials
is
a
mini
me
token.
B
Cool
super
cool
stuff,
so
yeah
a
bunch
of
warnings,
but
don't
let
these
scare
you
in
our
let's
see
in
our
hatch
template
we
have
function.
State
mutability
can
be
restricted
to
view
okay.
So
these
these,
we
might
actually
want
to
pay
attention
to
here's
a
few
opportunities
in
the
hatch
template
we
might
want
to
go
through
these.
This
is
an
opportunity
and
I
don't
know
exactly
like.
B
I
would
I'm
not
the
expert
here,
there's
some
devs
like
sam,
who
are
like
working
on
this
really
building
this
stuff
and
have
mastery,
but
these
kinds
of
warnings
might
come
up
like
if
we
do
the
hatch
freeze
and
we
well,
we
might
want
to
just
at
least
check
all
these
warnings
before
we
freeze
the
templates
and
submit
them.
B
This
could
be
something
sometimes
a
warning
is
indicating
some
sort
of
like
misuse
or
things
could
be
tightened
up
like
this
says
this
function
get
stored,
address
transaction
one,
it
could
be
a
view
function
and
I
think,
by
making
this
a
view
function,
it
means
it's
read
only
and
it
could
potentially
have
a
speed
up
in
performance
if
this
is
labeled.
As
a
view
function,
so
there's
it's
nice
to
see
that
there's
a
few
there's
only
three
warnings
on
the
hatch
template.
So
that's
actually
pretty
good.
B
B
B
B
B
B
B
B
B
B
Argument
of
type
string
yeah,
it's
just
this
little
simple
error:
it's
ext
expecting
a
string
and
we're
passing
like
not
a
string.
Some
sort
of
log
object,
so
I
think
I'm
going
to
commit
that
change
so
that
the
tests
run,
and
I'm
also
going
to
finish
the
documentation
that
I
was
adding
to
the
readme.
B
Thirdly,
run
the
tests
run
the
tests
with
the
specified
network.
B
B
B
B
The
the
yarn
lock
file
just
keeps
it's
it's
a
way
of
locking
in
all
of
the
dependency
like
the
versions
of
all
the
dependencies
that
we
use.
I'm
not
gonna
mess
with
that,
because
it
could
potentially
break
something
like
the
development
team
might
have
all
of
their
dependencies
locked
in
in
a
way
that
it
for
sure
works.
I
mean
it
would
probably
be
safe
to
add
this
because
the
tests
did
pass.
B
So
if
we
have
a
comprehensive
testing
suite
and
the
tests
are
all
passing,
then
it
seems
like
the
dependencies
that
we've
installed
this
time
all
work.
But
I
think
we
have
it's
good
that
we
have
tests,
but
I
don't
know
to
what
extent
it's
fully
comprehensive
and
I
wouldn't
want
to
accidentally
break
something
that
the
development
team
has
locked
in
place.
So
I'm
not
going
to
add
that
yarn
lock
file,
but
I'm
going
to
go.
Get
ad
on
the
read
me
and
get
ad
on
the
test
that
we
updated.
B
But
before
I
do
that,
I
think
I'll
go
well
yeah.
I
can
do
that.
Sorry.
What
is
that?
Oh,
oh
I
I
typed
git,
add
twice.
B
B
Good
now
I
can
commit
so
so
we
have
our
two
files
ready
for
commit.
So
I
can
say
git
commit
and
add
a
message
started:
tec,
custom,
documentation.
B
Sweet
so
we've
made
that
commit,
and
now
we
can
make
a
pull
request,
so
I
should
be
able
to
go.
B
I
should
be
able
to
push
this
branch,
so
we
can
check
our
with
this
command
get
remote
dash
v.
It
reminds
us
like
what
repository
we're
working
on
so
we're
working
on
github.com,
common,
swarm,
hatch,
template,
okay,
that
looks
good
so
and
the
name
of
that
remote
is
called
origin.
So
we
go
get
push
to
origin
and
our
branch
is
called
documentation
and
tests.
B
It
says
permission
denied.
Okay,
I
don't
think
I
have
org
access
to
the
common
swarm.
B
B
Financial,
okay,
so
now
I
have
my
own
fork
right
so
now
I
can
do
whatever
I
want
here.
No
one
can
stop
me
the
beauty
of
open
source,
and
so
now
I'm
going
to
work
off
of
this
fork.
B
B
Okay,
so
it
says
yep
success
and
if
you
want
to
open
a
pull
request
go
here,
so
we
see
now
on
this
long
tail
financial
fork.
It
says
we
have
recent
pushes
on
a
different
branch.
B
B
This
has
all
the
information
we
need.
It's
just
a
single
commit.
It
should
be
easy
to
review.
Maybe
I'll,
just
clean
this
up
a
little
bit.
B
It
expected
a
string,
so
please
review
that
section
and
we
might
want
to
expand
the
features
or
documentation
on
that
logging
process
because
it
looked
like
there
was
a
log
for
anyone
who's
not
familiar.
What
is
this
log
thing?
A
log
is
just
an
object
that
you
can
say
things
to
it
and
it's
gonna
take
take
those
messages
and
store
them
in
places
that
we
want
to
keep
them
or
it's
going
to
display
them
to
the
screen.
B
So
when
we
run
the
tests,
we
might
want
to
like
log
a
whole
bunch
of
information
about
what's
happening
and
so
that
log
that
was
trying
to
get
passed
into
the
test
is
it.
I
actually
saw
this
in
the
code
earlier.
It
has.
Actually,
I
think
all
it
does
is
it
adds
some
pretty.
It
makes
the
output
more
pretty.
B
B
B
Which
will
update
the
documentation
so
that
everyone
can
run
the
tests
and
in
fact
we
might
want
to
take
this
moment,
we
could
go
into
the
migration
tools
as
well.
It
would
be
a
very
similar
process,
but
I
would
actually
like
to
invite
everyone
to
see
to
try
to
replicate
this
process
and
see
if
we
can
all
run
the
the
contracts
locally.
It
should
work.
B
B
B
And
now,
if
we
go
to
long
tail
financial
on
the
master
branch,
we
should
see
the
documentation.
Yes,
except
it's
kind
of
it's
not
it
could
be
formatted
much
nicer,
so
I'm
just
gonna
make
a,
and
this
will
hopefully
be
caught
by
the
common
swarm
team.
B
A
A
A
The
first
test
works,
it's
doing
fine,
but
the
next.
B
A
B
B
B
B
B
Do
you
see
anywhere
where
it
just
says,
error
error
here
a
vm
exception,
while
processing
transaction
revert
error
impact
hours
not
fully
claimed
impact
hours,
not
fully
claimed,
let's
jump
into
the
code
and
see
where
this
is
triggering
so
hatchflow
when
max
goal
is
reached,
closes
the
contracts,
yeah
jump
to
the
code
and
search
for
closes
the.
A
Here
sorry,
I'm
gonna
increase
the
size.
B
B
A
Yes,
yes,
yes,
yes,
yes,
hold
on
it's
about
configuring.
The.
A
B
A
A
A
B
So
maybe
what
we
can
do,
this
is
cool.
We've
got
you
right
here
in
the
sort
of
debugging
workflow,
but
since
we're
getting
short
on
time,
why
don't
you.
A
A
A
B
B
Yeah,
looking
forward
to
seeing
the
issue
that
you
post
there
bart
because
I'll
be
able
to
read
all
through
all
of
it
and
we
can
probably
get
some
insights
from
the
dev
team
as
well
on
there
great
yeah,
maybe
just
post
a
link
to
the
issue.
Once
you
create
it
post
a
link,
just
drop
the
link
in
the
labs
channel.
A
Yeah
thanks
guys
today
was
a
very
nice
from
zero
to
a
thousand
session,
so
it
was
nice
to
follow.
Thank
you.
Awesome.
B
Yep,
cool
okay.
So
it's
andy
right.
B
Yes
really
appreciate
you
being
so
active
in
the
labs
that
helps
a
lot.
Oh,
hey,
niko,
hey.
A
B
No
yeah
we're
just
wrapping
up.
I
was
just
gonna
say
for
whoever's
left
on
the
call
here,
so
the
labs
are
taking
a
new
format
as
of
next
week.
Blair
is
gonna,
be
championing,
like
a
cad
cad
collaborative
study
series
for
like
six
weeks
and
there's
going
to
be
some
capstone
projects
at
the
end,
it'll
be
kind
of
similar
to
what
is
happening
in
the
git
coin.
B
Research
track
now,
but
a
lot
more
like
introductory
and
basic
level
it'll
be
study
sessions
for
like
six
weeks,
and
then
everyone
will
kind
of
work
on
some
projects
and
do
some
presentations
so
tonga,
you
might
be.
You
might
be
really
interested
to
follow
along
on
that
yeah
everyone
here.
Probably
we
could.
We
could
help
out
a
lot
so.
C
C
B
C
Yeah
because
we
use
metamask
to
relate
like
most
people,
there
is
other
wallets,
but
most
people
use
metamask.
So
it
can
happen.
B
B
C
Yeah,
luckily,
I
never
had
much
money
there,
but
I
hadn't
even
realized
that
was
happening,
but
I
I
always
had
zero
heater
in
metamask
and
I
thought
because
okay,
I
never
put
money
here
but
looking
at
the
history,
even
in
in
more
than
one
address
like
I
have
like
seven
addresses
and
at
least
in
two
of
them
it's
it's
happening
and
it
happened
last
year
I
didn't
realize
so
it's
like
it's
been
like
three
or
four
like
between
fifty
and
a
hundred
dollars
and
hacks,
like
it's
a
script
that
it's
detecting
whenever
anything
comes
in
and
it
pays
pays
the
highest
fee.
C
B
C
B
C
A
Happened
to
me
with
a
account
in
metamask
connected
to
ledger,
so
I
don't
know
what
I
think
I
approved
a
contract
of
a
scammer
and
I
don't
know
how
to
get
rid
of
this
approval.
So
yeah.