masari-project / masari Goto Github PK

Some endpoints returns duplicated content. It can be problematic on non wireless networks due to the cost of data.

Currently at least one endpoint has this problem. If more are found, i add them as comments and edit this post.

The endpoint /gettransactions (with {"decode_as_json":true,"txs_hashes":["24d2023bc3031baabf48409bb356eda31fd008441599f92875c03ca93da4cdc9"]} ) as parameter) returns this kind of content:
{ "status": "OK", "txs": [{ "as_hex": "HEX_VALUE", "as_json": "JSON_VALUE", "block_height": 255000, "block_timestamp": 1535516465, "double_spend_seen": false, "in_pool": false, "output_indices": [1149145,1149146], "tx_hash": "24d2023bc3031baabf48409bb356eda31fd008441599f92875c03ca93da4cdc9" }], "txs_as_hex": ["HEX_VALUE"], "txs_as_json": ["JSON_VALUE"], "untrusted": false }
Json values and hex values are present 2 times.
Also, when we explicitly ask for json, it could means we dont want the json value.

We could add a parameter to not receive the hex value to decrease the global data size.

Current endpoints like get_block under the rpc api /json_rpc are not sending back values like in the binaries endpoints like get_blocks_by_height.bin

It would be really good to get values like the output index in the transactions. It will allow a direct connection of the webwallet to the daemon.

blockchain-import fails somewhere after block 363000. See error below.

2019-07-08 17:48:30.782 7f0dc2940bc0 FATAL bcutil src/blockchain_utilities/blockchain_import.cpp:546 exception while reading from file, height=363605: Error in deserialization of chunk

This could be a failure on blockchain-export as well (or both).

File being tested is https://chain.masari.rocks/blockchain.raw but feel free to use your own export for testing. guard-against-pwnage was also set to zero.

363605 in @gnock's block explorer -> https://explorer.masari.rocks/block.html?height=363605

I'm left to assume this is an uncle and is why the export/import is failing.

Hi,

i got this erreur when i try to build docker image :

Dockerfile.zip

make[2]: Leaving directory '/usr/local/libsodium' make[1]: Leaving directory '/usr/local/libsodium' Removing intermediate container 8872400226c8 ---> cfdf3620f3e1 Step 24/35 : WORKDIR /src Removing intermediate container 69c80cd29275 ---> 6343fdcb21f1 Step 25/35 : COPY . . ---> 6f30e22756df Step 26/35 : ARG NPROC ---> Running in c6f3cf1a4886 Removing intermediate container c6f3cf1a4886 ---> 4b52ff37e1b9 Step 27/35 : RUN rm -rf build && if [ -z "$NPROC" ];then make -j$(nproc) release-static;else make -j$NPROC release-static;fi ---> Running in 99f1d3c9a9ad make: *** No rule to make target 'release-static'. Stop. The command '/bin/sh -c rm -rf build && if [ -z "$NPROC" ];then make -j$(nproc) release-static;else make -j$NPROC release-static;fi' returned a non-zero code: 2

How to generate GENESIS_TX and GENESIS_NONCE?

demo:
std::string const GENESIS_TX = "013c01ff0001ffffffffffff0302df5d56da0c7d643ddd1ce61901c7bdc5fb1738bfe39fbe69c28a3a7032729c0f2101168d0c4ca86fb55a4cf6a36d31431be1c53a3bd7411bb24e8832410289fa6f3b";
uint32_t const GENESIS_NONCE = 10002;

Thank you for any help！！

According to the IETF, a json string cannot contains binary values.

curl -X POST http://127.0.0.1:48081/get_transaction_pool -d '{}' -H 'Content-Type: application/json'
returns something like
{ "spent_key_images": [], "status": "OK", "transactions": [{ "blob_size": 14594, "do_not_relay": false, "double_spend_seen": false, "fee": 12774300000, "id_hash": "16e7427fb322eccaf6e9d3a32165ea17c87195a00fa052eed1324261ce156c07", "kept_by_block": false, "last_failed_height": 0, "last_failed_id_hash": "0000000000000000000000000000000000000000000000000000000000000000", "last_relayed_time": 1536520613, "max_used_block_height": 263363, "max_used_block_id_hash": "2b6dacf863929c19eedb1e22f239f164d412ff8a7399c3013033ae97a5ce9eeb", "receive_time": 1536520613, "relayed": true, "tx_blob": "DATA", "tx_json": "JSON_VALUE" }], "untrusted": false }

Sadly the tx_blob returns binary characters including the NULL character (0x0). It's impossible from a browser to parse this endpoint properly as the internal system do not store the content past the null character.

One possible alternative would be to add a parameter asking to not return the tx_blob. It will only also remove duplicate content.

The link

https://github.com/masari-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md

from your readme is a 404

docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "monerod": executable file not found in $PATH": unknown.

#41 should fix

Console version of the wallet does not accept the option of payment priority,
example:

transfer unimportant address 1.00

Error: payment id has invalid format, expected 16 or 64 character hex string: 1.00

The same command, but without indicating the priority, it works.

Tests to do for mainnet:

• Orphaned uncle transaction outs don't get included (void) in the transaction db and aren't spendable - add tests to ensure that outs are void and aren't spendable somehow
• Current re-org tests need assertions on expected behaviours (i.e. weight is as expected)

Tests already done for testnet:

• uncles mined properly and reorg well in all different cases
• a parent can't be an uncle
• an uncle must be at the same height as the parent
• an uncle must be the same version as parent
• an uncle must have a timestamp within range of the parent (T / 2)
• an uncle must have common ancestry (uncleparent == grandparent or uncleparent's parent == grandparent's parent)
• a nephew must mine the correct out tx to uncle
• a nephew must mine the corret out tx amount to uncle
• a nephew cannot overflow amounts in miner tx

Currently the endpoint takes a lit of "txs_hashes" as parameter.
Another way could be give a list of block height to retrieve all txs inside those blocks : it allow to remove 1 unnecessary call in some situations.

Due to "recent" securities in browsers, an https website cannot make ajax calls to an http website.
A RPC api is exposed as an http endpoint. Thus not callable from almost all website and incompatible with our need for the website/mobile wallet.

One alternative would be to implement the JSONP standart on some endpoint (new ones ?).

All request would be simulated by including a script tag in the page for each request
`

`

The content would be something like
mymethod(JSON_CONTENT)
The JSON_CONTENT is the regular content of the endpoint. "mymethod" is a function implemented in the rest of the application which would receive the content of the request.

Those request are made with a GET call so POST call are not possible anymore. All parameters would need to be converted into ?args=values parameters for this to work.

We will have to be careful with URL maxlength being 2048 characters on most browsers if we want the best compatibility.

If those endpoints also support classic GET calls (so no callback function) it would allow for nodes beeing behind a proxy (nginx, apache, ...) to prevent an "OPTION" request due to CORS security.

I've tried all the usual steps for rectification; this problem persists with both the GUI wallet and CLI wallet and cannot be avoided by a rescan or even new install of blockchain and recovery from seed.

Secret view key: 5b0ceb8d54a578e6a51c4e321d238e3002eae6641b97cf9660871583824ccf0e

Level 2 log from the GUI wallet is as follows:

