►
From YouTube: Data Platform Community Meeting (Jul '22)
Description
This week we discuss tools available to get data from NEAR, our new Lake Framework for Python, and listen to feedback & requests on the Enhanced API!
NEAR's indexer ecosystem:
👉 https://near-indexers.io/docs/intro
Dev Console Survey:
👉 https://docs.google.com/forms/d/e/1FAIpQLScjF-gIAZV_gNp64eKrUrZVI29xHu6qVhnJ2XzVX2AC28HqcQ/viewform
Lake Frameworks Available:
👉 https://github.com/near/near-lake-framework-rs
👉 https://github.com/near/near-lake-framework-js
👉 https://github.com/frolvanya/near-lake-framework-py
Ask NEAR Indexer Questions in StackOverflow!:
👉 https://stackoverflow.com/questions/tagged/nearprotocol+indexer
Join NEAR's community:
Website: https://near.org/
Reddit: https://www.reddit.com/r/nearprotocol/
Discord: https://near.chat/
Medium: https://medium.com/nearprotocol
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
Dev Docs: https://docs.near.org/
Create a wallet: https://wallet.near.org/create
Apps on NEAR: https://awesomenear.com/
Learn to Build On NEAR: https://www.near.university/
Grants & Funding: https://near.org/grants/
#Blockchain #FutureisNEAR #NEAR #nearprotocol
#nft #dao
A
B
A
Data
platform
community
meeting
I'm
joined
with
vlad
and
tiffany
from
pagoda
they're
going
to
go
over
data
data
platform.
Things
we're
gonna,
we're
gonna,
be
talking
about
just
kind
of
recap
and
why
indexes
aren't
important.
The
relationship
between
between
the
index
or
framework
and
like
framework
also
gonna,
be
chatting
about
lake
framework
for
python
and
also
go
over
more
of
the
enhanced
api
features
that
we
kind
of
discussed
a
little
bit
last
time.
So
yeah.
A
Thanks
everyone
tune
in
next
time,
yeah
if
yeah,
again
same
format.
As
always,
if
you're
new
just
drop
a
question
in
chat,
drop
or
or
the
q
a,
we
actually
prefer
the
q
a
button.
But
if
you
don't
understand,
that's
fine
too,
but
yeah
drop
a
question
at
any
point
in
time
and
we'll
answer
them
either
as
they
come
or
we'll
find
a
moment
to
to
answer
it
during
the
presentation
or
afterwards
so
yeah
tiffany.
B
So
yeah,
so
like
what
josh
mentioned,
we
have
a
couple
of
items.
The
only
one
that
was
added
basically,
is
the
alerts
demo
and
we
actually
just
released
the
alerts
internally
with
a
couple
of
the
add-on
feature
from
the
last
demo.
So
you
know
looking
forward
to
that
and
without
further
ado
I'll
pass
to
mike
to
fro
to
discuss
more
on
indexers.
C
Yeah,
hey
everybody.
I
hope
you
haven't
forgot
about
the
indexers,
but
for
those
who
are
just
new
to
the
ecosystem,
I
decided
to
actually
remind
everybody
where
we
are
standing
and
what
is
the
indexer
and
thanks
for
a
question
in
the
chat
I
saw
what
indexer
is.
So
it's
a
right
time
to
answer
this
question
once
again
and
you
can
find
all
the
dogs.
I
love
the
dogs,
they
they're
very.
C
C
Isolated
environment
and
it
doesn't
want
to
share
their
data,
it
actually
doesn't
need
to
do
it.
So
the
only
purpose
of
the
blockchain
is
that
is
to
actually
proceed
with
decentralized
consensus
being
done
and
moving
forward
from
like
block
to
block,
including
some
changes
from
different
parties
and
arriving
to
the
next
and
like
iteration
of
the
data
view.
C
So
all
the
ecosystem
is
on
the
same
page.
Basically
and
indexers
are
the
tools
that
and
like
approach
or
like
ideas.
That,
basically,
is
it's
very
simple.
You
just
need
to
know
what
those
changes
are
and
the
blockchain
itself
is
not
very
friendly
to
do
so.
So
we
actually
started
like
when
we
were
facing
this
problem
as
a
explorer
team.
Initially,
we
needed
some
way
to
record
all
the
changes
in
the
blockchain
into
our
positive
database
in
order
to
then
efficiently
serve
them
through
explore
ui.
C
People
refer
to
some
specific
indexer
that
was
implemented
with
a
tooling.
That
does
something
so
on
the
tooling
side
we
have.
We
currently
have
basically
two
of
them.
It's
the
index
of
framework
and,
like
framework,
I
will
dive
into
details
a
little
bit
in
the
next
slide,
but
for
now,
let's
just
remember
those
and
go
through
the
various
implementations.
I
just
want
to
highlight
a
few
that,
by
by
this
time,
we
have
probably
a
couple
of
dozens
of
indexers
that
I
I'm
aware
of.
C
I
decided
to
start
with
some
like
very,
very
old
ones,
so
near
index
f4
explorer
was
pro
like
was
the
second
indexer
that
we
built
the
ver.
Actually,
it
was
third,
but
the
the
very
first
for
explorer
was
not
really
like
a
proper
indexer.
I
would
say
it
was
very
hacky
solution
there,
so
the
very
first
indexer
was
actually
for
wallet
with
the
from
there.
We
actually
iterated
and
implement
the
whole
excerpt
for
explorer
for
all
the
needs
to
have
all
the
data
in
the
blockchain
dumped
into
the
positive
database.
C
And
the
from
there
once
we
tested
it
ourselves,
we
were
happy
to
actually
share
our
tooling
in
the
form
of
indexer
framework
and
the
very
first
community
implementation
was
flux
capacitor
at
least
from
what
I
know,
and
they
built
the
the
indexer
that
allows
you
to
selectively
put
some
of
the
blockchain
events
into
mongodb
and
then
run
from
there.
So
it
was
powering
mint
base
and
a
few
other
solutions
over
there.
C
Specifically,
so
we
require
a
near
coordinate,
requires
ssd
performance,
storage
and
a
lot
of
that.
So
if
you
want
to
have
something
like
all
blockchain
data
indexed,
you
need
archival
node
data
on
your
server
and
it's
terabytes
of
that
in
sitting
on
cd.
So
without
further
ado,
we
actually
implemented
this
near
lake
index
server,
which
is
very
simple
idea.
We
put
all
the
blockchain
data
that
we
collected
through
indexer
framework
to
a
s3,
aws,
s3
solution,
and
from
that
point
there
was
a
whole
family
of
new
indexers
based
on
display
framework.
C
We
call
them
just
near
index
near
dash
indexer
dash
something
on
our
github,
so
you
can
find
at
least
six
implementations
by
this
time,
which
do
like
index
events,
account
balances,
ft's
and
stuff
like
that.
Basically,
so,
let's
switch
to
the
third
slide
at
the
next
slide,
and
I
will
I'd
like
to
give
you
a
comparison
of
like
how
things
actually
fit
together.
C
So
both
of
the
approaches
of
index
framework
and
late
framework.
Allow
allows
you
but
like
the
basic
baseline,
is
to
actually
follow
all
the
blocks
and
transactions
in
your
protocol.
So
that's
strong!
Yes,
on
both
sides,
though
late
framework,
is
a
centralized
solution,
as
you
can
see
from
the
second
line,
which
affects
the
the
fact
that
you
basically
either
need
to
run
your
own
la
lake
indexer,
which
is
open
source,
and
you
do
do
so,
just
just
fine.
C
Also
is
amendments
for
the
indexer
framework.
You
need
to
follow
all
the
near
core
releases.
We
had
a
new
release
just
today
and
by
monday
you,
you
gotta,
be
updated
on.
If
you
run
indexer
framework
on
mainnet
on
the
lake
side,
you
don't
need
to
do
anything
like.
If
you
have
your
indexer
running,
it
will
just
run
just
fine
for
you,
because
we
will
update
our
indexer
like.
C
Implementation
which
dumps
all
the
data
onto
s3
and
all
the
like
upgrades,
will
be
just
zero
down
time
and
like
no
done
time
at
all,
but
and
then,
when
it
comes
to
starring,
you
note
your
indexer
it
or
is
such
a
good
strap
in
it.
It
takes
you
days
to
sync
with
magnet
and
test
net,
sometimes
on
the
leg
side,
you
just
spawn
it
and
it's
immediately
there.
It
reads
the
data
from
s3
storage.
C
Local
development
is
also
cannot
be
easier
than
it
is
with
lake,
because
you
can
run
the
nose.
You
don't
need
heavy
heavy
hardware
requirements
as
the
near
core
has,
however,
for
localnet
indexer
framework
is
totally
fine.
It's
it's
not
like
the
the
empty
near
network
is
super
lightweight,
and
it's
not
that
hard
to
do.
But
if
you
depend
on
some
network
state,
that
would
be
a
bit
challenging
and
well
the
the
requirement
that
indexer
framework
imposes
to
you
on
you
being
the
solution
based
on
top
of
near
core.
C
Is
that
it's
only
available
in
rust,
which
we
love,
but
we
saw
that
as
a
limitation
for
some
people.
So
if
you
are
into
using
python
javascript
or
any
other
programming
language,
you
would
be
out
of
luck
with
inductive
framework
sort
of
by
design
and
while
on
the
lake
framework
side,
your
by
design
can
use
any
programming
language
which
can
do
http
calls,
because
you
just
need
to
communicate
over
http
with
this
s3
buckets.
C
So-
and
this
is
a
teaser
over
here,
you
or
well
joshua
is
followed,
but
we
never
talked
previously
about
python
implementation
of
lake
framework.
But
actually
that's
what
we
want
to
mention
today
that
we
have
the
implementation
sitting
there.
It's
even
published
on
pi
pi,
and
you
can
run
with
it.
We
are
still
testing
it
and,
like
fixing
some
potential
bugs,
we
are
not
aware
of
any
yet
we.
C
C
Yeah
and
we
encourage
the
community
to
build
other
link
frameworks,
so
I
I
can
only
say
that
it's
just
a
couple
of
well
not
a
couple
of
hundreds,
but
maybe
a
thousand
of
lines
of
code,
basically
that
javascript
and
python
implementation
took
to
get
us
there.
So
you
can
contribute
your
own
implementation
to
the
community
of
lake
frameworks
and
maintain
it.
C
C
We
have
tutorials
on
our
indexer
or
near
indexers.io
website,
so
you
can
find
nft
tutorial
in
javascript
and
python.
We
actually
don't
have
one
interest
yet
because
we
believe
we
have
other
tutorials
in
rust
that
just
similar,
so
we
can
find
all
the
tutorials
on
the
website
and
yeah.
It's
it's.
Those
will
be
just
as
familiar
as
the
previous
like
frameworks,
if
you've
seen
them
cool.
I
think
that's
all
from
the
lick
from
the
indexers
landscape
and
I
I
like
to
pass
the
word
to
tiffany.
B
B
A
A
C
C
Yeah
sure
so
the
the
the
major
cost
there
is
from
a
double
ss3
storage.
So
we
configured
our
buckets
in
the
way
that
the
requester
pays
for
the
usage
and
the
in
order
to
listen
to
all
the
blocks
that
are
coming
so
that
they
are
stored
on
s3.
We
estimated
how
much
get
requests
get
object,
requests
and
how
much
list
objects
requests.
We
would
need
to
serve
two
s3
from
a
three
and
our
estimate
is
it's
20
bucks.
You
can
find
all
the
details
in
in
the
readme.
C
There
is
like
a
very
nice
breakdown
and
the
from
the
terms
of
the
node
requirement,
like
the
actual
instance
that
would
run
your
in
your
indexer.
You
can
even
use
some
free
instances
out
there,
which
are
like
less
than
500
megabytes
of
ram
and
share
cpu
power.
That
would
be
just
fine
and
just
enough
for
rig
like
to
follow
the
network.
A
C
Oh
yeah,
so
the
the
future
direction
graduates
towards
that.
We
will
actually
repackage
that
into
pagoda,
dev
console
and
we
will
reduce
the
cost
even
further
and
the
billing
will
go
through
the
console
and
it's
probably
gonna
be
much
cheaper
because
the
ecosystem
will
grow
and
reuse
the
same
resources.
So
we
will
need
to
hit
aws
as
much
and
we
will
cut
a
lot
of
costs
on
on
the
shared
resource.
Basically,
yeah.
B
One
quick
question
I
have
on
that,
actually
is
we
we
are
discussing.
You
know
enable
payment
with
usn
with
within
the
teams,
and
one
question
I
have
is
you
know,
because
enabling
recurring
payment
with
crypto
is
like
a
very
unsolved
question
within
industry,
and
sometimes
you
know,
maybe
people
don't
really
like
having
recurring
payment
with
crypto
with
access
key
and
all
of
that.
So
just
a
quick
like
feedback.
B
A
B
B
You
need
to
go
on
s3
and
you
know
pay
there,
and
and
all
of
that,
so
we're
we're
actually
hoping
to
making
that
process
easier
with
a
whole
pagoda
or
like
in
your
account
on
dev
console
and
enable
everything
from
there,
and
you
can
manage
your
billing
or
all
the
services
that
you
interact
with
the
pagoda
products
there
and
we're
planning
on
offering
you
know
even
like
a
better
pricing
for
it.
So
it
should
be
even
cheaper
and
you
know
we
hope
to
enable
crypto
payment
like
usn.
B
A
C
C
But
the
the
idea
is
basically
that
we
can
provide
much
better,
tooling
and
even
cost
efficient
solutions,
so
I
think
it
I
like
it.
It
will
just
eventually
converge
to
the
using
pagoda
instead
of
direct
aws
access
would
be
just
better.
Basically,
in
all
aspects,
we
can
provide
you
with
some
monitoring.
C
A
B
Yes,
okay.
Moving
on
to
the
next
slide,
which
is
the
next
topic,
is
the
api
landscape.
So
some
conversations
we've
been
having
is
you
know?
There's
too
many
places
you
can,
you
know,
interact
or
consume
primitive
data
from
the
blockchain,
and
there
are
a
lot
of.
There
are
a
lot
of
things
that
we
would
hope
our
rpc
calls
will
be
able
to
achieve,
or
you
know
just
make
everything
easier
or
better
or,
like
you
know,
easy
to
consume
or
interact.
So
we
create.
B
So
it's
going
to
be
something
like
api
pagoda,
testnet
or
maynet,
we'll
release
that
name
once
we
really
figure
our
finalize,
but
it
should
be
one
endpoint
that
enables
access
to
all
of
this
and
we're
actually
working
on
together
with
ro
here
also
to
provide
to
to
unify
our
regular
pc
and
our
cover
our
pc
access.
So
you
don't
no
longer
need
to.
You
know
have
like
oh,
like
this
five
app
hogs
I
poke
here
and
after
that
you
know
for
prior
and
all
you
know,
history
data.
B
Without
you
know,
the
extra
custom
work
that
needs
to
be
done
and
for
the
future
batches
we
are
going
to
offer
like
I
mentioned
the
price
apis
and
combined
price
with
you
know,
guest
spend
with
like
transaction
value
and
a
lot
of
those
to
give
you
even
more
and
better
information
on
the
amount
you
spend
and
then
we'll
we'll
also
want
to
have
more
detail
breakdown
on
account
and
contract
states.
So
you
know
right
now:
there
returns
a
lot
of
a
huge
strain
from
the
rpc
call
on
accounts
and
contract
state.
B
B
Given
the
long
history
of
our
blockchain
amount
of
data,
there
needs
to
be
some
sort
of
creative
solution,
but
that
is
definitely
in
discussion
and
we
we
definitely
understand
that
this
is
a
very
important
idea
to
need
from
the
community
and
we
also
is
planning
on
we're,
also
planning
on
supporting
logs
or
traces.
So
it's
helped
you,
you
know
easier
debug
and
we
are
thinking
if
it
can
be.
B
You
know
connected
to
other
tools
or
calls
to
to
make
that
you
know
the
whole
unified
debugging
process
easier
for
for
you
all
so
yeah,
that's
the
plan
for
enhanced
api.
We
really
welcome
more
suggestions
or,
like
you
know,
or
helping
us
prioritize
what
to
support
next.
It's
a
it's
a
lot
that
we
want
to
work
on.
I
want
to
provide
so
really
welcome
all
the
feedbacks
that
we
can
get
from
this,
and
I
see
a
question
in
the
chat.
B
B
B
Yeah,
so
so
that
is,
that
is
a
that's
like
not
really
for
super
api
as
a
price,
but
we
do
have
a
plan
to
start
monetize
on
on
this
front,
but
we'll
start
with
the
regular
rpc,
and
you
know
the
rpc
yeah,
it's
a
spoiler
alert.
So
rpc
is
it's.
I
think
a
couple
of
people
probably
already
know-
and
you
know
we're
we're
half-
that
we
have
to
plan
to
gradually.
B
B
B
You
know
what
yeah
for
anyone
who
don't
have
a
pagoda
account.
It
should
be
very
easy
to
I'm
just
going
to
log
out
and
redo
it.
So
am
I
sharing
I'm
still
sharing
the
screen
right,
yep,
okay,
cool,
so
yeah.
If
you
log
into
your
dev
console-
and
this
is
you
if
you
don't
have
an
account
or
you
know
you
can
sign
up
easily-
I
already
have
my
accounts
like
well.
B
I
just
connect
with
github,
it's
just
easier
for
me
to
do
that,
and
I
have
alerts
test
project
that
I
created
and
there
are
a
couple
of
tabs
right
here.
Well,
first
of
all,
very
selfishly.
We
actually
embed
it
near
lake
into
depth.
Console
too
so
you
have
the
indexer
tab
on
and
within
dev
console
that
you
can
just
you
know,
look
at
all
the
introduction
that
fro
just
talked
about
for
the
value
propositional
link.
B
You
know
how
powerful
it
is
and
how
easy
to
use-
and
you
will
have
like
the
you
know,
a
couple
of
links
that
you
can
just
directly
go
into
the
most
helpful
examples
and
and
like
try
out
near
lake,
go
ahead
directly
and
for
analytics
tab.
You
probably
talk
about
it
before
in
other
meetings,
but
you
can
also
add
your
contracts
within
within
this,
for
example,
I
can
try.
You
know
for
us,
the
marketplace.
B
Oh,
it's
not
okay.
I
actually
don't
remember
what
it
is,
but
you
basically
yeah
you
can.
You
can
add
your
contract
here
and
then
you
will
show
up
analytics
tabs
of
your
contract,
how
it's
performing
and
everything.
But
that's
not
the
point
of
this
demo.
The
point
of
this
demo
is
actually
demoing
about
alerts,
so
I
actually
have
alerts
set
up
for
successful
transaction.
I'm
just
gonna
delete
this
because
I
was
testing
it.
So
let's
pretend
that
doesn't
happen.
So
how
you
do
is
it's
very
easy.
B
It's
just
like
you
know,
hit
create
new
alerts.
You
go
into
alerts,
target
address
I'll
put
mine
in
case.
Anyone
wants
to
send
me
more
token
on
testnet,
so
select
condition
we
actually
now
and
from
the
last
demo.
We
we
actually
have
a
lot
more
supporting
this
time.
We
enabled
events
locked
on
on
top
of
this
alerts
and
we
also
enabled
account
balance,
change
and
account
balance
change
by
percentage.
B
So
all
of
these
are
sorry.
All
of
these
are
the
newly
supported
feature
that
we
worked
really
hard
to
support
on.
You
know
all
the
way
from
having
more
indexers
to
support
this
from
the
back
end.
All
the
way
to
you
know
enable
this
from
the
front
and
the
easier
way
for
the
simplicity-
and
you
know
I
just
don't-
have
it's
a
it's
a
account
account
address,
so
I
don't
have
a
lot
of
things
to
be
able
to
demo
here.
B
So
I
just
use
the
simplest
one
on
successful
transaction
and
I'll
enable
this
by
adding
a
destination.
So
this
is
also
very
easy.
You
have
a
web
hook
or
you
have
a
telegram
select
and
you
can
easily
enable
this
by
just
you
know,
scan
a
qr
code
or
just
directly
open
the
app
you
open
your
telegram,
and
it
will
just
pop
up,
which
I
think,
can
anyone
see
this
telegram
bot,
yep,
cool,
okay,
so
yeah?
B
So
you
can
just
you
know,
there's
this
def
console
def
bot,
it's
going
to
pop
up,
and
you
know
you
are
going
to
get
your
alerts
from
here.
So
I'll,
just
enable
this
destination
I'll
create
alerts.
What
I'm
going
to
do
next
is
go
on
a
test
at
knowledge.
This
is
like
the
tiffany
testnet
3
account,
and
anyone
want
free
test
net
tokens
submit
their
addresses.
If
not
I'm
just
going
to
send
it
to
pro
okay,
hey
ben
I'm
giving
you.
B
I
only
have
six
here,
I'm
giving
you
three,
I'm
very
generous.
You
know
that,
and
benjamin
dodge
has
that
okay,
send
I'm
giving
you
half
my
tokens
and
sending
excuse
me,
keep
coughing
okay,
awesome,
so
it
is
processed
here.
Let's
look
at
the
bots
and
see
if
it's
actually
responding,
yay,
okay,
popping
up,
you
have
successful
transactions
here,
yay
triggered
and
we
have
the
reason
it's
popping
up.
Multiple
times
is
because
you
know
there
are
couple
processing
that
that's
happening
there,
so
each
of
them
refer
to
actually
different
receipts.
B
So
you
can
look
into
the
details
of
your
transaction
but
yeah.
So
that's
pretty
much
the
alerts
demo
and
definitely
go
in
there.
Try
out
we're
going
to
have
a
public
release,
we're
going
to
have
a
public
release.
You
know
starting
next
week
on
you
know,
and
you
know
it
will
be
available
for
all
the
users
on
top
of
dev
console.
So
this
is
a
spoiler.
B
So
whoever
is
here,
you
know,
you
have
the
first
see
first
view
of
the
new
alerts
that
we're
gonna
support,
so,
okay,
going
forward
last
slide.
I
have
here,
is
pagoda
user
survey,
so
our
our
developer,
designer
team
actually
created
this
survey,
and
you
know
corvin
our
designer
actually
created
a
forum
post
so
that
everyone
can
actually
look
at
why
we
want
to
design
why
we
want
to
do
this
survey
and
what
we
want
to
know
about
from
you
guys.
B
We
really
value
the
feedbacks
and
and
suggestions
and
all
of
your
experiences.
The
survey
is
actually
very
simple
and
easy,
so
just
go
in
and
they're
only
like
you
know
a
couple
of
questions.
It's
enabled
with
a
google
google
form.
So
you
know
you
can
just
you
can
just
answer
this
question
selectively
and
really
value
that
it's
going
to
be
super
super
helpful
for
us
to
really
structure
pagoda
products
forward,
and
this
is
really
you
know
going
to
be
affecting
across
different
products
offering.
B
So
we
really
welcome
all
the
feedbacks
and
participation
here.
So
what
we'll
share
the
links?
I'll
actually
post
them
all
of
them
right
now
in
the
chat
and
we'll
also
share
the
links
after
the
call
in
other
areas
and
places,
and
that's
all
for
our
presentation-
and
I
see
one
question
about:
can
we
log
in
with
your
accounts
or
go
to
dev
console
yeah?
So
that
is
a
great
feedback.
B
We
actually
have
been
getting
that
feedback
from
a
couple
people
and
we're
we're
working
on
enabling
anonymous
login
to
dev
console,
and
we
have
actually
created
a
github
discussion
about
this.
So
we'll
love
more
discussion
and
follow
up
on
the
status
that
we
are
going
to
have
there
I'm
going
to
find
that
right
now.
A
A
Yeah
no
exciting
stuff
a
lot,
a
lot
of
cool
things
coming
coming
down
the
coming
of
the
pipe
any
chance
of
having
docs
in
spanish
yeah.
We
do
have
like
a
crowd
in
I'm
not
sure
about
near
indexer,
but
I
know
on
docs.new.org
we
do
have
a
crowd
in
translation
feature
that
community
members
have
been
helping
translate,
but
yeah
definitely
yeah.
Please,
please
open
up
a
pr
would
love
to
hear
have
some
more
community
contributions
for
translating
our.
A
Yeah
dev,
the
the
folks
on
devereaux,
like
we
have
five
individuals
that
speak
fluent
spanish,
so
yeah
hop
into
office
hours.
If
you,
if
you
speak
spanish
and
wanna,
and
want
to
talk
to
natively
yeah,
there's
there's
a
bunch
of
us
that
are
definitely
fluent
in
that
language
and
yeah
could
definitely
help
with
any
pr's
that
you
have.
A
Cool,
I
I
I
think
we
did
it.
I
think
I
think
I
think
we
answered
all
the
questions
that
you
have
yeah
and
if
you
have
any
follow-up
questions,
please
yeah
come
hang
out
office
hours,
we'll
upload
this
to
youtube.
We'll
also
have
links
for
feedback
that
you
can
participate
in
when's,
the
airdrop
sir.
A
C
We
are
always
present
in
the
communities
all
over
the
places
and
if,
if
we
suddenly
miss
something,
the
royal
team
will
definitely
help
us
to
like
to
be
brought
to
the
right
discussion
and
helped
you
out.
So
I
am,
I'm
excited
to
see
more
and
more
projects
building
on
top
of
all
the
tools
that
our
our
team
is
working
on.
I
am
it's
always
a
pleasure
to
see
your
success.
Vlogs
so
go
community.