Team Magi XMG wishes all Magi friends a happy & healthy 2018!
Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 237. (Read 2375622 times)
Team Magi XMG wishes all Magi friends a happy & healthy 2018!
Can someone please point me to the best config for my wallet?
This is what someone told me a while back but I'd love some confirmation as I really do not understand what these settings do.
Ah ok. I or somebody else will get back on this.This is what someone told me a while back but I'd love some confirmation as I really do not understand what these settings do.
Quote
# example: http://coinmagi.org/bin/example-conf/magi.conf
# this configuration file allows a user to load runtime options when the program starts
# Add nodes to connect to specific peers
# addnode=104.207.149.217:3333
# posii=1 to enable PoS staking; default = 0
posii=1
# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=2200
# Transactions with values less than the threshold will combine into one
stakecombinethreshold=800
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100
# this configuration file allows a user to load runtime options when the program starts
# Add nodes to connect to specific peers
# addnode=104.207.149.217:3333
# posii=1 to enable PoS staking; default = 0
posii=1
# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=2200
# Transactions with values less than the threshold will combine into one
stakecombinethreshold=800
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100
Can someone please point me to the best config for my wallet?
This is what someone told me a while back but I'd love some confirmation as I really do not understand what these settings do.
This is what someone told me a while back but I'd love some confirmation as I really do not understand what these settings do.
Quote
# example: http://coinmagi.org/bin/example-conf/magi.conf
# this configuration file allows a user to load runtime options when the program starts
# Add nodes to connect to specific peers
# addnode=104.207.149.217:3333
# posii=1 to enable PoS staking; default = 0
posii=1
# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=2200
# Transactions with values less than the threshold will combine into one
stakecombinethreshold=800
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100
# this configuration file allows a user to load runtime options when the program starts
# Add nodes to connect to specific peers
# addnode=104.207.149.217:3333
# posii=1 to enable PoS staking; default = 0
posii=1
# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=2200
# Transactions with values less than the threshold will combine into one
stakecombinethreshold=800
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100
if fork applied?
As of the time that I have posted this, it does not appear to be applied yet. There has been some conflicting information about when the network will reach block 1606950, so my guess is as good as yours.
The date was in reference to the expected release of the new wallet (it was released early)
The block is when the actual fork will take place.
if fork applied?
As of the time that I have posted this, it does not appear to be applied yet. There has been some conflicting information about when the network will reach block 1606950, so my guess is as good as yours.
if fork applied?
So everyone keeps saying "Wait until block #1606950", but are we running the test wallet until that block is reached? Are we making transactions until then? How are we to reach this block if most pools are disabled?
Also, I downloaded the new wallet, but it doesn't seem to want to connect... Is this a known bug?
Also, I downloaded the new wallet, but it doesn't seem to want to connect... Is this a known bug?
I have also updated the wallet, it shows the current amount of XMG correctly, but the price in $ is 0, whereas the previous wallet showed the $ price as well. Is this a bug?
i found same issue. but if you double click on the usd/xmg price it will update.
Nice catch, thank you.
was the same in the previous version for me as well.
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
For people who missed this post from dev JoeHard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
/\
this
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
For people who missed this post from dev JoeHard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
More like for people who refuse to read, lol.
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
For people who missed this post from dev Joe Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releases
http://m-core.org/download/
http://m-core.org/bin/m-wallet-1.4.5.1/
Source code: https://github.com/magi-project/magi/
Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz
Block chain: http://m-core.org/bin/block-chain/
v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
Hi
Is fork tied to a specific date or to a specific block?
So someone will make coins while we wait. It seems that someone will get a good profit for the new year
I wonder how much the coin will cost after the fork
Happy New Year and Merry Christmas!
C Hoвым Гoдoм и Poждecтвoм, peбятa!
Is fork tied to a specific date or to a specific block?
So someone will make coins while we wait. It seems that someone will get a good profit for the new year
I wonder how much the coin will cost after the fork
Happy New Year and Merry Christmas!
C Hoвым Гoдoм и Poждecтвoм, peбятa!
Price moving back up. Above 10000 currently on Bittrex off it's low. 
Cheers to the Dev Team and Happy New Years!
Strato
Cheers to the Dev Team and Happy New Years!
Strato
Happy New Years all - lets hope for a 2018 as good as 2017 for XMG
Thank you, same to you and everybody!
MINING POOLS HAVE TO UPDATE CODE FOR MINING TO WORK, HARDFORK HAS TO ARRIVE FOR MINING TO WORK.
Updating your wallet on your PC doesn't change the code base on the pools.
PLEASE give them some time before hammering the pools. Also, remember there is a sweet spot for the network, AND some pools (the main PoM pool for instance) have SPEED LIMITS to maximize rewards. Please do everyone a favor and obey the pool rules and imposed speed limits! The limits are there for your's and everyone else's benefit.
Updating your wallet on your PC doesn't change the code base on the pools.
PLEASE give them some time before hammering the pools. Also, remember there is a sweet spot for the network, AND some pools (the main PoM pool for instance) have SPEED LIMITS to maximize rewards. Please do everyone a favor and obey the pool rules and imposed speed limits! The limits are there for your's and everyone else's benefit.
Yeah - wouldn't expect every pool to update today or tomorrow - first working day is tuesday...
MINING POOLS HAVE TO UPDATE CODE FOR MINING TO WORK, HARDFORK HAS TO ARRIVE FOR MINING TO WORK.
Updating your wallet on your PC doesn't change the code base on the pools.
PLEASE give them some time before hammering the pools. Also, remember there is a sweet spot for the network, AND some pools (the main PoM pool for instance) have SPEED LIMITS to maximize rewards. Please do everyone a favor and obey the pool rules and imposed speed limits! The limits are there for your's and everyone else's benefit.
Updating your wallet on your PC doesn't change the code base on the pools.
PLEASE give them some time before hammering the pools. Also, remember there is a sweet spot for the network, AND some pools (the main PoM pool for instance) have SPEED LIMITS to maximize rewards. Please do everyone a favor and obey the pool rules and imposed speed limits! The limits are there for your's and everyone else's benefit.
I would research the device more, i couldnt find to much information on it, but from what ive read the m7m algo goes off the cache in the processor and mining actually uses very little memory hence why its possible on pi's, i doubt its impossible to get one to mine xmg but you would probably have to write your own miner or heavily modify one of the current ones to run on the xtensia 32bit processor and would expect 0.5h's, and it depends which version the esp32 uses, when looking on the xtensia chip each one is customised to the manufacturers specifications. It's all open source so you can see all the code at https://github.com/magi-project/magi. I think the xtensia chip could actually be quite use full to mine xmg and aeon when looking on the custom order section for the chips, but for someone who is prepared to custom order 100+ chips and build their own usb or asic type miner.
ESP's are very well known by the makers community. There are used for a lot of DIY projects about home-automation, IoT,... They are very cheap and available. Espressif provide a C SDK, and it is supported by many frameworks like Arduino and MicroPython.
I know this project would need a lot of work to port/implement M7M on the device, but I find it interesting (even if it would not be very powerful).
I'll have a look at the code, but I would be interested in any documentation that would help anyone to implement the algo, so that I can see if I have the time/knowledge to try to do it by myself
ESP32s are still too expensive to be profitable, not when you would need 22 of them to come close to what a single 35.00 Pi3 can do (11-12 kH/s)
Price moving back up. Above 10000 currently on Bittrex off it's low.
Cheers to the Dev Team and Happy New Years!
Strato
Cheers to the Dev Team and Happy New Years!
Strato
Happy New Years all - lets hope for a 2018 as good as 2017 for XMG
HAAAAAAAAAAAAPYYYYYYYY NEWWWWWW YEARRRRRRRRRRRRRRRRRRRRR AMIGOOOOOOOOOOOSSSSSS 
xpoolx.com appears to be down?
for me also, but only the website. stratum servers are still available...
Same on both counts.
xpoolx.com appears to be down?
for me also, but only the website. stratum servers are still available...
Jump to: