Jump to content

Masari

  • entries
    26
  • comments
    0
  • views
    7567

Re-capping the month of June in Masari


Snider

537 views

Authored by Cryptochangements

A lot has been happening with Masari this past month: the Core Team was disbanded, several new releases have been published, the first two community meetings were held, and some generous donors funded me to work part time on masari during this period.

To elaborate on that last piece, I was funded $800 to work 10 hours/week on Masari from the dates June 9th to today, July 9th. Below I will recap how I spent this time by week.

Week 1: I fixed some bugs in the core wallet library that is used for the GUI wallet, mainly fixing the bug where new wallets were saved without a password, along with some minor performance upgrades. A new release, v0.3.1.0, was published for both the CLI and GUI.

Week 2: I started by porting over cross compiling capability via depends from Monero, this allows us to build releases for any operating system from Linux, vastly simplifying the release process. I then setup continuous integration via travis-ci. This will help us to avoid build bugs in the future and could possibly be used for a build pipeline. I also made modifications to the core RPC API so that gnock could roll out a webwallet update in which the in browser wallet connects directly to a remote node, rather than using a server backend as a middle man. The webwallet was at this point functional again, it’s just a little slow with the new changes. During this week I published a new v0.3.1.1 CLI release including these changes.

Week 3: I made some more changes to the RPC API to fix a mempool bug and try to improve the speed of the webwallet sync. It still has not been deployed as gnock needs to deploy it.

Week 4: I fixed the import/export blockchain tools to include uncle blocks so that they will now function properly after hard fork version 8. I also made some logging more verbose to help debug github usie #169. A bug from monero was also patched in which the wallet would potentially misinterpret RingCT keys. A release version v0.3.1.2 was published including these fixes.

1*8b-x0hey_wgnLPnP7Zb6Qw.png

A full log of development can be found on Github https://github.com/masari-project/masari

The webwallet is now down again as the SSL certificate has expired and gnock is the only person with access but an alternative is being put together.

I look forward to continuing work with the Masari community

stat?event=post.clientViewed&referrerSou

View the full article

0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      404.65 GH
    • Avg Hashrate
      170.23 MH
    • Total Miners
      2377
    • Miners Paid
      48447
    • Total Payments
      1416089
    • Total Hashes
      9.23 EX
    • Blocks Found
      2719399
  • Posts

    • Buenos dias, no se me abre pool monero,des de hace dias. Me comenta al abrir k puede haver cambiado de pagina.alguien sabe algo
    • How can I tell HiveOS how many cores or threads I want to use for mining? My Ryzen 3600 has been lowered to 55w. In order to avoid clogging GPUs, I only want to use 11 threads for mining, with 1 thread for system-specific purposes. fnf
    • ./xmrig --url pool.hashvault.pro:80 --user *** --pass x -a cn-heavy/xhv * ABOUT XMRig/6.17.0 gcc/9.3.0 * LIBS libuv/1.43.0 OpenSSL/1.1.1m hwloc/2.7.0 * HUGE PAGES supported * 1GB PAGES disabled * CPU AMD EPYC-Rome Processor (1) 64-bit AES VM L2:0.5 MB L3:16.0 MB 1C/1T NUMA:1 * MEMORY 0.6/1.9 GB (31%) DIMM 0: 2 GB RAM @ 0 MHz DIMM 0 * MOTHERBOARD Vultr - VHP * DONATE 1% * ASSEMBLY auto:ryzen * POOL #1 pool.hashvault.pro:80 algo cn-heavy/xhv * COMMANDS hashrate, pause, resume, results, connection [2022-05-22 12:49:13.205] net use pool pool.hashvault.pro:80 131.153.76.130 [2022-05-22 12:49:13.205] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (7 tx) [2022-05-22 12:49:13.205] cpu use argon2 implementation AVX2 [2022-05-22 12:49:13.207] msr cannot read MSR 0xc0011020 [2022-05-22 12:49:13.207] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW [2022-05-22 12:49:13.207] randomx init dataset algo rx/0 (1 threads) seed 6ac097ea635e9d1d... [2022-05-22 12:49:13.207] randomx not enough memory for RandomX dataset [2022-05-22 12:49:13.235] randomx failed to allocate RandomX dataset, switching to slow mode (27 ms) [2022-05-22 12:49:13.517] randomx dataset ready (282 ms) [2022-05-22 12:49:13.517] cpu use profile rx (1 thread) scratchpad 2048 KB [2022-05-22 12:49:13.519] cpu READY threads 1/1 (1) huge pages 100% 1/1 memory 2048 KB (1 ms) [2022-05-22 12:49:17.487] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (52 tx) [2022-05-22 12:49:20.337] signal Ctrl+C received, exiting [2022-05-22 12:49:20.345] cpu stopped (8 ms I run xmrig and set the algorithm `cn-heavy/xhv`, but it still response `rx/0`.How to solve this problem?
    • Yes, I like the content of this article.  LOL Beans
    • Yeah, it does, but apparently it's not so transparent. So if we > mention that we'd better indicate in the same paragraph that you > probably don't actually want to use it. How about the attached?  UNO Online
×
×
  • Create New...