<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/cryptonote_basic/cryptonote_basic.h, branch main</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=main</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2022-04-18T07:49:53Z</updated>
<entry>
<title>Add view tags to outputs to reduce wallet scanning time</title>
<updated>2022-04-18T07:49:53Z</updated>
<author>
<name>j-berman</name>
<email>justinberman@protonmail.com</email>
</author>
<published>2021-11-15T13:23:53Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=ea87b30f8907ee11252433811e7a7d0c46758cca'/>
<id>urn:sha1:ea87b30f8907ee11252433811e7a7d0c46758cca</id>
<content type='text'>
Implements view tags as proposed by @UkoeHB in MRL issue
https://github.com/monero-project/research-lab/issues/73

At tx construction, the sender adds a 1-byte view tag to each
output. The view tag is derived from the sender-receiver
shared secret. When scanning for outputs, the receiver can
check the view tag for a match, in order to reduce scanning
time. When the view tag does not match, the wallet avoids the
more expensive EC operations when deriving the output public
key using the shared secret.
</content>
</entry>
<entry>
<title>Copyright: Update to 2022</title>
<updated>2022-03-04T05:59:20Z</updated>
<author>
<name>mj-xmr</name>
<email>mjxmr@protonmail.com</email>
</author>
<published>2022-03-01T11:16:17Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=da9aa1f7f802552b9de459f331a2f39c84898009'/>
<id>urn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009</id>
<content type='text'>
</content>
</entry>
<entry>
<title>RPC and ZeroMQ APIs to support p2pool</title>
<updated>2021-09-11T13:15:07Z</updated>
<author>
<name>SChernykh</name>
<email>sergey.v.chernykh@gmail.com</email>
</author>
<published>2021-08-26T08:20:20Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=dfee15eee18a97be5a8fb9822527f98ebd1b33e9'/>
<id>urn:sha1:dfee15eee18a97be5a8fb9822527f98ebd1b33e9</id>
<content type='text'>
Adds the following:

- "get_miner_data" to RPC API
- "json-miner-data" to ZeroMQ subscriber contexts

Both provide the necessary data to create a custom block template. They are used by p2pool.

Data provided:

- major fork version
- current height
- previous block id
- RandomX seed hash
- network difficulty
- median block weight
- coins mined by the network so far
- mineable mempool transactions
</content>
</entry>
<entry>
<title>Improve cryptonote (block and tx) binary read performance</title>
<updated>2021-01-23T06:23:39Z</updated>
<author>
<name>Lee Clagett</name>
<email>code@leeclagett.com</email>
</author>
<published>2021-01-24T07:42:57Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=08e4497c6e3b3f434c0bb255c3942648f153fe66'/>
<id>urn:sha1:08e4497c6e3b3f434c0bb255c3942648f153fe66</id>
<content type='text'>
</content>
</entry>
<entry>
<title>replace most boost serialization with existing monero serialization</title>
<updated>2020-08-17T16:23:58Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2020-06-24T23:26:58Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=7175dcb1078abbdaa130a8c5f5fd2b93fa7b3086'/>
<id>urn:sha1:7175dcb1078abbdaa130a8c5f5fd2b93fa7b3086</id>
<content type='text'>
This reduces the attack surface for data that can come from
malicious sources (exported output and key images, multisig
transactions...) since the monero serialization is already
exposed to the outside, and the boost lib we were using had
a few known crashers.

For interoperability, a new load-deprecated-formats wallet
setting is added (off by default). This allows loading boost
format data if there is no alternative. It will likely go
at some point, along with the ability to load those.

Notably, the peer lists file still uses the boost serialization
code, as the data it stores is define in epee, while the new
serialization code is in monero, and migrating it was fairly
hairy. Since this file is local and not obtained from anyone
else, the marginal risk is minimal, but it could be migrated
later if needed.

Some tests and tools also do, this will stay as is for now.
</content>
</entry>
<entry>
<title>Update copyright year to 2020</title>
<updated>2020-05-07T02:36:54Z</updated>
<author>
<name>SomaticFanatic</name>
<email>afdlkajdlfkj@aldkfjf.com</email>
</author>
<published>2020-05-07T02:36:54Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=5ef0607da6042df51a57703bd223c5c8024741f6'/>
<id>urn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6</id>
<content type='text'>
Update copyright year to 2020
</content>
</entry>
<entry>
<title>monerod can now sync from pruned blocks</title>
<updated>2019-09-27T00:10:37Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-09-16T12:18:34Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=8330e772f1ed680a54833d25c4d17d09a99ab8d6'/>
<id>urn:sha1:8330e772f1ed680a54833d25c4d17d09a99ab8d6</id>
<content type='text'>
If the peer (whether pruned or not itself) supports sending pruned blocks
to syncing nodes, the pruned version will be sent along with the hash
of the pruned data and the block weight. The original tx hashes can be
reconstructed from the pruned txes and theur prunable data hash. Those
hashes and the block weights are hashes and checked against the set of
precompiled hashes, ensuring the data we received is the original data.
It is currently not possible to use this system when not using the set
of precompiled hashes, since block weights can not otherwise be checked
for validity.

This is off by default for now, and is enabled by --sync-pruned-blocks
</content>
</entry>
<entry>
<title>serialization: check stream good flag at the end</title>
<updated>2019-06-14T08:47:23Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-04-16T18:48:40Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1387549e905fc206426d3099b069bd28df0aad71'/>
<id>urn:sha1:1387549e905fc206426d3099b069bd28df0aad71</id>
<content type='text'>
just in case
</content>
</entry>
<entry>
<title>cryptonote: rework block blob size sanity check</title>
<updated>2019-04-05T09:35:19Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2019-04-04T00:15:57Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=089c7637a64652c8bcf6c437065237c23266d4a9'/>
<id>urn:sha1:089c7637a64652c8bcf6c437065237c23266d4a9</id>
<content type='text'>
Use the actual block weight limit, assuming that weight is always
greater or equal to size
</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>
</feed>
