Bitcoin Forum
June 17, 2024, 01:58:49 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 [1121] 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 ... 1310 »
  Print  
Author Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]  (Read 2375351 times)
trader03
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
January 09, 2018, 01:38:41 AM
 #22401

WWWWWWWOOOOWWWWWWWW       Net Hashrate:   225,514.42 KH/s    just now
Amazing first time I see her so high
cryptoaficionado
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
January 09, 2018, 01:41:26 AM
 #22402

Greetings, first post, new(ish) to Magi, but not new to the Crypto scene. I've been following this coin in the shadows, and pumping in some hash power (60-80khash) mainly prior to the fork, which thanks to this rise in price, made a few bucks on the chain prior to the fork.  Just set my wallet machine 2 hours ahead, and pumped some hash into it, lots of orphans/boos, but some actually did go through, though it is not like I'm sitting pretty like the old timers, I got like 10 XMG (yeah I know ballin out of control here), but still managed to gain something (considering I had nothing to begin with 3 weeks ago).  Right now the network might as well be a turtle in a shell (and ROFL for whomever wrote "you could throw a unicorn at it, and out would come dust").  I know there isn't even a point of throwing anything larger than a Pi 3 @ 10khash at it. As for what I've been (cpu) mining instead, that has been very yum  Grin

Ultimately, for everyone who is complaining about the "whales", there is a solution... generate more transactions on the network, e.g. integrate it into more systems, that will cause the required network hashes to increase, thus increasing payout (at least from my understanding of how the Magi PoW algorithm works), or wait for them to (hopefully sooner than later) re-target a different coin.  Someone should go make a Crypto Puppies game powered on Magi or something  Cheesy
trader03
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
January 09, 2018, 02:04:15 AM
 #22403

Ranking     Miner                Kh/s       XMG/Day
1      kakaeli           8,328   3.255
2      anonymous   1,366   0.534
3      anonymous   888           0.347
4      lmdgzs           810           0.317
5      drmarian           703           0.275
6      haresh2421   646           0.253
7      gazk                   626           0.245
8      runningwithbeer   584           0.228
9      anonymous   492           0.192
10      mmagoo           486           0.190
11      anonymous   438           0.171
12      superminerow   425           0.166
13      nchls_gh1           419           0.164
14      anonymous   364           0.142
15      anonymous   351           0.137

999999      and me      0.0000001    0.0000000001  Grin Grin Grin Grin Grin
trader03
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
January 09, 2018, 02:14:21 AM
 #22404

friends it is possible to make a cpu have AES-NI Huh

Perform a mining test with an intel 550 i3 processor to the AEON currency, but I get an error because this processor does not have AES-NI that is required, someone knows something about this detail.
auskevin
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
January 09, 2018, 02:21:37 AM
 #22405

friends it is possible to make a cpu have AES-NI Huh

Perform a mining test with an intel 550 i3 processor to the AEON currency, but I get an error because this processor does not have AES-NI that is required, someone knows something about this detail.
[
Not that I am aware. I believe it is built in to the processor.
trader03
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
January 09, 2018, 02:38:44 AM
 #22406

Who knows if minar Verium Reverse (VRM) is profitable HuhHuh Huh
ParaplegicRacehorse
Member
**
Offline Offline

Activity: 79
Merit: 36

HODL. Patience.


View Profile
January 09, 2018, 04:41:47 AM
 #22407

friends it is possible to make a cpu have AES-NI Huh

Perform a mining test with an intel 550 i3 processor to the AEON currency, but I get an error because this processor does not have AES-NI that is required, someone knows something about this detail.

It is part of the processor and no amount of software can add it.

Who knows if minar Verium Reverse (VRM) is profitable HuhHuh Huh

And, please ask questions about other currencies in their respective forum threads.
- AEON https://bitcointalk.org/index.php?topic=641696.0
- Verium https://bitcointalk.org/index.php?topic=2385158

Thank you.
alokasi
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 09, 2018, 07:04:03 AM
 #22408

Could someone explain this to me.  I'm a complete noob to the cryptocurrency arena.  From my understanding this has to do with staking, but why are the values negative? This transaction (ID from my wallet) returns no results on https://chainz.cryptoid.info/xmg/

Thanks in advance.

Status: 0/unconfirmed, broadcast through 3 nodes
Date: 1/8/2018 15:41
Debit: 0.00 XMG
Transaction fee: -0.00009707 XMG
Net amount: -1.18281494 XMG
Transaction ID: 6b0f1b014b90ac1845d36795ac46aa3da98846225aab641dc46ff9bf1d6792b5
HeftyMagi
Newbie
*
Offline Offline

Activity: 93
Merit: 0


View Profile
January 09, 2018, 08:07:39 AM
 #22409

friends it is possible to make a cpu have AES-NI Huh

Perform a mining test with an intel 550 i3 processor to the AEON currency, but I get an error because this processor does not have AES-NI that is required, someone knows something about this detail.

no that is instruction set that cpu is lacking, mining Aeon is still profitable with cpus they are not that behind gpus. Aeon miners are constantly updating check posts of wolf maybe he made miner that support your cpu in Aeon thread. Cheers Smiley
jonathin.r
Member
**
Offline Offline

Activity: 98
Merit: 11


View Profile
January 09, 2018, 09:09:32 AM
 #22410

Ever since the Magi network has come back online, a lot of these CPU-whales have jumped onboard and started fucking up the share-to-reward balance that we’ve been handling quite well for some time. Listed below are some of the known whales who have been shamelessly ruining this coin by saturating the network with outrageous amounts of hashing power:

kakaeli (Supr Nova) with 9,246 kh/s

HHogan (MinerClaim) with 2,239 kh/s (though I have seen them even higher)

magstrat31 with 1,342 kh/s

deztroyr1 with 1,144 kh/s

preston7tree (LuckyPool) with 1,426 kh/s

gregor (BullMining)  with 1,538 kh/s

Sure compared to 9,246 kh/s, these 1,000 kh/s miners don’t seem like anything. However, considering the average hobbyist miner like myself can maybe get 75-100 kh/s on a good day, that 1,000 kh/s figure should seem outrageous. Also, remember that these numbers change constantly. These were just the whales of the time I posted this (except for HHogan. They’re always hashing crazy numbers.)

This is a message to all the pool operators: Keep the network fair. Impose kh/s limits and stick to them.

My XMG Address: 9LzxHqsxrRPMCyBffjMc3cLuB5hwEG5Ufq
"Un pour tous, tous pour un" - The Three Musketeers, 1844
Derko
Newbie
*
Offline Offline

Activity: 105
Merit: 0


View Profile
January 09, 2018, 09:09:47 AM
 #22411

friends it is possible to make a cpu have AES-NI Huh

Perform a mining test with an intel 550 i3 processor to the AEON currency, but I get an error because this processor does not have AES-NI that is required, someone knows something about this detail.

Ofcourse NO Smiley AES is hardware implementation in the CPU.
HeftyMagi
Newbie
*
Offline Offline

Activity: 93
Merit: 0


View Profile
January 09, 2018, 09:35:52 AM
 #22412

Ever since the Magi network has come back online, a lot of these CPU-whales have jumped onboard and started fucking up the share-to-reward balance that we’ve been handling quite well for some time. Listed below are some of the known whales who have been shamelessly ruining this coin by saturating the network with outrageous amounts of hashing power:

kakaeli (Supr Nova) with 9,246 kh/s

HHogan (MinerClaim) with 2,239 kh/s (though I have seen them even higher)

magstrat31 with 1,342 kh/s

deztroyr1 with 1,144 kh/s

preston7tree (LuckyPool) with 1,426 kh/s

gregor (BullMining)  with 1,538 kh/s

Sure compared to 9,246 kh/s, these 1,000 kh/s miners don’t seem like anything. However, considering the average hobbyist miner like myself can maybe get 75-100 kh/s on a good day, that 1,000 kh/s figure should seem outrageous. Also, remember that these numbers change constantly. These were just the whales of the time I posted this (except for HHogan. They’re always hashing crazy numbers.)

This is a message to all the pool operators: Keep the network fair. Impose kh/s limits and stick to them.

hhogan and kakaeli mine xmg for last 3-4 years constantly, even with them magi menage to have 30-55mhs nethash in some periods, now we have up to 200mhs, either someone is doing this on purpose to scare of small miners with bots or they bought huge hash power thinking after HF they will become rich or they think that xmg price will match extraction/power consumption/profit levels at this nethash Smiley
Jeremy450
Newbie
*
Offline Offline

Activity: 154
Merit: 0


View Profile
January 09, 2018, 09:43:16 AM
 #22413

Ever since the Magi network has come back online, a lot of these CPU-whales have jumped onboard and started fucking up the share-to-reward balance that we’ve been handling quite well for some time. Listed below are some of the known whales who have been shamelessly ruining this coin by saturating the network with outrageous amounts of hashing power:

kakaeli (Supr Nova) with 9,246 kh/s

HHogan (MinerClaim) with 2,239 kh/s (though I have seen them even higher)

magstrat31 with 1,342 kh/s

deztroyr1 with 1,144 kh/s

preston7tree (LuckyPool) with 1,426 kh/s

gregor (BullMining)  with 1,538 kh/s

Sure compared to 9,246 kh/s, these 1,000 kh/s miners don’t seem like anything. However, considering the average hobbyist miner like myself can maybe get 75-100 kh/s on a good day, that 1,000 kh/s figure should seem outrageous. Also, remember that these numbers change constantly. These were just the whales of the time I posted this (except for HHogan. They’re always hashing crazy numbers.)

This is a message to all the pool operators: Keep the network fair. Impose kh/s limits and stick to them.

honestly your speaking upon deaf ears. and just be warned your going to be labeled a cry baby like i was a day or so ago cos i spoke my mind and was going on about the same thing in regards to whales and fairness, etc. you'll get shot down if we keep going on about it. theres alot of good ppl who care about whats going on who have reduced their speeds to 250kh/s like my self. But really alot of dont care and just thinking of themselves. and will just say to you go and buy the coin. they think to buy 4xmg coin is cheap for everyone. For me 4xmg coins cost $15 by the time its converted from AUD to bitcoin to xmg

its pointless *sigh*

starmman
Legendary
*
Offline Offline

Activity: 1484
Merit: 1029



View Profile
January 09, 2018, 09:48:44 AM
 #22414

Ever since the Magi network has come back online, a lot of these CPU-whales have jumped onboard and started fucking up the share-to-reward balance that we’ve been handling quite well for some time. Listed below are some of the known whales who have been shamelessly ruining this coin by saturating the network with outrageous amounts of hashing power:

kakaeli (Supr Nova) with 9,246 kh/s

HHogan (MinerClaim) with 2,239 kh/s (though I have seen them even higher)

magstrat31 with 1,342 kh/s

deztroyr1 with 1,144 kh/s

preston7tree (LuckyPool) with 1,426 kh/s

gregor (BullMining)  with 1,538 kh/s

Sure compared to 9,246 kh/s, these 1,000 kh/s miners don’t seem like anything. However, considering the average hobbyist miner like myself can maybe get 75-100 kh/s on a good day, that 1,000 kh/s figure should seem outrageous. Also, remember that these numbers change constantly. These were just the whales of the time I posted this (except for HHogan. They’re always hashing crazy numbers.)

This is a message to all the pool operators: Keep the network fair. Impose kh/s limits and stick to them.

honestly your speak to deaf ears. and just be warned your going to be labeled a cry baby like i was a day or so ago cos i spoke my mind and was going on about the same thing in regards to whales and fairness, etc. you'll get shot down if we keep going on about it. theres alot of good ppl who care about whats going on who have reduced their speeds to 250kh/s like my self. But really alot of dont care and just thinking of themselves. and will just say to you go and buy the coin. they think to biu 4xmg coin is cheap for everyone. For me 4xmg coins cost $15 by the time its converted from AUD to bitcoin to xmg

its pointless *sigh*


Best thing to do is wait it out and profit when the dust settles - the whales will get bored, when they find out that their hash isn't yielding any reward, there are often a few bursts when a lot of greedy people come online and kill the net hashrate. I've been working that way for the last couple of years and its worked well for me. Magi is more of a get rich slowly than get rich quick coin - the price has been building really nicely...
HeftyMagi
Newbie
*
Offline Offline

Activity: 93
Merit: 0


View Profile
January 09, 2018, 10:27:53 AM
 #22415

Agreed with starman, in last 4 years there has been numerous times when magi was profitable to mine, and it netted profit to ppl who are around magi at that time and are following nethash. Magi mining is similar to trading you got to get in when its low  Grin
Ginzink
Full Member
***
Offline Offline

Activity: 462
Merit: 118


View Profile
January 09, 2018, 11:08:39 AM
 #22416

Agreed with starman, in last 4 years there has been numerous times when magi was profitable to mine, and it netted profit to ppl who are around magi at that time and are following nethash. Magi mining is similar to trading you got to get in when its low  Grin

I was thinking about mining but il just hold what i bought instead. It is an old coin and dev team seems to be ok so the mcap has a decent potential to go up.
Not something id but alot in atm, but that may also be because i have not researched it enough yet as i have only a small portion invested.
starmman
Legendary
*
Offline Offline

Activity: 1484
Merit: 1029



View Profile
January 09, 2018, 11:15:36 AM
 #22417

Agreed with starman, in last 4 years there has been numerous times when magi was profitable to mine, and it netted profit to ppl who are around magi at that time and are following nethash. Magi mining is similar to trading you got to get in when its low  Grin

I was thinking about mining but il just hold what i bought instead. It is an old coin and dev team seems to be ok so the mcap has a decent potential to go up.
Not something id but alot in atm, but that may also be because i have not researched it enough yet as i have only a small portion invested.

It's always a good idea not to be fully exposed to a single coin, I hold a quite few different coins - however for me Magi is one of the larger stores, but I got in when the price was low
the_drugs
Newbie
*
Offline Offline

Activity: 40
Merit: 0


View Profile
January 09, 2018, 11:58:15 AM
 #22418

After reading for the few weeks leading up to the hardfork, as well as the few days after, I've been both impressed and disappointed in the magi community. There are plenty of people that are happy with the growth in magi, and plenty that are simply upset they cant earn any mining. The mining issue has been one that has slowly been reaching a boiling point over the last few months, and was even an issue last time we forked. A lot of people are calling for limits for mining in the protocol, poolside, in the miners, etc. I'd like to take a minute to discuss the issues with each of these approaches and offer my suggestion.

To begin with, we need to understand the potential types of whales we're dealing with.
1 - Botnets
2 - People with large amounts of CPU/CPU power. This could quite simply be someone with a few, very powerful CPU at this point.
3 - People with a private or personal GPU/ASIC miner. Although this is a rumor, this should be considered.

We also need to look at some of the commonly proposed solutions to the hashrate.
1 - limit hashrate poolside
2 - limit hashrate in the protocol
3 - limit hashrate in the miner
I'm aware there are other suggestions as well, they simply dont come to mind as quickly as these and will likely fall under the same ineffective solution as these.

Looking at these issues, the first is easily avoided. Botnets can be configured to create workers for each CPU in the net, or if there is an account limit than a separate account. People with large amounts of CPU power can easily do the same, especially considering if they fall under the few, very powerful CPU category. This would solve the issue of a single miner/worker having a large hashrate, as would be the case for a GPU/ASIC miner, but these are unproven rumors and likely would have minimal impact. It would, however be nice to see.

Moving to limiting hashrate in the protocol. I've seen this suggested and I'm not a technical as many in this thread, however I can already see some issues with this. It will only be a matter of time before someone "cracks" the new update, and when that happens do you think this person will share the code? This will only punish those following the rules more and allow those that abuse the network even more success.

Finally, limiting hashrate in the miner. Same as above, this will just result in other miners without the limit being made, or endless guides on youtube/steemit showing you how to disable the limit.

So what can be done? In my opinion there is no silver bullet, and there is no perfect plan. No matter what the magi network as it stands and is designed will never function perfectly, but we can get closer to the ideal. To begin with, I do believe an updated miner should be released. This miner should use some sort of sweet spot control by default, so the hashrates adapt and change to promote healthy network hashrate. Of course this could be diabled, but that is an extra step that would need to be taken, and would help a good bit. Second, I believe the previously mentioned idea of having the miner suggest if you hashrate is too high/low/just right is good. This could potentially draw miners attention to this and may lead some of them to lower their hash, direct it elsewhere, or simply enable the previously mentioned "sweet spot" mode.
As for pools, simply suggesting on the dashboard whether a users/workers hashrate is too high/low/just right could also help, this would compliment the changes above as well.

The big change I'm suggesting is that we as a community start to seriously suggest and recommend dual mining XMG. I've been experimenting with this recently and I'll be posting some results in the following weeks, but this seems to be a good solution for a number of reasons. For starters, for big miners and botnets this offers the ability to earn more than mining either specific coin on its own. The main benefit for magi, at this point, is then that a majority of their hashrate is moved to another coin, however, some of it does remain. This would be a great point to bring up the idea that magi is supposed to be an "idle power" mine, in that you just use the idle power on you CPU, or in this case leftover from the other coin you're mining. A great example is XMR and XMG, XMR is very cache dependent, and so most of the time one runs out of cache before one runs out of cores. In this example, likely dual mining would take roughly 50-60% of the hashrate from magi, again not perfect, but better than where we are now. I know this wont encourage all of the botnets or large miners to switch, and I know this wont change everything, but I think that all of these things put into action would help to alleviate the strain on the network and small miners.

tl;dr
To help with the issues many are having mining these days I suggest:
1 - Modifying the miners to automatically use a "sweet spot" functionality
2 - modify the miners to suggest whether your hashrate is too high, too low, or just right
3 - draw attention to the fact that magi is design as a "idle power" mine, this can be done on the website, OP, regular posts through here, etc.
4 - suggest and draw attention to the benefits of dual mining XMG and others, such as XMR.

These are just my thoughts and I'd be interested to hear what everyone else thinks. I'm not trying to solve the problem, I'm just trying to come up with ways to help!! I'm sure magi will pull through though  Smiley
starcrys
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
January 09, 2018, 12:40:47 PM
 #22419

I don't know but you know, now my mindset's like "Come on whales lets jack the network hashrate up to 1 GB/s so that the rewards will be even more close to 0 XMG." Maybe then those whales might FINALLY GET LOST.

Sorry, I'm really getting pissed with only getting 0.05 XMG for 2 consecutive days.
trader03
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
January 09, 2018, 02:48:29 PM
 #22420

Thinking again about the issue, I believe that the solutions to many things that are happening at this time are already implanted in the structure of the currency algorithm as such.

The algorithm of each coin is in itself a set of solutions to each problem that is found around the linked events.
In the algorithm it is assumed that the solution to this detail of large amounts of hash per user on the network is already found, however it seems to be out of control, but I could read that the devs. They are taking action on the matter.
I trust the devs. and I think a lot of things are going to go well, it's just a matter of giving time to time.

* If the cause of high hash rates are botnets, it's just a question of neutralizing them. Is the detail like?

* If the causer are real miners with high hash rates in their mining rigs, the algorithm of the currency will already be in charge of finding a solution, I believe, however it is not enough to inform these miners that are affecting the network and also to themselves.

* It is clear that at least 98% of the hash power is concentrated in only a few users in a certain pool, for example: if there is a total of 1000 users in a certain pool, of those 1000 users only 2% that would be about 20 users, would be concentrating the largest amount of hash (98% hash rate), the rest; that would be 980 users would be contributing only a 2% hash rate to the total hash rate of that particular pool.

To be more educational, it would look like this:

Data:
-Pool hash rate: 34,000 Kh / s
-Quantity of pool workers: 1000 workers
-98% of workers: 980 workers, these only generate 2% of total hash that is equal to: 680Kh / s
-2% of workers: 20 workers, this micro group generates 98% of total hash that is equal to: 33,320 Kh / s
***** In a few words, practically the total network belongs only to those 20 users ********

This maybe looks a little exaggerated, but it is only to give an example, to have an idea of ​​"THE BRUTAL DESPROPORCION OF KH / S THAT CONTRIBUTES EACH USER TO THE NETWORK"

 :or






















Pages: « 1 ... 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 [1121] 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 ... 1310 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!