Show Posts
|
Pages: « 1 [2] 3 »
|
ALTs are a gamble. To a certain extent so is BTC.
So with any gamble whether the odds of winning are high or low, you only play with what you can afford to lose.
|
|
|
What is everyone doing to convert theirs? Or you holding yours.
I sent mine to my wallet to hold some and to send some to Yobit
|
|
|
I have a question - according to whattomine Musicoin profitability is roughly 10% more than for ETH. Although they both use "ethash", where does better profitability come from? Does it mean that let's say the same GPU will have better hashrate while mining musicoin than ETH because of lower network difficulty? Or there is some other reason? thanks!
The figures take into account the mining ability as well as market price. So if difficulty in musicoin were to rise, it would affect the values. In fact, any change in difficulty, price, etc changes the values
|
|
|
The test wallet checks blocks to make sure PoW and PoS following a pattern: 1) at least two PoS between PoW blocks, and 2) for any continuous five blocks contains at least one PoW block. When the above conditions are not satisfied, blocks come out at about every 15min. Blocks found before 15min is up will then be rejected, along with error "block violations".
The waiting time "15min" rule might be a concern when PoS blocks not coming out as expected; it would be necessary to rely on the PoS thing which is the main force in the future. By the time when the whole network is staking and PoS becomes a major force pushing forward the chain, we won't see the 15min rule. The 15min is somehow a random number I come up with, that was made to differ from the regular PoW block time (3min). Reducing the waiting time would recover things back to normal faster.
Thanks all for the test in both PoW and PoS. I believe the chain moves as expected, and I don't see particular concerns, except for the block time, which is 3.17min by averaging the past 100 blocks at #1451764. The longer block time is mainly due to limited PoS blocks; the situation shall get changed once on the mainnet that has more in PoS staking.
I'll update the way that difficulty adjustment works by taking into account the "15min" rule. Once we're done that, we will make changes to the main source code. I hope we get it done in next week.
Pls let me know if you see a fork in test.
Thank you for the timely update
|
|
|
Ive scanned the wallet with 3 different Anti-Virus products and they all quarantine it as a Trojan. I dont have this problem with other QT Wallets, why yours?
B
|
|
|
I like your temporary solution to the global hash. Thank you!!!
E
HEY -- Does anyone have what is required to do a NOMP correctly? I do not know how to get it to do the hashing because it doesn't seem to recognize the M7m Algo.>...
Pool owners of NOMP pools can someone help me install my own pool? I am completely confused now because I can't get P2pool to work due to some kind of p2p port lock up in the running of the P2Pool and the NOMP don't seem to have the config settings needed.
how did you guys get XMG working on NOMP or otherwise? Trying to get a ready-made server for linux or windows set up that I can just install, I am lost up to my chin in json and config file confusion. Please help? Thanks!
Enoch
I had the same problems with NOMP. Edward helped me out though. You have to add the algorithm, to the algroproperties.js file. I don't have access to the server right now but its under the node-multi-hashing/libs folder IIRC I got NOMP running but ran into problems creating the Stratum. I'm going to work on it again later this week B
|
|
|
Hello everyone,
I have been mining magi since 2 months till I stopped about the time the problems happened.
After that I came to this post and realized i was just killing the network.
I was new to mining and XMG was the first coin that came up when I googled CPU mine able coins.
I have access to about 60 I7 machines and 6 16 core Xeon servers and I was mining at them 24 / 7 (we don't have electricity bills in the country I am in).
I made about 5500 XMG in one month and in the fork problems I also lost a lot of coins.
I had no idea that putting in more PCs will simply reduce the reward as I was too lazy to come here and read first.
Now I have just put 10 PCs for XMG (2 hours a day) and remaining are mining VRM (6 hours a day) only.
Sorry people.
Thanks for curtailing the nodes.
|
|
|
Man we are under attack from a hash monkey again
How good would it be if magi had its own internal pool and there was no external ones, 250kh/s soft limit where your miner was built into the wallet and can only mine from that application
Decentralization is a key feature of the coin though
|
|
|
A fair point you have made. However...
The issue here is not where the highest valuation can be, it is where it tends to gravitate towards. There is little doubt that many who were mining SIGT when profits were significantly higher than ETH mining were doing so to turn the coin over into ETH. And... when they did, that caused a wave of selling. And, do not forget that when SIGT was 4000, it was both very brief and at a time when BTC was NOT in the mid 4000's USD.
My point is, SIGT hit quickly with strong daily mining profits and that invited the opportunity to SELL SIGT and roll over into more stable and mature coins. That will cease to be the case in just a few hours.
This is just one part of the equation, but it is the part that, at least for the last 30K blocks, explains where SIGT can only seem to get about 20% above ETH mining returns before it finds a ceiling in value.
If someone is always there to sell just a little higher than what they want to roll into, SIGT cannot advance. That opportunity will likely be gone in just a few hours and within a few days we will see what happens when these short term traders no longer can profit from their quick selling.
Well said... The coin matures today as the "get rich quick" traders disappear
|
|
|
Joe,
Still running on the test node. Just passed 1452012. Still waiting for a fork
B
|
|
|
getblockhash 1451400 00000087b7a1689e3bed8787f0c6cdb736f3ea7b81da076d9560fd35f022a891 getblockhash 1451402 000000786038a6da92a61753cc2ed0f920d8b745eca3901d849631becd27caf2
I'm only seeing this error
Flushed wallet.dat 17ms ERROR: mempool transaction missing input
Same block hashes here. We're on same chain. Seems like someone broadcasted a transaction with invalid input(s). Possibly from an orphaned block. EDIT: that errors seems to be logged inside the new block generation function, both for mining or staking. I believe your wallet won't find any of the two kinds of blocks. Does it resolve if you restart the wallet? I think that error is with wallet.dat and i don't think restart will help. getblockhash 1451404 000000397a5d746a3e3a29c5029dece846e4d319b7fbdb73fb24e6284ffa8847 Nor resetting the blockchain? Looks like it was addressed here https://bitcointalk.org/index.php?topic=735170.msg21217741#msg21217741
|
|
|
How can I tell if I'm forked? I assume I am since I just started mining ~30 Magis per hour.
B
I'm still in the main test chain. Check your blocks in the Console: getblockhash 1451400 00000087b7a1689e3bed8787f0c6cdb736f3ea7b81da076d9560fd35f022a891 But I have this warning in my log file: WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock WARNING: averaged over less than BBLOCK_AVER blocks --> GetDifficultyFromBitsV2 WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock ERROR: no actual average done --> GetDifficultyFromBitsV2 WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock WARNING: averaged over less than BBLOCK_AVER blocks --> GetDifficultyFromBitsV2 WARNING: GetLastPoWBlockIndex() not found; return pindexGenesisBlock ERROR: no actual average done --> GetDifficultyFromBitsV2 getblockhash 1451400 00000087b7a1689e3bed8787f0c6cdb736f3ea7b81da076d9560fd35f022a891 getblockhash 1451402 000000786038a6da92a61753cc2ed0f920d8b745eca3901d849631becd27caf2 I'm only seeing this error Flushed wallet.dat 17ms ERROR: mempool transaction missing input
|
|
|
How can I tell if I'm forked? I assume I am since I just started mining ~30 Magis per hour.
B
|
|
|
So far, no fork. Did you mean listen=0 instead of server=0? I believe you need server=1 to accept RPC mining commands. I was wondering the same. Should we be solo mining to push it along?
|
|
|
Sure. I'll see what I can do
|
|
|
Hello, as many of you have already seen, a few pools were running of out sync the last night again. We were also affected. That means, there were blocks which wasn't valid / on the right chain. It was affected a period of around 6 hours. We have updated our blockchain again and changed our banscore to a higher value again to get the chain more stable. However, we know that some of you lost a huge anmount of coins. We are really sorry about that. But you should know, this isn't a pool related problem, rather a general problem we all have since the last two weeks. In some cases its not easy to identify which pool is on the "right chain". I also would like to apologize for the fact that we also need sleep and can not always be reachable, but we try to be. As some you may saw, we decided to payout a part of the "wrong block" from our own funds. We talk about an anmount of ~300 XMG. We decided this due the fact that we have noticed the out of sync problem a little bit late ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) Will answer soon again regarding the high hashrate users. Thank you. Have you notified or taken action against the users who are running > 300k?
|
|
|
As I received many requests of no-rollback and also many posts here, we will take the majority that we will go on with the chain on 104.128.225.215 as is, NO ROLLBACK. However, I strongly believe the PoW reward needs a reset at this mode before fix is released in the near future, and the number I have in mind is maximum 15 XMG / block. This is a temporary solution so that we keep chain / mining going. I temporarily shut the node down until we make release of the wallet. Please be prepare for the mining which can be done through solo mining. Please ask if you have questions of starting up solo mining. In the meantime, we seek pools like NOMP; few people present help on NOMP. I appreciate this.
I was working on a NOMP node but am not finding that it supports M7M. Anybody else here running a NOMP node for MAGI? can always ask me. I have nomp node running on Magi. PMs a coming ;-)
|
|
|
I was working on a NOMP node but am not finding that it supports M7M. Anybody else here running a NOMP node for MAGI?
https://github.com/ganjitoka/nomp-multi-hashing-bp Thx!!
|
|
|
|