|
There is no way to proper mine now. See previous posts.
|
|
|
|
 Is there a way to mine magi now or there's no any way?
NO WAY |
|
|
|
I can provide 3 static ip for nodes with up to 5000 connections, and can link each with other. After hardcoding those ip in new version of wallet we can forget about splitting.
Chain will work correct and dev can calmly solve problem with splitting.
Hardcoding need to avoid connect to potential wrong nodes.
Simple rollover back is not solve anything.
Or we can simple buy VPS hosting for nodes, it costs 4$ month for 1 mounth for each. C'mon, it is simpliest and 100% working solution to stabilize chain. |
|
|
|
|
I can provide 3 static ip for nodes with up to 5000 connections, and can link each with other. After hardcoding those ip in new version of wallet we can forget about splitting.
Chain will work correct and dev can calmly solve problem with splitting.
Hardcoding need to avoid connect to potential wrong nodes.
Simple rollover back is not solve anything.
|
|
|
|
|
So vote my plan or suggest why it bad or something else.
|
|
|
|
I am developer with +10 years experience.
I know that at least first and last step easy to realize.
I am developer with +20 years experience. I know that nothing can`t be realised easily without bugs  I am developer with +30 years experience. I know you can't solve the problem without knowing what caused it. I am developer with +40 years experience. I can devide by 0!) |
|
|
|
I will try to detail my suggestions Example implementation of FIRST step, not final just one of possible variants: Our developer link to all 8 pools operators (may be we have more?) we see on https://poolinfo.systms.org/#magi + bittrex exchange Those pools must significant increase maxconnections parametr (1000-5000) in daemons to accept all new connections Also those pools must provide connection information (ip, ports) Then 1. Hard code non-drop connections to those pools to new version of wallet 2. Add condition by default that blocks only from those pools are true 3. This condition must be off in pools daemons ... PROFIT) We have stable chain General steps to improve stability of MAGI chain:1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true. 2. Try to find out vector of attack (pow or pos) and develop a protection system. 3. Test protection system several times with emulation of attack 4. Remove hardcoded pools. Please vote for my plan: https://twitter.com/moiseev_aa/status/899972940887994369 |
|
|
|
General steps to improve stability of MAGI chain: 1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true. 2. Try to find out vector of attack (pow or pos) and develop a protection system. 3. Test protection system several times with emulation of attack 4. Remove hardcoded pools. Please vote for my plan: https://twitter.com/moiseev_aa/status/899972940887994369If you're not a developer than what's purport to vote or not? Can you implement your "plan"? Seems you just rend the air. I am developer with +10 years experience. I know that at least first and last step easy to realize. If so, I'm sorry for my words. Please give me the link to coin that you've launch My developer work not linked with crypto coins. |
|
|
|
General steps to improve stability of MAGI chain:1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true. 2. Try to find out vector of attack (pow or pos) and develop a protection system. 3. Test protection system several times with emulation of attack 4. Remove hardcoded pools. Please vote for my plan: https://twitter.com/moiseev_aa/status/899972940887994369 If you're not a developer than what's purport to vote or not? Can you implement your "plan"? Seems you just rend the air. I am developer with +10 years experience. I know that at least first and last step easy to realize. |
|
|
|
General steps to improve stability of MAGI chain:1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true. 2. Try to find out vector of attack (pow or pos) and develop a protection system. 3. Test protection system several times with emulation of attack 4. Remove hardcoded pools. Please vote for my plan: https://twitter.com/moiseev_aa/status/899972940887994369
|
|
|
|
The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.
Without this steps, we will have new splits again and again.
just one more time) |
|
|
|
To ALL,
The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.
I buy 236XMG yesterday 9LXmpBZC54DwirHEc9z5NYKwihuqaj1EHV, rollover back after this tx 25276115ba9311ddf26ecbd754abb1f5d7a169f5f2cfcec7ae6a0bc94549b26f |
|
|
|
On Zpool, all blocks from the last 12 hours were orphans. I have also a small payment from them that has 0 confirmations in 45 minutes. All so confusing  to be or not to be I'm same Why u need XMG if you can`t sell it at bittrex..... Охотник, прошу прощения за мой фГанцуззский или я не так понял пост чувака... Но он вроде пишет, что типа майнил, майнил, но все это пошло прахом ДО вывода (как и у меня). О битрексе речи не было Sorry for my bad English ша ты получишь здюль за использование русского языка тут) |
|
|
|
Staking. Your weight 1. Network weight is 152711. Expected time to earn reward is 159 day(s) I wonder where I got 1 weight. I was at work all day my CPU was looking for in solo! Did I find a block or I just spent like all 10 hours in an empty one Sorry for my english! I see that you are complete newbie), but I try to explane: Stake block (pos-block) and solo mined block with CPU (pow-block) are defferent kind of blocks. You have probability to find pos-block in next 159 days Probability of finding pow-block depends of your hashrate and current difficulty of net. If you have no new tx in wallet that means you find nothing. |
|
|
|
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer... just after block 1449484 7 blocks of 800XMG or more https://imghost.io/image/P5pHCNo absurt high stakes. You made a mistake with this. |
|
|
|
|
new day - new fork)
waiting for 1.4.3 wallet with new checkpoints)
|
|
|
|
|
if "blocks" : 1449525 is true chain
and "difficulty" : {
"proof-of-work" : 0.44014829,
"proof-of-stake" : 0.00399164
},
that mean significant pow part mining on other chain)
we have new split?
|
|
|
|
|
My linux wallet (for solomine only) suddenly stop sync.
A replace "connect=104.128.225.215" with "addnode=104.128.225.215" and when connections has become > 1 sync continued.
So connection to only one node to save chain is not working, therefore we will have new split very very soon.
|
|
|
|
|
Show Posts
