Dash Evan Duffield at LaBitConf Mexico City Dec 2015.en

1
00:00:06,466 --> 00:00:08,175
Very interesting concept...

2
00:00:08,175 --> 00:00:10,668
It's mind boggling how much is actually going on

3
00:00:10,668 --> 00:00:12,068
in the Bitcoin ecosystem

4
00:00:12,068 --> 00:00:16,548
It's actually hard to keep track of.

5
00:00:16,548 --> 00:00:19,493
So I'm going to be talking about

6
00:00:19,493 --> 00:00:23,593
Bitcoin and a two tiered network.

7
00:00:23,593 --> 00:00:27,255
Um, where is my???....

8
00:00:27,255 --> 00:00:30,445
...laughter....

9
00:00:30,445 --> 00:00:33,035
Ah, here we go... Perfect.

10
00:00:33,035 --> 00:00:36,285
So, I'm Evan Duffield, I'm a software engineer

11
00:00:36,285 --> 00:00:38,455
I've been programming since I was 15 (years old)

12
00:00:38,455 --> 00:00:44,625
And as a little bit of background, I'm really interesting in finance, economics,

13
00:00:44,625 --> 00:00:49,515
machine learning, and these types of things.

14
00:00:49,515 --> 00:00:52,439
So when I got into Bitcoin, it was just fascinating

15
00:00:52,439 --> 00:00:54,999
it captivated my interest

16
00:00:54,999 --> 00:00:57,219
And what I wanted to do was

17
00:00:57,219 --> 00:01:01,139
I wanted to tinker with Bitcoin at like a really low level

18
00:01:01,139 --> 00:01:03,559
I wanted to mess with the protocol

19
00:01:03,559 --> 00:01:05,179
and I wanted to test things that

20
00:01:05,179 --> 00:01:08,489
you really can only do with your own currency.

21
00:01:08,489 --> 00:01:10,279
And so, what we've been doing

22
00:01:10,279 --> 00:01:13,539
is really adventurous things that

23
00:01:13,539 --> 00:01:17,539
you know you could never get into the Bitcoin project.

24
00:01:17,539 --> 00:01:19,669
Because they're just too dangerous.

25
00:01:19,669 --> 00:01:21,799
But with a small little network like this

26
00:01:21,799 --> 00:01:24,269
you can do things, because we can be

27
00:01:24,269 --> 00:01:26,929
really nimble with what we do.

28
00:01:26,929 --> 00:01:29,409
And so, what have we been doing?

29
00:01:29,409 --> 00:01:31,169
Um, some of the projects have been

30
00:01:31,169 --> 00:01:33,609
what we call a two tiered network,

31
00:01:33,609 --> 00:01:36,059
As opposed to a single tiered network

32
00:01:36,059 --> 00:01:37,749
on the Bitcoin network.

33
00:01:37,749 --> 00:01:40,059
and then decentralized funding and

34
00:01:40,059 --> 00:01:42,759
decentralized governance.

35
00:01:42,759 --> 00:01:45,679
So how does that work exactly?

36
00:01:45,679 --> 00:01:48,959
Well, if you think of Bitcoin like a job network,

37
00:01:48,959 --> 00:01:52,419
I would argue that it's actually the first

38
00:01:52,419 --> 00:01:55,049
truly decentralized job network.

39
00:01:55,049 --> 00:01:56,869
But there's only really one job,

40
00:01:56,869 --> 00:01:58,779
and it's mining currently.

41
00:01:58,779 --> 00:02:01,069
And so, what we did was we added a new job.

42
00:02:01,069 --> 00:02:05,069
And we call these people Masternode Operators

43
00:02:05,069 --> 00:02:08,039
and they run our infrastructure for us.

44
00:02:08,039 --> 00:02:10,029
And basically what we do is we

45
00:02:10,029 --> 00:02:13,449
require that they run specific types of hardware,

46
00:02:13,449 --> 00:02:18,159
and then we can actually rely on that hardware.

47
00:02:18,159 --> 00:02:20,679
So, how has it been working for us?

48
00:02:20,679 --> 00:02:22,679
I would say amazingly well.

49
00:02:22,679 --> 00:02:26,209
We've added hundreds of these Masternodes

50
00:02:26,209 --> 00:02:29,599
which are full nodes, which service the network

51
00:02:29,599 --> 00:02:32,719
over the past 12 months. We have

52
00:02:32,719 --> 00:02:38,348
3400 currently and about 4500 full nodes.

53
00:02:38,348 --> 00:02:41,368
As opposed to the Bitcoin network which has about

54
00:02:41,368 --> 00:02:45,965
5800. And so we have a comparable infrastructure

55
00:02:45,965 --> 00:02:48,865
to the bitcoin network, which is pretty amazing because

56
00:02:48,865 --> 00:02:53,035
we are at about 1/400 of the size.

57
00:02:53,035 --> 00:02:56,192
So how do you run one of these Masternodes

58
00:02:56,192 --> 00:02:57,502
on our network? (audio fades)

59
00:02:57,502 --> 00:03:00,012
Well, all you do is buy some coins....

60
00:03:00,012 --> 00:03:02,502
these nodes are collateralize,

61
00:03:02,502 --> 00:03:05,342
which means that they can not be faked.

62
00:03:05,342 --> 00:03:08,412
And all you do then is you configure your whole node...

63
00:03:08,412 --> 00:03:10,602
and then join the second tier.

64
00:03:10,602 --> 00:03:13,382
And you get paid, so you get compensated

65
00:03:13,382 --> 00:03:17,742
and you use that money to pay for the cost of the server

66
00:03:17,742 --> 00:03:21,082
And, the neat thing about the collateralize second tier

67
00:03:21,082 --> 00:03:24,502
is that you can do really cool things.

68
00:03:24,502 --> 00:03:26,882
Based off of that collateral,

69
00:03:26,882 --> 00:03:29,632
there is 1000 dash and that has a public key

70
00:03:29,632 --> 00:03:33,032
And the public key has a private key that only you know.

71
00:03:33,032 --> 00:03:36,332
So you can sign messages to the network.

72
00:03:36,332 --> 00:03:39,892
You have a secure communication protocol on the

73
00:03:39,892 --> 00:03:44,522
second tier and we implement decentralized voting with that.

74
00:03:44,522 --> 00:03:56,434
With the decentralized voting (sorry.... mic issues...)

75
00:03:56,434 --> 00:04:01,024
Yah, good to know - (laugh)

76
00:04:01,024 --> 00:04:04,524
It is on, Ok, so

77
00:04:04,524 --> 00:04:09,004
With the second tier, we have a collateralize full node network

78
00:04:09,004 --> 00:04:11,184
There we go, that's a lot better...

79
00:04:11,184 --> 00:04:12,794
Now I can hear it (laughs)

80
00:04:12,794 --> 00:04:16,534
And basically, we have thousands of these full nodes

81
00:04:16,534 --> 00:04:20,874
and each of them have 1000 dash collateral tied to them.

82
00:04:20,874 --> 00:04:24,324
That collateral has a public key and a private key.

83
00:04:24,324 --> 00:04:29,004
And so the public key is known by the network

84
00:04:29,004 --> 00:04:30,864
The private key is only known by the person

85
00:04:30,864 --> 00:04:34,554
running that full node, which is running as a Masternode.

86
00:04:34,554 --> 00:04:36,444
So what do you do with this?

87
00:04:36,444 --> 00:04:38,744
You can do interesting things, such as

88
00:04:38,744 --> 00:04:40,914
implementing decentralized voting,

89
00:04:40,914 --> 00:04:43,634
So imagine thousands of these collateralize nodes

90
00:04:43,634 --> 00:04:46,554
voting on topics on the network.

91
00:04:46,554 --> 00:04:49,564
Then you can do even more interesting things

92
00:04:49,564 --> 00:04:52,764
like, you can build decentralized funding.

93
00:04:52,764 --> 00:04:55,584
So what if you allocate a piece of the block reward

94
00:04:55,584 --> 00:04:59,174
and then you have people that are running these nodes

95
00:04:59,174 --> 00:05:01,774
voting on where to send the money to.

96
00:05:01,774 --> 00:05:05,734
and so, you could propose things to the network and get them paid.

97
00:05:05,737 --> 00:05:07,837
Um, and then you can also govern the network.

98
00:05:07,837 --> 00:05:11,627
And, you could answer questions, pretty much instantaniously,

99
00:05:11,627 --> 00:05:15,777
about what direction the network should go in.

100
00:05:15,777 --> 00:05:19,777
So here is our decentralized governance and funding system.

101
00:05:19,777 --> 00:05:23,167
And we've only had this for 3 months now.

102
00:05:23,167 --> 00:05:25,897
And over the 3 months, we've funded 3

103
00:05:25,897 --> 00:05:30,077
different conferences, one in Mexico, one in Florida and

104
00:05:30,077 --> 00:05:32,765
one in the Netherlands.

105
00:05:32,765 --> 00:05:35,315
And it actually paid for our airfair, for the

106
00:05:35,315 --> 00:05:38,625
hotels, and things like that because the

107
00:05:38,625 --> 00:05:41,135
people that are promoting the currency or

108
00:05:41,135 --> 00:05:43,905
doing work for it shouldn't have to bare the cost

109
00:05:43,905 --> 00:05:46,255
of doing it themselves. And this stuff is

110
00:05:46,255 --> 00:05:49,505
actually paid directly from the blockchain.

111
00:05:49,505 --> 00:05:52,675
Also, we bought a new website,

112
00:05:52,675 --> 00:05:55,555
dash.org, from the blockchain itself.

113
00:05:55,555 --> 00:05:58,045
I think it's actually the first domain to ever

114
00:05:58,045 --> 00:06:01,445
be purchased directly from a blockchain.

115
00:06:01,445 --> 00:06:03,095
And we fund our business development

116
00:06:03,095 --> 00:06:05,115
with this method.

117
00:06:05,115 --> 00:06:08,745
So, how could you apply something like this to Bitcoin?

118
00:06:08,745 --> 00:06:11,815
Well, I think first you've got to imagine

119
00:06:11,815 --> 00:06:14,115
what makes the perfect bitcoin?

120
00:06:14,115 --> 00:06:16,325
And I don't know the answer to how

121
00:06:16,325 --> 00:06:19,255
the bitcoin developers or the community

122
00:06:19,255 --> 00:06:21,655
would want to use this technology, but

123
00:06:21,655 --> 00:06:23,935
I just want to open a conversation about,

124
00:06:23,935 --> 00:06:25,895
you know, what would it be like if they

125
00:06:25,895 --> 00:06:27,785
had decentralized funding and decentralized

126
00:06:27,785 --> 00:06:31,345
governance. It could be pretty neat.

127
00:06:31,345 --> 00:06:34,205
There's definitely an issue with the

128
00:06:34,205 --> 00:06:36,135
full node relationship and the

129
00:06:36,135 --> 00:06:38,305
transaction volume that the

130
00:06:38,305 --> 00:06:40,605
network is doing. As transaction volumes

131
00:06:40,605 --> 00:06:44,745
rise, the full nodes actually fall off.

132
00:06:44,745 --> 00:06:47,695
And with a second tier, you automatically

133
00:06:47,695 --> 00:06:50,025
fix this issue.

134
00:06:50,025 --> 00:06:52,175
And so then, what else do you get?

135
00:06:52,175 --> 00:06:54,535
We want to scale the Bitcoin ecosystem

136
00:06:54,535 --> 00:06:56,575
and we want to be able to support millions

137
00:06:56,575 --> 00:06:58,185
of mobile devices.

138
00:06:58,185 --> 00:07:01,385
So I've come up with a couple of strategies

139
00:07:01,385 --> 00:07:04,785
of doing this with a two tiered network.

140
00:07:04,785 --> 00:07:08,785
So you want to support millions of these mobile devices

141
00:07:08,785 --> 00:07:12,285
and you could actually do it with a decentralized

142
00:07:12,285 --> 00:07:14,805
SPV installation.

143
00:07:14,805 --> 00:07:17,235
What if you had all of the second tier nodes

144
00:07:17,235 --> 00:07:18,745
running SPV?

145
00:07:18,745 --> 00:07:21,295
And then you point a round robin DNS

146
00:07:21,295 --> 00:07:23,715
at this second tier?

147
00:07:23,715 --> 00:07:25,985
And then now, you have thousands of them

148
00:07:25,985 --> 00:07:28,875
bearing the load of the entire network.

149
00:07:28,875 --> 00:07:31,235
And then you could also have decentralized funding

150
00:07:31,235 --> 00:07:34,675
like we're using, or decentralized governance.

151
00:07:34,675 --> 00:07:36,855
You could probably even implement Bitcoin

152
00:07:36,855 --> 00:07:40,235
Lightening in a similar fashion.

153
00:07:40,235 --> 00:07:42,695
I was also thinking about governance.

154
00:07:42,695 --> 00:07:46,235
What if you proposed the BIPs to the network

155
00:07:46,235 --> 00:07:49,575
via the second tier and have the vote on them?

156
00:07:49,575 --> 00:07:52,245
So then we would have an instantaneous way

157
00:07:52,245 --> 00:07:54,565
of telling how the network feels about

158
00:07:54,565 --> 00:07:56,425
individual proposals.

159
00:07:56,425 --> 00:07:59,525
And, this, this could be... it's sybil proof

160
00:07:59,525 --> 00:08:02,095
because the second tier is collateralized.

161
00:08:02,095 --> 00:08:04,405
It's instantaneous and then the network

162
00:08:04,405 --> 00:08:08,405
has an immediate direction that it can go in.

163
00:08:08,405 --> 00:08:10,515
They could also have a funding system

164
00:08:10,515 --> 00:08:12,765
like we have and they could actually pay

165
00:08:12,765 --> 00:08:15,295
for the core development directly from

166
00:08:15,295 --> 00:08:16,535
the blockchain.

167
00:08:16,535 --> 00:08:19,755
Currently it's financed by grant money

168
00:08:19,755 --> 00:08:22,485
and it used to be financed by donations

169
00:08:22,485 --> 00:08:25,685
and from a foundation. So I can see this

170
00:08:25,685 --> 00:08:29,715
as being a vast improvement.

171
00:08:29,715 --> 00:08:33,815
Here is the decentralized SPV idea.

172
00:08:33,815 --> 00:08:37,295
All you do is you point that round robin DNS

173
00:08:37,295 --> 00:08:39,275
at the second tier, and then you have the

174
00:08:39,275 --> 00:08:42,445
mobile wallets point at the second tier.

175
00:08:42,445 --> 00:08:45,125
And then, it should scale, because it's thousands

176
00:08:45,125 --> 00:08:47,565
of servers.

177
00:08:47,565 --> 00:08:50,545
So how would they do this?

178
00:08:50,545 --> 00:08:52,495
I don't really know, they would have to

179
00:08:52,495 --> 00:08:54,845
plan and implement it and these are some

180
00:08:54,845 --> 00:08:57,225
of the smartest people I've ever met, so I'm

181
00:08:57,225 --> 00:08:59,685
sure they could do an amazing job.

182
00:08:59,685 --> 00:09:02,955
It does require that part of the block reward gets

183
00:09:02,955 --> 00:09:05,335
allocated for the second tier so that it

184
00:09:05,335 --> 00:09:09,445
compensate them, and it requires that part

185
00:09:09,445 --> 00:09:11,775
of the block reward would get allocated to

186
00:09:11,775 --> 00:09:14,315
decentralized funding as well.

187
00:09:14,315 --> 00:09:17,025
And then you trustlessly detect and pay the

188
00:09:17,025 --> 00:09:19,465
Masternodes that are on the system.

189
00:09:19,465 --> 00:09:21,625
And then you should be able to scale rather

190
00:09:21,625 --> 00:09:23,235
efficiently.

191
00:09:23,235 --> 00:09:25,375
So, what's the conclusion? I would say

192
00:09:25,375 --> 00:09:27,515
that we should start talking about this and

193
00:09:27,515 --> 00:09:31,245
see what the Bitcoin community thinks about

194
00:09:31,245 --> 00:09:37,455
adopting something like this on the Bitcoin network.

195
00:09:37,455 --> 00:09:41,455
As a short announcement, we're opensourcing Dash

196
00:09:41,455 --> 00:09:45,215
Evolution today which.. it's basically what I've

197
00:09:45,215 --> 00:09:48,005
been talking about times 100.

198
00:09:48,005 --> 00:09:51,495
We want to implement something like a

199
00:09:51,495 --> 00:09:53,905
decentralized paypal on top of our

200
00:09:53,905 --> 00:09:56,945
decentralized currency. Where you could

201
00:09:56,945 --> 00:10:00,945
basically log into your mobile wallet

202
00:10:00,945 --> 00:10:03,385
and then it would connect to the second tier.

203
00:10:03,385 --> 00:10:06,355
We would store all of the needed information

204
00:10:06,355 --> 00:10:09,545
that you use on the second tier encrypted, such as

205
00:10:09,545 --> 00:10:11,705
friends lists, and things like that.

206
00:10:11,705 --> 00:10:14,805
So I could friend somebody, and I would send them

207
00:10:14,805 --> 00:10:17,925
5 of my next public keys to use, and they would send me

208
00:10:17,925 --> 00:10:21,085
5 of their next public keys, then I could literally just click their

209
00:10:21,085 --> 00:10:25,555
name, click, I want to send you 2 dash, and then click send.

210
00:10:25,555 --> 00:10:28,065
And I think that's a pretty powerful feature if it's

211
00:10:28,065 --> 00:10:30,365
completely network wide.

212
00:10:30,365 --> 00:10:33,335
And that's the type of stuff that we're building into

213
00:10:33,335 --> 00:10:35,325
Dash Evolution. So if you're interested in that,

214
00:10:35,325 --> 00:10:39,625
go to dashevolution.com and check out the new papers.

215
00:10:39,625 --> 00:10:48,505
That's it, thanks, thanks alot. (clapping)

216
00:10:48,505 --> 00:10:51,395
(host) I will do, like, try to summarize

217
00:10:51,395 --> 00:10:54,365
because all of these are very like high level,

218
00:10:54,365 --> 00:10:58,265
or very complex ideas. But, my remarks, and then

219
00:10:58,265 --> 00:11:00,215
I will give the microphone to you

220
00:11:00,215 --> 00:11:02,165
so you can correct me or

221
00:11:02,165 --> 00:11:07,089
expand my assumptions, but um...

222
00:11:07,089 --> 00:11:11,419
Well, Evan, you have developed a consensus

223
00:11:11,419 --> 00:11:14,779
model, ah, a governance model for a

224
00:11:14,779 --> 00:11:17,309
cryptocurrency and an incentive model

225
00:11:17,309 --> 00:11:20,509
that is governed by that consensus model

226
00:11:20,509 --> 00:11:23,999
that you created, and I think that's amazing

227
00:11:23,999 --> 00:11:26,649
and that's something that Bitcoin is lacking

228
00:11:26,649 --> 00:11:30,649
in terms of giving incentives to full nodes

229
00:11:30,649 --> 00:11:33,399
that are the auditors of the network

230
00:11:33,399 --> 00:11:36,009
so I think you're finding or trying to find a

231
00:11:36,009 --> 00:11:40,189
solution to a very big systemic risk of

232
00:11:40,189 --> 00:11:44,299
Bitcoin, so I think it's very interesting,

233
00:11:44,299 --> 00:11:48,299
very exciting to see what you have done.

234
00:11:48,299 --> 00:11:51,419
And that consensus also applies to the

235
00:11:51,419 --> 00:11:53,449
development and to the evolution of

236
00:11:53,449 --> 00:11:56,429
your own platforms. So that's my summerizing

237
00:11:56,429 --> 00:11:59,489
of you and then you will expand on it.

238
00:11:59,489 --> 00:12:03,179
Alexandre, you were talking about doing

239
00:12:03,179 --> 00:12:07,179
a secure, like a cold storage using an old

240
00:12:07,179 --> 00:12:12,329
smart phone, a not just smart but an old phone

241
00:12:12,329 --> 00:12:14,659
(Alexandre) "Airplane Mode phone!"

242
00:12:14,659 --> 00:12:18,129
Yah, like a Nokia 1100, something like that?

243
00:12:18,129 --> 00:12:22,129
That's interesting, the hacker in me craves for it.

244
00:12:22,129 --> 00:12:27,959
And then, I realize what your doing Louis, you're

245
00:12:27,959 --> 00:12:31,579
creating a layer, you're creating a layer on top

246
00:12:31,579 --> 00:12:35,579
of the cryptocurrencies layer. I think this layer

247
00:12:35,579 --> 00:12:40,629
(stuff?) concept is growing everywhere, I mean

248
00:12:40,629 --> 00:12:43,579
we are wondering that Bitcoin is just one layer

249
00:12:43,579 --> 00:12:47,579
but we have to build like in the OSi model

250
00:12:47,579 --> 00:12:51,579
I mean, we have to build layers on top of it

251
00:12:51,579 --> 00:12:54,409
whether it's Bitcoin or other cryptocurrency but

252
00:12:54,409 --> 00:12:56,949
stop trying to make Bitcoin do everything.

253
00:12:56,949 --> 00:12:57,969
(Luis) exactly.

254
00:12:57,969 --> 00:13:00,019
(Host) Relying on Bitcoin for what it does well.

255
00:13:00,019 --> 00:13:02,459
(Luis) The ecosystem is growing from down

256
00:13:02,459 --> 00:13:05,689
like in several layers of protocols that's

257
00:13:05,689 --> 00:13:08,679
started from the top down. with the idea

258
00:13:08,679 --> 00:13:10,369
of the strong segmentation - that's why we

259
00:13:10,369 --> 00:13:13,759
build all this stuff with plugins so as to...

260
00:13:13,759 --> 00:13:17,559
(Host) Yah, let me summerize, then you will talk.

261
00:13:17,559 --> 00:13:20,629
I have the power now! (laughter)

262
00:13:20,629 --> 00:13:23,389
So, as I was saying, I think what was exciting about you

263
00:13:23,389 --> 00:13:26,876
is your project is this concept of building a layer

264
00:13:26,876 --> 00:13:29,806
on top of the layers that exist and bringing more

265
00:13:29,806 --> 00:13:33,806
functionality and I think you share with Ira

266
00:13:33,806 --> 00:13:37,116
this concept of bringing in (a) framework.

267
00:13:37,116 --> 00:13:38,976
That's something we will see more and more

268
00:13:38,976 --> 00:13:42,026
happening, I mean building frameworks so

269
00:13:42,026 --> 00:13:45,356
others can focus on the last layer that is the

270
00:13:45,356 --> 00:13:47,506
one that interacts with users.

271
00:13:47,506 --> 00:13:51,826
So I think that's very interesting, I will read deeper

272
00:13:51,826 --> 00:13:54,866
into your platform, I really like fermat

273
00:13:54,866 --> 00:13:59,506
And finally, what Ira is saying, I live it in my own

274
00:13:59,506 --> 00:14:03,076
flesh. Because Rootstock is the kind of project

275
00:14:03,076 --> 00:14:05,676
that everybody wants, everybody loves, but

276
00:14:05,676 --> 00:14:11,154
it's difficult to fund. Because, the business model

277
00:14:11,154 --> 00:14:13,864
is a complex one. I mean there is a business model

278
00:14:13,864 --> 00:14:17,024
but it's a very complex one. So I think we have

279
00:14:17,024 --> 00:14:20,404
to find a solution to keep creating the tools that

280
00:14:20,404 --> 00:14:22,684
bring more value to the ecosystem, to the

281
00:14:22,684 --> 00:14:26,054
decentralized ecosystem and find a way, so

282
00:14:26,054 --> 00:14:30,204
maybe, and that's maybe a long shot, but taking

283
00:14:30,204 --> 00:14:34,054
something of what Evan did, and putting it into what you're

284
00:14:34,054 --> 00:14:38,054
building, we can find a solution. So I think,

285
00:14:38,054 --> 00:14:40,554
that's my summarizing, I hope it helps the ones

286
00:14:40,554 --> 00:14:42,904
that are not so technical because I think it's

287
00:14:42,904 --> 00:14:45,364
difficult to grasp (what) all these guys were

288
00:14:45,364 --> 00:14:49,174
talking about. And now you have 30 seconds

289
00:14:49,174 --> 00:14:52,254
to wrap up, to correct me, to expand....

290
00:14:52,254 --> 00:14:56,254
(Ira) I'd like to use my 30 seconds to agree with you.

291
00:14:56,254 --> 00:15:00,834
I think we're all working on very similar things,

292
00:15:00,834 --> 00:15:02,844
we're all definitely working towards the same

293
00:15:02,844 --> 00:15:05,504
goals, and I'm very excited to... I didn't know

294
00:15:05,504 --> 00:15:07,574
about any of your... well, I've known about

295
00:15:07,574 --> 00:15:09,894
Dash for a while, but I learned a lot more,

296
00:15:09,894 --> 00:15:13,014
and I'm just excited to work more with you guys.

297
00:15:13,014 --> 00:15:16,354
we're making it happen, so...

298
00:15:16,354 --> 00:15:18,954
(Evan) It's, It's been interesting meeting everybody

299
00:15:18,954 --> 00:15:22,954
because I've found the same project being run by

300
00:15:22,954 --> 00:15:26,244
different people multiple times so we're all after

301
00:15:26,244 --> 00:15:28,094
the same thing, just in completely different

302
00:15:28,094 --> 00:15:31,234
ways and I think now is the time that you figure

303
00:15:31,234 --> 00:15:33,894
out the best possible way to do it, and then we

304
00:15:33,894 --> 00:15:37,204
follow that path. And I think that's really the end

305
00:15:37,204 --> 00:15:39,564
goal.

306
00:15:39,564 --> 00:15:41,494
(Alexandre) Yah, I think we are reaching

307
00:15:41,494 --> 00:15:44,234
the end of the beginning where the infrastructure

308
00:15:44,234 --> 00:15:47,684
will be completely ready. And we're very very

309
00:15:47,684 --> 00:15:53,014
close now. And it's still- this is something I used

310
00:15:53,014 --> 00:15:55,854
to talk about back in 2010, I mean people

311
00:15:55,854 --> 00:15:58,884
thought I was talking about like a "Farmville" money.

312
00:15:58,884 --> 00:16:02,074
And still, that's what the public thinks we're

313
00:16:02,074 --> 00:16:05,004
talking about, Farmville money. You know, we buy a

314
00:16:05,004 --> 00:16:08,234
new house for Farmville, they still don't understand

315
00:16:08,234 --> 00:16:11,864
the military grade cryptography, and the infrastructure

316
00:16:11,864 --> 00:16:17,614
that's been built silently over these years.

317
00:16:17,614 --> 00:16:21,204
(Luis) Ok, I will agree with you. Basically, what

318
00:16:21,204 --> 00:16:24,614
we had in mind was to build something to enable

319
00:16:24,614 --> 00:16:28,094
a strong segmentation in order to give each possible

320
00:16:28,094 --> 00:16:32,214
user a custom tailored solution. Not done by

321
00:16:32,214 --> 00:16:34,934
ourselves, but by letting other people by reusing these

322
00:16:34,934 --> 00:16:38,934
components to find niches of user interfaces

323
00:16:38,934 --> 00:16:41,614
or functionality that any segments in the world

324
00:16:41,614 --> 00:16:45,614
can use. Basically, so we build from the top down,

325
00:16:45,614 --> 00:16:48,764
until we find the protocols that we need, yah, down there.

326
00:16:48,764 --> 00:16:50,464
We, we find kind of an empty space within the

327
00:16:50,464 --> 00:16:51,924
ecosystem.

328
00:16:51,924 --> 00:16:56,564
(host) Ok, thank you very much, a big applause for the panel...

329
00:16:56,564 --> 00:17:00,564
(applause)