<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/cryptonote_core/cryptonote_tx_utils.cpp, branch v0.15.0.1</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.1</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.1'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2019-10-31T01:25:07Z</updated>
<entry>
<title>cryptonote: untangle dependency from miner to blockchain</title>
<updated>2019-10-31T01:25:07Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-10-31T01:05:58Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=d31024c2e1634d32cfbf750ce5713b52a1e67707'/>
<id>urn:sha1:d31024c2e1634d32cfbf750ce5713b52a1e67707</id>
<content type='text'>
It causes link errors at least on mac
</content>
</entry>
<entry>
<title>Add hmac over encrypted value during transaction</title>
<updated>2019-10-03T14:01:34Z</updated>
<author>
<name>cslashm</name>
<email>cslashm@gmail.com</email>
</author>
<published>2019-09-25T12:31:14Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=d25acd7a1dbd05b24fba13fc4910886948ab90ba'/>
<id>urn:sha1:d25acd7a1dbd05b24fba13fc4910886948ab90ba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>RandomX integration</title>
<updated>2019-09-25T20:29:42Z</updated>
<author>
<name>Howard Chu</name>
<email>hyc@symas.com</email>
</author>
<published>2019-04-23T19:32:27Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=81c2ad6d5b17cf280a4a55fd6159e8dde423f5a8'/>
<id>urn:sha1:81c2ad6d5b17cf280a4a55fd6159e8dde423f5a8</id>
<content type='text'>
Support RandomX PoW algorithm
</content>
</entry>
<entry>
<title>Changed the use of boost:value_initialized for C++ list initializer</title>
<updated>2019-09-02T12:16:29Z</updated>
<author>
<name>Jesus Ramirez</name>
<email>jesus.rami.serra@gmail.com</email>
</author>
<published>2019-06-26T14:39:41Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=2cd4fd8972620737956aeeb4262209f8a446e3ee'/>
<id>urn:sha1:2cd4fd8972620737956aeeb4262209f8a446e3ee</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Replace std::random_shuffle with std::shuffle</title>
<updated>2019-08-15T14:33:15Z</updated>
<author>
<name>Tom Smeding</name>
<email>tom.smeding@gmail.com</email>
</author>
<published>2019-07-03T09:05:01Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=7b9a420787c71624ff0e9c6bcfe1e72c74feb677'/>
<id>urn:sha1:7b9a420787c71624ff0e9c6bcfe1e72c74feb677</id>
<content type='text'>
According to [1], std::random_shuffle is deprecated in C++14 and removed
in C++17. Since std::shuffle is available since C++11 as a replacement
and monero already requires C++11, this is a good replacement.

A cryptographically secure random number generator is used in all cases
to prevent people from perhaps copying an insecure std::shuffle call
over to a place where a secure one would be warranted. A form of
defense-in-depth.

[1]: https://en.cppreference.com/w/cpp/algorithm/random_shuffle
</content>
</entry>
<entry>
<title>Update 2019 copyright</title>
<updated>2019-03-05T21:05:34Z</updated>
<author>
<name>binaryFate</name>
<email>binaryfate@users.noreply.github.com</email>
</author>
<published>2019-03-05T21:05:34Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1f2930ce0bec07e28958c059444151ad4968e1e6'/>
<id>urn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>New scheme key destination contrfol</title>
<updated>2019-02-08T16:02:44Z</updated>
<author>
<name>cslashm</name>
<email>cslashm@gmail.com</email>
</author>
<published>2018-12-11T09:20:21Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=460da140ec1e1b22e3ac1e371abd2368c3bda5f5'/>
<id>urn:sha1:460da140ec1e1b22e3ac1e371abd2368c3bda5f5</id>
<content type='text'>
Implies protocol version management.
</content>
</entry>
<entry>
<title>add a bulletproof version, new bulletproof type, and rct config</title>
<updated>2019-01-22T23:17:24Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-01-06T13:47:16Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=f931e16c6e45da6880c333cf1f355d7228c143d9'/>
<id>urn:sha1:f931e16c6e45da6880c333cf1f355d7228c143d9</id>
<content type='text'>
This makes it easier to modify the bulletproof format
</content>
</entry>
<entry>
<title>core: include a dummy encrypted payment id when no payment is used</title>
<updated>2019-01-18T16:58:50Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2018-12-23T14:32:40Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=c6d387184e05437d8f68a4227d739ad28568aa5e'/>
<id>urn:sha1:c6d387184e05437d8f68a4227d739ad28568aa5e</id>
<content type='text'>
For better transaction uniformity, even though this wastes space.
</content>
</entry>
<entry>
<title>crptonote_core: do not error out sending unparsable extra field</title>
<updated>2019-01-18T16:58:45Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2018-12-23T11:33:05Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=a9b1c04acfaa21e7b0adfea9216dffae002ac7e3'/>
<id>urn:sha1:a9b1c04acfaa21e7b0adfea9216dffae002ac7e3</id>
<content type='text'>
extra is arbitrary, and the user may well want to send custom data
</content>
</entry>
</feed>
