 Show Posts
|
|
Pages: [1]
|
Thanks! I've compiled it using the same options mentioned in the post and now I'm getting 7Kh/s in the rpi3 with arch64. I will try with another power supply and I will repeat the test (now I'm using an Anker multi port power supply that gives 2.1A per port as max). What power supply are you using with the rpi? Another test that I will run is use pi64 instead of arch64. |
|
|
|
Hi, One question, I'm trying to mine XMG using two rpi3. Using raspbian I'm getting about 4Kh/s (4 * 1.1) for each rpi3. Some time ago I've read this thread https://www.raspberrypi.org/forums/viewtopic.php?t=196909 where an user says that he's getting about 10Kh/s for a single rpi3 using a 64bit SO. So I've installed arch64 in one of my rpi3 and after compiling the m-cpuminer-v2 I'm getting the same 4Kh/s than the 32bit SO. Are these the expected results? Could it be related with the way I've compiled it? Could it be related with the pool I'm using (minerclaim)? Any idea about what's happening? Thanks in advance for your help. |
|
|
|
Hi guys,
Another newbie question here.
I started mining on Minerclaim yesterday with my little rpi3 cluster, I can see now some balance as "unconfirmed" in my account, how long it usually takes to confirm the balance inside a pool? I don't know exactly how this "confirmation process works", that's the origin of my questions.
Thanks in advance.
A MagiCoin Block need 520 confirmations to be counted as mature , doesnt matter if generated by pool workers or solo miners so in short , you must wait untill another 520 blocks were solved Thanks for the quick reply! much appreciated! It's clear now  |
|
|
|
|
Hi guys,
Another newbie question here.
I started mining on Minerclaim yesterday with my little rpi3 cluster, I can see now some balance as "unconfirmed" in my account, how long it usually takes to confirm the balance inside a pool? I don't know exactly how this "confirmation process works", that's the origin of my questions.
Thanks in advance.
|
|
|
|
mining seems to be doing nothing. no magi coming in at all at minerclaim. minerclaim issue or global?
Another pools seems to be assigning correctly the blocks, so I think that's a minerclaim issue. |
|
|
|
Can someone please provide a link to download the block chain that works. I inadvertently deleted it.  You can download it from this link : http://m-core.org/bin/block-chain/Just enter it, select the resource desired and uncompress it |
|
|
|
I've compiled the new wallet version and all is running fine. Thanks Magi team for all your work today! |
|
|
|
My wallet (running over a rpi3) is getting connection timeout issues during this morning, I don't know why because the internet connection is running fine. May it be related with the issue? I'm using the 1.4.5.1 version.
If I want to update it to 1.4.5.2 (or another release) the procedure will be (just asking for confirmation).
Stop current wallet
Backup the wallet.dat file.
Compile new wallet
Run new wallet with the same wallet.dat file.
Is this correct? should I remove the blockchain folder and sync it again? or could I use the same data? It takes hours to full sync.
Minning on Minerclaim is activated? It's not clear based on the messages shown on their site but I'm still getting connection refused messages both using xmg.minerclaim.net or eu1.minerclaim.net urls (don't know exactly which is the right one).
Best thing is hold your actions & wait for new info Thanks! will do it. Thanks for all your work here guys! |
|
|
|
|
My wallet (running over a rpi3) is getting connection timeout issues during this morning, I don't know why because the internet connection is running fine. May it be related with the issue? I'm using the 1.4.5.1 version.
If I want to update it to 1.4.5.2 (or another release) the procedure will be (just asking for confirmation).
Stop current wallet
Backup the wallet.dat file.
Compile new wallet
Run new wallet with the same wallet.dat file.
Is this correct? should I remove the blockchain folder and sync it again? or could I use the same data? It takes hours to full sync.
Minning on Minerclaim is activated? It's not clear based on the messages shown on their site but I'm still getting connection refused messages both using xmg.minerclaim.net or eu1.minerclaim.net urls (don't know exactly which is the right one).
|
|
|
|
Has anyone been successful in recompiling m-wallet 1.4.5.1 on RPI3 (stretch)?
I download the source from github, recompiled successfully, but then I keep on getting segfaults when I launch the wallet. Even if I use the -debug flag, it doesn't dump any debug.log into the .magi folder. Any pointers?
According to this guide https://steemit.com/cryptocurrency/@gridcat/how-to-install-coin-magi-wallet-on-your-raspberry-pi there is an incompatibility between the libssl-dev package version that is being shipped with strech and the version required by the wallet. So in this post you will find instructions about how to install the jessie version of this lib in strech and make the wallet working as expected. Hope it helps. |
|
|
|
|
I've updated my wallet to the latest version and I'm still getting "connection refused" from Minerclaim, is it correct?
|
|
|
|
I used to be able to mint this coin but my coins are no longer staking although the blockchain is fully synced. Does anyone know what is the issue?
A new wallet will be available on New Years Eve (~22:00 CET) following the hard fork Ok, so we should replace the old one with the new one, right? Thanks! |
|
|
|
|
Hi guys, another newbie here.
I've just installing configuring my magi wallet and my magi miner when I saw the notice about the hardfork.
Yesterday I've configured the wallet using latest version available on Github (compiling it from sources) and I've attached the current blockchain available.
I understand that at this moment I can't run my wallet locally with the current blockchain data, isn't it? When the hard fork occurs what modifications will be required over the wallet?
Sorry in advance if my questions are very basic, these are my first steps using cryptocurrencies and I haven't found information about it.
Thanks in advance.
|
|
|
|
|
