additional blog posts, minor tweaks, updated readme

parent ccb5a6e0
......@@ -10,10 +10,23 @@ IRC: [#monero-dev on Freenode](irc://chat.freenode.net/#monero-dev)
## About this Project
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, so contributors don't need to have any knowledge of HTML or anything else.
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.
## Pages, Formats, and Rules
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.
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:
- 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
- since all static content (CSS/JS/images) is hosted in a separate, non-public repository, changes can be suggested via Github issues and we will cross-apply them to that repo, crediting you in the commit message
- 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
## Deployment
Deploying this website requires Jekyll (2.5+) and the following ruby gems: builder, rubysl-rexml
Multiple language support will be added soon.
......
......@@ -37,3 +37,11 @@
- slug: crypto
name: Cryptography
- slug: platforms
name: Platform Support
- slug: core
name: Monero Core
- slug: accounts
name: Accounts (Wallets)
---
layout: post
title: Monero Missive for the Week of
summary:
tags: [monero missives, ]
author: Riccardo Spagni (fluffypony)
---
---
layout: post
title: Dev Diary for the Week of 2014-06-16
summary: New checkpoint, better mempool handling from BBR, Arch Linux support
tags: [dev diaries, usability, platforms, accounts, core]
author: Riccardo Spagni (fluffypony)
---
*June 18th, 2014*
Core: Checkpoint added at block 80 000
Core: We've incorporated two changes from BBR - proper tx_pool handling, and a fix for the high number of orphans pool miners were experiencing. tx_pool handling is incomplete, as it is implemented by the daemon but the wallet is not, as yet, mempool aware.
Core: Initial tx auto-split commit, ready for testing
Build: Made changes to CMakeLists to allow for the project to build on Arch
---
layout: post
title: Monero Missive for the Week of 2014-06-16
summary: Monero number 1 on the MintPal voting list, whitepaper annotations released and peer review started, initial transaction splitting test
tags: [monero missives, exchanges, research, usability, gui]
author: Riccardo Spagni (fluffypony)
---
*June 18th, 2014*
Hello, and welcome to our third Monero Missive.
**Major Updates**
1. We've been stalling this week's Missive on purpose, because we were hoping it would happen...and it happened! We got to number 1 on the MintPal voting list in a week - which is quite an achievement. There was quite a stack of paid-for votes (more than normal for a cryptocurrency on the MintPal voting list), which is surprising, but it definitely helped catapult us up front.
An [interesting graph on CryptVote](http://cryptvote.com) shows the meteoric climb (XMR is the blue line):  
![](http://i.imgur.com/GfQ67Tz.jpg){: .center-image }
2. We are immensely grateful for the work the CryptoNote developers have put into the protocol, but their whitepaper is unfortunately lacking in peer reviews. To that end, we have taken it upon ourselves to peer review the whitepaper, and to release the peer review as an annotated whitepaper.
The two primary peer reviewers are not part of the Monero core team, and are highly qualified academics in the fields of mathematics and cryptography. They are assisted by some of the Monero core team who have a similar computer science academic background. Due to the nature of the Monero project both of the primary peer reviewers have chosen to work under a pseudonym. In a later missive we'll introduce them more formally, but for the moment we wanted to release the current copy of the annotated whitepaper for everyone to take a look at. If you'd like to provide your input on the annotations, please feel free to email any comments to [email protected]
The latest annotated whitepaper can be downloaded here: http://monero.cc/downloads/whitepaper_annotated.pdf. Please bear in mind that it is only up to page 8 in the CryptoNote whitepaper at present, so the annotation does cut short there:)
3. We have completed initial work and testing on transaction auto-splitting (thanks to tewinget's tireless work). Now, if you have too many inputs for your transaction, simplewallet will automatically try to split your transfer up to as many as 30 transactions. It will prompt you first and let you know the total fees before just sending it, of course:
![](http://i.imgur.com/IyG3Uq0.jpg){: .center-image }
This feature requires more testing, and is NOT in the main code base yet. If you're able to build Monero, please grab it from fluffypony's repo here, and build and test: https://github.com/fluffypony/bitmonero - you won't need to build tests or change the daemon, it's just simplewallet's operation that has changed. Please do not try this with the RPC API yet, this needs the CLI at the moment.
4. We have had a lot of people asking about the progress of the GUI wallet. We'd like to reiterate that there are a great number of core and fundamental things that need to be worked on *before* we can get lots and lots of users flocking in. Some of the core necessities that we're working on at breakneck pace are: QoS to reduce the bandwidth demand on full nodes (as everyone will be running a full node at this stage anyway), segregation of wallet functions in order to create a far more robust system for exchanges and merchants to use, [Gitian-based builds](http://gitian.org) for everyone's safety and to ensure binaries are safe (safer, really), moving blockchain storage to an embedded database, fixing the now-infamous "ABSTRACT_SERVER_SEND_QUE_MAX_COUNT" (in big red letters!) error that is quite harmless but everyone freaks out about, and so on.
   These are issues at Monero's core that we're working on, and we need to have these in place and fixed before a GUI wallet is widely dispersed, otherwise there will be massive resource constraints placed on user's systems. We're not here to win a race against other cryptocurrencies. We're here to to continue to push out great features and stable and reliable code, in a way that will make sure Monero is around for decades and not just a flash-in-the-pan.
\ No newline at end of file
---
layout: post
title: Monero Missive for the Week of
summary:
tags: [monero missives, ]
author: Riccardo Spagni (fluffypony)
---
---
layout: post
title: Monero Missive for the Week of 2014-06-30
summary:
tags: [monero missives, ]
author: Riccardo Spagni (fluffypony)
---
*July 6th, 2014*
Hello, and welcome to our fifth Monero Missive!
**Major Updates**
1. fluffypony had a great time discussing Monero at the Bitcoin Supernode Conference in Estonia. Many thanks to rpietila for hosting him and all attendees.
2. Work on the academic peer review of the CryptoNote whitepaper is slowly starting to move away from an academic platform and on to the code itself, to determine whether the reference implementation correctly implements the whitepaper. Before that happens, though, a summary of the initial findings will be published. We are expecting this to be completed this coming week.
3. Transaction auto-splitting is now in the main codebase. To explain our methodology: the main github repo will always be "active development", and may contain code that will be reverted or is not fully tested. For those that are brave and want to test and contribute to development, it is the ideal starting point. However, on an ongoing basis we are going to create tagged releases, whereby when a group of new features have been fully tested, a new release can be tagged, and binaries can be put out (along with the code on the github tag, of course). Expect this change to start taking effect within the next 4 weeks.
4. We'd like to apologise for not finalise the GUI bounty - everyone has been a little scattered this week. We will resolve this in its entirety within the next 48 hours!
\ No newline at end of file
......@@ -56,7 +56,7 @@ index:
untraceable: Untraceable
private_text: "Monero uses a cryptographically sound system to allow you to send and receive funds without your @transactions being easily revealed on the @blockchain (the distributed ledger of transactions). This ensures that your purchases, receipts, and all transfers remain absolutely private by default."
untraceable_text: "By taking advantage of @ring-signatures, a special property of certain types of cryptography, Monero is able to ensure that transactions are not only untraceable, but have an optional measure of ambiguity that ensures that transactions cannot easily be tied back to an individual user or computer."
secure_text: "Using the power of a distributed peer-to-peer @consensus network, every transaction on the network is cryptographically secured. Individual @accounts have a 25 word @mnemonic-seed that is only displayed once, and can be written down to backup the @account. Account files are encrypted with a passphrase to ensure they are useless if stolen."
secure_text: "Using the power of a distributed peer-to-peer @consensus network every transaction is cryptographically secured. Individual @accounts have a 25 word @mnemonic-seed displayed when created, and can be written down to backup the @account. Account files are encrypted with a passphrase to ensure they are useless if stolen."
how_do_i_1: "How do I "
how_do_i_2: " ?"
get_started: get started
......
......@@ -11,11 +11,11 @@ attribution: "<!-- Icon is based on work by Icons8 (http://www.icons8.com) and i
### The Basics
Monero works a little differently to what you may have become accustomed to from other cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient address for each payment or user.
Monero works a little differently to what you may have become accustomed to from other @cryptocurrencies. In the case of a digital currency like Bitcoin and its many derivatives merchant payment systems will usually create a new recipient @address for each payment or user.
However, because Monero has stealth addresses there is no need to have separate recipient addresses for each payment or user, and a single wallet address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
However, because Monero has @stealth-addresses there is no need to have separate recipient addresses for each payment or user, and a single @account address can be published. Instead, when receiving payments a merchant will provide the person paying with a "payment ID".
A payment ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is: <span class="long-term">666c75666679706f6e7920697320746865206265737420706f6e792065766572</span>
A @payment-ID is a hexadecimal string that is 64 characters long, and is normally randomly created by the merchant. An example of a payment ID is: <span class="long-term">666c75666679706f6e7920697320746865206265737420706f6e792065766572</span>
### Checking for a Payment in simplewallet
......
......@@ -71,7 +71,7 @@ Title: Home
{% include download.php %}
</div>
<div class="col-lg-12 left-pad other-links">
{% t index.different_os %}<br><a href="/{{ site.lang }}/downloads">{% t index.all_downloads %}</a>
{% t index.different_os %}<br><a href="/downloads">{% t index.all_downloads %}</a>
</div>
</div>
</div>
\ No newline at end of file
......@@ -11,7 +11,7 @@ attribution: ""
### The Monero Project
The bulk of the content on this website is copyright The Monero Project. It is made available under the CC BY 3.0 license (the [Creative Commons Attribution 3.0 Unported license](http://creativecommons.org/licenses/by/3.0/)). This means that you can copy and redistribute the material in any medium or format, and remix, transform, and build upon the material for any purpose, even commercially. However, when doing so you must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests The Monero Project endorses you or your use.
The majority of the content on this website, including our Monero Missive podcast, is copyright The Monero Project. It is made available under the CC BY 3.0 license (the [Creative Commons Attribution 3.0 Unported license](http://creativecommons.org/licenses/by/3.0/)). This means that you can copy and redistribute the material in any medium or format, and remix, transform, and build upon the material for any purpose, even commercially. However, when doing so you must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests The Monero Project endorses you or your use.
### Icons and Other Attributed Items
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment