mirror of
https://github.com/monero-project/monero-site.git
synced 2025-03-28 10:08:52 +00:00
Merge pull request #292
79c3d97Updated README (rehrar)4e41a6aAdded new site (rehrar)3c3d069Removed old site (rehrar)
This commit is contained in:
Riccardo Spagni
commit
c80c882429
350 changed files with 14204 additions and 1644 deletions
404
css
images
_data
_includes
_layouts
base.htmlblog_by_tag.htmlcustom.htmldefault.htmldefaultnt.htmlffs-cp.htmlffs-fr.htmlffs-ideas.htmlffs-ot.htmlffs-wip.htmlffs.htmlfull-text.htmlfull.htmlmoneropedia.htmlpost.htmlproposal.htmlstatic_page.html
_plugins
_posts
2016-06-05-logs-for-the-kovri-dev-meeting-held-on-2016-06-05.md2016-06-05-overview-and-logs-for-the-dev-meeting-held-on-2016-06-05.md2016-06-19-logs-for-the-Kovri-dev-meeting-held-on-2016-06-19.md2016-06-19-overview-and-logs-for-the-dev-meeting-held-on-2016-06-19.md2016-06-20-monero-missive-for-the-week-of-2016-06-20.md2016-07-03-logs-for-the-Kovri-dev-meeting-held-on-2016-07-03.md2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md2016-07-31-logs-for-the-Kovri-dev-meeting-held-on-2016-07-31.md2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md2016-08-14-overview-and-logs-for-the-dev-meeting-held-on-2016-08-14.md2016-08-28-logs-for-the-Kovri-dev-meeting-held-on-2016-08-28.md2016-08-28-overview-and-logs-for-the-dev-meeting-held-on-2016-08-28.md2016-09-11-logs-for-the-Kovri-dev-meeting-held-on-2016-09-11.md2016-09-11-overview-and-logs-for-the-dev-meeting-held-on-2016-09-11.md2016-09-19-monero-0.10.0-released.md2016-09-21-a-statement-on-the-mwr-labs-disclosure.md2016-10-02-logs-for-the-Kovri-dev-meeting-held-on-2016-10-02.md2016-10-02-overview-and-logs-for-the-dev-meeting-held-on-2016-10-02.md2016-10-16-logs-for-the-Kovri-dev-meeting-held-on-2016-10-16.md2016-10-16-overview-and-logs-for-the-dev-meeting-held-on-2016-10-16.md2016-10-30-logs-for-the-Kovri-dev-meeting-held-on-2016-10-30.md2016-10-30-overview-and-logs-for-the-dev-meeting-held-on-2016-10-30.md2016-11-13-logs-for-the-Kovri-dev-meeting-held-on-2016-11-13.md2016-11-13-overview-and-logs-for-the-dev-meeting-held-on-2016-11-13.md2016-11-27-logs-for-the-Kovri-dev-meeting-held-on-2016-11-27.md2016-11-27-overview-and-logs-for-the-dev-meeting-held-on-2016-11-27.md2016-12-14-monero-0.10.1-released.md2016-12-22-monero-core-gui-beta-released.md2017-02-05-logs-for-the-Kovri-dev-meeting-held-on-2017-02-05.md2017-02-05-overview-and-logs-for-the-dev-meeting-held-on-2017-02-05.md2017-02-19-overview-and-logs-for-the-dev-meeting-held-on-2017-02-19.md2017-02-23-monero-0.10.2-released.md2017-02-24-monero-0.10.2.1-released.md2017-03-12-overview-and-logs-for-the-dev-meeting-held-on-2017-03-12.md2017-03-25-monero-0.10.3-released.md2017-03-26-logs-for-the-Kovri-dev-meeting-held-on-2017-03-26.md2017-03-26-overview-and-logs-for-the-dev-meeting-held-on-2017-03-26.md2017-03-27-monero-0.10.3.1-released.md2017-03-29-monero-gui-beta-2-released.md2017-04-01-announcing-the-monero-celebrity-center.md2017-04-09-logs-for-the-Kovri-dev-meeting-held-on-2017-04-09.md2017-04-09-overview-and-logs-for-the-dev-meeting-held-on-2017-04-09.md2017-04-19-an-unofficial-response-to-an-empirical-analysis-of-linkability.md2017-04-23-logs-for-the-Kovri-dev-meeting-held-on-2017-04-23.md2017-05-07-logs-for-the-Kovri-dev-meeting-held-on-2017-05-07.md2017-05-07-overview-and-logs-for-the-dev-meeting-held-on-2017-05-07.md2017-05-17-disclosure-of-a-major-bug-in-cryptonote-based-currencies.md
android-chrome-144x144.pngandroid-chrome-192x192.pngandroid-chrome-36x36.pngandroid-chrome-48x48.pngandroid-chrome-72x72.pngandroid-chrome-96x96.pngapple-touch-icon-114x114.pngapple-touch-icon-120x120.pngapple-touch-icon-144x144.pngapple-touch-icon-152x152.pngapple-touch-icon-180x180.pngapple-touch-icon-57x57.pngapple-touch-icon-60x60.pngapple-touch-icon-72x72.pngapple-touch-icon-76x76.png
48
404/css/ie7.css
Executable file → Normal file
48
404/css/ie7.css
Executable file → Normal file
|
|
@ -1,25 +1,25 @@
|
|||
@charset "utf-8";
|
||||
div.not-found-text{
|
||||
top:65px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
z-index:-1;
|
||||
}
|
||||
|
||||
div.dog{
|
||||
z-index:1000;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
filter: alpha(opacity=0); /* IE6+ */
|
||||
filter: progid:DXImageTransform.Microsoft.Alpha(opacity=0); /* IE6+ */
|
||||
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(opacity=0)";
|
||||
padding-top:35px;
|
||||
}
|
||||
|
||||
#dog-changer ul li a{
|
||||
filter: alpha(opacity=30); /* IE6+ */
|
||||
filter: progid:DXImageTransform.Microsoft.Alpha(opacity=30); /* IE6+ */
|
||||
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(opacity=30)";
|
||||
@charset "utf-8";
|
||||
div.not-found-text{
|
||||
top:65px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
z-index:-1;
|
||||
}
|
||||
|
||||
div.dog{
|
||||
z-index:1000;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
filter: alpha(opacity=0); /* IE6+ */
|
||||
filter: progid:DXImageTransform.Microsoft.Alpha(opacity=0); /* IE6+ */
|
||||
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(opacity=0)";
|
||||
padding-top:35px;
|
||||
}
|
||||
|
||||
#dog-changer ul li a{
|
||||
filter: alpha(opacity=30); /* IE6+ */
|
||||
filter: progid:DXImageTransform.Microsoft.Alpha(opacity=30); /* IE6+ */
|
||||
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(opacity=30)";
|
||||
}
|
||||
624
404/css/main.css
Executable file → Normal file
624
404/css/main.css
Executable file → Normal file
|
|
@ -1,313 +1,313 @@
|
|||
@charset "utf-8";
|
||||
|
||||
/* === General stuff === */
|
||||
|
||||
html, body{
|
||||
height:100%;
|
||||
background:#186aa9 url(/404/images/sky-background.png) top repeat-x;
|
||||
overflow:hidden;
|
||||
padding:0;
|
||||
margin:0;
|
||||
font-family:Arial, Helvetica, sans-serif;
|
||||
margin-top: 5px;
|
||||
}
|
||||
|
||||
.footer{
|
||||
display: none;
|
||||
}
|
||||
|
||||
a{
|
||||
color:#3680b1;
|
||||
}
|
||||
|
||||
img, a img{
|
||||
border:0px none;
|
||||
outline:none;
|
||||
}
|
||||
|
||||
/* === Main Section === */
|
||||
|
||||
#wrapper{
|
||||
width:980px;
|
||||
margin:0px auto;
|
||||
position:relative;
|
||||
height:100%;
|
||||
background:url(/404/images/sky-shine.jpg) top left no-repeat;
|
||||
}
|
||||
|
||||
div.top-left{
|
||||
position:absolute;
|
||||
right:0px;
|
||||
}
|
||||
|
||||
div.not-found-text{
|
||||
position:absolute;
|
||||
top:35px;
|
||||
right:0px;
|
||||
width:430px;
|
||||
}
|
||||
|
||||
h1.not-found-text{
|
||||
font-size:50px;
|
||||
color:#fff;
|
||||
letter-spacing:2px;
|
||||
margin-bottom:20px;
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:80px;
|
||||
left:0px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-720px;
|
||||
margin:0px auto;
|
||||
z-index:0;
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:960px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:45px;
|
||||
left:440px;
|
||||
}
|
||||
|
||||
div.dog{
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:0px;
|
||||
width:80px;
|
||||
height:80px;
|
||||
z-index:999;
|
||||
background:url(/404/images/dog1.png) 0px 0px no-repeat;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
font-size:18px;
|
||||
line-height:1.5;
|
||||
font-style:italic;
|
||||
height:179px;
|
||||
width:246px;
|
||||
background:url(/404/images/bubble.png) top center no-repeat;
|
||||
padding:20px 0px;
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:30px;
|
||||
z-index:999;
|
||||
opacity:0;
|
||||
color:#555555;
|
||||
text-shadow:1px 1px 0 #ffffff;
|
||||
}
|
||||
|
||||
div.dog-bubble>p{
|
||||
text-align:center;
|
||||
padding:0px 35px;
|
||||
}
|
||||
|
||||
div.bubble-options{
|
||||
opacity:0;
|
||||
visibility:hidden;
|
||||
display:none;
|
||||
}
|
||||
|
||||
/* === Responsive === */
|
||||
|
||||
/* #Small laptop screens
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 960px) {
|
||||
#wrapper{
|
||||
width:600px;
|
||||
background-image:none;
|
||||
margin-top: 50px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-300px;
|
||||
margin:0 auto 0 -280px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:560px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:30px;
|
||||
left:250px;
|
||||
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:50px;
|
||||
left:40px;
|
||||
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 0px;
|
||||
top: -40px;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:60%;
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
left: 0px;
|
||||
position: absolute;
|
||||
top: 20px;
|
||||
}
|
||||
|
||||
div.not-found-text{
|
||||
right:0px;
|
||||
top:22px;
|
||||
width:320px;
|
||||
}
|
||||
|
||||
h1.not-found-text{
|
||||
font-size:35px;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
|
||||
/* #Tablets and small screens
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 767px) {
|
||||
|
||||
#wrapper{
|
||||
width:400px;
|
||||
background-image:none;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:40%;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-170px;
|
||||
margin:0 auto 0 -180px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:360px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:30px;
|
||||
left:150px;
|
||||
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:20px;
|
||||
left:0px;
|
||||
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 390px;
|
||||
top: 170px;
|
||||
}
|
||||
|
||||
h1.not-found-text {
|
||||
font-size: 26px;
|
||||
}
|
||||
|
||||
div.not-found-text {
|
||||
right: -60px;
|
||||
top: 33px;
|
||||
width: 270px;
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 0;
|
||||
top: -38px;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
|
||||
/* #Mobile phones
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 479px){
|
||||
|
||||
#wrapper{
|
||||
width:320px;
|
||||
background-image:none;
|
||||
}
|
||||
|
||||
h1.not-found-text {
|
||||
font-size: 20px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
div.not-found-text {
|
||||
right: 20px;
|
||||
top: 210px;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:100%;
|
||||
}
|
||||
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-70px;
|
||||
margin:0 auto 0 -100px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:200px;
|
||||
}
|
||||
|
||||
div.dog-wrapper {
|
||||
left: 70px;
|
||||
position: absolute;
|
||||
top: 26px;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
font-size:10px;
|
||||
line-height:1.5;
|
||||
font-style:italic;
|
||||
height:107px;
|
||||
width:147px;
|
||||
background:url(/404/images/bubble.png) top center no-repeat;
|
||||
background-size: contain;
|
||||
padding:10px 0px;
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:55px;
|
||||
z-index:999;
|
||||
opacity:0;
|
||||
color:#555555;
|
||||
text-shadow:1px 1px 0 #ffffff;
|
||||
}
|
||||
@charset "utf-8";
|
||||
|
||||
/* === General stuff === */
|
||||
|
||||
html, body{
|
||||
height:100%;
|
||||
background:#186aa9 url(/404/images/sky-background.png) top repeat-x;
|
||||
overflow:hidden;
|
||||
padding:0;
|
||||
margin:0;
|
||||
font-family:Arial, Helvetica, sans-serif;
|
||||
margin-top: 5px;
|
||||
}
|
||||
|
||||
.footer{
|
||||
display: none;
|
||||
}
|
||||
|
||||
a{
|
||||
color:#3680b1;
|
||||
}
|
||||
|
||||
img, a img{
|
||||
border:0px none;
|
||||
outline:none;
|
||||
}
|
||||
|
||||
/* === Main Section === */
|
||||
|
||||
#wrapper{
|
||||
width:980px;
|
||||
margin:0px auto;
|
||||
position:relative;
|
||||
height:100%;
|
||||
background:url(/404/images/sky-shine.jpg) top left no-repeat;
|
||||
}
|
||||
|
||||
div.top-left{
|
||||
position:absolute;
|
||||
right:0px;
|
||||
}
|
||||
|
||||
div.not-found-text{
|
||||
position:absolute;
|
||||
top:35px;
|
||||
right:0px;
|
||||
width:430px;
|
||||
}
|
||||
|
||||
h1.not-found-text{
|
||||
font-size:50px;
|
||||
color:#fff;
|
||||
letter-spacing:2px;
|
||||
margin-bottom:20px;
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:80px;
|
||||
left:0px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-720px;
|
||||
margin:0px auto;
|
||||
z-index:0;
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:960px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:45px;
|
||||
left:440px;
|
||||
}
|
||||
|
||||
div.dog{
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:0px;
|
||||
width:80px;
|
||||
height:80px;
|
||||
z-index:999;
|
||||
background:url(/404/images/dog1.png) 0px 0px no-repeat;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
font-size:18px;
|
||||
line-height:1.5;
|
||||
font-style:italic;
|
||||
height:179px;
|
||||
width:246px;
|
||||
background:url(/404/images/bubble.png) top center no-repeat;
|
||||
padding:20px 0px;
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:30px;
|
||||
z-index:999;
|
||||
opacity:0;
|
||||
color:#555555;
|
||||
text-shadow:1px 1px 0 #ffffff;
|
||||
}
|
||||
|
||||
div.dog-bubble>p{
|
||||
text-align:center;
|
||||
padding:0px 35px;
|
||||
}
|
||||
|
||||
div.bubble-options{
|
||||
opacity:0;
|
||||
visibility:hidden;
|
||||
display:none;
|
||||
}
|
||||
|
||||
/* === Responsive === */
|
||||
|
||||
/* #Small laptop screens
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 960px) {
|
||||
#wrapper{
|
||||
width:600px;
|
||||
background-image:none;
|
||||
margin-top: 50px;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-300px;
|
||||
margin:0 auto 0 -280px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:560px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:30px;
|
||||
left:250px;
|
||||
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:50px;
|
||||
left:40px;
|
||||
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 0px;
|
||||
top: -40px;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:60%;
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
left: 0px;
|
||||
position: absolute;
|
||||
top: 20px;
|
||||
}
|
||||
|
||||
div.not-found-text{
|
||||
right:0px;
|
||||
top:22px;
|
||||
width:320px;
|
||||
}
|
||||
|
||||
h1.not-found-text{
|
||||
font-size:35px;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
|
||||
/* #Tablets and small screens
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 767px) {
|
||||
|
||||
#wrapper{
|
||||
width:400px;
|
||||
background-image:none;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:40%;
|
||||
}
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-170px;
|
||||
margin:0 auto 0 -180px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:360px;
|
||||
}
|
||||
|
||||
div.dog-wrapper{
|
||||
position:absolute;
|
||||
top:30px;
|
||||
left:150px;
|
||||
|
||||
}
|
||||
|
||||
div.graphic{
|
||||
position:absolute;
|
||||
top:20px;
|
||||
left:0px;
|
||||
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 390px;
|
||||
top: 170px;
|
||||
}
|
||||
|
||||
h1.not-found-text {
|
||||
font-size: 26px;
|
||||
}
|
||||
|
||||
div.not-found-text {
|
||||
right: -60px;
|
||||
top: 33px;
|
||||
width: 270px;
|
||||
}
|
||||
|
||||
div.top-left {
|
||||
position: absolute;
|
||||
right: 0;
|
||||
top: -38px;
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
|
||||
/* #Mobile phones
|
||||
================================================== */
|
||||
|
||||
@media only screen and (max-width: 479px){
|
||||
|
||||
#wrapper{
|
||||
width:320px;
|
||||
background-image:none;
|
||||
}
|
||||
|
||||
h1.not-found-text {
|
||||
font-size: 20px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
div.not-found-text {
|
||||
right: 20px;
|
||||
top: 210px;
|
||||
}
|
||||
|
||||
div.graphic>img{
|
||||
width:100%;
|
||||
}
|
||||
|
||||
|
||||
div.planet{
|
||||
position:absolute;
|
||||
bottom:-70px;
|
||||
margin:0 auto 0 -100px;
|
||||
z-index:0;
|
||||
left:50%;
|
||||
|
||||
}
|
||||
|
||||
div.planet>img{
|
||||
width:200px;
|
||||
}
|
||||
|
||||
div.dog-wrapper {
|
||||
left: 70px;
|
||||
position: absolute;
|
||||
top: 26px;
|
||||
}
|
||||
|
||||
div.dog-bubble{
|
||||
font-size:10px;
|
||||
line-height:1.5;
|
||||
font-style:italic;
|
||||
height:107px;
|
||||
width:147px;
|
||||
background:url(/404/images/bubble.png) top center no-repeat;
|
||||
background-size: contain;
|
||||
padding:10px 0px;
|
||||
position:absolute;
|
||||
bottom:0px;
|
||||
left:55px;
|
||||
z-index:999;
|
||||
opacity:0;
|
||||
color:#555555;
|
||||
text-shadow:1px 1px 0 #ffffff;
|
||||
}
|
||||
}
|
||||
0
404/images/404.png
Executable file → Normal file
0
404/images/404.png
Executable file → Normal file
|
Before 
(image error) Size: 9.5 KiB After 
(image error) Size: 9.5 KiB
|
0
404/images/bubble.png
Executable file → Normal file
0
404/images/bubble.png
Executable file → Normal file
|
Before 
(image error) Size: 9.2 KiB After 
(image error) Size: 9.2 KiB
|
0
404/images/cat.png
Executable file → Normal file
0
404/images/cat.png
Executable file → Normal file
|
Before 
(image error) Size: 3.3 KiB After 
(image error) Size: 3.3 KiB
|
0
404/images/cookie.png
Executable file → Normal file
0
404/images/cookie.png
Executable file → Normal file
|
Before 
(image error) Size: 5.4 KiB After 
(image error) Size: 5.4 KiB
|
0
404/images/dog1.png
Executable file → Normal file
0
404/images/dog1.png
Executable file → Normal file
|
Before 
(image error) Size: 13 KiB After 
(image error) Size: 13 KiB
|
0
404/images/planet.png
Executable file → Normal file
0
404/images/planet.png
Executable file → Normal file
|
Before 
(image error) Size: 1.2 MiB After 
(image error) Size: 1.2 MiB
|
0
404/images/sky-background.png
Executable file → Normal file
0
404/images/sky-background.png
Executable file → Normal file
|
Before 
(image error) Size: 3.3 KiB After 
(image error) Size: 3.3 KiB
|
0
404/images/sky-shine.jpg
Executable file → Normal file
0
404/images/sky-shine.jpg
Executable file → Normal file
|
Before 
(image error) Size: 73 KiB After 
(image error) Size: 73 KiB
|
431
README.md
431
README.md
|
|
@ -1,45 +1,422 @@
|
|||
# Monero
|
||||
# Monero Website Instructions
|
||||
|
||||
Copyright (c) 2014-2017, The Monero Project
|
||||
|
||||
## Development Resources
|
||||
## Table of Contents
|
||||
|
||||
Web: [getmonero.org](http://getmonero.org)
|
||||
Mail: [dev@getmonero.org](mailto:dev@getmonero.org)
|
||||
IRC: [#monero-dev on Freenode](irc://chat.freenode.net/#monero-dev)
|
||||
1.0 Introduction
|
||||
|
||||
## About this Project
|
||||
2.0 What you'll need
|
||||
|
||||
This is the Monero website. Instead of using MediaWiki or similar, we are using Jekyll and hosting the source on github. All site content is in the easy-to-use Markdown format (Kramdown, specifically), so contributors don't need to have any knowledge of HTML or anything else.
|
||||
3.0 General change recommendations
|
||||
|
||||
## Pages, Formats, and Rules
|
||||
4.0 How to make a blog post
|
||||
|
||||
If you would like to suggest changes you can do so by forking the repository, making changes directly on your fork, and then submitting them as pull requests. If you need help doing so feel free to ask for assistance in #monero-dev on Freenode.
|
||||
5.0 How to make a User Guide
|
||||
|
||||
Pages and formats should be based off existing pages to maintain a consistent look-and-feel. The following notes apply to various parts of the site:
|
||||
6.0 How to make a Moneropedia entry
|
||||
|
||||
- changes made to _layouts, _includes, and home.php will need to use {% t x.x %} translation tags to pull in the YAML tag from _strings_en.yml, as this is required for multi-language support later on
|
||||
- with the exception of something like blog/index.html (that is required to be a .html file for Jekyll's pagination to work) all pages should be .md files
|
||||
- static content (CSS/JS/images) can be found in the [monero-forum](https://github.com/monero-project/monero-forum) repo
|
||||
- SVG should be used in header icons and diagrams, and FontAwesome icons can be used in text
|
||||
- Moneropedia entries require nothing more than creating the .md file in knowledge-base/moneropedia/, please use the 00-base-00 file as a boilerplate
|
||||
- To create a CLI screen shot, prefix the text block with {:.cli-code}, and use span elements for the colours; see getting-started/running.md, getting-started/accepting.md, and the account.md Moneropedia entry
|
||||
7.0 How to make a FFS Proposal
|
||||
|
||||
## Deployment
|
||||
8.0 How to update the Team page
|
||||
|
||||
Deploying this website requires Jekyll (3.0+) and the following ruby gems: builder, rubysl-rexml, jekyll-paginate
|
||||
9.0 How to make an Event
|
||||
|
||||
Multiple language support will be added soon.
|
||||
10.0 How to update the Roadmap
|
||||
|
||||
To test changes locally before pushing to git, make sure you have ruby installed on your system, then:
|
||||
11.0 How to add a new Merchant
|
||||
|
||||
1. Make sure you have the necessary ruby gems: `gem install builder rubysl-rexml jekyll-paginate jekyll`
|
||||
2. Navigate to the your local `monero-site` repository.
|
||||
3. Serve the website: `jekyll serve`
|
||||
4. Open a browser and go to [http://127.0.0.1:4000](http://127.0.0.1:4000).
|
||||
5. A basic page list will appear. Click on the part of the site you are working on (ex: `design_goals`) and see your work!
|
||||
12.0 How to add a question to the FAQ
|
||||
|
||||
## License
|
||||
13.0 License
|
||||
|
||||
## 1.0 Introduction
|
||||
|
||||
Greetings everyone, this is rehrar. I'm here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new getmonero.org website. It'll definitely be a bit of a ride, so strap yourself in. Please note that translations are not available yet, but when they are added, this document will be updated with instructions on how to translate the content of getmonero.org. In the meantime, any help translating this document into another language is greatly appreciated.
|
||||
|
||||
Feel free to skip down to a relevant section if you already know what you need. So to go to the (ADD SECTION HERE) use your find function and type (THING TO TYPE HERE).
|
||||
|
||||
If for any reason you have questions or need to contact us, you can find us on the IRC channel #monero. We'll do whatever we can to help you.
|
||||
|
||||
## 2.0 What you'll need
|
||||
|
||||
* Jekyll: Getmonero.org is made using a simple, static website generator called [Jekyll](https://jekyllrb.com/). You will need it installed on your system to test any changes that you made. If you're using a Linux-based system you can just follow the instructions on the website to get up and going. If you're using Windows, you will want to check out [this site](http://jekyll-windows.juthilo.com/) for instructions on how to get Jekyll working on your system.
|
||||
|
||||
* GitHub: Pretty much everything in Monero is hosted on [GitHub](https://github.com) and uses Git as the primary version control system. If you're not familiar with how to use Git, you can check out [this tutorial](https://guides.github.com/activities/hello-world/) for a good overview. It will take you through pretty much everything you'll need to know to edit the website. If you haven't already, register for GitHub and fork the [Monero Website repository](https://github.com/monero-project/monero-site).
|
||||
|
||||
* Markdown experience: To write pages, you're going to need to know how to use Markdown. It's basically a in-between language that enables people who don't know HTML to just write, and it will be compiled into HTML for you. You can find a great Markdown cheat sheet with examples [here](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet). IF you need more help, Google and YouTube are great resources.
|
||||
|
||||
*Note: If you're confused, feel free to click other files in the same directory (folder) that you are in for the step that you are on to see some working examples. Compare them to the instructions and you should understand better.*
|
||||
|
||||
* Jekyll Gems: The current iteration of the getmonero.org website uses the following plugins:
|
||||
* [jekyll-paginate](https://jekyllrb.com/docs/pagination/)
|
||||
* builder
|
||||
* rubysl-rexml
|
||||
* In the event that more gems are added, this documentation will be updated to reflect the changes needed to build the site.
|
||||
|
||||
*Note:* To install them all at once, use the command: `gem install builder rubysl-rexml jekyll-paginate`
|
||||
|
||||
Once you have the above list of things, it's typically a good idea to build the website from your local computer to make sure it works before you make any changes. To do this, complete the following steps:
|
||||
|
||||
1. Navigate to the your local `monero-site` repository.
|
||||
2. Serve the website: `jekyll serve`
|
||||
3. Open a browser and go to [http://127.0.0.1:4000](http://127.0.0.1:4000).
|
||||
4. If all went well, you should see the Monero website and you're ready to make changes.
|
||||
|
||||
## 3.0 General change recommendations
|
||||
|
||||
The average Monero user that will want to contribute to the website should probably stick with making blog posts, user guides, Moneropedia entries, or a Forum Funding System proposal, all of which are covered in this document. If this is all you want to do, don't worry, it's actually not a daunting task at all. If you are not well versed in web development however, it is not recommended you try to do anything beyond that.
|
||||
|
||||
If you are a web developer and would like to make large macro-level changes, it would be best to get in contact with rehrar. The HTML/CSS framework is custom, though quite easy to use for a seasoned developer. Still, there are some pages that are more complicated than others and would require fair amounts of styling changes should the structure change significantly.
|
||||
|
||||
This website is completely open-source however, and anything and everything is available for changing should the community deem it necessary.
|
||||
|
||||
Every section from here on out will talk about how to make a specific type of web page. It will start with a bullet point list of what to do for the advanced among you that just want a quick overview. For those who are still learning this list is followed by a detailed explanation, starting with example front matter. Any variable in the front matter written in all caps you are expected to change (make sure your changes are not all caps though). It will then lead you through the rest of the process until it's time to type your content.
|
||||
|
||||
All external links must have http:// or https:// in front of them or they will not redirect properly.
|
||||
|
||||
## 4.0 How to make a blog post
|
||||
|
||||
### 4.1 Quick Start
|
||||
* Make new .md file in _posts (named whatever, no spaces)
|
||||
* Front Matter (below)
|
||||
* Write Blog Post
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### 4.2 Make a file
|
||||
Navigate to the _posts folder of the website and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### 4.3 Front Matter
|
||||
```
|
||||
---
|
||||
layout: post
|
||||
title: CHANGE TO YOUR TITLE
|
||||
summary: A BRIEF ONE OR TWO SENTENCE SUMMARY
|
||||
tags: [CHOOSE, RELEVANT, TAGS, AND, SEPARATE, THEM, BY, COMMAS, KEEP, THE, BRACKETS]
|
||||
author: YOUR NAME OR HANDLE HERE
|
||||
---
|
||||
```
|
||||
|
||||
### 4.4 Write
|
||||
After the front matter is finished you are free to write the remainder of your blog post in markdown.
|
||||
|
||||
### 4.5 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test that your page appears in the 'News' section of the website, as well as the sidebars.
|
||||
|
||||
### 4.6 Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 5.0 How to make a User Guide
|
||||
|
||||
### 5.1 Quick Start
|
||||
|
||||
* Make file in /resources/user-guides with a .md ending and no spaces in filename.
|
||||
* Front Matter as in 5.3
|
||||
* Write User Guide
|
||||
* Add guide using markdown in the correct category in /resources/user-guides/index.md being careful not to mess with any indentation
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### 5.2 Make a file
|
||||
Navigate to the /resources/user-guides folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### 5.3 Front Matter
|
||||
```
|
||||
---
|
||||
layout: static_page
|
||||
title: TITLE OF YOUR USER GUIDE
|
||||
---
|
||||
```
|
||||
|
||||
### 5.4 Write
|
||||
Write your user guide. Be succinct but thorough. Remember, people will be using your guides when they need help. Make sure all the information is there. Feel free to use images or screenshots if necessary to help get your point across.
|
||||
|
||||
### 5.5 Add Guide to the 'User Guide' landing page
|
||||
In the /resources/user-guides folder, find the file labeled index.md and open it.
|
||||
|
||||
DO NOT CHANGE ANYTHING IN THIS DOCUMENT BESIDES WHAT YOU ARE INSTRUCTED TO.
|
||||
|
||||
This file will look quite different because it's HTML. Don't panic. Simply Ctrl + F (i.e. the find feature) and search for the category that you want to put your User Guide in. You will see there are some sections that are not indented like the others. They are flush with the left side of the screen. **Do not change the indentation.** You can put markdown in these areas.
|
||||
|
||||
Once you've identified the non-indented area under the category you would like your User Guide to be under, you can use markdown to insert your link underneath the others. `[TITLE OF USER GUIDE](LINK-TO-USER-GUIDE.html)`. Please note that the file name in between the paranthases must be EXACTLY the same name as the file name you made in step 5.2, but with a `.html` at the end instead of `.md`.
|
||||
|
||||
In the event that you think your User Guide should be in a new Category that doesn't exist yet, contact rehrar to make one for you.
|
||||
|
||||
### 5.6 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test that your link appears in the correct category and that it leads to your User Guide when clicked. Test your User Guide in the browser and contact rehrar if there are any bugs.
|
||||
|
||||
### 5.7 Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 6.0 How to make a Moneropedia Entry
|
||||
|
||||
### 6.1 Quick Start
|
||||
|
||||
### 6.2 Make a file
|
||||
Navigate to the /resources/moneropedia folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### 6.3 Front Matter
|
||||
```
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "PUT THE NAME OF THE TERM HERE IN QUOTE, THIS IS HOW IT WILL SHOW UP ON THE LANDING PAGE"
|
||||
terms: ["PUT", "TERMS", "HERE", "EXPLAINED", "BELOW"]
|
||||
summary: "PUT SUMMARY OF YOUR ENTRY HERE IN QUOTES"
|
||||
---
|
||||
```
|
||||
|
||||
There is one thing to highlight. The `terms:` section of the front matter can be filled with as many terms as you would like. This is how other Moneropedia entries will link to this page. You can link to other Moneropedia entries as well in your page by putting an ampersand before the term used, i.e. `@THE-TERM-USED`. This will make an automatic link in the Moneropedia entry to the referred term, replace the @term with the word used in that terms `entry:` area of the front matter, and on hover it will show the summary. How cool is that?
|
||||
|
||||
### 6.4 Write
|
||||
Write your Moneropedia entry. Remember that you can link to other Moneropedia entries using `@term-used-in-entry` as described above. Just go to the .md file of the Moneropedia entry you want to link to and use any of the terms in the `terms:` field of the front matter. Be sure to write whichever one you choose EXACTLY as shown and preceded by an ampersand.
|
||||
|
||||
### 6.5 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test check the link to your entry is appearing on the alphabetical list of Moneropedia entries and that it leads to your entry when clicked. Test your Moneropedia entry in the browser and contact rehrar if there are any bugs.
|
||||
|
||||
### 6.6 Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 7.0 How to make a FFS Proposal
|
||||
|
||||
Before starting this section, it is recommended that you read the User Guide for [How the Forum Funding System works](#) as well as the [Forum Funding System Terms and Guidelines](#). If you do not read these expect your FFS proposal to be laughed at, not to mention not funded.
|
||||
|
||||
### 7.1 Quick Start
|
||||
|
||||
* Read [How the Forum Funding System works](#) and the [Forum Funding System Terms and Guidelines](#).
|
||||
* Make the .md file in the /forum-funding-system/proposals folder. Remember the name.
|
||||
* Choose your front matter layout based on whether your proposal is an Idea (`ffs-ideas`) or Open Task (`ffs-ot`) as specified in the above reading
|
||||
* Fill out the rest of the Front Matter below, leaving the `address` and `paymentid` sections empty
|
||||
* Edit the ffs.yml file. I strongly recommend you read this section.
|
||||
* Write the proposal
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### 7.2 Make the proposal
|
||||
|
||||
Navigate to the /forum-funding-system/proposals folder and make a new file. Be sure the file name has no spaces and the ending is .md. It is very important that you remember the EXACT name of this file.
|
||||
|
||||
### 7.3 Front Matter
|
||||
|
||||
```
|
||||
---
|
||||
layout: ffs-ideas OR ffs-ot
|
||||
title: NAME OF YOUR PROPOSAL
|
||||
summary: A BRIEF SUMMARY OF YOUR PROPOSAL
|
||||
author: YOUR NAME OR HANDLE
|
||||
address:
|
||||
paymentid:
|
||||
---
|
||||
```
|
||||
|
||||
The layout will depend on if you are simply presenting an idea that you do not plan to do yourself or if you are presenting an idea that you are capable and willing to do, the chosen layout will be `ffs-ideas` or `ffs-ot` respectively. You can get more information in the [How the Forum Funding System works](#) User Guide. Fill out the next three sections as normal (title, summary, author), but leave the last two (address, paymentid) blank. Again, DO NOT PUT ANYTHING HERE.
|
||||
|
||||
### 7.4 Editing the .yml file
|
||||
|
||||
Navigate to the /_data folder and open the file titled `ffs.yml`. In this file you will find a long list of FFS proposals.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Identify the section you will be placing your proposal in. If you used `ffs-ideas` in the layout variable in the front matter then you will be putting your proposal in `stage: ideas`, and if you used `ffs-ot` in the layout, then you will be putting your proposal in the `stage: Open Tasks`. Copy the following code:
|
||||
|
||||
```
|
||||
- name:
|
||||
url: /forum-funding-system/proposals/
|
||||
summary:
|
||||
author:
|
||||
```
|
||||
|
||||
and paste it as the very top underneath the `proposals:`.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail. If in doubt, put the line with the hyphen (-name) all the way to the left and press space four time, and then put the remainder of the variables all the way to the left and press space six times.**
|
||||
|
||||
Fill in the information.
|
||||
* `name:` should be the same as the title chosen in 7.3
|
||||
* for `url:` you should append the EXACT name of the file as chosen in 7.2 to the current string but with `.html` at the end instead of `.md`. So it should look like `/forum-funding-system/proposals/YOUR-FILE-NAME.html`
|
||||
* `summary:` should be the same summary copy and pasted from the front matter in 7.3
|
||||
* `author:` should be your name or handle, again the same as the front matter in 7.3
|
||||
|
||||
Sorry for the repetition here, but it's how Jekyll is working to put things correctly.
|
||||
|
||||
### 7.5 Write the proposal
|
||||
Go ahead and write your proposal now. Go back to your .md file in `/forum-funding-system/proposals`. Be sure to follow the [Forum Funding System Terms and Guidelines](#). Let me be the first to thank you for wanting to contribute your time and energy to better Monero.
|
||||
|
||||
### 7.6 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `ffs.yml` file back in 7.4. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Forum Funding System section of the website and make sure that your proposal is showing up in the correct areas, and that when the linked is clicked it takes you to the correct page with your proposal. Use this time to read everything for accuracy and make any changes. If not, you will have to do multiple PRs to make edits and updates. It is this way by design so we can keep track of edits made by authors.
|
||||
|
||||
### 7.7 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 8.0 How to update the Team page
|
||||
|
||||
If you are acting on behalf of another individual, please make sure you get their permission first before adding them onto the Team page.
|
||||
|
||||
### 8.1 Change the .yml file
|
||||
Navigate to the `/_data/` folder and open `team.yml`. You will notice a long list separated by main `-area:` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the area that you want to update and copy the code below:
|
||||
```
|
||||
- name:
|
||||
url:
|
||||
```
|
||||
Put the name or handle of the person in the `name` section and in the `url:` section put the link to their GitHub URL (it must have https:// at the beginning). If they have no GitHub, then you may leave it blank, it won't mess anything up.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### 8.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `team.yml` file back in 8.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Team page `/community/team/` and check to see that the contributor is showing up in the correct place. Click their GitHub link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 8.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 9.0 How to make an Event
|
||||
|
||||
### 9.1 Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `events.yml`. You will notice a list separated by hyphenated `-event` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the area that you want to update and copy the code below:
|
||||
```
|
||||
- event:
|
||||
where:
|
||||
when:
|
||||
description:
|
||||
link:
|
||||
```
|
||||
and paste it IN THE CHRONOLOGICAL ORDER that it will be in. So if there is an event happening before yours, make sure it is higher up than yours. If there is an event happening AFTER yours, make sure it is after your event.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `event:` The name of the event goes here as well as the date. The recommended format is: `Event Name - January 1st, 2000`
|
||||
* `where:` Where the event will take place. Vanue name and address are recommended.
|
||||
* `when:` Date and time
|
||||
* `description:` Descriptoin of the happenings of your event
|
||||
* `link:` The website of your event (if applicable, this can be left blank and everything will be ok). This link must have http:// at the beginning if it is an external link.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### 9.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `events.yml` file back in 9.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Events page `/community/events/` and check to see that the event is showing up in the correct place. Click their Event url link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 9.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 10.0 How to update the Roadmap
|
||||
|
||||
### 10.1 Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `roadmap.yml`. You will notice a list separated by hyphenated `-year` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the year that you want to update and copy the code below:
|
||||
```
|
||||
- name:
|
||||
date:
|
||||
status:
|
||||
```
|
||||
and paste it in the correct years `accomplishments:` section IN THE CHRONOLOGICAL ORDER that it will be in. So if there is a accomplishment that happened/is happening before the one you are inputting, make sure it is higher up than yours. If there is an accomplishment that happened/is happening AFTER yours, make sure it is after yours. If you don't have exact dates, just do your best to estimate.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `name:` The name of the accomplishment. Try to keep it short, a sentence or two at most.
|
||||
* `date:` When the accomplishment happened (past) or when it is expected to happen (future)
|
||||
* `status:` If the task is done, put `completed`, if the task is currently in the works put `ongoing`, and if work on the task has not yet started to your knowledge, but is expected to, put `upcoming`.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### 10.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `roadmap.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Events page `/resources/roadmap/` and check to see that the newly added accomplishment is showing up in the correct place in the correct year. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 10.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 11.0 How to add a new Merchant
|
||||
|
||||
### 11.1 Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `merchants.yml`. You will notice a list separated by hyphenated `-category` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the category that best describes your business/service and copy the code below:
|
||||
```
|
||||
- name:
|
||||
url:
|
||||
```
|
||||
and paste it in the correct category under the `merchants:` section.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `name:` The name of the the business/service.
|
||||
* `url:` The external url of the business/service. This link must have http:// (or https://) at the beginning if it is an external link.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### 11.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `merchants.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Merchants page `/community/merchants/` and check to see that the business is showing up in the correct category and that the link is redirecting correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 11.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 12.0 How to add a question to the FAQ
|
||||
|
||||
### 12.1 Copy/Paste Code
|
||||
Navigate to the `/get-started/faq` folder and open the `index.md` file. Inside you will see HTML code, but you will see it is very repetetive.
|
||||
|
||||
Copy the code below:
|
||||
```
|
||||
<div class="tab">
|
||||
<input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
|
||||
<label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
|
||||
|
||||
<div class="tab-content" markdown="1">
|
||||
|
||||
CHANGE ANSWER
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
```
|
||||
And paste it at the very bottom of the file. Literally underneath everything else.
|
||||
|
||||
Now we're going to change just a couple of things. Find the section with:
|
||||
```
|
||||
<input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
|
||||
<label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
|
||||
```
|
||||
|
||||
and change the sections in between the quotes that say 'CHANGETHIS'. Leave the first part `tab-` alone. You can change it to anything really, as long as they are identical in the input and label, but it's good to see what number is on the last FAQ question (i.e. `tab-nine`) and make it the next number.
|
||||
|
||||
Now inside the label tag you're going to find where it says 'CHANGE QUESTION' and change it to the Question you want answered.
|
||||
|
||||
Lastly, find the words 'CHANGE ANSWER' and change it to the answer of your question.
|
||||
|
||||
**DO NOT MESS WITH THE INDENTATION HERE. The div that has `markdown=1` MUST be flush with the left side, the answer to the question must start flush with the left side, and the `</div>` MUST be flush with the left side. **
|
||||
|
||||
### 12.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build is successful, go to the FAQ page `/get-started/faq/` and check to see that your question is showing up and, when clicked, the answer drops down. If not, check to make sure that the `id="tab-CHANGETHIS"` in the input and the `for="CHANGETHIS"` in the label are identical to each other. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 12.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
|
||||
## 13.0 Website License
|
||||
|
||||
Copyright (c) 2014-2017, The Monero Project
|
||||
|
||||
|
|
@ -53,4 +430,4 @@ Redistribution and use in source and binary forms, with or without modification,
|
|||
|
||||
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
|
||||
|
||||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
|
|
@ -11,6 +11,7 @@ markdown: kramdown
|
|||
# TODO: smart quotes are actually quite pretty, so this is perhaps better handled via a plugin that reverts them for CLI blocks
|
||||
kramdown:
|
||||
smart_quotes: ["apos", "apos", "quot", "quot"]
|
||||
input: GFM
|
||||
|
||||
exclude: ["README.md"]
|
||||
gems: [jekyll-paginate]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
- platform: Windows, 64-bit
|
||||
icon: windows.svg
|
||||
id: windows
|
||||
icon: icon-windows
|
||||
cli_url: win64
|
||||
cli_hash: 2fbda6f6b1051053703e40cf77b6c6e11334509ad03a3c22d89b6bcb05615910
|
||||
gui_url: win64
|
||||
|
|
@ -9,7 +10,7 @@
|
|||
blockchain: win
|
||||
|
||||
- platform: Windows, 32-bit
|
||||
icon: windows.svg
|
||||
icon: icon-windows
|
||||
cli_url: win32
|
||||
cli_hash: da628a45adfcb8be44df06ac904711d644d608c4eb6479a5d256062a5f6d74de
|
||||
version: 0.10.3.1
|
||||
|
|
@ -17,7 +18,8 @@
|
|||
blockchain: win
|
||||
|
||||
- platform: Mac OS X, 64-bit
|
||||
icon: apple.svg
|
||||
id: mac
|
||||
icon: icon-apple
|
||||
cli_url: mac64
|
||||
cli_hash: fd17d55a8c9e901ff4064c39d9e14786cdd077aff9b3bb556e60d3a5e322050c
|
||||
gui_url: mac64
|
||||
|
|
@ -27,7 +29,8 @@
|
|||
blockchain: mac
|
||||
|
||||
- platform: Linux, 64-bit
|
||||
icon: linux.svg
|
||||
id: linux
|
||||
icon: icon-linux
|
||||
cli_url: linux64
|
||||
cli_hash: 8db80f8cc4f80d4106db807432828df730a59eac78972ea81652aa6b9bac04ad
|
||||
gui_url: linux64
|
||||
|
|
@ -37,7 +40,7 @@
|
|||
blockchain: linux
|
||||
|
||||
- platform: Linux, 32-bit
|
||||
icon: linux.svg
|
||||
icon: icon-linux
|
||||
cli_url: linux32
|
||||
cli_hash: abc99f3928f4083bd1a380a869253e07bee9950e0aeb6388e9493bc0f0ec3f53
|
||||
gui_url: linux32
|
||||
|
|
@ -47,7 +50,8 @@
|
|||
blockchain: linux
|
||||
|
||||
- platform: ARMv7
|
||||
icon: arm.svg
|
||||
id: arm
|
||||
icon: icon-arm
|
||||
cli_url: linuxarm7
|
||||
cli_hash: 8473fa20e0db4a3d3e46120cdf92c55be6a159478c511e21f7b77aa05d6c1910
|
||||
version: 0.10.3.1
|
||||
|
|
@ -55,7 +59,7 @@
|
|||
blockchain: arm
|
||||
|
||||
- platform: ARMv8
|
||||
icon: arm.svg
|
||||
icon: icon-arm
|
||||
cli_url: linuxarm8
|
||||
cli_hash: 451f65e4846b92d54859e22a5d92124557b397b4208d8752d5289d0262573c3c
|
||||
version: 0.10.3.1
|
||||
|
|
@ -63,15 +67,23 @@
|
|||
blockchain: arm
|
||||
|
||||
- platform: FreeBSD, 64-bit
|
||||
icon: freebsd.svg
|
||||
id: bsd
|
||||
icon: icon-freebsd
|
||||
cli_url: freebsd64
|
||||
cli_hash: 4c66a76752e18ae70b5fb1c728f0d2780eb129a6c8c7d0dee7ba02e05d91efae
|
||||
version: 0.10.3.1
|
||||
tag: Wolfram Warptangent
|
||||
blockchain: freebsd
|
||||
|
||||
- platform: Source Code
|
||||
icon: github.svg
|
||||
- platform: Source Code & Blockchain
|
||||
id: source
|
||||
icon: icon-github
|
||||
cli_url: https://github.com/monero-project/bitmonero
|
||||
cli_hash: source
|
||||
version: Bleeding edge (possibly unstable)
|
||||
version: Bleeding edge (possibly unstable)
|
||||
|
||||
- platform: Mobile & Light Wallets
|
||||
id: mobilelight
|
||||
|
||||
- platform: Hardware Wallets
|
||||
id: hardware
|
||||
5
_data/events.yml
Normal file
5
_data/events.yml
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
- event: Monero Meetup (Dublin, Ireland) - June 26th, 2017
|
||||
where: J.W. Sweetman Craft Brewery, 1-2 Burgh Quay, Dublin 2, Dublin, Ireland
|
||||
when: 7:00 PM - Monday, June 26, 2017
|
||||
description: The meeting will cover the history of privacy and fungibility in Bitcoin, discuss several approaches to these problems, and explain how Monero achieves its privacy in detail. Justin will discuss the next steps in development going forward and the limitations compared to other coins. Finally, there will be a Q&A session after the meeting, where he can clear up some final thoughts.
|
||||
link: https://www.meetup.com/Bitcoin-Dublin/events/240152422/
|
||||
34
_data/ffs.yml
Normal file
34
_data/ffs.yml
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
- stage: Ideas
|
||||
proposals:
|
||||
- name: Fake. Nothing here yet. Check WiP and Completed Proposals.
|
||||
url: #
|
||||
summary: This is for the best ideas ever!
|
||||
author: rehrar
|
||||
|
||||
- stage: Open Tasks
|
||||
proposals:
|
||||
- name: Fake. Nothing here yet. Check WiP and Completed Proposals.
|
||||
url: #
|
||||
summary: This is for the best ideas ever!
|
||||
author: rehrar
|
||||
|
||||
- stage: Funding Required
|
||||
proposals:
|
||||
- name: Monero Bounty For HackerOne
|
||||
url: /forum-funding-system/proposals/monero-bounty-hackerone.html
|
||||
summary: we need dedicated funds to satisfy bounty for Monero and all Monero sub-projects on hackerone.com/monero
|
||||
author: anonimal
|
||||
|
||||
- stage: Work in Progress
|
||||
proposals:
|
||||
- name: Getmonero.org Redesign
|
||||
url: /forum-funding-system/proposals/getmonero-redesign.html
|
||||
summary: Redesign the official getmonero.org website to make it more accessible and aesthetically pleasing.
|
||||
author: rehrar
|
||||
|
||||
- stage: Completed Proposals
|
||||
proposals:
|
||||
- name: What is Monero? is produced and open-sourced
|
||||
url: /forum-funding-system/proposals/whatismonero-produced.html
|
||||
summary: Make an introduction video to Monero.
|
||||
author: savandra
|
||||
79
_data/roadmap.yml
Normal file
79
_data/roadmap.yml
Normal file
|
|
@ -0,0 +1,79 @@
|
|||
- year: 2014
|
||||
accomplishments:
|
||||
- name: Launched on Bitcointalk
|
||||
date: April 18, 2014
|
||||
status: completed
|
||||
- name: Renamed from Bitmonero to Monero
|
||||
date: April 23, 2014
|
||||
status: completed
|
||||
- name: Recovered from a spam attack
|
||||
date: September 4, 2014
|
||||
status: completed
|
||||
- name: Monero Research Lab Papers 1 and 2 published
|
||||
date: September 12, 2014
|
||||
status: completed
|
||||
- name: Monero Research Lab Paper 3 published
|
||||
date: September 25, 2014
|
||||
status: completed
|
||||
- name: 0.8.8.6 released
|
||||
date: December 8, 2014
|
||||
status: completed
|
||||
- year: 2015
|
||||
accomplishments:
|
||||
- name: Monero Research Lab Paper 4 published.
|
||||
date: January 26, 2015
|
||||
status: completed
|
||||
- year: 2016
|
||||
accomplishments:
|
||||
- name: 0.9.0 Hydrogen Helix published
|
||||
date: January 1, 2016
|
||||
status: completed
|
||||
- name: Monero Research Lab Paper 5 published
|
||||
date: February, 2016
|
||||
status: completed
|
||||
- name: Hardfork to impose minimum ringsize 3 on all transactions
|
||||
date: March, 2016
|
||||
status: completed
|
||||
- name: 0.10.0 Wolfram Warptangent released
|
||||
date: September 18, 2016
|
||||
status: completed
|
||||
- name: Official GUI Beta 1 released
|
||||
date: December, 2016
|
||||
status: completed
|
||||
- year: 2017
|
||||
accomplishments:
|
||||
- name: RingCT enabled. Sees quick acceptance.
|
||||
date: January, 2017
|
||||
status: completed
|
||||
- name: 0.10.2 released; critical vulnerability patched
|
||||
date: February 22, 2017
|
||||
status: completed
|
||||
- name: Hardfork for dynamic block and dynamic fee improvements
|
||||
date: April, 2017
|
||||
status: completed
|
||||
- name: Hardfork for increased ringsize and mandatory RingCT
|
||||
date: September, 2017
|
||||
status: upcoming
|
||||
- name: Fluffy blocks
|
||||
date:
|
||||
status: ongoing
|
||||
- name: 0MQ/ZeroMQ
|
||||
date:
|
||||
status: ongoing
|
||||
- name: GUI out of beta
|
||||
date:
|
||||
status: ongoing
|
||||
- name: Kovri Alpha release
|
||||
date:
|
||||
status: ongoing
|
||||
- name: Website Redesign
|
||||
date:
|
||||
status: ongoing
|
||||
- year: 2018
|
||||
accomplishments:
|
||||
- name: Research papers
|
||||
date:
|
||||
status: upcoming
|
||||
- name: Second layer solutions for speed and scalability
|
||||
date:
|
||||
status: upcoming
|
||||
64
_data/team.yml
Normal file
64
_data/team.yml
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
- area: Core
|
||||
member:
|
||||
- name: othe
|
||||
url:
|
||||
email: othe@getmonero.org
|
||||
description:
|
||||
- name: smooth
|
||||
url: https://github.com/iamsmooth
|
||||
email: smooth@getmonero.org
|
||||
description:
|
||||
- name: Riccardo "fluffypony" Spagni
|
||||
url: https://github.com/fluffypony
|
||||
email: ric@getmonero.org
|
||||
description:
|
||||
- name: tacotime
|
||||
url:
|
||||
email: tacotime@getmonero.org
|
||||
description:
|
||||
- name: Francisco "ArticMine" Cabañas
|
||||
url: https://github.com/ArticMine
|
||||
email: articmine@getmonero.org
|
||||
description:
|
||||
- name: luigi1111
|
||||
url: https://github.com/luigi1111
|
||||
email: luigi1111@getmonero.org
|
||||
description:
|
||||
- name: NoodleDoodle
|
||||
url: https://github.com/NoodleDoodleNoodleDoodleNoodleDoodleNoo
|
||||
email: noodledoodle@getmonero.org
|
||||
description:
|
||||
- area: Developers
|
||||
member:
|
||||
- name: moneromooo
|
||||
url: https://github.com/moneromooo-monero
|
||||
- name: hyc
|
||||
url: https://github.com/hyc
|
||||
- name: Thomas Winget
|
||||
url: https://github.com/tewinget
|
||||
- name: Jaqueeee
|
||||
url: https://github.com/Jaqueeee
|
||||
- name: mikezackles
|
||||
url: https://github.com/mikezackles
|
||||
- name: Paul Shapiro
|
||||
url: https://github.com/paulshapiro
|
||||
- area: Community
|
||||
member:
|
||||
- name: dEBRUYNE
|
||||
url:
|
||||
- name: SamsungGalaxyPlayer
|
||||
url:
|
||||
- name: gingeropolous
|
||||
url:
|
||||
- area: Special Thanks
|
||||
member:
|
||||
- name: warptangent
|
||||
url: https://github.com/warptangent
|
||||
- name: Shen Noether
|
||||
url:
|
||||
- area: Monero Research Lab
|
||||
member:
|
||||
- name: Brandon Goodell (Surae Noether)
|
||||
url:
|
||||
- name: Sarang Noether
|
||||
url:
|
||||
|
|
@ -1,30 +1,61 @@
|
|||
<div class="footer">
|
||||
<div class="container">
|
||||
<p>
|
||||
<strong style="color: #ffffff;">[ <a href="/legal/terms">{% t global.terms %}</a> | <a href="/legal/privacy">{% t global.privacy %}</a> | <a href="/legal/copyright">{% t global.copyright %}</a> ]</strong>
|
||||
<strong style="color: #ffffff;">[ <a href="https://github.com/monero-project/monero-site/edit/master/{{ page.path }}">{%t global.edit %}</a> ]</strong>
|
||||
<a href="https://getmonero.org/feed.xml"><i class="fa fa-2x fa-rss-square"></i></a>
|
||||
<a href="mailto:dev@getmonero.org"><i class="fa fa-2x fa-envelope-square"></i></a>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="container-fluid">
|
||||
<div class="container">
|
||||
<div class="row around-xs footer-wrapper">
|
||||
<div class="col-sm-3 col-xs-6">
|
||||
<h3>Resources</h3>
|
||||
<ul class="list-unstyled">
|
||||
<li><a href="/resources/about/" class="white">About Monero</a></li>
|
||||
<li><a href="/resources/moneropedia/" class="white">Moneropedia</a></li>
|
||||
<li><a href="/resources/developer-guides/" class="white">Developer Guides</a></li>
|
||||
<li><a href="/resources/user-guides/" class="white">User Guides</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-sm-3 col-xs-6">
|
||||
<h3>IRC Channel</h3>
|
||||
<ul class="list-unstyled">
|
||||
<li><a href="irc://chat.freenode.net/#monero" class="white">#monero (General)</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-dev" class="white">#monero-dev (Development)</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-markets" class="white">#monero-markets (Markets)</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-pools" class="white">#monero-pools (Mining)</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-community" class="white">#monero-community (Community)</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-sm-3 col-xs-6">
|
||||
<h3>Community</h3>
|
||||
<ul class="list-unstyled">
|
||||
<li><a href="https://reddit.com/r/monero" class="white">Reddit</a></li>
|
||||
<li><a href="https://monero.stackexchange.com" class="white">Stack Exchange</a></li>
|
||||
<li><a href="https://bitcointalk.org/index.php?topic=583449.0" class="white">BitcoinTalk Thread</a></li>
|
||||
<li><a href="https://monero.slack.com" class="white">Slack Chat</a></li>
|
||||
<li><a href="https://telegram.me/bitmonero" class="white">Telegram Chat</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="col-sm-3 col-xs-6">
|
||||
<h3>The Monero Project</h3>
|
||||
<ul class="list-unstyled">
|
||||
<li><a href="https://openalias.org" class="white">Open Alias</a></li>
|
||||
<li><a href="https://getkovri.org" class="white">Kovri</a></li>
|
||||
<li><a href="/resources/research-lab/" class="white">Monero Research Lab</a></li>
|
||||
<li><a href="#" class="white">Monero Press Kit</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row center-xs">
|
||||
<div class="social-icons">
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<ul class="list-unstyled list-inline">
|
||||
<li><a href="/legal/" class="white footer-link">Legal</a></li>
|
||||
<li><a href="https://github.com/monero-project" class="white footer-link">Source Code</a></li>
|
||||
<li><a href="#" class="white footer-link">Coin Specs</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
|
||||
<!-- JS -->
|
||||
<script src="//static.getmonero.org/scripts.js"></script>
|
||||
<script type="text/javascript">
|
||||
$(document).ready(function(){
|
||||
$('[data-toggle="tooltip"]').tooltip();
|
||||
});
|
||||
|
||||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
|
||||
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
|
||||
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
|
||||
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
|
||||
|
||||
ga('create', 'UA-53312765-1', 'auto');
|
||||
ga('require', 'linkid', 'linkid.js');
|
||||
ga('send', 'pageview');
|
||||
</script>
|
||||
|
||||
{% include hostflag.html %}
|
||||
|
|
@ -14,26 +14,15 @@
|
|||
<meta property="og:url" content="https://getmonero.org{{ page.url }}">
|
||||
<meta property="og:type" content="website">
|
||||
|
||||
<link rel="apple-touch-icon" sizes="57x57" href="/apple-touch-icon-57x57.png">
|
||||
<link rel="apple-touch-icon" sizes="60x60" href="/apple-touch-icon-60x60.png">
|
||||
<link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72x72.png">
|
||||
<link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png">
|
||||
<link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png">
|
||||
<link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png">
|
||||
<link rel="apple-touch-icon" sizes="144x144" href="/apple-touch-icon-144x144.png">
|
||||
<link rel="apple-touch-icon" sizes="152x152" href="/apple-touch-icon-152x152.png">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon-180x180.png">
|
||||
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
|
||||
<link rel="icon" type="image/png" href="/favicon-194x194.png" sizes="194x194">
|
||||
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
|
||||
<link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
|
||||
<link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
|
||||
<link rel="manifest" href="/manifest.json">
|
||||
<meta name="msapplication-TileColor" content="#2d89ef">
|
||||
<meta name="msapplication-TileImage" content="/mstile-144x144.png">
|
||||
<meta name="theme-color" content="#ffffff">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/meta/apple-touch-icon.png">
|
||||
<link rel="icon" type="image/png" sizes="32x32" href="/meta/favicon-32x32.png">
|
||||
<link rel="icon" type="image/png" sizes="16x16" href="/meta/favicon-16x16.png">
|
||||
<link rel="manifest" href="/meta/manifest.json">
|
||||
<link rel="mask-icon" href="/meta/safari-pinned-tab.svg" color="#5bbad5">
|
||||
<meta name="theme-color" content="#ffffff">
|
||||
|
||||
<link href="/css/custom.css" rel="stylesheet">
|
||||
|
||||
<link href="//static.getmonero.org/style.css?1" rel="stylesheet">
|
||||
|
||||
<meta name="msapplication-config" content="/ietemplates/ieconfig.xml">
|
||||
|
||||
|
|
|
|||
|
|
@ -1,76 +1,162 @@
|
|||
<!-- Static navbar -->
|
||||
<div class="navbar navbar-default navbar-static-top" role="navigation">
|
||||
<div class="navbar-wrapper">
|
||||
<div class="navbar-header">
|
||||
<input type="checkbox" id="menu-toggle">
|
||||
<label for="menu-toggle" class="navbar-toggle">
|
||||
<span class="sr-only">Toggle navigation</span>
|
||||
<span class="icon-bar"></span>
|
||||
<span class="icon-bar"></span>
|
||||
<span class="icon-bar"></span>
|
||||
</label>
|
||||
<a class="navbar-brand" href="/"><img class="logo" src="//static.getmonero.org/images/logo.svg"></a>
|
||||
<ul class="nav navbar-nav navbar-right navbar-collapse">
|
||||
<li><a class="yellow" href="https://forum.getmonero.org">{% t menu.forum %}</a></li>
|
||||
<li class="dropdown">
|
||||
<input type="checkbox" class="dropdown-input" id="drop-1"/><label for="drop-1" class="purple">{% t menu.blog %} <span class="caret"></span></label>
|
||||
<ul class="dropdown-menu" role="menu">
|
||||
<li><a href="/blog">{% t menu.allblog %}</a></li>
|
||||
<li><a href="/blog/tags/monero%20missives">{% t menu.missives %}</a></li>
|
||||
<li><a href="/blog/tags/dev%20diaries">{% t menu.devdiaries %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="dropdown">
|
||||
<input type="checkbox" id="drop-2"/><label for="drop-2" class="red">{% t global.getting_started %} <span class="caret"></span></label>
|
||||
<ul class="dropdown-menu" role="menu">
|
||||
<li><a href="/getting-started/choose">{% t menu.choose %}</a></li>
|
||||
<li><a href="/getting-started/running">{% t menu.running %}</a></li>
|
||||
<li><a href="/getting-started/contribute">{% t menu.contribute %}</a></li>
|
||||
<li><a href="/getting-started/donate">{% t menu.donations %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li><a href="/downloads">{% t menu.downloads %}</a></li>
|
||||
<li><a href="https://github.com/monero-project">{% t menu.github %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li><a href="/getting-started/accepting">{% t menu.accepting %}</a></li>
|
||||
<li><a href="/getting-started/merchants">{% t menu.merchants %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="dropdown">
|
||||
<input type="checkbox" id="drop-3"/><label for="drop-3" class="orange">{% t menu.knowledge_base %} <span class="caret"></span></label>
|
||||
<ul class="dropdown-menu" role="menu">
|
||||
<li><a href="/knowledge-base/about">{% t menu.about %}</a></li>
|
||||
<li><a href="/knowledge-base/people">{% t menu.people %}</a></li>
|
||||
<li><a href="/knowledge-base/moneropedia">{% t global.wiki %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li><a href="/knowledge-base/user-guides">{% t menu.userguides %}</a></li>
|
||||
<li><a href="/knowledge-base/developer-guides">{% t menu.developerguides %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li><a href="/design-goals">{% t menu.goals %}</a></li>
|
||||
<li><a href="/research-lab">{% t menu.lab %}</a></li>
|
||||
<li><a href="/knowledge-base/openalias">{% t menu.openalias %}</a></li>
|
||||
<li><a href="/knowledge-base/projects">{% t menu.projects %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="dropdown">
|
||||
<input type="checkbox" id="drop-4"/><label for="drop-4" class="softyellow last">{% t menu.community %} <span class="caret"></span></label>
|
||||
<ul class="dropdown-menu" role="menu">
|
||||
<li><a href="https://forum.getmonero.org">{% t menu.forum %}</a></li>
|
||||
<li><a href="https://www.reddit.com/r/monero/">{% t menu.reddit %}</a></li>
|
||||
<li><a href="https://monero.stackexchange.com">{% t menu.stackexchange %}</a></li>
|
||||
<li><a href="https://bitcointalk.org/index.php?topic=583449.0">{% t menu.bitcointalk %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li><a href="https://monero.slack.com/">{% t menu.slack %}</a></li>
|
||||
<li><a href="https://telegram.me/bitmonero">{% t menu.telegram %}</a></li>
|
||||
<li class="divider"></li>
|
||||
<li class="dropdown-header">{% t menu.irc %}</li>
|
||||
<li><a href="irc://chat.freenode.net/#monero">{% t menu.irc-general %}</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-dev">{% t menu.irc-development %}</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-otc">{% t menu.irc-trading %}</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-markets">{% t menu.irc-markets %}</a></li>
|
||||
<li><a href="irc://chat.freenode.net/#monero-pools">{% t menu.irc-mining %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="mob-nav">
|
||||
<input class="burger-check" id="mobile-burger" type="checkbox"><label for="mobile-burger" class="burger"></label>
|
||||
|
||||
<div class="slide-in-nav">
|
||||
<div class="container slide-in">
|
||||
<div class="row">
|
||||
<div class="col-xs-12 dropdown text-center nav-item">
|
||||
<label for="drop1">Get Started<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop1" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/get-started/what-is-monero/">What Is Monero?</a>
|
||||
<a href="/get-started/using/">Using</a>
|
||||
<a href="/get-started/accepting/">Accepting</a>
|
||||
<a href="/get-started/contributing/">Contributing</a>
|
||||
<a href="/get-started/mining/">Mining</a>
|
||||
<a href="/get-started/faq">FAQ</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12">
|
||||
<div class="text-center nav-item">
|
||||
<a href="/downloads/">Downloads</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12 dropdown text-center nav-item">
|
||||
<label for="drop2">Recent News<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop2" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/blog/">All Posts</a>
|
||||
<a href="/blog/tags/monero%20missives.html">Missives</a>
|
||||
<a href="/blog/tags/dev%20diaries.html">Meeting Logs</a>
|
||||
<a href="/blog/tags/releases.html">Releases</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12 dropdown text-center nav-item">
|
||||
<label for="drop4">Community<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop4" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/community/team/">Team</a>
|
||||
<a href="/community/hangouts/">Hangouts</a>
|
||||
<a href="/community/events/">Events</a>
|
||||
<a href="/community/sponsorships/">Sponsorships</a>
|
||||
<a href="/community/merchants/">Merchants</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12 dropdown text-center nav-item">
|
||||
<label for="drop3">Resources<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop3" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/resources/about/">About</a>
|
||||
<a href="/resources/roadmap/">Roadmap</a>
|
||||
<a href="/resources/research-lab/">Monero Research Lab</a>
|
||||
<a href="/resources/moneropedia/">Moneropedia</a>
|
||||
<a href="/resources/user-guides/">User Guides</a>
|
||||
<a href="/resources/developer-guides/">Developer Guides</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12">
|
||||
<div class="text-center nav-item mob">
|
||||
<a href="/forum-funding-system/">Forum Funding System</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12">
|
||||
<div class="text-center nav-item mob">
|
||||
<a href="/the-monero-project/">The Monero Project</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
<div class="desktop-nav">
|
||||
<nav class="container">
|
||||
<div class="topnav">
|
||||
<div class="row middle-xs">
|
||||
<div class="col-lg-4 col-md-4 col-sm-4 col-xs-4">
|
||||
<a href="/"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
|
||||
</div>
|
||||
<div class="col-lg-8 col-md-8 col-sm-8 topnav-list end-xs">
|
||||
<div class="row end-xs">
|
||||
<div class="col-md-12">
|
||||
<a href="/forum-funding-system/" class="mob top-link col-md-4">Forum Funding System</a>
|
||||
<a href="/the-monero-project/" class="mob top-link col-md-3">The Monero Project</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="botnav white-nav">
|
||||
<input class="burger-check" id="burger-check" type="checkbox"><label for="burger-check" class="burger"></label>
|
||||
<div class="row between-xs nav-items">
|
||||
<div class="col dropdown nav-item">
|
||||
<label for="drop1">Get Started<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop1" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/get-started/what-is-monero/">What Is Monero?</a>
|
||||
<a href="/get-started/using/">Using</a>
|
||||
<a href="/get-started/accepting/">Accepting</a>
|
||||
<a href="/get-started/contributing/">Contributing</a>
|
||||
<a href="/get-started/mining/">Mining</a>
|
||||
<a href="/get-started/faq">FAQ</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col nav-item">
|
||||
<a href="/downloads/">Downloads</a>
|
||||
</div>
|
||||
<div class="col dropdown nav-item">
|
||||
<label for="drop2">Recent News<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop2" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/blog/">All Posts</a>
|
||||
<a href="/blog/tags/monero%20missives.html">Missives</a>
|
||||
<a href="/blog/tags/dev%20diaries.html">Meeting Logs</a>
|
||||
<a href="/blog/tags/releases.html">Releases</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col dropdown nav-item">
|
||||
<label for="drop4">Community<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop4" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/community/team/">Team</a>
|
||||
<a href="/community/hangouts/">Hangouts</a>
|
||||
<a href="/community/events/">Events</a>
|
||||
<a href="/community/sponsorships/">Sponsorships</a>
|
||||
<a href="/community/merchants/">Merchants</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col dropdown nav-item">
|
||||
<label for="drop3">Resources<div class="arrow-down"></div></label>
|
||||
<input class="burger-checkdropdown" id="drop3" type="checkbox">
|
||||
<div class="dropdown-content">
|
||||
<a href="/resources/about/">About</a>
|
||||
<a href="/resources/roadmap/">Roadmap</a>
|
||||
<a href="/resources/research-lab/">Research Lab</a>
|
||||
<a href="/resources/moneropedia/">Moneropedia</a>
|
||||
<a href="/resources/user-guides/">User Guides</a>
|
||||
<a href="/resources/developer-guides/">Developer Guides</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
</div>
|
||||
<div class="mob bot-nav white-nav">
|
||||
<div class="row center-xs">
|
||||
<div class="col-xs-6">
|
||||
<a href="/"><img src="/img/monero-logo.png" alt="Monero Logo" class="monero-logo"></a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
13
_layouts/base.html
Normal file
13
_layouts/base.html
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
|
||||
{% include head.html %}
|
||||
|
||||
<body>
|
||||
<div class="page-wrapper">
|
||||
{% include header.html %}
|
||||
{{content}}
|
||||
{% include footer.html %}
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,5 +1,7 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
---
|
||||
layout: custom
|
||||
---
|
||||
|
||||
{% assign filename = page.path | remove: '.md' | split: '/' | last %}
|
||||
{% for data_tag in site.data.tags %}
|
||||
{% if data_tag.slug == filename %}
|
||||
|
|
@ -7,35 +9,68 @@
|
|||
{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
{% include head.html %}
|
||||
|
||||
<body>
|
||||
|
||||
{% include header.html %}
|
||||
|
||||
<div class="container main-content">
|
||||
|
||||
<div class="page-title">
|
||||
<!-- Icon is based on work by Sergiu Bagrin (http://pixelkit.com) and is licensed under Creative Commons BY 3.0 -->
|
||||
<img src="//static.getmonero.org/images/icon_tags.svg" class="title-icon"><h2 class="inline">{% t tags.all %}: <span class="kicks">{{ tag.name }}</span></h2>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
{% if site.tags[tag.slug] %}
|
||||
<div class="site-wrap">
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
<!-- left two-thirds block-->
|
||||
<div class="left two-thirds col-lg-8 col-md-8 col-sm-8 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="page-title">
|
||||
<h2 class="inline">{% t tags.all %}: <span class="kicks">{{ tag.name }}</span></h2>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{% if site.tags[tag.slug] %}
|
||||
{% for post in site.tags[tag.slug] %}
|
||||
<h3><a href="{{ post.url }}">{{ post.title }}</a></h3>
|
||||
<blockquote>
|
||||
<p>
|
||||
{{ post.summary }}
|
||||
</blockquote>
|
||||
</p>
|
||||
{% endfor %}
|
||||
{% else %}
|
||||
<h3>{% t tags.notags %}</h3>
|
||||
{% endif %}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- end left two-thirds block-->
|
||||
|
||||
<!-- right one-third block-->
|
||||
<div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
|
||||
<div class="sidebar col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col"><h2>Recent Posts</h2></div>
|
||||
</div>
|
||||
{% for post in site.posts limit:4 %}
|
||||
<div class="row start-xs info-block-row">
|
||||
<div class="col">
|
||||
<p><a href="{{ post.url }}">{{ post.title }}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Popular Tags</h2>
|
||||
</div>
|
||||
</div>
|
||||
{% for tag in site.data.tags limit:4 %}
|
||||
<div class="row start-xs">
|
||||
<div class="col">
|
||||
<p><a href="/blog/tags/{{ tag.slug }}.html">{{ tag.name }}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- end right one-third block-->
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</div>
|
||||
|
|
|
|||
7
_layouts/custom.html
Normal file
7
_layouts/custom.html
Normal file
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
---
|
||||
|
||||
<div class="site-wrap">
|
||||
{{content}}
|
||||
</div>
|
||||
|
|
@ -1,18 +1,5 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
|
||||
{% include head.html %}
|
||||
|
||||
<body>
|
||||
|
||||
{% include header.html %}
|
||||
|
||||
<div class="container main-content">
|
||||
{{ content }}
|
||||
</div>
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
---
|
||||
layout: base
|
||||
---
|
||||
<h1 class="text-center">{{page.title}}</h1>
|
||||
{{content}}
|
||||
17
_layouts/defaultnt.html
Normal file
17
_layouts/defaultnt.html
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col"><h2>Title Goes Here</h2></div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
30
_layouts/ffs-cp.html
Normal file
30
_layouts/ffs-cp.html
Normal file
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<div class="container ffs-breadcrumbs">
|
||||
|
||||
<p><a href="/forum-funding-system/">Forum Funding System</a> > <a href="/forum-funding-system/completed-proposals/">Completed Proposals</a> > {{page.title}}</p>
|
||||
|
||||
</div>
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{{page.title}}</h2>
|
||||
<p>by {{page.author}}</p>
|
||||
<div class="ffs-status complete">
|
||||
<p>This project has been completed. The proposal is kept here both to celebrate the achievements of the Monero community, and for historical accuracy about what was accomplished.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
48
_layouts/ffs-fr.html
Normal file
48
_layouts/ffs-fr.html
Normal file
|
|
@ -0,0 +1,48 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
|
||||
<div class="site-wrap">
|
||||
<div class="container ffs-breadcrumbs">
|
||||
|
||||
<p><a href="/forum-funding-system/">Forum Funding System</a> > <a href="/forum-funding-system/funding-required/">Funding Required</a> > {{page.title}}</p>
|
||||
|
||||
</div>
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>How to Contribute</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row">
|
||||
<div class="col-xs-12">
|
||||
<p>In order to contribute to the cause of <strong>{{page.title}}</strong> all you have to do is the following:</p>
|
||||
<p>Have a valid Monero address. If you don't have one, you can read on getting started!</p>
|
||||
<p>Send the amount of XMR that you wish to contribute to the address: <strong>{{page.address}}</strong></p>
|
||||
<p>Make sure that you enter a payment ID of <strong>{{page.paymentid}}</strong> in order for us to be able to assign your contribution to this specific project!</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{{page.title}}</h2>
|
||||
<p>by {{page.author}}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
27
_layouts/ffs-ideas.html
Normal file
27
_layouts/ffs-ideas.html
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<div class="container ffs-breadcrumbs">
|
||||
|
||||
<p><a href="/forum-funding-system/">Forum Funding System</a> > <a href="/forum-funding-system/ideas/">Ideas</a> > {{page.title}}</p>
|
||||
|
||||
</div>
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{{page.title}}</h2>
|
||||
<p>{{page.author}}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
28
_layouts/ffs-ot.html
Normal file
28
_layouts/ffs-ot.html
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<div class="container ffs-breadcrumbs">
|
||||
|
||||
<p><a href="/forum-funding-system/">Forum Funding System</a> > <a href="/forum-funding-system/open-tasks/">Open Tasks</a> > {{page.title}}</p>
|
||||
|
||||
</div>
|
||||
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{{page.title}}</h2>
|
||||
<p>{{page.author}}</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
32
_layouts/ffs-wip.html
Normal file
32
_layouts/ffs-wip.html
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<div class="site-wrap">
|
||||
|
||||
<div class="container ffs-breadcrumbs">
|
||||
|
||||
<p><a href="/forum-funding-system/">Forum Funding System</a> > <a href="/forum-funding-system/work-in-progress/">Work in Progress</a> > {{page.title}}</p>
|
||||
|
||||
</div>
|
||||
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>{{page.title}}</h2>
|
||||
<p>by {{page.author}}</p>
|
||||
<div class="ffs-status inprogress">
|
||||
<p>This project has been funded and is being worked on. Keep an eye out here at the bottom of the proposal for updates.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
17
_layouts/ffs.html
Normal file
17
_layouts/ffs.html
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
layout: default
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<a href="/forum-funding-system/ideas/">Back to Ideas</a>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
||||
<!-- JAVASCRIPT FOR DISQUS -->
|
||||
14
_layouts/full-text.html
Normal file
14
_layouts/full-text.html
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
layout: default
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
14
_layouts/full.html
Normal file
14
_layouts/full.html
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
layout: default
|
||||
---
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block">
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
|
@ -1,22 +1,16 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
|
||||
{% include head.html %}
|
||||
|
||||
<body>
|
||||
|
||||
{% include header.html %}
|
||||
|
||||
<div class="container main-content">
|
||||
<div class="page-title">
|
||||
<img src="//static.getmonero.org/images/icon_wiki.svg" class="title-icon"><h2 class="inline">{{ page.entry }} - <span class="softyellow-kicks">{% t global.wiki %}</span></h2>
|
||||
</div>
|
||||
|
||||
{{ content }}
|
||||
</div>
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
---
|
||||
layout: base
|
||||
---
|
||||
<h1 class="text-center">{{page.title}}</h1>
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<h2>{{page.entry}}</h2>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
layout: base
|
||||
---
|
||||
|
||||
{% assign post = page %}
|
||||
{% if post.tags.size > 0 %}
|
||||
{% capture tags_content %}Post tags {% if post.tags.size == 1 %}<i class="fa fa-tag"></i>{% else %}<i class="fa fa-tags"></i>{% endif %}: {% endcapture %}
|
||||
|
|
@ -11,32 +12,67 @@ layout: default
|
|||
{% endif %}
|
||||
{% endfor %}
|
||||
{% if tag %}
|
||||
{% capture tags_content_temp %}{{ tags_content }}<a href="/blog/tags/{{ tag.slug }}">{{ tag.name }}</a>{% if forloop.last == false %}, {% endif %}{% endcapture %}
|
||||
{% capture tags_content_temp %}{{ tags_content }}<a href="/blog/tags/{{ tag.slug }}.html">{{ tag.name }}</a>{% if forloop.last == false %}, {% endif %}{% endcapture %}
|
||||
{% assign tags_content = tags_content_temp %}
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
{% else %}
|
||||
{% assign tags_content = '' %}
|
||||
{% endif %}
|
||||
<div class="site-wrap post">
|
||||
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
<!-- left two-thirds block-->
|
||||
<div class="left two-thirds col-lg-8 col-md-8 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row">
|
||||
<div class="col"><h2>{{ page.title }}</h2>
|
||||
<p class="author">{% t blog.author %}: {% if page.author %}{{page.author}}{% else %}{{site.author}}{% endif%}</p></div>
|
||||
</div>
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
<hr>
|
||||
<p id="post-meta">{{ tags_content }}</p>
|
||||
</div>
|
||||
</div>
|
||||
<!-- end left two-thirds block-->
|
||||
|
||||
<!-- right one-third block-->
|
||||
<div class="right one-third col-lg-4 col-md-4 col-sm-12 col-xs-12">
|
||||
<div class="sidebar col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col"><h2>Recent Posts</h2></div>
|
||||
</div>
|
||||
{% for post in site.posts limit:4 %}
|
||||
<div class="row start-xs info-block-row">
|
||||
<div class="col">
|
||||
<p><a href="{{ post.url }}">{{ post.title }}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Popular Tags</h2>
|
||||
</div>
|
||||
</div>
|
||||
{% for tag in site.data.tags limit:4 %}
|
||||
<div class="row start-xs">
|
||||
<div class="col">
|
||||
<p><a href="/blog/tags/{{ tag.slug }}.html">{{ tag.name }}</a></p>
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
|
||||
<article>
|
||||
<header>
|
||||
<div class="page-title">
|
||||
<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->
|
||||
<img src="//static.getmonero.org/images/icon_blog_post.svg" class="title-icon"><h2 class="inline">{{ page.title }}</h2>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- end right one-third block-->
|
||||
</div>
|
||||
<span class="author">{% t blog.author %}: {% if page.author %}{{page.author}}{% else %}{{site.author}}{% endif%}</span>
|
||||
</header>
|
||||
|
||||
<p>{{ content }}</p>
|
||||
|
||||
<footer>
|
||||
<hr>
|
||||
<p id="post-meta">{{ tags_content }}</p>
|
||||
{% if post.forum %}
|
||||
<hr>
|
||||
<p id="post-comments"><h3 class="text-center"><a href="{{ post.forum }}">{% t blog.forum %}</a></h3></p>
|
||||
{% endif %}
|
||||
</footer>
|
||||
|
||||
</article>
|
||||
</section>
|
||||
</div>
|
||||
5
_layouts/proposal.html
Normal file
5
_layouts/proposal.html
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
layout: base
|
||||
---
|
||||
<h1 class="text-center">{{page.title}}</h1>
|
||||
{{content}}
|
||||
|
|
@ -1,23 +1,15 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
|
||||
{% include head.html %}
|
||||
|
||||
<body>
|
||||
|
||||
{% include header.html %}
|
||||
|
||||
<div class="container main-content">
|
||||
<div class="page-title">
|
||||
{{ page.attribution }}
|
||||
<img src="//static.getmonero.org/images/{{ page.icon }}.svg" class="title-icon"><h2 class="inline">{{ page.title-pre-kick }} <span class="{{ page.kick-class }}">{{ page.title-kick }}</span> {{ page.title-post-kick }}</h2>
|
||||
</div>
|
||||
|
||||
{{ content }}
|
||||
</div>
|
||||
|
||||
{% include footer.html %}
|
||||
|
||||
</body>
|
||||
|
||||
</html>
|
||||
---
|
||||
layout: base
|
||||
---
|
||||
<h1 class="text-center">{{page.title}}</h1>
|
||||
<div class="site-wrap">
|
||||
<!-- FULL WIDTH BLOCK -->
|
||||
<section class="container full">
|
||||
<div class="info-block text-adapt">
|
||||
<div>
|
||||
{{content}}
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<!-- END FULL WIDTH BLOCK -->
|
||||
</div>
|
||||
|
|
@ -38,7 +38,7 @@ module Jekyll
|
|||
if @@moneropedia.empty?
|
||||
|
||||
# grab all .md files in the Moneropedia folder, ignore index.md
|
||||
moneropedia_path = File.join(@config["source"], "/knowledge-base/moneropedia/*.md")
|
||||
moneropedia_path = File.join(@config["source"], "/resources/moneropedia/*.md")
|
||||
files = Dir.glob(moneropedia_path).reject{|f| f =~ Regexp.new('index.md', Regexp::EXTENDED | Regexp::IGNORECASE) }
|
||||
|
||||
# step through all the files
|
||||
|
|
@ -57,13 +57,13 @@ module Jekyll
|
|||
if content.include? '@moneropedia'
|
||||
# Moneropedia index, replace with a list of entries
|
||||
cur_letter = 'A'
|
||||
replace = "<div class='col-lg-4'>\n<h4 class='text-center'>A</h4>\n"
|
||||
replace = "<div class='col-md-4 col-sm-6 col-xs-12 moneropedia'>\n<h4 class='text-center'>A</h4>\n"
|
||||
@@moneropedia_ordered.sort.map do |entry, link|
|
||||
if cur_letter != entry[0]
|
||||
replace += "</div>\n<div class='col-lg-4'>\n<h4 class='text-center'>" + entry[0] + "</h4>\n"
|
||||
replace += "</div>\n<div class='col-md-4 col-sm-6 col-xs-12 moneropedia'>\n<h4 class='text-center'>" + entry[0] + "</h4>\n"
|
||||
cur_letter = entry[0]
|
||||
end
|
||||
replace += "<a href='/knowledge-base/moneropedia/" + link + "'>" + entry + "</a><br>\n"
|
||||
replace += "<a href='/resources/moneropedia/" + link + ".html'>" + entry + "</a><br>\n"
|
||||
end
|
||||
replace += "</div>"
|
||||
content = content.gsub(/(\@moneropedia)/i, replace)
|
||||
|
|
@ -72,7 +72,7 @@ module Jekyll
|
|||
# replace instances of @term with tooltips of the summary
|
||||
@@moneropedia.each do |entry|
|
||||
entry[:terms].each do |term|
|
||||
content = content.gsub(/(\@#{term})\b/i, '<a class="moneropedia" href="/knowledge-base/moneropedia/' + entry[:file] + '" data-toggle="tooltip" data-placement="top" data-original-title="' + entry[:summary] + '">' + term.gsub('-',' ') + '</a>')
|
||||
content = content.gsub(/(\@#{term})\b/i, '<a data-tooltip="' + entry[:summary] + '" href="/resources/moneropedia/' + entry[:file] + '.html" >' + term.gsub('-',' ') + '</a>')
|
||||
end
|
||||
end
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*June 5th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok so I think let's move on to Kovri - anonimal, the floor is yours
|
||||
**\<meeting-bot> [anonimal]** Thanks fluffypony, I need about 30-60 seconds.
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony / Aerbax
|
|||
|
||||
*June 5th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-06-05)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** everyone ready to start? smooth / tewinget / dEBRUYNE / ArticMine / luigi1111w / luigi1112 / luigi1114 / NoodleDoodle / gingeropolous etc.
|
||||
**\<ArticMine>** yes
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*June 19th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok I guess we move on to Kovri - anonimal, the floor is yours
|
||||
**\<meeting-bot> [anominal]** From agenda https://github.com/monero-project/kovri/issues/192
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*June 19th, 2016*
|
||||
|
||||
# Overview (by Aerbax)
|
||||
### Overview (by Aerbax)
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-06-19)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok
|
||||
**\<fluffypony>** hello and welcome
|
||||
|
|
|
|||
|
|
@ -15,6 +15,6 @@ In this week's episode we discuss the rationale behind rolling hard forks and th
|
|||
|
||||
Until next week!
|
||||
|
||||
# Podcast Transcription
|
||||
### Podcast Transcription
|
||||
|
||||
*Pending*
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*July 3th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok I guess we move on to Kovri - anonimal, the floor is yours
|
||||
**\* fluffypony:** ding dings
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*July 3th, 2016*
|
||||
|
||||
# Overview (by Aerbax)
|
||||
### Overview (by Aerbax)
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-07-03)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** time for meeting to start
|
||||
**\<hyc>** ok
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*July 31th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** ping fluffypony we missed you in #monero-dev
|
||||
**\<anonimal>** I'll proceed with the meeting as planned but the bulk of the agenda is picking on your assigned issues.
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*July 31th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
-
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** time for meeting to start
|
||||
**\<i2p-relay> {-anonimal}** Are we not having a meeting?
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*August 14th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-08-14)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<wallet42>** moneromoo: rewview guidelines?
|
||||
**\<moneromooo>** wallet42: well, whatever you feel comfortable with. Do you have anything in mind ?
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*August 28th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** anonimal: all yours
|
||||
**\<tewinget>** in the meantime, for those not interested (or relevant to) the kovri meeting, anyone wanna help me test the zmq wallet<->daemon interactions?
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*August 28th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-08-28)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<hyc>** ding ding ding
|
||||
**\<fluffypony>** hello meeting-bot!
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*September 11th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** anonimal: all yours :)
|
||||
**\<meeting-bot> [anonimal]** 1. Community input for kovri logo https://99designs.com/logo-design/contests/create-beautiful-logo-kovri-privacy-enhancing-open-source-652257/entries
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*September 11th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** Hi all
|
||||
**\<fluffypony>** I'm on my phone
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*September 19th, 2016*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is the next major release of Monero. It adds an initial release of RingCT, which is already live on testnet. The RingCT whitepaper [can be found here](https://lab.getmonero.org/pubs/MRL-0005.pdf). Note that the v4 hard fork has been moved to the beginning of January, 2017, although the v5 hard fork remains set at September, 2017. This is to enable early availability of RingCT transactions on the Monero network, although they will not be enforced as the only possible transaction type until the v5 hard fork.
|
||||
|
||||
|
|
@ -40,13 +40,13 @@ Some highlights of this release are:
|
|||
- more bug fixes than you can shake a stick at
|
||||
- temporary patch (via a predefined user-agent) for the CSRF attack against monero-wallet-cli's RPC API, as disclosed by Henry Hoggard
|
||||
|
||||
## Updating: Blockchain Conversion
|
||||
### Updating: Blockchain Conversion
|
||||
|
||||
Due to the space savings and performance gains it is again highly recommended that you delete the contents of your Monero working directory and sync from scratch. This directory can be found in ~/.bitmonero on Linux and OS X, and on Windows in \Users\username\AppData\Roaming\bitmonero or \ProgramData\bitmonero.
|
||||
|
||||
Alternatively, you can use ```blockchain_export``` from your previous install to export your current blockchain, then delete the lmdb folder in your working directory, and finally use ```monero-blockchain-import``` from 0.10.0 to reimport it.
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 28 people who worked, largely unpaid and altruistically, to put out 725 commits containing 15 332 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ This release was the direct result of 28 people who worked, largely unpaid and a
|
|||
- dEBRUYNE
|
||||
- blashyrkh
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/monero.win.x64.v0-10-0-0.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/monero.win.x86.v0-10-0-0.zip)
|
||||
|
|
@ -88,7 +88,7 @@ This release was the direct result of 28 people who worked, largely unpaid and a
|
|||
- [Linux, 32-bit](https://downloads.getmonero.org/monero.linux.x86.v0-10-0-0.tar.bz2)
|
||||
- [Linux, ARMv7](https://downloads.getmonero.org/monero.linux.arm7.v0-10-0-0.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ tags: [core, rpc]
|
|||
author: Riccardo Spagni (fluffypony)
|
||||
---
|
||||
|
||||
## Statement
|
||||
### Statement
|
||||
|
||||
There seem to be some misconceptions and even outrightly false statements being made around the unauthenticated RPC "bug" that was ["discovered" by MWR Labs](https://labs.mwrinfosecurity.com/advisories/csrf-vulnerability-allows-for-remote-compromise-of-monero-wallets/), and we'd like to make certain facts of the matter clear.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 2nd, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-and-kovri-dev-meeting-note-highlights-2016-10-02)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** anonimal: all yours :)
|
||||
**\<meeting-bot> [anonimal]** 1. Greetings
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 2nd, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-and-kovri-dev-meeting-note-highlights-2016-10-02)
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** Hi all
|
||||
**\<fluffypony>** starting meeting bot
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 16th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<i2p-relay> {-anonimal}** 17:00!
|
||||
**\<moneromooo>** Go go go!
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 16th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-dev-meeting-note-highlights-2016-10-16).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<moneromooo>** So, fluffypony asked if I could talk. I have no relay bot, so #kovri-dev will have to be here to listen.
|
||||
**\<moneromooo>** He suggested I talk about guidelines for submitting patches. So we'll see if everyone mostly agrees.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 30th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** alright anonimal, the floor is yours
|
||||
**\<meeting-bot> [anonimal]** Proposed meeting items:
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*October 30th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monerokovri-dev-meeting-note-highlights-2016-10-30).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<Jaquee>** it takes quite long time to open/close wallets with this mempool size. Could the mempool be saved in wallet cache?
|
||||
**\<Jaquee>** or is that a bad idea?
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*November 13th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<i2p-relay> {-anonimal}** Proposed meeting items:
|
||||
**\<i2p-relay> {-anonimal}** 1. Greetings
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*November 13th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-dev-meeting-note-highlights-2016-11-13).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<@ArticMine>** Hi
|
||||
**\<+moneromooo>** Oh hi
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*November 27th, 2016*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<i2p-relay> {-fluffypony}** ok anonimal
|
||||
**\<i2p-relay> {-fluffypony}** Kovri meeting start, all yours
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*November 27th, 2016*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-dev-meeting-note-highlights-and-transcript-2016-11-27).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<tewinget>** ugh, I wanted to stay up for the dev meeting, but I just...can't.
|
||||
**\<tewinget>** I'll put an update here in a minute or two though, someone can paste it for me perhaps.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*December 14th, 2016*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is a necessary point release of Monero v0.10 "*Wolfram Warptangent*", and is highly recommended as it includes consensus-changing fixes to the RingCT implementation and various other bug fixes.
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ Some highlights of this release are:
|
|||
- overhauled the sweep_unmixable implementation
|
||||
- fixed FreeBSD builds
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 29 people who worked, largely unpaid and altruistically, to put out 481 commits containing 10 517 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ This release was the direct result of 29 people who worked, largely unpaid and a
|
|||
- Jacob Brydolf
|
||||
- Ilya Kitaev
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/monero.win.x64.v0-10-1-0.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/monero.win.x86.v0-10-1-0.zip)
|
||||
|
|
@ -75,7 +75,7 @@ This release was the direct result of 29 people who worked, largely unpaid and a
|
|||
- [Linux, ARMv7](https://downloads.getmonero.org/monero.linux.arm7.v0-10-1-0.tar.bz2)
|
||||
- [FreeBSD, 64-bit](https://downloads.getmonero.org/monero.freebsd.x64.v0-10-1-0.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,19 +8,19 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*December 22nd, 2016*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
The first beta of the Monero Core GUI has been released. Note that, at this time, we have not completed support for 32-bit Windows, FreeBSD, and ARMv7 Linux devices. They are all being worked on, and we hope to complete support for them by the time of the first release.
|
||||
|
||||
Download links are at the bottom of this post, and please take note of the known issues and caveats listed below.
|
||||
|
||||
## Known Issues
|
||||
### Known Issues
|
||||
|
||||
- Due to several important updates, 0.10.1 wallet binaries will not work with with wallets created by the GUI. Please use the binaries included in the package instead. Note: you can definitely use the 0.10.1 daemon:)
|
||||
- If you have been testing earlier builds you may have to delete your configs. There is [a guide describing how to do this on this StackExchange post](http://monero.stackexchange.com/questions/2866/where-are-the-monero-core-configuration-parameters-stored/2870#2870).
|
||||
- Older computers may have an issue with the QT renderer, and will either crash or display a white / black window. You can change the rendering mode [as described on this StackExchange post](http://monero.stackexchange.com/questions/2928/how-to-change-the-monero-core-rendering-mode-for-older-computers/2929#2929).
|
||||
|
||||
## FAQ
|
||||
### FAQ
|
||||
|
||||
- *Can I use a remote node?* This is certainly possible. In the wizard, change the daemon address from `localhost:18081` to the address of the remote node. For instance, if you want to use the remote node of moneroworld.com, change `localhost:18081` to `node.moneroworld.com:18081`. For more open node options, please check out the [MoneroWorld open node directory.](https://moneroworld.com/#nodes) Alternatively, you can specify a daemon address on the `Settings` page.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ Download links are at the bottom of this post, and please take note of the known
|
|||
|
||||
- *Can I open a wallet I created with the CLI?* Yes, this is possible with the wallet picker in the wizard. Use the "I want to open a wallet from file" option and select your .keys file to open the wallet created with the CLI. Alternatively, if you already have a wallet opened and want to switch to your CLI wallet, go to the `Settings` page and choose `Close wallet`. This will bring you back to the wizard, where you can choose your CLI wallet. Note that your cache may be incompatible and you may incur an error. If this happens, see the FAQ questions above.
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 32 people who worked, largely unpaid and altruistically, to put out 736 commits containing 321 056 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -72,14 +72,14 @@ This release was the direct result of 32 people who worked, largely unpaid and a
|
|||
- Clement
|
||||
- Christoph Schnerch
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/gui/monero.gui.win.x64.beta.zip)
|
||||
- [macOS, 64-bit](https://downloads.getmonero.org/gui/monero.gui.mac.x64.beta.tar.bz2)
|
||||
- [Linux, 64-bit](https://downloads.getmonero.org/gui/monero.gui.linux.x64.beta.tar.bz2)
|
||||
- [Linux, 32-bit](https://downloads.getmonero.org/gui/monero.gui.linux.x86.beta.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*February 5th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** 1. Greetings
|
||||
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*February 5th, 2017*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-dev-meeting-note-highlights-and-transcript-2017-02-05).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok
|
||||
**\<fluffypony>** welcome to the 77th annual hunger games
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*February 19th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** 1. Greetings
|
||||
**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*February 23rd, 2017*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is a necessary point release of Monero v0.10 "*Wolfram Warptangent*", and is a **strongly, strongly** recommended update as it includes massive efficiency improvements to the RingCT validation code and various other necessary bug fixes.
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Some highlights of this release are:
|
|||
- added support for DragonFlyBSD
|
||||
- fixed armv8 build issues
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 24 people who worked, largely unpaid and altruistically, to put out 527 commits containing 21 090 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- iDunk5400
|
||||
- NanoAkron
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/cli/monero-win-x64-v0.10.2.0.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/cli/monero-win-x86-v0.10.2.0.zip)
|
||||
- [macOS, 64-bit](https://downloads.getmonero.org/cli/monero-mac-x64-v0.10.2.0.tar.bz2)
|
||||
|
|
@ -80,7 +80,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- [FreeBSD, 64-bit](https://downloads.getmonero.org/cli/monero-freebsd-x64-v0.10.2.0.tar.bz2)
|
||||
- [DragonFlyBSD, 64-bit](https://downloads.getmonero.org/cli/monero-dragonflybsd-x64-v0.10.2.0.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*February 24th, 2017*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is a necessary point release of Monero v0.10 "_Wolfram Warptangent_", and is a **strongly, strongly** recommended update as it includes massive efficiency improvements to the RingCT validation code and various other necessary bug fixes.
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ Some highlights of this release are:
|
|||
- added support for DragonFlyBSD
|
||||
- fixed armv8 build issues
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 24 people who worked, largely unpaid and altruistically, to put out 527 commits containing 21 090 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- iDunk5400
|
||||
- NanoAkron
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/cli/monero-win-x64-v0.10.2.1.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/cli/monero-win-x86-v0.10.2.1.zip)
|
||||
|
|
@ -82,7 +82,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- [FreeBSD, 64-bit](https://downloads.getmonero.org/cli/monero-freebsd-x64-v0.10.2.1.tar.bz2)
|
||||
- [DragonFlyBSD, 64-bit](https://downloads.getmonero.org/cli/monero-dragonflybsd-x64-v0.10.2.1.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*March 12th, 2017*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-03-12).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** 1. Greetings
|
||||
**\<fluffypony>** ok cool
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*March 25th, 2017*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is a necessary point release of Monero v0.10 "_Wolfram Warptangent_", and it is a mandatory update due to the April 15th hard fork, which in turn has been necessitated by the unexpectedly high adoption rate of RingCT transactions necessitating a modification of the dynamic block size limiter algorithm.
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ Since it has only been 30 days since the last release, this is something of a "l
|
|||
- massive API changes to support new features in the GUI
|
||||
- as always, loads of bug fixes and performance improvements
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 24 people who worked, largely unpaid and altruistically, to put out 189 commits containing 5 705 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -60,7 +60,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- Miguel Herranz
|
||||
- kenshi84
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/cli/monero-win-x64-v0.10.3.0.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/cli/monero-win-x86-v0.10.3.0.zip)
|
||||
- [macOS, 64-bit](https://downloads.getmonero.org/cli/monero-mac-x64-v0.10.3.0.tar.bz2)
|
||||
|
|
@ -71,7 +71,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- [FreeBSD, 64-bit](https://downloads.getmonero.org/cli/monero-freebsd-x64-v0.10.3.0.tar.bz2)
|
||||
- [DragonFlyBSD, 64-bit](https://downloads.getmonero.org/cli/monero-dragonflybsd-x64-v0.10.3.0.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*March 26th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** 1. Greetings
|
||||
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*March 26th, 2017*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-03-26).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
|
||||
**\<fluffypony>** ok so since the last meeting I guess the main thing is we tagged and released 0.10.3
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*March 27th, 2017*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
This is a necessary point release of Monero v0.10 "_Wolfram Warptangent_", and it is a mandatory update due to the April 15th hard fork, which in turn has been necessitated by the unexpectedly high adoption rate of RingCT transactions necessitating a modification of the dynamic block size limiter algorithm.
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ Since it has only been 30 days since the last release, this is something of a "l
|
|||
- massive API changes to support new features in the GUI
|
||||
- as always, loads of bug fixes and performance improvements
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 24 people who worked, largely unpaid and altruistically, to put out 190 commits containing 5 706 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- Miguel Herranz
|
||||
- kenshi84
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/cli/monero-win-x64-v0.10.3.1.zip)
|
||||
- [Windows, 32-bit](https://downloads.getmonero.org/cli/monero-win-x86-v0.10.3.1.zip)
|
||||
- [macOS, 64-bit](https://downloads.getmonero.org/cli/monero-mac-x64-v0.10.3.1.tar.bz2)
|
||||
|
|
@ -73,7 +73,7 @@ This release was the direct result of 24 people who worked, largely unpaid and a
|
|||
- [FreeBSD, 64-bit](https://downloads.getmonero.org/cli/monero-freebsd-x64-v0.10.3.1.tar.bz2)
|
||||
- [DragonFlyBSD, 64-bit](https://downloads.getmonero.org/cli/monero-dragonflybsd-x64-v0.10.3.1.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Riccardo Spagni (fluffypony)
|
|||
|
||||
*March 29th, 2017*
|
||||
|
||||
## Overview
|
||||
### Overview
|
||||
|
||||
The second beta of the Monero GUI has been released. Due to our focus on completing the features required for the initial release we have not, as yet, completed support for 32-bit Windows, FreeBSD, DragonflyBSD, ARMv7 Linux, and ARMv8 Linux devices. Whilst these are being worked on, it may not be feasible to support some environments (like 32-bit Windows) due to performance degradation.
|
||||
|
||||
|
|
@ -16,13 +16,13 @@ Download links are at the bottom of this post, and please take note of the known
|
|||
|
||||
To upgrade, just replace your existing GUI with this newer release. Beta 1 wallets will continue to work in beta 2, without any changes required from your side.
|
||||
|
||||
## Known Issues
|
||||
### Known Issues
|
||||
|
||||
- If the GUI doesn't start on Windows, or starts with a blank screen, then try launch it using the ```start-low-graphics-mode.bat``` batch file.
|
||||
- The unsigned transaction format, used by cold wallets, may cause issues when moving between platforms (eg. from Linux to Windows) for signing.
|
||||
- Cold transaction signing does not work with split transactions (sends that are split over multiple transactions).
|
||||
|
||||
## Contributors for this Release
|
||||
### Contributors for this Release
|
||||
|
||||
This release was the direct result of 50 people who worked, largely unpaid and altruistically, to put out 1202 commits containing 345 646 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
|
||||
|
||||
|
|
@ -77,13 +77,13 @@ This release was the direct result of 50 people who worked, largely unpaid and a
|
|||
- Roy Jacobs
|
||||
- pigeons
|
||||
|
||||
## Official Download Links
|
||||
### Official Download Links
|
||||
- [Windows, 64-bit](https://downloads.getmonero.org/gui/monero-gui-win-x64-v0.10.3.1.zip)
|
||||
- [macOS, 64-bit](https://downloads.getmonero.org/gui/monero-gui-mac-x64-v0.10.3.1.tar.bz2)
|
||||
- [Linux, 64-bit](https://downloads.getmonero.org/gui/monero-gui-linux-x64-v0.10.3.1.tar.bz2)
|
||||
- [Linux, 32-bit](https://downloads.getmonero.org/gui/monero-gui-linux-x86-v0.10.3.1.tar.bz2)
|
||||
|
||||
## Download Hashes
|
||||
### Download Hashes
|
||||
|
||||
If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: Monero Core Team
|
|||
|
||||
*April 1st, 2017*
|
||||
|
||||
## For Immediate Release
|
||||
### For Immediate Release
|
||||
|
||||
The Monero Core Team is very proud to announce that we have broken ground on the construction of the Monero Celebrity Center in Los Angeles, USA!
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*April 9th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** 1. Greetings
|
||||
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*April 9th, 2017*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-04-09).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** ok
|
||||
**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -6,13 +6,13 @@ tags: [core, crypto, research]
|
|||
author: Justin Ehrenhofer (SamsungGalaxyPlayer) and the Monero community
|
||||
---
|
||||
|
||||
# Preface
|
||||
### Preface
|
||||
|
||||
This release attempts to contain the opinions of the Monero community. It is possible that not every viewpoint is expressed, but this paper includes the best response to the author's ability that encapsulates all these opinions. The author opens all discussion to how certain viewpoints are represented, and the purpose of this response is solely for easier documentation by interested parties. He has done the best to include sources wherever possible, and to be as accurate as possible. For any concerns with this publication, please express them to the [author's Reddit account](https://www.reddit.com/u/SamsungGalaxyPlayer) or on [the Monero subreddit](https://www.reddit.com/r/Monero/). This version has been updated for clarity, though the core content has remained unchanged.
|
||||
|
||||
The Monero contributors and community at large always appreciate any research done on Monero's technology. They heavily encourage constructive criticism of all cryptocurrencies.
|
||||
|
||||
# Notable Findings
|
||||
### Notable Findings
|
||||
|
||||
The Monero contributors appreciate the effort that has gone into this mentioned publication and research methods. It helps quantify several realizations that had already been known to the Monero community at large for a long time (ref: [MRL-0001](https://lab.getmonero.org/pubs/MRL-0001.pdf) and [MRL-0004](https://lab.getmonero.org/pubs/MRL-0004.pdf)), including the following:
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ The Monero contributors appreciate the effort that has gone into this mentioned
|
|||
|
||||
4. The phenomenon where the most recent input is the real one is a concern when using Monero. There is no way to prove that this input is indeed the correct one, and with recent transactions, the assertion is nearly impossible to prove and is accurate less than half of the time. As the report states, there is about a 40% chance that the most recent input in a default transaction is the real one. Ideally, this number should be closer to 20% (1 in 5). Note that this does not mean that there is a 40% chance that this transaction is traceable (see appendix). Increasing the transaction ringsize has only a marginal improvement.
|
||||
|
||||
# Recommendations and Responses
|
||||
### Recommendations and Responses
|
||||
|
||||
The following are the recommendations listed in the paper and responses to them:
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ The following are the recommendations listed in the paper and responses to them:
|
|||
|
||||
3. Monero users should be warned that their prior transactions are likely vulnerable to linking analysis. We mostly disagree with this recommendation. The vulnerabilities of 0-mixin transactions were well-documented and continuously shared with the Monero community while they were still allowed. The first research paper shared in the Monero community ([MRL-0001](https://lab.getmonero.org/pubs/MRL-0001.pdf)) was published in September 2014. Furthermore, most of Monero's community growth occurred after these 0-mixin transactions were prohibited across the network.
|
||||
|
||||
# Concerns
|
||||
### Concerns
|
||||
|
||||
The Monero community would like to list several concerns with this research paper. They are documented below:
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ The Monero community would like to list several concerns with this research pape
|
|||
|
||||
4. Andrew Miller was named in the paper as a consultant to the Zerocoin Electric Coin Company and a board member of the ZCash Foundation. ZCash is a cryptocurrency with a focus on privacy that uses different technology than Monero. However, [he downplayed his involvement in an interview](https://cointelegraph.com/news/monero-transactions-history-can-be-revealed-and-exposed-research) about this paper. We feel author involvement in cryptocurrencies with similar interests should be fully disclosed, though he did refer people to the first page of the report. Nevertheless, we feel that Miller's disclosure of his contribution to a competing project was unsatisfactory, given the severity of the allegations in the paper.
|
||||
|
||||
# Other Information
|
||||
### Other Information
|
||||
|
||||
1. The timing of the publication. This paper was released approximately an hour before the hardfork. While it is impossible to know the reason for the specific timing without an admission, we speculate that this was timed to draw as much attention to the paper as possible. More people would have been tuning in to see how the hardfork was proceeding than typical community participation traffic. Andrew Miller has responded to this criticism in a Reddit comment, saying "the timing of our release with the imminent hard fork was totally unintentional and a coincidence. No one on the team noticed there was a hardfork planned, and we'd definitely have delayed till afterward if we had."
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ The Monero community would like to list several concerns with this research pape
|
|||
|
||||
5. This paper has not yet been published, is not finalized, and is not yet peer reviewed. Thus, there will most certainly be changes to this research paper before publication. We suggest that all claims and research be taken as preliminary and not concrete, since not enough people have evaluated their methods of research yet.
|
||||
|
||||
# Conclusion
|
||||
### Conclusion
|
||||
|
||||
We appreciate the effort that went into this research paper, but we suggest the following changes for later improvements:
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ We appreciate the effort that went into this research paper, but we suggest the
|
|||
|
||||
6. Consider cooperating with Riccardo Spagni to permanently include the research portion of this paper in our Monero Research Lab documents.
|
||||
|
||||
# Appendix
|
||||
### Appendix
|
||||
|
||||
**Figure 5 from the report showing the fraction of deducible inputs. Notice the large drops following block height 1,000,000, when 0-mixin transactions were prohibited. Furthermore, these inputs likely do not include all those used in a single transaction. For instance, for a mixin 9 transaction, 5 may be deduced. This means that the inputs would be reported here as deducible, even if the transaction is not traceable.**
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*April 23th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** 1. Greetings
|
||||
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*May 7th, 2017*
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<anonimal>** 1. Greetings
|
||||
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ author: dEBRUYNE / fluffypony
|
|||
|
||||
*May 7th, 2017*
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
An overview [can be found on MoneroBase](https://monerobase.com/wiki/DevMeeting_2017-05-07).
|
||||
|
||||
# Logs
|
||||
### Logs
|
||||
|
||||
**\<fluffypony>** 1. Greetings
|
||||
**\<fluffypony>** 2. Brief review of what's been completed since the previous meeting
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ tags: [core, crypto, research]
|
|||
author: luigi1111 and Riccardo "fluffypony" Spagni
|
||||
---
|
||||
|
||||
# Overview
|
||||
### Overview
|
||||
|
||||
In Monero we've discovered and patched a critical bug that affects all CryptoNote-based cryptocurrencies, and allows for the creation of an unlimited number of coins in a way that is undetectable to an observer unless they know about the fatal flaw and can search for it.
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ Once we were certain that the network had updated, we notified all active and af
|
|||
|
||||
***We strongly caution against anyone using, trading, exchanging, or running services involving the following currencies affected by this issue: Bytecoin, DashCoin, DigitalNote***
|
||||
|
||||
# Timeline
|
||||
### Timeline
|
||||
|
||||
2017-02-19: A member of the Monero Research Lab discovers the exploit, triggered by a detailed discussion of the [XEdDSA signature schemes](https://whispersystems.org/docs/specifications/xeddsa/) on the [Curves mailing list](https://moderncrypto.org/mail-archive/curves/2017/000846.html)
|
||||
2017-02-20: The Monero blockchain is scanned to see if this had ever been exploited; thankfully it had not and the blockchain is intact.
|
||||
|
|
@ -30,11 +30,11 @@ Once we were certain that the network had updated, we notified all active and af
|
|||
2017-04-17: All CryptoNote coins are contacted, and told that they have until mid-May to patch their coins, before there will be a public disclosure of the issue.
|
||||
2017-04-17: As noted by [Riccardo "fluffypony" Spagni on Twitter](https://twitter.com/fluffyponyza/status/854029169667309569), the hash of the message sent to the various CryptoNote currencies is committed to the Monero blockchain.
|
||||
|
||||
# Problem
|
||||
### Problem
|
||||
|
||||
The so-called "key image" as used in CryptoNote coins utilising elliptic curve ed25519 can be modified in a special way, allowing double-spends. This effectively allows someone to create an infinite amount of coins in a way that is impossible to detect without knowing about the exploit and explicitly writing code to check for it.
|
||||
|
||||
# Mitigation
|
||||
### Mitigation
|
||||
|
||||
Several options exist for mitigation. The simplest, least invasive is noted below.
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
Before 
(image error) Size: 5.9 KiB |
Binary file not shown.
|
Before 
(image error) Size: 7.8 KiB |
Binary file not shown.
|
Before 
(image error) Size: 1.9 KiB |
Binary file not shown.
|
Before 
(image error) Size: 2.3 KiB |
Binary file not shown.
|
Before 
(image error) Size: 3 KiB |
Binary file not shown.
|
Before 
(image error) Size: 4.1 KiB |
Binary file not shown.
|
Before 
(image error) Size: 4.6 KiB |
Binary file not shown.
|
Before 
(image error) Size: 4.9 KiB |
Binary file not shown.
|
Before 
(image error) Size: 6.1 KiB |
Binary file not shown.
|
Before 
(image error) Size: 6.4 KiB |
Binary file not shown.
|
Before 
(image error) Size: 7.6 KiB |
Binary file not shown.
|
Before 
(image error) Size: 2.6 KiB |
Binary file not shown.
|
Before 
(image error) Size: 2.8 KiB |
Binary file not shown.
|
Before 
(image error) Size: 3.2 KiB |
Binary file not shown.
|
Before 
(image error) Size: 3.2 KiB |
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue