►
From YouTube: Filecoin Dev Demo 03 - go-filecoin & Testnet Simulator
Description
go-filecoin & testnet simulator demo
A
In
this
demo
will
show
a
local
test
network
with
many
falcon
nodes
and
a
simulator
issuing
a
number
of
actions
randomly
to
run
this
we'll
use
gopal
coin
and
a
test
line
simulator
tool.
Note
everything
we
are
showing
here
is
still
in
development
and
very
much
subject
to
change,
especially
the
naming
or
arranging
of
commands
on
the
right.
We
can
see
the
help
text
of
the
goal
falcon
program
on
the
left.
We
can
see
the
help
text
of
our
test
net
simulator.
A
This
is
a
program
that
creates
a
network
ads
falcon
nodes
with
a
roll
miner,
a
client
and
then
automatically
runs
through
many
kinds
of
actions
sending
payments,
adding
market
orders
storing
files.
We
can
configure
the
simulator
to
set
the
size
of
the
network
block
times
and
other
durations
the
actions
to
issue
and
more.
It
allows
other
test
programs
to
issue
commands
and
even
manual
user
input,
it's
useful
for
debugging
for
testing
and
for
demoing
flatpoint.
Let's
run
it
with
default
settings,
it
out
put
some
links,
its
configuration
and
starts
up.
A
It
is
now
spawning
Falcon
notes,
according
to
configuration
and
issuing
commands
to
run
randomly
chosen
actions
below.
We
can
see
the
Gopalan
processes
running
on
this
computer
go
Falcon,
daemons
are
the
individual
notes.
The
ephemeral
go
Falcon
processes
issue
commands
to
the
knows.
The
message
wait
command
is
used
to
wait
until
a
particular
transaction
is
mined
into
a
walk.
A
The
logs
endpoint
aggregates
the
event
logs
of
all
the
Paco
nodes
in
the
network.
This
is
all
the
activity
in
the
network.
We
can
filter
it,
the
familiar
tools
like
grep
and
Jake
you
and
we
can
use
it
to
drive
visualizations
more.
On
that
later,
we
can
also
inspect
the
running
pond
processes
and
issue
commands
to
each
of
the
notes
manually.
Let's
try
one
out.
We
can
get
information
about
the
node
like
the
peer-to-peer
connections.
A
You,
the
message
pool
and
so
on.
We
can
also
send
transactions
manually,
which
we'll
see,
in
other
demos,
quitting
the
simulator
will
shut
down
all
the
four
notes.
Cleanly
the
local
repositories
are
left
in
temporary
directories
so
that
its
internal
data
and
its
logs
can
be
inspected
manually.
This
is
useful
for
continuous
integration
tests
and
debugging.