►
From YouTube: Core Unit Tools #11: Radicle.xyz | Nov 17, 2021
Description
Radicle.xyz is a permissionless and decentralized code collaboration tool that easily allows users to share code without relying on a third party. The solution is built as a peer-to-peer networking layer (called Radicle Link) on top of Git’s smart transfer protocol, packfiles. Backed by public-key crypto, as a project gains interest more redundant copies are stored and shared locally with peers.
A
Well,
hello:
everyone.
Thank
you
for
joining
this
episode
of
core
unit
tools,
I'm
retro
contributor,
with
the
sustainable
ecosystem
scaling
core
unit
and
today
we're
joined
by
radical.
They
are
for
lack
of
a
better
phrase,
a
decentralized
github
and
are
here
to
share
how
their
toolset
can
further
progress.
The
decentralization
of
core
units
at
maker
dow
we'll
hand
it
over
to
the
radical
team.
Please
take
it
away.
C
C
Yep
cool
right,
so
then
you
know
based
on
the
architecture,
I'll
kind
of
run
you
through
kind
of
some
of
the
stuff
we've
got
already
there's
there's
the
desktop
client,
which
we've
we've
got
up
and
running,
which
allows
you
to
you
know
kind
of,
add,
add
repositories
to
a
mono
repo
which
which,
as
I
mentioned,
is
kind
of
gossip
between
the
pairs.
And
so
you
can
kind
of
see
that
up
and
running.
C
So
you
can,
you
know,
source
browsing
and
all
those
features
you
can
see
commits
and
you
can
see
it's
contributing
to
it,
that's
kind
of
my
individual
profile
and
then
there's
orgs,
as
I
mentioned,
which
right
now
we're
actually
kind
of
polishing
our
kind
of
replication
stuff.
So
it's
it's,
it's
not
quite
them
showing
for
the
org
nodes,
but
but
yeah.
This
will
allow
you
to
access
repositories
as
an
org.
C
C
Actually
you
know
you
connect
your
wallet
and
you're
able
to
create
and
and
then
and
then
manage
it
as
a
signer
on
on
either
a
multi-stake
or
a
dow
contract,
and
then
this
shows
how
you
can
connect
kind
of
a
an
org
node.
That
then,
is
able
to
replicate
and
be
an
always-on
node
for
your
organization.
C
As
part
of
that
kind
of,
I
guess
kind
of
replication
and
sharing
of
that
data,
and
then
we've
got
the
web
client,
which
is
kind
of
again
showing
the
same
thing.
But
it's
got
a
web
interface
over
it.
So
you
can,
you
know,
grab
a
url
and
just
send
it
to
someone
for
them
to
be
able
to
view
it.
I
decided
to
click
on
the
one:
that's
not
working,
which
is
always
always
good.
The
rest
are
kind
of
replicating
and
showing,
which
is
great.
C
This
is
starting
to
get
pretty
stable
right,
so
that's
kind
of
the
peer-to-peer
code,
distribution
side
and
the
benefits
of
that
kind
of
as
one
kind
of
laid
out
in
his
and
is
quite
quite
you
know
great
kind
of
intro
to
what
radical
is
in
in
the
invite.
You
know
it's:
it's
free
forever.
It's
completely
open
source,
it's
available
anywhere,
there's
intrinsic
spam
and
content
moderation
and
then
there's
also
the
you
know.
We've
kind
of
been
using
these
ethereum
features
to
tackle
the
global,
namespace
and
discoverability
challenges.
C
And,
as
I
mentioned,
you
know,
the
graph
is
has
started
using
it
for
protocol
governance
and
so
has
synthetics
and
and
yeah,
I'm
kind
of
in
the
process
of
onboarding
a
bunch
of
the
basically
top
projects
now
kind
of
you
know
once
you've
kind
of
got
the
code
distribution
side
of
it.
You
know,
as
I
mentioned
it's,
you
know
it's
very
much
about
building
the
collaboration
around
that
we're
currently
working
on
kind
of
adding
collaboration,
features
via
issues
and
and
kind
of
we
already
have
patches
built,
we're
now.
C
Building
collaboration,
features
to
allow
for
things
like
code
review
and
then
also
building
out
more
of
the
profiles.
I'll
show
you
here,
so
this
is
gonna.
This
is
how
issues
will
look,
and
you
know
I
guess,
similar
to
what
you
see
on
github,
but
the
the
main
difference
being
that
we're
using
things
like
auto,
merge,
doctor,
docs
and
crdts
to
kind
of
you
know,
share
that
data
around
rather
than
I
guess
I
guess,
storing
it
and
getting
receiving
it
from
from
a
central
server.
C
And
now
you
know
what
we've
been
seeing
is
with.
Teams
is
the
way
that
they,
the
initial
kind
of
powerful
use
cases
around.
You
know
dao's
using
it
to
support
the
dev
ecosystems
and
and
become
kind
of
doubt,
holding
for
developers,
we're
kind
of
trying
we're
very
much.
You
know
playing
on
that
meme
dev
dao,
which
we
think
is
going
to
become
quite
dominant
and
and
so
what
that
means,
I
guess
in
practice,
is
a
number
of
features
for
projects
to
on
board.
C
When
a
developer
comes
to
an
org
they
should
they
should
be
able
to
understand
what
works
being
done,
who's
working
on
it.
What
kind
of
funding
is
being
put
behind
the
developer
dell
by
an
org
and
and
then
also
you
know,
who's
contributing
to
it
and
and
how
they
can
contribute?
And
so
this
this
page
is
very
much
about
onboarding
developers
as
they
land
in
in
within
a
kind
of
I
guess,
dev
dell
and
dev
down.
C
Is
you
know
it's
it's
an
interesting
one
because
excuse
me
as
I
need
some
of
juan's
drink,
but
so
the
the
org
you
know,
there's
there's
kind
of
a
project
dial
which
is
kind
of
a
organization
which
it
seems
like
the
the
kind
of
the
pattern
that's
being
developed
is.
Is
that
there'll
be
many
many
dowels
kind
of
within
an
organization
that
kind
of
kind
of
loosely
connected
and
collaborate
in
different
ways?
C
They
want
to
discover
contribution
opportunities
so,
whether
that's
a
grant
application
they
want
to
put
in
whether
they
want
to
join
as
a
contributor
and
have
streamed
funds
for
for
taking
on
a
particular
role
or
whether
they
want
to
take
on
funded
issues
that
are
in
the
in
the
projects
of
the
of
the
org.
They
can
kind
of
discover
it
hair
and,
and
then
they
can.
C
C
And
right
and
so
and
then
you
know,
I've
already
shown
the
screen.
You
know
that
there's
building
out
issues,
but
I
guess
what's
really
cool
is
is-
is
the
fact
that
you're
going
to
be
able
to
have
funded
issues
which
means
that,
whether
it's
a
single,
dow
or
multiple
dollars,
putting
some
funds
behind
getting
an
issue
complete?
C
We
can
definitely
see
projects
funding
their
own
issues,
but
also,
if,
if
it's
a
project,
maybe
an
open
source
project
that
other
projects
are
relying
on.
Maybe
maybe
a
number
of
them
put
funds
behind
an
issue
to
to
try
and
get
it
done
and-
and
I
guess
the
beauty
of
it
being
that
it
all
stays
within
the
workflow
rather
than
taking
them
off
the
platform.
C
I
think
one
of
the
one
of
the
examples
I
really
liked.
So
you
know,
as
I
said,
one
of
the
inspirations
that
we
things
that
we've
taken
inspiration
from
is
things
like
the
falcon
grants
program,
and
you
know
this
is
a
comment
that's
copied
from
there,
which
is
you
know
the
the
reason
why
they've
done
it
in
in
that
workflow
is
because
so
developers
who
are
making
proposals
you
know
can
can
get
kind
of
guidance
and
feedback
and
reviews
from
developers
who
actually
within
their
workflow.
C
It
allows
them
to
actually
contribute
to
that
discussion
before
funding
is
given,
and
we
think
we
thought
it's
kind
of
very
you
know
disconnected
and
broken
that
once
you
is
approved.
Suddenly
all
of
this
admin
is
created
and,
and
the
workflow
goes
off
of
off
of
it.
I
guess
this
is
the
entire
point
of
web
3.
Is
that
it
should.
C
I
guess
continue
to
contribute
and
actually
feel
feel
like
they
can
do
some
good
work
right.
I
think
that's
that's
that
kind
of.
Actually,
I
think
I
still
got
some
some
slides
for
you.
So
fast-growing
ecosystem.
That's
always
a
valuable
slide.
We've
got
a
lot
of
projects,
onboarding
we're
actually
working
towards
the
launch
which
is
aimed
for
january
and
and
and
I'm
aiming
for
about
50
of
the
top
projects
to
to
be
onboarded
and
and
set
up.
C
So
we
can,
we
can
kind
of
go
out
and
do
a
big
co-marketing
push
to
kind
of,
engage
and
and
on
board
developers
to
those
projects
have
partnered
with
us
and
that's
kind
of
the
timeline,
as
I've
said,
and
I've
clearly
gone
crazy
with
the
gifts
abby
mocks
it,
but
also,
I
think,
secretly
enjoys
it
and
then
yeah.
So
you
know
if
you
guys,
if
that
kind
of
connects
with
the
kind
of
things
you
guys
are
thinking
and
it
fits
with.
You
then
yeah.
C
I
think
the
next
steps
are
setting
up
a
radical
org,
sharing
kind
of
the
contributor
or
positions
and
opportunities
that
you
guys
are
thinking
of,
or
you
already
either
have
out
there
or
that
you
think
would
fit
well
with
with
these
workflows-
and
I
can
I
can
kind
of-
and
we
can
kind
of
do
the
work
to
support
to
get
to
kind
of
get
you
guys
going
up
and
running.
I'm
now,
looking
at
all
of
the
the
comments
in
chat
but
cool,
that's
that's
all
of
it.
C
B
A
It
was
a
a
great
introductory
overview,
I'll
kick
off
questions
one
one
of
the
things
that
was
provided
in
the
the
forum
post
announcing
this
call
was
the
ability
to
use
multi-sig
wallets
in
order
to
manage
repos.
Could
you
go
into
that
a
little
bit?
Multi-Six
is
something
that
we
use
pretty
heavily
here
at
maker
dow
and
I
think
that's
a
an
interesting
application
of
it.
C
Yep,
so
so,
if
you,
if
you
actually
want
to
create
an
org,
you
can
click
on
multi-signer
and
it
creates
a
multisig
for
you.
You
can
also
connect,
use
an
existing
multistage.
Add
it
to
that
list
and
well,
I
think
you
can
add
input
in
this
thing,
although
that
you
should
really
be
here,
but
you
can
someone
come
in
admit
there
we
go
better
late
than
never.
I
guess,
but
let's
see
good
so
welcome,
welcome
to
whoever
joined
but
yeah.
C
So
you
can,
you
can
add,
you
can
add
the
kind
of
address
for
for
emoji,
sig
and
also
you
know.
I
think
dxdow
has
a
custom,
dow
contract
that
they've
they're
using
to
govern
their
org
and
so
yeah.
I
mean
it's
a
it's
a
gnosis,
safe
that
that
people
are
that
that's
the
default,
that's
that's
created
and
you
can
have
as
many
signatories
and
and
then
in
gnosis
define.
D
Maybe
just
add
a
little
bit
of
context
here,
because
I
realized
that
maybe
we
didn't
talk
a
lot
about
radical
works,
but
I
think
that
the
feature
with
radical
that
ties
multi-cigs
to
code
collaboration
is
radical
or
radical.
Orgs
are
basically
like
on-chain
entities
that
can
be
governed
by
an
external
address
or
a
multi-sig,
and
so
basically,
what
you
do
is
you
anchor
canonical
project
state
to
these
orgs
via
anchors,
which
are
just
like
signed
messages
that
can
be
committed
via
quorum
through
a
multi-sig
or
through
a
single
transaction?
D
And
so
basically,
what
it's
saying
is
that,
instead
of
you
know
relying
on
a
single
account
or
a
single
like
github
org,
to
maintain
a
canonical
canonical
project
state
of
a
set
of
repositories.
You
can
actually
do
that
on
chain
via
ethereum
identities
and
via
decentralized
control
through
multi-sigs
and
so
right.
Now.
Radical
works
is
all
about
kind
of
like
maintaining,
canonical
and
global
project
state
of
repositories.
D
But
you
can
imagine
these
as
a
really
important
primitive
for
decentralizing
access,
control
of
repositories
in
the
future
right
of
automating
interactions
with
repositories
in
the
future.
So
we
actually
have
a
lot
of
really
cool
ideas
that
are
in
you
know
in
the
gnosis
guild
and
radical
ecosystems
around
like.
D
How
can
you
automate
merge,
merge,
requests
right
via
radical
orgs
and
how
can
you
utilize
the
power
of
multi-sigs
and
the
decentralized
access
that
they
provide
and
incorporate
those
into
the
development
flows,
and
so
right
now
again
it's
all
about
anchors,
and
if
you
go
to
our
mirror
page,
you
can
actually
see
a
really
awesome
tutorial.
That
kind
of
runs
through
what
radical
orgs
are,
how
you
would
start
it
and
how
you
would
use
it
as
a
team.
D
A
Yeah
yeah,
definitely
it
answered
my
question
and,
as
always,
we
encourage
the
audience
to
ask
questions.
So
if
there
are
any,
please
go
ahead
and
drop
them
in
the
chat.
We'll
give
you
the
ability
to
speak
as
a
follow-up
to
that
first
question:
what
what
would
be
the
easiest
way
for
a
group
to
get
started
then
to
start
using
radical.
C
Yeah,
I
think,
as
I've
said
this,
you
know,
we've
got
a
tutorial
that
kind
of
allows
you
to
get
set
up
quite
quite
easily,
I'm
also
currently
personally,
jumping
on
calls
and
onboarding
people.
So
there's
a
number
of
you
know
with
all
these
things.
All
the
tech
is
kind
of
less
than
polished.
You
know
a
wallet
fails
or
something
like
that,
so
I'm
I'm
personally
on
boarding
teams.
C
So
if
you
guys
want
to
get
set
up,
we
can
just
set
up
an
onboarding
call
for
an
hour
and
and
get
that
done,
and
I-
and
we
also
just
to
be
clear-
we're
covering
we're
covering
gas
right
now
as
we're
not
on
layer
two
yet
so
I
can
kind
of
as
we
as
we
do
that
setup
either.
You
guys
send
me
a
wallet
after
saying
I
set
it
up
or
or
I
can.
B
That
gas
part
mates,
we
have
another
question
but
I'll
come
back
and
ask
my
original
one
first,
so
I'm
pros
11,
I'm
the
one
of
the
governance
facilitators.
So
I
was
obviously
thinking
about
this
for
our
own
core
unit
and
how
we
might
be
able
to
use
it
within
the
org,
particularly
around
ideas
of
like
documentation
like
we
recently
just
spent
a
bunch
of
time,
setting
up
a
get
books
to
kind
of
allow
people
to
explore
and
see
all
the
docs
and
things
we're
working
on
like
is
this
compatible
get
books
like?
B
C
D
Yeah,
so
maintaining
repositories
on
radical
on
the
peer-to-peer
network
is
as
simple
as
pushing
to
another
remote,
so
while
github
obviously
makes
it
very
easy
to
integrate
with
different
endpoints
or
where
you
want
to
push
those
repositories,
there's
some
work
to
be
done.
But
you
know
a
lot
of
this
stuff
is
possible,
it's
more
about
how
you
want
to
relate
it
to
some
of
the
ethereum
features
where
things
get
interesting
right.
So,
for
example,
like
I
maintain
the
the
community
blog,
we
sorry,
we
maintain
the
community
blog
via
a
radical
org.
D
So
all
posts
to
the
mirror
platform
have
to
be
anchored
on
chain
before
published
to
the
platform.
Of
course,
there's
a
lot
of
trust
points
there.
It's
just
a
dog-fooded
experiment,
but
that
example,
I
think
relates
to
you
know
that
any
radical
can
be
used
to
manage
any
version,
control
repository
of
any
information
and
it's
more
about
how
you're,
integrating
it
locally
and
and
pushing
it
and
deploying
it
to
different
platforms
like
like
gitbooks
or
like
we're
thinking
like
deployment
of
apps
as
well.
D
C
Yeah,
I
guess
so
I
would
you
know,
I
don't
know
if
it's
worth
adding,
but
I
can
definitely
see
right
right
now.
I
guess
the
github
is
built
on
on
open.
Well,
get
get
sorry
radicals
built
on
kind
of
open
protocols
and
open
data,
and-
and
so
I
can
very
much
see
you
know-
either
you
know
a
team
being
funded
or
or
other
teams
building
on
that
data
and
actually
fully
integrating
it
into
the
documentation
sites.
So
as
they
because
I
think
right
now
kind
of
the.
C
It's
it's
kind
of
this
disconnected
experience
of
of
has
has
the
educational
material
and
then
here's
the
you
know
where
all
the
work's
being
done,
and
so
I
think
you
know-
I
think
I
mentioned
to
one
of
your
team
members
as
well
about
the
idea
of
you
know.
If
you
guys
are
working
on
you
know,
it
seems,
like
you
guys,
are
doing
a
lot
of
good
work
on
education
and
building
out
this
tooling.
E
E
And
I
think
I
might
have
saw
something
on
ceramic,
which
I'm
a
big
fan
of
by
the
way-
and
I
just
wanted
to
see
if
you
guys
are
doing
something
for
them,
or
are
you
looking
to
do
something
with
them
in
the
near
future
as
far
as
decentralizing
the
data
that
might
be
going
on
to
something
like
the
forum
that
we
use
a
lot
right?
It's
pretty
centralized
it's
no
secret.
So
it's
this
course.
So
if
you
can
just
comment
on
that,
and
I
apologize
for
missing
that
part
of
the
presentation-
that's
right.
C
C
We
kind
of
believe
that
those
those
kind
of
need
to
be
run
by
individual
organizations
rather
than
a
single
central
server,
of
course,
and
so
we're
looking
at
automating
and
simplifying
that
setup
and
and
one
of
the
options
we're
looking
at
is
our
cache
network.
We've
already
done
a
lot
of
the
setup
to
make
that
possible.
That's
still,
but
there's
a
few
things
left
to
do
that
there
and
then
we've
also.
C
The
third
component
is,
we've
actually
just
had
it's
probably
in
one
of
our
open
repos.
I
won't
actually
show
my
discord
because
I
don't
know
what
craziness
people
may
be
messaging
in
there,
but
but
there's
a
there's,
someone
who's,
just
posted
in
in
our
old
clients.
We
just
had
someone
join
our
team
who's
working
on
one
click
deploy
via,
I
think,
a
different
mechanism,
so
so
yeah
and
that's
kind
of
so.
C
D
You
know
the
github
killer,
but
instead
making
it
a
very
resilient
stack
of
collaboration,
tooling,
that's
decentralized
and
and
built
on
ethereum
that
projects
can
take
to
use
and
empower
their
development
workflows
within
their
decentralized
communities.
So,
obviously,
like
you
know,
the
maker
community
is
very
strong,
very
decentralized,
probably
like
the
most
decentralized.
You
know
the
maker
journey.
F
D
Been
kind
of
a
resemblance
of
kind
of
everything,
that's
now
kind
of
starting
to
kick
off
in
the
dow
space,
and
so
there's
a
lot
of
space
to
start
figuring
out.
You
know
how
radical
could
support
different
development
communities,
like
makers
and
figure
out
what
tooling
is
necessary
and
and
what
pieces
of
the
stack
should
be
built
together
to
create.
You
know
those
that
tooling.
E
Oh
and
just
one
quick,
thank
you
for
that,
providing
all
that
information
and
I'm
not
a
developer
but
from
a
web
2.0
of
you
would
you
guys
say
you
are
similar
to
linear.app
or
a
lot
different,
where
you're
servicing
more
for
web3
I
mean,
I
guess
linear
is
also
moving
into
the
space,
but
just
wanted
to
get
your
thoughts
on
that,
and
thanks
in
advance
for
answering
my
questions.
That'll
be
it
for
me.
D
Last
time
I
checked
up
on
linear,
they
were
issue
tracking,
so
I
think
that
they're
definitely
like
a
a
collaboration
tool,
but
that's
pretty
heavily
based
in
the
social
collaboration
where
I
think
radical,
which
this
is
actually
like.
A
perfect
echo
of
what
I
just
said.
Radicals
ain't
needing
to
be
a
resilient
stack
for
collaboration.
That's
you
know,
based
you
know,
everything
on
radical
is
actually
built
on
a
decentralized
peer-to-peer
network
right.
D
You
know
with
a
goal
that
people
could
use
linear
on
top
of
radical,
so
really,
like
repositories,
are
hosted
on
radical.
You
know
it's
not
just
another
app
to
view
and
interact
with
your
repositories
if
that
makes
sense,
but
I'd
be
very
interested
to
learn
more
if
they're
getting
into
a
web
3
territory
for
sure.
A
F
Yes,
hello:
this
is
rafael,
I'm
from
the
one
of
the
development
teams
in
makerada.
We
are
especially
focused
on
frontend
systems
and
our
team
heavily
relies
in
automation
and
right
now
we
are
using
different
services,
but
especially
with
circle
ci
and
virtual
for
deployments,
and
we
need
also
not
the
front-end
but
microservices
and
other
things
that
we
that
we
run
we'd
like
to
know.
Maybe
we
already
talked
about
this,
but
I
arrived
late
to
the
meeting.
Sorry,
if
you
support
integrations
with
those
systems
to
automate
deployments
and
so
on,.
C
I
guess
cool
workflows
on
on
github
as
they
transition
over.
You
know,
as
we
kind
of
get
more
and
more
robust,
so
that's
kind
of
step,
one.
I
think
one
of
the
things
I
really
should
say
early
on
when
I'm
talking
to
these
things
I
do
try,
but
I
forget
sometimes,
is
that
you
know
we're
not
asking
people
to
come
up
with
github
right
now.
It's
it's
very
much.
C
This
is
kind
of
a
secondary
layer,
that
kind
of
adds
resilience
and
then
also
allows
people
to
start
building
that
yeah
develop
ecosystem
and
supporting
them,
and
the
second
thing
I'll
say
is
yeah.
I
guess
that
we
were
speaking
to
versailles
yesterday
and
and
the
you
know
from
the
the
ceo
down.
You
know,
they're
very
much
being
told:
we've
got
to
integrate
with
web
3
and
they're
very
keen
to
support.
D
A
D
Radical
is
a
free
and
open
source
project,
so
radical
aims
to
be
the
first
community-led.
You
know
free
and
open
source
project
that's
covered
on
the
internet,
so
one
of
the
big
aspects
of
the
radical
ecosystem
is
its
governing
ecosystem.
So
the
network
in
february
was
decentralized
with
the
launch
of
the
radical
token,
which
you
know,
gives
the
community
opportunity
to
participate
in
the
communal
governance
of
the
radical
network.
So
I
think
success
of
the
project
is
actually
the
continuous
decentralization
of
the
project.
D
So
I
know
I
keep
just
like
linking
you
guys,
forum
post,
but
honestly
this
is,
I
realize
where
we
capture
most
of
our
thoughts
share
right,
but
there's
a
post
about
our
r,
as
in
the
core
team
and
initial
contributors
to
the
radical
project
and
setting
the
goal
of
completely
decentralizing
the
project.
You
know
obviously
similar
to
the
to
the
maker
approach
and
and
the
goal
is
for
all
project
development
on
the
radical
project
to
be
funded
via
the
radical
dao,
which
is
currently
governs.
D
The
radical
treasury,
which
holds
over
50
of
the
radical
token
supply
and
so
right
now
what's
happening
in
the
community.
Is
the
activation
of
that
radical
governance
and
the
deployment
of
the
radical
treasury
into
the
radical
open
source
project
to
continue
decentralizing
development?
Empowering
you
know
radical
as
an
open
source
project,
so
getting
more
developers
building
on
radical
funding,
more
pieces
of
the
stack
and
creating
the
community
infrastructure
necessary
to
support.
D
You
know
the
the
growth
and
the
success
of
radical
as
in
the
long
term,
as
a
self-sustaining
community-led
and
governed
open
source
project.
So
it's
really
about
kind
of
shifting
the
paradigm
of
what
is
required
from
a
project,
because
the
main
goal
for
radical
is
to
be
resilient
collaboration,
infrastructure
for
web3
and
so,
and
we
want
to
do
that
in
you
know
a
way
that
leaves
our
users
and
our
network
participants
resistant
to
extraction
of
traditional
web
2
models,
so
lots
more
in
the
forum
there.
D
You
can
also
take
a
look
at
what's
happening
in
our
governance
forum.
We
have
a
governance
working
group
that
meets
every
two
weeks
and
is
currently
stewarding
grant's
proposal
for
it
and
leaning
into
you
know.
How
can
we
be
supporting
adoption
and
growth
through
the
dow
through
the
deployment
of
the
radical
treasury?
So
also
like
really
really
exciting
stuff
happening
there.
A
Very
cool:
I
have
grabbed
the
links
that
you
were
sharing
and
we'll
make
sure
to
update
the
forum
post
with
that,
so
anybody
watching
the
recordings
will
be
able
to
interact
with
the
the
references
that
you've
provided.
There
aren't
any
other
further
questions
we'll
go
ahead
and
wrap
this
up.
I
always
like
to
to
end
with
follow-up
opportunities.
So
what's
the
best
way
to
get
a
hold
of
you
guys,
I
believe
you
mentioned
that.
C
C
C
If
you
can,
you
can
kind
of,
you
know,
jump
into
discord
or
twitter
and
then
there's
the
tutorial
link
you
guys
can
get
set
up
and
and
in
the
within
and
then
also
just
reach
out
to
me
and
and
and
we
can
set
up
an
onboarding
pool
and
and
then
we're
also
reimbursing
gas,
so
so
yeah,
let
me
know,
I
think
I
don't
know
if
that
covers.
It
probably
need
to
find
a
better
way
of
saying
all
of
that
there
we
go.
A
Awesome
well,
thank
you
so
much
to
nassar
and
abby
for
joining
from
the
radical
team.
Just
as
a
quick
shout
out,
the
blog
at
radical.xyd,
xyz,
backslash
blog
was
very
well
put
together.
It's
a
great
resource
to
get
caught
up
quickly
with
the
the
community
and
ecosystem
and
we'll
be
sure
to
stay
in
touch
and
stay
up
to
date
with
the
developments
or
radical.