Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 108. (Read 2375603 times)
How do i import my backup wallet .dat file into my newly created wallet?
For test only (don't run for regular use):
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
Code:
rpcuser=magirpc
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
My wallet data is not getting in the test wallet. Where should it be located?
Your wallet should be located in C:\User\Your_Username\appdata\roaming\magi for Windows Wallets, and /home/your_username/.magi/ for Linux. The test wallet does not use any kind of special folder for it's files and blockchain, as it is attempting to replicate the actual blockchain as closely as possible.
Since I refuse to upload any blockchain snapshots until this blockchain issue gets smoothed out, I figured I might as well try to help in other way.
I've created a BASH script for Linux Miners that allows you to quickly and easily switch between pools. It can be also be configured to allow for different configurations of the same pool (less threads, more efficiency, etc.).
You can check it out at https://pastebin.com/824VSdYi
I've created a BASH script for Linux Miners that allows you to quickly and easily switch between pools. It can be also be configured to allow for different configurations of the same pool (less threads, more efficiency, etc.).
You can check it out at https://pastebin.com/824VSdYi
I would like to point out that this is a BASH shell script. I have tried this in a SH terminal, but since it contains "BASHisms", it didn't work.
Blockchain snapshot as follows:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
should we use this chain from now on or is it just for the tests of the new client 1.4.6.1?
The blockchain data posted above can be used for normal operation. For normal use, make sure wallet version is 1.4.5.
The test wallet uses the above chain also, because it undergoes a hard fork at later block #. Normal wallet version 1.4.5 and test version 1.4.6.1 won't interfere each other, and won't pick the opposit chain.
REASON we're doing such a test on mainnet instead of testnet is to mimic real situation and make sure hardfork proceeds as expected, after all final going live without real situation simulation risks further damages. I do see test on mainnet moves slow, and would thus consider a parallel testnet test.
There are a few confusions; so if one isn't aware of the process and difference of test, pls don't run 1.4.6.1.
I just extracted the block chain, deleted the db and block folders, and restarted, but it appears to be downloading all the blocks from the network. Did I forget something? I am running the v1.4.5.3 (64-bit) wallet.
Moved the folders up to the correct path, but now I appear to be missing 84+ XMG!
What I did instead of deleting old blockchain was add a letter in from of the old folder name. ie.. blocks is now zblocks Then I extracted the files into the directory and now it is syncing. In case something happens with this chain, I won't have to spend half the day on my crappy interwebs redownloading.
Blockchain snapshot as follows:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
should we use this chain from now on or is it just for the tests of the new client 1.4.6.1?
The blockchain data posted above can be used for normal operation. For normal use, make sure wallet version is 1.4.5.
The test wallet uses the above chain also, because it undergoes a hard fork at later block #. Normal wallet version 1.4.5 and test version 1.4.6.1 won't interfere each other, and won't pick the opposit chain.
REASON we're doing such a test on mainnet instead of testnet is to mimic real situation and make sure hardfork proceeds as expected, after all final going live without real situation simulation risks further damages. I do see test on mainnet moves slow, and would thus consider a parallel testnet test.
There are a few confusions; so if one isn't aware of the process and difference of test, pls don't run 1.4.6.1.
I just extracted the block chain, deleted the db and block folders, and restarted, but it appears to be downloading all the blocks from the network. Did I forget something? I am running the v1.4.5.3 (64-bit) wallet.
Moved the folders up to the correct path, but now I appear to be missing 84+ XMG!
https://tothemoon.live/?IsPast=False&Page=1&Month=0&Year=0&CoinTypes=Magi+%28XMG%29&SortBy=0
Hey guys. Nothing about you and yours events on calendar. Add your events to https://tothemoon.live/ traders already there
Hey guys. Nothing about you and yours events on calendar. Add your events to https://tothemoon.live/ traders already there
About 100 blocks was deleted right now from dev node.
some of which I mined... thanks our great dev 
This is by the strangest coin ever, with a dev come and clean what he doesn't like...
djm34 u are a famous GPU mining software creator
ur high interest in XMG show me u found ways to mine it with GPU
u should offer XMG community the price for open source ur GPU miner
as soon as this happens many problems of the coins would be solved
because noone have 100x more hashpower then everyone else
Also in view of the reward being at 0.5xmg or less most of the time during the last 3months, it would be a lot worst....
Basically all cpu miner (ie xmg community) would go and be replaced by other including big gpu farm which have way more than 100x the hashpower of a everyone else... (and we saw very well during the last 3 months that scarcity doesn't influence market price either...)
so it would be totally pointless to release one...
About 100 blocks was deleted right now from dev node.
some of which I mined... thanks our great dev This is by the strangest coin ever, with a dev come and clean what he doesn't like...
djm34 u are a famous GPU mining software creator
ur high interest in XMG show me u found ways to mine it with GPU
u should offer XMG community the price for open source ur GPU miner
as soon as this happens many problems of the coins would be solved
because noone have 100x more hashpower then everyone else
Blockchain snapshot as follows:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
should we use this chain from now on or is it just for the tests of the new client 1.4.6.1?
The blockchain data posted above can be used for normal operation. For normal use, make sure wallet version is 1.4.5.
The test wallet uses the above chain also, because it undergoes a hard fork at later block #. Normal wallet version 1.4.5 and test version 1.4.6.1 won't interfere each other, and won't pick the opposit chain.
REASON we're doing such a test on mainnet instead of testnet is to mimic real situation and make sure hardfork proceeds as expected, after all final going live without real situation simulation risks further damages. I do see test on mainnet moves slow, and would thus consider a parallel testnet test.
There are a few confusions; so if one isn't aware of the process and difference of test, pls don't run 1.4.6.1.
For test only (don't run for regular use):
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
Code:
rpcuser=magirpc
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
Read the big red print Joe has on the top before listening to Vit and screwing things up worse. Do you really think the Vit is going to give good sound advice when he is the one that created all this damage? Would you let someone that robbed you come stay at your house??? I know I wouldn't follow such practices.
At the bottom of his post also says to "We'll monitor progress; pls help mining on test chain, particularly PoS staking. "
So as the BIG RED LETTERS say For test only (don't run for regular use):
I stand corrected and I withdrawl my last.
Read the big red print Joe has on the top before listening to Vit and screwing things up worse. Do you really think the Vit is going to give good sound advice when he is the one that created all this damage? Would you let someone that robbed you come stay at your house??? I know I wouldn't follow such practices.
The blockchain snapshot should be fine.
From the wallet production branch - https://github.com/magi-project/magi/blob/master/README.md - under Setup...
Quote
Download latest block-chain data from here: http://m-core.org/bin/block-chain
That links to what Joe posted under "download blockchain..." but he provided direct links rather than dropping you in the directory.
The wallet is test.
For test only (don't run for regular use):
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
The following are for testing solutions to the current issue; for one who wants to help out, here are the steps:
Source: https://github.com/magi-project/magi/tree/1.4.6-test-1
# Download blockchain and unzip into the right place:
https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz
# Download binaries (windows, linux and osx):
https://m-core.org/bin/m-wallet-1.4.6.1-test/m-wallet-1.4.6.1-test.zip
# Setup magi.conf:
Code:
rpcuser=magirpc
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
rpcpassword=magipass
daemon=1
server=1
listen=1
rpcallowip=127.0.0.1
posii=1
addnode=159.203.71.237
addnode=138.197.70.198
# Launch the wallet
We'll monitor progress; pls help mining on test chain, particularly PoS staking.
Read the big red print Joe has on the top before listening to Vit and screwing things up worse. Do you really think the Vit is going to give good sound advice when he is the one that created all this damage? Would you let someone that robbed you come stay at your house??? I know I wouldn't follow such practices.
The dev node and two other pools (pom-m-hash.com and magi.trasmamod.com) seem to be in sync, but CryptoID seems to be about ~10 blocks ahead.
https://image.ibb.co/cirEeS/Capture.png -- https://image.ibb.co/hFQwtn/Capture1.png
https://image.ibb.co/cirEeS/Capture.png -- https://image.ibb.co/hFQwtn/Capture1.png
I am mining with Trasmamod. Now my wallet will not sync up. Anyone besides the douche that caused have a fix? I will not trust advice from the one that broke it....
XpoolX is now on the good network
Good to know, although I lost 350-400 (confirmed) coins so far over these couple of days ... so basically we're producing nothing more than "hot air"
XpoolX is now on the good network
So, just to be clear, the new wallet is for testing, don't connect it to the main network, and just run it with a fresh chain, right?
That's what I'm doing ATM.
That's what I'm doing ATM.
Minerclaim
Short Update: We are working on several problems all the time. Mining is currently unstable and affected by frequent malfunctions. We don't recommend mining at this time. Its very experimental in that moment. Coin Magi development is working on a fix for the major issue. Meanwhile, we are also working to improve our availability.
Short Update: We are working on several problems all the time. Mining is currently unstable and affected by frequent malfunctions. We don't recommend mining at this time. Its very experimental in that moment. Coin Magi development is working on a fix for the major issue. Meanwhile, we are also working to improve our availability.
Why the heck would you use the chain provided by Joe and the single node from him for regular use and mining when it was clearly stated by him that it is ONLY for test use.
Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.
this the regular blockchain and regular node... not the test stuff. The real question is why he isn't asking to use testnet... Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.
so tests are made on some nodes on the main net and he is asking people to help (while half the people "helping" will just mess up...).
This is a recipe for disaster...
wondering how this coin has been able to survive 4 years with such practices
Why the heck would you use the chain provided by Joe and the single node from him for regular use and mining when it was clearly stated by him that it is ONLY for test use.
Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.
Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.
The dev node and two other pools (pom-m-hash.com and magi.trasmamod.com) seem to be in sync, but CryptoID seems to be about ~10 blocks ahead.
-- 
-- Jump to: