►
From YouTube: Lotus client inspect deal command
Description
Anton demonstrates a new Lotus command "inspect-deal" for showing information about about any Filecoin deal.
A
Yeah
hi
everyone.
Let
me
share
my
screen
and
talk
a
little
bit
about
yeah
what
we've
been
working
on.
So
yes,
basically,
we
have
worked
on
inspect
this
command,
which
looks
something
like
this
at
the
moment.
So
let
me
explain
what
this
is
about.
The
idea
is
that
we
wanted
basically
to
propagate
more
inspection
yeah.
A
We
wanted
to
basically
propagate
more
information
about
deals
and
actually
record
their
life
cycle
in
terms
of
seeing
the
history
of
the
different
stages
that
I
do
went
through,
as
well
as
the
different
stages
that
a
data
transfer
attached
to
a
given
deal
went
through
so
that
we
can
understand
a
little
bit
better
at
what
stages.
For
example,
there
are
problems
with
the
deal
because,
as
all
of
you
know,
these
are
somewhat
flaky
at
the
moment
and
a
lot
of
times
they
fail.
A
A
The
reason
that
you
can
query
them
by
both
is
because
duid
is
zero
before
the
deal
ends
on
chain
and
you
might
be
interested
to
know
what
happened
with
the
deal
if,
for
some
reason,
something
fails
within
the
stages
before
the
deal
actually
hits
the
chain
which
happens
around
this
stage
here,
basically
at
stage
check
for
acceptance,
the
provider
submits
the
d1
chain
and
we
wait
for
a
confirmation,
and
at
this
stage
we
basically
have
a
duide
right.
So
here
we
can
now
see
all
the
different
stages
that
you
went
through.
A
Basically,
the
client,
reserving
funds
opening
of
the
data
transfer
to
the
storage
provider.
The
different
stages
within
the
data
transfer
checking
that
the
provider
actually
accepts
the
deal
and
publishes
it
on
chain
are
waiting
for
pre-commit
message
ceiling
and
the
last
one
where
we
see
that
deal
was
activated
and
this
coating
took
like
four
or
five
minutes,
because
this
is
a
devnet
with
the
2k
sectors
right.
So
let
me
quickly
create
a
new
deal
just
for
for
illustration
purposes.
A
I'm
gonna
create,
let's
say
a
deal
with
some
other
data
on
it.
I've
already
created
the
wallet.
So
if
we
say
load
us
wallet
list
yeah,
we
see
that
I
have
a
default
wallet
with
some
view
in
it,
and
I'm
gonna
create
a
doc
data,
cid,
basically
importing
the
data
and
creating
importing
the
data
into
lotus
and
then
creating
the
proposal.
Cid
right
and
this
should
I've
called
it
dlcid
in
my
notes.
But
this
is
actually
a
proposal
city,
that's
how
it
is
known
into
lotus.
A
Cid
with
this
the
id-
and
we
see
that
it's
actually
already
at
the
stage
where
we're
checking
for
your
acceptance
waiting
for
the
provider
to
publish
the
d1
chain
and
due
to
the
defaults
of
lotus
at
the
moment
there
is
a
delay.
I
mean
providers,
do
not
immediately
like
publish
deals
so
the
due
depending
for
publishing.
A
I
think
there
is
like
a
one
hour,
yeah
published
period,
we're
waiting
for
more
deals
to
come,
because
this
is
a
very
small
deal
and
miners
want
to
collect
a
bunch
of
deals
together
before
they
actually
publish
them.
So
I'm
just
gonna
go
ahead
and
publish
this
one
specifically,
which
triggered
the
publishing,
and
we
can
see
that
the
provider
has
now
published
the
deal
on
chain
and
we're
waiting
for
confirmation
and
we're
going
to
get
into
the
further
stages.
Yeah
time
passes.
A
So
the
idea
is
that
we
are
going
to
collect
all
relevant
error
messages
and
we're
going
to
see
how
long
do
you
stay
in
various
stages
and
basically
provide
a
bit
more
information
about
the
life
cycle
of
a
deal
for
users.
This
is
still
not
complete.
Ideally,
we
should
have
even
more
data
like
we
should
be
able
to
see
that
there
are
more
stages
upcoming
at
the
moment.
This
is
not
visible
on
my
screen.
A
A
B
A
I
actually
have
a
minor
here
in
my
local
network,
so
I'm
first
going
to
try
that
and
introduce
some
failures
with
it,
and
I
haven't
thought
about
actually
testing
it
with
other
miners.
Considering
that
I
have
have
yeah
a
local
miner
that
I
can
queue
and
restart
by
myself,
but
we
could
totally
test
it
with
other
folks
as
well.
Yeah.
B
A
C
Another
another
thing
worth
mentioning
here
is
that
the
this
is
backed
by
changes
in
the
json
rbc
api
as
well.
So
what
we
plan
is
for
the
deal
bot
that
that
a
bunch
of
us
are
about
ac
and
and
my
girls
are
working
on,
we
plan
to
capture
the
deal
stages
and
the
timeline
of
the
deal
in
the
data
point,
so
that
for
deals
that
went
wrong,
we
we
have
the
entire
trace
to
go
back
and
analyze
and
debug
what
went
wrong.
B
B
A
Dirk
went
through
the
gold
data
transfer
recently
and
he
fixed
a
couple
of
books
and
I've
seen
that
we
propagate
more
error
messages,
so
we're
at
the
stage
where
now
we're
going
to
start
seeing
those-
and
hopefully
they
make
more
sense
than
the
information
that
we've
currently
had
so
yeah.
We
do
propagate
now
a
bit
more
error
messages
within
those
stages.