2018-08-01 01:51:45.087 5420 INFO logging contrib/epee/src/mlog.cpp:185 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2018-08-01 01:51:46.660 5420 WARN net.http src/common/util.cpp:628 Failed to determine whether address '' is local, assuming not
2018-08-01 01:52:01.380 5420 INFO logging contrib/epee/src/mlog.cpp:185 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2018-08-01 01:52:02.521 8768 WARN wallet.wallet2 src/wallet/wallet2.cpp:3742 Loaded wallet keys file, with public address: 5pBkt3sMfCFMJkiYMrvJpa9TU1bhLw3Pj8FqQ6GqpQto6ySuVQ1AAA7hkVCZAJ6HftG57p6hfQAY69QvpjJqJSEDTFKWuTC
2018-08-01 01:52:47.983 5420 INFO logging contrib/epee/src/mlog.cpp:185 New log categories: *:DEBUG
2018-08-01 01:53:03.461 5420 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:3881 trimming to 169999, offset 169999
2018-08-01 01:53:03.566 5420 INFO WalletAPI src/wallet/api/wallet.cpp:367 ~WalletImpl
2018-08-01 01:53:03.567 5420 DEBUG WalletAPI src/wallet/api/wallet.cpp:1726 pauseRefresh: refresh paused...
2018-08-01 01:53:03.567 5420 INFO WalletAPI src/wallet/api/wallet.cpp:657 closing wallet...
2018-08-01 01:53:03.567 5420 INFO WalletAPI src/wallet/api/wallet.cpp:668 Calling wallet::stop...
2018-08-01 01:53:03.567 5420 INFO WalletAPI src/wallet/api/wallet.cpp:670 wallet::stop done
2018-08-01 01:53:03.569 5420 INFO WalletAPI src/wallet/api/wallet.cpp:380 ~WalletImpl finished
2018-08-01 01:53:13.101 5528 INFO logging contrib/epee/src/mlog.cpp:185 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2018-08-01 01:53:13.651 5528 WARN net.http src/common/util.cpp:628 Failed to determine whether address '' is local, assuming not
2018-08-01 01:53:16.966 5528 INFO logging contrib/epee/src/mlog.cpp:185 New log categories: *:DEBUG
2018-08-01 01:53:18.063 9764 INFO wallet.wallet2 src/wallet/wallet2.cpp:5457 ringdb path set to C:\ProgramData.shared-ringdb
2018-08-01 01:53:18.101 9764 WARN wallet.wallet2 src/wallet/wallet2.cpp:3742 Loaded wallet keys file, with public address: 5pBkt3sMfCFMJkiYMrvJpa9TU1bhLw3Pj8FqQ6GqpQto6ySuVQ1AAA7hkVCZAJ6HftG57p6hfQAY69QvpjJqJSEDTFKWuTC
2018-08-01 01:53:18.101 9764 INFO wallet.wallet2 src/wallet/wallet2.cpp:3761 Trying to decrypt cache data
2018-08-01 01:53:18.179 9764 DEBUG wallet.wallet2 src/wallet/api/address_book.cpp:98 Refreshing addressbook
2018-08-01 01:53:18.195 5528 DEBUG net.http src/common/util.cpp:642 Address 'localhost:38081' is local
2018-08-01 01:53:18.196 9764 DEBUG net.http src/common/util.cpp:642 Address 'localhost:38081' is local
2018-08-01 01:53:18.196 5528 DEBUG WalletAPI src/wallet/api/wallet.cpp:1706 startRefresh: refresh started/resumed...
2018-08-01 01:53:18.202 9976 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1666 Daemon is recent enough, asking for pruned blocks
2018-08-01 01:53:18.203 5528 DEBUG net.http src/common/util.cpp:642 Address 'localhost:38081' is local
2018-08-01 01:53:18.695 9976 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1770 Block is already in blockchain: 843f3fa6b1ee6cdd0f85240581db2423e1136060396e5633365834bd8b6d25da
2018-08-01 01:53:18.695 7420 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1666 Daemon is recent enough, asking for pruned blocks
2018-08-01 01:53:18.695 9976 ERROR cn src/cryptonote_basic/cryptonote_format_utils.cpp:233 key image helper precomp: given output pubkey doesn't match the derived one
2018-08-01 01:53:18.695 9976 ERROR wallet.wallet2 src/wallet/wallet2.cpp:1069 !r. THROW EXCEPTION: error::wallet_internal_error
2018-08-01 01:53:18.695 9976 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/TKhawaja/masari-wallet-gui/monero/src/wallet/wallet2.cpp:1069:N5tools5error21wallet_internal_errorE: Failed to generate key image
2018-08-01 01:53:19.052 9976 INFO wallet.wallet2 src/wallet/wallet2.cpp:2304 Another try pull_blocks (try_count=0)...
2018-08-01 01:53:19.052 9976 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1770 Block is already in blockchain: 843f3fa6b1ee6cdd0f85240581db2423e1136060396e5633365834bd8b6d25da
2018-08-01 01:53:19.052 7380 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1666 Daemon is recent enough, asking for pruned blocks
2018-08-01 01:53:19.052 9976 ERROR cn src/cryptonote_basic/cryptonote_format_utils.cpp:233 key image helper precomp: given output pubkey doesn't match the derived one
2018-08-01 01:53:19.052 9976 ERROR wallet.wallet2 src/wallet/wallet2.cpp:1069 !r. THROW EXCEPTION: error::wallet_internal_error
2018-08-01 01:53:19.052 9976 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/TKhawaja/masari-wallet-gui/monero/src/wallet/wallet2.cpp:1069:N5tools5error21wallet_internal_errorE: Failed to generate key image
2018-08-01 01:53:19.168 9976 INFO wallet.wallet2 src/wallet/wallet2.cpp:2304 Another try pull_blocks (try_count=1)...
2018-08-01 01:53:19.168 9976 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1770 Block is already in blockchain: 843f3fa6b1ee6cdd0f85240581db2423e1136060396e5633365834bd8b6d25da
2018-08-01 01:53:19.168 9012 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1666 Daemon is recent enough, asking for pruned blocks
2018-08-01 01:53:19.168 9976 ERROR cn src/cryptonote_basic/cryptonote_format_utils.cpp:233 key image helper precomp: given output pubkey doesn't match the derived one
2018-08-01 01:53:19.168 9976 ERROR wallet.wallet2 src/wallet/wallet2.cpp:1069 !r. THROW EXCEPTION: error::wallet_internal_error
2018-08-01 01:53:19.168 9976 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/TKhawaja/masari-wallet-gui/monero/src/wallet/wallet2.cpp:1069:N5tools5error21wallet_internal_errorE: Failed to generate key image
2018-08-01 01:53:19.284 9976 INFO wallet.wallet2 src/wallet/wallet2.cpp:2304 Another try pull_blocks (try_count=2)...
2018-08-01 01:53:19.284 9976 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1770 Block is already in blockchain: 843f3fa6b1ee6cdd0f85240581db2423e1136060396e5633365834bd8b6d25da
2018-08-01 01:53:19.284 7380 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:1666 Daemon is recent enough, asking for pruned blocks
2018-08-01 01:53:19.284 9976 ERROR cn src/cryptonote_basic/cryptonote_format_utils.cpp:233 key image helper precomp: given output pubkey doesn't match the derived one
2018-08-01 01:53:19.284 9976 ERROR wallet.wallet2 src/wallet/wallet2.cpp:1069 !r. THROW EXCEPTION: error::wallet_internal_error
2018-08-01 01:53:19.284 9976 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/TKhawaja/masari-wallet-gui/monero/src/wallet/wallet2.cpp:1069:N5tools5error21wallet_internal_errorE: Failed to generate key image
2018-08-01 01:53:19.390 9976 ERROR wallet.wallet2 src/wallet/wallet2.cpp:2309 pull_blocks failed, try_count=3
2018-08-01 01:53:19.403 5528 DEBUG cn src/cryptonote_basic/cryptonote_basic_impl.cpp:216 Invalid address format
2018-08-01 01:53:19.403 5528 DEBUG cn src/cryptonote_basic/cryptonote_basic_impl.cpp:216 Invalid address format

I have verified this patch for Monero worked for me in Masari:

monero-project/monero#3667

Everytime I run ./masarid then run the CLI, and type in the command:
Kamal-Server-1:~/Downloads/masari/masari-linux-x64-v0.2.3.0$ ./masari-wallet-rpc --wallet-file MyFileName --password MyPassword --rpc-bind-port 38082 --disable-rpc-login

I keep getting into this failed error

2018-05-23 23:27:16.459	    7f08a9d85bc0	INFO 	global	contrib/epee/include/net/http_server_impl_base.h:76	Binding on 127.0.0.1:38082
2018-05-23 23:27:16.464	    7f08a9d85bc0	FATAL	net	contrib/epee/include/net/abstract_tcp_server2.inl:741	Error starting server: bind: Address already in use
2018-05-23 23:27:16.464	    7f08a9d85bc0	ERROR	net.http	contrib/epee/include/net/http_server_impl_base.h:80	Failed to bind server
2018-05-23 23:27:16.464	    7f08a9d85bc0	ERROR	wallet.rpc	src/wallet/wallet_rpc_server.cpp:2973	Failed to initialize wallet RPC server

However, if I don't start ./masarid then it would say failed to connect to daemon. I am trying to start the ./masari-wallet rpc binding so that in the config file for my mining pool it would connect correctly to the masari RPC. However, I don't know why I keep getting to the failed to initialize wallet RPC server or how the address is already in use.

Any suggestion would be greatly appreciated.

Windows 10 OS
Almost every file i unzipped caused Windows Defender security block. Numerous attempts to exclude these files failed. I am experienced with many GUI wallets and this one is by far the worst experience I had so far.

We've developed a new algorithm that's the best of the best and allows integer math on the target.

zawy12/difficulty-algorithms#17

Hi
I just compiled and installed masarid on macOS. I want to hold the blockchain on a ZFS volume, but the initial synchronisation always fails with "Bus error: 10". I also tried the --db-salvage option but then the sync hangs.

When saving the blockchain to the main APFS volume (default location under my home dir) everything works fine. Is there a way to track and fix this as I really don't want to waste my scarce SSD space?

Healthcheck on Docker image are great to detect problems as soon as possible.
The process might not crash, but might not respond to external requests (both on the p2p port and rpc port).

Adding the HEALTHCHECK instruction in the Dockerfile would allow a better high availibility.

Possible options are to write a bash script runned each 10s trying to establish a connection on the p2p port, and another instruction making a call to get the blockchain height and expecting a 200 http status.

In the future, a fork detection would also be welcomed.

when trying to build, the following error is thrown and the build does not complete
CMakeError.log

Users of your software that enable DNSSEC will not be able to validate DNS after October the 11th 2018.

Your repository contains a dns_utils.cpp file without the new DNSSEC trust-anchors:

. IN DS 19036 8 2 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
It should also include:

. IN DS 20326 8 2 E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D

More information can be found at: https://www.icann.org/resources/pages/ksk-rollover

Please don’t hesitate to get in touch.

Warmly,

Roy Arends
ICANN

Hi.
Today morning on my previous wallet masari-mac-x64-v0.2.0.2 i did transaction but I didn't found this transaction in block explorer after 2 hours. I have found new version mac-wallet-cli and after update my wallet refresh my previous balance before transfer.

Now I doing new transfer and still unsucceable with error:
Error: internal error: Known ring does not include the spent output: 722396
What I can do for success transfer ?

fedora-release: Fedora release 32 (Thirty Two)
gcc version 10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)

make.log

no work no rebase very dry

Some Masari blocks that we mine do not have any including reward transactions in the wallet. I assume it is because they are uncle. However it is just assumption and I can not be sure from block dump. How I can be sure we actually mined this block?

For example for block a0d497c8b882541e98bfa281735aba46f0e0df1b310381b8677f1bf6e44440c that our pool found (I think since pool node reported this hash) I see that there are two miner_tx outputs (while block is "uncle_status: false"):

