Information

2021 11 27 15 00 07

Basic shortcuts

Ctrl + SSave subtitles
Ctrl + click
Double click
Edit highlighted caption
TabEdit next caption
Shift + TabEdit previous caption
EscLeave edit mode
Ctrl + SpacePlay / pause video
Ctrl + HomePlay selected caption
Ctrl + EnterSplit caption at cursor position
at current time

Advanced shortcuts

Ctrl + InsertAdd new caption
Ctrl + DeleteDelete selected caption
Ctrl + IEdit currently played segment
Shift + EnterNew line when editing
Ctrl + LeftPlay from -1s
Ctrl + RightPlay from +1s
Alt + LeftShift caption start time -0.1s
Alt + RightShift caption start time +0.1s
Alt + DownShift caption end time -0.1s
Alt + UpShift caption end time +0.1s

Annotation shortcuts

Ctrl + 1Hesitation
Ctrl + 2Speaker noise
Ctrl + 3Background noise
Ctrl + 4Unknown word
Ctrl + 5Wrong segment
Ctrl + 6Crosstalk segment
You are in the read-only mode. Close
00:00.0
00:08.2
Ok so, hello everyone listening, this is obviously Everscale incubator. I belive we're on show number one.
00:08.3
00:16.0
I'm speaking today with Norton who is bringing his project to us, Fidosafe
00:16.1
00:19.5
So hi Norton. Good to have you here! Would you introduce yourself?
00:19.6
00:24.4
Yes, sure, Ben, thanks for providing the stage
00:24.5
00:29.3
for presenting my project, actually cannot
00:29.4
00:34.2
say much about myself, like I'm ordinary guy
00:34.3
00:39.1
developer, crypto enthusiast, and, yes, I'm like
00:39.2
00:44.0
keeping an eye on the Everscale blockchain
00:44.1
00:48.9
for a while, but did not have a chance to
00:49.0
00:53.8
find applicable cases that I can implement
00:53.9
00:58.7
but, yes, recently I've found a niche
00:58.8
01:03.6
that sounds interesting to me, and today I would like to
01:03.7
01:08.5
say a few words about this niche, describe the target
01:08.6
01:13.4
audience, its pains, its needs, and share
01:13.5
01:18.3
some insights, and, actually, like it
01:18.4
01:23.2
was the grounds for, this project,
01:23.3
01:28.1
Fidosafe, that I'll also maybe share
01:28.2
01:33.0
during this broadcast. Ok, well, in this case
01:33.1
01:37.9
I think we should probably dive straight into it and
01:38.0
01:42.8
... doing a screensharing
01:42.9
01:47.7
01:47.8
01:52.6
aha, yes.
01:52.7
01:57.5
so can everyone see that pitch there on the screen if I've shared the right screen?
01:57.6
02:02.4
Yes, I guess the wrong screen, it is a website page
02:02.5
02:07.3
Wrong screen? Yeaw. Here we go. Yes. Go to... We've got the infinite loop, I apologise guys.
02:07.4
02:12.2
let's close that down. More used to working with
02:12.3
02:17.1
Zoom, yeah. Yes, me too, that's why I didn't want to share.
02:17.2
02:22.0
there we go. so. can everyone see the pich?
02:22.1
02:26.9
We should see Fidosafe
02:27.0
02:31.8
on the screen. Yeah, I do.
02:31.9
02:36.7
Ok, excellent. Let's just quickly roll through this
02:36.8
02:41.6
We won't going through every point on the document, as I've got a few questions, I'll try to keep it
02:41.7
02:46.5
a little more informal, but yeah, obviously, if you could give us just
02:46.6
02:51.4
a very quick high-level interview of what is Fidosafe.
02:51.5
02:56.3
Hm, ok, just to warm up
02:56.4
03:01.2
I would like to say a few words about the name, so the name originates from
03:01.3
03:06.1
actually Latin, and Fido means the first person
03:06.2
03:11.0
verb, like "I trust",
03:11.1
03:15.9
like the safe that I trust, Fidosafe, but recently
03:16.0
03:20.8
somebody shared a reference that there is a famous player
03:20.9
03:25.7
chess player, Vladimir Fidoseev, and yes,
03:25.8
03:30.6
from that time, when I hear Fidosafe, I think about chess.
03:30.7
03:35.5
This is a very hot topic with the World Championship
03:35.6
03:40.4
of course. Yeah, uh. But basically in a nutshell
03:40.5
03:45.3
this is a service, webservice where
03:45.4
03:50.2
actually people can jointly
03:50.3
03:55.1
manage their financial resources, so that we would have
03:55.2
04:00.0
multiple custodians using different wallets who can sign transactions
04:00.1
04:04.9
and perform some operations as community
04:05.0
04:09.8
as DAO, yeah.
04:09.9
04:14.7
Touching into your first point, who is this product aimed at?
04:14.8
04:19.6
who is going to use Fidosafe?
04:19.7
04:24.5
Yeah,it might
04:24.6
04:29.4
sound surprising
04:29.5
04:34.3
that there are some B2B tools around on the market
04:34.4
04:39.2
so not only personal accounts in crypto nowadays but also business
04:39.3
04:44.1
accounts start start penetrating the crypto surface
04:44.2
04:49.0
more and more, and of course market starts preparing
04:49.1
04:53.9
some tools for catering to these accounts. THat's why I can describe
04:54.0
04:58.8
these companies as small
04:58.9
05:03.7
crypto investment firms, or maybe crypto
05:03.8
05:08.6
brockers, and possibly communities who also come together
05:08.7
05:13.5
to make financial decisions together, other
05:13.6
05:18.4
audiences for the shared using are of
05:18.5
05:23.3
the accounts are for example are miners or exchanges, but they are I guess too big to
05:23.4
05:28.2
fit the Fidosafe requirements
05:28.3
05:33.1
so that I would just
05:33.2
05:38.0
limit the users to
05:38.1
05:42.9
small and medium crypto businesses theat we will call crypto funds
05:43.0
05:47.8
or crypto firms. Ok, so essentially blockchain
05:47.9
05:52.7
centric small and medium enterprises and businesses which have to
05:52.8
06:05.6
follow more formal path. Yeah. And so, again, this is a very nicely laid out slide presentation, what is it that there is a need
06:05.7
06:10.5
that will why they are ready products that use these people
06:10.6
06:15.4
06:15.5
06:20.3
There are the tools, and the tools serve actually the existing blockchains
06:20.4
06:25.2
if one of these companies
06:25.3
06:30.1
would like to start their operations on Everscale, then they would need to
06:30.2
06:35.0
to uh
06:35.1
06:39.9
adjust to also continue
06:40.0
06:44.8
operations from here, and they could have different options
06:44.9
06:49.7
for this
06:49.8
06:54.6
06:54.7
06:59.5
that's ok, I've thought someone bombing, now all good
06:59.6
07:04.4
as you say, this is the solution which
07:04.5
07:09.3
already exist on the chains in the forms, but there is
07:09.4
07:14.2
obiously... I'll let you explain aside this slide yourself if you want, existing solutions
07:14.3
07:19.1
so yes,
07:19.2
07:24.0
to prepare to this presentation I checked the market
07:24.1
07:28.9
and tried to find the tools that people use
07:29.0
07:33.8
and tried to investigate which functionality is built into these
07:33.9
07:38.7
tools, so that here is my list that originated from
07:38.8
07:43.6
maybe two hours of searching
07:43.7
07:48.5
of course there are more solutions on the market, but these are the
07:48.6
07:53.4
prominent ones, and basing on the
07:53.5
07:58.3
solutions I can make some assumptions on what these businesses should require
07:58.4
08:03.2
and the functionality of these solutions is actually
08:03.3
08:08.1
is pretty much the same, so that if we go
08:08.2
08:13.0
to maybe the second slide
08:13.1
08:17.9
that could help us, we will find out that
08:18.0
08:22.8
in the bare minimum it will require three
08:22.9
08:27.7
things actually. First: some tools for collective
08:27.8
08:32.6
decision making, so that multiple custodians can
08:32.7
08:37.5
vote for this or that or against this or that decision
08:37.6
08:42.4
then user management, the ability to assign roles
08:42.5
08:47.3
and to add more people, remove people from
08:47.4
08:52.2
the list of custodians,
08:52.3
08:57.1
I mean onboarding and offboarding employees actually
08:57.2
09:02.0
Sorry, I believe I've got the right temp here, we can kind say an exmple, so that this is actually
09:02.1
09:06.9
the product doing it here, I belive you've added
09:07.0
09:11.8
a custodian here as an example transaction you showed me earlier
09:11.9
09:16.7
Yes, we can see that happening, sorry, carry on...
09:16.8
09:21.6
... and the third maybe the most tricky
09:21.7
09:26.5
one is auditing facilities
09:26.6
09:31.4
the ability to see the historical
09:31.5
09:36.3
log and be able to understand who did what and when
09:36.4
09:41.2
and when I started with Everscale,
09:41.3
09:46.1
I tried a few multisig accounts
09:46.2
09:51.0
and actually, and none of them had
09:51.1
09:55.9
open source code, but there were compiled versions
09:56.0
10:00.8
of these multisig accounts, and using these accounts is
10:00.9
10:05.7
it was really tricky to understand the history of operations
10:05.8
10:10.6
maybe it was something wrong with me, but
10:10.7
10:15.5
I feel total obscurity, that was one of the reasons to actually
10:15.6
10:20.4
create something where the transactions are obvious
10:20.5
10:25.3
you can at every moment glance at a transaction and see
10:25.4
10:30.2
its details and who confirmed or rejected it
10:30.3
10:35.1
and what was inside this transaction, what operation should happen
10:35.2
10:40.0
so essentially just comming to this part of the slide
10:40.1
10:44.9
there are solutions
10:45.0
10:49.8
which kinda do the task that Fidosafe does, but you do it in more refined
10:49.9
10:56.1
manner which is more suitable for the target audience you're aiming for here
10:56.2
11:01.0
Right, actually it is a service, and not a wallet,
11:01.1
11:05.9
so that users are not obliged to
11:06.0
11:10.8
to come to this new wallet and operate only in this
11:10.9
11:15.7
wallet, comparing to, for example, Oberton
11:15.8
11:19.1
when you need to forcefully switch to this solution
11:19.2
11:24.0
for all your operations, but instead it is a webservice that uses different wallets
11:24.1
11:28.9
for a very-very concrete purpose
11:29.0
11:33.8
for signing multisig transactions and for managing multisig transactions, and for
11:33.9
11:38.7
managing the related operations, so, yes, on the one hand there are
11:38.8
11:43.6
wallets that can potentially implement the same
11:43.7
11:48.5
but it is not their specialization, they are busy with
11:48.6
11:53.4
other things like implementing DeBots, implementing trueNFTs
11:53.5
11:58.3
implementing other features, that their customers actually require
11:58.4
12:03.2
instead, why would they
12:03.3
12:08.1
turn to some other niche market and start doing something
12:08.2
12:13.0
different, it does not make sense. Yes of course, I understand that
12:13.1
12:17.9
completely, that makes a lot of sense, so obviously these
12:18.0
12:22.8
other solution providers it's an option, it's a feature
12:22.9
12:27.7
of these products, but it's not their product as you say.
12:27.8
12:32.6
Yeah, that's brilliant. Comming to the next slide, you've turned this one Pains, obviously,
12:32.7
12:37.5
so we're just going to touch on these, but what on the Pains like you say your target audience at the moment.
12:37.6
12:42.4
Yes, also started to
12:42.5
12:47.3
discuss the pains, but the main pain so actually how to
12:47.4
12:52.2
proceed with operations when you go to Everscale
12:52.3
12:57.1
for example, you had Gnosis to govern your operations
12:57.2
13:02.0
in Etherium, and you just look for the similar stuff
13:02.1
13:06.9
and you have these four options
13:07.0
13:11.8
Firstly, you can revive an existing multisig wallet
13:11.9
13:16.7
and try to somehow operate under it with
13:16.8
13:21.6
ll its obscurity and limitations, maybe it is possible, it is
13:21.7
13:26.5
like dooing accounting in Google Spreadsheets, so it is possible, but it
13:26.6
13:31.4
is not that convenient. Then they could
13:31.5
13:36.3
implement their in-house solution
13:36.4
13:41.2
and in this case it would be also ok, but they would need to spend money
13:41.3
13:46.1
and would need to spend time to implement this
13:46.2
13:51.0
and the biggest issue is that their code will not be open source
13:51.1
13:55.9
it will be an in-house solution
13:56.0
14:00.8
that means it won't be audited, this means it could be possibly prone to
14:00.9
14:05.7
errors or maybe some hacker attacks
14:05.8
14:10.6
so they will always run risk of losing their money
14:10.7
14:15.5
I guess it's not that convenient
14:15.6
14:20.4
to always live in this risk
14:20.5
14:25.3
Right, risk is not convenient in that sense
14:25.4
14:30.2
and the third option is that they can calml wait for somebody
14:30.3
14:35.1
some authority like Metamask Institutional
14:35.2
14:40.0
when the biggest vendor implements this
14:40.1
14:44.9
function for Everscale
14:45.0
14:49.8
but I guess that unfortunately they would have to wait for a bit while.
14:49.9
14:54.7
and because
14:54.8
14:59.6
something very extraordinary should happen
14:59.7
15:04.5
for these conservative providers to actually onboard
15:04.6
15:09.4
Everscale, the blockchain that is on the
15:09.5
15:14.3
three hundred and eighty fourth place?
15:14.4
15:19.2
why would they? maybe they would, but
15:19.3
15:24.1
it will require some time, and I have doubts that
15:24.2
15:29.0
even if they start doing this, they will also look on the market
15:29.1
15:33.9
for the comparable solutions
15:34.0
15:38.8
and they would just buy this solution and adjust it
15:38.9
15:43.7
Of course the technical aspect of Everscale with we're right now would that
15:43.8
15:48.6
they all gonna require time for beginning integration, so I completely understand what you mean
15:48.7
15:53.5
the 4th is
15:53.6
15:58.4
to find an alternative and
15:58.5
16:03.3
a month ago I stumbled upon
16:03.4
16:08.2
the alternatives, and maybe
16:08.3
16:13.1
that's why I started to working on this project
16:13.2
16:18.0
if you know any good alternatives around, please let me know
16:18.1
16:22.9
It sounds like you're definitely developing something which
16:23.0
16:27.8
there is a need for at Everscale firm as far as I can see
16:27.9
16:32.7
so this next slide kinda moves us into more of the overall market
16:32.8
16:37.6
side of things, I donno if you want to quickly walk us through this one?
16:37.7
16:42.5
Yes, so the idea for the this slide was
16:42.6
16:47.4
actually if we have this bere minimum
16:47.5
16:52.3
in the existing solutions, what if we
16:52.4
16:57.2
just implement this bare minimum and sit and wait for companies
16:57.3
17:02.1
to start going into Everscale for their operational activity?
17:02.2
17:07.0
Sounds like a good plan. But actually not because these B2B vendors
17:07.1
17:11.9
do not sit on their ass and they also evolve
17:12.0
17:16.8
and the whole defi
17:16.9
17:21.7
land and landscape evolves
17:21.8
17:26.6
so that they develop new and new of working with financial tools
17:26.7
17:31.5
firstly it was liquidity providing,
17:31.6
17:36.4
then it was marginal farming,
17:36.5
17:41.3
then it was this NFT and cross-chain farming
17:41.4
17:46.2
there were bridges, then there were diferent kinds of protocols
17:46.3
17:51.1
different kinds of networks, and people get confused
17:51.2
17:56.0
and they would like some professionals to manage their money
17:56.1
18:00.9
because they do not want
18:01.0
18:05.8
to continuesly be fed by more and more information
18:05.9
18:10.7
and because they get lost, so they want to have professional brockers
18:10.8
18:15.6
it is the reflection of the mutual funds
18:15.7
18:20.5
in our real life, so people, the lend their money
18:20.6
18:25.4
for the interest
18:25.5
18:30.3
and of course brockers get their percent from
18:30.4
18:35.2
this money for their operations, so from what I see
18:35.3
18:40.1
from the communication with the Gnosis team, I recently had the communication,
18:40.2
18:45.0
the are starting to build the new team which actually focuses on just precisely that
18:45.1
18:49.9
so they have this Gnosis safe which is a B2B tool
18:50.0
18:54.8
and they want to make it work for
18:54.9
18:59.7
the normal users, for the private accounts
18:59.8
19:04.6
and another thing is SuperDAO
19:04.7
19:09.5
they raised one million dollars, seed round with lots of funds
19:09.6
19:14.4
but still it means that this topic
19:14.5
19:19.3
of actually making joint decisions and creating DAO
19:19.4
19:24.2
using smart contracts is vibrant currently
19:24.3
19:29.1
among people so that they easily can
19:29.2
19:34.0
get investments on the one hand and succeed
19:34.1
19:38.9
in implementing the solution that users require on the other
19:39.0
19:43.8
Yeah, of course, well, you've done your homework, always good to say
19:43.9
19:48.7
so we're gonna talk a bit about
19:48.8
19:53.6
the future of Fidosafe very quickly
19:53.7
19:58.5
so I see
19:58.6
20:03.4
two steps as I mentioned on my forum thread,
20:03.5
20:08.3
the first is to actually implement this bare minimum
20:08.4
20:13.2
with transactions, users and settings, so that every bussiness which wants to start
20:13.3
20:18.1
their operations on Everscale can start doing this
20:18.2
20:23.0
with Fidosafe, and step 2 would be to evolve,
20:23.1
20:27.9
to make it DAO
20:28.0
20:32.8
where people can profit from these B2B tools
20:32.9
20:37.7
I see it as
20:37.8
20:42.6
system where everything is transparent
20:42.7
20:47.5
you can see how much money you want to lend
20:47.6
20:52.4
you will see how much money you will get
20:52.5
20:57.3
after some period, of course your money will be blocked
20:57.4
21:02.2
for some time, I guess it would be something
21:02.3
21:07.1
like in real life, when we have only quartely payments
21:07.2
21:12.0
one per quarter and also
21:12.1
21:16.9
this smart contract can
21:17.0
21:21.8
give the transparency
21:21.9
21:26.7
in terms of how much money these brockers have earned
21:26.8
21:31.6
and if it is reasonable to stick to them
21:31.7
21:36.5
or maybe switching to somebody else, like finding another
21:36.6
21:41.4
company or a firm with better stats.
21:41.5
21:46.3
Excellent, thanks, very comprehensive slides
21:46.4
21:51.2
Thank you very much for putting it together and sharing it with us
21:51.3
21:56.1
Let's take it a little more informally
21:56.2
22:01.0
I just wannt know a little more about your background
22:01.1
22:05.9
so you say you're a developer? Not really
22:06.0
22:10.8
So I must have misinterpreted that.
22:10.9
22:15.7
I would say that I'm an enterpreneur,
22:15.8
22:20.6
and what I like to do it actually create
22:20.7
22:25.5
new value, so I had a history of
22:25.6
22:30.4
a few startups, and some of them were
22:30.5
22:35.3
this or that successful
22:35.4
22:40.2
at least I had tracktion on some of them
22:40.3
22:45.1
but maybe did some mistakes so that cannot
22:45.2
22:50.0
bragging about something very familiar that you are all aware of
22:50.1
22:54.9
The only really failure in life is not trying
22:55.0
22:59.8
again so... Yes. So waht were these startups?
22:59.9
23:04.7
Can you give us an idea about these things?
23:04.8
23:09.6
Ah...
23:09.7
23:14.5
I would like not to reveal it, sorry. Oh, no, you don't have to tell what the exact product,
23:14.6
23:19.4
but what areas you were working in? What type of startups? It?
23:19.5
23:24.3
Ok,
23:24.4
23:29.2
Funny enough, they were all B2B services, so that it is my
23:29.3
23:34.1
primary target, I understand
23:34.2
23:39.0
that it is harder to get B2B accounts
23:39.1
23:43.9
but as soon as you acquire them, it is easier in
23:44.0
23:48.8
terms of financials, in terms of statistics, in terms of
23:48.9
23:53.7
everything, in terms of churn especially. yeah!
23:53.8
23:58.6
I've worked in a several sales positions in my past, and obviously B2B
23:58.7
24:03.5
is a much longer pipeline with onboarding, but
24:03.6
24:08.4
when customers are onboarded, there is much more professional relationship
24:08.5
24:13.3
so yeah, that's brilliant. Just to kinda verify that.. was it mostly kind of software as a service, sort of things or?
24:13.4
24:18.2
Yeah,
24:18.3
24:23.1
So you're mostly in a B2B SaaS.
24:23.2
24:28.0
B2B2C SaaS
24:28.1
24:32.9
and so with this project
24:33.0
24:37.8
have you got a team with you, or you're working on your own? You're outsourcing?
24:37.9
24:42.7
How is it working there?
24:42.8
24:47.6
Yeah, currently I work on my own.
24:47.7
24:52.5
but I cannot call myself a developer because actually I
24:52.6
24:57.4
don't have technical education in Computer Science
24:57.5
25:02.3
of course I have a great deal of experience in coding, but
25:02.4
25:07.2
do not have an experience of corporate coding
25:07.3
25:12.1
so that coding in team and this stuff and
25:12.2
25:17.0
one of the reasons also to start this product was to
25:17.1
25:21.9
get acquainted with the blockchain and the technology
25:22.0
25:26.8
and understand how the smart contracts work on Everscale and
25:26.9
25:31.7
it was a kinda learning curve
25:31.8
25:36.6
for me, and the learning curve, so yes, the learning curve for everyone around here I think, I'm still learning every day
25:36.7
25:41.5
Sorry,
25:41.6
25:46.4
Yeah, I can code, and you can see from
25:46.5
25:51.3
the repository that yeah, every line of code was written by me
25:51.4
25:56.2
if you want to spot any refinements
25:56.3
26:01.1
please let me know
26:01.2
26:06.0
Excellent, so all your code is in open source, so everyone can have a look at it. Yeah. That's great to know.
26:06.1
26:10.9
One quick follow-up question from that:
26:11.0
26:15.8
you say "learning", how long have you been in the space?
26:15.9
26:20.7
in crypto currency? just out of interest. in crypto, not that long,
26:20.8
26:25.6
I guess from
26:25.7
26:30.5
You know, the last spike
26:30.6
26:35.4
Maybe from the beginning of this year.
26:35.5
26:40.3
Somewhere there in January I hopped into this market
26:40.4
26:45.2
because everything grew.
26:45.3
26:50.1
I wish I'de went in the market in January I told you. That is fantastic.
26:50.2
26:55.0
So regarding Fidosafe, about cold-heart details
26:55.1
26:59.9
about the product, what have you achieved so far, is it a fully-functioning?
27:00.0
27:04.8
Is it ready to go? Where you are at in kinda
27:04.9
27:09.7
MVP roadmap sort of things?
27:09.8
27:14.6
this bare minimum functionality
27:14.7
27:19.5
has this management
27:19.6
27:24.4
transaction management, user management, session management
27:24.5
27:29.3
and also sending value
27:29.4
27:34.2
and the question of sending value is not ready yet
27:34.3
27:39.1
so with onboarding of this feature
27:39.2
27:44.0
I would say that I would have this bare minimum MVP
27:44.1
27:48.9
or course some bells and whistles need to be added
27:49.0
27:53.8
for example validation checks, notifications
27:53.9
27:58.7
about removal and so on
27:58.8
28:03.6
of course users like and developers do not like to implement
28:03.7
28:08.5
but I think in the nutshell
28:08.6
28:13.4
everything is ready besides the transfer transaction itself
28:13.5
28:18.3
Excellent. Apart from items you've just mentioned,
28:18.4
28:23.2
like you say with the transfer transaction
28:23.3
28:28.1
and all these bells and whistles
28:28.2
28:33.0
what are your immediate plans
28:33.1
28:37.9
in terms of one-two-three months
28:38.0
28:42.8
I would say
28:42.9
28:47.7
... onboarding that kind of thing.
28:47.8
28:52.6
I would say that it would not get into
28:52.7
28:57.5
havily into the development
28:57.6
29:02.4
but rather
29:02.5
29:07.3
I would start trying to communicate with these companies how actually use
29:07.4
29:12.2
this software in different other blockchains and will try to attract them to Everscale
29:12.3
29:17.1
but for this I would need
29:17.2
29:22.0
this software to adhere to basic requirements
29:22.1
29:26.9
that they will need, and firstly is the security
29:27.0
29:31.8
what I would need
29:31.9
29:36.7
once all the code is ready
29:36.8
29:41.6
it to accomplish a number of code audits
29:41.7
29:46.5
and also publish them and be able to
29:46.6
29:51.4
run some campaign among the community to
29:51.5
29:56.3
encourage reporting bugs
29:56.4
30:01.2
if people see them
30:01.3
30:06.1
Excellent. Just to kinda re-iterate for a people who are really slow on technical side like me, obviously Everscale incubator
30:06.2
30:11.0
it has immediate plans looking for projects to list on DappRadar specifically
30:11.1
30:15.9
would you say
30:16.0
30:20.8
that Fidosafe is 90% ready?
30:20.9
30:25.7
once it has the audits and the transfer function added?
30:25.8
30:30.6
Yes, but you must understand that it takes time
30:30.7
30:35.5
Soon is everyone's favorite word
30:35.6
30:40.4
In Everscale and blockchain projects
30:40.5
30:45.3
but if you put a timeline to this again assuming the best case with this?
30:45.4
30:50.2
Ok, let's divide the things into technical -
30:50.3
30:55.1
implementation, development and verification
30:55.2
31:00.0
and in terms of technical completion I guess
31:00.1
31:04.9
we're no longer than a month away from the publication
31:05.0
31:09.8
in terms of the technicals
31:09.9
31:14.7
we'd be looking, yeah, I'm mustoring to myself, but don't worry, carry on
31:14.8
31:19.6
31:19.7
31:24.5
and in terms of adoption and reviews
31:24.6
31:29.4
and some kind of input from the users, I would say it will also require some time
31:29.5
31:34.3
and of course it depends on the community
31:34.4
31:39.2
so that I would rely on the feedback from the community
31:39.3
31:44.1
Yeah, of course feedback loop, that's brilliant. And so,
31:44.2
31:49.0
We're getting through my questions very and very efficiently, but you're very good at this
31:49.1
31:53.9
What would you say gonna be the biggest hurdles, so what's gonna
31:54.0
31:58.8
be the biggest potential road blocks, stops in your path?
31:58.9
32:03.7
32:03.8
32:08.6
I guess the biggest limiting factor is time of course
32:08.7
32:13.5
because I have 9-to-5 job
32:13.6
32:18.4
and it could have some deadlines, I have family
32:18.5
32:23.3
to manage, and this also means that I'm kind of
32:23.4
32:28.2
vulnerable because I can turn to something else
32:28.3
32:33.1
and won't be able to devote much time
32:33.2
32:38.0
to this product by refocusing on
32:38.1
32:42.9
my work, home, my family, etc., so
32:43.0
32:47.8
that I guess this would be the biggest risk
32:47.9
32:52.7
as in solo-founder startups
32:52.8
32:57.6
in general, and the best way to handle it is
32:57.7
33:02.5
to maybe share
33:02.6
33:07.4
the vision of the next steps and build up a team who can also help
33:07.5
33:12.3
Ok, that leads quite nicely, so what exactly are you
33:12.4
33:17.2
looking to get from the Everscale incubator
33:17.3
33:22.1
what help and support do you really need to take this forward
33:22.2
33:27.0
Initially
33:27.1
33:31.9
I would love to have
33:32.0
33:36.8
this problem with the security solved, so that
33:36.9
33:41.7
if it requires some effort from the community members
33:41.8
33:46.6
it would be great as it requires some
33:46.7
33:51.5
costs to perform these audits
33:51.6
33:56.4
also ok, but I would like the community to help me with collecting the
33:56.5
34:01.3
necessary money to accomplish this
34:01.4
34:06.2
so first and foremost in your immediate kinda plan you need some kind of helpie
34:06.3
34:11.1
in terms of auditing costs involved
34:11.2
34:16.0
to be where it needs to be in terms of security. Yes.
34:16.1
34:20.9
the second would be to actually
34:21.0
34:25.8
guarantee to the first users, first commercial users
34:25.9
34:30.7
that this software works as intended, so that I would also like
34:30.8
34:35.6
to have the beta testers program
34:35.7
34:40.5
where people can try it and report whatever they find
34:40.6
34:45.4
for this I would need some PR
34:45.5
34:50.3
to make my product noticed among the people who actually
34:50.4
34:55.2
may need it and be able to
34:55.3
35:00.1
ping me around and join my
35:00.2
35:05.0
Telegram channel or something like that so that they can also contribute
35:05.1
35:09.9
with their ideas, with their features
35:10.0
35:14.8
in terms of the Everscale community
35:14.9
35:19.7
you're speaking with the right man, sure I can help you out as much as possible with that if we go forward
35:19.8
35:24.6
Excellent, so we've got auditing costs, beta testing programs,
35:24.7
35:29.5
these are both the areas where you need support, is there anything else?
35:29.6
35:34.4
Again, immediate.
35:34.5
35:39.3
For immediate I guess yes, for the long-term goals I also
35:39.4
35:44.2
would like to have
35:44.3
35:49.1
this PR support, maybe copywriters help with
35:49.2
35:54.0
articles and publications to forums and catalogs
35:54.1
35:58.9
and maybe
35:59.0
36:03.8
some help with communicating with some external entities
36:03.9
36:08.7
whe trying to helping get started
36:08.8
36:13.6
with this new blockchain
36:13.7
36:18.5
and ultimately when we have a plan for
36:18.6
36:23.4
the next steps, it would be great to also have a help about team building
36:23.5
36:28.3
but of course it is currently
36:28.4
36:33.2
only on the horizon
36:33.3
36:38.1
not the shirt-term goal. Yes, of course, it sounds like you've got quite a solid plan in place
36:38.2
36:43.0
let's go to the speculative side of things
36:43.1
36:47.9
assuming that everything goes through and well with the Everscale incubator
36:48.0
36:52.8
and you receive all the help you need in the shirt term
36:52.9
36:57.7
let's put a rough date on it, where would you see
36:57.8
37:02.6
the product in terms of usage
37:02.7
37:07.5
consumer customer figures that kind of things
37:07.6
37:12.4
one year from now and three years from now, what would be your very optimistic outlook for this?
37:12.5
37:17.3
not very optimistic but yours
37:17.4
37:22.2
I don't wanna you to sound too sunshining you know, your realistically
37:22.3
37:27.1
best-case scenario
37:27.2
37:32.0
Ok, I guess that even if we
37:32.1
37:36.9
lure even one company
37:37.0
37:41.8
you must understand that their operational volumes
37:41.9
37:46.7
are starting from one million dollars, so that
37:46.8
37:51.6
it would be success to me at least
37:51.7
37:56.5
to have even one corporate client that uses this software on the day-to-day basis
37:56.6
38:01.4
if their volume is like
38:01.5
38:06.3
this 1 mln dollars
38:06.4
38:11.2
than the transactional costs would be
38:11.3
38:16.1
in a year
38:16.2
38:21.0
calculation it would be a few
38:21.1
38:25.9
tens of thousands dollars
38:26.0
38:30.8
even this would cover some
38:30.9
38:35.7
budget for bread and butter
38:35.8
38:40.6
yeah
38:40.7
38:45.5
ok, one kind of
38:45.6
38:50.4
stickler problem I could see possibly, so you'd need
38:50.5
38:55.3
help with auditing and beta testing and such, would there be any
38:55.4
39:00.2
insurance liability, accountability issues here because obviously as
39:00.3
39:05.1
I understand it's the big part of the institutional need is
39:05.2
39:10.0
that for this accountability, they don't wanna be responsible for
39:10.1
39:14.9
their own keys and own coins. of course,
39:15.0
39:19.8
I guess nobody in crypto is responsible for anything
39:19.9
39:24.7
and every time you use a product, it has a big
39:24.8
39:29.6
disclaimer that "We are not responsible for anything"
39:29.7
39:34.5
and please do your own research, so I guess for these
39:34.6
39:39.4
these tools it is also be the truth
39:39.5
39:44.3
because in the majority of cases
39:44.4
39:49.2
in the similar products the completed code audits
39:49.3
39:54.1
are basically enough to say that the solution is secure
39:54.2
39:59.0
and then users are invited to have their own research
39:59.1
40:03.9
but all the risks are actually on them
40:04.0
40:08.8
ok, and obviously the crypto currency is
40:08.9
40:13.7
ever-changing regulatory landscape
40:13.8
40:18.6
do you see any issues with it at all coming up?
40:18.7
40:23.5
have you already done your homework in
40:23.6
40:28.4
terms of legal due dilligent side?
40:28.5
40:33.3
No, I didn't, and what I see here
40:33.4
40:38.2
it is of course a regulated activity
40:38.3
40:43.1
and the entities which do these kind of
40:43.2
40:48.0
brockership operations, they require some kind of certificates
40:48.1
40:52.9
they are unders some regulations, definitely
40:53.0
40:57.8
but these regulations normally lie
40:57.9
41:02.7
outside of the software they use, for example
41:02.8
41:07.6
they need to have a brockership license, they need some docs
41:07.7
41:12.5
to keep crypto, to sell and buy crypto, but this doesn't
41:12.6
41:17.4
have any connection to the software they use for performing
41:17.5
41:22.3
their operations at least on the surface, hopefully
41:22.4
41:27.2
Yes, of course a little more deepdigging required just in case
41:27.3
41:32.1
but given your knowledge of the landscape this is
41:32.2
41:37.0
forced down to individual liabilities actually
41:37.1
41:41.9
Brilliant, so what we're gonna do, Norton, is we just gonna take
41:42.0
41:46.8
a very quick two-minute break
41:46.9
41:51.7
I'm gonna refill my coffee, and we're gonna see if anyone in the group has any questions for you
41:51.8
41:56.6
let me just find, too many Telegram groups out there
41:56.7
42:01.5
Incubator, so...
42:01.6
42:06.4
any questions?
42:06.5
42:11.3
right, so don't know if you wanna grab yourself a very quick drink, I just gonna go get my coffee up, and we
42:11.4
42:16.2
come back and see if anyone in the group has any questions and see if any more pop up into my little head
42:16.3
42:21.1
In two minutes, right? Yes, just a couple of minutes. Brilliant, speak to you in a moment.
42:21.2
42:26.0
42:26.1
42:30.9
42:31.0
42:35.8
I've got my coffee filled up, guys, I think...
42:35.9
42:40.7
As far as I can see no questions in the group as of yet, so
42:40.8
42:45.6
I believe it was a pretty comprehensive run through today, yeah, anything you'd like to add?
42:45.7
42:50.5
Oh, I'm really excited about your questions
42:50.6
42:55.4
and I think we've covered everything that I wanted
42:55.5
43:00.3
Thank you very much for this deep and detailed interview, you were great, Ben, thanks.
43:00.4
43:05.2
Thank you.
43:05.3
43:10.1
I'm sure you know I used to do slightly frivolous style of hosting
43:10.2
43:15.0
it's been nice having you in a more serious conversation
43:15.1
43:19.9
which is good to expand, it's been a brilliant meeting, Norton,
43:20.0
43:24.8
and I'm very excited to find out how your progect progresses
43:24.9
43:29.7
you have a great rest of your day, thank you for listending a lot
43:29.8
43:32.9
have a great day