Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 90. (Read 2375603 times)
Really Vitalik? You haven't fucked this coin up enough? You have to fuck it up even more? Enjoy your invalid transactions.
A question for some of the more computer savvy members. I will be going out of town for a few months but I want my wallet to continue to stake and to solo mine while I am gone. I can write a bash script to start the solo miner if/when my wife gets her hands on my computer to play a game on Windoze. What I am not sure of is the command to start the wallet unlocked and staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
I'm away quite often and currently dont have a solution - however, I'm using the qt wallet - which is probably why
A question for some of the more computer savvy members. I will be going out of town for a few months but I want my wallet to continue to stake and to solo mine while I am gone. I can write a bash script to start the solo miner if/when my wife gets her hands on my computer to play a game on Windoze. What I am not sure of is the command to start the wallet unlocked and staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
A question for some of the more computer savvy members. I will be going out of town for a few months but I want my wallet to continue to stake and to solo mine while I am gone. I can write a bash script to start the solo miner if/when my wife gets her hands on my computer to play a game on Windoze. What I am not sure of is the command to start the wallet unlocked and staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
ask Joe... he probably knows... considering he's gone at the worst time and things continue to runs somehow...Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
you will probably need to teach your wife/ to resync
A question for some of the more computer savvy members. I will be going out of town for a few months but I want my wallet to continue to stake and to solo mine while I am gone. I can write a bash script to start the solo miner if/when my wife gets her hands on my computer to play a game on Windoze. What I am not sure of is the command to start the wallet unlocked and staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
Does anyone know how to start m-wallet unlocked and staking? ./m-wallet will start it, but the wallet is locked (needs password) and not staking.
i'll try that, thanks
Then your IP is probably temporary banned at the 104.128.225.215 node due to previously fork (misbehaviour).
Are you able to refresh your internet-connection to get a new public IP ? (then that will help)
(or you have to wait until your IP is "released" again)
i've redownloaded the chain and had it pointed to 104.128.225.215 but its been at 0 connections for the past 30 mins.
Then your IP is probably temporary banned at the 104.128.225.215 node due to previously fork (misbehaviour).
Are you able to refresh your internet-connection to get a new public IP ? (then that will help)
(or you have to wait until your IP is "released" again)
i've redownloaded the chain and had it pointed to 104.128.225.215 but its been at 0 connections for the past 30 mins.
Then your IP is probably temporary banned at the 104.128.225.215 node due to previously fork (misbehaviour).
Are you able to refresh your internet-connection to get a new public IP ? (then that will help)
(or you have to wait until your IP is "released" again)
i've redownloaded the chain and had it pointed to 104.128.225.215 but its been at 0 connections for the past 30 mins.
Coin of magi, last block 1823008
off by 1000-ish
xmgpool , network block 1822033
xmg luckypool, network block 1822033
PoM pool, network block 1823008
minerclaim, network block 1823006
CoinMagi XMG, network block 1823008
off by 60-ish
TrasMaMod, network block 1822945
XpoolX, network block 1822945
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
Resync my wallet from m-core, current block seems to be 1822950, I would say TrasMaMod and XpoolX seem to be correct. The only connection I have for my wallet is 104.128.225.215.
Coin of magi, last block 1823008
off by 1000-ish
xmgpool , network block 1822033
xmg luckypool, network block 1822033
PoM pool, network block 1823008
minerclaim, network block 1823006
CoinMagi XMG, network block 1823008
off by 60-ish
TrasMaMod, network block 1822945
XpoolX, network block 1822945
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
Resync my wallet from m-core, current block seems to be 1822950, I would say TrasMaMod and XpoolX seem to be correct. The only connection I have for my wallet is 104.128.225.215.
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
Mineproject appears to not be on the current chain after last week's fork.
Hashtech is offline, or at least their website is not responding.
Mineproject remove Magi from the coins list, so it is shutdown.
Minerclaim is all messed up at the moment. miners getting errors, Pool efficiency at 38.60% My unconfirmed are through the roof. Think its time to shut down and wait for the shit to clear.
edit Pool just went down
edit Pool just went down
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
Mineproject appears to not be on the current chain after last week's fork.
Hashtech is offline, or at least their website is not responding.
Coin of magi, last block 1823008
off by 1000-ish
xmgpool , network block 1822033
xmg luckypool, network block 1822033
PoM pool, network block 1823008
minerclaim, network block 1823006
CoinMagi XMG, network block 1823008
off by 60-ish
TrasMaMod, network block 1822945
XpoolX, network block 1822945
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
Resync my wallet from m-core, current block seems to be 1822950, I would say TrasMaMod and XpoolX seem to be correct. The only connection I have for my wallet is 104.128.225.215.
Coin of magi, last block 1823008
off by 1000-ish
xmgpool , network block 1822033
xmg luckypool, network block 1822033
PoM pool, network block 1823008
minerclaim, network block 1823006
CoinMagi XMG, network block 1823008
off by 60-ish
TrasMaMod, network block 1822945
XpoolX, network block 1822945
-- These feels totally wrong
MineProject, network block 1816206
hashtexh xmg, network block 1678263
TrasMaMod, please post your current blockchain archive
ok,
reloading the blockchain with listen=0, etc enabled the wallet to be up todate.
However it still feels totally unstable with all different network blocks.
reloading the blockchain with listen=0, etc enabled the wallet to be up todate.
However it still feels totally unstable with all different network blocks.
Anyone have the latest chain snapshot? I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old. Only goes up to 1813042. I solved 3 blocks last night solo mining but they are probably on the wrong fork.
This advice is working! resetting the blockchain WITH the changes in the config is keeping me up to date. Thank you!
This advice is working! resetting the blockchain WITH the changes in the config is keeping me up to date. Thank you!
Also, mining on Tras. and that is working too!
Anyone have the latest chain snapshot? I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old. Only goes up to 1813042. I solved 3 blocks last night solo mining but they are probably on the wrong fork.
Sigh...
That's the last "safe"/"Correct" block in the chain before the split. so best start from there to stop any more errors.Sigh...
Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero
Code:
connect=104.128.225.215
listen=0
listen=0
replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :
Code:
checkwallet
thenCode:
repairwallet
in the wallet console and restart the wallet.You might loose the coins mined unfortunately!
(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet)
so you're not alone in the pain of loosing xmgThis advice is working! resetting the blockchain WITH the changes in the config is keeping me up to date. Thank you!
Wallet debuglog :
trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71064, blocks=1821844, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
receive version message: version 71064, blocks=1822934, us=31.209.18.153:38873, them=104.128.225.215:8233, peer=104.128.225.215:8233
Flushed 8942 addresses to peers.dat 15ms
received block 000000017c1729d9f0bf
ProcessBlock: ORPHAN BLOCK, prev=000000018863b1645665
Flushed 8942 addresses to peers.dat 16ms
received block a6c7243194fbadbe7d2b
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215
ERROR: ProcessBlock() : block with too little proof-of-stake
Debug window:
Current number of block 1821844
https://poolinfo.systms.org/ gives a couple of different network blocks for the pools..
trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71064, blocks=1821844, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
receive version message: version 71064, blocks=1822934, us=31.209.18.153:38873, them=104.128.225.215:8233, peer=104.128.225.215:8233
Flushed 8942 addresses to peers.dat 15ms
received block 000000017c1729d9f0bf
ProcessBlock: ORPHAN BLOCK, prev=000000018863b1645665
Flushed 8942 addresses to peers.dat 16ms
received block a6c7243194fbadbe7d2b
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215
ERROR: ProcessBlock() : block with too little proof-of-stake
Debug window:
Current number of block 1821844
https://poolinfo.systms.org/ gives a couple of different network blocks for the pools..
I confirm.
This is new kind of that how Joe modificated node. Уeбaн бля зaeбaл.
That's the last "safe"/"Correct" block in the chain before the split. so best start from there to stop any more errors.
Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero
replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :
You might loose the coins mined unfortunately!
(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet) so you're not alone in the pain of loosing xmg
You're a great friend, your information is useful to someone else's friend. Continue like this park, Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero
Code:
connect=104.128.225.215
listen=0
listen=0
replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :
Code:
checkwallet
thenCode:
repairwallet
in the wallet console and restart the wallet.You might loose the coins mined unfortunately!
(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet)
so you're not alone in the pain of loosing xmgWhat does the change on listen=1 to listen=0 do?
it means: Do not accept any incomming request from other nodes, you are then sticked only to the node you specified with connect=
Wallet debuglog :
trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71064, blocks=1821844, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
receive version message: version 71064, blocks=1822934, us=31.209.18.153:38873, them=104.128.225.215:8233, peer=104.128.225.215:8233
Flushed 8942 addresses to peers.dat 15ms
received block 000000017c1729d9f0bf
ProcessBlock: ORPHAN BLOCK, prev=000000018863b1645665
Flushed 8942 addresses to peers.dat 16ms
received block a6c7243194fbadbe7d2b
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215
ERROR: ProcessBlock() : block with too little proof-of-stake
Debug window:
Current number of block 1821844
https://poolinfo.systms.org/ gives a couple of different network blocks for the pools..
trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71064, blocks=1821844, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
receive version message: version 71064, blocks=1822934, us=31.209.18.153:38873, them=104.128.225.215:8233, peer=104.128.225.215:8233
Flushed 8942 addresses to peers.dat 15ms
received block 000000017c1729d9f0bf
ProcessBlock: ORPHAN BLOCK, prev=000000018863b1645665
Flushed 8942 addresses to peers.dat 16ms
received block a6c7243194fbadbe7d2b
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215
ERROR: ProcessBlock() : block with too little proof-of-stake
Debug window:
Current number of block 1821844
https://poolinfo.systms.org/ gives a couple of different network blocks for the pools..
Jump to: