monzero-core.git/src/rpc/core_rpc_server.cpp, branch v0.18.4.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.22025-07-11T16:27:12Zrpc: return error correctly on bad key image string2025-07-11T16:27:12Zjeffro256jeffro256@tutanota.com2025-07-11T15:39:00Zurn:sha1:45152f9ef0a762d9f6b61fc2602b97a2085f2dc3
Because of the missing `return` statement, the status is set to "OK" later on in the method when it shouldn't be.
Thank you to ADA Logics and the MAGIC Monero Fund for reporting this!
Merge pull request #97402025-03-10T16:20:00Ztobtohttob@featherwallet.org2025-03-10T16:20:00Zurn:sha1:3da68db9789697d30dc309df2f1da5d348bc4ce2
008ba966d blockchain sync: reduce disk writes from 2 to 1 per tx (jeffro256)
blockchain sync: reduce disk writes from 2 to 1 per tx2025-03-10T06:32:08Zjeffro256jeffro256@tutanota.com2024-01-17T23:17:16Zurn:sha1:008ba966da88f073f226b299533faca905ceabf8Set response limits on http server connections2025-02-14T05:21:05ZLee *!* Clagettcode@leeclagett.com2025-01-21T14:56:52Zurn:sha1:13ff355cf6081776fd7379080c17246e35c1236dvalidate ip parameter in set_bans rpc call2025-01-14T20:16:28Zeversinc33svrath@web.de2024-12-28T22:31:46Zurn:sha1:936046f71bd82ae9b14f8dedc39550b64a0f6727Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]2024-04-29T05:08:53Zjeffro256jeffro256@tutanota.com2024-02-04T03:59:58Zurn:sha1:dd47d03cf2b5b3dc59cd99aca247d1025679f83a
Related to https://github.com/monero-project/research-lab/issues/78
Added a relay rule that enforces the `unlock_time` field is equal to 0 for non-coinbase transactions.
UIs changed:
* Removed `locked_transfer` and `locked_sweep_all` commands from `monero-wallet-cli`
APIs changed:
* Removed `unlock_time` parameters from `wallet2` transfer methods
* Wallet RPC transfer endpoints send error codes when requested unlock time is not 0
* Removed `unlock_time` parameters from `construct_tx*` cryptonote core functions
@tobtoht: undo rebase changes tx.dsts -> tx_dsts
Merge pull request #88912023-08-17T15:18:12Zluigi1111luigi1111w@gmail.com2023-08-17T15:18:12Zurn:sha1:894adef29588f20951a675fc25139ebb777493eb
842478c core_rpc_server: return ID of submitted block (jeffro256)
Enforce restricted # pool txs served via RPC + optimize chunked reqs [release-v0.18]2023-07-09T06:38:18Zj-bermanjustinberman@protonmail.com2022-12-14T00:08:56Zurn:sha1:f137a35984985232a3aae50cd4c7b47634866594
- `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when
returning pool txs via a restricted RPC daemon.
- A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs
in the `added_pool_txs` field, and returns any remaining pool hashes
in the `remaining_added_pool_txids` field. The client then requests
the remaining txs via `/gettransactions` in chunks.
- `/gettransactions` no longer does expensive no-ops for ALL pool txs
if the client requests a subset of pool txs. Instead it searches for
the txs the client explicitly requests.
- Reset `m_pool_info_query_time` when a user:
(1) rescans the chain (so the wallet re-requests the whole pool)
(2) changes the daemon their wallets points to (a new daemon would
have a different view of the pool)
- `/getblocks.bin` respects the `req.prune` field when returning
pool txs.
- Pool extension fields in response to `/getblocks.bin` are optional
with default 0'd values.
wallet2, RPC: Optimize RPC calls for periodic refresh from 3 down to 1 call [release-v0.18]2023-07-09T06:30:53Zrbrunner7rbrunner@dreamshare.ch2021-11-21T16:40:50Zurn:sha1:23f782b21113035b57e4560d6a9b522ac1f03ccacore_rpc_server: return ID of submitted block2023-06-30T20:32:49Zjeffro256jeffro256@tutanota.com2023-06-03T03:00:11Zurn:sha1:842478c5a922aa67dc0cf51f71128c42587021ec