Monero Core consists of several applications, including bitmonerod (the daemon used if running a @full-node, as it maintains the connection to the Monero network) and simplewallet (a Monero @account manager application), as well as several other helper applications.
{% t downloads.core_text_1 %}
If you are using Monero Core for the first time you can simply download an appropriate release, and run bitmonerod to get synced up to the network.
{% t downloads.core_text_2 %}
Note: the SHA hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).
{% t downloads.core_text_3 %}
<divclass="row">
...
...
@@ -31,7 +31,7 @@ Note: the SHA hashes are listed by the downloads for convenience, but a GPG-sign
@@ -71,8 +71,8 @@ Note: the SHA hashes are listed by the downloads for convenience, but a GPG-sign
{% endfor %}
</div>
### Other Downloads
### {% t downloads.other_downloads %}
- If you'd prefer to use a blockchain bootstrap, instead of syncing up from scratch, you can [use this link for the most current bootstrap](https:////downloads.getmonero.org/blockchain.raw).
- For Monero Research Lab publications please visit the [Monero Research Lab section](/research-lab) of this site.
- High resolution and vector copies of the Monero logo [can be downloaded at this link](https://downloads.getmonero.org/resources/branding.zip).
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.
{% t gs.accepting.basics_text_1 %}
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".
{% t gs.accepting.basics_text_2 %}
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: <spanclass="long-term">666c75666679706f6e7920697320746865206265737420706f6e792065766572</span>
{% t gs.accepting.basics_text_3 %}
### Checking for a Payment in simplewallet
### {% t gs.accepting.checking_sw %}
If you want to check for a payment using simplewallet you can use the "payments" command followed by the payment ID or payment IDs you want to check. For example:
If you need to check for payments programmatically, then details follow the next section.
{% t gs.accepting.checking_sw_text_2 %}
### Receiving a Payment Step-by-Step
### {% t gs.accepting.receiving %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Generate a random 64 character hexadecimal string for the payment
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Communicate the payment ID and Monero address to the individual who is making payment
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Check for the payment using the "payments" command in simplewallet
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.receiving_text_1 %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.receiving_text_2 %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.receiving_text_3 %}
### Checking for a Payment Programatically
### {% t gs.accepting.checking_prog %}
In order to check for a payment programatically you can use the get_payments or get_bulk_payments JSON RPC API calls.
{% t gs.accepting.checking_prog_text_1 %}
*get_payments*: this requires a payment_id parameter with a single payment ID.
{% t gs.accepting.checking_prog_text_2 %}
*get_bulk_payments*: this is the preferred method, and requires two parameters, payment_ids - a JSON array of payment IDs - and an optional min_block_height - the block height to scan from.
@@ -61,13 +61,13 @@ An example of returned data is as follows:
}
}
It is important to note that the amounts returned are in base Monero units and not in the display units normally used in end-user applications. Also, since a transaction will typically have multiple outputs that add up to the total required for the payment, the amounts should be grouped by the tx_hash or the payment_id and added together. Additionally, as multiple outputs can have the same amount, it is imperative not to try and filter out the returned data from a single get_bulk_payments call.
{% t gs.accepting.checking_prog_text_5 %}
Before scanning for payments it is useful to check against the daemon RPC API (the get_info RPC call) to see if additional blocks have been received. Typically you would want to then scan only from that received block on by specifying it as the min_block_height to get_bulk_payments.
{% t gs.accepting.checking_prog_text_6 %}
### Programatically Scanning for Payments
### {% t gs.accepting.scanning %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Get the current block height from the daemon, only proceed if it has increased since our last scan
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Call the get_bulk_payments RPC API call with our last scanned height and the list of all payment IDs in our system
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Store the current block height as our last scanned height
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>Remove duplicates based on transaction hashes we have already received and processed
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.scanning_text_1 %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.scanning_text_2 %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.scanning_text_3 %}
<iclass="fa fa-level-up fa-rotate-90 fa-lg instruction-list"></i>{% t gs.accepting.scanning_text_4 %}
Ongoing development of the Monero Project is solely supported by donations and sponsors. At this time the project is vastly underfunded, and thus donations are greatly appreciated.
{% t gs.donate.how_funded_text %}
### Donating and Sponsoring
### {% t gs.donate.donate_sponsor %}
If you would like to make a donation you can do so by using any of the methods below:
{% t gs.donate.donate_sponsor_text_1 %}
{:.text-center style="letter-spacing: 30px;"}
- Donating in Monero: you can send XMR donations to [donate.getmonero.org](monero:46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8aHYjA3jk3o1Bv16em?recipient_name=Monero%20Development&tx_description=Donation%20to%20Monero%20Core%20Team), or directly to our Monero donation address -
- Donating in Bitcoin: you can also send BTC donations to [donate.getmonero.org](bitcoin:1FhnVJi2V1k4MqXm2nHoEbY5LV7FPai7bb?label=Monero%20Development&message=Donation%20to%20Monero%20Core%20Team), or directly to our Bitcoin address: [1FhnVJi2V1k4MqXm2nHoEbY5LV7FPai7bb](bitcoin:1FhnVJi2V1k4MqXm2nHoEbY5LV7FPai7bb?label=Monero%20Development&message=Donation%20to%20Monero%20Core%20Team)
- To donate via credit card, wire transfer, or PayPal, please email the core team at [{{ site.email }}](mailto:{{ site.email }})
{% t gs.donate.donate_sponsor_text_2 %}
{% t gs.donate.donate_sponsor_text_3 %}
{% t gs.donate.donate_sponsor_text_4 %}
{% t gs.donate.donate_sponsor_text_5 %}
Sponsorships are also greatly appreciated, including those companies that give us free or reduced-cost access to development hardware, hosting and other services, and software licenses. If you would like to sponsor Monero development in some form, please email the core team at [{{ site.email }}](mailto:{{ site.email }})
### {% t gs.donate.current_sponsors %}
### Current Sponsors
Current sponsors include several mining pools that contribute a portion of their fees to development. You can find a list of these pools in [the first post on the Monero thread on Bitcointalk](https://bitcointalk.org/index.php?topic=583449.0). Over and above that, our sponsors include:
All donators to Monero development are also eligible to be listed in the [Community Hall of Fame](/getting-started/donate/hall-of-fame). Members of the most prestigious level of donators, 8th Dan, are also listed below. The full [Hallof Fame can be viewed at this link](/getting-started/donate/hall-of-fame).
