Could anyone, please suggest, the solution to resolve this problem  I'd suggest try re-syncing the block chain; the fast way is to download blockchain data from our site. |
|
|
|
I'm on ubuntu now. No antivirus.
What version of wallet you ran in the past? |
|
|
|
Hey ! Long time since my last come. And sadly, after another try to reach up my wallet on my Pi, I got a blk[something] error. I do not know what we said last time about this, but I might be generous if the problem is solved tonight !
Hey bud, do you use the new wallet? What if you follow the new release guide? |
|
|
|
hopefully it will nicelly go up and not pump and dump 44chan style.. because it is a good tech. the only thing a little strange is dev talking about web hosting cost an so on...this should have brought some money by now to him , no? didnt he keep some coins?
I can't recall that I mentioned being lack of funding running the web hosting. I've been years in support of hosting like the main site, forum, a couple of VPS including the primary one m-hash.com running on a major node $20/mo for years now; putting all together you know how much would be. There was a very tough time though, while I've been through, and make myself to settle down in another place. I believe I can keep going. Today's rising definitely won't bring money to me, though I do have some coins. Things like those people may not know like tens k support for an exchange hacked in order to recover users' account, PoM, PoI funds and so on that drained some somehow, I believed magic did quite that way for PoI too. Absolutely it's not a game about rich, but coding and keeping the coin going is such fruitful and meaningful. Either way, I'm glad to see a nice move in price; actually the most important are the activity and volume that brings, which means a lot and very much makes me some time to brew wines. |
|
|
|
I have two 50K cpu, can solo?
I'd say try and see.  |
|
|
|
Price is looking pretty stable today and market cap has >$200k for about 3 days now - despite the downturn in the BTC price - previously during a couple of pumps we only manage to keep the level over $200k for about a day or so. Magi is doing pretty nicely comparatively to its past.
It's been a nice move. |
|
|
|
|
This is only part of the things we're doing I'd say, and I know where we're heading. All were being designed according to what's supposed to be -- a purpose, and the things hence worked out as such. Of course, we shouldn't talk merely all just the basic coin things, instead we're keen to some more horizons I'd like to be going. Stay tuned..
|
|
|
|
the more coins you stake the bigger the rewards, sure if by default u can only stake 10k at a time in a wallet , who wants to run 30 wallets. People dont want to have to optimize and change paramaters manually. i should be able to download the wallet and stake my stash and reap rewards. the staking is more centralized here by the few who have messed with paramaters or devs that can optimize their rewards. good luck to this coin but this is not a long term for me
I can't argue more, bud. There are info around one can easily pick up. If you don't think this PoS meant something, we're fine too. There are really things you misunderstood; 10k at a time staking in a wallet is a very wrong understanding. I believe a more general staking will serve your purpose which can be found from a coin list. Good luck! |
|
|
|
i originally bought this cointo hold n stake longterm but it seems pretty crazy if u have 300k 400k n cnt get a reward, so while i dnt make it a habit of atoring large amount coins on polo seems not logical keep in wallet tht reaps no benefits
Well, I'd believe most did stakesplitthreshold and stakecombinethreshold for optimum staking that isn't difficult at all. Personally I got a wallet running and staking 24/7. I recommend you try this (example for simplicity only though it's not necessary exactly the way I'm saying): 1) Get a fresh wallet, and a fresh address 2) Send an amount say 10,000Σ to the fresh address 3) Lock the wallet with a password, and unlock to enable staking, just like the way of PoS staking normally 4) Keep the wallet running until you get stakes 5) Repeat 1) ~ 4) for the rest of coins if you have. Not being able to stake with a number of coins is a misunderstanding. I did try to figure a way of staking rewards inversely proportional to the total number of coins, while I noticed this may not be likely in the scope of the present principle, and it's not that straightforward we should go with either. It is true, though, that I'm not a fan of simple big rewards by having simple powers. I'm not meaning going the other way around, but keeping the things under limits, that's the way of operation in nature. And I stand for a high-priority point where people contribute to the network get rewards preferentially. |
|
|
|
Just asking, is this normal?  It's been like that since last week. Thanks! Move cursor to the top of the price info (BTC/XMG or USD/XMG) to show tooltips; price updates only occur by clicking in order to avoid any interference with the wallet operation. |
|
|
|
I think your old i7 are better than my server CPU, my i5 is more powerfull than the intel avoton for mining I mine too in a pool, pom.m-hash, with the sweet spot controller so the CPU ran only at 100% when the block reward is greater than 12 XMG and the rest of the time he is at 10%. It's more profitable to mine in pool I think, you always have a little reward but the majority of the time the block reward is 1 XMG, when I look the graphs on the pool there are only 2-3 hours per 24H where my CPU > 10%. I like magi and the fact that it is designed for little miners with CPU but in reality magi is only profitable to the big miners, they come when the block reward is big and when the block reward is low they can quietly put their power for mining another coin and we, the little miners, have only 1 XMG blocks to mine for the majority of the time. If you want try to solo mine it's not very complicated to setup, I wrote what I did in this topic for linux, I used a tuto that I found in this topic and just changed a few things. For windows I have an option for solo mining in the sweet spot controller program but I never tried it. You will not be rich in solo mining, only happy when you find a block I agree, though small miners are capable, concerns remain somehow like the profits; solo mining does sound made a point. Anyway we're looking into rejecting big miners sharply with a more comprehensive consideration of the likability and a solution in the incoming release. |
|
|
|
I am talking about on the exchanges, there's been a spike of activity in the past 24hr and the price went up by 10-15%.
Don't know the reason. Exchanges have there own lives. Sometimes price goes up because of a Magi update, sometimes prices goes down because of the value of btc. I know one thing; Magi team & community are very active and working on a awesome future for the coin of the Magi. We will continue with that for a long long time. hey 111magic, I am Looking for great coins with group,if you can help me to understand what makes you to hold Magi for longer period of time , means salient features of it , unique developments ahead, and price appreciation since launch. Sometime no reasons I guess; 111magic made me recall the old time; bottom line some of us are sticking around, and for sure we're looking for a future. |
|
|
|
Hi,
It's been a while now cryptopia having some issues with their wallet.
The market there is paused.
Please somebody contact them who has technical knowledge.
Thank you.
Did they update the wallet already or is it in progress? I asked them in chat what's going on, they didn't give me any info. Only thing they told me is to tell the dev to contact them. Ok thats good to know! Joe pls check info from Mozsi! Thanks amigo! Actually I sent a message to them a while ago, but no response yet. I just sent another... |
|
|
|
hmm seems that no big holder here has the funds or ability to take mkt to a decent price tho. 2100 satoshi for this limited supply coin is nt vry good. lets see if it improves
Magi is growing slowly, but has done pretty well over the last year - Market Cap has increased from 40k to 200k in 12m, not explosive growth but nice and steady SMA - there has been a nice bit of volatility - but usually with a range of 1500 to 3000 sat, its a unique coin and difficult for the big players to mine and take advantage of with large hash rates - which is probably why the growth rate is how it is, volume is significantly up over the last year too. I'm very much aware of two important things we're missing: marketing and road-mapped development. I'm glad that the coin has been existing without confusing people by, for example, pump; pump is one of the major factors in this crypto land in the pricing leading to speculation and in turn the pumping. There should be a growing curve. Looking back price/cap does sound the coin provides a field for people to participate into now and then, though it's not necessary good to holders. Except for concerns of being alerted delisting from Bittrex or potential delisting by Poloniex due to low volumes, I live with where the coin is now that seems decent and the fact that people can join the party fairly at different time. |
|
|
|
I've notice that the price info disappeared from wallet from about 2 days.  Also the wallet isn't staking from atleast 10 hours  getmininginfo
{
"blocks" : 1220363,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 2.04336221,
"proof-of-stake" : 0.01807929,
"search-interval" : 1
},
"blockvalue" : {
"difficulty-V2" : 3.18456382,
"blockvalue" : 2.77791977
},
"netmhashps" : 44.34277312,
"netstakeweight" : 928195.69517220,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 17615,
"maximum" : 0,
"combined" : 17615
},
"Expected PoS (hours)" : 1,
"stakeinterest" : 0.03125170,
"testnet" : false,
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 44342773,
"testnet" : false
} I can see that you seem to have PoS coming. What does "getmininginfo" give? I don't see issues with price info; try to click on it to refresh. |
|
|
|
Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.
Will change the connect line into addnode and try again.
Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.
"Connect" will force connection with the nodes only we're running. There seems no issues with "connect" as I just tried. |
|
|
|
Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine. trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat 61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23 (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat 46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout I can upload the debuglog for you if you need. I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash daemon: magid getblockhash 1217757 qt-wallet under console: 819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htmOnce this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet: connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check. |
|
|
|
I'm running the new wallet but I see this error and can't get past the block...
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work
Also got those issues, always losing connection. It seems due to connection with misbehaved peers, which are supposed to be disconnected. Pls try to remove peers.dat, add only the following nodes, and restart the wallet: addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc |
|
|
|
I just completed my first successful - fully automated Magi transaction =) exciting stuff.
Curious what you got? |
|
|
|
Joe, what would be the best blocksize for maximum PoS value? I can't figure this out of the figures above. I now use blocksize of 1000 XMG (without splitting), PoS reward around 1 XMG per 10K XMG a day. (4%) Sorry for my delayed reply. I'd say 1000XMG is an ideal number. However, we might take into account the factors like how much time to get a PoS block, and how much margin generated on a certain base of coins; putting all together would give a more accurate number, for which some cals I haven't had will need to be taken. I actually would like to put the best number somewhere at or below 500XMG, which is apparently not the case at this moment. I'd get it onto one of the optimizations to be done regarding changes in the PoS. It's not intended to frustrate staking but to enhance network activities without affecting those wallets under frequent staking. |
|
|
|
|
Show Posts