curl -X POST http://127.0.0.1:38081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"getblock","params":{"hash":"a0d497c8b882541e98bfa281735aba46f0e0df1b310381b8677f1bf6e44440c"}}' -H 'Content-Type: application/json'
{
  "id": "0",
  "jsonrpc": "2.0",
  "result": {
    "blob": "08089693d4e405b635305740fde980885826d23ed135162b9a8135069268a32a5b7b91cfa1d3e12903a01f01def91a01ffa2f91a02d3ebbc92ee7602f81945f4159fcf1b70cf052a13e2a89d4150ca0a1b4342a3beeab4c580cacee687f3afb8d7f9010267112414d304c2ec8209637f25f1226117a44bc064816148fb853793acbaae0755013cbbf443b0a97d40591262b30d79050a8bcc958398c1b72d70f6b3cf5f6f60fe01440000000d8b30040030cd3ca48bf2044b09311d8cc987f48ff413e7ee6f953d021100000000000000000000000000000000000001221cca1725211577cfb3a37a9b2c21176357406ac7cfeb5afcab332d2c35dd4238e1727db5a9f2eb8cd26f840e6698be53898ec9f23aefe75be3589622f89969",
    "block_header": {
      "block_size": 3338,
      "depth": 20514,
      "difficulty": 378607792,
      "hash": "a0d497c8b882541e98bfa281735aba46f0e0d8f1b310381b8677f1bf6e44440c",
      "height": 441506,
      "major_version": 8,
      "minor_version": 8,
      "nonce": 530580265,
      "num_txes": 1,
      "orphan_status": false,
      "prev_hash": "b635305740fde980885826d23ed135162b9a8135069268a32a5b7b91cfa1d3e1",
      "reward": 12663062736730,
      "timestamp": 1553271190,
      "uncle_status": false,
      "weight": 746940157
    },
    "json": "{\n  \"major_version\": 8, \n  \"minor_version\": 8, \n  \"timestamp\": 1553271190, \n  \"prev_id\": \"b635305740fde980885826d23ed135162b9a8135069268a32a5b7b91cfa1d3e1\", \n  \"nonce\": 530580265, \n  \"miner_tx\": {\n    \"version\": 1, \n    \"unlock_time\": 441566, \n    \"vin\": [ {\n        \"gen\": {\n          \"height\": 441506\n        }\n      }\n    ], \n    \"vout\": [ {\n        \"amount\": 4084015773139, \n        \"target\": {\n          \"key\": \"f81945f4159fcf1b70cf052a13e2a89d4150ca0a1b4342a3beeab4c580cacee6\"\n        }\n      }, {\n        \"amount\": 8579046963591, \n        \"target\": {\n          \"key\": \"67112414d304c2ec8209637f25f1226117a44bc064816148fb853793acbaae07\"\n        }\n      }\n    ], \n    \"extra\": [ 1, 60, 187, 244, 67, 176, 169, 125, 64, 89, 18, 98, 179, 13, 121, 5, 10, 139, 204, 149, 131, 152, 193, 183, 45, 112, 246, 179, 207, 95, 111, 96, 254, 1, 68, 0, 0, 0, 13, 139, 48, 4, 0, 48, 205, 60, 164, 139, 242, 4, 75, 9, 49, 29, 140, 201, 135, 244, 143, 244, 19, 231, 238, 111, 149, 61, 2, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0\n    ], \n    \"rct_signatures\": {\n      \"type\": 0\n    }\n  }, \n  \"tx_hashes\": [ \"221cca1725211577cfb3a37a9b2c21176357406ac7cfeb5afcab332d2c35dd42\"\n  ], \n  \"uncle\": \"38e1727db5a9f2eb8cd26f840e6698be53898ec9f23aefe75be3589622f89969\"\n}",
    "miner_tx_hash": "6894eed067a79d11b9292340a237193bb81c94e78639d04531e3c4116c8fed99",
    "status": "OK",
    "tx_hashes": ["221cca1725211577cfb3a37a9b2c21176357406ac7cfeb5afcab332d2c35dd42"],
    "untrusted": false
  }
}

However nothing comes into mining wallet at height 441506:

[wallet 5hnMXU]: show_transfers 441400 441600
  441455     in       2019-03-22       8.175943847866 0e6ca7de876f419ad1e45ab3a1ea752cc9430e426457f00858c34c9576cff72d 0000000000000000 0 -
  441458    out       2019-03-22       7.975943847866 1640aa217e9c664c8dd65768647196327c626d58bce2c7728f79af4b1a8a4ef1 0000000000000000 0.000980220000  0 -
  441503     in       2019-03-22       8.168054915248 9415c77148851bd4d7bccc424b3030a4eae624f0fa2d38ebd35c34ad114c47bc 0000000000000000 0 -
  441505     in       2019-03-22       8.168039335927 cb5c7ad53bdb78798906d624da81a1319f807d4926c4e5f264eca6697b8244c3 0000000000000000 0 -
  441507    out       2019-03-22       7.968054915248 765a3075483ded6bffc6a66949d8b02818ae229480bed4471116942a05d43ab4 0000000000000000 0.000980190000  0 -
  441509    out       2019-03-22       7.968039335927 e6efff112059694177dd1a5ae4bfd9143df7653190eae4faec92f83f48775a70 0000000000000000 0.000980190000  0 -
  441554     in       2019-03-22       8.167657651846 099fce45b24a27f07ca87c565912064a1f71839f693b9c2a558a1bc633139467 0000000000000000 0 -
  441556    out       2019-03-22       7.967657651846 d10376085b74b6a87ba087cdd3c257ead07b912a72e3d9d24897c036ef5e5172 0000000000000000 0.000980130000  0 -

Moreover I do not see any incoming transfers in wallet that are less than 8 MSR (that correspond to reduced uncle block rewards), but I have some extra money somehow in it.

Reported by mrknc:

2019-01-29 15:16:03.253    [P2P8]    INFO     blockchain    src/cryptonote_core/blockchain.cpp:4099    +++++ BLOCK SUCCESSFULLY ADDED
id:    <fca71e28277fd9d37931bc0a3e78532ec30facf804815d64c93e713ada6d51d7>
prev:    <296131bde4088aeab33325f6165ba9e70b45171953b2a17892f8695a9921f166>
PoW:    <7bee449d02aabfaac6e0bd4ae923b21b8e8f9d5d631132bf7d2d63f502000000>
height:    367235
version:    8
difficulty:    431727140
weight:    431727140
cumulative_difficulty:    488930506809681
cumulative_weight:    488932396422562
block reward:    8.769662194999(8.767557934999 + 0.002104260000 + 0.000000000000 + 0.000000000000)
coinbase_blob_size: 104, cumulative size: 3084, 23(0/17)ms
uncle:    <0000000000000000000000000000000000000000000000000000000000000000>
2019-01-29 15:16:03.993    [RPC1]    ERROR    cn    src/cryptonote_core/cryptonote_core.cpp:1166    Transaction not found in pool
2019-01-29 15:16:03.993    [RPC1]    INFO     stacktrace    src/common/stack_trace.cpp:124    Exception: std::runtime_error
2019-01-29 15:16:03.993    [RPC1]    INFO     stacktrace    src/common/stack_trace.cpp:125    Unwound call stack:

see, the block gets submitted 0.7 seconds after we have received the block from the network, some txs in it are no longer in the mempool, so it gets rejected outright
now if i were to mine empty block, it would still be accepted for alt chain
so it would have a chance to get mined later, so this creates an incentive to mine empty blocks```

In the console version of the wallet, the password does not work.
When you are prompted for a password, you can not type characters from the keyboard.
Also does not work the insertion of characters from the clipboard.
OS Win10x64

Hello. How did you generated new genesis block for monero fork?

Take mined uncle block difficulties into account when "weighting" chains with cumulative difficulty for deciding whether to reorg or not

The idea is to be able to retrieve chunks of blocks directly on the Rpc Json API like the endpoint get_blocks_by_height.bin binary one