Bitcoin Forum
January 14, 2026, 11:43:10 PM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 1172 [1173] 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 ... 1310 »
  Print  
Author Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]  (Read 2377376 times)
jonathin.r
Member
**
Offline Offline

Activity: 98
Merit: 11


View Profile
April 23, 2018, 07:25:41 PM
 #23441

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

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

Activity: 22
Merit: 0


View Profile
April 23, 2018, 08:30:29 PM
 #23442

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

Seems fine but how do you get all pools onboard? You can't - and whichever one is the holdout will be the one used for the attacks.

I don't know what the actual solution is though. What is the feasibility of a protocol side upper limit on hashrate for any one mining device?  If that upper limit is a carefully selected value it might solve a lot of problems. But this is probably not that easy to actually implement.
paul30003
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
April 23, 2018, 11:04:54 PM
 #23443

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

So I've been a programmer for several years now, I am quite fluent in C, but not so much with C++ for the last couple of weeks, I have been going over the Magi code and the m7m algo in the hope I could suggest some ideas and fixes to the dev, problem is without knowing the exact method the attacker is using, its hard to suggest a fix.  How the attacks are happening, I would expect is being kept very secretive as if this information was to make it into the wild, then many crooks would be jumping onboard and hitting the network hard.

Aside from building wallets and custom miner code, I have been looking at starting a pool.

I'm not sure if I will yet, but if I did I would be enforcing strict hash rate limits, a place to answer queries and complaints from pool members.  Email and or support tickets.  One of my biggest problems with mining pools, has been little to no communication or reply from pool owners.

Another feature that I have thought about, could be a weekly random draw with prizes in XMG.  The prize fund would come from 100% of donations.  All who donate would automatically be in the draw.

I have a wealth of experience with running servers, web applications, including CMS portals, databases, forums, live chat, support ticket systems.

If I do go ahead with this, then I will obtain a paid SSL cert from a trusted CA, a reliable dedicated server, rather than a shared VPS.  Low server latency would be key.

Maybe if I got a lot of interest from sub 150Khps miners who are sick of the whales killing the pool rewards, I could get something started.  If mining could be more rewarding for people with lower hashrates, maybe It could give Magi a small boost in popularity and value.

Just thought I would put this idea out there for opinion. 
tazzz013
Newbie
*
Offline Offline

Activity: 118
Merit: 0


View Profile
April 23, 2018, 11:06:58 PM
 #23444

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

Seems fine but how do you get all pools onboard? You can't - and whichever one is the holdout will be the one used for the attacks.

I don't know what the actual solution is though. What is the feasibility of a protocol side upper limit on hashrate for any one mining device?  If that upper limit is a carefully selected value it might solve a lot of problems. But this is probably not that easy to actually implement.

At least we can agree on on thing,  Its need to be fixed sooner than later.
Jeremy450
Newbie
*
Offline Offline

Activity: 154
Merit: 0


View Profile
April 23, 2018, 11:28:31 PM
 #23445

All of this talk is useless/pointless the devs wont do any of this that we are crying/begging/desperately needing for OUR COIN because it decentralizes their idea!!! all of this was all talked about in January its total pointless the devs said it them selves they wont implement any of this 111magic said it himself.

mean while we are being kicked in the balls by big whales like below

http://jemisp.com/screen5.png
Jeremy450
Newbie
*
Offline Offline

Activity: 154
Merit: 0


View Profile
April 23, 2018, 11:36:16 PM
 #23446

they aren't listening or talking about the situation, theres no communication, theres no reinsurance. its all hush hush we have something big happening. Instead of focusing on the problem instead of telling the community they are working on a solution. Actions speak 5 times more then words and so far we are seeing nothing.

almost 4 months of no actions. i'm a software developer if i had my community/clients complaining about an issues i would of dam fixed it already. That way i know they would have faith in me and my software.
hemidart
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
April 24, 2018, 12:17:11 AM
 #23447

they aren't listening or talking about the situation, theres no communication, theres no reinsurance. its all hush hush we have something big happening. Instead of focusing on the problem instead of telling the community they are working on a solution. Actions speak 5 times more then words and so far we are seeing nothing.

almost 4 months of no actions. i'm a software developer if i had my community/clients complaining about an issues i would of dam fixed it already. That way i know they would have faith in me and my software.


+1
DatsunPatrol
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
April 24, 2018, 02:09:14 AM
 #23448

Maybe if I got a lot of interest from sub 150Khps miners who are sick of the whales killing the pool rewards, I could get something started.  If mining could be more rewarding for people with lower hashrates, maybe It could give Magi a small boost in popularity and value.

I am interested in this for sure. Since you have studied the code a bit maybe you can clarify to me how the hashrate affects the block reward. If you have a perfectly moderated mining pool that actively kicks off users with >250kh/s does that gaurantee a larger reward when the pool atually finds a block or are bad actors on the global network still going to spoil it for us?
earl3000
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
April 24, 2018, 04:41:55 AM
 #23449

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

Seems fine but how do you get all pools onboard? You can't - and whichever one is the holdout will be the one used for the attacks.

I don't know what the actual solution is though. What is the feasibility of a protocol side upper limit on hashrate for any one mining device?  If that upper limit is a carefully selected value it might solve a lot of problems. But this is probably not that easy to actually implement.

One thing we should not forget, what if the attacker sets up his own pool (it is pretty easy), with the hashrate that he seems to have, it might even work,
Iame3
Newbie
*
Offline Offline

Activity: 102
Merit: 0


View Profile
April 24, 2018, 05:11:14 AM
 #23450

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

Seems fine but how do you get all pools onboard? You can't - and whichever one is the holdout will be the one used for the attacks.

I don't know what the actual solution is though. What is the feasibility of a protocol side upper limit on hashrate for any one mining device?  If that upper limit is a carefully selected value it might solve a lot of problems. But this is probably not that easy to actually implement.

One thing we should not forget, what if the attacker sets up his own pool (it is pretty easy), with the hashrate that he seems to have, it might even work,

Would it be possible to hardcode mining only from registered pools?  I was also thinking about limiting hashrate of everything to, say, 3mh/s, but then one can set multiple pools.
jonathin.r
Member
**
Offline Offline

Activity: 98
Merit: 11


View Profile
April 24, 2018, 10:17:31 AM
 #23451

Okay, message received. Bad idea, but you want to hear an ever worse one that could possibly work and not require any changes to the current MagiCoin infrastructure?

Hand-approved pool registrations in conjunction with pool-side hashrate limits, where users would need to disclose their estimated hashrate upon registration. That way, if a user goes over their registered hashrate (or if their registered hashrate is exactly the pool limit, then the pool limit), then they will be kicked from the pool. Sure, it adds more work to the pools, but it ensures the fairness of the rest of the miners who are actually following the rules. You could just solo-mine with a botnet, but at least that's less unfair to pool miners because you're not invalidating the blocks of miners who did nothing wrong. You're just lowering the block reward for everyone on the network, which is still unfair.

Seems fine but how do you get all pools onboard? You can't - and whichever one is the holdout will be the one used for the attacks.

I don't know what the actual solution is though. What is the feasibility of a protocol side upper limit on hashrate for any one mining device?  If that upper limit is a carefully selected value it might solve a lot of problems. But this is probably not that easy to actually implement.

One thing we should not forget, what if the attacker sets up his own pool (it is pretty easy), with the hashrate that he seems to have, it might even work,

Would it be possible to hardcode mining only from registered pools?  I was also thinking about limiting hashrate of everything to, say, 3mh/s, but then one can set multiple pools.

The problem in that is that it removes the idea of a decentralized currency. By picking and choosing who is allowed to process transactions may cause a case of favoritism that is against the idea of decentralization in the first place. We're currently stuck between the proverbial rock and hard place, where the rock is all these whales coming onto the network to flush us sub-150kh miners out, and the hard place being respecting the ideology of a decentralized cryptocurrency in the first place. The same could be said for my idea of a pool-side hashrate limit, since you're enforcing which people with which amounts of hashing power can come utilize your pool, but it's not such a heinous idea given the current state of the coin.

I hate to say this due to how much I used to support this coin, but if something isn't done about this issue soon, then I ask that someone please fork the project and be more diligent in responding to your user's complaints. The concept of this coin is incredible, but this lack of response from the developers is disheartening.

My XMG Address: 9LzxHqsxrRPMCyBffjMc3cLuB5hwEG5Ufq
"Un pour tous, tous pour un" - The Three Musketeers, 1844
jonathin.r
Member
**
Offline Offline

Activity: 98
Merit: 11


View Profile
April 24, 2018, 10:37:13 AM
 #23452

(snip)
Maybe if I got a lot of interest from sub 150Khps miners who are sick of the whales killing the pool rewards, I could get something started.  If mining could be more rewarding for people with lower hashrates, maybe It could give Magi a small boost in popularity and value.

Just thought I would put this idea out there for opinion. 

I think this is a great idea! Incentivizing anything makes it more attractive to public attention. Appealing to the potential lower-hashrate miners like myself could greatly strengthen the network against what are essentially burst-fire round-robin 51% attacks. From what I can see, these attackers are bouncing from pool to pool, and these pool owners are either that naive, or genuinely don't care that the platform that they are making money on is getting slapped around. It can't be that hard to throw some IPs into UFW and call it a day, right? Huh Sure, there is the pesky issue of Tor nodes and VPNs, but if pool owners at least tried to do this, I feel it would drive away the less-motivated attackers into oblivion.

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

Activity: 154
Merit: 0


View Profile
April 24, 2018, 11:25:24 AM
 #23453

111magic and joe your community is asking you to speak to us about the situation. And your solution to the issue. Right now you guys are pissing everyone off by not talking about it. I'll quote something you said to me in a PM "But i also know if we continue with responding on those posts it will do no good." that is only part of the message. I'm not trying to DIS you, your message to me had alot of a bright future in it. if i need to i can prove this with a screenshot.

You say this. but the problem is yous haven't truly spoken up to the community on this problem. You want us to listen? then speak to us write a message explaining whats going on and your solution to fix it and we'll listen. is that so hard? do you have that much doubt about your fellow community members that we wont listen?

Even if you have to post it a few times so everyone see its. I dont care seeing the same message from you guys telling us whats happening, what your progress is in fixing this problem, etc. You need to show everyone that this community is alive, this coin is alive and you want to kick the whalers asses. If you guys arent going be leaders then shut this coin down cos right now you's arent helping the situation!!!!! You have doubt in what i say? i'll happily do a poll to prove to you that we want to hear from you guys and what we want to hear.

I got accused of being a cry baby cos i spoke my mind about this situation in January. You dont like to repeat your selves? then add a blog on your site and say whats happening in there so everyone can see going on.

I love my sayings for one main reason they tell the truth and to the heart.

"Actions speak louder then words."
[/color]
earl3000
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
April 24, 2018, 12:16:19 PM
 #23454

111magic and joe your community is asking you to speak to us about the situation. And your solution to the issue. Right now you guys are pissing everyone off by not talking about it. I'll quote something you said to me in a PM "But i also know if we continue with responding on those posts it will do no good." that is only part of the message. I'm not trying to DIS you, your message to me had alot of a bright future in it. if i need to i can prove this with a screenshot.

You say this. but the problem is yous haven't truly spoken up to the community on this problem. You want us to listen? then speak to us write a message explaining whats going on and your solution to fix it and we'll listen. is that so hard? do you have that much doubt about your fellow community members that we wont listen?

Even if you have to post it a few times so everyone see its. I dont care seeing the same message from you guys telling us whats happening, what your progress is in fixing this problem, etc. You need to show everyone that this community is alive, this coin is alive and you want to kick the whalers asses. If you guys arent going be leaders then shut this coin down cos right now you's arent helping the situation!!!!! You have doubt in what i say? i'll happily do a poll to prove to you that we want to hear from you guys and what we want to hear.

I got accused of being a cry baby cos i spoke my mind about this situation in January. You dont like to repeat your selves? then add a blog on your site and say whats happening in there so everyone can see going on.

I love my sayings for one main reason they tell the truth and to the heart.

"Actions speak louder then words."
[/color]

I new here, but I second this request, with one minor addendum, in the unlikely case the project team can't continue, don't shut the coin down, let's find a new team / team members, who can/should continue / help with XMG.
edward0181
Full Member
***
Offline Offline

Activity: 276
Merit: 100


View Profile WWW
April 24, 2018, 12:23:31 PM
 #23455

AS PER SLACK:

Code:
edward0181 [11:44 AM]
wondering what latest status is... see and hear no news yet :disappointed:

SavvyKrypt [2:05 PM]
Everyone is worried no news no communications
It’s very worrying

joelao95 [2:20 PM]
We’re working on things, will update ASAP


So just... take a relax pill or some coffee... project is running for so long, no-one will abandon it just yet.

hemidart
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
April 24, 2018, 01:23:01 PM
 #23456

Orphans starting on Trasmamod, more hashing in a vacuum.
Filkus
Newbie
*
Offline Offline

Activity: 53
Merit: 0


View Profile
April 24, 2018, 01:49:25 PM
 #23457

I am a sub 150k miner, and I have to wonder if none of you notice what I have during these weird times:

I'm getting more coin per day thn I was when things were "STABLE". Now, sure, I don't make much, but it is more than before.

Is it not the same for the rest of you?

On a different note: Is everyone here minting as well to help the network?

Last thought: XMG is at $0.55 today and I am now in profit after 4 months.

I am curious about the dev situation and would like to talk about strategies for expanding that team.

Overall, I am happy and not complaining.

Am I the only one noticing the increase in coin/day?
starmman
Legendary
*
Offline Offline

Activity: 1484
Merit: 1029



View Profile
April 24, 2018, 02:14:51 PM
 #23458

I am a sub 150k miner, and I have to wonder if none of you notice what I have during these weird times:

I'm getting more coin per day thn I was when things were "STABLE". Now, sure, I don't make much, but it is more than before.

Is it not the same for the rest of you?

On a different note: Is everyone here minting as well to help the network?

Last thought: XMG is at $0.55 today and I am now in profit after 4 months.

I am curious about the dev situation and would like to talk about strategies for expanding that team.

Overall, I am happy and not complaining.

Am I the only one noticing the increase in coin/day?

Good to hear about the increase - I stopped mining a while ago (staking and trading made it not worthwhile) - so no increase for me - staking revenue seems fairly linear although I don't chart it, trading revenue seems great today
fullspeedin
Full Member
***
Offline Offline

Activity: 624
Merit: 100


HiveNet - Distributed Cloud Computing


View Profile
April 24, 2018, 02:23:09 PM
 #23459

it looks interesting from the side, I hope you manage to get to the ico stage if you wish it, for example I do not understand the POW \ POS system to the end and got a negative experience using POS Token

Vitalik_Pedik
Newbie
*
Offline Offline

Activity: 168
Merit: 0


View Profile
April 24, 2018, 02:52:28 PM
 #23460

Orphans starting on Trasmamod, more hashing in a vacuum.
You not hashing into a vacum, when I finish my so called attack, you will get much bigger rewards due to POW block rewards stay big.
Pages: « 1 ... 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 1172 [1173] 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 ... 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!