-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathcontribute-to-the-protocol.html
610 lines (359 loc) · 25.3 KB
/
contribute-to-the-protocol.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="">
<meta name="keywords" content=" governance, security program, Bitmark Upgrade Proposal">
<title>Contribute to the Protocol | Bitmark Documentation</title>
<link rel="stylesheet" href="/css/syntax.css">
<link rel="stylesheet" type="text/css" href="/css/font-awesome.min.css">
<!--<link rel="stylesheet" type="text/css" href="/css/bootstrap.min.css">-->
<link rel="stylesheet" href="/css/modern-business.css">
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="/css/bootstrap.min.3.3.7.css" crossorigin="anonymous">
<link rel="stylesheet" href="/css/customstyles.css">
<link rel="stylesheet" href="/css/boxshadowproperties.css">
<!-- most color styles are extracted out to here -->
<link rel="stylesheet" href="/css/theme-blue.css">
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js"></script>
<script src="/js/jquery.navgoco.min.js"></script>
<!-- Latest compiled and minified JavaScript -->
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>
<!-- Anchor.js -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/4.2.0/anchor.min.js"></script>
<script src="/js/toc.js"></script>
<script src="/js/customscripts.js"></script>
<link rel="shortcut icon" href="/assets/images/favicon.ico">
<link rel="stylesheet" href="/css/uikit.min.css" />
<script src="/js/uikit.min.js"></script>
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
<![endif]-->
<link rel="alternate" type="application/rss+xml" title="docs" href="/feed.xml">
<!-- <script>
$(document).ready(function() {
// Initialize navgoco with default options
$("#mysidebar").navgoco({
caretHtml: '',
accordion: false,
openClass: 'active', // open
save: false, // leave false or nav highlighting doesn't work right
cookie: {
name: 'navgoco',
expires: false,
path: '/'
},
slide: {
duration: 250,
easing: 'swing'
}
});
// expand first level at indexes [0,3,7]
$("#mysidebar").navgoco('toggle', true, 0, 3, 7);
$("#collapseAll").click(function(e) {
e.preventDefault();
$("#mysidebar").navgoco('toggle', false);
});
$("#expandAll").click(function(e) {
e.preventDefault();
$("#mysidebar").navgoco('toggle', true);
});
});
</script> -->
<script>
$(function () {
$('[data-toggle="tooltip"]').tooltip()
})
</script>
<script>
$(document).ready(function() {
$("#tg-sb-link").click(function() {
// $("#tg-sb-sidebar").toggle();
$("#tg-sb-content").toggleClass('col-md-8');
$("#tg-sb-content").toggleClass('col-md-12');
$("#tg-sb-icon").toggleClass('fa-toggle-on');
$("#tg-sb-icon").toggleClass('fa-toggle-off');
});
});
</script>
</head>
<body>
<!-- Navigation -->
<nav class="navbar navbar-inverse navbar-fixed-top">
<div class="container topnavlinks">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/index.html"><span class="projectTitle home-logo">Bitmark<!-- <img src="/assets/images/Bitmark_Logo-desktop_white.svg" alt="Bitmark logo"/> --><!-- Home --></span></a>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<!-- toggle sidebar button -->
<!-- <li><a id="tg-sb-link" href="#"><i id="tg-sb-icon" class="fa fa-toggle-on"></i> Nav</a></li> -->
<!-- entries without drop-downs appear here -->
<li><a href="https://registry.bitmark.com/" target="_blank" rel="noopener">Registry</a></li>
<li><a href="https://bitmark.com/products/bitmark-protocol/faq/" target="_blank" rel="noopener">FAQ</a></li>
<!-- entries with drop-downs appear here -->
<!-- conditional logic to control which topnav appears for the audience defined in the configuration file.-->
<!--
<li>
<a class="email" title="Submit feedback" href="#" target="_blank" onclick="javascript:window.location='mailto:[email protected]?subject=Bitmark Inc feedback&body=I have some feedback about the Contribute to the Protocol page: ' + window.location.href;"><i class="fa fa-envelope-o"></i> Need help?</a>
</li>
-->
<!--comment out this block if you want to hide search-->
<li>
<!--start search-->
<div id="search-demo-container">
<input type="text" id="search-input" placeholder="search...">
<ul id="results-container"></ul>
</div>
<script src="/js/jekyll-search.js" type="text/javascript"></script>
<script type="text/javascript">
SimpleJekyllSearch.init({
searchInput: document.getElementById('search-input'),
resultsContainer: document.getElementById('results-container'),
dataSource: '/search.json',
searchResultTemplate: '<li><a href="{url}" title="Contribute to the Protocol">{title}</a></li>',
noResultsText: 'No results found.',
limit: 10,
fuzzy: true,
})
</script>
<!--end search-->
</li>
</ul>
</div>
</div>
<!-- /.container -->
</nav>
<!-- Page Content -->
<div class="container">
<div id="main">
<!-- Content Row -->
<div class="">
<!-- Sidebar Column -->
<div class="col-md-4" id="tg-sb-sidebar">
<ul id="mysidebar" class="nav">
<li class="sidebarTitle"> </li>
<li>
<a class="sidebar-title" title="Register & Control data" href="#">Register & Control data</a>
<ul class="sidebar-list">
<li><a title="Register data" href="/register-and-control-data/register-data"><b>Register data</b></a></li>
<li><a title="Control access" href="/register-and-control-data/control-access"><b>Control access</b></a></li>
<li><a title="Transfer rights" href="/register-and-control-data/transfer-rights"><b>Transfer rights</b></a></li>
<li><a title="Share rights" href="/register-and-control-data/share-rights"><b>Share rights</b></a></li>
<li><a title="Run a Node" href="/register-and-control-data/run-a-node"><b>Run a Node</b></a></li>
</ul>
</li>
<li>
<a class="sidebar-title" title="Explore the Protocol Docs" href="#">Explore the Protocol Docs</a>
<ul class="sidebar-list">
<li><a title="Blockchain Overview" href="/explore-the-protocol-docs/blockchain-overview"><b>Blockchain Overview</b></a></li>
<li><a title="Block Validation and Synchronization" href="/explore-the-protocol-docs/block-verification-and-synchronization"><b>Block Validation and Synchronization</b></a></li>
<li><a title="Block Mining" href="/explore-the-protocol-docs/block-mining"><b>Block Mining</b></a></li>
<li><a title="Payment Verification" href="/explore-the-protocol-docs/payment-verification"><b>Payment Verification</b></a></li>
<li><a title="Storage Databases" href="/explore-the-protocol-docs/storage-databases"><b>Storage Databases</b></a></li>
<li><a title="Blockchain Security" href="/explore-the-protocol-docs/blockchain-security"><b>Blockchain Security</b></a></li>
<li><a title="RPC Communication" href="/explore-the-protocol-docs/rpc-communication"><b>RPC Communication</b></a></li>
<li><a title="Glossary" href="/explore-the-protocol-docs/glossary"><b>Glossary</b></a></li>
</ul>
</li>
<li>
<a class="sidebar-title" title="Read our Papers" href="#">Read our Papers</a>
<ul class="sidebar-list">
<li><a title="Bitmark versus Ethereum" href="/read-our-papers/bitmark-eth-comparison"><b>Bitmark versus Ethereum</b></a></li>
<li><a title="White Papers" href="/read-our-papers/white-papers"><b>White Papers</b></a></li>
</ul>
</li>
<li>
<a class="sidebar-title" title="Contribute to the Protocol" href="#">Contribute to the Protocol</a>
<ul class="sidebar-list">
<li class="active"><a title="Contribute to the Protocol" href="/contribute-to-the-protocol"><b>Contribute to the Protocol</b></a></li>
</ul>
</li>
<li>
<a class="sidebar-title" title="Browse our FAQ" href="#">Browse our FAQ</a>
<ul class="sidebar-list">
<li><a title="Bitmark Protocol FAQ" href="/browse-our-faq/bitmark-protocol-faq"><b>Bitmark Protocol FAQ</b></a></li>
</ul>
</li>
<!-- if you aren't using the accordion, uncomment this block:
<p class="external">
<a href="#" id="collapseAll">Collapse All</a> | <a href="#" id="expandAll">Expand All</a>
</p>
-->
</ul>
<!-- this highlights the active parent class in the navgoco sidebar. this is critical so that the parent expands when you're viewing a page. This must appear below the sidebar code above. Otherwise, if placed inside customscripts.js, the script runs before the sidebar code runs and the class never gets inserted.-->
<script>$("li.active").parents('li').toggleClass("active");</script>
</div>
<!-- Content Column -->
<div class="col-md-8" id="tg-sb-content">
<!-- <div class="post-header">
<h1 class="post-title-main">Contribute to the Protocol</h1>
</div> -->
<div class="post-content">
<div class="row">
<div class="col-md-9 page-article"><h1 id="contribute-to-the-protocol">Contribute to the Protocol</h1>
<p><em>Last updated: 24 FEB 2020</em></p>
<p>[TOC]</p>
<h2 id="about-the-bitmark-protocol">About the Bitmark Protocol</h2>
<p>We expect you probably got here from https://bitmark.com. But just in case you didn’t, the explanation of the Bitmark Protocol is here:</p>
<ul>
<li><a href="../browse-our-faq/bitmark-protocol-faq">https://bitmark.com/faq</a></li>
<li><a href="../read-our-papers/white-papers">https://bitmark.com/white-papers</a></li>
</ul>
<p>The Bitmark Protocol software project is the means by which the peer-to-peer network implements the Bitmark Protocol.</p>
<p>The core values of both Bitmark Inc. and the Bitmark Protocol software project are transparency and trust. The end goal of the Bitmark Protocol software project is to develop a means of establishing transparency and trust in digital property.</p>
<p>To that end, this document attempts to transparently establish the principles by which Bitmark Inc. provides the Bitmark Protocol to the community and invites community participation, with the hope of establishing trust in that community.</p>
<h3 id="about-bitmark-inc">About Bitmark Inc.</h3>
<p>Bitmark Inc. is a venture-funded private company. Current information regarding our funders is here: <a href="https://bitmark.com/about">https://bitmark.com/about</a>. Bitmark Inc. has been to date the main developer of the Bitmark Protocol software project, and we will offer services and products which rely on it, but we don’t want to be the only people using it. We think it can be useful to the wider community.</p>
<p>Just as the larger project of Bitmark Inc. and the Bitmark Protocol software project is a distributed peer-to-peer network for managing and claiming crypto property, we’d like the Bitmark Protocol software project to become a community project.</p>
<h3 id="why-not-a-foundation">Why not a Foundation?</h3>
<p>Bitmark Inc. is a small company. We simply don’t have the resources to establish and sustain a separate foundation to manage the Bitmark Protocol software project. As we grow, we will continue to evaluate whether, between Bitmark Inc. and the community, there are adequate resources to establish and sustain a separate foundation for the development and maintenance of the Bitmark Protocol software project.</p>
<h3 id="why-the-internet-systems-consortium-isc-license">Why the Internet Systems Consortium (“ISC”) License?</h3>
<p>We chose a permissive license in order to allow the broadest possible set of uses for the Bitmark Protocol software project. It also makes contribution easy – just license your contribution under the ISC License. We may at some point revisit the licensing model based on the actual uses of the Bitmark Protocol software project and community input.</p>
<h2 id="principles-of-operation">Principles of Operation</h2>
<p>Bitmark Inc. will maintain the primary code repository for the Bitmark Protocol software project and will retain primary development and maintenance responsibility. We will also retain control of the code commit decisions, at least until a sufficiently strong community has arisen from which to select trusted code committers.</p>
<p>Bitmark Inc. will also provide one or more community moderators to guide the discussion about the project, again, at least until a sufficiently strong community has arisen from which to select trusted community moderators.</p>
<p>Bitmark Inc. will provide its reasons for all of its decisions regarding the Bitmark Protocol software project, including the direction it chooses for development, code commit decisions, and community management decisions.</p>
<p>The primary method of communication among the communities will be one or more mailing lists. This creates an archive of community conversations and allows asynchronous conversations. Our expectations for behavior are here: https://bitmark.com/conduct. Generally speaking, however, we expect our community members to conduct open and honest conversations, <strong><em>while always treating each other with respect and honoring the dignity of each individual participant</em></strong>.</p>
<p>We will over time evaluate the community to determine whether we have a sufficient number of active participants to establish additional roles for community members or to establish a more democratic mode of governance.</p>
<p>Our expectation is that only Bitmark employees speak for the organization for which they work, and even then, only within their scope of authority. All other community members speak only for themselves.</p>
<h3 id="bitmark-upgrade-proposals">Bitmark Upgrade Proposals</h3>
<p>A Bitmark Upgrade Proposal (BUP) is a design document providing information to the Bitmark community or describing a new feature for
Bitmark or its processes or environment. A BUP provides a concise technical specification of the feature and a rationale for it.</p>
<p>We have a repo at GitHub specifically for BUPs. We do not maintain it as part of the
Bitmark documentation <a href="https://github.com/bitmark-inc/docs">repository</a> because we want that to be a clean
environment where developers are not distracted by other
repos.</p>
<p>For full access to all BUPs, please go to: <a href="https://github.com/bitmark-property-system/bups">Bitmark Upgrade Proposal</a></p>
<p>Please assume that everything you contribute intentionally to the Bitmark Protocol software project is public. This includes emails on public lists, wikis, other online discussions of all sorts, and software or documentation that you post to this website or our revision control repositories. There may be cases where you are invited to share private information for various purposes, and denote that information as such. That information is subject to the privacy policy of Bitmark Inc., located here: <a href="https://bitmark.com/privacy">https://bitmark.com/privacy</a>. Similarly, other information collected by this website is subject to that privacy policy.</p>
<p>Although what participants disclose here is public, both community members and Bitmark Inc. are limited by intellectual property law in how the use of community member contributions. <strong><em>Bitmark Inc. only accepts voluntary contributions of software and documentation that are expressly licensed to Bitmark Inc. (or all comers) under the ISC license.</em></strong></p>
<h2 id="security-program">Security Program</h2>
<p>Bitmark strives to make the Bitmark Property System safe and secure for everyone. We greatly value the work done by security researchers in improving the security of our products and service offerings, so we are committed to working with this community to verify, reproduce, and respond to legitimate reported vulnerabilities. We encourage the community to participate in our responsible reporting process.</p>
<p><strong>Important:</strong> We only accept bug reports for the <strong><code class="language-plaintext highlighter-rouge">bitmarkd</code></strong> project. Bug reports for web applications or any other project that is not <strong><code class="language-plaintext highlighter-rouge">bitmarkd</code></strong> will not be accepted nor given any reward.</p>
<p><a href="https://docs.google.com/forms/d/e/1FAIpQLSeVzZfd-DDQNuVVDMkwgu4VSxmPnvB6OLo_sw_9CH1w34xoZA/viewform">SUBMIT A BUG</a></p>
<p>We offer rewards in Bitcoin:</p>
<table>
<thead>
<tr>
<th>Critical</th>
<th>High</th>
<th>Medium</th>
<th>Low</th>
<th>Note</th>
</tr>
</thead>
<tbody>
<tr>
<td>1 BTC</td>
<td>0.5 BTC</td>
<td>0.2 BTC</td>
<td>0.1 BTC</td>
<td>0.01 BTC</td>
</tr>
</tbody>
</table>
<p>Latest bug updates:</p>
<ul>
<li><strong>2018.11.14</strong>: Congratulations to bughunterboy for finding bugs and earning rewards!</li>
<li><strong>2018.10.11</strong>: Join our Bug Bounty Program and earn rewards now!</li>
</ul>
<h3 id="how-to-report-a-bug">How to report a bug</h3>
<h4 id="determining-scope">Determining scope</h4>
<p><a href="https://github.com/bitmark-inc/bitmarkd">Bitmarkd</a> is the codebase for the Bitmark blockchain.</p>
<h5 id="bug-scope">Bug scope</h5>
<p>Only bugs in Scope are eligible for a bug bounty. A qualifying bug has to be a danger to the blockchain records, privacy, or client operations. These include bugs in:</p>
<ol>
<li><strong>Protocol</strong>: Flaws in protocol design, an example being the incentive design flaw in the <a href="/assets/pdf/bitmark-technical-white-paper.pdf">white paper</a></li>
<li><strong>Implementation of client</strong>: Any implementation bug in <code class="language-plaintext highlighter-rouge">bitmarkd</code> that could cause cause bad block, invalid assets, transaction failure, bad operations, or program crashes</li>
<li><strong>Cryptography</strong>: Incorrect implementation of Cryptographic algorithms</li>
<li><strong>Network Attacks</strong>: Attacks such as Sybil attacks</li>
<li>Any bugs that Bitmark considers important</li>
</ol>
<h5 id="restrict-online-low-bandwidth-attack-to-these-two-nodes-only">Restrict online low-bandwidth attack to these two nodes only:</h5>
<ul>
<li><code class="language-plaintext highlighter-rouge">node-d3.test.bitmark.com</code></li>
<li><code class="language-plaintext highlighter-rouge">node-a3.test.bitmark.com</code></li>
</ul>
<h5 id="bugs-in-third-party-packages">Bugs in third-party packages</h5>
<p>Third-party package bugs may or may not be rewarded by Bitmark. In theory, you should claim the bug(s) directly with a third-party bounty program; however, we may also reward you for your efforts.</p>
<h5 id="out-of-scope-bugs">Out-of-scope bugs</h5>
<p>Bugs that are out of scope include those that require:</p>
<ul>
<li>Physical access to a user’s device</li>
<li>Social engineering</li>
<li>MITM attacks</li>
<li>DDoS / Fuzzing / High-Bandwidth Attack</li>
</ul>
<h3 id="submitting-a-bug">Submitting a bug</h3>
<ul>
<li>Submit your report to: <a href="https://docs.google.com/forms/d/e/1FAIpQLSeVzZfd-DDQNuVVDMkwgu4VSxmPnvB6OLo_sw_9CH1w34xoZA/viewform">Bug Bounty Submission Form</a></li>
</ul>
<h3 id="collecting-rewards">Collecting rewards</h3>
<p>Rewards are considered based on the impact and severity of the vulnerability, with relation to the scope and quality of the report.</p>
<ul>
<li>Critical Bugs: key leaks</li>
<li>High Bugs (At Least): invalid block or corrupted database</li>
<li>If a bug does not fit into the Critical or High criteria as defined above, it will be considered Medium, Low, or Note</li>
<li>Only unknown and first-submitted bugs are considered eligible for a reward</li>
<li>A detailed proof of concept has to be presented when claiming a Critical or High bug</li>
</ul>
<h3 id="disclosure-policy">Disclosure policy</h3>
<p>Please discuss with us before disclosure of your bugs. Bitmark will endeavor to respond to reports within <strong>2-3 business days</strong> and will make every effort to quickly address reported vulnerabilities. To encourage responsible reporting, we commit that we will <strong>not take legal action</strong> against you or ask law enforcement to investigate you if you give us at least <strong>90 days</strong> from the time of your report to correct the issue before you make the reported vulnerability public.</p>
<p>Contact us at: <a href="mailto:[email protected]">[email protected]</a></p>
<h2 id="updates-to-this-document">Updates to this Document</h2>
<p>Bitmark Inc. may update this document from time to time. We will maintain a <a href="https://github.com/bitmark-inc/legal/commits/master/contribute.md">revision history</a> in our revision control repository.</p>
<h2 id="questions">Questions</h2>
<p>Questions should be directed to: <a href="mailto:[email protected]">[email protected]</a>.</p>
</div>
<div class="col-md-3">
<!-- this handles the automatic toc. use ## for subheads to auto-generate the on-page minitoc. if you use html tags, you must supply an ID for the heading element in order for it to appear in the minitoc. -->
<script>
$( document ).ready(function() {
// Handler for .ready() called.
$('#toc').toc({ minimumHeaders: 0, listType: 'ul', showSpeed: 0, headers: 'h2,h3,h4' });
/* this offset helps account for the space taken up by the floating toolbar. */
$('#toc').on('click', 'a', function() {
var target = $(this.getAttribute('href'))
, scroll_target = target.offset().top
$(window).scrollTop(scroll_target - 10);
return false
})
});
</script>
<!-- <div id="toc" class="affix"></div> -->
</div>
</div>
<div class="tags">
</div>
</div>
<!-- <hr class="shaded"/> -->
<footer>
<div class="row">
<div class="col-lg-12 footer">
©2020 Bitmark Inc. All rights reserved.
<!-- <br/> Powered by <a href="https://jekyllrb.com/">Jekyll</a> -->
<!-- <p><img src="/assets/images/company_logo.png" alt="Company logo"/></p>
</div>
</div> -->
</footer>
</div>
<!-- /.row -->
</div>
<!-- /.container -->
</div>
<!-- /#main -->
</div>
</body>
</html>